Utilities : ManagementAgentConfig

ManagementAgentConfig
Command Utility
Syntax
ManagementAgentConfig [-console]
Description
Creates and configures a management agent instance in a WebSphere application server.
Location
 
TIBCO_HOME/amma-was/<version_num>/bin/ManagementAgentConfig
Remarks
This utility creates one management agent instance each time it runs to successful completion. It associates that agent with a WebSphere application server, according to the parameters you specify.
For each new management agent instance, you must run this utility to create and configure it. Use values you recorded in Table 5, Management Agent for WebSphere Instances Plan.
This utility configures the management agent instance with the Policy Manager host and port. If the location of the central services changes, you must remove the agent instance (you may preserve the agentcache directory), and run this utility again to recreate the agent instance.
Log
This utility logs its activity to the file TIBCO_HOME/amma-was/<version_num>/logs/ManagementAgentConfig.log.
This utility deploys the file PolicyAgentManagementService-<appserver_profile_name> -<appserver_cellname>-<appserver_nodename>-<appserver_servername>.ear within the WebSphere application server profile. You must not modify any configuration parameters of this .ear file.
When this command line flag is absent, the utility executes in the GUI mode, prompting you to enter information in text fields within the pop-up windows.
When this command line flag is present, the utility executes in Console mode, prompting you to type information on separate lines of the console or alphanumeric interface. Console mode is suitable for configuring agents in situations that do not support GUI mode.
Procedure
1.
Refer to Table 5, Management Agent for WebSphere Instances Plan, where you recorded the values that you will use in this procedure.
2.
On the WebSphere application server host computer, locate the ManagementAgentConfig utility, and start it (either double-click its icon, or type its name at a command prompt).
Enter the parameter values required for configuration. (If you supply the -console flag, the prompts appear as text in the command I/O stream, rather than in windows.)
3.
Enter the parameter values from Table 5. Figure 9, Figure 10 and Figure 11 illustrate the user interface for entering these values.
Figure 9 ManagementAgentConfig: WebSphere Parameters
Figure 10 ManagementAgentConfig: Management Agent Parameters
Figure 11 ManagementAgentConfig: Policy Manager Parameters
 
Table 6 ManagementAgentConfig: Agent Instance Parameters
Supply the full directory pathname of installation directory for WebSphere Application Server software; for example, /IBM/WebSphere/AppServer.
First, collect WebSphere server names into the drop-down menu, by clicking the Get Servers button. Then select a server name from the menu; the menu contains only those server names for which agents have not yet been configured.
Note: If the application server is federated, then specify the deployment manager’s administrative username and password.
If you did not configure a username and password for the WebSphere application server, you may omit them here as well. (We recommend using administrative passwords to protect production environments.)
Supply the fully-qualified hostname of the WebSphere default host object. (You specified this hostname when you configured the WebSphere application server profile.)
Policy Manager Connects Using SSL
When enabled, the agent listens for Policy Manager connection requests using HTTPS (SSL) protocols (and ignores HTTP requests). When disabled, the agent listens for HTTP requests (and ignores HTTPS requests).
HTTP or HTTPS Transport Port
Supply the SOAP connection port. (You specified this port when you configured the WebSphere application server profile.)
Note that for a Federated Application Server, get this value from the 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.
The management agent connects to a JMX interface at this port to discover the deployed services within the application server.
Supply the fully qualified hostname of the Policy Manager central services host computer. (You specified this hostname when you configured Policy Manager.)
4.
Review the configuration values, as in Figure 12. Compare them against the plan you recorded in Table 5. Make sure they are correct. If you have made any last-minute changes, update your plan accordingly for future reference.
Figure 12 ManagementAgentConfig: Summary
5.
Finish the configuration by clicking the Next button until the utility finishes.
 
See Also
Record the Management Agent for WebSphere Configuration Plan
Record the Policy Manager Installation Planin TIBCO ActiveMatrix Policy Manager Installation
If the ManagementAgentConfig fails due to wrong or invalid inputs, re-run it with valid inputs to reconfigure the agent correctly.