Sie sind auf Seite 1von 50

Rapid Installer v7.

3
Installation Guide

Authors:
Tomasz Kopacki
Jakub Ciesla
Michal Jusik
Security classification
This document is intended for internal use and should not be distributed outside IBM.

Document abstract
The Rapid Installer 7.3 Installation Guide provides detailed information for uploading configuration data
to a dedicated IBM Control Desk (ICD) implementation.
Trademarks and service marks
The following terms are trademarks or service marks of International Business Machines Corporation in
the United States and other countries:
1 DB2
2 IBM

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

Release date: May 2017


© Copyright International Business Machines Corporation 2017. All rights reserved.

PAGE 1
Contents
1.Introduction............................................................................................................................................................. 5
Description ............................................................................................................................................................. 5
Purpose ................................................................................................................................................................... 5
Terms of Use .......................................................................................................................................................... 5
Audience................................................................................................................................................................. 6
Structure of this document.................................................................................................................................... 6
Troubleshooting ..................................................................................................................................................... 7
2.What Rapid Installer can and can’t do ................................................................................................................... 8
How to use Rapid Installer .................................................................................................................................... 8
Supported architectures ........................................................................................................................................ 8
Technical introduction to WAS-current-node variable and technical details for both architectures. ...........9
Tiny environment.............................................................................................................................................. 11
Cluster Environment ......................................................................................................................................... 12
Upgrade paths ....................................................................................................................................................... 15
3.Requirements ........................................................................................................................................................ 16
Auto configuration ............................................................................................................................................... 16
OS requirements .................................................................................................................................................. 16
Passport Advantage repository ............................................................................................................................. 17
IBM Fix Central repository ................................................................................................................................... 17
Additional libraries – AIX only ............................................................................................................................. 17
Middleware requirements .................................................................................................................................... 17
DB2 Enterprise Server Edition .......................................................................................................................... 17
Security Directory Server ................................................................................................................................. 18
WebSphere Application Server........................................................................................................................ 18
QuickStart best practices ..................................................................................................................................... 18
4.Steps ...................................................................................................................................................................... 19
Rapid Installer configuration............................................................................................................................... 19
Installation Steps.................................................................................................................................................. 19
Step 1 – DB2 Installation ................................................................................................................................... 21
Step 2 – DB2 Configuration for ICD ................................................................................................................. 21
Step 3 – SDS Installation .................................................................................................................................. 22
Step 4 – SDS Configuration.............................................................................................................................. 23

PAGE 2
Step 5 – WebSphere Installation...................................................................................................................... 24
Step 6 – IHS Installation .................................................................................................................................. 25
Step 7 – WebSphere – Deployment Manager configuration .......................................................................... 26
Step 8 – WebSphere – ICD Node configuration ............................................................................................. 28
Step 9 – IHS Configuration .............................................................................................................................. 29
Step 10 – ICD 7.6.0.0 – QS 7.0 .......................................................................................................................... 30
Step 11 – ICD 7.6.0.1 – QS 7.1............................................................................................................................. 33
Step 12 – ICD 7.6.0.2 – QS 7.2........................................................................................................................... 33
Step 13 – ICD build and deploy ........................................................................................................................ 34
Appendix A: RI-Values.props .................................................................................................................................. 34
Appendix B: SPiN manual .......................................................................................................................................46
Appendix C: Required software packages ............................................................................................................... 48
Passport Advantage.............................................................................................................................................. 48
IBM Fix Central ....................................................................................................................................................49
Appendix D: Installation packages paths................................................................................................................. 51
Appendix E: Recommended folders size ................................................................................................................. 52

PAGE 3
1. Introduction
Description
This document provides a step-by-step walkthrough of the Rapid Installer (RI) installation for building an IBM
Control Desk 7.6.0.1 server, to prepare the system to the point where the QS 7.3 installation can start (using
the Migration Manager component) or to upgrade an existing QS 7.2.

Purpose
The primary purpose of this document is guide an installer through the installation, without having to have
an in-depth knowledge of RI.

Terms of Use
Rapid Installer uses technology that has been licensed from the Rapid Delivery Services (RDS) team for the
purpose of installing ISM components in support of the QuickStart solution. This is made available by the
Global ISM program and is free to use when used for this purpose.
ISM Rapid Installer is licensed to support QuickStart deployments ONLY. It is imperative that it is not used for
any other purpose. The consequences could be significant including all uses of the Installer, including for ICD
becoming chargeable, and not being compliant from an audit perspective.

PAGE 4
Audience
This guide in intended for users that install and maintain QuickStart stack. Although most of the tasks are
automated, it is required that users have at least basic skills described below
1) Linux/AIX OS skills
• users know how to create OS users and groups, assign users to multiple groups, creates
partitions and their mount points.
• How to use basic bash commands such as cp, scp, mv, rm, tail, vi, mkfs.*, mount, ln
2) DB2 skills
• user understands the difference between instance and the database
• Knows how to manually start/stop instance and perform basic SQL queries on the DB
3) LDAP skills
• user understands dependency between SDS and DB2
4) WebSphere skills
• user knows how to login to the WAS console and perform basic administration tasks
• start/stop JVM
• create a JVM
• generate WEB plugin
• configure JMS queues and LDAP authorization

Structure of this document


This document contains four chapters that describes Rapid Installer purpose, configuration and usage. At the
end of the documents we placed four appendixes that contains practical information about the configuration.
Chapter 1 – Introduction, explains what is the purpose of that documentation and what is Rapid Installer
generally. There is also a description who should read it and what are minimal knowledge requirements for
the users. At the end of the chapter there is a section how to troubleshoot installation issues.
Chapter 2 – Explains Rapid Installer main functions and supported solutions. One can find detailed description
of supported architectures and upgrade paths for existing environment.
Chapter 3 – This chapter contains list of all requirements for the platform. At the beginning of the chapter
we put a list of OS level requirements and a description of the new function that can automate those tasks.
Further in this chapter one can find a list of external software repositories that support software installation
packages. At the end of the chapter we described platform requirements for each middleware piece.
Chapter 4 – Steps. General description how to configure Rapid Installer and brief description of each RI step.
For each step, we described its purpose, required files, configuration and what is the output of it.
Appendix A: RI-Values – description of each RI property with its default value.
Appendix B: SPiN manual – short manual for the tool.
Appendix C: Required software packages – list of all required files from external repositories.
Appendix D: Paths for all required installation packages.
Recommended folders size

PAGE 5
Troubleshooting
Although authors of the Rapid Installer put a huge effort in making the tool easy to use and prone to errors,
it wasn't possible to make it resistant to wrong configuration. In a need of debugging checking RI report logs
file should be always point of start.
Each RI step writes it output into separate log file placed in /usr/spin/spinPackage/custom-spin/reports
Additionally, each middleware piece has its own log files. Below we present a list of the most important log
files for them:
DB2: db2diag
Security Directory Server: /usr/IBM/ldap/idsslapd-ldapusr/logs
WebSphere Application Server: /usr/IBM/WebSphere/AppServer/profiles/<profile_name>/logs
IBM Control Desk: /usr/IBM/SMP/ConfigTools/logs/

PAGE 6
2. What Rapid Installer can and can’t do
How to use Rapid Installer
Rapid Installer is a SPiN framework based tool. It was designed to automate ICD stack installation. That
automation was implemented in a set of atomic steps. Each step is responsible for installation or configuration
one of the stack piece.
Complete list of steps with detailed description if available on chapter 4. At the end of the document - in
Appendix B we published short SPiN manual.

Supported architectures
Rapid Installer supports two main architectures. Tiny and Cluster.
Regardless of the scenario all values and infrastructure information is kept in the configuration file: RI-
Values.props.
Situation when all components are installed on a single machine is called Tiny installation.
Cluster environment contains two or more hosts. In such situation, it is mandatory that hosts can communicate
each other and can resolve hostnames either locally or by DNS system.

Scenario 1:
Server1 – Installed DB2, SDS, Dmgr, Node and IHS

Scenario 2:
Server1 - Installed DB2 and SDS
Server2 - Installed WAS with Dmgr, Node1 and IHS1
Server3 - Installed WAS with Node2 and IHS2

PAGE 7
Technical introduction to WAS-current-node variable and technical details for both
architectures.
WAS-current-node variable has been designed to implement architecture as a code in RI-Values.props file.
It is done once, while the Rapid installer is being run on different nodes which are part of the
infrastructure/environment. It allows to have consistent settings while copying Rapid Installer between
different host. The only settings which changes is WAS-current-node. Rest of the JVM blocks shouldn't be
modified.
By default, block with "Node1" part, looks like below:
WAS-node-jvms-Node1-UI=0
WAS-node-jvms-Node1-INT=0
WAS-node-jvms-Node1-CRON=0
WAS-node-jvms-Node1-BROS=0
WAS-node-jvms-Node1-Tiny=1

This configuration should be read in this way:


On Node1:
- 1 Tiny JVM will be installed
- 0 UI, INT, CRON and BROS JVMs will be configured.

Such structure allows to design infrastructure before starting installation on all nodes.
For instance, if it's required, just copy and paste last block and change the "Node" part in variable names.

If we would like to create configuration for node 2 it would be as follows:


