Connect Command Central to an Existing Product Installation
1. Go to the Software AG_directory\profiles directory.
If you do not see an SPM directory, install
Platform Manager in the product installation using the
Software AG Installer. You will find
Platform Manager at the top level of the installer product selection tree, or under Infrastructure, depending on your release. Note the
Platform Manager port numbers. The
Software AG Installer starts
Platform Manager automatically after installation.
If you do see an SPM directory, go to the configuration\com.softwareag.platform.config.propsloader directory and note the
Platform Manager port numbers on the files named com.softwareag.catalina.connector.http.pid-
port.properties and com.softwareag.catalina.connector.https.pid-
port.properties. If
Platform Manager is not running, go to the profiles/SPM/bin directory and start
Platform Manager by running the startup.{bat|sh} script.
2. Go to Environments > ALL > Installations, click 
, click Add Installation, and provide the requested values. Command Central automatically adds the installation to Environments > ALL. 3. When managing product instances and components of release 9.8 and later (or My webMethods Server 9.9 and later), Command Central uses trusted authentication, which is based on SAML 2.0. When managing instances and components of earlier releases, however, Command Central uses basic authentication. If the instance or component is using non-default credentials for basic authentication, Command Central must supply those non-default credentials to connect. In such cases, do the following:
a. On the Instances tab, click the instance or component for which to supply non-default credentials.
b. On the Overview tab, if the status shows that the instance or component is not running, start it. Click 
every few seconds to refresh the status. If the status shows Starting and then Online, Command Central is using the correct credentials to connect. If the status shows another status such as Unresponsive, click the Logs tab and open the logs; they will contain errors that say access was denied. In this case continue to the next step.
c. Click 
next to Authentication, then click Fixed User and supply the non-default user name and password. d. Click . After a few seconds, the status should show Online and KPIs should display. e. Restart the instance or component and click each status in turn to make sure they report correctly. Check the logs again to make sure there are no access denied errors.