Packaging Standard Overview

Packaging Standard for CI/CD Automation

Packaging Standard, also known as JPS, is a framework for preparing ready-to-deploy application and add-on templates. A JPS package can describe the target environment, deployment workflow, resource allocation, configuration steps and lifecycle automation required to deliver a complete application.

In this article

Packaging Standard Overview

JPS packaging is designed to convert application installation and configuration logic into reusable templates. These templates can be integrated into compatible platforms and launched through an automated installation process.

Ready-to-Go Applications

Prepare complete application templates that can be installed without manually configuring every environment component.

Add-On Packages

Create reusable add-ons that extend or modify an existing environment with additional services, configuration or automation.

JPS packaging standard overview
JPS packages combine environment definitions with automated installation and configuration logic.

JPS Package and Installation Manifest

A JPS package is based on an installation manifest. The manifest describes how the target application environment should be created and configured.

Environment CreationDefines the server topology and required environment structure.
Application DeploymentDescribes how the application package or source should be deployed.
ConfigurationAutomates post-deployment setup and application tuning.
Resource AllocationSpecifies compute resources required by each server or node.
Scaling LimitsDefines the limits and behavior for supported scaling operations.

This makes it possible to bundle application topology and lifecycle logic into one repeatable deployment definition instead of configuring each installation manually.

Application CI/CD Automation with Cloud Scripting

JPS packaging works together with Cloud Scripting to automate application delivery. Cloud Scripting can connect platform API operations into a lifecycle workflow that moves an application through development, testing and production stages.

Cloud Scripting CI/CD automation
Cloud Scripting can automate multi-stage application delivery and environment lifecycle operations.
✓

From simple tasks to complex automation

Cloud Scripting can be used for small configuration actions as well as distributed application, clustering and full CI/CD scenarios.

Cloud Scripting Capabilities

When building a custom package, Cloud Scripting can combine predefined behavior, user input and container-level automation.

ActionsDefine the configuration operations and expected application behavior required by the package.
Lifecycle EventsAttach operations to specific application or environment lifecycle stages.
User InputCollect installation values from the user and use them inside package logic.
Custom ScriptsExecute custom scripts directly inside the created containers when required.
Platform APIsCombine platform API methods to automate more advanced infrastructure and application workflows.
i

Use existing examples as a starting point

Before creating a package from scratch, review ready-made JPS examples. Existing packages can often be reused directly or adapted to a new automation scenario.

Widget for Instant Application Deployment

After an application is packaged as JPS, it can be distributed through an installation widget. The widget launches the package and simplifies deployment for users who do not need to understand the underlying topology or installation steps.

The widget references the installation manifest, which describes the required cloud environment and the automated steps needed to configure the application.

Application manifest converted into installation widget
The installation widget uses the JPS manifest to describe the application environment and deployment workflow.

Typical Installation Flow

  1. The user starts installation through the application widget.
  2. The platform receives and parses the referenced manifest.
  3. The required environment and nodes are created or adjusted.
  4. Application components are deployed and interconnected.
  5. Configuration logic defined by the package is executed automatically.
  6. The user receives a ready-to-run application.
Installation widget to running application workflow
The widget initiates automated provisioning and produces a configured running application.

Package Distribution

Packaging an application makes it easier to distribute a consistent installation to other users and platforms. A packaged solution can also reduce support effort because routine installation and post-install configuration are handled automatically.

Installation WidgetShare a direct automated deployment experience with users and developers.
MarketplaceA hosting provider can make approved JPS packages available as installable Marketplace solutions.
Reusable PackageThe same manifest can serve as a base for related application versions, customer environments or add-ons.

After preparing a package, the hosting provider may review it for inclusion in the platform Marketplace, making the solution available for one-click deployment to platform users.

Important Notes

  • Use the manifest to keep environment topology and installation logic together.
  • Use lifecycle events and actions to automate repeatable CI/CD operations.
  • Collect user-specific values as input rather than hard-coding them into a package.
  • Use existing JPS examples as references when designing a new package.
  • Test packages in a non-production environment before public distribution.
  • Marketplace publication depends on the policies and approval process of the hosting provider.

What’s Next?