Creating a WebSphere deployment with BMC Middleware Automation
This topic demonstrates one way to use BMA when creating a deployment to install the JDBC data provider action library on IBM WebSphere 7.0 on a target computer. This action could either be added to existing processes or triggered with a new package and process.
Before you begin
- Ensure that the BMA JDBC install config XML action with the name Bma@websphere_jdbc_install is available in the WebSphere 7 pack.
- Ensure that the deployment server is running (Host 1).
- Ensure that NSH is installed (Host 1).
- Ensure that BMA is installed on the same computer as NSH (Host 1).
- Ensure that the dispatcher service is running on the NSH/BMA computer (Host 1).
- Ensure that the NSH RSCD agent is installed on the target computer (Host 2).
- Ensure that WebSphere 7.0 is running on the target computer (Host 2).
To create a WebSphere deployment with BMC Middleware Automation
- Define an NSH dispatcher agent for communication between the deployment console and the target computer.
- For the host name, enter the WebSphere or WebLogic host.
- For the agent, select the NSH agent from the list.
- For Agent Server, enter the NSH/BMA host name.
- For details, see Managing-servers.
- Construct a deployment process that uses the WebSphere action library Bma@websphere_jdbc_install.
For details, see Creating-and-managing-processes-and-content-process-sets and WebSphere-6-7-and-8-action-pack. - Define a package to deploy the process that you just created.
- Define the channel template, the WebSphere 7.0 environment, and other properties.
- In the channel definition, define the server profile properties and token properties for JDBC Name and Data Provider Name.
- Deploy the application:
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*