2 Installing Configuration Management

This chapter describes how to install and start Oracle Communications Configuration Management.

Prerequisites

If you are installing Configuration Management and Oracle Communications IP Service Activator on the same server, you must install IP Service Activator first.

Before beginning the Configuration Management installation:

Verify that the database user was created.
Verify that the Oracle WebLogic domain was created.
Start the WebLogic server.
Start the managed server.

Installing WebLogic Server on a 64-bit Platform

To install WebLogic Server on a 64-bit platform:

Run the java -version command. This ensures that JAVA_HOME refers to a 64-bit JDK. For example, if installing in graphical mode using the package installer:
```
java -d64 -jar wlsversion_generic.jar
```
where version is the WebLogic version. For example:
```
java -d64 -jar wls1036_generic.jar
```
The new WebLogic Installer 64-bit starts.

Installing JDK

In the 32-bit WebLogic server installation, a JDK comes pre-packaged and can be re-used when running the scripts in the following directory: /opt/OracleCommunications/ConfigurationManagement/Scripts

The scripts are:

BulkArchiveDelete.sh
ConfigMgmtRoleAssign.sh
dbUpgrade.sh

However, the 64-bit installation assumes that you have a JDK or JRE already installed, and it does not package the script.

To make these scripts work, do the following:

Install a 64-bit JDK (if not already installed on the system).
Set JAVA_HOME to that value (export JAVA_HOME=/opt/jdk1.7.x).
Run the script.

Installing Configuration Management

If you are accessing the Oracle Solaris server remotely, set the display variable by running the following command:

export DISPLAY=IPaddress:port.0

where IPaddress is the IP address of the computer where the browser accesses Configuration Management and port is the port on which VNC server is running.

To install Configuration Management:

On the computer on which you want to install Configuration Management, download the Configuration Management 7.2 Solaris/Linux media pack from the Oracle software delivery Web site. For more information, see "Downloading a Media Pack".
Un-zip the media pack.

Note:
If you are installing Configuration Management on a different server from the one on which you installed IP Service Activator, install the required network processor cartridges from the IP Service Activator installer.
Log in as the admin user.
Go to the media pack un-zip location/cm/Disk1/install directory.
There are two installation methods:
- Interactive: For an interactive installation, continue with the next step of this procedure.
- Silent: For information about silent installations, including recording an installation session for later re-use in a silent installation, see "About Silent Installations".
Run the following command:

./runInstaller

The Welcome window opens.
Click Next.

The Select Installation Type window opens.
Select the installation type:
- All Components: Installs the Configuration Management server and all cartridges. Select this option if you want to install Configuration Management on the same server as the IP Service Activator Network Processor.
- Configuration Management Server: Installs only the Configuration Management server. Select this option if you want to install Configuration Management on a different server than the IP Service Activator Network Processor.
- Cartridges: Allows you to select the cartridges that you want to install.
- Custom: Allows you to select the components that you want to install.
Click Next.

If you selected All Components or Configuration Management Server, the Specify Home Details window opens.

If you selected the Cartridges or Custom installation types, the Available Product Components window opens.
Select the components that you want to install.
Click Next.

The Specify Home Details window opens.
Enter the location where you want to install Configuration Management.
Click Next.

A WebLogic window opens.
Enter the path to the WebLogic server domain.

For example, /opt/Oracle/Middleware/user_projects/CMDomain.
Verify the components to be installed and click Install.

The Install window opens.

After the installation completes, the End of Installation window opens.
Click Exit.

The Exit dialog box appears.
Click No.

The End of Installation window opens.

Note:
You can now click Yes to start the Configuration GUI, or, if you have already configured Configuration Management in the Configuration GUI, click No to go back to the command prompt.
You must enter the correct values in the Configuration GUI, in the Configuration Management tab. You must edit User ID and Password.

About Silent Installations

Oracle Universal Installer supports silent installations by using a response file.

A silent installation does not use the Installer GUI and does not display the typical dialog boxes.

Note:

You can record installation details into a response file for use in a future silent installation by running the runInstaller -record -destinationFile path command.

Complete details about silent installations, the contents of response files, and customizing and creating new response files are available in the Oracle Universal Installer documentation on the Oracle Technology Network Web site:

http://download.oracle.com/docs/cd/B28359_01/em.111/b31207/toc.htm

Note:

Some response parameters specific to Configuration Management are not mentioned in the Oracle Universal Installer documentation.