WAS-node-jvms-Node2-UI=2
WAS-node-jvms-Node2-INT=2
WAS-node-jvms-Node2-CRON=1
WAS-node-jvms-Node2-BROS=1
WAS-node-jvms-Node2-Tiny=0

When launching RI-Step08-WebSphere-Configure-Maximo step on Node2 and changing WAS-current-node


value to "Node2", application servers will be created on second node.
In above example 2 UI and INT servers would be created. 1 CRON and BROS server. No Tiny server will be
created.

Example for third node might be as follows:


WAS-node-jvms-Node3-UI=1
WAS-node-jvms-Node3-INT=1
WAS-node-jvms-Node3-CRON=0
WAS-node-jvms-Node3-BROS=0
WAS-node-jvms-Node3-Tiny=0

Please note that if we choose tiny configuration only WAS-node-jvms-Node1-Tiny should be set.
If we decide to create cluster environment UI, INT, CRON, BROS variables should be considered. It is not
mandatory to create all types of application server on node.

IMPORTANT: Either set Tiny variable or rest of variables.

PAGE 8
Figure 1

PAGE 9
Tiny environment
Let's assume that we are installing all components on a server which has hostname tiny.local
Proper parts of the configuration file are shown below:
WAS-dmgr-name=Dmgr
WAS-dmgr-node-name=maximo-dmgr
WAS-dmgr-cell-name=maximo-dmgr
WAS-node-cell-name=maximo-node
WAS-dmgr-hostname=tiny.local
WAS-dmgr-port=9043

#WAS profile name and reference to node settings below


#Possbile values for WAS-current-node are Node1, Node2 etc.
WAS-current-node=Node1

#JVMs for Node1


WAS-node-jvms-Node1-UI=0
WAS-node-jvms-Node1-INT=0
WAS-node-jvms-Node1-CRON=0
WAS-node-jvms-Node1-BROS=0
WAS-node-jvms-Node1-Tiny=1

#Profile name for Node 1


WAS-Node1-name=Maximo
WAS-Node1-node-name=maximo-${WAS-Node1-name}-${WAS-Node1-hostname}
WAS-Node1-hostname=tiny.local

For overview please look on the image below:

Figure 2

PAGE 10
Cluster Environment
Let's consider "Scenario 2" from first part of this chapter.

Scenario 2:
Server1 - Installed DB2 and SDS
Server2 - Installed WAS with Dmgr, Node1 and IHS1
Server3 - Installed WAS with Node2 and IHS2

In such case let's assume Server2 has hostname server-A.local. Server3 hostname is server-B.local.
RI-Values configuration file on Server2 would be as follows:
WAS-dmgr-name=Dmgr
WAS-dmgr-node-name=maximo-dmgr
WAS-dmgr-cell-name=maximo-dmgr
WAS-node-cell-name=maximo-node
WAS-dmgr-hostname=server-A.local
WAS-dmgr-port=9043

#Possbile values for WAS-current-node are Node1, Node2 etc.


WAS-current-node=Node1

#Clusters names
WAS-cluster-UI-name=MXCluster
WAS-cluster-INT-name=INTCluster
WAS-cluster-CRON-name=CronCluster
WAS-cluster-BROS-name=BROSCluster

#JVMs name templates


WAS-jvm-UI=UIServer
WAS-jvm-INT=IntServer
WAS-jvm-CRON=CronServer
WAS-jvm-BROS=BrosServer
WAS-jvm-Tiny=MXServer

### Node 1 section

#JVMs for Node1


WAS-node-jvms-Node1-UI=2
WAS-node-jvms-Node1-INT=2
WAS-node-jvms-Node1-CRON=0
WAS-node-jvms-Node1-BROS=1
WAS-node-jvms-Node1-Tiny=0

#Profile name for Node 1


WAS-Node1-name=Maximo
WAS-Node1-node-name=maximo-${WAS-Node1-name}-${WAS-Node1-hostname}
WAS-Node1-hostname=server-A.local

PAGE 11
Now we can launch RI-Step08-WebSphere-Configure-Maximo step on Server2 and wait till it finishes
configuration.
For reference please look on the image below:

Figure 3
Please note that both configurations must be in the same file.
For readability, RI-Values.props configuration section has been shown only for WAS-current-node and suitable
Node2 section.

RI-Values.props configuration file on Sserver3 would be as follows:


#Possible values for WAS-current-node are Node1, Node2 etc.
WAS-current-node=Node2

PAGE 12
### Node 2 section ###

#JVMs for Node2


WAS-node-jvms-Node2-UI=3
WAS-node-jvms-Node2-INT=0
WAS-node-jvms-Node2-CRON=1
WAS-node-jvms-Node2-BROS=0
WAS-node-jvms-Node2-Tiny=0

#Profile name for Node 2


WAS-Node2-name=Maximo
WAS-Node2-node-name=maximo-${WAS-Node2-name}-${WAS-Node2-hostname}
WAS-Node2-hostname=server-B.local

After making sure that WAS-current-node variable has been changed to Node2 and configuration is properly
set, we can launch RI-Step08-WebSphere-Configure-Maximo step on Server3 and wait till it finishes
configuration.

Figure 4

PAGE 13
Upgrade paths

PAGE 14
3. Requirements
Auto configuration
In previous RI versions, it was required to create directories, users and groups manually by the user. In this
version, we developed new feature that can automate those tasks. By default, feature is enabled and fulfills
those requirements based on the configuration provided in RI-Values.props file.
Feature can be disabled be setting flag RI-create-missing-os-configuration to false.

OS requirements
Rapid Installer has been tested on AIX 7.1 and Red Hat 7.3. All Rapid Installer tasks must be run as root user
and requires Java JRE in version 1.7 or higher.
The user IDs, Groups, and directories described in this document follow the standards used by the QuickStart
team when building systems for ICD. Where there is a requirement to vary from these, for example to meet
local support team requirements, this can be accomplished by setting up the appropriate groups and
directories and configuring the property files accordingly.
OS Groups
Group Purpose
db2iadm1 Db2 admin group
db2iadm2 Db2 admin group
db2fadm1 Shared db2 fenced group
idsldap LDAP admin group
wasadmin Wasadmin group
OS Users
User Primary Group Additional Groups Home Directory

existing groups plus the following /root


root System
db2iadm1, db2iadm2, idsldap

idsccmdb db2iadm1 idsldap /home/idsccmdb


db2fenc1 db2fadm1 db2fadm1 /home/db2fenc1
db2sbysa db2iadm2 db2iadm2 /home/db2sbysa
db2fenc2 db2fadm1 db2fadm1 /home/db2fenc1
ldapusr db2iadm1 idsldap /usr/IBM/ldap
maximo db2iadm2 db2iadm2 /home/maximo
ihsadmin ihsadmin ihsadmin /home/ihsadmin
wasadmin wasadmin wasadmin /home/wasadmin

PAGE 15
Passport Advantage repository
Installation packages for the middleware stack is available on Passport Advantage. Diamond Team doesn't
provide access to the PA platform nor publish those files directly. Access must be purchased by the local
Project Manager.
Full list of the required software is available in Appendix C: Required software packages
Passport Advantage platform is available under this URL:
http://www-01.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm

IBM Fix Central repository


Software published on Passport Advantage doesn’t include latest fix packs. Those files are available on the
IBM Fix Central platform.
Full list of the required software is available in Appendix C: Required software packages
IBM Fix Central platform is available under this URL:
https://www-945.ibm.com/support/fixcentral/

Additional libraries – AIX only


These additional libraries are required by middleware software and they should be on board before installation
process is started. These packages are automatically installed on Red Hat system during the installation.
Package name
compat-libstdc++-33.i686
compat-libstdc++-33.x86_64
libstdc++.i686
libstdc++.x86_64
ksh
pam.i686
libaio
unzip
hostname
pam
file
util-linux

Middleware requirements
DB2 Enterprise Server Edition
1. Hardware requirements
• Memory requirements are affected by the size and complexity of your database system, and the
extent of database activity and the number of clients accessing your system. At a minimum, we
recommend 1G.

PAGE 16
2. Software requirement
• Java IBM Runtime Environment in version 5 or later
• Internet connectivity
• yum package in Linux system.
3. Documentation
• http://www-01.ibm.com/support/docview.wss?uid=swg27038033#105Ent

Security Directory Server


1. Hardware requirements
• Minimum 128 Mb memory required
2. Software requirements
• IBM Global Security Kit
• Korn shell
3. Documentation
• https://www.ibm.com/support/knowledgecenter/SSVJJU_6.4.0/com.ibm.IBMDS.doc_6.4/c_po_S
DS_sysreq.html

WebSphere Application Server


1. Hardware requirements
• Minimum 1G memory recommended
• processor Intel or AMD family, 1.2GHz or faster
2. Software requirements
• OS AIX 7.1 with TL version 1
• OS Red Hat Enterprise Linux (RHEL) 7.1
• OS Red Hat Enterprise Linux (RHEL) 7.3
3. Documentation
• http://www-01.ibm.com/support/docview.wss?uid=swg27038218

QuickStart best practices


