Create the installation users,
configure the installation properties,
and run the installation script to configure each server.
Before you begin
If you want to install the optional
Device Management Enablement component, ensure that you have the prerequisite
products. You must have the following licenses:
- WebSphere® MQ
- For IBM® Intelligent Operations Center V5.2.1, you must have the license for WebSphere MQ V9.1.0.1 for Linux on X86 64 Multilingual
- For IBM Intelligent Operations Center V5.2.0, you must have the license for WebSphere MQ V8.0 for Linux
on X86 64 Multilingual
- IBM Integration Bus
- For IBM Intelligent Operations Center V5.2.1, you must have the license for IBM Integration Bus V10.0.0.16 Linux x86-64 including Toolkit Multilingual
- For IBM Intelligent Operations Center V5.2.0, you must have the license for IBM Integration Bus V10.0.0.3 Linux x86-64 including Toolkit Multilingual
Also, ensure that the
IBM Integration Bus installation files and
the
WebSphere MQ installation files are in the
/installmedia/linux_x64 directory.
To use Device Management Enablement,
you must also configure an LDAP user registry,
and add the IBM Intelligent Operations Center users
and groups to the registry.
For more information, see Configuring an LDAP user registry.
About this task
Configure and install the four servers in the following order:
- Data server
- Web server
- Analytics server
- Application server
Note: - Complete steps
1 - 6, and optionally steps 7 - 8, to configure each of the four
servers before you begin step 9.
- Wait for each installation script to complete before you start the
installation steps on the next server.
Procedure
Configuring the servers
Note: Complete steps
1 - 6, and optionally steps 7 - 8,
on each server in turn, unless indicated otherwise.
- On the server, open a terminal window and log on as a root user.
- Enter the following command to go to the /opt/IBM installation
directory:
cd /opt/IBM
- Enter the following command
to extract the ioc_platform.tar.gz file
to the /opt/IBM directory:
tar -zxvf ioc_platform.tar.gz
- Create the installation users and configure a shared SSH key between each of the servers.
Create the SSH key on only one server, then share the SSH key with the other servers.
- On the data server, enter the following commands as a root user:
cd /opt/IBM/ioc_install/applications/ioc/bin/ioc_install_user
./s1_create_ssh_key.sh
./s2_create_install_user.sh
- To copy the output files to the other servers,
enter the following command on the data server once for each of the other servers. In each case, enter the command on one line
and replace server_hostname
with the host name of the server that you are copying the output files to:
scp /opt/IBM/ioc_install/applications/ioc/bin/ioc_install_user/ioc_rsa
/opt/IBM/ioc_install/applications/ioc/bin/ioc_install_user/s2_create_install_user.sh
server_hostname:/opt/IBM/ioc_install/applications/ioc/bin/ioc_install_user/
- Enter the following two commands on each server, except for the data server:
cd /opt/IBM/ioc_install/applications/ioc/bin/ioc_install_user/
./s2_create_install_user.sh
- To change from a root user to an ioc_installer user
and go to the installation directory, enter the following commands:
su - ioc_installer
cd /opt/IBM/ioc_install/bin
- Configure the installation properties
in the ioc.install.properties file:
- To edit the ioc.install.properties file,
enter the following command:
sudo vi ../cfg/ioc.install.properties
- Configure each of the following installation server host name properties
with the fully qualified host name of the corresponding server in the installation environment:
ana.server.hostname
app.server.hostname
db.server.hostname
ihs.server.hostname
ldap.hostname
To obtain the fully qualified host name of a server,
open a terminal window on the server
and enter the following command:
hostname -f
- On the analytics server, the application server, and the web server,
configure the values of the liberty.instance.name properties
with the appropriate values for each server,
as shown in the following table:
Table 1. Values for liberty.instance.name properties on each server| Server |
Property name |
Property value |
| Analytics server |
liberty.instance.name |
iocana01 |
| Application server |
liberty.instance.name |
iocapp01 |
| Web server |
liberty.instance.name |
iocsvr1 |
- Optional: On only the data server, configure the value of the db2.data.logs.dir
property. The property is optional, so you can leave the value blank.
- 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:
- Exclamation point, !
- Opening parenthesis, (
- Closing parenthesis, )
- Ampersand, &
- Dollar sign, $
- Grave accent, `
Running the installation
Note: The preceding steps to configure the four servers
must be completed before you begin step 9.
- On only the data server, run the following license script, read the license agreement,
and enter Y to accept the agreement:
sudo ./ioc.accept.license.sh
- To run the installation script, choose one of the following options.
Note: You must run the installation script on the servers
in the order that is indicated in
About this task.
In the command, substitute a value for
server_initials
depending on the server that you are installing:- dat for the data server.
- web for the web server.
- ana for the analytics server.
- app for the application server.
What to do next
The installation log files are saved to the /tmp
directory. To prevent the log files from being deleted by automated system maintenance tasks, copy
the log files from the /tmp directory to another location.
The naming convention for the log files
is:
ioc.install.short_host_name.yymmdd-hhmm_timestamp.three_random_alphanumeric_characters
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 the related link.
For information about the sample users that are installed with the solution, and
about how to change user passwords, see the related link to "Securing the solution".
For information about how to log on to IBM Intelligent Operations Center, see the related link.