IBM Intelligent Operations Center

Version 5 Release 1

Installing the IBM Intelligent Operations

Center multi-server platform and
application

IBM
IBM Intelligent Operations Center
Version 5 Release 1

Installing the IBM Intelligent Operations

Center multi-server platform and
application

IBM
 Note
Before using this information and the product it supports, read the information in Notices on page 19.

This edition applies to IBM Intelligent Operations Center version 5, release 1, modification 0. This edition applies to
all subsequent releases and modifications until otherwise indicated in new editions.
Copyright IBM Corporation 2011, 2015.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Installing the multi-server platform and Adding the application server certificate. .. 10
application . . . . . . . . . . . .. 1 Adding the analytics server certificate . .. 10
Preparing for installation . . . . . . . . .. 1 Generating the plug-ins . . . . . . .. 11
Installation updates . . . . . . . . . .. 1 Retrieving the plug-ins . . . . . . .. 12
Prerequisites . . . . . . . . . . . .. 1 Merging and updating the plug-in content .. 12
Preparing the servers . . . . . . . . .. 1 Activating the plug-in . . . . . . . .. 16
Security and data privacy . . . . . . . .. 4 Restarting the HTTP server . . . . . .. 16
Deploying multiple servers . . . . . . . .. 4 Installation log files. . . . . . . . . . .. 17
Extracting the installation media and scripts . .. 5
Installing the servers. . . . . . . . . .. 7 Notices . . . . . . . . . . . . .. 19
Adding the web server certificate to the keystores 8
Configuring the HTTP plug-in . . . . . .. 9 Trademarks. . . . . . . . . . . .. 23
Extracting the application server certificate .. 9
Extracting the analytics server certificate . .. 9

Copyright IBM Corp. 2011, 2015 iii

iv IBM Intelligent Operations Center: Installing the IBM Intelligent Operations Center multi-server platform and application
Installing the multi-server platform and application
A multi-server deployment provides extra capacity to maintain performance under peak loads when
IBM Intelligent Operations Center is integrated with intensive data and analytic applications.

Preparing for installation

Prepare the servers and review the prerequisites before you install IBM Intelligent Operations Center.

Installation updates
Before you start installing IBM Intelligent Operations Center, review the latest installation updates to
ensure that you have the most recent version of the installer.

To review the latest installation updates, see the technote at IBM Intelligent Operations Center V5.1
installation updates.

Prerequisites
Review the hardware and software requirements for installing IBM Intelligent Operations Center.

Detailed system requirements

For detailed system requirements, see Detailed system requirements for IBM Intelligent Operations
Center.

Preparing the servers

Before you install IBM Intelligent Operations Center, prepare the servers.

About this task

Install the following Red Hat Package Manager (RPM) files that are required by the IBM Intelligent
Operations Center installation:
v audit-libs.i686
v audit-libs.x86_64
v compat-libstdc++*i686
v dos2unix.x86_64
v gettext.x86_64
v glibc.i686
v glibc.x86_64
v ksh.x86_64
v libaio.i686
v libaio.x86_64
v libgcc.i686
v libgcc.x86_64
v libstdc++.i686
v nss-softokn-freebl.i686
v nss-softokn-freebl.x86_64
v ntp.x86_64

Copyright IBM Corp. 2011, 2015 1

v openssh-clients.x86_64 pam.i686
v pam-devel.i686
v pam_passwdqc.x86_64
v tcsh.x86_64 unzip.x86_64
v xorg-x11-xauth.x86_64
v zlib.i686 zlib.x86_64
v gtk2.i686 gtk2.x86_64
v gtk2-engines.i686
v gtk2-engines.x86_64 libXtst.i686
v libXtst.x86_64
v nfs-utils

Note: The nfs-utils RPM file is required only if you are using NFS to mount the installation media.

Procedure

Do the following steps on each of the four servers, unless indicated otherwise.
v Data server
v Analytics server
v Application server
v Web server
1. Open a terminal window, and log on as a root user.
2. Define a fully qualified name and short host name either by using a DNS server, or by creating a
definition in the /etc/hosts file.

Note: Ensure that the database server host name is not the same as either of the following database
names:
v IOCDB
v IOCDATA
3. Ensure that the HOSTNAME value that is defined in the /etc/sysconfig/network file is set to the short
host name, and that it is not set to the fully qualified host name. For example, set HOSTNAME=xyz
instead of HOSTNAME=xyz.yourco.com.
4. Verify that the host name, fully qualified host name, and domain name are configured correctly on
each server:
a. Enter the following command: hostname -s. The verification is successful if the command returns
the defined short host name for the server.
b. Enter the following command: hostname -f. The verification is successful if the command returns
the fully qualified domain and host name for the server.
c. Enter the following command: hostname -d. The verification is successful if the command returns
the domain name of the server.
d. Choose the appropriate option:
v In an IPV6 environment, enter the following command: ping6 server_short_host_name.
v In all other environments, enter the following command: ping server_short_host_name.
The verification is successful if the command returns a result that indicates that the server is
accessible.
e. Choose the appropriate option:
v In an IPV6 environment, enter the following command: ping6
server_fully_qualified_host_name.

2 IBM Intelligent Operations Center: Installing the IBM Intelligent Operations Center multi-server platform and application
 v In all other environments, enter the following command: ping
server_fully_qualified_host_name.
The verification is successful if the command returns a result that indicates that the server is
accessible.
5. To enable local loopback addressing for each server, ensure that the first line in the /etc/hosts file is
edited with the following content:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4

