Deploy

After publishing the assets and configurations that reside within on-premises runtimes or repositories to IBM® webMethods Cloud Container, you can pull assets from the given solution residing in an environment to the current solution for the same runtime type.

Note: IBM webMethods Cloud Container supports assets deployment only for the environments in the same region.

During the deployment of Integration Server or Universal Messaging assets and configurations, the latest version of assets and configurations stored in Git repository will take precedence. In order to retain the older assets and configurations, you must select those assets and configurations during deployment. Additionally, assets and configurations that have already been deployed are automatically selected by default for subsequent deployments. However, this guidance does not apply to packages.

Select a solution and then click Deploy. Select a runtime instance. All active solutions of the instance will list all the assets of the selected solution in the environment for the selected runtime instance.

Click on a solution and select the runtime package folder. Then click on the runtime instance. The assets of the solution corresponding to the selected runtime instance will appear. Select the assets and then click Promote to promote the assets to the current solution (right panel).

After you click Promote, the Promote Assets dialog box appears for the selected asset.

Select an asset and change the values for the variable substitution properties, if needed.

The variable substitution properties appear for the selected asset, only if the asset has properties. If there are any similar type of assets for which you want the same values, then select the Show similar assets to apply values option. Then select the assets in the lower panel. Click Apply to apply the property values to the selected assets. The changed values will be applied to all the selected similar assets during promotion.

On the Promote dialog box, you can type a message to describe the promotion. The promotion message will appear on the History page. For Unit Test the promotion message will not appear.

Click Check Dependencies to check the consistency of the assets and unit test and their dependencies. If there are dependencies, then for a successful promotion, you have to select all the dependent assets. Select Save and Promote to save the variable substitution and promote the assets to the next environment.

On the Deploy page, click Rollback to rollback all promoted assets to their previous state. For Unit Tests rollback is not available.

You can type a message to describe the rollback. The rollback message will appear on the History page.

When promoting assets, due to webMethods Integration Server restart, IBM webMethods Cloud Container notifies you a confirm restart message to continue the promotion of assets. Click OK to continue with the promotion of assets. Once Integration Server restarts, you will see the assets promoted to the other environment.

Rollback

Rollback is the process of restoring the deployed assets in the target repository to their previous state.

Rollback Deployed Assets

Pre-requisites

  • You must have the required permissions under Settings > Access Profiles > Administrative Permissions > Functional Controls > Assets > Deploy to rollback and delete assets.

  • You can rollback the deployed assets that are already available in the target repository at any time.

To rollback deployed assets

  1. On the Deploy page, click Rollback.

    Information regarding each rollback is previewd on the Confirm Rollback page

    • Assets: Displays the name of the asset that was deployed from the source instance.
    • Last modified: Displays the date and time when the information record was last updated.
    • Last status: Displays the last modified status of the assets.
    • Change status: Displays the assets updated state after the rollback is complete.

  2. Enter a description of the rollback in the text box. The promotion message will appear on the History page.

  3. Click Rollback.

Viewing Rollback Details

Rollbacks are listed in the History tab. You can also examine the details of a rollback in the History tab.

Deleting assets

On the Deploy page, you can delete an asset from the current solution (right panel). The asset will be deleted from the asset repository in that solution as well as from the runtime. Currently, only webMethods Integration Server packages can be deleted, not the configurations for webMethods Integration Server or Universal Messaging.

History

The History page shows the Trace ID, that is, the tracking ID, which is automatically generated on every successful status of activities such as promotion, rollback, and deletion of the assets in a solution.

From the Filters dialog box, you can choose the following filters to view a custom set of transactions.

  • Trace ID: Distinct identifier for the transaction generated internally by the system.

  • Action: Specific action of the activity. For example, Deployment, Rollback, and Deletion.

  • Created Start Date: Time at which the transaction started.

  • Created End Date: Time at which the transaction ended.

  • User: User who performed the action.

  • Message: The committed message for the selected instance.

The applied filters show up on the top of the page as shown in the following example:

Key Points to Consider for History

  • If a solution pod restarts, the packages will be automatically deployed to the new pod. As a result, the dates of the deployment logs contained in the Trace ID and the actual deployment date will differ.

  • Promotion, rollback, or deletion details appear only for the current environment.

Viewing the trace details

To view the trace details

  1. On the History page, click the Trace ID for which you want to view the trace logs details.

    A list of all the trace ID logs appears by default in the Deployment Details page.

  2. From the filters dialog box, you can choose the following filters to view the logs.

    • Product: The name of the product(s) involved in the deployment.
    • Log Level: The severity of the messages to be logged. The possible values are ERROR, INFO, DEBUG, TRACE, WARN, and FATAL.
    • Message: The status message. For example, Changes are detected in the asset repository.
    Note: For any asset deployment, the trace view details show the message as Changes are detected in the asset repository. The applied filters show up on the top of the page.

The retention period for asset deployment history has a maximum limit of 30 days. Entries older than this period will be automatically deleted.