Defining properties for deploying BMC Middleware Automation actions


To deploy BMC Middleware Automation actions through BMC Release Lifecycle Management suite products, you must define the following Server Profile properties in either the channels or channel templates in the BMC VaraLogix Q Deployment Automation interface:

  • adminHost: Name or IP address of the host BMC Middleware Automation target (such as WebSphere, WebLogic, or any other application server)
  • adminPort: Server port number
  • adminUser: Administrator user name for logging on to the server
  • adminPassword: Password for the specific admin user (you can encode the password in BMC VaraLogix Q Deployment Automation when you create the property)
  • applicationServer: Type and version of application server (for example, websphere70 for WebSphere Application Server 7)
  • useSecureConnection: Whether to use a secure connection for the server; a value of either true or false
  • useRetrieveSigners: Whether to base the secure connection on the default certificate from any WebSphere server (version 6.1 or higher) and use the default trust store provided by BMC Middleware Automation; the value is either true or false
  • InstallNode: WebSphere nodes on which to install configurations associated with this Server Profile. The format is InstallNode|nodename= with nothing after the = sign. You can have multiple entries.
  • BMA_MODE: Value is either install or preview.
  • BMA_HOME: BMC Middleware Automation installation directory location.
  • TokenName: Token name of the BMC Middleware Automation configurations. The value is the token value for the token name. You can have multiple entries of token name/value pairs.

For more information, see Properties for Server Profile creation through the CLI.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC VaraLogix Q Deployment Automation 4.3