BMC Release Process Management enables you to integrate with version 8.2.00 of BMC Application Automation. With version 2.6.00, you can use the BMC Release Process Management interface to perform various functions in BMC Application Automation while carrying out your deployment process.
Integration workflow
The following figure and the corresponding steps (under the figure) describe the integration of BMC Application Automation version 8.2.00 with BMC Release Process Management version 2.6.00.
BMC Application Automation integration workflow
Before starting the setup tasks, the application team ensures that the web services are enabled in BMC Application Automation.
- The application team (internal team) performs setup tasks in BMC Application Automation, such as creating component templates, components, component groups, and BLPackages.
- The application team prepares the infrastructure: configures nodes, clusters or servers and enrolls them in BMC Application Automation.
- The Coordinator configures an application and environments in BMC Release Process Management and optionally maps components (for the specified application) of BMC Release Process Management with component templates of BMC Application Automation.
- The Requestor creates a deployment request in BMC Release Process Management with appropriate steps to perform deployment tasks (by using automation scripts) and runs the request.
- The deployment automation scripts launch necessary operations in BMC Application Automation, for example they might create and execute a Deploy Job for the necessary application.
- The application team performs a sanity check to ensure that the application is deployed correctly.
- The application team take snapshots of the deployed application components.
This task can be performed either by using BMC Application Automation or by using BMC Release Process Management with automation scripts while adding steps in a request. - The application team performs periodic compliance and audit for the targets specified earlier in the deployment tasks to spot inconsistencies.
This task can be performed either by using BMC Application Automation or by using BMC Release Process Management with automation scripts while adding steps in a request.
The application team can repeat steps 4 to 8 for deploying new versions of the same application.
Sample use case for the integration workflow
The following use case describes the preceding integration workflow and demonstrates the deployment of an online library web application called eBooks.war.
BMC Application Automation integration use case: deployment of an online library web application
- User logs into BMC Application Automation version 8.2.00 and performs the following setup tasks:
- Creates a component template, BAA_ebooks_CT1
- Creates a component instance, BAA_ebooks_CInst1, under the BAA_ebooks_CT1 component template
- Creates a component group, "CTG" and under that add the component, BAA_ebooks_CInst1
- Enrolls target servers and establishes a connection with them for deploying the ebooks.war application
- He now logs into BMC Release Process Management version 2.6.00 as a Coordinator (or Administrator) and performs the following setup tasks:
- Creates an application, ebooks.war
- Creates two environments, Pre-Production and Testing
- Creates two components, ebooks_db (manual) and ebooks_portal, and assign both the components to both the environments, Pre-Production and Testing
- He performs the following tasks in BMC Release Process Management version 2.6.00 as a Deployer (or Administrator):
- Navigates to Environment > Automation and imports all the resource automation and automation scripts available for BMC Application Automation 8.2
- Navigates to Environment > BMC Bladelogic and imports all the automation scripts available
- Navigates to System > Integrations and creates an integration server to be able to successfully integrate BMC Application Automation with BMC Release Process Management
- Maps component ebooks_portal with the component template, BAA_ebooks_CT1 (of BMC Application Automation)
- Navigates to the Requests tab and creates a Request 1001 named Deploy the .war file of the ebooks web application
- Adds the following steps under Request 1001:
- Step 1: Copy the source file of the ebooks.war application to an appropriate location on the target server by using the Baa create and run file deploy job automation script.
Example of the target location: C/ebooks_source/ebooks.war - Step 2: Create a BL package under the component BAA_ebooks_CInst1 and a Deploy Job by using the Baa create and run deploy from component automation script.
- Step 3: Execute the Deploy Job created in Step 2 by using the Baa execute job with job name automation script.
- Runs the Request 1001
- Creates a Request 1002 and under that adds a manual step to modify the following attributes of the BL package created in step f:
- Change UploadApplication=false to true.
- Change deployResourceFromSourcePath=false to true.
- In the value of the sourcePath=locationPath attribute, provide the same location path that you used in Step 1 added under Request 1001.
- Runs the Request 1002
- He performs a sanity check of the application ebooks.war to verify that the application was successfully deployed.
- He now logs into BMC Application Automation and performs the following tasks:
- Takes a snapshot of the deployed application
- Performs the periodic compliance and audit for the targets specified