The configuration utility, ManagementAgentConfig, explicitly configures a management agent instance.Before using ManagementAgentConfig, you must first start the instance of Policy Manager central services to which the management agent will connect. The configuration utility validates its arguments by contacting central services; if central services are unavailable, the configuration utility reports an error.Repeat this task to configure each management agent on the respective WebSphere host computer.
Before associating a Federated profile, it is important to ensure that the Federated profile is completely synchronized with the Deployment Manager.
4. Run the ManagementAgentConfig utility.Supply the required information at each prompt. For a complete description each parameter, see ManagementAgentConfig on page 45.
Make sure the wasserviceagent.properties file has correct entries as per your environment settings. The log4j.properties file allows you to set customized logging.For example, the WAS Service Probe log gets generated at the location <IBM WAS home>\profiles\<profile name> with name was_service_probe.log.You can change this location by setting appropriate value for log4j.appender.service_probe_file.File property.
5. Verify that the new instance exists. The new instance is a directory named TIBCO_HOME/amma-was/instances/appsvr_profile_name/cells/cell_name/nodes/node_name/servers/server_name/pluginagent.properties (where appsvr_profile_name is the name of the corresponding WebSphere application server, which you supply in step 4).
Copyright © TIBCO Software Inc. All Rights Reserved.