Before installing CMS, verify that all of the requirements have been met. Because CMS is a separate product with its own installation CD or download, it is not installed as part of Operations Center server. For more information about installing Operations Center, see the Operations Center 5.6 Server Installation Guide.
During installation, various configuration values must be set for CMS. After installation, you must start the CMS service.
Do the following in order:
Because CMS must communicate with the Operations Center server, we recommend verifying Operations Center server configuration settings before you start to install. It is also important to verify and update (if necessary)values, which can cause memory errors if not set properly.
To verify and update Operations Center Configuration Settings:
Open the Operations Center Configuration Manager, and select.
To avoid memory issues, verify the JRE Flag is set as –XX:MaxPermSize=256m in the setting, as shown in this illustration:
Click thetab, and select .
Thetab in the Operations Center Configuration Manager allows you to view all settings in a single list, as shown in the following illustration:
Verify the following Operations Center server settings, which are important for open communication between Operations Center and CMS:
Hostname: The hostname for the Operations Center server.
Client/Server Communication Mode: The method of communication for the Operations Center server. Select betweenor .
Web Server Ports: The Web server HTTP and HTTPS ports for the Operations Center server.
Remote Services Port (RMI): The RMI server port for the Operations Center server.
Continue to Section 2.1, Installing CMS.
Usually, CMS is installed by using the Installation Wizard. It can also be installed using a console installation or an unattended (or silent) installation as detailed in the following note.
For more information about any of the installation methods, see the Operations Center 5.6 Server Installation Guide.
To install CMS:
(Recommended) Stop all programs before continuing especially those any programs that might interfere with the Operations Center installation.
If installing on Windows 2012 and using a DVD/CD, mounted ISO or mounted network install, do the following:
Locate the installation .exe file:
Right-click the file and select.
Open the Compatibility tab, mark the Windows 7.option and select
Do one of the following:
Windows: Do one of the following:
Insert the CMS CD into the CD drive of the server on which the software is to be installed.
The Installation Wizard should launch automatically. If not, enter install.bat at a command prompt to manually launch the Installation Wizard.
Access the downloaded CMS files, then enter install.bat at a command prompt to manually launch the Installation Wizard.
UNIX Do one of the following:
Set the variable path to where the Java executable is, mount the CD, then run install.sh from the root.
Set the variable path to where the Java executable is, change to the directory where the downloaded CMS files exist, then run install.sh from the root.
On thepage, review the contents of the license agreement and select the radio button if you agree with the terms.
On thepage, do the following:
To install the Java VM, do one of the following:
(Windows 32-bit) Select theradio button and select the desired Java VM from the list.
Selectto list additional installed VMs.
Selectto navigate to the location of the Java VM you want to use.
IMPORTANT:If installing on a Windows 32-bit platform, select a 32-bit JVM. If installing on a Windows 64-bit platform, select a 64-bit JVM. CMS cannot run if the wrong JVM is selected.
On thepage, do one of the following:
Clickto accept the default typical install set and install the most common application features.
Click .war files to your server.for the installer to save the
On thepage, click to accept the default installation directory or click to browse for a different location.
On thepage, do the following:
Specify the CMS communications mode by selecting one of the followingradio buttons:
http only to only use unsecure communications.
https only to only use secure communications.
both to allow both unsecure and secure communications.
Specify the http port CMS is to use for http communications in thefield.
Specify the http port CMS is to use for https communications in thefield.
Specify the communications mode that CMS uses to communicate with the Operations Center server by selecting one of the followingradio buttons:
http to use unsecure communication with Operations Center.
https to use secure communications with Operations Center.
Specify the host name for the Operations Center server in thefield.
Specify the Web port for the Operations Center server in thefield.
Select theafter install option to launch the Configuration Manager during installation.
On thepage, review all installation details and then click . During installation:
The status display is updated as CMS installs.
The Configuration Manager launches to configure settings for the installation if selected in Step 8.i. For details on these settings, see Section 2.1.3, Configuring CMS Settings.
After installation is complete, continue with Section 2.1.3, Configuring CMS Settings.
A console installation runs a text-based version of the Installation Wizard. Options are the same as the Windows-based version, except that you must provide responses.
To run a console installation, do one of the following:
Run install.bat ‑i console at a command prompt in Windows.
Run install.sh ‑i console at a command prompt in UNIX.
Reply to responses as they appear.
An unattended installation installs CMS without opening the installation wizard. The installation takes all default values and runs silently in the background.
To run an unattended installation, issue one of the following commands replacing installation_path with the complete path to the location where CMS is installed:
install.bat –i silent –D USER_INSTALL_DIR=installation_path
install.sh –i silent –D USER_INSTALL_DIR=installation_path
Configurations must be made for general CMS operation and communications with the Operations Center server. CMS configuration settings are defined using the CMS Configuration Manager during the installation process.
The CMS Configuration Manager and the Operations Center Configuration Manager are two different configuration managers.
After making changes in the Configuration Manager, it is necessary to restart CMS for any changes to take affect. Changing the settings through the Configuration Manager replaces all existing configuration files and any manual changes are lost.
For information about securing Operations Center and CMS across servers, see
Communications Security in the Operations Center 5.6 Security Management Guide.
To configure CMS settings:
To access the CMS Configuration Manager, do one of the following:
From themenu in Windows, select > > .
To configure Operations Center server Communication, do the following:
Click thetab, and select .
In order for CMS to communicate with the Operations Center server, some configuration settings must match the settings of the Operations Center server’s configuration.
Match the same settings as in the Operations Center Configuration Manager:
Configure the following CMS settings to be the same as for the Operations Center server:
Operations Center Host Name: The hostname for the Operations Center server.
Operations Center Communication Mode: The method of communication for the Operations Center server. Select betweenor .
Operations Center Web Server Port: The Web server port for the Operations Center server. If using unsecured communication, specify the Web Server Port number for HTTP from the Operations Center server. Or, if using Secured communication using SSL, specify the Web Server Port number for HTTPS from the Operations Center server.
Operations Center RMI Server Port: The RMI server port for the Operations Center server. The default RMI port is 1099. The value must match the RMI server port specified in the Operations Center configuration manager. If the port is changed in the CMS Configuration Manager, the port must be updated in the Operations Center Configuration Manager, and vice versa.
Clickto save the settings.
To configure CMS, do the following:
In thesection, click the tab.
Configure the following which configure how the user accesses CMS:
Configuration Management System Communication Mode: The method of communication for CMS. Select, , or .
Configuration Management System Web Server Port (HTTP): The port to access CMS if using an unsecured communication protocol.
Configuration Management System Web Server Port (HTTPS): The port to access CMS if using a secure communication protocol.
Configuration Management System Web Server Shutdown Port: The TCP/IP port number to which CMS listens for a shutdown command.
Configure the following to enable the Operations Center server to use standard metamodel validation rules to evaluate CI information:
NOC Server Field Validation: Set to Enabled to enable the Operations Center server to perform field validation when the CI Edit dialog is updated. Enabling this property, enables the following properties related to field validation.
Delay Validation During Create: Set toto turn off validation so that a list of property pages and fields can be returned for the CI prior to actual CI registration. During this process, an internal ORG element is used in Operations Center until CI fields are valid, at which point the actual element is created.
If set to, the element is created in Operations Center when the button is clicked. If any CI fields are invalid, then the CI is removed after confirmation when the property is set to . It is recommended to set the property to when using a complex custom matching script or script validation rules.
Validate On Page Load: Set toto perform server-side validation when attributes are first populated in the page of the CI Edit dialog.
Allow Validation Override: Set toto prompt the user if the CI has invalid fields. The user is given a choice to continue with CI registration or update, or to return and correct the information. If set to , the CI cannot be registered or updated until all validation rules are satisfied.
Show Validate Button: Set toto show a button in the CI Edit dialog.
Allow non-admin producers to delete CIs: Set toto allow producers who are not Operations Center administrators to delete CIs. When set to , all delete CI options are hidden for producers who are not also Operations Center administrators.
Specify Java configuration options:
Java Development Kit Directory: The location of the JDK used by CMS. Clickto select a new location.
Java Initial Memory Pool: (Windows only) Initial and minimum Java heap size in megabytes.
Java Max Memory Pool: (Windows only) Maximum Java heap size in megabytes.
Java Runtime Options: List of command line options in the form of -D or -X that are passed to the JDK. For Windows, separate entries with a semicolon. For UNIX, separate entries with a space.
For more information about JRE requirements, see
Requirements for the Dashboard and CMS in the Operations Center 5.6 Getting Started Guide.
Clickto save the settings.
Continue to Section 2.1.4, Starting CMS and Verifying the Installation.
The last step to installing CMS is to start the CMS service and log in to verify a successful connection.
For more information about starting and stopping CMS, see Section 2.3.1, Starting CMS.
To log in to CMS:
From your Web browser, access the CMS, then enter the following URL:
For example, if you have installed CMS on your current machine and set the HTTP port in the CMS Configuration Manager to 8888, then point your browser to:
Log in to the CMS.
Use the Operations Center default admin account credentials.
If authentication fails, do the following as necessary:
Confirm your administrator default account credentials.
Verify you are using the correct HTTP or HTTPS port.
Confirm that the RMI connections specified in the CMS Configuration Manager and the Operations Center Configuration Manager match.
If settings are changed in the Configuration Manager, restart the associated server.
Check the CMS.trc file for error messages.
Verify the correct JVM is installed for the platform you are running.