Diamond Team created a DB2 best practices document that describes recommended DB2 configuration. It
was designed to meet IBM ITCS security standards and guideline delivered by Tivoli team. Rapid Installer was
created in line with that document. However, if you want to increase database security or improve database
performance it is recommend to download and follow instructions placed in the QS Best Practices guide. To
get the documentation follow those steps:
1. Log in into diamond instance https://diamond.extnet.ibm.com/maximo/ui/login
3 Go to Self Service -> Self Service Center
2. In search panel type "db2 practices"
3. In results select DB2 Best Practices
4. Click order now on right side
5. Click Show Details
6. Link to documentation is available from the SR's attachments

PAGE 17
4. Steps
Rapid Installer configuration
Although Rapid Installer comes with a default configuration it is highly recommended to carefully check if
default values can be applied on a target infrastructure.
Whole RI configuration is kept in a single file:
spinPackage/custom-properties/RI-Values.props
Each installation step is described below with a list of required files and properties. In Appendix A we described
all configuration properties used by RI.

Installation Steps
Rapid Installer is divided into several steps where each step is divided into sub-steps. This structure allows to
gather activities in smaller pieces which are logically consistent. After launching main menu list of available
steps is being displayed. They are numbered and ordered in a typical scenario flow.
IMPORTANT: Some steps can be launched only once. Running some steps several times might corrupt the
environment.
IMPORTANT: It is not required to always run all steps – please refer to the supported upgrade paths chapter.
No. Step name Description
1 RI-Step01-DB2-Install.props Installs DB2 software
2 RI-Step02-DB2-Configure-Maximo.props Configures DB2 for ICD application
3 RI-Step03-SDS-Install.props Installs IBM Security Directory Server
4 RI-Step04-SDS-Configure.props Applies initial SDS configuration
5 RI-Step05-WebSphere-Install.props Installs WebSphere Application Server and its fix
pack
6 RI-Step06-IHS-Install.props Installs IBM HTTP Server and its fix pack
7 RI-Step07-WebSphere-Configure-Dmgr.props Configures Deployment manager
8 RI-Step08-WebSphere-Configure-Maximo.props Creates nodes, federate them to DMGR and
creates application servers
9 RI-Step09-IHS-Configure.props Configures IHS, add it to WAS. Generates,
propagates plug-in
10 RI-Step10-ICD7600-QS70.props Installs ICD 7600
11 RI-Step11-ICD7601-QS71.props Upgrades version ICD 7600 to version 7601
12 RI-Step12-ICD7602-QS73.props Upgrades version ICD 7601 to version 7602
13 RI-Step13-ICD-Build-and-Deploy.props Builds and deploys ear based on previously
prepared configuration

PAGE 18
Step 1 – DB2 Installation
Name of the step RI-Step01-DB2-Install.props
Pre-requisites N/A
Description This step installs DB2 software on a desired path.
Required files DB2
AIX v10.5fp8_aix_server_t.tar.gz
Linux v10.5fp8_linuxx64_server_t.tar.gz
DB2 License
Multiplatform DB2_ESE_Restricted_QS_Act_V10.5.zip
Configuration Property Default Value Description
DB-hostname db2.local DB2 hostname

DB-installation-dir /opt/IBM/db2 DB2 installation path

Output After successful installation DB2 software is installed on a desired path without any
instances configured yet.

Step 2 – DB2 Configuration for ICD


Name of the step RI-Step02-DB2-Configure-Maximo.props
Pre-requisites Step 1
Description This step configures DB2 instance for the ICD. Maximo database is created with pre-
defined settings required by ICD product. This database is ready to use as placeholder
fur future ICD installation and does NOT contains product itself.
Required files N/A
Configuration Property Default Value Description
DB-maximo-instance-user db2sbysa Database instance user with
highest administration rights
DB-maximo-instance-user- ${RI-standard-password} Password for instance user
password
DB-maximo-instance-user-main- db2iadm2 Main group for instance user
group
DB-maximo-instance-user-home- /home/db2sbysa Home directory for instance user
dir

DB-maximo-instance-user- db2ictl1 Placeholder group for system


syscontrol-grp control authority

DB-maximo-instance-user-port 51000 Exposed database port for


external connections
DB-fenc1-user db2fenc1 User created for executing user
defined function
DB-fenc1-user-password ${RI-standard-password} Fenced user password

DB-fenc1-user-main-group db2fadm1 Fenced user group

PAGE 19
DB-fenc1-user-home-dir /home/db2fenc1 Fenced user home directory

DB-maximo-database-name maximo ICD database name

DB-maximo-schema=maximo maximo Main schema used for ICD


database

DB-maximo-tablespace-data MAXDATA Tablespace for ICD data. highly


recommend to keep MAXDATA

DB-maximo-tablespace-index MAXINDX Tablespace for ICD indexes.


highly recommend to keep
MAXINDX
DB-maximo-tablespace-temp MAXTEMP Tablespcae for ICD temporary
data. highly recommend to keep
MAXTEMP
DB-maximo-tablespace- SYSCATSCPACE Default tablespace created during
syscatspace database creation
DB-maximo-tablespace- userspace Default tablespace created during
userspace=userspace database creation

DB-maximo-tablespace- tempspace Default tablespace created during


tempuserspace=tempspace database creation

DB-maximo-user maximo Main ICD database user

DB-maximo-user-password ${RI-standard-password} Password for ICD database user


DB-maximo_user-main-group db2iadm2 Group for ICD database

DB-maximo-user-home-dir /home/maximo Home folder for ICD database


user

DB-maximo-instance-root-dir /home/db2sbysa Home folder for ICD database

DB-maximo-instance-data-dir /home/db2sbysa/db2data Path where the database


containers are stored.

DB-maximo-instance-logs-dir /home/db2sbysa/logs Path to transaction logs


DB-maximo-instance-backups-dir /db2backups Backup directory

DB-maximo-instance-archlogs-dir /home/db2sbysa/archlogs Path to old transaction logs

DB-maximo-instance-dump-dir /home/db2sbysa/dump Path to database informational


logs

Output DB2 instance created with empty database ready for ICD installation.

Step 3 – SDS Installation


Name of the step RI-Step03-SDS-Install.props
Pre-requisites N/A
Description Following step install SDS on your operating system. SDS provides way to
authenticate users to maximo application by non-encrypted channel. During this step,
also GsKit is installed which is required by SDS itself. At this stage database instance
for LDAP protocol is not created yet. By default, /opt/ibm/ldap for Linux and
/opt/IBM/ldap for AIX is used. It's recommend to keep these paths during installation.
Further path changes can be handle by creating symbolic links.
Required files SDS
AIX sds64-aix-ppc.iso

PAGE 20
Linux sds64-linux-x86-64.iso
Libraries and fix packs
6.4.0.11-ISS-ISDS-AIX-IF0011.tar.gz
AIX 8.0.50.71-ISS-GSKIT-AIX-FP0071.tar.gz
6.0.16.26-ISS-JAVA-AIX-FP0026.tar
6.4.0.11-ISS-ISDS-LinuxX64-IF0011.tar.gz
Linux 8.0.50.71-ISS-GSKIT-LinuxX64-FP0071.tar.gz
6.0.16.26-ISS-JAVA-LinuxX64-FP0026.tar
Configuration Property Default Value Description
SDS-ldap-hostname ldap.local SDS hostname

SDS-ldap-bind cn=root LDAP administration user

SDS-ldap-bindPwd ${RI-standard-password} LDAP administration user


password

SDS-ldap-base-entry ou=SWG,o=IBM,c=US Distinguished name for ldap


repository

SDS-ldap-ldapEncrpt custEncSeed08 Randomization parameter for


encryption settings.

SDS-ldap-ldapSALT custEncSalt8 Randomization parameter for


encryption settings.

SDS-ldap-port 389 LDAP port for non-encrypted


connection

SDS-ldap-ssl-port 636 LDAP port for encrypted


connection

Output LDAP service installed, not yet configured.

Step 4 – SDS Configuration


Name of the step RI-Step04-SDS-Configure.props
Pre-requisites Step 1 and Step 3
Description This step configures SDS service with default accounts for WebSphere and ICD.
During the configuration DB2 instance is also created and configured as an LDAP
backend.
Required files N/A
Configuration Property Default Value Description
DB-ldap-instance-user idsccmdb Database instance user with
highest administration rights
DB-ldap-instance-user-password ${RI-standard-password} Password for instance user

DB-ldap-instance-user-main-group db2iadm1 Main group for instance user


DB-ldap-instance-user-additional- db2iadm1 Administration group for instance
groups user

DB-ldap-instance-user-home-dir /home/idsccmdb Home directory for instance user

PAGE 21
DB-ldap-instance-user-syscontrol- db2ictl1 Placeholder group for system
grp control authority
DB-ldap-instance-user-port 50000 LDAP database port

DB-fenc2-user db2fenc2 User created for executing user


defined function

DB-fenc2-user-password ${RI-standard-password} Fenced user password

DB-fenc2-user-home-dir /home/db2fenc2 Fenced user home directory

DB-fenc2-user-port 61000 Fenced user port

SDS-ldap-db-name ldapdb2 LDAP database name

DB-ldap-instance-root-dir /home/idsccmdb Home folder for ICD database

DB-ldap-instance-data-dir /home/idsccmdb/db2data Path where the database


containers are stored.

DB-ldap-instance-logs-dir /home/idsccmdb/logs Path to transaction logs

DB-ldap-instance-backups-dir /home/idsccmdb/backups Directory for backups

DB-ldap-instance-archlogs-dir /home/idsccmdb/archlogs Path to old transaction logs


