Configuration : Record the Management Agent for WebSphere Configuration Plan

Record the Management Agent for WebSphere Configuration Plan
Use the forms in this section to record decisions you make as part of your installation plan. You will use this information in subsequent tasks.
The following parameter descriptions apply to the items in Table 5.
WebSphere Application Server Home
Record the full directory pathname of installation directory for WebSphere Application Server software; for example, /IBM/WebSphere/AppServer.
In the Management Agent for WebSphere documentation set, the variable was_home refers to this location.
Application Server Profile Name
You can configure at most one ActiveMatrix management agent for each WebSphere application server. For each management agent, record the name of corresponding application server in Table 5.
Admin Username and Password
If an application server is protected by an administrative username and password, you must supply the those values when configuring the corresponding management agent—but to protect the security of this information, do not record it here.
If the Application server is a Federated application server and the Deployment Manager associated with it is protected by an administrative username and password, then you must enter the credentials of the Deployment Manager when configuring the management agent.
If the ManagementAgentConfig utility fails due to invalid username and password, re-run the ManagementAgentConfig utility with valid credentials.
WebSphere Host Name
Each application server instance has a default host object, which consists of a hostname and port number. This object describes a locator for communication into services within the application server. In particular, Policy Manager components communicate with the management agent at this address.
Record the fully-qualified hostname from the WebSphere default host object. (You specified this hostname when you configured the WebSphere application server profile.)
Policy Manager Connects Using SSL
Policy Manager connects to management agents to deliver policy instructions and to query for log data. These requests use either HTTP protocols or HTTPS (SSL) protocols. Each management agent listens for one of these protocols, and ignores the other. To properly configure a management agent to receive these requests, you must first determine which protocol Policy Manager uses for these requests.
If the Policy Manager connects using SSL, then circle yes in Table 5.
Otherwise, circle no.
If you circle yes, then you must prepare a keystore for the management agent containing its identity, and a truststore for Policy Manager containing the agent’s public certificate.
For further information, see Chapter 5, SSL; especially Configuring SSL for Policy Manager Requests.
WAS Requires Client Authentication from Policy Manager
The WebSphere application server could be configured to require client authentication. If so, then when Policy Manager connects using SSL, it must supply its identity. (If Policy Manager does not connect using SSL, then this requirement is not relevant.)
If the application server is configured to require client authentication, circle yes in Table 5. Otherwise, circle no.
If you circle yes, then you must prepare a keystore for Policy Manager containing its identity, and a truststore for the management agent containing the Policy Manager’s public certificate.
For further information, see Chapter 5, SSL; especially Configuring SSL for Policy Manager Requests.
HTTP or HTTPS Transport Port
An application server accepts inbound requests on this port, and routes them to its deployed services.
Record one of two possible port numbers, depending on the value you specified for Policy Manager Connects Using SSL (see above):
If you circled yes, then record the HTTPS transport port.
If you circled no, then record the HTTP transport port.
 
(You specified these ports when you configured the WebSphere application server profile.)
SOAP Connector Port
An application server uses a connector port to route SOAP requests among its deployed services. In particular, the management agent connects to a JMX interface at this port to discover the deployed services.
Record the SOAP connection port. (You specified this port when you configured the WebSphere application server profile).
For a Standalone Application Server get this value from the following serverindex.xml file: <was_home>/profiles/profile_name/config/cells/cell_name/nodes/node_name.
The serverindex.xml file contains an element with a serverType attribute value as "APPLICATION_SERVER". This element consists of a child element with endPointName attribute value as "SOAP_CONNECTOR_ADDRESS". This element has a child element with one of the attribute as port. The value for this attribute must be used as the soap connector port.
For a Federated Application Server get this value from the following serverindex.xml file:
The serverindex.xml file contains an element with a serverType attribute value as "NODE_AGENT". This element consists of a child element with endPointName attribute value as "SOAP_CONNECTOR_ADDRESS". This element has a child element with one of the attribute as port. The value for this attribute must be used as the soap connector port.
Policy Manager Host
Each management agent connects to a Policy Manager instance running on a specific host computer.
Record the fully qualified hostname of the Policy Manager central services host computer. (You specified this hostname when you configured Policy Manager.)
Policy Manager HTTP Port
Policy Manager accepts inbound requests on its central services port.
Record the central services port that you specified when you configured Policy Manager.
Record Management Agent Instances
Record the information for configuring each management agent instance in Table 5. For further details about each item, see the descriptions above.
To facilitate later use of these values, Table 5 divides the information pertaining to each instance into three sections (highlighted by color) corresponding to the three input screens of the configuration utility’s graphic user interface.
 
1.
Policy Manager Connects
Using SSL       yes       no
WAS Requires Client Authentication
from Policy Manager       yes       no
2.
Policy Manager Connects
Using SSL       yes       no
WAS Requires Client Authentication
from Policy Manager       yes       no
3.
Policy Manager Connects
Using SSL       yes       no
WAS Requires Client Authentication
from Policy Manager       yes       no
4.
Policy Manager Connects
Using SSL       yes       no
WAS Requires Client Authentication
from Policy Manager       yes       no
5.
Policy Manager Connects
Using SSL       yes       no
WAS Requires Client Authentication
from Policy Manager       yes       no
6.
Policy Manager Connects
Using SSL       yes       no
WAS Requires Client Authentication
from Policy Manager       yes       no
7.
Policy Manager Connects
Using SSL       yes       no
WAS Requires Client Authentication
from Policy Manager       yes       no
8.
Policy Manager Connects
Using SSL       yes       no
WAS Requires Client Authentication
from Policy Manager       yes       no