Configurations for integrating with BMC Middleware Automation

You can integrate version 8.2.03 Patch 3 of BMC Middleware Automation with version 4.3.00 of BMC VaraLogix Q Deployment Automation. With this integration, you can perform various functions in BMC Middleware Automation by using the BMC VaraLogix Q Deployment Automation user interface with the help of automation scripts. To be able to perform these functions you must perform certain configurations tasks.

Before you begin

1. Ensure that you have operational knowledge of version 8.2.03 Patch 3 and later of the BMC Middleware Automation product.
2. Ensure that you have installed version 8.2.03 Patch 3 of BMC Middleware Automation and it is up and running.
3. Ensure that you have BMC Middleware Automation, dispatcher, NSH and RSCD agents installed on the same host.
4. Ensure that RSCD agents are installed on every target that you want to retrieve files from or deploy to.
5. In BMC Middleware Automation: you must have updated the setupDeliver.properties properties file.

Configurations required for the integration

You can choose from two supported procedures to integrate with BMC Middleware Automation. BMC Software, Inc., recommends the first procedure because it aligns with other VaraLogix Q Deployment Automation actions. The second procedure requires additional topology configuration.

Create BMA Configuration xml files as RLM action libraries

1. Install BMC Middleware Automation on the dispatcher host.
    Note: Please make sure that you already have a host with a dispatcher installed.
2. On the System tab of the BMC VaraLogix Q Deployment Automation, in the Configure area,  click Servers, and then click New Server to create a server that points to a BMC Middleware Automation supported target (IBM WebSphere, Oracle WebLogic etc).
3. Create a topology around the server:
   • Create Channel templates
   • Create Channel
   • Create Environment
   • Create Routes
4. Add BMC Middleware Automation properties which contain server profile information and token values to the channel pointing to the server.
5. Import BMC Middleware Automation actions into the action library with the Bma@ prefix (optional) or use out of the box BMC Middleware Automation Actions which starts with Bma@ prefix.
6. Create a package that will trigger the process.
7. Create a deployment process for the Middleware server channel template.
8. Add imported or out of the box BMC Middleware Automation config actions to the process.
9. Deploy the package to launch the process.

Retrieve BMA Configuration xml files as Package References

1. Install BMC Middleware Automation on the dispatcher host.
2. Create a Server to point to that host.
3. Create a BMC Middleware Automation channel template.
4. Create a BMC Middleware Automation Channel associated with that BMC Middleware Automation Channel Template.
5. Add BMC Middleware Automation properties to the channel.
6. Build an environment and route around that channel.
7. Create an empty Bma action under the appropriate pack: Websphere 7, Weblogic, etc.
    Example: Bma@intallserver
8. Create a process with trigger on the *.xml file and add the Invoke Action deployment activity with the Action Name Bma@installserver (or any other Action Name created in Step 7).
9. Create a package to retrieve a BMC Middleware Automation config .xml.
   
10. Add a reference to the package with same name as action name in Step 7 and refer to the path of the Configuration xml.
11. Deploy the package to launch the process.