DB-ldap-instance-dump-dir /home/idsccmdb/dump Path to database informational
logs

Output Once this step finishes LDAP service is started and ready to work.

Step 5 – WebSphere Installation


Name of the step RI-Step05-WebSphere-Install.props
Pre-requisites None
Description This step has been designed to automatically install all required WebSphere
Application Server packages and fix packs.
Before launching this step, proper software packages must be downloaded from IBM
official repositories.
Required files WebSphere Application Server
WASND_v8.5.5_1of3.zip
Multiplatform WASND_v8.5.5_2of3.zip
WASND_v8.5.5_3of3.zip
WebSphere Application Server fix packs
8.5.5-WS-WAS-FP011-part1.zip
8.5.5-WS-WAS-FP011-part2.zip
Multiplatform WS_SDK_JAVA_TEV7.0_1OF3_WAS_8.5.5.zip
WS_SDK_JAVA_TEV7.0_2OF3_WAS_8.5.5.zip
WS_SDK_JAVA_TEV7.0_3OF3_WAS_8.5.5.zip
Installation Manager
AIX agent.installer.aix.gtk.ppc_1.7.3000.20140521_1925.zip

PAGE 22
Linux agent.installer.linux.gtk.x86_64_1.7.3000.20140521_1925.zip
Configuration Property Default Value Description
RI-was-user wasadmin Administrative user account which
is created at OS level.

RI-was-user-password ${RI-standard-password-for-ICD} User's associated password which


is used for authentication
purposes.
By default, abcd1234 is being
used which is only for demo
purposes.
In production environments, this
value must be changed.

RI-was-installation-dir /usr/IBM/WebSphere/AppServer Installation directory of the


WebSphere Application Server.

Output After completing this step WAS ND software is being installed. Environment is
prepared for the configuration which will take place in next steps.
WebSphere ND does not have any profiles created at this stage and cannot be
launched.
Profiles and other configuration settings will be done in next steps.

Step 6 – IHS Installation


Name of the step RI-Step06-IHS-Install.props
Pre-requisites None
Description This step has been designed to automatically install all required packages and fix
packs for IBM HTTP Server.
Before launching this step, proper software packages must be downloaded from IBM
official repositories.
Required files IBM HTTP Server
WAS_V8.5.5_SUPPL_1_OF_3.zip
Multiplatform WAS_V8.5.5_SUPPL_2_OF_3.zip
WAS_V8.5.5_SUPPL_3_OF_3.zip
IBM HTTP Server fix packs
8.5.5-WS-WASSupplements-FP011-part1.zip
Multiplatform 8.5.5-WS-WASSupplements-FP011-part2.zip
8.5.5-WS-WASSupplements-FP011-part3.zip
Installation Manager
AIX agent.installer.aix.gtk.ppc_1.7.3000.20140521_1925.zip
Linux agent.installer.linux.gtk.x86_64_1.7.3000.20140521_1925.zip
Configuration Property Default Value Description

PAGE 23
IHS-admin-username ihsadmin Administrative user account which
is created at OS level.
Allows to managed the http server
locally and/or remotely.

IHS-admin-password ${RI-standard-password-for-ICD} User's associated password which


is used for authentication
purposes.
By default, abcd1234 is being
used which is only for demo
purposes.
In production environments, this
value must be changed.

RI-ihs-installation-dir /usr/IBM/HTTPServer Installation path for the IHS.

RI-ihs-plugin-installation-dir /usr/IBM/WebSphere/Plugins Installation directory for IHS


Plugin.

Output After completing this step IBM HTTP Server software is installed. Environment is
prepared for the configuration which will take place in next steps.
Configuration files (httpd.conf) have default settings. Integration between IHS, WAS
and ICD will be done in later activities.
SSL Configuration also is not set up yet and will be configured in coming activities.
By default, IHS is being installed to /usr/IBM/HTTPServer
IBM HTTP Server Plugin is being installed as well.
It allows to manage IHS and integrate WAS with ICD. It grants ability to map all
applications on different application servers to be available on a single HTTPS port.
By default, IHS Plugin is installed to /usr/IBM/WebSphere/Plugins.

Step 7 – WebSphere – Deployment Manager configuration


Name of the step RI-Step07-WebSphere-Configure-Dmgr.props
Pre-requisites Steps 1-6
Description This step configures WebSphere Application Servers for ICD platform. It creates all
required (and desired) clusters/JVMs. Also configures ldap authentication and JMS
queues.
Required files N/A
Configuration Property Default Value Description
RI-was-user wasadmin Administrative user name which
allows to log on to the WebSphere
Administration console via web
browser. User with the same name is
being created and/or required at the
OS level.
RI-was-user-password ${RI-standard-password} By default, standard password for all
demo installation is being used.
RI-standard-password variable has
default value of "abcd1234". This
setting allows to associate password
with user, which grants access to the

PAGE 24
OS and WebSphere Administration
console
WAS-dmgr-name Dmgr This variable indicates of the profile
name which is being created in the
configuration step.

WAS-dmgr-node-name maximo-dmgr Value of this setting determines the


name of the node which is correlated
with Deployment Manager profile.

WAS-dmgr-cell-name maximo-dmgr This setting sets up the cell name for


Deployment Manager.

WAS-dmgr-hostname dmgr.local Hostname on which the RI-Step05-


