Integrating with a version control system (VCS)

Whenever you click Commit on the Manage Solutions page in Case Builder, the server saves new and updated solution assets to the design object store. If you integrate with a VCS, the server also copies the changed solution files to the directory that you designated to act as the sandbox. This sandbox provides a staging area for the solution files that are to be stored in the VCS. Solution files are copied to the appropriate sandbox subdirectory according to the solution and the user. The server then runs your commit script to check in the changes from the sandbox to the VCS. The commit script creates a change set that contains all new or modified solution assets, associates comments with each asset, and checks the change set into the VCS.

After a solution is committed, you can click Deliver to check in the solution as a whole to the VCS. After the server copies all solution files and a solution manifest file to the sandbox, the server runs your deliver script to check in the files from the sandbox to the VCS. The script then creates and labels a baseline or snapshot of the solution and delivers it to the VCS.

After you deliver the files, you can deploy an IBM Business Automation Workflow solution from the VCS into another environment, such as a production environment or a different development environment. You first extract the solution assets and solution manifest from the VCS according to a specific delivery label. You then use the solution manifest file to import the solution into the design object store in the new environment before you deploy the solution.

You can use the graphical user interface of your VCS to export the solution assets and solution manifest from the VCS according to a delivery label and then use the IBM Business Automation Workflow Case administration client to import and deploy the solution to the new environment. Alternatively, you can create a custom script to automatically extract, import, and deploy the solution.