The response directory contains the following response template files for the corresponding installation type:

All Components: oracle.communications.cm.AllComponents.rsp
Cartridges: oracle.communications.cm.Cartridges.rsp
Custom: oracle.communications.cm.Custom.rsp
Configuration Management Server: oracle.communications.cm.Server.rsp

To run the Configuration Management installer in silent mode for a Solaris or Linux installation:

Locate the response template file in media pack un-zip location/cm/Disk1/stage/Response.

Open the oracle.communications.cm.Custom.rsp file and, in the DEPENDENCY_LIST section, remove the components that you do not want to install.
- oracle.communications.ipsa.jre1_7, 1.7.x: Java Runtime Environment 1.7.x
- oracle.communications.ipsa.tools.configtool, 7.2.x.x.x: Configuration GUI 7.2.x.x.x
- oracle.communications.cm.server, 7.2.x.x.x: Configuration Management Server 7.2.x.x.x
- oracle.communications.cm.cartridges, 7.2.x.x.x: Cartridges 7.2.x.x.x
- oracle.communications.cm.tools, 7.2.x.x.x: Tools 7.2.x.x.x
- oracle.communications.cm.tools.syslog, 7.2.x.x.x: Configuration Scripts for Syslog 7.2.x.x.x
- oracle.communications.cm.cartridges.cisco.ios, 7.2.x.x.x: Cisco IOS 7.2.x.x.x
- oracle.communications.cm.cartridges.cisco.iosxr, 7.2.x.x.x: Cisco IOSXR 7.2.x.x.x
- oracle.communications.cm.cartridges.juniper.junos, 7.2.x.x.x: Juniper JUNOS 7.2.x.x.x
- oracle.communications.cm.cartridges.huawei.vrp, 7.2.x.x.x: Huawei VRP 7.2.x.x.x
  
  Note:
  If you do not remove any of the components from the DEPENDENCY_LIST section, the Custom installation installs all the components.
Open the response file and modify the following installation parameters if they are different from the default parameters:
- ORACLE_HOME="/opt/OracleCommunications/cm_install"
- ORACLE_HOME_NAME="cm_install"
- DOMAIN_HOME="/opt/Oracle/Middleware/user_projects/domains/CMDomain"
Save and close the file.
Log on to the server as the admin user.
Go to the cm/Disk1/install directory and run the following command:
```
./runInstaller -silent -responseFile response_file_path
```
where response_file_path is the full path to the response file, including the file name.
After the installation is complete, check the log files.

Setting Up TFTP or FTP Services

Set up TFTP or FTP services on your Linux or UNIX server. Whether you choose to set up TFTP or FTP depends on the cartridge that you are using.

Note:

Oracle recommends that you set up the TFTP or FTP directory outside the IP Service Activator or Configuration Management directories.

To set up TFTP:

Install TFTP on your Linux or UNIX server.
Create a directory that has permissions 755 and is owned by the IP Service Activator user.

For example, /tftpboot
Configure TFTP to use the directory that you created as its home directory.
In the IP Service Activator Configuration GUI, click Network Processor Framework, and then click Common.
In Restore file location, enter the name of the directory that you created.

See IP Service Activator System Administrator's Guide for information about using the Configuration GUI.

To set up FTP:

Install FTP on your Linux or UNIX server.
Enable FTP for anonymous.
Create a directory that has permissions 755 and is owned by the IP Service Activator user.

For example, /ftpboot
Configure FTP to use the directory that you created in this procedure as its home directory.
In the IP Service Activator Configuration GUI, click Network Processor Framework, and then click Common.
In Restore file location, enter the name of the directory that you created.

Setting Up the Syslog Server

The syslog server, used for tracking changes, is automatically configured by the Configuration Management installer on systems where Configuration Management and the IP Service Activator Network Processor are collocated. By running a pre-defined script you can enable or disable the syslog server functionality on a Solaris or Linux server.

Note:

If you are installing Configuration Management on a different computer from that on which IP Service Activator is installed, you must run the installer again and choose the Cartridges installation type.

Enabling and Disabling Syslog Server on a Solaris Server

To enable syslog server on a Solaris server:

Switch users to root.
Go to the CM_Home/ConfigurationManagement/tools directory.
Run the following script:
```
./enableSyslog.sh
```

To disable syslog server on a Solaris server:

