Deploy Application in ONEWEB

ONEWEB provides built-in Pipeline to deploy the complete application or even parts of an application to another server runtime. For e.g. user can choose to deploy only microflow or user can deploy only page to the UAT or SIT environment using pipeline.

ONEWEB Pipeline provides different types of service provider for deploying different component type.

• Deploy Microflow.

• Deploy Pages.

• Deploy Business Process.

• Deploy Smart Forms.

• Run Database script.

• Deploy jars/war to application server.

• Add datasources on application server.

To deploy an application created on ONEWEB to another environment, the basic steps are as shown below.

Step 1. Design the pipeline for your application deployment. To design the pipeline, go to the Deployment and Distribution menu in AppSpace.

Step 2. Choose Pipeline Type as 'Deploy Application'. Enter details including environment configuration and secrets.

Step 3. Create the stages for deploying the various components that are part of your application. The user has to add one stage each for deploying each component type to the target runtime. For e.g., one stage for deploying microflow snapshot and another for deploying pages from the snapshot. Users need to input both the environment properties as well as the runtime host server path. The runtime host path is mandatory and needs to be correct.

Step 4. Complete all stages for the pipeline.

Step 5. Once you design the pipeline, you can go ahead and execute it every time you need to deploy your app to the target server. For this use Execute pipeline option.

Step 6. The Final step is to verify the deploying of the modules. Go to the Deployment History menu. Click on the ... icon. Users can check the real-time logs in the view menu.

Step 7. Once complete the pipeline the status is shown as below.

Deployment Center will deploy the components in the snapshot version to the selected pipeline runtime environment. Users can monitor the progress on the screen. If any error occurs, the user can see the error details from the log output.

Users can add several additional stages to the pipeline to execute different scenarios. To run the database script as part of the pipeline stage, the list of properties is different. Currently, this stage supports only Postgres driver as shown in the default value.

The stage properties for deploying jar or war files to the JBoss server are as shown below.

The stage properties for adding a data source to the JBoss server are as follows.

User can also pass data from one stage to next using syntax {{sid.variable_name}}