WebSphere-Install step has been
performed. Allowed values are FQDN
and/or names resolved locally. (e.g.
via hosts file). This hostname will be
used in next steps to provide
connectivity between other
components. In cluster environment,
other machines must resolve this
hostname as well.
WAS-dmgr-port 9043 WebSphere Administration console
port setting indicates on which port
Deployment Manager is listening.
This value determines what port
must be entered in URL when
accessing administration console via
web browser. Typical URL is as
follows https://<WAS-dmgr-
hostname>:<WAS-dmgr-
port>/ibm/console/
(e.g.
https://dmgr.local:9043/ibm/console)

Output After this step finishes WebSphere DMGR profile is created and configured. Although,
it is required to proceed with the next step to create actual JVMs that run ICD
platform.

Step 8 – WebSphere – ICD Node configuration


Name of the step RI-Step08-WebSphere-Configure-Maximo.props
Pre-requisites Steps 1-7
Description RI-Step08-WebSphere-Configure-Maximo step is responsible for creating node and its
configuration.
In similar manner as it is for RI-Step07-WebSphere-Configure-Dmgr user action is
required before running this step.
In this step beside node and its profile creation, application servers and/or clusters
are created as well.
Within this process node is being created and federated to Deployment Manager cell.
Please notice:
Note 1: WAS must be installed on the box where the Dmgr and/or Node is being
configure.

PAGE 25
Note 2: WAS and Node must be installed and configured prior IHS installation and
configuration on particular machine.
Required files N/A
Configuration Property Default Value Description
WAS-current-node Node1 Determines which JVM block is
considered. For detailed
description please check
paragraph "Supported
Architectures"
WAS-Node1-name Maximo This variable determines the name
of the profile on "Node1". When
planning cluster configuration.
This variable is also copied and
"Node1" is replaced to next node.
For instance, when making
configuration for node2 variable
would look like this:
WAS-Node2-name=Maximo

WAS-Node1-node-name ${WAS-Node1-name}-${WAS- This variable defines the node


Node1-hostname} name which will be configured
and federated with Dmgr. In
similar manner, as before "Node1"
must be replaced with proper
value. For instance, when making
configuration for node2 variable
would look like this:
WAS-Node2-node-name=maximo-
${WAS-Node2-name}-${WAS-
Node2-hostname}

WAS-Node1-hostname node1.local This variable determines the


hostname on which we are
running Rapid Installer. Like in
previous cases it must be FQDN or
locally resolved name. Also,
communication between Dmgr
and this node must be present. In
similar way as previously when
configuring it for next node
"Node1" has to be replaced with
proper node. For instance, when
making configuration for node2
variable would look like this:
WAS-Node2-
hostname=node2.local
Please notice that "Node1" has
been changed to "Node2". Value
has been adjusted to situation and
value is node2.local

Output This setup requires to launch Rapid Installer on each server one by one. For detailed
information of this step please look on paragraph "Supported architecture".
As an outcome dependent on the chosen configuration we would have Tiny or cluster
environment.
It would have proper/chosen types and quantity of application servers, JMS, JDBC and
other components set.

PAGE 26
Step 9 – IHS Configuration
Name of the step RI-Step09-IHS-Configure.props
Pre-requisites Steps 6-8
Description This step is responsible for configuration of the IBM HTTP Server.
Required files N/A
Configuration Property Default Value Description
IHS-admin-username ihsadmin Administrative user account which
is created at OS level.
Allows to manage the http server
locally and/or remotely.

IHS-admin-password ${RI-standard-password-for-ICD} User's associated password which


is used for authentication
purposes.
Default password is being used
only for demo purposes.
In production environments, this
value must be changed.

80 Port number under which the http


IHS-node1-http-port
service is available.

IHS-node1-admin-port 8008 Administrative port which allows


to configure and control IHS.
This functionality allows to locally
or remotely change server's
settings.
For authentication IHS-admin-
username and IHS-admin-
password variables values are
used.

IHS-hostname ihs.local This variable determines the


hostname on which the IHS server
is installed.
It has to be FQDN or locally
resolved name.
In cluster environment
connectivity between this host
and other hosts must be working.
If installing more than one IHS
server this value must be changed
before running this step on
another node.

IHS-webserver-name ihs-01 The name of the IHS server which


will be present in WAS
Administrative console under
server’s section.
When installing more than one
IHS server this value must be
changed before running this step
on another node.

IHS-node-name WebServerNode1 It's the name of the unmanaged


node which is going to be added
to the WAS.

PAGE 27
When installing more than one
IHS server this value must be
changed before running this step
on another node.

IHS-logs ${RI-ihs-installation-dir}/logs This variable determines the logs


directory which is being set while
configuring IHS.
Default value is resolved to
/usr/IBM/HTTPServer/logs when
considering initial settings.

Output When successfully finishing this step IHS should be configured, added as an
unmanned node to the WAS Deployment Manager.
IHS Plugin which has been installed earlier should be linked with WAS and proper
plugin configuration should be propagated.
All installed application will be mapped to a single https port 443.
Self-singed certificate is being generated.

Step 10 – ICD 7.6.0.0 – QS 7.0


Name of the step RI-Step10-ICD7600-QS70.props
Pre-requisites Steps 1 - 9
Description This step has been designed to install ICD version 7.6.0.0.
It must be launched on host on which WAS with Deployment Manager has been
installed and configured.
Before launching this step, proper software packages must be downloaded from IBM
official repositories.
It's mandatory to install all middleware (DB2, SDS, WAS, IHS) and configure it before
running this step.
If the ICD is being installed in a clustered environment connectivity between servers
is required.
Required files IBM Control Desk
CD_SP_Ed_V760_1of2_Mltptfm.tar
Multiplatform
CD_SP_Ed_V760_2of2_Mltptfm.tar
Installation Manager
AIX agent.installer.aix.gtk.ppc_1.7.3000.20140521_1925.zip
Linux agent.installer.linux.gtk.x86_64_1.7.3000.20140521_1925.zip
Configuration Basic configuration properties:
Property Default Value Description
RI-Cluster-environment false This variable determines if the application
will be in all-in-one or clustered
environment.
By default, non-clustered environment is
set.

PAGE 28
ICD-installation-dir /usr/IBM/SMP Installation path for the ICD

SCCD-maxadmin-user-name maxadmin Administrative account for Maximo.

SCCD-maxadmin-password ${RI-standard-password-for- Maxadmin's associated password which is


ICD} used for authentication purposes.
Referenced by the RI-standard-
password-for-ICD property.
Default setting is being used only for
demo purposes.
In production environments, this value
must be changed.

SCCD-maxreg-user-name maxreg Maximo system registration user.

SCCD-maxreg-password ${RI-standard-password-for- Maxreg's associated password which is


ICD} used for authentication purposes.

Referenced by the RI-standard-


password-for-ICD property.
Default setting is being used only for
demo purposes.
In production environments, this value
must be changed.

SCCD-mxintadm-user-name Mxintadm Maximo system integration user.

SCCD-mxintadm-password ${RI-standard-password-for- Mxintadm's associated password which is


ICD} used for authentication purposes.
Referenced by the RI-standard-
password-for-ICD property.
Default setting is being used only for
demo purposes.
In production environments, this value
must be changed.

RI-icd-admin-email n/a Administrator's email account for


notifications. No default value
If it's required to receive system
notification this setting must be set.

RI-icd-smtp-host n/a SMTP server which allows to receive


messages for administrator's email
account

RI-icd-additional-languages n/a Additional language pack which are going


to be installed in this step.
By default, no additional languages are
installed.

Cluster configuration properties:


Property Default Value Description
RI-cluster-appname-ui MAXIMO_UI User Interface application which
allows to use ICD via web
browser.

PAGE 29
RI-cluster-appname-int MAXIMO_INT Integration application which
allows to integrate ICD with other
systems.

RI-cluster-appname-cron MAXIMO_CRON Cron application is task scheduler


designed to manage jobs and
launch them at proper time.

RI-cluster-appname-bros MAXIMO_BROS BIRT Report Only Server (BROS)


application is being used for
report generation.

Output After successful installation ICD is installed to the installation directory. Database is
being updated which might take some time(up to 4 hours). It is advised to run this
step with tools such as Linux screen or tmux. In the process of updating database,
schema and tables and relations are created.
After completing this step ICD is prepared for installation QuickStart 7.0 packages.

Step 11 – ICD 7.6.0.1 – QS 7.1


Name of the step RI-Step11-ICD7601-QS71.props
Pre-requisites Step 10
Description This step has been designed to upgrade ICD version 7.6.0.0 to ICD version 7.6.0.1.
This step must be launched on host on which WAS with Deployment Manager has
been installed and configured.
Before launching this step, proper software packages must be downloaded from IBM
official repositories.
Required files IBM Control Desk
Multiplatform icd_7.6.0_part1_spm.zip
AIX icd_7.6.0_part2_aix.zip
Linux icd_7.6.0_part2_linux64.zip
Installation Manager
AIX agent.installer.aix.gtk.ppc_1.7.3000.20140521_1925.zip
Linux agent.installer.linux.gtk.x86_64_1.7.3000.20140521_1925.zip
Configuration Property Default Value Description
ICD-installation-dir /usr/IBM/SMP Installation path for the ICD

Output After successful completion of this step ICD has been upgraded to version 7.6.0.1 and
is ready to apply QuickStart 7.1 packages.
Proper update of the database has been performed.
Like in previous step, it's advised to use tools such as "Linux screen or tmux" while
executing this step.

PAGE 30
Step 12 – ICD 7.6.0.2 – QS 7.2
Name of the step RI-Step12-ICD7602-QS73.props
Pre-requisites Step 11
Description This step has been designed to upgrade ICD version 7.6.0.1 to ICD version 7.6.0.2.
This step must be launched on host on which WAS with Deployment Manager has
been installed and configured.
Before launching this step, proper software packages must be downloaded from IBM
official repositories.
Required files IBM Control Desk
Multiplatform icd_7.6.0_part1_spm.zip
AIX icd_7.6.0_part2_aix.zip
Linux icd_7.6.0_part2_linux64.zip
Installation Manager
AIX agent.installer.aix.gtk.ppc_1.7.3000.20140521_1925.zip
Linux agent.installer.linux.gtk.x86_64_1.7.3000.20140521_1925.zip
Configuration Property Default Value Description
ICD-installation-dir /usr/IBM/SMP Installation path for the ICD

Output After successful completion of this step ICD has been upgraded to version 7.6.0.2 and
is ready to apply QuickStart 7.2 packages.
Proper update of the database has been performed.
Like in previous step, it's advised to use tools such as "Linux screen or tmux" while
executing this step.

Step 13 – ICD build and deploy


Name of the step RI-Step13-ICD-Build-and-Deploy.props
Pre-requisites Steps 1-12
Description If you choose to install single JVM then only maximo.ear will be build and after that
deployment process begin. For cluster environment, additional ear files will be
appropriately built. For more information how split maximo and scenario examples
see WebSphere configuration chapter.
Installation for each ear takes approximately 45 minutes.
Required files N/A
Configuration N/A
Output After this step finish ICD is ready to work.

PAGE 31
Appendix A: RI-Values.props
Property Default Value Description
Common
RI-Cluster-environment false This variable determines if the
application will be in tiny or clustered
environment.
By default, non-clustered environment
is set.
DB2
DB-hostname db2.local Hostname on which DB2 engine is
installed. In clustered environment
connectivity is required between
hosts.
DB-installation-dir /opt/IBM/db2 Installation directory at which DB2 is
installed.
DB2 ICD Configuration
DB-maximo-instance-user db2sbysa Instance owner. User authenticated at
OS level. It's used to manage ICD
database.
This user ID controls all DB2
processes and owns all filesystems
and devices used by the databases
contained within the instance.
DB-maximo-instance-user-password ${RI-standard-password} Instance user's password. For demo
purposes, standard password is being
used which is resolved to "abcd1234".
In production environments, this value
must be changed.
DB-maximo-instance-user-main-group db2iadm2 Instance user's primary group.
DB-maximo-instance-user-home-dir /home/db2sbysa Instance user's home directory.
DB-maximo-instance-user-syscontrol- db2ictl1 Syscontrol group is responsible for
grp maintaining permissions in ICD
application. In details, it is highest
level of system control authority.
Provides the ability to perform
maintenance and utility operations
against the database manager
instance and its databases. Does not
allow direct access to data in the
databases. Has the implicit privilege to
connect to a database and can
perform the functions of users with
SYSMAINT and SYSMON authority.
Designed for users administering a
database manager instance containing
sensitive data
DB-maximo-instance-user-port 51000 Variable indicates on which port ICD
database will be available.
DB-fenc1-user db2fenc1 Fence user authenticated at OS level.
It is used to run user defined

PAGE 32
functions (UDFs) and stored
procedures outside of the address
space used by the DB2 database
DB-fenc1-user-password ${RI-standard-password} Fence user's password. For demo
purposes, standard password is being
used which is resolved to "abcd1234".
In production environments, this value
must be changed.
DB-fenc1-user-main-group db2fadm1 Fence user's primary group.
DB-fenc1-user-home-dir /home/db2fenc1 Fence user's home directory.
DB-fenc1-user-port 60000 Fence user port for ICD instance tells
on which port this user should
connect.
DB-maximo-database-name maximo The name of the ICD database.
DB-maximo-schem maximo Schema name for the ICD database
DB-maximo-tablespace-data MAXDATA Data table space name.
DB-maximo-tablespace-index MAXINDX Index table space name.
DB-maximo-tablespace-temp MAXTEMP DB2's System Temporary Tablespace
that can be used to support Maximo
application.
DB-maximo-tablespace-syscatspace SYSCATSCPACE SYSCATSPACE name in DB2. The
catalog table space holds the system
catalog tables.
DB-maximo-tablespace-userspace userspace A user table space name for ICD
which contains user-defined tables.
DB-maximo-tablespace- tempspace User temporary table spaces name
tempuserspace which holds temporary data from
tables created with a DECLARE
GLOBAL TEMPORARY TABLE or
CREATE GLOBAL TEMPORARY TABLE
statement.
DB-maximo-user maximo Maximo database user authenticated
at OS level. Allows to connect to the
database and perform actions.
DB-maximo-user-password ${RI-standard-password} Maximo user's password. For demo
purposes, standard password is being
used which is resolved to "abcd1234".
In production environments, this value
must be changed.
DB-maximo_user-main-group db2iadm2 Primary group for Maximo user.
DB-maximo-user-home-dir /home/maximo User's home directory.
DB-maximo-instance-root-dir /home/db2sbysa ICD instance directory indicates the
path to database files.
DB-maximo-instance-data-dir /home/db2sbysa/db2data ICD's data directory indicates where
DB2 will store ICD database files.
DB-maximo-instance-logs-dir /home/db2sbysa/logs ICD's logs directory indicates where
DB2 will store log files.

PAGE 33
DB-maximo-instance-backups-dir /db2backups ICD's backup directory indicates
where DB2 will keep ICD's backup
files.
DB-maximo-instance-archlogs-dir /home/db2sbysa/archlogs ICD's archive logs directory. Indicates
where DB2 keeps logs used to track
changes between backups.
DB-maximo-instance-dump-dir /home/db2sbysa/dump ICD's dump directory. Indicates where
DB2 stores error tracking logs.
DB2 LDAP Configuration
DB-ldap-instance-user idsccmdb Instance owner. User authenticated at
OS level. It's used to manage
LDAP/SDS database. This user ID
controls all DB2 processes and owns
all filesystems and devices used by
the databases contained within the
instance.
DB-ldap-instance-user-password ${RI-standard-password} Instance user's password. For demo
purposes, standard password is being
used which is resolved to "abcd1234".
In production environments, this value
must be changed.
DB-ldap-instance-user-main-group db2iadm1 Instance user's primary group.
DB-ldap-instance-user-additional- db2iadm1 Additional groups membership for the
groups instance user. If the main and
additional groups names are the
same, it means that there are no
additional groups for this user.
DB-ldap-instance-user-home-dir /home/idsccmdb Instance user's home directory.
DB-ldap-instance-user-syscontrol-grp db2ictl1 Syscontrol group is responsible for
maintaining permissions in SDS
database. In details, it is highest level
of system control authority. Provides
the ability to perform maintenance
and utility operations against the
database manager instance and its
databases. Does not allow direct
access to data in the databases. Has
the implicit privilege to connect to a
database and can perform the
functions of users with SYSMAINT and
SYSMON authority. Designed for users
administering a database manager
instance containing sensitive data
DB-ldap-instance-user-port 50000 Variable indicates on which port SDS's
database will be available.
DB-fenc2-user db2fenc2 Fence user authenticated at OS level
for SDS database. It is used to run
user defined functions (UDFs) and
stored procedures outside of the
address space used by the DB2
database

PAGE 34
DB-fenc2-user-password ${RI-standard-password} Fence user's password. For demo
purposes, standard password is being
used which is resolved to "abcd1234".
In production environments, this value
must be changed.
DB-fenc2-user-home-dir /home/db2fenc2 Fence user's home directory.
DB-fenc2-user-main-group db2fadm1 Fence user's primary group.
DB-fenc2-user-port 61000 Fence user port for SDS instance tells
on which port this user should
connect.
SDS-ldap-db-name ldapdb2 SDS's database name
DB-ldap-instance-root-dir /home/idsccmdb SDS instance directory indicates the
path to database files.
DB-ldap-instance-data-dir /home/idsccmdb/db2data SDS's data directory indicates where
DB2 will store SDS database files.
DB-ldap-instance-logs-dir /home/idsccmdb/logs SDS's logs directory indicates where
DB2 will store log files.
DB-ldap-instance-backups-dir /home/idsccmdb/backups SDS's backup directory indicates
where DB2 will keep ICD's backup
files.
DB-ldap-instance-archlogs-dir /home/idsccmdb/archlogs SDS's archive logs directory. Indicates
where DB2 keeps logs used to track
changes between backups.
DB-ldap-instance-dump-dir /home/idsccmdb/dump SDS's dump directory. Indicates where
DB2 stores error tracking logs.
LDAP
DB-ldap-user ldapusr SDS user which allows to connect to
SDS database. Authenticated at OS
level.
DB-ldap-user-password ${RI-standard-password} User's password. For demo purposes,
standard password is being used
which is resolved to "abcd1234". In
production environments, this value
must be changed.
DB-ldap-user-main-group db2iadm1 User's primary group.
DB-ldap-user-additional-groups idsldap User's additional group membership
which means that user "ldapusr" is in
"db2iadm1" and "idsldap" group.
DB-ldap-user-home-dir /usr/IBM/ldap User's home directory.
SDS-ldap-hostname ldap.local SDS hostname on which SDS service
is running. In clustered environment
connectivity between nodes is
required.
SDS-ldap-bind cn=root It is the distinguished name that binds
to the LDAP directory.
SDS-ldap-bindPwd ${RI-standard-password} Associated password for demo
purposes standard password is being
used which is resolved to "abcd1234".

PAGE 35
In production environments, this value
must be changed.
SDS-ldap-base-entry ou=SWG,o=IBM,c=US Base entry under which users will be
written to the SDS database.
SDS-ldap-ldapEncrpt custEncSeed08 SDS encryption passphrase
SDS-ldap-ldapSALT custEncSalt8 SDS salt passphrase
SDS-ldap-port 389 SDS service port number.
SDS-ldap-ssl-port 646 SDS secured service port number.
WebSphere Application Server
RI-was-user wasadmin Administrative user account created at
OS level.
RI-was-user-password ${RI-standard-password} User's associated password which is
used for authentication purposes.
${RI-standard-password} variable is
resolved to abcd1234 which is only for
demo purposes. In production
environments, this value must be
changed.
RI-was-user-main-group wasadmin Primary group for the Websphere
administrative account.
RI-was-user-additional- wasadmin Additional groups membership for the
groups Websphere administrative account If
the main and additional groups names
are the same, it means that there is
no additional groups for this user.
RI-was-user-home-dir /home/wasadmin Home directory for the Websphere
administrative account
RI-was-installation-dir /usr/IBM/WebSphere/AppServer Installation directory of the
WebSphere Application Server.
WAS-dmgr-name Dmgr This variable indicates of the profile
name which is being created in the
configuration step.
WAS-dmgr-node-name maximo-dmgr Value of this setting determines the
name of the node which is correlated
with Deployment Manager profile.
WAS-dmgr-cell-name maximo-dmgr This setting sets up the cell name for
Deployment Manager.
WAS-dmgr-hostname dmgr.local Hostname on which the RI-Step05-
WebSphere-Install step has been
performed. Allowed values are FQDN
and/or names resolved local (e.g. via
hosts file). This hostname will be used
in next steps to provide connectivity
between other components. In cluster
environment, other machines must
resolve this hostname as well.

PAGE 36
WAS-node-cell-name maximo-node Temporarily cell name to which the
node is added before federating it to
Deployment manager.
WAS-dmgr-port 9043 WebSphere Administration console
port setting indicates on which port
Deployment Manager is listening. This
value determines what port must be
entered in URL when accessing
administration console via web
browser. Typical URL is as follows
https://<WAS-dmgr-
hostname>:<WAS-dmgr-
port>/ibm/console/
(e.g.
https://dmgr.local:9043/ibm/console)
WAS-current-node Node1 Determines which JVM block is
considered.
WAS-cluster-UI-name MXCluster UI cluster name which is going to be
created if clustered environment is
chosen.
WAS-cluster-INT-name INTCluster Integration cluster name which is
going to be created if clustered
environment is chosen.
WAS-cluster-CRON-name CronCluster Cron cluster name which is going to
be created if clustered environment is
chosen
WAS-cluster-BROS-name BROSCluster Reporting cluster name which is going
to be created if clustered environment
is chosen
WAS-jvm-UI UIServer UI application server name. Servers
are created with names starting with
this value and numbered
incrementally.
WAS-jvm-INT IntServer Integration application server name.
Servers are created with names
starting with this value and numbered
incrementally.
WAS-jvm-CRON CronServer Cron application server name. Servers
are created with names starting with
this value and numbered
incrementally.
WAS-jvm-BROS BrosServer BROS application server name.
Servers are created with names
starting with this value and numbered
incrementally.
WAS-jvm-Tiny MXServer Name of the application server in tiny
configuration. There is only one
application server named by the value
of this variable.
WAS-node-jvms-Node1-UI 0 Number of UI application servers
which is being created on Node1.

PAGE 37
WAS-node-jvms-Node1-INT 0 Number of Integration application
servers which is being created on
Node1.
WAS-node-jvms-Node1-CRON 0 Number of Cron application servers
which is being created on Node1.
WAS-node-jvms-Node1-BROS 0 Number of BROS application servers
which is being created on Node1.
WAS-node-jvms-Node1-Tiny 1 Indicates if Tiny application server is
going to be created or not. Value 0
Removes application server from
Node1. Every positive value creates
exactly one application server.
WAS-Node1-name Maximo This variable determines the name of
the profile on "Node1". When planning
cluster configuration. This variable is
also copied and "Node1" is replaced to
next node. For instance, when making
configuration for node2 variable would
look like this: WAS-Node2-
name=Maximo
WAS-Node1-node-name maximo-${WAS-Node1-name}-${WAS- This variable defines the node name
Node1-hostname} which will be configured and
federated with Dmgr. In similar
manner, as before "Node1" must be
replaced with proper value. For
instance, when making configuration
for node2 variable would look like
this: WAS-Node2-node-
name=maximo-${WAS-Node2-name}-
${WAS-Node2-hostname}
WAS-Node1-hostname node1.local This variable determines the
hostname on which we are running
Rapid Installer. Like in previous cases
it has to be FQDN or locally resolved
name. Also, communication between
Dmgr and this node has to be
present. In similar way as previously
when configuring it for next node
"Node1" has to be replaced with
proper node. For instance, when
making configuration for node2
variable would look like this: WAS-
Node2-hostname=node2.local
Please notice that "Node1" has been
changed to "Node2". Value has been
adjusted to situation and value is
node2.local
IBM HTTP Server
IHS-admin-username ihsadmin Administrative user account which is
created at OS level. Allows to
managed the http server locally
and/or remotely.

PAGE 38
IHS-admin-password abcd1234 User's associated password which is
used for authentication purposes. By
default, abcd1234 is being used which
is only for demo purposes. In
production environments, this value
must be changed.
IHS-admin-user-home-dir /home/ihsadmin Home directory for the IBM HTTP
Server administrative account
IHS-admin-user-main-group ihsadmin Primary group for the IBM HTTP
Server administrative account.
IHS-admin-user-additional-groups ihsadmin Additional groups membership for the
IBM HTTP Server administrative
account If the main and additional
groups names are the same, it means
that there is no additional groups for
this user.
RI-ihs-installation-dir /usr/IBM/HTTPServer Installation directory of the IHS.
RI-ihs-plugin-installation-dir /usr/IBM/WebSphere/Plugins Installation directory for IHS Plugin.
IHS-node1-http-port 80 Port number under which the http
service is available. By default,
standard 80 port is being configured.
IHS-node1-admin-port 8008 Administrative port which allows to
configure and control IHS. This
functionality allows to locally or
remotely change server's settings. For
authentication IHS-admin-username
and IHS-admin-password variables
values are used.
IHS-hostname ihs.local This variable determines the
hostname on which the IHS server is
installed. Like in previous cases it has
to be FQDN or locally resolved name.
In cluster environment connectivity
between this host and other hosts
must be working. If installing more
than one IHS server this value must
be changed before running this step
on another node.
IHS-webserver-name ihs-01 The name of the IHS server which will
be present in WAS Administrative
console under server’s section. When
installing more than one IHS server
this value must be changed before
running this step on another node.
IHS-node-name WebServerNode1 It's the name of the unmanaged node
which is going to be added to the
WAS. When installing more than one
IHS server this value must be
changed before running this step on
another node.
IHS-logs ${RI-ihs-installation-dir}/logs This variable determines the logs
directory which is being set while

PAGE 39
configuring IHS. Default value is
resolved to /usr/IBM/HTTPServer/logs
when taking into account initial
settings.
IBM Control Desk
ICD-installation-dir /usr/IBM/SMP Installation directory where the
package is going to be placed.
SCCD-maxadmin-user-name maxadmin Administrative account for Maximo.
The product administrator user that is
used for initial configuration and for
adding users.
SCCD-maxadmin-password ${RI-standard-password-for-ICD} Maxadmin's associated password
which is used for authentication
purposes. RI-standard-password-for-
ICD variable has default value of
"kyJ.f~f.2". Default setting is being
used only for demo purposes. In
production environments, this value
must be changed.
SCCD-maxreg-user-name maxreg Maximo system registration user. The
user that is used for the self-
registration of users.
SCCD-maxreg-password ${RI-standard-password-for-ICD} Maxreg's associated password which
is used for authentication purposes.
RI-standard-password-for-ICD
variable has default value of
"kyJ.f~f.2". Default setting is being
used only for demo purposes. In
production environment this value
must be changed.
SCCD-mxintadm-user-name mxintadm Maximo system integration user. The
user that is used with enterprise
adapters
SCCD-mxintadm-password ${RI-standard-password-for-ICD} Mxintadm's associated password
which is used for authentication
purposes. RI-standard-password-for-
ICD variable has default value of
"kyJ.f~f.2". Default setting is being
used only for demo purposes. In
production environment this value
must be changed.
RI-icd-admin-email No default value Administrator's email account for
notifications. By default, there is no
value set. If it's required to receive
system notification this setting must
be set.
RI-icd-smtp-host No default value SMTP server which allows to receive
messages for administrator's email
account
RI-icd-additional-languages No default value Additional language pack which are
going to be installed in this step. By
default, no additional languages are

PAGE 40
installed. If it's required to install
additional language pack this setting
must be set.
RI-cluster-appname-ui MAXIMO_UI User Interface application which
allows to use ICD via web browser.
RI-cluster-appname-int MAXIMO_INT Integration application which allows to
integrate ICD with other systems.
RI-cluster-appname-cron MAXIMO_CRON Cron application is task scheduler
designed to manage jobs and launch
them at proper time.
RI-cluster-appname-bros MAXIMO_BROS BIRT Report Only Server (BROS)
application is being used for report
generation.
Installation Manager
IM-installation-path /opt/IBM/InstallationManager Installation Manager install directory.
IM-IMS-path /opt/IBM/IMShared Installation MAnager shared directory
path.
Miscalaneous
RI-create-missing-os-configuration true OS configuration automatization. If
set to 'true' Rapid Installer will check
if all users, directories and privileges
are set correctly and fix if necessary.
If set to 'false' Rapid Installer will just
check configuration and show errors.
RI-standard-password abcd1234 Default password for demo purposes.
In production environment, users such
as wasadmin, ihsadmin,dbsbysa etc.
must be changed.
RI-standard-password-for-ICD kyJ.f~f.2 Default password for demo purposes
for ICD application. In production
environment maxadmin's, maxreg's
and maxint's password must be
changed.

PAGE 41
Appendix B: SPiN manual
First action which is required to launch RI® is installing Java® Runtime Environment. Currently the minimum
version of the JRE is 1.7.
When Java® is successfully installed, download, and unpack RI zip file. Standard path for the RI is /usr/spin
Change your path to newly created folder and invoke command ./menu.sh – then you should see RI main
menu
#> cd /usr/spin/spinPackage
#> ./menu.sh
Step number Step name
1 custom-spin/RI-Step01-DB2-Install.props
2 custom-spin/RI-Step02-DB2-Configure-Maximo.props
3 custom-spin/RI-Step03-SDS-Install.props
4 custom-spin/RI-Step04-SDS-Configure.props
5 custom-spin/RI-Step05-WebSphere-Install.props
6 custom-spin/RI-Step06-IHS-Install.props
7 custom-spin/RI-Step07-WebSphere-Configure-Dmgr.props
8 custom-spin/RI-Step08-WebSphere-Configure-Maximo.props
9 custom-spin/RI-Step09-IHS-Configure.props
10 custom-spin/RI-Step10-ICD7600-QS70.props
11 custom-spin/RI-Step11-ICD7601-QS71.props
12 custom-spin/RI-Step12-ICD7602-QS73.props
13 custom-spin/RI-Step14-ICD-Build-and-Deploy.props
To choose the step we want to run just simply enter its number, which can be found on the left-hand side of
the steps section. After inserting it hit enter which should launch desired step.
Welcome to Simple Product Installer (SPIN) :-)
cwd: /usr/spin/spinPackage
Script: custom-spin/RI-Step01-DB2-Install.props
Version: Version 2.3.0, 20120723 Jul 23, 11:11AM
Initialization: Read 8 script files in 80 ms.
Report file: custom-spin/report/RI-Step01-DB2-Install-111f49449eac-report-20170510-Wed-12-
18-23.txt
Spin file: custom-spin/RI-Step01-DB2-Install.props

1 - Check run

PAGE 42
2 - list files to unpack
3 - run Spin
4 - Display current step name in checkpoint file
5 - Set step name in checkpoint file
6 - Clear checkpoint file
r - Reload file(s)
p - previous menu
x - exit

There is some useful information on the header of the each step:


• cwd – current working directory. It tells where the SPiN® is located.
• Report file – location of the report file. It contains full output for each step.
At the bottom of the screen there is a menu that allows to control SPiN®:
1. Check run – basic configuration validation
2. List files to unpack – shows a list of required files
3. Run Spin – executes the sub step
4. Display current step name in checkpoint file – prints the checkpoint – latest sub step that was
finished successfully
5. Set step name in checkpoint file – Allows to manually set the checkpoint
6. Clear checkpoint file – Clear the checkpoint which – useful in case of a need to restart the step from
the beginning
7. Reload file(s) – Reloads property files and clears last error message
8. Previous menu – Back to the main menu
9. Exit – exits SPiN®
Important: Some steps such as profile creation or ICD configuration should be run once. Repeating those
steps several times might cause configuration failure.
Activities which are logically consistent are gathered into a single step.
For instance, all required actions which are needed to install IBM DB2 Server® are gathered into “custom-
spin/RI-Step01-DB2-Install.props”. After successfully completing this step thus db2 engine is installed on the
machine.
Checkpoint are files which store information regarding last executed sub step of the main step.
For instance, if step 1 ("custom-spin/RI-Step01-DB2-Install.props") was chosen, checkpoint might indicate
that the last step which was executed is:
"Last executed step is db2-600-prepare-files-check.
Spin file: custom-spin/RI-Step01-DB2-Install.props".
Also, information regarding the file location is displayed. In a given example it is:
"Report file: custom-spin/report/RI-Step01-DB2-Install-111f49449eac-report-20170510-Wed-12-18-23.txt"

PAGE 43
Appendix C: Required software packages
Passport Advantage

IBM DB2 Activation

IBM DB2 ESE Restricted Use, Quick Start and Activation V10.5 for Linux, UNIX
All platforms CIK0LML
and Windows Multilingual

IBM Security Directory Server V6.4

IBM Security Directory Server V6.4 Client-Server ISO with entitlement for AIX
AIX CN47GML
Multilingual

IBM Security Directory Server V6.4 Client-Server ISO with entitlement for Linux
Linux x86_64 CN47MML
x86-64 Multilingual

IBM WebSphere Application Server Network Deployment V8.5.5

IBM WebSphere Application Server Network Deployment V8.5.5 (1 of 3) for


CIK2HML
Multiplatform Multilingual

IBM WebSphere Application Server Network Deployment V8.5.5 (2 of 3) for


All platforms CIK2IML
Multiplatform Multilingual

IBM WebSphere Application Server Network Deployment V8.5.5 (3 of 3) for


CIK2JML
Multiplatform Multilingual

IBM WebSphere Application Server V8.5.5 Supplements

IBM WebSphere Application Server V8.5.5 Supplements (1 of 3) for Multiplatform


CIK1VML
Multilingual

IBM WebSphere Application Server V8.5.5 Supplements (2 of 3) for Multiplatform


All platforms CIK1WML
Multilingual

IBM WebSphere Application Server V8.5.5 Supplements (3 of 3) for Multiplatform


CIK1XML
Multilingual

IBM WebSphere SDK Java (TM) Technology Edition V7.0

IBM WebSphere SDK Java (TM) Technology Edition V7.0 (1 of 3) (for full profile
All platforms and Liberty profile WebSphere Application Server V8.5.5) Multiplatform CIUC7ML
Multilingual

PAGE 44
IBM WebSphere SDK Java (TM) Technology Edition V7.0 (2 of 3) (for full profile
and Liberty profile WebSphere Application Server V8.5.5) Multiplatform CIUC8ML
Multilingual

IBM WebSphere SDK Java (TM) Technology Edition V7.0 (3 of 3) (for full profile
and Liberty profile WebSphere Application Server V8.5.5) Multiplatform CIUC9ML
Multilingual

IBM Control Desk Service Provider Edition V7.6.0

IBM Control Desk Service Provider Edition V7.6.0 part 1 of 2 for Multiplatform
CN66DML
Multilingual
All platforms
IBM Control Desk Service Provider Edition V7.6.0 part 2 of 2 for Multiplatform
CN66EML
Multilingual

IBM Fix Central

IBM Control Desk Service Provider Edition V7.6.0.1

AIX 7.6.0.1-TIV-ICD-AIX-FP0001
Linux x86_64 7.6.0.1-TIV-ICD-Linux-FP0001

IBM Control Desk Service Provider Edition V7.6.0.2


AIX 7.6.0.2-TIV-ICD-AIX-FP0002
Linux x86_64 7.6.0.2-TIV-ICD-Linux-FP0002

DB2 V10.5.0.8
AIX DB2-aix64-server_t-10.5.0.8-FP008
Linux x86_64 DB2-linuxx64-server_t-10.5.0.8-FP008

IBM Security Directory Server V6.4.0.11


6.4.0.11-ISS-ISDS-AIX-IF0011
AIX 6.0.16.26-ISS-JAVA-AIX-FP0026
8.0.50.71-ISS-GSKIT-AIX-FP0071
6.4.0.11-ISS-ISDS-LinuxX64-IF0011
Linux x86_64 6.0.16.26-ISS-JAVA-LinuxX64-FP0026
8.0.50.71-ISS-GSKIT-LinuxX64-FP0071

IBM WebSphere Application Server Network Deployment V8.5.5.11


8.5.5-WS-WAS-FP011-part1
All platforms
8.5.5-WS-WAS-FP011-part2

PAGE 45
8.5.5-WS-WAS-FP011-part3

IBM WebSphere Application Server V8.5.5.11 Supplements


8.5.5-WS-WASSupplements-FP011-part1
All platforms 8.5.5-WS-WASSupplements-FP011-part2
8.5.5-WS-WASSupplements-FP011-part3

IBM Installation Manager V1.7.3


AIX 1.7.3.0-IBMIM-AIX-20140521_1925
Linux x86_64 1.7.3.0-IBMIM-LINUX-X86_64-20140521_1925

PAGE 46
Appendix D: Installation packages paths
DB2 V10.5.0.8

Path /usr/spin/spinPackage/spin/software/db2
10.5fp8_[OS]_server_t.tar.gz
Files
DB2_ESE_Restricted_QS_Act_V10.5.zip

IBM Security Directory Server V6.4.0.11


Path /usr/spin/spinPackage/spin/software/sds
6.0.16.26-ISS-JAVA-[OS]-FP0026.tar
6.4.0.11-ISS-ISDS-[OS]-IF0011.tar.gz
Files
8.0.50.71-ISS-GSKIT-[OS]-FP0071.tar.gz
sds64-[OS].iso

IBM WebSphere Application Server Network Deployment V8.5.5.11


Path /usr/spin/spinPackage/spin/software/was
8.5.5-WS-WAS-FP011-part1.zip
8.5.5-WS-WAS-FP011-part2.zip
WASND_v8.5.5_1of3.zip
WASND_v8.5.5_2of3.zip
Files
WASND_v8.5.5_3of3.zip
WS_SDK_JAVA_TEV7.0_1OF3_WAS_8.5.5.zip
WS_SDK_JAVA_TEV7.0_2OF3_WAS_8.5.5.zip
WS_SDK_JAVA_TEV7.0_3OF3_WAS_8.5.5.zip

IBM WebSphere Application Server V8.5.5.11 Supplements


Path /usr/spin/spinPackage/spin/software/ihs
8.5.5-WS-WASSupplements-FP011-part1.zip
8.5.5-WS-WASSupplements-FP011-part2.zip
8.5.5-WS-WASSupplements-FP011-part3.zip
Files
WAS_V8.5.5_SUPPL_1_OF_3.zip
WAS_V8.5.5_SUPPL_2_OF_3.zip
WAS_V8.5.5_SUPPL_3_OF_3.zip

IBM Installation Manager V1.7.3


Path /usr/spin/spinPackage/spin/software/im

PAGE 47
Files agent.installer.[OS]_1.7.3000.20140521_1925.zip

IBM Control Desk Service Provider Edition V7.6.0.0


Path /usr/spin/spinPackage/spin/software/icd
CD_SP_Ed_V760_1of2_Mltptfm.tar
Files
CD_SP_Ed_V760_2of2_Mltptfm.tar

IBM Control Desk Service Provider Edition V7.6.0.1


Path /usr/spin/spinPackage/spin/software/icd/7601
icd_7.6.0_part1_spm.zip
Files
icd_7.6.0_part2_[OS].zip

IBM Control Desk Service Provider Edition V7.6.0.2


Path /usr/spin/spinPackage/spin/software/icd/7602
icd_7.6.0_part1_spm.zip
Files
icd_7.6.0_part2_[OS].zip

Appendix E: Recommended folders size

Mount points on operating system

Partition Size[GB] Comments

/opt/IBM/db2 5 Db2 path

Default rapid installer path. All installation files are


/usr/spin 20 extracted under expandArea folder inside Rapid installer.
Rapid installer can be removed after installation.

/tmp 5

/home/db2sbysa 20 Maximo database path, can grow in time

/home/idsccmdb 1.5 Ldap database path

PAGE 48
15Gb for tiny environment and 1GB for each additional JVM
/usr/IBM/WebSphere/AppServer 15+
in cluster environment.

/opt/ibm/ldap/V6.4 1 Linux path for sds installation

/opt/IBM/ldap/V6.4 1 AIX path for sds installation

/usr/IBM/HTTPServer 1

This size depends from version of ICD and from cluster


/usr/IBM/SMP 20/25 configuration. At least 20GB recommended for tiny
installation, 25GB for cluster environment.

PAGE 49