An approach to software development lifecycle operations for Cloud Application Integration assets

Back Next

Use case 2: simple patch deployment

Consider the following scenario and best practices:

QA finds a bug with the first deployment. The issue is with the Application Integration process.

The Developer updates the v1 Process in the development environment and assigns a new tag v2 for this process alone.

When the Developer needs to deliver the patched process to QA: Use the CLI utility and perform the following steps:

Use iics list -q "tag==v2" -o assetlist
to get the list of assets tagged with v2 and write them into the assetlist file.

Use iics export -f assetlist
to export all the assets.

Use iics extract
to extract all the assets to the SCM local workspace.

When QA needs to consume the patch: Use the CLI utility and perform the following steps for deployment:

Use iics package -o assetlist
to create the import package.

Use iics import
to import the assets into the QA organization.

Use iics publish
to publish the assets in the organization. Ensure that you publish the dependencies first and then the dependents. This can be done by publishing the assets in the following order: Service Connectors, App Connections, Processes, and Guides.

Use case scenarios

Download Guide

Watch

Comments

Cloud Application Integration Homepage