Go to the CM_Home/ConfigurationManagement/tools directory.
Run the following script:
```
./disableSyslog.sh
```

Enabling and Disabling Syslog Server on a Linux Server

The Oracle Linux syslog server does not support IPv6 functionality. You must install rsyslog.

To install rsyslog:

As the root user, run the following command:
```
yum install rsyslog
```
Open the /etc/sysconfig/rsyslog file in a text editor.

Add the following lines:

# Options to syslogd
# -m 0 disables 'MARK' messages.
# -rPortNumber Enables logging from remote machines. The listener will listen to
 the specified port.
# -x disables DNS lookups on messages recieved with -r
# See syslogd(8) for more details
SYSLOGD_OPTIONS="-c3"
# Options to klogd
# -2 prints all kernel oops messages twice; once for klogd to decode, and
#    once for processing with 'ksymoops'
# -x disables all klogd processing of oops messages entirely
# See klogd(8) for more details
KLOGD_OPTIONS="-x"

Save the file.
Run the following commands:
```
ps -ef | grep syslogd
kill -9 <pid>
```
Run the following command, which starts the syslog daemon:
```
/etc/init.d/rsyslog start
```
Run the following script:
```
./enableSyslog.sh
```

Post-Installation Tasks

Perform the following tasks after you install Configuration Management.

Verifying the Installation

You can use the Configuration GUI to make configuration changes. You need to enter or verify the parameters of the Configuration Management Server and Configuration Management Collector. See IP Service Activator System Administrator's Guide for information about using the Configuration GUI.

In the Configuration GUI, specify the path of the syslog.log file of the CMCollector component as CM_Home/ConfigurationManagement/logs/syslog.log

If the syslog.log file is deleted manually when the CMCollector is functioning, CMCollector tries to read that file from the specified location. If the syslog.log file is not present, CMCollector takes fifty percent of the central processing unit (CPU) time to read that file. Polling for this file does not consume CPU time continuously.

Starting the Configuration Management GUI

To start the Configuration Management GUI:

Open a browser and enter the following address:
```
IPaddress:ManagedServerWithCMPort/ConfigMgmt
```
where IPaddress is the IP address of the Configuration Management installation.

The Configuration Management login screen appears.
Log in as a valid user. You can obtain login credentials from your IP Service Activator installation.
You can now create and schedule archives, as well as restore archived configurations. See Configuration Management online Help for instructions.

Exiting the Configuration Management GUI

To exit the Configuration Management GUI:

Click the Logout link in the upper right-hand corner.

The Configuration Management login screen appears.

Uninstalling Configuration Management

This section describes how to uninstall Configuration Management.

Note:

Perform the following procedure on every server where Configuration Management (engine and components) is installed.

To uninstall Configuration Management:

In the Configuration Management GUI, click the Configuration Management tab.
Click Undeploy.

This removes all WebLogic configuration and stops the application.

Note:
Undeploying does not remove the database information or schema from the Oracle database.
Go to the media pack un-zip location/cm/Disk1/install directory and run the following command:
```
./runInstaller
```
The installer starts and the Welcome window opens.
Click Deinstall Products.

The Inventory window opens.
Select the items that you want to uninstall and click Remove.

The Confirmation window opens.
Click Yes.

Note:
You can click No to go back and change the uninstall options.

The Remove window opens with a progress bar and uninstalls the selected components.
Click Close.
Click Cancel.

The Exit window opens.
Click Yes.

The uninstallation is complete.

Upgrading Configuration Management 5.2.4 to Configuration Management 7.0.0

To upgrade Configuration Management 5.2.4 to Configuration Management 7.0.0:

Upgrade IP Service Activator from 5.2.4 to 7.0.0.

Do not run the dbUpgrade and npUpgrade script when asked in the IP Service Activator installation instructions. You will run the dbUpgrade and npUpgrade scripts after Configuration Management 7.0.0 is installed.

For more information about installing IP Service Activator, see IP Service Activator Installation Guide.
Stop the following Configuration Management tools, which are running as UNIX processes:
- syslog daemon
- TFTP server
- FTP server
Uninstall Configuration Management 5.2.4 by running the following command:
```
./runInstaller
```
Wait until the uninstallation process is completed.
Stop the WebLogic server.
Delete the existing WebLogic domain (WebLogic_Home/user_projects/domains/domain_name).

