Configuration : Navigating the Installation Directories

Navigating the Installation Directories
Table 3 presents the organization of the directories associated with Management Agent for WebSphere software.
 
TIBCO_HOME, the root for TIBCO software
Configuration utilities and configuration files
Contains wasserviceagent.properties
Unconfigured .ear file for the management service component, amma-was-config.xml and template file
uninstaller_archives
The configuration utility creates the instances directory, and a subdirectory for each configured WebSphere application server instance (identified by the profile name).
ManagementAgentConfig creates the file pluginagent.properties in the WebSphere application server profile directory.
Each subdirectory under instances contains configuration data for a specific WebSphere profile. Do not place other subdirectories or files in this tree.
The agent caches configuration data, managed endpoint data, policy data, logging configuration, log data, database configuration in this directory.
Configured .ear file for the management service component
pluginagent.properties
ibm_home, the root for IBM software
was_home, the root for WebSphere Application Server
ManagementAgentConfig modifies startServer by appending the three (tibco.agent.property.file,com.ibm.websphere.webservices.saaj.accessSOAPBody and com.amberpoint.util.Extension.dir) system properties in the java execution command. It saves the backup copy (with extension.bak) in the same directory before modification.
ManagementAgentConfig copies the TIBCO OSGI plug-ins required by the Management Agent for WebSphere into this directory.
WebSphere Users define application server profiles in this directory.
appsvr_profile_name
ManagementAgentConfig modifies setupCmdline, to set the TIBCO_AGENT_PROP_FILE environment variable. It saves the backup copy (with extension .bak) in the same directory before modification.
ManagementAgentConfig creates serverPaths.properties file under this directory.