Note: This is the line that is typically installed by default on Red Hat.
a. For IP version 6, ensure that the following line appears in the /etc/hosts file and ensure that the
line is not commented out.
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
6. To verify local loopback addressing, choose the appropriate option:
v In an IPV6 environment, enter the following commands:
a. Enter the following command: ping6 -n localhost6. The verification is successful if the
command returns the address ::1.
b. Enter the following command: ping6 -n localhost6.localdomain6. The verification is
successful if the command returns the address ::1.
v In all other environments, enter the following commands:
a. Enter the following command: ping -n localhost. The verification is successful if the
command returns the address 127.0.0.1.
b. Enter the following command: ping -n localhost.localdomain. The verification is successful if
the command returns the address 127.0.0.1.
7. In the /etc/selinux/config file, configure the SELinux setting to either permissive or disabled. For
example, to configure the SELinux setting to permissive, in the /etc/selinux/config file, edit the
SELinux setting as shown in the following example and then restart the server:
SELINUX=permissive

Note: The SELinux setting must not be enabled.

8. Reboot the operating system using the following command to make the SELinux changes effective:
reboot
9. To disable the server firewalls, enter the following commands:
service iptables save
service iptables stop
chkconfig --level 123456 iptables off
10. To install the prerequisite RPM files, enter the following command:
yum install -y audit-libs.i686 audit-libs.x86_64 compat-libstdc++*i686
compat-libstdc++_*x86_64 dos2unix.x86_64 gettext.x86_64
glibc.i686 glibc.x86_64 ksh.x86_64 libaio.i686 libaio.x86_64
libgcc.i686 libgcc.x86_64 libstdc++.i686 nss-softokn-freebl.i686
nss-softokn-freebl.x86_64 ntp.x86_64 openssh-clients.x86_64
pam.i686 pam-devel.i686 pam_passwdqc.x86_64 tcsh.x86_64
unzip.x86_64 xorg-x11-xauth.x86_64 zlib.i686 zlib.x86_64
gtk2.i686 gtk2.x86_64 gtk2-engines.i686 gtk2-engines.x86_64
libXtst.i686 libXtst.x86_64 nfs-utils
11. Install the Red Hat Enterprise Linux packages for the X Window System on the analytics,
application, and web servers.
X Windows is not required for the initial installation of IBM Intelligent Operations Center, but it is
required if you want to update the underlying IBM products by using IBM Installation Manager. For
example, you can update WebSphere Application Server Liberty Profile and IBM HTTP Server. You
can install either the GNU Object Model Environment (GNOME) desktop or the K Desktop
Environment (KDE) desktop to use with IBM Installation Manager.

Installing the multi-server platform and application 3

 Note: DB2 does not use the IBM Installation Manager, so the data server does not require the
graphical user interface (GUI) that is provided by either the GNOME desktop or the KDE desktop.
a. Choose one of the following options:
v To install the GNOME desktop, enter the following command:
yum -y groupinstall "X Window System" Desktop
v To install the KDE desktop, enter the following command:
yum -y groupinstall "X Window System" "KDE Desktop"
b. Enter the following command: yum -y update
c. To start the desktop, enter the following command: init 5
d. To configure the GUI desktop to be the default desktop, edit the /etc/inittab file and change the
value of the initdefault property from 3 to 5. The following example shows the updated line:
id:5:initdefault:
e. Save the changes, and then restart the server.
12. To use the Chinese, Japanese, or Korean language version of the graphical installer, enter the
appropriate commands as shown in the following example:
yum install -y "@Chinese Support"
yum install -y "@Japanese Support"
yum install -y "@Korean Support"

Security and data privacy

Review the security and data privacy considerations.

Security

By default, IBM Intelligent Operations Center has some installation and configuration features that
enhance the security and privacy of the solution. For example, you should not use well-known product
user IDs, such as db2inst1.

User data privacy

By default, the IBM Intelligent Operations Center platform installation process enables the DB2
Encryption Offering. Application databases that contain sensitive customer data can use local DB2
encryption facilities to protect sensitive information while the databases are not being accessed.

Encryption of customer data in DB2 does not provide protection against all potential data breach attacks.
IBM recommends that installers also install and use complementary tools and techniques:
v Full disk encryption
v Code scanning tools
v Limited access to sensitive data, by granting access to as few users as possible, explicitly granting
privileges, and not granting privileges to PUBLIC.

Deploying multiple servers

Deploy IBM Intelligent Operations Center onto the four servers in the production environment.

The following list indicates the components that are installed on each server in a multi-server
deployment:
Data server
v DB2 Workgroup Server Edition with Enterprise Framework and Storage Optimization offerings
Analytics server
v IBM Installation Manager

4 IBM Intelligent Operations Center: Installing the IBM Intelligent Operations Center multi-server platform and application
 v IBM Java Development Kit
v WebSphere Application Server Liberty Profile server 2
IBM Intelligent Operations Center ASK service
v IBM SPSS Modeler Professional
Modeler server
Premium server
Data access
Basic batch
v Components from IBM ILOG CPLEX Optimization Studio
Application server
v IBM Installation Manager
v IBM Java Runtime Environment
v WebSphere Application Server Liberty Profile server 1
IBM Intelligent Operations Center EAR files
Web server
v IBM Installation Manager
v IBM HTTP Server
v WebSphere Application Server HTTP plug-in
v WebSphere Application Server configuration tool

Extracting the installation media and scripts

Provide the installation media and scripts to each server that hosts an IBM Intelligent Operations Center
component.

Before you begin

Before you start installing IBM Intelligent Operations Center, review the latest installation updates to
ensure that you have the most recent version of the installer. See the technote at IBM Intelligent
Operations Center V5.1 installation updates.

The installation media is provided as four ISO image files. Copy the ISO image files to a temporary
location on the analytics server. Alternatively, copy the files to a Network File System (NFS) server that is
accessible from each of the servers that will host an IBM Intelligent Operations Center component.

About this task

Use the following procedure to extract the installation media and scripts that are contained in the four
ISO image files to an /installmedia directory on the analytics server. Alternatively, you can extract the
ISO images files to an NFS server.

After all of the ISO image files have been extracted, create an NFS export to share the /installmedia
directory with all the servers that host an IBM Intelligent Operations Center component.

Procedure
1. Enter the following commands in a terminal window as the root user to create directories either on
the analytics server, or on an NFS server:
mkdir /solution_iso_images
mkdir /solutionmedia
mkdir /installmedia
2. Copy the following ISO image files into the /solution_iso_images directory:

Installing the multi-server platform and application 5

 IBM_IOC_V5.1_MultiSer_1of4_Lin_ML.iso
IBM_IOC_V5.1_MultiSer_2of4_Lin_ML.iso
IBM_IOC_V5.1_MultiSer_3of4_Lin_ML.iso
IBM_IOC_V5.1_MultiSer_4of4_Lin_ML.iso
3. Enter the following commands to extract the contents of each of the four ISO image files to the
/installmedia directory.
cd /solution_iso_images
mount -o loop IBM_IOC_V5.1_MultiSer_1of4_Lin_ML.iso /solutionmedia
cp -r /solutionmedia/* /installmedia/
umount /solutionmedia
mount -o loop IBM_IOC_V5.1_MultiSer_2of4_Lin_ML.iso /solutionmedia
cp -r /solutionmedia/* /installmedia/
umount /solutionmedia
mount -o loop IBM_IOC_V5.1_MultiSer_3of4_Lin_ML.iso /solutionmedia
cp -r /solutionmedia/* /installmedia/
umount /solutionmedia
mount -o loop IBM_IOC_V5.1_MultiSer_4of4_Lin_ML.iso /solutionmedia
cp -r /solutionmedia/* /installmedia/
umount /solutionmedia
rmdir /solutionmedia
4. On the analytics server, or on the NFS server where you extracted the media, configure an NFS
export:
a. Create the /etc/exports file if it does not exist.
b. Edit the /etc/exports file, and add the following line:
/installmedia/ *(ro,sync)
c. Enter the following command to start rpcbind and the NFS server:
service rpcbind start; service nfs start
d. Enter the following command to check the NFS server status:
service nfs status
e. Enter the following command to verify that the mount is exported:
showmount -e localhost
5. On each of the servers that do not have the media extracted into /installmedia, create an NFS mount
to the /installmedia directory:
a. Enter the following command to start the NFS server:
service nfs start
b. Enter the following command to create the /installmedia directory:
mkdir /installmedia

Note: If the /installmedia directory exists, ensure that the directory is empty. The directory must
be empty for the mount command to work correctly.
c. Enter the following command to verify that the mount is available:
showmount -e analytics or NFS file server hostname

A list of available mount points are listed. If the /installmedia directory is correctly mounted, it is
displayed as an option. The following example shows the command and the resulting output:
#showmount -e ioc51anal
Export list for ioc51anal:
/installmedia *
d. Enter the following command to mount the /installmedia share locally on the server with an NFS
mount tool:
mount -t nfs ioc51ana:/installmedia /installmedia
e. Repeat steps 55a to 55d on each of the servers that does not have the media extracted to the
/installmedia directory.

6 IBM Intelligent Operations Center: Installing the IBM Intelligent Operations Center multi-server platform and application
6. On each of the servers, create an installation directory and copy the ioc51platform.tar.gz
compressed installation file to the installation directory:
a. Open a terminal window and log on as the root user.
b. Enter the following command to create the base IBM Intelligent Operations Center installation
directory:
mkdir -p /opt/IBM/
c. Enter the following command to copy the ioc51platform.tar.gz installation file from the
/installmedia directory to the base IBM Intelligent Operations Center installation directory:
cp /installmedia/ioc51platform.tar.gz /opt/IBM/

Installing the servers

Run the installation script to configure each server.

About this task

Configure the four servers in the following order:

1. Data server
2. Analytics server
3. Application server
4. Web server

Note: Wait for each installation script to complete before you start the installation steps on the next
server.

Procedure
1. On the server, open a terminal window and log on as a root user.
2. Enter the following command:
cd /opt/IBM
3. Enter the following command to extract the ioc51platform.tar.gz file to the /opt/IBM directory:
tar -xvzf ioc51platform.tar.gz
4. Enter the following command to go to the directory where the ioc.5_1.install.properties
installation properties file is located:
cd /opt/IBM/ioc51install/cfg
5. To retrieve the server's fully qualified host name value, enter the following command in the terminal
window on the server:
hostname -f
6. Locate the following values in the ioc.5_1.install.properties installation properties file:
ana.server.hostname = localhost
app.server.hostname = localhost
db.server.hostname = localhost
ihs.server.hostname = localhost
7. For the server that you are currently configuring, replace the server's localhost property value in
the installation properties file with the associated fully qualified host name value that you
determined for the server:
ana.server.hostname = ana.yourco.com
app.server.hostname = app.yourco.com
db.server.hostname = db.yourco.com
ihs.server.hostname = ihs.yourco.com

Installing the multi-server platform and application 7

 8. Optional: Edit the password property values in the installation properties file. Each password
property name has the suffix .pwd. The password for sample users is configured in the
ioc.sample.users.pwd property. Do not use the following special characters in password property
values:
v Exclamation point, !
v Opening parenthesis, (
v Closing parenthesis, )
9. To change directory to where the installation script is located, enter the following command:
cd ../bin
10. On the data server only, run the following license script, read the license agreement, and enter y or Y
to accept the agreement.
./ioc51.accept.license.sh
11. Enter the following command to run the installation script:
./ioc51.server.install.sh -p 4.<server_initials>

where <server_initials> is:

v dat for the data server.
v ana for the analytics server.
v app for the application server.
v web for the web server.

What to do next

Add the web server certificate to the WebSphere Application Server Liberty Profile keystores, and
configure the HTTP plug-in. See the next topics in this section.

A basic user registry is installed by default at /opt/IBM/WebSphere/wlp/usr/servers/iocsvr1/server.xml.

However, the basic user registry does not support password policies, password length, password
expiration dates, or user lockout. Configure the solution to work with a Lightweight Directory Access
Protocol (LDAP) user registry. For more information, see Configuring an LDAP user registry in the
product documentation.

For information about the sample users that are installed with the solution, and about how to change
user passwords, see the Securing the solution topic.

For information about how to log on to IBM Intelligent Operations Center, see Logging on in the product
documentation.

Adding the web server certificate to the keystores

You must add the web server certificate to the WebSphere Application Server Liberty Profile keystores as
part of the installation.

About this task

Complete the following instructions to generate the certificate and to add the web server certificate to the
WebSphere Application Server Liberty Profile keystores:

Procedure
1. Run the following command from a command prompt on the web server, where ${value} indicates the
appropriate value from your installation properties file at /ioc51install/cfg/
ioc.5_1.install.properties. The password for the /opt/IBM/HTTPServer/cert/key.kdb file is
specified in the ihs.keystore.pwd property in the installation properties file.

8 IBM Intelligent Operations Center: Installing the IBM Intelligent Operations Center multi-server platform and application
 ${ihs.install.dir}/bin/gskcapicmd -cert -extract -db /opt/IBM/HTTPServer/cert/key.kdb
-label IOC_Cert -target /tmp/IOC_Cert.arm -format ascii

For example:
/opt/IBM/HTTPServer/bin/gskcapicmd -cert -extract -db /opt/IBM/HTTPServer/cert/key.kdb
-label IOC_Cert -target /tmp/IOC_Cert.arm -format ascii
2. Copy the generated certificate from the web server to the /tmp directory on both the analytics and
application servers.
3. On the analytics server, open a command prompt and run the following command:
/opt/ibm/java-x86_64-80/jre/bin/keytool -import -trustcacerts -alias web_server_cert
-file /tmp/IOC_Cert.arm -keystore
/opt/IBM/WebSphere/wlp/usr/servers/iocsvr1/resources/security/key.jks
4. On the application server, open a command prompt and run the following command:
/opt/ibm/java-x86_64-80/jre/bin/keytool -import -trustcacerts -alias web_server_cert
-file /tmp/IOC_Cert.arm -keystore
/opt/IBM/WebSphere/wlp/usr/servers/iocsvr1/resources/security/key.jks
5. Stop and start the both the application server and the analytic server.

Configuring the HTTP plug-in

After IBM Intelligent Operations Center is installed, the HTTP plug-in must be configured on the web
server with information obtained from the application and analytics servers.

Extracting the application server certificate

Extract the IBM Intelligent Operations Center application server Liberty profile root certificate from the
application server and copy it to the web server.

Procedure
1. Log on to the application server as the iocadmin user.
2. Extract the root certificate by entering the following command, where value indicates the appropriate
value from your installation properties file.
/opt/ibm/java-x86_64-80/jre/bin/ikeycmd -cert -extract -label default
-db liberty.install.dir/usr/servers/iocsvr1/resources/security/key.jks
-pw liberty.instance.ssl.cert.pwd -type jks -target /tmp/app_cert.arm
-format ascii
For example:
/opt/ibm/java-x86_64-80/jre/bin/ikeycmd -cert -extract -label default
-db /opt/IBM/WebSphere/wlp/usr/servers/iocsvr1/resources/security/key.jks
-pw liberty.instance.ssl.cert.pwd -type jks -target /tmp/app_cert.arm
-format ascii

Note: Do not use the following special characters in the password (-pw) value: exclamation point (!),
open parenthesis ((), or closed parenthesis ()).
The certificate is copied to the /tmp/app_cert.arm file.
3. Copy the certificate to the web server by running the following command where ${value} indicates the
appropriate value from your installation properties file. You will be prompted for the ihsadmin user
password.
scp /tmp/app_cert.arm ihs.admin.user@ihs.server.hostname:/tmp
For example:
scp /tmp/app_cert.arm ihsadmin@ioc51web.yourco.com:/tmp

Extracting the analytics server certificate

Extract the IBM Intelligent Operations Center analytics server Liberty profile root certificate from the
analytics server and copy it to the web server.

Installing the multi-server platform and application 9

Procedure
1. Log on to the analytics server as the iocadmin user.
2. Extract the root certificate by running the following command where ${value} indicates the appropriate
value from your installation properties file.
/opt/ibm/java-x86_64-80/jre/bin/ikeycmd -cert -extract -label default
-db ${liberty.install.dir}/usr/servers/iocsvr1/resources/security/key.jks
-pw ${liberty.instance.ssl.cert.pwd} -type jks -target /tmp/ana_cert.arm
-format ascii
For example:
/opt/ibm/java-x86_64-80/jre/bin/ikeycmd -cert -extract -label default
-db /opt/IBM/WebSphere/wlp/usr/servers/iocsvr1/resources/security/key.jks
-pw ChangeM3N0w -type jks -target /tmp/ana_cert.arm
-format ascii

Note: Do not use the following special characters in the password (-pw) value: exclamation point (!),
open parenthesis ((), or closed parenthesis ()).
The certificate is copied to the /tmp/ana_cert.arm file.
3. Copy the certificate to the web server by running the following command where ${value} indicates the
appropriate value from your installation properties file. You will be prompted for the ihsadmin user
password.
scp /tmp/ana_cert.arm ${ihs.admin.user}@${ihs.server.hostname}:/tmp
For example:
scp /tmp/ana_cert.arm ihsadmin@ioc51web.yourco.com:/tmp

Adding the application server certificate

Add the IBM Intelligent Operations Center application server Liberty root certificate to the web server.

Procedure
1. Log on to the web server as the root user.
2. Add the certificate to the HTTP keystore by entering the following command, where $value indicates
the appropriate values from your installation properties file in installLocation/ioc51install/cfg/
ioc.5_1.install.properties.
$ihs.install.dir/java/jre/bin/ikeycmd -cert -add -label APP_SERVER
-db $plugin.install.dir/config/webserver1/plugin-key.kdb
-pw plugin.keystore.pwd -file /tmp/app_cert.arm -format ascii -trust enable
In the following example, the variables that are indicated by $value have been replaced with default
values from the installation properties file:
/opt/IBM/HTTPServer/java/jre/bin/ikeycmd -cert -add -label APP_SERVER
-db /opt/IBM/WebSphere/Plugins/config/webserver1/plugin-key.kdb
-pw WebAS -file /tmp/app_cert.arm -format ascii -trust enable

Adding the analytics server certificate

Add the IBM Intelligent Operations Center analytics server Liberty profile root certificate to the web
server.

Procedure
1. Log on to the web server as the root user or use the same window that you opened when adding the
application server certificate.
2. Add the certificate to the HTTP keystore by running the following command where value indicates the
appropriate value from your installation properties file.
ihs.install.dir/java/jre/bin/ikeycmd -cert -add -label ANA_SERVER
-db plugin.install.dir/config/webserver1/plugin-key.kdb
-pw plugin.keystore.password -file /tmp/ana_cert.arm -format ascii -trust enable
For example:

10 IBM Intelligent Operations Center: Installing the IBM Intelligent Operations Center multi-server platform and application
 /opt/IBM/HTTPServer/java/jre/bin/ikeycmd -cert -add -label ANA_SERVER
-db /opt/IBM/WebSphere/Plugins/config/webserver1/plugin-key.kdb
-pw plugin.keystore.password -file /tmp/ana_cert.arm -format ascii -trust enable

Generating the plug-ins

Generate a plugin-cfg.xml file on the Liberty server for the application and analytics servers.

Before you begin

The Liberty servers on the IBM Intelligent Operations Center application server and analytics server must
be started before doing these steps.

Note: If these steps are being done immediately after the installation of IBM Intelligent Operations
Center, the Liberty server should already be started.

To check the status of the Liberty server, run the following command as the iocadmin user on the
application server and on the analytics server:
${liberty.install.dir}/bin/server status iocsvr1

Run one of the following commands as the iocadmin user on the application server and analytics server
to start the Liberty server if it is not running:
${liberty.install.dir}/bin/server start iocsvr1

or
${liberty.install.dir}/bin/server start iocsvr1 --clean

${liberty.install.dir} is the property value for the Liberty installation directory in your installation
properties file.

About this task

These commands invoke a JMX MBean on the application and analytics servers to export the connection
and web resource definition information as an HTTP plug-in configuration file. This file will be retrieved
and merged in subsequent steps.

The MBean requires a secure HTTP connection. The Liberty system administrator (sysadmin) is used to
make the connection. If you changed the password for the sysadmin id, you will need to supply the new
password on the -w parameter.

Procedure
1. Log on to the web server as the root user.
2. Generate the application server plug-in by running the following command where ${value} indicates
the appropriate value from your installation properties file and <IOC_install_directory> is the location
where IBM Intelligent Operations Center was installed from.
<IOC_install_directory>/bin/genPlugin.sh -h ${app.server.hostname} -s iocsvr1
-w <password>
The parameter values are:
-h is the host name running the Liberty server
-s is the Liberty server name
-w is the Liberty server administrator password
For example:
/opt/IBM/ioc51install/bin/genPlugin.sh -h ioc51app.yourco.com -s iocsvr1 -w ChangeM3N0w!

Installing the multi-server platform and application 11

3. Generate the analytics server plug-in by running the following command where ${value} indicates the
appropriate value from your installation properties file and <IOC_install_directory> is the location
where IBM Intelligent Operations Center was installed from.
<IOC_install_directory>/bin/genPlugin.sh -h ${ana.server.hostname} -s iocsvr1
The parameter values are:
-h is the host name
-s is the Liberty server name
-w is the Liberty server administrator password
For example:
/opt/IBM/ioc51install/bin/genPlugin.sh -h ioc51anapp.yourco.com -s iocsvr1
If you run the genPlugin.sh command and get a 404 response when specifying the analytics server,
instead of the anticipated 200 response, restart the Liberty server on the analytics server and try again.

Retrieving the plug-ins

Get copies of the plug-ins created on the application and analytics servers.

About this task

While these steps are run as the root user, the download is done using the IBM Intelligent Operations
Center Liberty owner userid. This userid is specified by the ioc.user value in the installation properties
file. The default value is iocadmin.

When you run the commands you will be prompted for the password for the ioc.user user.

Procedure
1. Log on to the web server as the root user.
2. Download the IBM Intelligent Operations Center application server plug-in by running the following
command where ${value} indicates the appropriate value from your installation properties file and
<IOC_install_directory> is the location where IBM Intelligent Operations Center was installed from. For
<unique-file-name> specify a file name of your choice.
<IOC_install_directory>/bin/getPlugin.sh -h ${app.server.hostname}
-i ${liberty.install.dir}
-o <unique-file-name>
For example:
/opt/IBM/ioc51install/bin/getPlugin.sh -h ioc51app.ibm.com -o /tmp/app_plugin.xml
-i /opt/IBM/WebSphere/wlp
3. Download the IBM Intelligent Operations Center analytics server plug-in by running the following
command where ${value} indicates the appropriate value from your installation properties file and
<IOC_install_directory> is the location where IBM Intelligent Operations Center was installed from. For
<unique-file-name> specify a file name of your choice.
<IOC_install_directory>/bin/getPlugin.sh -h ${ana.server.hostname}
-i ${liberty.install.dir}
-o <unique-file-name>
For example:
/opt/IBM/ioc51install/bin/getPlugin.sh -h ioc51ana.ibm.com -o /tmp/ana_plugin.xml
-i /opt/IBM/WebSphere/wlp

Merging and updating the plug-in content

Merge the two plug-ins you retrieved from the IBM Intelligent Operations Center application and
analytics servers to create a single plug-in. After merging, make any updates required for your
installation.

12 IBM Intelligent Operations Center: Installing the IBM Intelligent Operations Center multi-server platform and application
About this task

Merging plug-in content is a manual process requiring care and analysis. There are multiple ways to do
this, but the following instructions provide guidance.

Procedure
1. On the web server create a backup copy of your ${plugin.install.dir}/config/webserver1/plugin-
cfg.xml file where ${plugin.install.dir} is the plugin.install.dir value from your installation
properties file.
2. The plug-ins retrieved from the application and analytics servers have elements with the same name.
Use the cvtPlugin.sh script to change one of the plug-in files so it has unique element names and
references. Merging plug-ins with elements with the same name will result in a non-functional
plug-in.
<IOC_install_directory> is the location where IBM Intelligent Operations Center was installed from.
<IOC_install_directory>/bin/cvtPlugin.sh -f <plugin-file>
-h <optional-host-id-text> -n <optional-node-id-text>
For example:
# the -n and -h values are the default values
/opt/ibm/ioc51install/bin/cvtPlugin.sh -f /tmp/ana_plugin.xml
-h ioc_host_ana -n ioc_node_ana

All occurrences of the following strings are replaced in the plug-in:

v The default_node_ string is replaced with the value specified by -n.
v The default_host_ string is replaced with the value specified by -h.
The plug-ins can now be merged without duplicate element names and values.
3. Open the plug-in copied from the application server (/tmp/app_plugin.xml) in an editor of your
choice and copy the following sections, in their entirety, from the analytics server plug-in
(/tmp/ana_plugin.xml) into the application server plug-in..
<ServerCluster>

<UriGroup>

<Route>
The three sections can be pasted into the consolidated plug-in prior to the </Config> tag.
4. Update the keyring and stashfile values so they are appropriate for a standalone HTTP server.
When the default plug-in for the Liberty instance is generated, the values for these properties are for a
local plug-in configuration. These values must be changed to refer to the valid location of your
plug-in keystore.
The certLabel property for each IBM Intelligent Operations Center <ServerCluster> element must
reference the certificate label created for the IBM HTTP Server keystore. For the analytics server
section, use ANA_SERVER. For the application server section, use APP_SERVER.
The following is an example section before being updated:
<ServerCluster ....>
<Server ....>
<Transport Hostname=... Port=9443 Protocol=https />
<Property Name=keyring Value=keyring.kdb/>
<Property Name=stashfile Value=keyring.sth/>
<Property name=certLabel Value=LibertyCert />
</Server>
</ServerCluster>
The following is an example section for the analytics server after changes have been made:
<ServerCluster ....>
<Server ....>
<Transport Hostname=... Port=9443 Protocol=https />

Installing the multi-server platform and application 13

 <Property Name=keyring
Value=/opt/IBM/WebSphere/Plugins/config/webserver1/plugin-key.kdb/>
<Property Name=stashfile
Value=/opt/IBM/WebSphere/Plugins/config/webserver1/plugin-key.sth/>
<Property Name=certLabel Value='ANA_SERVER' />
..
</Server>
</ServerCluster>
5. Update the Log value in the Config element so it is appropriate for standalone HTTP server. When the
default plug-in for the Liberty instance is generated, the plug-in specifies a default location for the
plug-in log file This value must be changed for the standalone HTTP server.
The value from the generated plug-in is:
<Config .....>
<Log Loglevel=Error Name=/opt/IBM/WebSphere/wlp/logs/iocsvr1/http_plugin.log/>
..
</Config>
The following shows the change required if IBM Intelligent Operations Center was installed using the
default installation parameters for the HTTP plug-in. If the HTTP plug-in parameters were changed,
update the Log value appropriately.
<Config .....>
<Log Loglevel=Error Name=/opt/IBM/WebSphere/Plugins/logs/webserver1/http_plugin.log/>
..
</Config>
6. Update the Property Name="PluginInstallRoot" value in the Config element to reference the plug-in
directory.
The following shows the change required if IBM Intelligent Operations Center was installed using the
default installation parameters for the HTTP plug-in. If the HTTP plug-in parameters were changed,
update the PluginInstallRoot value appropriately.
<Config .....>
<Property Name="PluginInstallRoot" Value="/opt/IBM/WebSphere/Plugins"/>
..
</Config>
7. In the <VirtualHostGroup> element define the following ports as <VirtualHost> entries unless they are
already defined. The default values are shown. The ${value} indicates the configuration parameter
from your installation properties file.
v ${ihs.http.port} (default value 80)
v ${ihs.https.port} (default value 443)
v ${liberty.http.port} (default value 9080)
v ${liberty.https.port} (default value 9443)
8. Remove the following content from both the application and analytic server <UriGroup> sections:
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/adminCenter/explore-1.0/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/adminCenter/*"/>
9. Save the changes to your consolidated plug-in file.

Example

The following shows an example consolidated plug-in with updated values and sections copied from the
analytics server plug-in into the application server plug-in in bold text.
<?xml version="1.0" encoding="UTF-8"?><!--HTTP server plugin config file for iocsvr1 generated on 2015.07.21 at 00:43:43 CDT-->
<Config ASDisableNagle="false" AcceptAllContent="false" AppServerPortPreference="HostHeader" ChunkedResponse="false"
FIPSEnable="false" IISDisableNagle="false" IISPluginPriority="High" IgnoreDNSFailures="false" RefreshInterval="60"
ResponseChunkSize="64" SSLConsolidate="false" TrustedProxyEnable="false" VHostMatchingCompat="false">
<Log LogLevel="Error" Name="/opt/IBM/WebSphere/Plugins/logs/webserver1/http_plugin.log"/>
<Property Name="ESIEnable" Value="true"/>
<Property Name="ESIMaxCacheSize" Value="1024"/>
<Property Name="ESIInvalidationMonitor" Value="false"/>
<Property Name="ESIEnableToPassCookies" Value="false"/>
<Property Name="PluginInstallRoot" Value="/opt/IBM/WebSphere/Plugins"/>
<!-- Configuration generated using httpEndpointRef=defaultHttpEndpoint-->

14 IBM Intelligent Operations Center: Installing the IBM Intelligent Operations Center multi-server platform and application
<!-- The default_host contained only aliases for endpoint defaultHttpEndpoint.
The generated VirtualHostGroup will contain only configured web server ports:
webserverPort=80
webserverSecurePort=443 -->
<VirtualHostGroup Name="default_host">
<VirtualHost Name="*:80"/>
<VirtualHost Name="*:443"/>
<VirtualHost Name="*:9080"/>
<VirtualHost Name="*:9443"/>
</VirtualHostGroup>
<ServerCluster CloneSeparatorChange="false" GetDWLMTable="false" IgnoreAffinityRequests="true" LoadBalance="Round Robin"
Name="iocsvr1_ioc_node_app_Cluster" PostBufferSize="0" PostSizeLimit="-1" RemoveSpecialHeaders="true" RetryInterval="60">
<Server CloneID="09285bf8-422d-4cdd-ab67-fabfa1b7d8b7" ConnectTimeout="5" ExtendedHandshake="false" MaxConnections="-1"
Name="ioc_node_app_iocsvr1" ServerIOTimeout="900" WaitForContinue="false">
<Transport Hostname="iocapp.smartercitiescloud.com" Port="9080" Protocol="http"/>
<Transport Hostname="iocapp.smartercitiescloud.com" Port="9443" Protocol="https">
<Property Name="keyring" Value="/opt/IBM/WebSphere/Plugins/config/webserver1/plugin-key.kdb"/>
<Property Name="stashfile" Value="/opt/IBM/WebSphere/Plugins/config/webserver1/plugin-key.sth"/>
<Property Name="certLabel" Value="APP_SERVER"/>
</Transport>
</Server>
<PrimaryServers>
<Server Name="ioc_node_app_iocsvr1"/>
</PrimaryServers>
</ServerCluster>
<ServerCluster CloneSeparatorChange="false" GetDWLMTable="false" IgnoreAffinityRequests="true" LoadBalance="Round Robin"
Name="iocsvr1_ioc_node_ana_Cluster" PostBufferSize="0" PostSizeLimit="-1" RemoveSpecialHeaders="true" RetryInterval="60">
<Server CloneID="96965c05-63a3-4a36-8f12-bf926409cff4" ConnectTimeout="5" ExtendedHandshake="false" MaxConnections="-1"
Name="ioc_node_ana_iocsvr1" ServerIOTimeout="900" WaitForContinue="false">
<Transport Hostname="iocana.smartercitiescloud.com" Port="9080" Protocol="http"/>
<Transport Hostname="iocana.smartercitiescloud.com" Port="9443" Protocol="https">
<Property Name="keyring" Value="/opt/IBM/WebSphere/Plugins/config/webserver1/plugin-key.kdb"/>
<Property Name="stashfile" Value="/opt/IBM/WebSphere/Plugins/config/webserver1/plugin-key.sth"/>
<Property Name="certLabel" Value="ANA_SERVER"/>
</Transport>
</Server>
<PrimaryServers>
<Server Name="ioc_node_ana_iocsvr1"/>
</PrimaryServers>
</ServerCluster>
<UriGroup Name="ioc_host_app_iocsvr1_ioc_node_app_Cluster_URIs">
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/iochelp/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/IBMJMXConnectorREST/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/iss/cros/js/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/api/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/images/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/sop/mail/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/theme/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/upload-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/export-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/cros-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/configuration-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/user-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/journal-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/userattribute-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/about-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/notification-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/analytic-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/comment-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/theme-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/taskbar-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/receiver-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/filter-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/authorization-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/session-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/cognos-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/location-map-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/login-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/sop-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/data-injection-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/datasource-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/geocoder-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/association-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/sysprop-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/image-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/kpi-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/slm-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/dataimport-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/i18n-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/extension-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/mapsettings-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/vote-service/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/ioc/api/spatial-service/*"/>

Installing the multi-server platform and application 15

 <Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ioc/*"/>

</UriGroup>
<Route ServerCluster="iocsvr1_ioc_node_app_Cluster" UriGroup="ioc_host_app_iocsvr1_ioc_node_app_Cluster_URIs"
VirtualHostGroup="default_host"/>
<UriGroup Name="ioc_host_ana_iocsvr1_ioc_node_ana_Cluster_URIs">
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/IBMJMXConnectorREST/*"/>
<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/ibm/api/*"/>

<Uri AffinityCookie="JSESSIONID" AffinityURLIdentifier="jsessionid" Name="/askws/*"/>

</UriGroup>
<Route ServerCluster="iocsvr1_ioc_node_ana_Cluster" UriGroup="ioc_host_ana_iocsvr1_ioc_node_ana_Cluster_URIs"
VirtualHostGroup="default_host"/>
</Config>

Activating the plug-in

Activate the consolidated application and analytics server plug-in.

Procedure
1. On the web server run the following commands to make a backup copy of your existing
plugin-cfg.xml plug-in where ${value} indicates the appropriate value from your installation
properties file.
cd ${plugin.install.dir}/config/webserver1
mv plugin-cfg.xml plugin-cfg-original.xml
For example:
cd /opt/IBM/WebSphere/Plugins/config/webserver1
mv plugin-cfg.xml plugin-cfg-original.xml
2. Compare the original plug-in with the consolidated plug-in. Add any changes required from the
original plug-in to the consolidated plug-in. For an initial installation no changes will be required.
For example, check that the Log element references the correct log file.
/opt/IBM/WebSphere/wlp/logs/iocsvr1/http_plugin.log

should be

/opt/IBM/WebSphere/Plugins/logs/webserver1/http_plugin.log
3. Copy the merged plug-in to the WebSphere plug-in configuration directory using the following
commands where ${value} indicates the appropriate value from your installation properties file and
<merged-plugin-file> is the fully-qualified name of your merged plug-in.
cd ${plugin.install.dir}/config/webserver1
cp <merged-plugin-file> plugin-cfg.xml
For example:
cd /opt/IBM/WebSphere/Plugins/config/webserver1
cp /tmp/app_plugin.xml plugin-cfg.xml

Restarting the HTTP server

Restart the HTTP server on the IBM Intelligent Operations Center web server to pick up your
configuration changes.

Procedure

Restart the HTTP server on the web server by running the following command as the root user where
${value} indicates the appropriate value from your installation properties file.
${ihs.install.dir}/bin/apachectl restart

For example:
/opt/IBM/HTTPServer/bin/apachectl restart

16 IBM Intelligent Operations Center: Installing the IBM Intelligent Operations Center multi-server platform and application
Installation log files
A script creates a log file for each installation invocation. The log files are saved to the /tmp directory.

The naming convention and location for the log file is:
/tmp/ioc51.install.<short_host_name>.<yymmdd-hhmm_timestamp>.<three_random_alphanumeric_characters>

For example, see the following log file names:

ioc51.install.iitsfweb.20150727-0636.dJ2
ioc51.install.iitsfdat.20150727-0702.X9N
ioc51.install.iitsfana.20150727-0721.5SC
ioc51.install.iitsfapp.20150727-0744.6QI

Installing the multi-server platform and application 17

18 IBM Intelligent Operations Center: Installing the IBM Intelligent Operations Center multi-server platform and application
Notices
Product legal notices for IBM Intelligent Operations Center V5.1.

This information was developed for products and services offered in the US. This material might be
available from IBM in other languages. However, you may be required to own a copy of the product or
product version in that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that
only that IBM product, program, or service may be used. Any functionally equivalent product, program,
or service that does not infringe any IBM intellectual property right may be used instead. However, it is
the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or
service.

IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not grant you any license to these patents. You can send
license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual
Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"

WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not in
any manner serve as an endorsement of those websites. The materials at those websites are not part of
the materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way it believes appropriate without
incurring any obligation to you.

Copyright IBM Corp. 2011, 2015 19

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Director of Licensing

IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US

Such information may be available, subject to appropriate terms and conditions, including in some cases,
payment of a fee.

The licensed program described in this document and all licensed material available for it are provided
by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or
any equivalent agreement between us.

The performance data and client examples cited are presented for illustrative purposes only. Actual
performance results may vary depending on specific configurations and operating conditions.

Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.

This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to actual people or business enterprises is
entirely coincidental.

Terms and conditions for product documentation

Permissions for the use of these publications are granted subject to the following terms and conditions.
Applicability
These terms and conditions are in addition to any terms of use for the IBM website.
Personal use
You may reproduce these publications for your personal, noncommercial use provided that all
proprietary notices are preserved. You may not distribute, display or make derivative work of
these publications, or any portion thereof, without the express consent of IBM.
Commercial use
You may reproduce, distribute and display these publications solely within your enterprise
provided that all proprietary notices are preserved. You may not make derivative works of these
publications, or reproduce, distribute or display these publications or any portion thereof outside
your enterprise, without the express consent of IBM.
Rights Except as expressly granted in this permission, no other permissions, licenses or rights are
granted, either express or implied, to the publications or any information, data, software or other
intellectual property contained therein.
IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion,
the use of the publications is detrimental to its interest or, as determined by IBM, the above
instructions are not being properly followed.
You may not download, export or re-export this information except in full compliance with all
applicable laws and regulations, including all United States export laws and regulations.

20 IBM Intelligent Operations Center: Installing the IBM Intelligent Operations Center multi-server platform and application
IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE
PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF
MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

Copyright notice

Copyright IBM Corporation 2011, 2015. All rights reserved. May only be used pursuant to an IBM
software license agreement. No part of this publication may be reproduced, transmitted, transcribed,
stored in a retrieval system, or translated into any computer language, in any form or by any means,
electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written
permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or
other reproductions of any machine-readable documentation for your own use, provided that each such
reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are
granted without prior written permission of IBM Corporation. The document is not intended for
production and is furnished as is without warranty of any kind. All warranties on this document are
hereby disclaimed, including the warranty of non-infringement and the implied warranties of
merchantability and fitness for a particular purpose.

U.S. Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corporation.

Notices 21
22 IBM Intelligent Operations Center: Installing the IBM Intelligent Operations Center multi-server platform and application
Trademarks
Cognos, CPLEX, IBM, ibm.com, DB2, Domino, GDDM, ILOG, Lotus, Notes, Passport Advantage,
Rational, Sametime, Tivoli, Service Request Manager, Smarter Cities, SPSS, Redbooks, WebSphere,
and Worklight, are trademarks of the IBM Corporation in the United States, other countries, or both.

Microsoft, Internet Explorer, Windows, and the Windows logo are trademarks of Microsoft Corporation in
the United States, other countries, or both.

Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the
United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or
trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

Oracle, Javascript, JavaBeans, and Java are registered trademarks of Oracle and/or its affiliates.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other names may be trademarks of their respective owners. Other company, product, and service names
may be trademarks or service marks of others.

Copyright IBM Corp. 2011, 2015 23

24 IBM Intelligent Operations Center: Installing the IBM Intelligent Operations Center multi-server platform and application
Readers Comments We'd Like to Hear from You
IBM Intelligent Operations Center
Installing the IBM Intelligent Operations Center multi-server platform and application
Version 5 Release 1

We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,
organization, subject matter, or completeness of this book. The comments you send should pertain to only the
information in this manual or product and the way in which the information is presented.

For technical questions and information about products and prices, please contact your IBM branch office, your
IBM business partner, or your authorized remarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use
the personal information that you supply to contact you about the issues that you state on this form.

Comments:

Thank you for your support.

Submit your comments using one of these channels:
v Send your comments to the address on the reverse side of this form.
v Send a fax to the following number: 1-800-227-5088 (US and Canada)

If you would like a response from IBM, please fill in the following information:

Name Address

Company or Organization

Phone No. Email address

 ___________________________________________________________________________________________________
Readers Comments We'd Like to Hear from You Cut or Fold
IBM Along Line

_ _ _ _ _ _ _Fold
_ _ _and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______

NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES

BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM
Information Development Department DLUA
P.O. Box 12195
Research Triangle Park, NC
USA 27709-9990

_________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape

Cut or Fold
Along Line
IBM

Printed in USA