where WebLogic_Home is the location of the WebLogic Server instance and domain_name is the path to the WebLogic created domain.
(Optional) Remove the old WebLogic server (WebLogic 92 mp1 or mp3).
Install WebLogic.
Create a new WebLogic server domain by using the WebLogic domain creation tool (WebLogic_Home/wlserver_10.3/common/bin/config.sh script).
Start the newly created WebLogic domain by running the following script:
```
startWeblogic.sh
```
Run the Configuration Management installer:
```
./runInstaller
```
Run the Configuration GUI and enter Configuration Management parameters, for example, IP Service Activator user id and password.
Commit the changes in the Configuration GUI.
Run the IP Service Activator dbUpgrade and npUpgrade scripts.

For more information about running the scripts, see IP Service Activator Installation Guide.

Note:
npUpgrade might report a device audit failure, which indicates a MISSING logging host command for the ciscoSyslog cartridge. Expect this if the source and target Configuration Management software are installed on different servers (such as when upgrading and migrating to a different platform at the same time). In this case, you must re-issue the modified command to the device.
Run the following script, which upgrades the database:
```
CM_Home/ConfigurationManagement/Scripts/dbUpgrade.sh -dbUser userid -dbPass pwd -dbHost db_Ipaddr
```
where userid is the database user ID, pwd is the database password, and db_Ipaddr is the IP address of the database.
Stop and start the WebLogic server.

Upgrading Configuration Management 7.0.0 to Configuration Management 7.2.0

To upgrade Configuration Management 7.0.0 to Configuration Management 7.2.0:

Upgrade IP Service Activator from 7.0.0 to 7.2.0.

Do not run the dbUpgrade and npUpgrade script when asked in the IP Service Activator installation instructions. You will run the dbUpgrade and npUpgrade scripts after Configuration Management 7.2.0 is installed.

For more information about installing IP Service Activator, see IP Service Activator Installation Guide.
Stop the following Configuration Management tools, which are running as UNIX processes:
- syslog daemon
- TFTP server
- FTP server
Uninstall Configuration Management 7.0.0 by running the following command:
```
./runInstaller
```
Wait until the uninstallation process is completed.
Stop the WebLogic server.
Delete the existing WebLogic domain: delete the directory (WebLogic_Home/user_projects/domains/domain_name).
(Optional) Remove the old WebLogic server (WebLogic 92 mp1 or mp3).
Install WebLogic 10.3.6.

For information, see "Prerequisites".
Create a new WebLogic server domain by using the WebLogic domain creation tool (WebLogic_Home/wlserver_10.3/common/bin/config.sh script).
Start the newly created WebLogic domain by running the following script.
```
.startWeblogic.sh
```
Run the Configuration Management installer:
```
./runInstaller
```
Run the configuration GUI and enter the Configuration Management parameters, for example, IP Service Activator user id and password.
Commit the changes in the Configuration GUI.
Run the IP Service Activator dbUpgrade and npUpgrade scripts.

For more information about running the scripts, see IP Service Activator Installation Guide.

Note:
npUpgrade might report a device audit failure, which indicates a MISSING logging host command for the ciscoSyslog cartridge. Expect this if the source and target Configuration Management software are installed on different servers (such as when upgrading and migrating to a different platform at the same time). In this case, you must re-issue the modified command to the device.
Run the following script, which upgrades the database:
```
CM_Home/ConfigurationManagement/Scripts/dbUpgrade.sh -dbUser userid -dbPass pwd -dbHost db_Ipaddr
```
where userid is the database user ID, pwd is the database password, and db_Ipaddr is the IP address of the database.
Stop and start the WebLogic server.

Moving Configuration Management

This section describes how to move a Configuration Management installation from one server to another. The source and target servers can be on the same or different platforms: Solaris (64-bit), or Linux (64-bit).

To move Configuration Management:

Install the target version of Configuration Management (and all necessary components) on a Solaris or Linux server using the Configuration Management Installer (Solaris or Linux version). For more information about installing Configuration Management, see "Installing Configuration Management".

Note:
Do not run the Configuration GUI tool when prompted by the installer. You must restore the Config directory to the new installation directory before running the tool.
Copy the CM_Home/ConfigurationManagement/Config directory from the source server to the new CM_Home/ConfigurationManagement directory on the target server.
Manually run the Configuration GUI tool to configure the system and commit changes to the host. Update the CORBA parameters if the target server IP address has changed. CM_Home/ServiceActivator/bin/configGUI.sh.