Installing IBM Intelligent Operations Center using Installation Manager

IBM® Intelligent Operations Center can be installed using the provided graphical installer.

1. Run the export JAVA_HOME=/opt/ibm/java-x86_64-60/jre command.
2. Extract the BA_1.5_GUI_Installer_Lite_Launchpad.zip file in install_home.
3. Start the installation launchpad by running the install_home/launchpad.sh command.
4. Install IBM Installation Manager.
   1. Click Install IBM Installation Manager.
   2. Click Next.
   3. Read the license information.
   4. If you agree to the license terms, select I accept the terms in the license agreement and click Next. The installation will continue.
   5. If you do not agree to the license terms, select I do not accept the terms in the license agreement and click Next. The installation will terminate.
   6. Select where IBM Installation Manager will be installed.
   7. Click Next.
   8. Click Install.
   9. Restart the IBM Installation Manager.
   IBM Installation Manager is installed.
5. After the IBM Installation Manager is installed, the IBM Installation Manager needs to be closed and restarted. Starting IBM Installation Manager from the launchpad will pick up the topology file for IBM Intelligent Operations Center.
6. Click Install IBM Intelligent Operations Center.
7. Select the IBM Intelligent Operations Center - Version 1.5 package.
8. Click Next.
9. Read the license information.
   1. If you agree to the license terms, select I accept the terms in the license agreement and click Next. The installation will continue.
   2. If you do not agree to the license terms, select I do not accept the terms in the license agreement and click Next. The installation will terminate.
10. Specify the Shared Resource Directory for the installation. This directory will be used any time you use the IBM Installation Manager to install products using the installation server. Make sure to specify a drive with the most available space on the server.
11. Click Next.
12. Create a new package group by selecting Create a new package group. Select IBM Intelligent Operations Center.
13. Specify the name of the Installation Directory. The Installation Directory will be created. The installer will create subdirectories under this directory as needed.
14. For Architecture Selection, select 64-bit.
15. Click Next.
16. Deselect all options.
17. Select Configure topology.
18. Click Next.
19. Enter the configuration options. Make note of any defined passwords.
20. Click Next.
21. Review the installation options and click Next to start the installation.
22. After the installation completes, close IBM Installation Manager and the launchpad. Do not close the terminal window where the launchpad was started in step 3 since it has the JAVA_HOME environment set. If the terminal window is closed, JAVA_HOME must be exported again before continuing.
23. If the value entered for the topology password is greater than 15 characters in length, do the following to define a password for ITM.ADMIN.USER.PWD that is 15 characters or less in length.
    1. On the installation server edit the install_home/ioc/topology/iop_lite_topo.properties file where install_home is the directory where the IBM Intelligent Operations Center installation package was copied.
    2. Change the value defined for the ITM.ADMIN.USER.PWD to a value 15 characters or less. This password will be used when logging in the sysadmin user instead of the topology password.
    3. Save the changes.
24. Start the IBM Installation Manager by running the /opt/IBM/InstallationManager/eclipse/IBMIM command.
25. Click Modify > Next.
26. Select Prepare target servers.
27. Click Next > Modify.
28. If there are errors, review the log files in the /var/ibm/InstallationManager/logs/native directory. the log file names begin with a timestamp that can be used to correlate the log to when the installation tool was run.
29. Correct any errors or warnings found in the logs pertaining to your system and finish the installation before installing the next component. Some warnings and errors can be ignored. For example, warnings about IPv6 if you do not have IPv6 enabled or if your configuration is not connected to a Domain Name Service (DNS).
30. After correcting any errors, return to step 25 You will have the option to ignore system check errors. Select the next component in the list in step 26. Continue the process until cyber hygiene is to be installed.
    Important: Do not shut down the servers between installation phases. Shutting the servers down between phases has not been tested and can result in unpredictable results.

    Cyber hygiene applies best practice configurations to provide additional security to the IBM Intelligent Operations Center system. Before installing cyber hygiene, complete the post-installation configuration. Once the post-installation configuration is complete, return to step 24 and install and run cyber hygiene. Components successfully installed when IBM Installation Manager was previously run are checked. Do not uncheck these components or the components will be uninstalled when IBM Installation Manager is run again.

    If running in a virtualized environment, take a snapshot with memory of all servers after an installation step successfully complete and before installing the next component. This snapshot can be used to restart the installation at a successful state should an error occur.

    To reduce the time cyber hygiene runs scans and remediation, unmount any file system not required to be assessed for security. For example, the install_media directories on each server can be deleted after all installation steps are complete. These directories can be deleted or unmounted before running cyber hygiene.

    Note: Cyber hygiene is installed and run in the same step.

    Cyber hygiene should be the last step before moving your system to production status or when your system must address good security practices. All applications and solutions should be installed and configured before running cyber hygiene so the final system can be scanned and remediations applied.

    Changes applied to the system by cyber hygiene can cause problem with other applications and solutions. For example, other applications and solutions might have requirements on the Linux environment that are not in accord with good security practices. An application or solution might require for the system to be logged on as the root user to be installed or run. In this case some of the cyber hygiene changes might need to be temporarily or permanently changed or another solution found from the supplier of the application or solution.

    Once cyber hygiene changes are made, there is no automated method to change them. Any changes must be made by manual updates to the Linux operating system or by changing file or directory permissions.