Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

ApplicationMiddleware - addWebsphereApplicationServer


ApplicationMiddleware - addWebsphereApplicationServer

Description :

This command creates a WebSphere AMO representing a WebSphere 6.0/6.1/7.0 DMGR target and enrolls it in the system.

About the profileInstance argugment:

The Application Release Automation installation process creates the ARA_WAS_PROPERTIES class for use with WebSphere servers.

Before you run this command, you need to create one instance of the ARA_WAS_PROPERTIES class for each WebSphere server you want to manage. Within each instance, you configure property values for the target application server and for the proxy server that communicates with it.

Use the profileInstance argument to specify the name of this instance.

Return type : String

Command Input :

Variable Name

Variable Type

Description

amoName

String

The name you want to use for the AMO that represents the target application server. This is the name that will appear in the BMC Server Automation system.

proxyHostName

String

Host name of the AMO proxy server.

profileInstance

String

Name of the ARA_WAS_PROPERTIES instance. See description above.

Example

The following example creates a Websphere AMO named 'testAMO' running on the proxy hosted on localhost and enrolls it in the system.

Script





blcli ApplicationMiddleware addWebsphereApplicationServer testAMO localhost WAS61-on-myServer



 

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

BMC Server Automation Command Line Interface 8.3