IBM SmartCloud Control Desk

Version 7 Release 5.1

Installation Guide
(IBM WebSphere)


 Note
Before using this information and the product it supports, read the information in “Notices” on page 305.
Contents
Chapter 1. Preparing for installation . . 1
Before you begin . . . . . . . . . . . . . 1
Programmatically verifying prerequisites . . . . 2
Checking port availability . . . . . . . . . 7
Accessing system directories . . . . . . . . 7
AIX and HP-UX tar command requirements . . . 8
AIX font requirements . . . . . . . . . . 8
Increasing AIX file size and number of descriptors 8
Increasing AIX paging space . . . . . . . . 9
Verifying large page size support for AIX . . . 10
Enabling asynchronous I/O on AIX . . . . . 10
Checking for required libraries on Linux. . . . 11
Configuring the JRE in Linux . . . . . . . 11
Setting the ulimit . . . . . . . . . . . 12
Setting the swap size . . . . . . . . . . 12
Setting shared memory . . . . . . . . . 12
Remote configuration enablement . . . . . . 13
Enabling SSL client authentication . . . . . . 14
System password policy settings . . . . . . 15
Backing up the Deployment Engine database . . 15
Specifying host name values. . . . . . . . 16
Establishing a fully qualified host name on
Windows systems . . . . . . . . . . 16
Forcing the middleware installer to use
alphanumeric hostnames . . . . . . . . 16
Enabling full text search for IBM DB2 . . . . 17
Launchpad . . . . . . . . . . . . . . 17
Starting the launchpad . . . . . . . . . 17
Chapter 2. Deploy with automatic
middleware configuration. . . . . . . 19
Middleware installation program middleware
deployment plan overview . . . . . . . . .
Installing middleware using the middleware
installation program . . . . . . . . . . .
Middleware installation program logs . . . .
Middleware installation program log reference
Configuring IBM Tivoli Directory Server user and
group strings . . . . . . . . . . . . .
Configuring SSL between Microsoft Active
Directory and WebSphere Application Server
Network Deployment . . . . . . . . . .
Uninstalling middleware . . . . . . . . . .
Reinstalling middleware with IBM DB2 . . . . .
Installation program overview . . . . . . . .
Simple installation path values . . . . . . .
Installing the product and automatically
configuring middleware . . . . . . . . .
Installing optional content . . . . . . . .
Installing optional integration modules . . . .
Language deployment after database update
deferral . . . . . . . . . . . . . . . .
Manually deploying languages after database
update deferral . . . . . . . . . . . .
© Copyright IBM Corp. 2012
Chapter 3. Deploying automatically
reusing existing middleware . . . . . 53
Run the middleware installation program on
existing middleware servers . . . . . . . . . 53
Configuring an existing DB2 with the
middleware installation program . . . . . . 55
Verifying an existing IBM Tivoli Directory Server
using the middleware installer . . . . . . . 57
Preparing Microsoft Active Directory for reuse . 58
Installation program overview . . . . . . . . 60
Simple installation path values . . . . . . . 61
Installing the product and automatically
configuring middleware . . . . . . . . . 63
Installing optional content . . . . . . . . 69
Installing optional integration modules . . . . 69
Language deployment after database update
deferral . . . . . . . . . . . . . . . . 70
Manually deploying languages after database
update deferral . . . . . . . . . . . . 70
Chapter 4. Deploying manually reusing
existing middleware . . . . . . . . . 73
SmartCloud Control Desk installation with manual
middleware configuration . . . . . . . . . 73
Manually configuring the database . . . . . 73
Manually configuring DB2 9.x . . . . . . 74
Manually configuring Oracle 11g . . . . . 76
Manually configuring Oracle 10g . . . . . 78
Manually configuring Microsoft SQL Server 80
Manually configuring the directory server . . . 83
Manually configuring IBM Tivoli Directory
Server . . . . . . . . . . . . . . 83
19 Manually configuring Microsoft Active
Directory . . . . . . . . . . . . . 87
19 Manually configuring the J2EE server . . . . 91
22 Manually configuring WebSphere Application
24 Server Network Deployment . . . . . . 91
Installing the product and manually configuring
34 middleware . . . . . . . . . . . . . . 133
Installing optional content . . . . . . . . . 139
Installing optional integration modules . . . . . 139
35 Language deployment after database update
39 deferral . . . . . . . . . . . . . . . 140
40 Manually deploying languages after database
41 update deferral . . . . . . . . . . . . 140
42
Chapter 5. Silent installation . . . . . 143
44
Installing SmartCloud Control Desk silently . . . 143
50
Silent installation properties . . . . . . . . 145
50
51
51
iii
Chapter 6. Programmatically verifying Create a general ledger account . . . . . . 207
that the installation was successful . . 171 Update General Ledger Component Type
Authorization . . . . . . . . . . . . 207
Update Company-Related Accounts . . . . . 207
Chapter 7. Verifying the installation Create default insert site. . . . . . . . . 208
manually . . . . . . . . . . . . . 177 Create worktypes . . . . . . . . . . . 208
Create a classification structure for IT assets . . 209
Chapter 8. Configuring the HTTPOnly Specify a top-level class for IT assets and
attribute. . . . . . . . . . . . . . 179 software . . . . . . . . . . . . . . 209
Signing out and signing in . . . . . . . . 210
Before working with BIRT reports . . . . . . 210
Chapter 9. Installing Integration
Generating xml request pages . . . . . . . . 211
Composer . . . . . . . . . . . . . 181 Synchronizing users and groups . . . . . . . 211
Integration Composer overview . . . . . . . 181 Understanding and configuring security . . . . 212
Hardware and software requirements . . . . . 182
Installation prerequisites. . . . . . . . . . 184
Chapter 13. Middleware clean up
Performing an Integration Composer installation 185
Installing Integration Composer using the scripts . . . . . . . . . . . . . . 213
Launchpad . . . . . . . . . . . . . 185 Using the middleware cleanup scripts . . . . . 213
Installing Integration Composer on UNIX
operating systems in console mode . . . . . 187 Chapter 14. Uninstalling the product 217
Performing an Integration Composer upgrade . . 189 Uninstalling an automatically configured
Upgrading Integration Composer using the deployment . . . . . . . . . . . . . . 217
Launchpad . . . . . . . . . . . . . 190 Running the product uninstallation program for
Upgrading Integration Composer on UNIX automatically configured middleware . . . . 218
operating systems in console mode . . . . . 191 Uninstalling a manually configured deployment 219
Confirming the installation . . . . . . . . . 192 Running the product uninstall program for
Post-installation tasks. . . . . . . . . . . 193 manually configured middleware. . . . . . 219
Verifying the settings in the Integration Database configuration recovery . . . . . . 220
Composer fusion.properties file . . . . . 193 Restoring the DB2 database server . . . . 220
Changing the memory allocation in the Restoring the Oracle database . . . . . . 221
startFusion file (optional) . . . . . . . . 195 Restoring the Microsoft SQL Server database 222
Changing the memory allocation in the Uninstalling the product without the uninstallation
executeMapping file (optional) . . . . . . . 195 program . . . . . . . . . . . . . . . 223
Uninstalling Integration Composer . . . . . . 196 Uninstall program recovery tool . . . . . . 223
Uninstalling Integration Composer on Windows Using the uninstallation program recovery
operating systems . . . . . . . . . . . 196 tool. . . . . . . . . . . . . . . 224
Uninstalling Integration Composer on UNIX Manual uninstallation . . . . . . . . . 227
operating systems . . . . . . . . . . . 197 Recovering WebSphere Application Server
configuration . . . . . . . . . . . 227
Chapter 10. Installing the Deployer's Removing files from the system . . . . . 230
Workbench . . . . . . . . . . . . 199
Chapter 15. Starting and stopping
Chapter 11. Installing IBM SmartCloud middleware . . . . . . . . . . . . 231
Control Desk Everyplace . . . . . . 201 Restarting middleware on Windows . . . . . . 231
Restarting middleware on UNIX . . . . . . . 232
Installing as part of a new product installation . . 201
Stopping middleware on Windows . . . . . . 233
Installing as part of a product upgrade . . . . . 202
Stopping middleware on Linux and AIX . . . . 234
Installing after SmartCloud Control Desk has been
installed . . . . . . . . . . . . . . . 202
Chapter 16. Process solution package
Chapter 12. Post installation tasks 203 installation methods . . . . . . . . 237
Accessing product documentation . . . . . . 203 Software life cycle operations . . . . . . . . 237
Initial data configuration . . . . . . . . . 203 Process solution packages . . . . . . . . . 238
Signing in using a default user ID . . . . . 203 Package types . . . . . . . . . . . . . 238
Configuring SMTP . . . . . . . . . . 204 Aggregation packages . . . . . . . . . . 239
Create currency codes . . . . . . . . . 205 Determining which process solution installation
Create item and company sets . . . . . . . 205 program to use . . . . . . . . . . . . . 239
Create an organization . . . . . . . . . 205 Supported operations for the process solution
Create a general ledger account component . . 206 installation programs . . . . . . . . . . . 240
Applying changes to the database . . . . . 206

iv IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Before using the process solution installation
programs . . . . . . . . . . . . . . . 241
Managing process solution deployment from the
administrative workstation . . . . . . . . . 241
Typical deployment operation . . . . . . . . 242
Selectable features . . . . . . . . . . . . 242
Deferring J2EE and database configuration . . . 247
Manually completing deployment . . . . . 248
Pre-deployment system check . . . . . . . . 249
Installing process managers using the process
solution installation wizard. . . . . . . . . 250
Process solution installation client command-line
interface . . . . . . . . . . . . . . . 252
Starting the process solution installation client
CLI. . . . . . . . . . . . . . . . 252
General syntax . . . . . . . . . . . 252
Perform action . . . . . . . . . . . 253
Summary of supported parameters . . . . 253
Process solution command-line interface
reference . . . . . . . . . . . . . . 255
install action - install\ a package . . . . . 255
modfeatures action - modify existing features
of a deployed package . . . . . . . . 256
Process solution installation logs . . . . . . . 257
Chapter 17. Advanced installation
topics. . . . . . . . . . . . . . . 261
WebSphere Application Server Network
Deployment management . . . . . . . . . 261
Starting the application server from the
command line . . . . . . . . . . . . 261
Starting the application server from the
administrative console . . . . . . . . . 262
Securing the WebSphere Application Server
Network Deployment administrative console . . 263
Configuring Windows services . . . . . . 264
Configuring the WebSphere Application
Server Network Deployment application
server to run as a Windows service . . . . 264
Changing the middleware installation program
configuration parameters . . . . . . . . . 265
Maintaining EAR files . . . . . . . . . . 266
Building EAR files. . . . . . . . . . . 267
Manually uninstalling applications from
WebSphere Application Server Network
Deployment . . . . . . . . . . . . . 267
Manually installing applications in WebSphere
Application Server Network Deployment . . . 267
Chapter 18. Middleware on Solaris
and HP-UX . . . . . . . . . . . . 269
Operating system preparation . . . . . . . . 269
Middleware installation on Solaris . . . . . 269
HP-UX . . . . . . . . . . . . . . 269
Installing the components . . . . . . . . . 270
Installing DB2 . . . . . . . . . . . . 270
Installing IBM Tivoli Directory Server on Solaris 272
Installing WebSphere Application Server
Network Deployment . . . . . . . . . 273
Creating WebSphere Application Server
Network Deployment profiles . . . . . . 274
Manually configuring Virtual Member
Manager on WebSphere Application Server
Network Deployment . . . . . . . . 276
Installing the WebSphere update installer . . 280
Installing and configuring IBM HTTP Server 280
Installing the WebSphere plug-in . . . . . 283
Configuring Virtual Member Manager on IBM
WebSphere Application Server Network
Deployment . . . . . . . . . . . . . . 285
Chapter 19. Backup and restoration 287
Backing up the administrative workstation . . . 287
Restoring the administrative workstation . . . . 288
Installation properties . . . . . . . . . . 288
Updating environment data . . . . . . . 301
Notices . . . . . . . . . . . . . . 305
Trademarks . . . . . . . . . . . . . . 307
Index . . . . . . . . . . . . . . . 309

Contents v
vi IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Chapter 1. Preparing for installation
These topics provide information about product media, preinstallation
considerations, overview of the installation procedure, and instructions on using
the SmartCloud Control Desk launchpad.

Use the planning information to familiarize yourself with the overall process of a
SmartCloud Control Desk deployment before you use this information to conduct
the installation.

Before you begin

A set of tasks must be completed before installing SmartCloud Control Desk. In
some cases, to perform the steps, you must be logged in as a user with
administrator privileges on Windows or as root on UNIX. Some processes, such as
anti-virus programs, can negatively affect SmartCloud Control Desk installation on
the system. You must temporarily shut down any noncritical processes before
running the SmartCloud Control Desk installation program.

Most tasks must be completed for middleware installed on UNIX systems,

regardless of whether you intend to use the middleware installation program to
install and configure SmartCloud Control Desk middleware. These tasks must be
completed for any UNIX systems hosting middleware you intend to use with
SmartCloud Control Desk.

Note: Make a copy of the image of the system, database, and application server on
which you are planning to install the product.

Note: IBM® publishes updates to the middleware installation program. Before

using it, visit the IBM Support Portal to see whether there is an updated copy of
the installation program available for your use.

Ensure that you have adequate disk space for the future on the systems being used
for the SmartCloud Control Desk deployment. Filling up the disk space on a
SmartCloud Control Desk deployment system can cause problems with
SmartCloud Control Desk operations.

Fully qualified host names provided to the installation programs must resolve
between systems involved in the product deployment. Ensure all IP addresses
configured for systems targeted for the product deployment are reachable using
the ping command from the administrative workstation.
“Checking port availability” on page 7
You need to ensure that certain ports are available before using the product
installation programs.
“AIX and HP-UX tar command requirements” on page 8
Both the native UNIXtar command and the GNU version of the tar command
are required by the middleware installation program. Because the native utility
does not support long file names, ensure that GNU tar version 1.14 or higher is
installed. GNU tar version 1.14 ensures that installation files can be extracted.
“Increasing AIX file size and number of descriptors” on page 8
For SmartCloud Control Desk to function correctly, you must increase the

© Copyright IBM Corp. 2012 1

 default number of file descriptors that are allowed for the root user and set the
maximum allowable file size to unlimited.
“Increasing AIX paging space” on page 9
To successfully install and run SmartCloud Control Desk, you must increase the
default paging space for the AIX® system to a minimum of 4 GB, or, preferably,
the total amount of physical memory in the system.
“Enabling asynchronous I/O on AIX” on page 10
IBM Tivoli® Directory Server requires asynchronous I/O be enabled on AIX
systems.
“Checking for required libraries on Linux” on page 11
The SmartCloud Control Desk deployment requires certain Linux system
libraries.
“Configuring the JRE in Linux” on page 11
In some cases, the middleware installation program fails on Red Hat Enterprise
Linux 5 systems, or other systems with Security-Enhanced Linux (SELinux)
enabled.
“Setting the ulimit” on page 12
This section details how to set the ulimit in Linux, which is used to define user
system and process resource limits.
“Setting the swap size” on page 12
SmartCloud Control Desk can be a resource-intensive application. Configure
and tune your system for maximum performance. This section details how to
set the size of the swap space used in Linux systems.
“Setting shared memory” on page 12
This section details how to set a minimum shared memory value in Linux.
“Remote configuration enablement” on page 13
The SmartCloud Control Desk installation program can automatically configure
middleware. You must enable a remote access protocol for each system on
which you intend to install the middleware.
“Enabling SSL client authentication” on page 14
The SmartCloud Control Desk installation program and the process solution
installer fail if the client authentication feature of secure sockets layer (SSL) is
enabled in the IBM HTTP Server. You can use a workaround to enable client
authentication during installation.
“System password policy settings” on page 15
Be familiar with the password policies of systems you are using as part of a
SmartCloud Control Desk deployment.
“Backing up the Deployment Engine database” on page 15
These instructions are for backing up the Deployment Engine database.
Backups are used to restore the database to the state it was before installing.
“Programmatically verifying prerequisites”
You can use the prerequisite verification utility to verify that installation
program prerequisites are present on a system. Use this utility before starting
the middleware and product installation programs.

Programmatically verifying prerequisites

You can use the prerequisite verification utility to verify that installation program
prerequisites are present on a system. Use this utility before starting the
middleware and product installation programs.

2 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 About this task

The prerequisite verification utility checks the following items:

v Operating system requirements, including fix packs.
v Hardware requirements, including memory and hard disk space.
v Port availability.
v Middleware requirements such as software packages, library files, directory
permissions, host names, and installation locations.

You can start the prerequisite verification utility from the product installation
launchpad or from the command line. When started from the launchpad, the utility
runs in interactive mode. When started from the command line, the prerequisite
verification utility accepts various parameters. The prerequisite verification utility
must be run on the system hosting the prerequisite being checked. You cannot use
this utility to check prerequisites on a remote system.
Table 1. System verification parameters
Parameters Details
-component Specifies the type of component being verified. At least one component must be
used with the prerequisite verification utility.
dbserver
Use the dbserver parameter to have the prerequisite verification utility check
for DB2® prerequisites.
dirserver
Use the dirserver parameter to have the prerequisite verification utility check
for IBM Tivoli Directory Server prerequisites.
j2eeserver
Use the j2eeserver parameter to have the prerequisite verification utility
check for WebSphere® Application Server Network Deployment prerequisites.
bsi
Use the bsi parameter to have the prerequisite verification utility check for
prerequisites required by the product installation program. Run the
prerequisite verification utility with the bsi parameter on the administrative
workstation.

Syntax example:
tpae_req_check.bat -component bsi

If you do not use the -component parameter, you are prompted to specify
components when using the utility.

Multiple components can be specified as comma-separated values.

Chapter 1. Preparing for installation 3

Table 1. System verification parameters (continued)
Parameters Details
-input The prerequisite verification utility can accept a property file as input. The utility
verifies property values found in the file.

For example, the default DB2 server port parameter is DB2_SERVER_PORT=50000.

The prerequisite verification utility verifies that this port is available on the DB2
server host.

The default input property file is tpae.properties, and is found on the

middleware installation media in the SystemRequirements directory. There are also
several sample property files found in the SystemRequirements\
sample_property_files. These sample property files contain custom values
defined for particular operating systems. You can copy these property files to the
system and modify them, or create your own, before running the prerequisite
verification utility.

Syntax example:
tpae_req_check.bat -component dbserver -input path to the property file

If you do not use the input parameter when you run the prerequisite verification
utility, the utility is run in interactive mode. You are prompted for individual
values to be verified.
-mode The prerequisite verification utility can be run in silent or interactive mode.
interactive
By default, the prerequisite verification utility is run in interactive mode. If
you do not specify the -mode parameter, the utility defaults to running in
interactive mode. When started from the launchpad, the utility runs in
interactive mode.
silent
If you use the silent qualifier, you can also use the input parameter and
supply a property file. If an input file not provided, default property values
are used. The output must also be directed to a file to view the results.

Syntax example:
tpae_req_check.bat
-component dbserver
-mode silent
-input path to the property file > prereqresults.log
-lang Parameter used to specify the locale of the system being verified.

Syntax example:
tpae_req_check.bat
-component dbserver
-lang en

Results are produced in the language of the locale specified.

This is an optional parameter.

By default, the language set in the system locale is used. If the resource bundle is
not found for the system locale, or, the system locale language is not supported,
messages are displayed in English.

4 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 1. System verification parameters (continued)
Parameters Details
-trace Parameter used to specify trace output statements while the utility is running.
None
Selecting this qualifier results in no trace information being generated while
the utility is running.
Verbose
Selecting this qualifier results in detailed trace information being generated
while the utility is running.
Normal
Selecting this qualifier results in default trace information being generated
while the utility is running.

Syntax example:
tpae_req_check.bat
-component dbserver
-trace None

Procedure
1. Log on to the system you are checking for prerequisites with a user ID that has
permission to run scripts on the system. Ensure that the middleware
installation media is mounted or otherwise available to the system. This
example procedure uses values found in the default tpae.properties file to
verify that a system is suitable to host DB2 for a SmartCloud Control Desk
deployment.
2. Open a command-line window and change directory to the SystemRequirements
directory of the middleware installation media.
3. Run the prerequisite verification utility. Specify the component being checked
and the property file to use.
tpae_req_check.bat
-component dbserver
-input d:\SystemRequirements\tpae.properties

In this example, the tpae.properties file is located in the same directory as the
tpae_req_check.bat script.

Results

After the prerequisite verification utility has completed successfully, results are
printed to the screen.
CTGIN8117I : The Tivoli Pre-requisite Scanner has been launched.
CTGIN8118I : The Tivoli Pre-requisite Scanner exited with the return code
IBM Prerequisite Scanner
Version : 1.0.34
Build : 20101109
OS Name : Microsoft Windows Server 2003, Enterprise Edition Service Pack 2
User Name: Administrator

Machine Info
Machine name : MYMACHINE
Serial Number: KKKKKK0
OS Serial : 66666-666-6666666-66666

PAE [not defined] [version 07500000]:

Property Result Found Exp...
======== ====== ===== ===...

Chapter 1. Preparing for installation 5

os.totalPhysicalMemory PASS 2.00GB 1.90GB
network.hasFQDN FAIL False True
Disk#1 (C:\ibm\tivoli\mwi\workspace) PASS 27.99GB 300MB
Disk#2 (C:\Temp\1) PASS 27.99GB 1000MB
Disk#3 (C:\Temp\1) PASS 27.99GB 250MB
network.availablePorts.db2 PASS 135,445,1025,2967,3389,5800,5900,139 50000
network.availablePorts.ctginst PASS 135,445,1025,2967,3389,5800,5900,139 50005
Disk#4 (C:\Program Files\IBM\SQLLIB) PASS 27.99GB 1.40GB

ALL COMPONENTS :
Property Result Found Exp...
======== ====== ===== ===...
C: PASS 27.99GB 2.91GB

Prereq Scanner Overall Result: FAIL

prereq_checker.bat 1

These values can also be redirected to a file when starting the command from the
command line.

If any of the verification steps report a failure, resolve the issue and rerun the
verification utility before installing SmartCloud Control Desk components.

Table 2 contains a list of the properties checked. Use this information to analyze
prerequisite verification utility results.
Table 2. Prerequisite verification utility properties
Property Description
CpuArchitecture Verifies the machine architecture is supported.
disk(rw permissions) Checks read/write permissions of required directories.
network.availablePorts.* Verifies required ports are available.

The following example checks to ensure a port required by DB2 is available.

network.availablePorts.db2inst=50000
network.dns Verifies there is a DNS entry for the system on the DNS server.
network.fqdn Verifies that the system host name is fully qualified.
os.architecture Verifies the operating system architecture is supported.
os.dir.tmp/home Verifies required permissions for the system directories
os.FreePagingSpace Verifies adequate free paging space is available on the system.
os.iodevicestatus Verifies the I/O device status of the system.
os.lib.ksh Checks the ksh library.
os.lib.libstdc++.so.5 Verifies a prerequisite library is available on the system.
os.lib.xlC.rte=xlC.rte.9.0.0.8+ Verifies a prerequisite library is available on the system.
os.mountcheck Checks for the existence of nosuid on the file system.
os.package.rpm Verifies prerequisite packages are available on the system.
os.RAMSize Reports system RAM available.
os.SELinux Determines if selinux is enabled.
os.servicePack Verifies required service packs are installed on the system.
os.shell.default Determines the default shell for users.

6 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 2. Prerequisite verification utility properties (continued)
Property Description
os.space.* Determines disk space availability for various file systems.

The following example shows the check made for the middleware installation
program workspace.
os.space.root=[dir:root=/root/ibm/tivoli/mwi/workspace,unit:MB]300
os.totalPhysicalMemory Reports physical RAM available to the operating system.
os.ulimit Identifies user limits configured on the system.
os.Version Reports the operating system type and version.

Checking port availability

You need to ensure that certain ports are available before using the product
installation programs.

About this task

You must check to see if ports are in use and accepting connections for the system
you are using to host middleware.

For example, port 50000 must be made available for DB2.

Port 9060 must be made available for IBM WebSphere Application Server Network
Deployment.

If you intend to use these default port values, ensure that the port is not already
assigned before you run installation programs.

You can either use the prerequisite verification utility to check for port availability,
or you can check manually.

Procedure
1. Open the appropriate port checking utility on the host system. If present, check
firewall rules for the system.
2. Check the availability of ports required by SmartCloud Control Desk. If you
find that port already assigned, ensure that you choose another value when
prompted by the middleware installation program.
“Programmatically verifying prerequisites” on page 2
You can use the prerequisite verification utility to verify that installation
program prerequisites are present on a system. Use this utility before starting
the middleware and product installation programs.

Accessing system directories

Before using the product installation programs, you need to assign access
permission to particular directories.

Before you begin

Before using the product installation programs, you need to assign access
permission for the /tmp and /home directories on Linux systems.

Chapter 1. Preparing for installation 7

 About this task

The user that starts the product installation programs requires read, write, and
execute permissions for the /tmp and /home directories. If one of these directories
uses a symbolic link, for example, /products/home, ensure that symbolic link
directory also has the proper access.

Procedure
1. Log in to the system as a user with root authority on the system.
2. Enter the following commands:
#chmod 777 /tmp
#chmod 777 /home

AIX and HP-UX tar command requirements

Both the native UNIXtar command and the GNU version of the tar command are
required by the middleware installation program. Because the native utility does
not support long file names, ensure that GNU tar version 1.14 or higher is
installed. GNU tar version 1.14 ensures that installation files can be extracted.

Verify that the system path variable contains both native UNIX tar and GNU tar
paths. The GNU tar path must be defined before the native UNIX tar path. For
example, the native tar utility is installed in /usr/bin and the GNU tar utility is
installed in /opt/freeware/bin/tar.

If you have set a symbolic link to overwrite the native UNIX tar command with
the GNU tar command an error occurs.
http://www.ibm.com/systems/p/os/aix/linux/toolbox/download.html

AIX font requirements

AIX requires specific fonts in order to produce reports.

About this task

When producing reports from AIX systems, TrueType fonts must be available on
the system.

Procedure
1. Install TrueType fonts on the AIX system.
2. Ensure the fonts-path environment variable refers to the location of the fonts.

Increasing AIX file size and number of descriptors

For SmartCloud Control Desk to function correctly, you must increase the default
number of file descriptors that are allowed for the root user and set the maximum
allowable file size to unlimited.

About this task

To increase the allowable file size and number of allowable descriptors for the root
user in AIX, complete the following steps:

Procedure
1. Edit the /etc/security/limits file by opening it in a text editor.

8 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 2. Locate the section for the root user, and change the parameters to the following
values:
root:
fsize = -1
nofiles = 8192
A value of -1 for the fsize parameter indicates no limit.
3. Save and exit the file. You must log out as root and log back in for these
changes to take effect.
4. Verify the settings from a command window using the following command:
ulimit -a
Output from the ulimit command is like the following example:
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 2097152
stack(kbytes) 32768
memory(kbytes) unlimited
coredump(blocks) 2097151
nofiles(descriptors) 8192

Increasing AIX paging space

To successfully install and run SmartCloud Control Desk, you must increase the
default paging space for the AIX system to a minimum of 4 GB, or, preferably, the
total amount of physical memory in the system.

About this task

In order to add more paging space, you add more logical partitions to the system.

Procedure
1. Determine the current amount of paging space available to the server by
issuing the following command.
lsps -a

This command results output contains the following information, for example:

Page Space Physical Volume Volume Group Size Used

hd6 hdisk0 rootvg 5632MB 2

2. Determine the size of a logical partition by issuing the following command:

lslv hd6

This command results in output that includes partition information, for

example:
Table 3.
LPs PP Size
44 127 megabytes

In the example output, there are a total of 44 Logical Partitions that are each
128 Mb in size. These results show a total of 5632 Mb of paging space available
to the system.
3. Add more logical partitions, which are required in order to add more paging
space, by issuing the following command:
chps -s xx yyy

Chapter 1. Preparing for installation 9

 Where xx is the number of logical partitions to add and yyy identifies the
logical volume. For example,
chps -s 10 hd6

adds 10 logical partitions to the logical volume hd6, which results in adding
1280 Mb to the paging space.

Verifying large page size support for AIX

For SmartCloud Control Desk to function correctly, large page size support must
be enabled on AIX servers that host WebSphere Application Server.

About this task

If you are deploying SmartCloud Control Desk on WebSphere Application Server

hosted on an AIX system, that system must be configured to support large page
sizes.

Large page usage is primarily intended to provide performance improvements to

high performance computing applications. Typically this feature is enabled by
default on AIX systems.

Procedure
1. Log on to the AIX system that hosts WebSphere Application Server and open a
console window. You must have root authority to work with the AIX operating
system commands.
2. Verify large page size support by running the following command:
ps -Z

Output from the command includes 4K and 64K page sizes listed for processes,
for example:
# ps -Z
PID TTY TIME DPGSZ SPGSZ TPGSZ CMD
311342 pts/4 0:00 4K 4K 4K ksh
397526 pts/4 0:00 4K 4K 4K ps
487558 pts/4 0:00 64K 64K 4K sleep

Enabling asynchronous I/O on AIX

IBM Tivoli Directory Server requires asynchronous I/O be enabled on AIX systems.

About this task

Enabling asynchronous I/O on AIX is an installation requirement, so this step

must be run before running the middleware installation program. You need to
perform this step only if the system hosts the IBM Tivoli Directory Server.

Without asynchronous I/O, DB2 database instances cannot be started successfully.

Without asynchronous I/O, Oracle database instances cannot be started

successfully.

To turn on asynchronous I/O follow these steps:

10 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Procedure
1. Log in to the system as root.
2. Open a terminal and run the following command:
smit chgaio
3. From the System Management Interface Tool (SMIT) dialog box, change STATE
to be configured at system restart from defined to available.
4. Click OK.
5. Exit SMIT.
6. Run the following command from the command line:
smit aio
7. In the System Management Interface Tool (SMIT) dialog box, select Configure
Defined Asynchronous I/O, and then click Enter.
8. Reboot the system to enable the changes.

Checking for required libraries on Linux

The SmartCloud Control Desk deployment requires certain Linux system libraries.

Procedure
1. Locate the libstdc++.so.5 library in the /usr/lib/ directory. If this library is
not installed, the middleware installation program throws an error when
running the middleware installation program in graphical mode. If you cannot
locate this library on your system, locate the RPM package for your system that
contains this library and install the package.
2. Ensure that you have the libstdc++33-32bit-3.3.3-11.9.x86_64.rpm package
installed before running the product installation program. SUSE Linux
Enterprise Server 10 64-bit systems hosting manually configured middleware
must host this package.
3. Ensure you have the compat-libstdc++ library installed on Red Hat Enterprise
Linux v6 systems running the product installation program or the process
solution installation program.

Configuring the JRE in Linux

In some cases, the middleware installation program fails on Red Hat Enterprise
Linux 5 systems, or other systems with Security-Enhanced Linux (SELinux)
enabled.

About this task

In one scenario, the middleware installation program fails with an error stating
that the Java™ Runtime Environment (JRE) cannot be found. In another scenario,
the middleware installation program fails stating that it cannot find the VM.

Complete the following steps to avoid these problems:

Procedure
1. Temporarily disable SELinux by using the setenforce 0 command.
2. Run the middleware installation program.
3. Re-enable SELinux by using the setenforce 1 command.
4. Manually issue the chcon -R -t textrel_shlib_t install_home/jvm/jre> command.

Chapter 1. Preparing for installation 11

 Results

The middleware installation program is now able to locate the JRE. Alternatively,
you can edit the /etc/selinux/config file and set SELINUX to either permissive or
disabled for a more permanent fix. This solution, however, affects the level of
security for the entire system.

Setting the ulimit

This section details how to set the ulimit in Linux, which is used to define user
system and process resource limits.

About this task

For Linux systems, you must set the ulimit for the system before using the
middleware installation program.

If you set the ulimit in .profile for root, the ulimit setting applies to all processes.

To set the ulimit, complete the following steps:

For AIX systems, see “Increasing AIX file size and number of descriptors” on page
8.

Procedure
1. From a command line, type ulimit -f unlimited
2. From a command line, type ulimit -n 8192

Setting the swap size

SmartCloud Control Desk can be a resource-intensive application. Configure and
tune your system for maximum performance. This section details how to set the
size of the swap space used in Linux systems.

About this task

Typically, the swap size for Linux is set to twice the amount of physical RAM in
the server. See the product documentation for your Linux distribution for more
information. For AIX systems, See “Increasing AIX paging space” on page 9.

Additional swap space can be made available to the system by:

Procedure
v increasing the size of the existing swap partition
v creating a new, additional swap partition
v creating a swap file

Setting shared memory

This section details how to set a minimum shared memory value in Linux.

About this task

For Linux systems, you must set a minimum shared memory value for the system
before using the middleware installer.

12 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 To set the minimum shared memory value, complete the following steps:

Procedure
1. From a command line, type sysctl kernel.shmmax and determine if the value is
less than 268435456 bytes (256 Mb).
2. If you must increase the value, from a command line, type sysctl -w
kernel.shmmax=268435456.
3. Update the value in /etc/sysctl.conf.

Remote configuration enablement

The SmartCloud Control Desk installation program can automatically configure
middleware. You must enable a remote access protocol for each system on which
you intend to install the middleware.

Use SSH for logging on to and configuring remote Linux and UNIX systems. Use
Windows SMB for logging on to and configuring remote Windows systems.
Windows SMB is a Windows protocol. The IBM JRE on the administrative
workstation includes SSH.

You do not need an SSH client to remotely configure middleware on Linux or

UNIX systems. But, you must install OpenSSH on remote non-Windows
workstations so that you can log on to them, using SSH protocol.

Before you start the installation program, ensure that you can log on to any remote
servers with the protocols that you intend to use. Use the credentials that you plan
to supply to the installation program.

For remote Windows systems, ensure that the following requirements are met
before installing the software:
v The user name that you provide to the installation program must exist as a local
account on the remote system. This user must be a member of the Windows
Administrators group.
v The following Windows services must be started on the remote system before
you begin a remote installation and configuration:
– winmgmt (Windows Management Instrumentation)
– RemoteRegistry (Remote Registry)
– lanmanserver (Service)
v The SMB protocol must be enabled and configured to send NetBIOS over
TCP/IP, by choosing to use port 139. Alternatively, you can configure SMB to
use TCP/IP as the transport protocol, without NetBIOS, by configuring it to use
port 445.
v Ensure that any ports that you use for remote protocols are not blocked by
firewalls or security policies, including ports 137 and 139. Port 139 is used if
SMB is configured to run on NetBIOS over TCP/IP. Port 445 is used if SMB is
run directly on TCP/IP, without NetBIOS.
v To disable simple file sharing, start Windows Explorer. Click Tools > Folder
Options, and clear the Use Simple File Sharing check box.
v The Windows administrative share (C$) and the interprocess communications
(IPC$) folder must be shared.
v For Microsoft Windows Server 2008 systems that support password-protected
sharing, disable password-protection. Shares must be shared for the Guest or
Everyone accounts.

Chapter 1. Preparing for installation 13

 v For Windows systems that have User Account Control (UAC) enabled, it must
be disabled before software can be remotely installed and configured.
v If Cygwin is installed on the remote Windows system the SSH daemon (sshd)
must be uninstalled or disabled.

For remote Linux or UNIX systems, ensure that the following requirements are met
before installing the software:
v For AIX systems, set the following SSH parameters located in the
/etc/ssh/sshd_config file:
– ClientAliveInterval 900
– ClientAliveCountMax 10
Stop the SSH daemon using the stopsrc -s sshd command and then restart it
using the startsrc -s sshd command.
v For AIX systems, set the TMOUT and TIMEOUT variables in the user profile
script to 0. This setting prevents the user from idling out and being logged off
the remote system during the installation.
v The user name that you provide to the installation program must exist as a
privileged account (for example, root) on the remote systems.
v Ensure that a current version of OpenSSH is installed and running. Do not use
OpenSSH 4.7.0.5302.
v For Oracle Solaris systems, the remote access protocols require the use of
internal shell scripts that must be run within the korn (ksh) shell. The methods
need ksh, even if the user ID that you use to log on to the remote system is
configured to use a different shell. Consequently, Oracle Solaris systems must
have the ksh environment installed and properly configured.
v If you plan to remotely configure software on remote Linux or UNIX computers,
ensure that SSH is installed.

Remote configuration does not support accessing network drives on the local or
remote system.

Enabling SSL client authentication

The SmartCloud Control Desk installation program and the process solution
installer fail if the client authentication feature of secure sockets layer (SSL) is
enabled in the IBM HTTP Server. You can use a workaround to enable client
authentication during installation.

Before you begin

The SmartCloud Control Desk installation and process solution installer programs
use HTTP client requests for various configuration actions. The SmartCloud
Control Desk installation program does not configure WebSphere Application
Server Network Deployment nor IBM HTTP Server to use SSL. However, they do
function in environments where WebSphere Application Server Network
Deployment and IBM HTTP Server are manually configured to use SSL.
SmartCloud Control Desk installation programs and standard deployment
procedures do not work correctly when the client authentication feature of SSL is
enabled in the IBM HTTP Server. As a result, the validation of product
administration credentials or the import of data with Maximo® Enterprise Adapter
fails. Client authentication is enabled in the IBM HTTP Server, by using the
SSLClientAuth Required directive in the httpd.conf configuration file.

14 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 About this task

If client authentication must be enabled for the IBM HTTP Server, use the
following workaround procedure to install the product.

Procedure
1. Remove the SSLClientAuth Required directive in the httpd.conf configuration
file of the IBM HTTP Server.
2. Stop and restart the IBM HTTP Server.
3. Run the SmartCloud Control Desk installation program or process solution
installation programs.
4. Add the SSLClientAuth Required directive back to the httpd.conf
configuration file of the IBM HTTP Server.
5. Stop and restart the IBM HTTP Server.

System password policy settings

Be familiar with the password policies of systems you are using as part of a
SmartCloud Control Desk deployment.

Your organization might have password policy regulations enforced on systems on

your network. Before deploying SmartCloud Control Desk, be sure that you are
familiar with the password policies of systems used in the deployment, or you
might experience errors during installation.

For example, Microsoft Windows Server 2008 systems have a stricter set of
password requirements than previous versions configured by default. If you are
not familiar with these stronger password requirements, you might experience an
error during the installation of SmartCloud Control Desk. This error occurs when
creating users on a Microsoft Windows Server 2008 system.

Password values that you provide during the SmartCloud Control Desk installation
must be compliant with the password policies set for the target system. Passwords
are not validated against the password policies of target systems at the time you
enter them on the installation program panels. If your passwords do not conform
to the password policies of systems used to deploy the product, errors occur when
the installation program attempts to create these passwords during the
configuration step,

Backing up the Deployment Engine database

These instructions are for backing up the Deployment Engine database. Backups
are used to restore the database to the state it was before installing.

Before you begin

Back up the Deployment Engine database of the system before and after applying
any updates to an existing deployment. Use backups to recover from partial
installation attempts.

About this task

To back up the Deployment Engine database, complete the following steps:

Chapter 1. Preparing for installation 15

 Procedure
1. Set up the environment using the following command:
Windows
c:\install_home\ctg_DE\acsi\setenv.cmd
UNIX
cd install_home/ctg_DE/acsi
./setenv.sh
2. Run the command to back up the Deployment Engine registry:
Windows
c:\install_home\ctg_DE\acsi\bin\backupdb.cmd backup file name
UNIX
cd install_home/ctg_DE/acsi/bin
./backupdb.sh backup file name
Use a meaningful name for backup file name to reflect the fact that it contains the
state of the registry after your installation of SmartCloud Control Desk. For
example, DEBackupAfterInstall.

Specifying host name values

Do not use localhost for host name values in the installation program. Specify the
fully qualified host name or IP address of the system on which you are installing.

For Linux or UNIX systems, if the hostname -f command does not return a fully
qualified host name, consult the system documentation for assistance.

Establishing a fully qualified host name on Windows systems

Use this task to establish a fully qualified host name on Windows systems.

About this task

To establish a fully qualified host name on Windows systems, complete the

following steps.

Procedure
1. On the desktop, right-click My Computer.
2. Select Properties.
3. On the Computer Name tab, click Change.
4. Enter a fully qualified host name in the Computer name field, and then click
More.Alternatively, you can provide the IP address for the system.
5. In the DNS Suffix and NetBIOS Computer Name window, verify that the
Primary DNS suffix field displays a domain name, and then click OK.
6. In the Computer Name Changes window, click OK.
7. Click Apply and close the System Properties window.

Forcing the middleware installer to use alphanumeric hostnames

You can force the use of alphanumeric host name use within the middleware
installation program by starting it from the command line and using the
forceHostname=true parameter.

Example

The following example shows a use of the forceHostname=true parameter:

mwi-console -V forceHostname=true

16 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 What to do next

If you launched the middleware installation program from the command line using
the forceHostname=true parameter, then you are required to provide an
alphanumeric value in the Hostname field. An IP address results in an error
message.

Enabling full text search for IBM DB2

Full text search is a search option that lets you search for words and phrases, as
well as perform more complex searches using wildcards and logical operators. For
SmartCloud Control Desk 7.5.1, it is essential to install and enable the Text Search
feature that comes with DB2 9.7.5 or later.

About this task

The steps that you take depend on whether you are installing a new instance of
SmartCloud Control Desk 7.5.1 , or you are upgrading from an earlier release. This
procedure applies to a new installation. If you are upgrading from an earlier
release, refer to the Upgrade Guide.

Important: Follow this procedure before you install SmartCloud Control Desk.

Procedure
1. Ensure that DB2 9.7.5 or later is installed.
2. From the DB2 server, enable full text search. For more information, see
Installing and configuring DB2 Text Search .
3. Install SmartCloud Control Desk.

Launchpad
The IBM SmartCloud Control Desk launchpad serves as a centralized interface for
launching a collection of installation programs and product information.

The launchpad application assists you in choosing which product installation

programs you must install and indicates the order in which they must be installed.

Use the SmartCloud Control Desk launchpad to:

v start the middleware installation program.
v start the prerequisite checker utility.
v start the SmartCloud Control Desk installation program.
v start the Service Provider support installation program.
v access the SmartCloud Control Desk information center, including information
used to plan the SmartCloud Control Desk installation and deployment.

Just before starting the launchpad, ensure that you meet the middleware
prerequisites. Ensure that you have the correct service pack levels for your
environments and always use fully qualified domain names when entering values
for the installation program.

Starting the launchpad

Use the following information to start the SmartCloud Control Desk launchpad

Chapter 1. Preparing for installation 17

 Before you begin

Launchpad generated messages are captured in a hidden log frame while the
launchpad is running. To show the log frame on the bottom of the launchpad
panels, hold the CTRL key while simultaneously clicking the banner frame of the
launchpad. Messages that are generated while the launchpad is running are not
automatically saved on the hard disk drive. You can manually save the messages
from a session by clicking Save at the bottom of the log frame and then specifying
where you want to save the file.

About this task

To start the IBM SmartCloud Control Desk launchpad, complete the following
steps:

Procedure
1. Log on to an account with system administration privileges on the computer
where you want SmartCloud Control Desk components to be installed.
2. Start the launchpad from the root directory of the installation image:
v Windows: Start the launchpad by using the launchpad.exe program.
v AIX: Start the launchpad from the root directory by using the launchpad.sh
program.
The launchpad program uses the system default browser to run. If the
default browser on AIX is Firefox, it is likely that the launchpad program
does not run properly due to the ksh shell interface. If you must use the
launchpad with the Firefox browser, follow these steps to modify it.
a. Download and extract the launchpad images as described in the
download document.
b. Modify /user_dir/launchpad/Firefox.sh and remove the following lines:
typeset +r LOGNAME 2>/dev/null
LOGNAME=lp_user_$$; export LOGNAME
c. Run the launchpad from /user_dir
v Linux: Start the launchpad by using the launchpad.sh program.
For example,
./launchpad.sh

18 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Chapter 2. Deploy with automatic middleware configuration
Use this information to use product installation programs and tools to install and
automatically configure a SmartCloud Control Desk deployment within your
enterprise.

This information provides a high-level overview or road map of tasks you need to
complete in order to deploy SmartCloud Control Desk with automatic middleware
configuration.

In this scenario, you use the middleware installation program to install and
automatically configure new instances of the following components:
v DB2
v WebSphere Application Server Network Deployment
v IBM Tivoli Directory Server

You use the product installation program to perform further middleware

configuration tasks automatically before finally deploying the product itself.

You can use the middleware installation program to install DB2. You then use the
SmartCloud Control Desk installation program to automatically configure it.

Middleware installation program middleware deployment plan overview

The deployment plan resides in the workspace directory and is generated from
deployment choices selected in the middleware installation program.

The plan is a series of deployment steps and configuration parameters. Each step is
responsible for installing and uninstalling one portion of the middleware. When
deployment choices are changed, the existing deployment plan is deleted and
replaced with the new deployment plan.

Installing middleware using the middleware installation program

You use the middleware installation program to install middleware components for
use with IBM SmartCloud Control Desk. The middleware components that you
choose to install, and the associated configuration parameters, are recorded in a
deployment plan for the target system.

Before you begin

v Plan your installation.
v Use the planning worksheets for middleware installation to record the values
that you need to specify during the installation procedure.

About this task

These instructions cover the use of the middleware installation program to install
and configure middleware components on a single server. The single server
deployment scenario is suitable for demonstration, test, or training purposes.

The following middleware components are installed:

© Copyright IBM Corp. 2012 19

 v DB2
v WebSphere Application Server Network Deployment
v Tivoli Directory Server

You must run the middleware installation program locally on the target system.
You can start the program by using the launchpad or a setup script. When you use
the launchpad, the program files are copied to a temporary directory on the target
system. When you use a setup script, no files are copied to the target system. If
you are installing on a 64-bit Windows system, you must use a setup script to start
the program.

Procedure
1. Log in to the target system as a user with administrative authority. If you are
running the middleware installation program from a Linux or UNIX terminal
window, you must be logged in as the root user.
2. Start the middleware installation program by using the launchpad or a setup
script.
v Use the launchpad to start the middleware installation program.
a. Start the launchpad.
Windows (32-bit only)
From the root directory of the installation image, run the
following command: launchpad.exe.
Linux and UNIX
From the root directory of the installation image or product
media, run the following command: launchpad.sh.
b. Run the middleware installation requirements checking utility.
c. Click Middleware.
v Run the following command to launch a setup script which starts the
middleware installation program:
Windows
launchpad\Install\MWI\setupwin.bat /l
Linux and UNIX
launchpad/Install/MWI/setupUNIX.sh -l
3. Specify the workspace location for this installation of middleware.
4. On the Deployment Choices panel, select the components that you want to
install on this system.
5. Review the summary of the generated deployment plan and click Next to
proceed with configuration of the specified components. When you click Next,
the middleware installation program verifies the prerequisites for installing
the specified components.
6. To specify a host name for the target system other than the default host name,
select Override the local machine hostname and enter a host name in the
Hostname field. You cannot clear this option after it has been selected,
however, you can change the value in the Hostname field.
7. Optional: To specify a default password that can be used throughout the
middleware installation program, select Use this password as the value for
all subsequent passwords and enter the required password.
8. Specify the following details for DB2 Enterprise Edition Server:
a. Specify the installation directory.

20 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 b. Specify administrative account details for the DB2 Administration Server.
The password that you specify is also used as the password for the DB2
default database instance.
c. If you are installing on a Linux or AIX system, specify fenced user account
details for DB2.
9. Specify an instance name, port, and user name for the default database
instance.
10. Specify an instance name, port, and user account details for the SmartCloud
Control Desk database instance.
11. Specify names for the DB2 administrators and users groups. A users group
name is required only if DB2 Enterprise Edition Server is installed on a
Windows system.
12. Specify the following details for IBM Tivoli Directory Server:
a. Specify the installation directory.
b. Specify a distinguished name and password for the Tivoli Directory Server
administrator.
13. Specify the configuration parameters that are required for Tivoli Directory
Server, including the organizational unit, organization suffix, and country
suffix that are required when the directory server is used with SmartCloud
Control Desk.
14. Specify the following details for the Tivoli Directory Server database instance:
a. Specify the name of the DB2 database that you are using to hold Tivoli
Directory Server data.
b. Specify the name and password of the Tivoli Directory Server database
instance.
15. Specify the configuration parameters that are required when Tivoli Directory
Server is being used as the LDAP resource for WebSphere Application Server
Network Deployment security.
16. Specify the bind distinguished name and password that are required for
binding to the LDAP instance. When you click Next, the middleware
installation program validates the host and directory information that you
specified for the directory server. The specified information must be verified
before the installation can proceed.
17. Specify the install location and administrative account details for WebSphere
Application Server Network Deployment.
18. Specify the profile names for the WebSphere Application Server Network
Deployment deployment manager and application servers.
19. Specify the following details for WebSphere Application Server Network
Deployment:
a. Specify the WebSphere Application Server Network Deployment cell name.
b. Specify the names of the WebSphere Application Server Network
Deployment deployment manager and application server nodes.
c. Specify the install location WebSphere Application Server Network
Deployment update installer.
20. Specify the install location, the port used by IBM HTTP Server, and the port
that must be used to administer IBM HTTP Server. If you install IBM HTTP
Server into a directory path that includes spaces, for example, the default
install location for Windows systems, you cannot start and stop it from the
administrative console. If the directory path includes spaces, you must start
and stop the IBM HTTP Server from the command line.

Chapter 2. Deploying with automatic middleware configuration 21

 21. Accept the default profile name for the WebSphere Application Server
Network Deployment plug-in for IBM HTTP Server by clicking Next. This
value cannot be changed.
22. Specify whether you need to copy the SmartCloud Control Desk middleware
installation images from the product media to your file system:
v If you need to copy the middleware installation images from the product
media, specify the source and destination directories.
v If the middleware installation images are already saved to the file system,
specify the directory where they are located.
23. Optional: Before you deploy, verify the integrity of the middleware installation
images by selecting the option for checksum validation. If the checksum
operation fails, click Back and recopy the images. If you do not select this
option and the middleware installation images are corrupted or otherwise
inaccessible from the directory specified, an error occurs. If you encounter this
error, you must replace the corrupted middleware installation images and
then restart the middleware installation program.
24. Specify a directory to use for middleware installation program temporary files
and extracted middleware installation images.
25. Select Deploy the plan to confirm that you are ready to install and configure
the selected middleware components.
26. Click Deploy to initiate the installation process.
27. When the deployment is complete, click Finish to close the installation
wizard.

Middleware installation program logs

Middleware installation program log files are in the workspace directory that was
defined in the middleware installation program.

There are several types of log files.

User interface logs
The logs generated by the middleware installation program user interface
are in the workspace directory.
The middleware installation program logs all information in
<workspace_loc>/mwi.log: Default workspace locations for all platforms are
as follows:
Windows
C:\ibm\tivoli\mwi\workspace
Linux /root/ibm/tivoli/mwi/workspace
AIX /ibm/tivoli/mwi/workspace
The mwi.log file is the high-level log file that was generated by the most
recent invocation of the middleware installation program. If an error
occurs, examine this log file first. An entry in this log file might direct you
to a lower-level log file.
Log files named mwi.logX, where X is a number, are copies of the mwi.log
file from earlier invocations of the middleware installation program. So, for
example, mwi.log0 is produced after the first invocation of the middleware
installation program. mwi.log1 is produced after the second invocation of
the middleware installation program.

22 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Logs for steps run by the user interface
In addition to collecting input from the user, the user interface of the
middleware installation program also performs several system checks.
Examples of system checks run by the user interface runs include:
v dependency checking to ensure that the operating system meets the
deployment requirements
v inventorying the software on the system to locate existing instances of
middleware products deployed by the middleware installation program
v checking the available disk space to ensure that there is enough for the
deployment
Each of these checks is produced in the form of a step so that it can also be
run as part of the deployment plan. When the user interface runs a step, it
copies the step into a subdirectory of the workspace directory. The log files
generated by a step are in the same subdirectory. These files follow the
same pattern as a step that is run as part of the deployment plan.
Logs for the deployment plan
The deployment plan is in the directory <Workspace Directory>/host
name/deploymentPlan, where host name is the host name of the current
system. Each time the deployment plan is used to install or uninstall
middleware products, a process ID is assigned and log files are generated.
The log files for the deployment plan are in the subdirectory
logs/processID. The primary log file for the deployment plan is
DeploymentPlan.log, a high-level log file that lists the steps started as part
of the deployment plan.
Logs for the workstation plan
The machine plan is located in the directory <Workspace Directory>/host
name/deploymentPlan/MachinePlan_host name. The log files for the machine
plan are in the logs subdirectory. The primary log files for the machine
plan are named MachinePlan_host name_processID. These log files contain
the output generated by Apache ANT when running the machine plan
ANT script.
Logs for steps in the deployment plan
Each step in the deployment plan is in a directory named <Workspace
Directory>/host name/deploymentPlan/MachinePlan_host
name/stepNum_stepID, where stepNum is the sequence number of this step
in installation processing order of the deployment plan and stepID
identifies the step. The log files for the step are in the logs subdirectory.
Some steps might provide a message log file named
stepID_processID.message, which contains a few entries that summarize
the result of starting the step. All steps provide a trace log file named
stepID_processID.log, which contains many entries, typically including
information about the input parameters and the substeps started.
Logs for substeps
Each step contains one or more substeps. The substeps perform the actual
installation, uninstall, and checking work for the middleware installation
program.
Each substep is in the directory <Workspace Directory>/host
name/deploymentPlan/MachinePlan_host name/stepNum_stepID/operation/
substepNum_substepID, where operation is the ANT target in the step ANT
script that starts this substep. substepNum is the sequence number of this

Chapter 2. Deploying with automatic middleware configuration 23

 substep in the processing order of the step, and substepID identifies the
substep. Typical values for operation are install, uninstall, and check.
The log files for the substep are typically in a subdirectory named
processID/logs.
Log files generated by the native middleware installation programs are
also kept here.

As an example, the log file generated by the middleware installation program

during DB2 installation on a UNIX system would be found in the following
directory: <workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_DB2_9.7/install/01_BASE/<Time_Stamp>/logs/
db2setup.log

Middleware installation program log reference

The following logs are produced during the use of the middleware installation
program.

DB2 Installation Step

DB2 installation logs can be found in the following locations:

DB2 base
The following DB2 base log files can be found in the <workspace>/
<machine_name>/deploymentPlan/MachinePlan_<machine_name>/
000XX_DB2_9.7/install/01_BASE/<Time_Stamp>/logs directory:
v DB2_ESE_InstallProduct_<TimeStamp>.err
v DB2_ESE_InstallProduct_<TimeStamp>.log
v DB2_ESE_MoveDB2InstallLogsToLogsLoc_<TimeStamp>.err
v DB2_ESE_MoveDB2InstallLogsToLogsLoc_<TimeStamp>.log
v DB2_ESE_Register_DB_<TimeStamp>.err
v DB2_ESE_Register_DB_<TimeStamp>.log
v DB2_ESE_Verify_DB2_Level_<TimeStamp>.err
v DB2_ESE_Verify_DB2_Level_<TimeStamp>.log
v db2setup.log
v de_processreq.log
v de_processreq.log_utf8
v de_trace.log
For Windows, the following additional files will be available:
v DB2_ESE_Verify_DB2_Service_20080805_063132GMT.err
v serviceList.log
The de_processreq.log contains status information. This log file provides
details on which action has failed. The failed action log can be examined
for more information. The db2setup.log file is the native product log for
DB2. This log contains DB2 installation information.
DB2 fix pack
The following DB2 fix pack log files can be found in the
<workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_DB2_XX/install/02_FP/
<Time_Stamp>/logs directory:
v DB2_ESE_FP2MoveDB2LogsToLogsLoc_<Time_Stamp>.err

24 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 v DB2_ESE_FP2MoveDB2LogsToLogsLoc_<Time_Stamp>.log
v DB2_ESE_InstallDB2Fixpack_<Time_Stamp>.err
v DB2_ESE_InstallDB2Fixpack_<Time_Stamp>.log
v DB2_ESE_ListDB2FPAdmin_<Time_Stamp>.err
v DB2_ESE_ListDB2FPAdmin_<Time_Stamp>.log
v DB2_ESE_ListDB2FPinstance_<Time_Stamp>.err
v DB2_ESE_ListDB2FPinstance_<Time_Stamp>.log
v DB2_ESE_StartDB2FPAdminInstance_<Time_Stamp>.err
v DB2_ESE_StartDB2FPAdminInstance_<Time_Stamp>.log
v DB2_ESE_StopDB2FPAdminInstance_<Time_Stamp>.err
v DB2_ESE_StopDB2FPAdminInstance_<Time_Stamp>.log
v DB2_ESE_UpdateDB2_<Time_Stamp>.err
v DB2_ESE_UpdateDB2_<Time_Stamp>.log
v DB2_ESE_Verify_DB2_FP_Level_<Time_Stamp>.err
v DB2_ESE_Verify_DB2_FP_Level_<Time_Stamp>.log
v de_processreq.log
v de_processreq.log_utf8
v de_trace.log
v installFixPack.log
The de_processreq.log contains status information. This log file provides
details on which action has failed. The failed action log can be examined
for more information. The installFixPack.log file is the native log for the
fix pack. This log contains DB2 fix pack installation information.
No fix pack logs are available on Windows systems.

If you encounter a failure wrapper failure, more information can be found in the
$(_TempLocation) directory in the <Time_Stamp> folder. This directory contains the
logs related to DB2 installation

DB2 Configuration Step

The following DB2 configuration logs can be found in <workspace>/

<machine_name>/deploymentPlan/MachinePlan_<machine_name>/
000XX_DB2_Configuration/install/01_CONFIG/<Time_Stamp>/logs:
v checkpasswdCreated.log
v createuser.log
v etcgroupfile.log
v etcpasswdfile.log
v setUserPassword.log

For Linux, including Linux on IBM System z®, the following additional files are
produced:
v permissions.log
v catalogLocalNode.log (produced in the 02_CONFIG folder)
v catalogLocalNode.log (produced in the 02_CONFIG folder)
v startDB2.log

For Windows, the following additional files are produced:

Chapter 2. Deploying with automatic middleware configuration 25

 v createDB2instance.log
v localEnvVariables.log
v setTCPIPCommForDB2instance.log
v setTCPIPPortForDB2instance.log
v setWindowsServiceToAutoStart.log

For UNIX, including Linux, Linux on IBM System z, and AIX, the following
additional files are produced:
v createinstance.log
v SetTCPIPCOMM.log
v stopDB2.log
v updatePort.log

IBM Tivoli Directory Server DB2 for SmartCloud Control Desk Step

The following IBM Tivoli Directory Server DB2 for SmartCloud Control Desk logs
can be found in <workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_ITDS_DB2_CCMDB/check/01_CHECKS/
<Time_Stamp>/logs:
v etcgroupfile.log
v etcpasswdfile.log

IBM Tivoli Directory Server Installation Step

IBM Tivoli Directory Server installation logs can be found in the following
locations:
GSKIT
The following IBM Tivoli Directory Server installation log files can be
found in the <workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_ITDS_6.3/install/01_GSKIT/
<Time_Stamp>/logs directory.
v de_processreq.log
v de_trace.log
For Windows and Linux, including Linux on IBM System z, the following
additional files are produced:
v GSKit_Install_GSKit_<Time_Stamp>.log
v GSKit_Install_GSKit_<Time_Stamp>.err
For 32-bit Windows systems, the following additional file is produced:
v gskInstall.log
For 32-bit Windows systems, the following additional files are produced:
v ISScript_Install.log
v gskInstall.log
For AIX systems, the following additional files are produced:
v GSKit_Install_JS_RTE_20080721_084044GMT-06.00.log
v GSKit_Install_SA_RTE_20080721_084044GMT-06.00.log
v vGSKit_Install_TA_RTE_20080721_084044GMT-06.00.log
v rteList.log

26 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 The de_processreq.log contains status information. This log file provides
details on which action has failed. The failed action log can be examined
for more information.
IBM Tivoli Directory Server base
The following IBM Tivoli Directory Server base log files can be found in
the <workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_ITDS_6.3/install/02_BASE/
<Time_Stamp>/logs directory:
v de_processreq.log
v de_trace.log
For Windows, the following additional files are available:
v ldapinst.log
v registryList.log
For Linux, including Linux on IBM System z, the following additional files
are produced:
v ITDS6.3_CheckRPMEntry_<Time_Stamp>.err
v ITDS6.3_CheckRPMEntry_<Time_Stamp>.log
v rpmList.log
For AIX systems, the following additional files are produced:
v ITDS6.3_CheckRTEEntry_<Time_Stamp>.log
v ITDS6.3_CheckRTEEntry_<Time_Stamp>.err
v rteList.log
The de_processreq.log contains status information. This log file provides
details on which action has failed. The failed action log can be examined
for more information.
IBM Tivoli Directory Server fix pack
The following IBM Tivoli Directory Server fix pack log files can be found
in the <workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_ITDS_6.3/install/02A_FP/
<Time_Stamp>/logs directory:
v de_processreq.log
v de_trace.log
For Windows, the following additional file are available:
v ldapinst.log
For Linux, the following additional files are produced:
v ITDS6.3_CheckRPMEntry_<Time_Stamp>.err
v ITDS_InstallFixpack_<Time_Stamp>.log
v rpmList.log
For AIX systems, the following additional files are produced:
v ITDS_InstallFixpack_<Time_Stamp>.err
v ITDS_InstallFixpack_<Time_Stamp>.log
v ITDS6.3_CheckRTEEntry_<Time_Stamp>.log
v ITDS6.3_CheckRTEEntry_<Time_Stamp>.err
v rteList.log

Chapter 2. Deploying with automatic middleware configuration 27

 The de_processreq.log contains status information. This log file provides
details on which action has failed. The failed action log can be examined
for more information.
IBM Tivoli Directory Server language pack
The following IBM Tivoli Directory Server language pack log files can be
found in the <workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_ITDS_6.3/install/03_LP/
<Time_Stamp>/logs directory:
v de_processreq.log
v de_trace.log
For Windows, the following additional files are available:
v ldapLP_inst.log
v registryList.log
For Linux, including Linux on IBM System z, the following additional file
is produced:
v checkIfRPMEntryExists_<Time_Stamp>.log
For AIX systems, the following additional files are produced:
v checkIfRTEEntryExists_<Time_Stamp>.log
v checkIfRTEEntryExists_<Time_Stamp>.err

IBM Tivoli Directory Server Configuration Step

The following IBM Tivoli Directory Server configuration logs can be found in
<workspace>/<machine_name>/deploymentPlan/MachinePlan_<machine_name>/
000XX_ITDS_Configuration/install/01_CONFIG/logs:
v createUsers.log
v netUserCheck.log

For Windows, the following additional files are produced:

v PasswdNeverExpires.log
v configureDB.log (produced in the 02_CONFIG folder)
v configureDNPassword.log (produced in the 02_CONFIG folder)
v configureSuffix.log (produced in the 02_CONFIG folder)
v startInstanceTool.log (produced in the 02_CONFIG folder)
v startServer.log (produced in the 02_CONFIG folder)
v audit.log (produced in the C:\idsslapd-idsccmdb\logs folder)
v bulkload.log (produced in the C:\idsslapd-idsccmdb\logs folder)
v db2clicmds.log (produced in the C:\idsslapd-idsccmdb\logs folder)
v lostandfound.log (produced in the C:\idsslapd-idsccmdb\logs folder)
v traceibmslapd.log (produced in the C:\idsslapd-idsccmdb\logs folder)
v adminaudit.log (produced in the C:\idsslapd-idsccmdb\logs folder)
v ibmdiradm.log (produced in the C:\idsslapd-idsccmdb\logs folder)
v db2cli.log (produced in the C:\idsslapd-idsccmdb\logs folder)
v perftune_stat.log (produced in the C:\idsslapd-idsccmdb\logs folder)
v idstools.log (produced in the C:\idsslapd-idsccmdb\logs folder)

For UNIX, including Linux,Linux on IBM System z, and AIX, the following
additional files are produced:

28 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

v permissions.log
v ITDS_LDAP_Config.encrypted.ldif (produced in the 03_CONFIG folder)
v addLDIFData.log (produced in the 03_CONFIG/logs folder)
v idsadm.log (produced in the /var/idsldap/V6.3 folder)
v idsadmdb2.log (produced in the /var/idsldap/V6.3 folder)
v idsadmdb2cmds.log (produced in the /var/idsldap/V6.3 folder)

WebSphere Application Server Network Deployment Installation Step

WebSphere Application Server Network Deployment installation logs can be found

in the following locations:
WebSphere Application Server Network Deployment
The following WebSphere Application Server Network Deployment
installation log files can be found in the <workspace>/<machine_name>/
deploymentPlan/MachinePlan_<machine_name>/000XX_WAS_ND_7.0/install/
01_BASE/<Time_Stamp>/logs directory.
v de_processreq.log
v de_processreq.log_utf8
v de_trace.log
v ProductInstall.log
v WAS_ND_InstallProduct_<Time_Stamp>.err
v WAS_ND_InstallProduct_<Time_Stamp>.log
UpdateInstaller
The following UpdateInstaller installation log files can be found in the
<workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_WAS_ND_7.0/install/01_UPDT_INST/
<Time_Stamp>/logs directory.
v de_processreq.log
v de_processreq.log_utf8
v de_trace.log
v ProductInstall.log
v Update_Installer_InstallProduct_<Time_Stamp>.err
v Update_Installer_InstallProduct_<Time_Stamp>.log
v UpdateInstaller_MoveUpdateInstallerInstallLogsToLogsLoc.err
v UpdateInstaller_MoveUpdateInstallerInstallLogsToLogsLoc.log

The de_processreq.log contains status information. This log file provides details
on which action has failed. The failed action log can be examined for more
information. The ProductInstall.log file is the native log for the fix pack. This log
contains WebSphere Network Deployment and UpdateInstaller installation
information.

WebSphere Application Server Network Deployment Configuration

Step

WebSphere Application Server Network Deployment configuration logs can be

found in the <workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_WAS_ND_Configuration/install/01_CONFIG/
<Time_Stamp>/logs directory:
v createAppServer.log

Chapter 2. Deploying with automatic middleware configuration 29

 v MXServer_serverStatus.log
v nodeagent_serverStatus.log
v setupcmd.log
v startManager.log
v startServer.log
v UnixAugmentProfileDMgrForISC.log
v UnixCreateProfileAppSvr.log
v UnixCreateProfileDMgr.log
v verifyProfile.log
v startManager.log (produced in the 02_CONFIG folder)
v stopManager.log (produced in the 02_CONFIG folder)
v stopNode.log (produced in the 02_CONFIG folder)
v syncNode.log (produced in the 02_CONFIG folder)
v VMMConfigData.log (produced in the 02_CONFIG folder)
v SystemErr.log (produced in the <WAS_HOME>/profiles/ctgDmgr01/logs/dmgr
folder)
v SystemOut.log (produced in the <WAS_HOME>/profiles/ctgDmgr01/logs/dmgr
folder)
v addNode.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs folder)
v runAddNode.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs
folder)
v syncNode.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs
folder)
v wsadmin.traceout (produced in the <WAS_HOME>/profiles/ctgAppSrv01/
logsfolder)
v SystemErr.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
nodeagent folder)
v SystemOut.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
nodeagent folder)
v startServer.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
MXServer folder)
v stopServer.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
MXServer folder)
v SystemErr.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
MXServer folder)
v SystemOut.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
MXServer folder)

IBM HTTP Server Installation Step

IBM HTTP Server installation logs can be found in the following locations:
IBM HTTP Server Base
The following IBM HTTP Server base installation log files can be found in
the <workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_IHS_7.0/install/01_BASE/
<Time_Stamp>/logs directory.
v de_processreq.log
v de_processreq.log_utf8

30 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 v de_trace.log
v IHS_InstallProduct_<Time_Stamp>.err
v IHS_InstallProduct_<Time_Stamp>.log
v ProductInstall.log
The de_processreq.log contains status information. This log file provides
details on which action has failed. The failed action log can be examined
for more information. ProductInstall.log is the native product log. This
log contains IBM HTTP Server installation information.
IBM HTTP Server fix pack
The following IBM HTTP Server fix pack log files can be found in the
<workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_IHS_7.0/install/01A_FP/
<Time_Stamp>/logs directory:
v de_processreq.log
v de_processreq.log_utf8
v de_trace.log
v IHS_Fixpack_GetIHSUpdateVersion_<Time_Stamp>.err
v IHS_Fixpack_GetIHSUpdateVersion_<Time_Stamp>.log
v IHS_Fixpack_InstallIHSFixpack_<Time_Stamp>.err
v IHS_Fixpack_InstallIHSFixpack_<Time_Stamp>.log
v IHS_Fixpack_MoveIHSFixInstallLogsToLogsLoc_<Time_Stamp>.err
v IHS_Fixpack_MoveIHSFixInstallLogsToLogsLoc_<Time_Stamp>.log
For Windows, the following additional files are available:
v IHS_Fixpack_StartIHSAdminService_<Time_Stamp>.err
v IHS_Fixpack_StartIHSAdminService_<Time_Stamp>.log
v IHS_Fixpack_StartService_<Time_Stamp>.err
v IHS_Fixpack_StartService_<Time_Stamp>.log
v IHS_Fixpack_StopIHSAdminService_<Time_Stamp>.err
v IHS_Fixpack_StopIHSAdminService_<Time_Stamp>.log
v v IHS_Fixpack_StopService_<Time_Stamp>.err
v v IHS_Fixpack_StopService_<Time_Stamp>.log
For UNIX, including Linux,Linux on IBM System z, and AIX, the following
additional files are produced:
v IHS_Fixpack_StartServiceLinux_<Time_Stamp>.err
v IHS_Fixpack_StartServiceLinux_<Time_Stamp>.log
v IHS_Fixpack_StopServiceLinux_<Time_Stamp>.err
v IHS_Fixpack_StopServiceLinux_<Time_Stamp>.log
v ProductInstall.log
The de_processreq.log contains status information. This log file provides
details on which action has failed. The failed action log can be examined
for more information. ProductInstall.log is the native product log. This
log contains IBM HTTP Server fix pack installation information.
WebSphere plug-ins
The following WebSphere plug-in logs can be found in the
<workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_IHS_7.0/install/02_WAS_PLUGIN/
<Time_Stamp>/logs directory:

Chapter 2. Deploying with automatic middleware configuration 31

 v de_processreq.log
v de_processreq.log_utf8
v de_trace.log
v ProductInstall.log
v WAS_plugins_for_WAS_InstallProduct_<Time_Stamp>.err
v WAS_plugins_for_WAS_InstallProduct_<Time_Stamp>.log
The de_processreq.log contains status information. This log file provides
details on which action has failed. The failed action log can be examined
for more information. ProductInstall.log is the native product log. This
log contains IBM HTTP Server fix pack installation information.
WebSphere plug-in fix pack
The following WebSphere plug-in logs can be found in the
<workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_IHS_7.0/install/02A_FP/
<Time_Stamp>/logs directory:
v de_processreq.log
v de_processreq.log_utf8
v de_trace.log
v ProductInstall.log
v WAS_Plugins_for_WAS_Fixpack_GetWASPluginUpdateVersion_
<Time_Stamp>.err
v WAS_Plugins_for_WAS_Fixpack_GetWASPluginUpdateVersion_
<Time_Stamp>.log
v WAS_Plugins_for_WAS_Fixpack_InstallWASPluginsFixpack_
<Time_Stamp>.err
v WAS_Plugins_for_WAS_Fixpack_InstallWASPluginsFixpack_
<Time_Stamp>.log
v WAS_Plugins_for_WAS_Fixpack_MoveIHSFixInstallLogsToLogsLoc_
<Time_Stamp>.err
v WAS_Plugins_for_WAS_Fixpack_MoveIHSFixInstallLogsToLogsLoc_
<Time_Stamp>.log
The de_processreq.log contains status information. This log file provides
details on which action has failed. The failed action log can be examined
for more information. ProductInstall.log is the native product log. This
log contains IBM HTTP Server fix pack installation information.
For Windows, the following additional files are available:
v WASPlugin _Fixpack_StartIHSAdminService_<Time_Stamp>.err
v WASPlugin _Fixpack_StartIHSAdminService_<Time_Stamp>.log
v WASPlugin _Fixpack_StartService_<Time_Stamp>.err
v WASPlugin _Fixpack_StartService_<Time_Stamp>.log
v WASPlugin _Fixpack_StopIHSAdminService_<Time_Stamp>.err
v WASPlugin _Fixpack_StopIHSAdminService_<Time_Stamp>.log
v WASPlugin _Fixpack_StopService_<Time_Stamp>.err
v WASPlugin _Fixpack_StopService_<Time_Stamp>.log
For UNIX, including Linux,Linux on IBM System z, and AIX, the following
additional files are produced:
v WASPlugin_Fixpack_StartServiceLinux_<Time_Stamp>.err

32 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 v WASPlugin_Fixpack_StartServiceLinux_<Time_Stamp>.log
v WASPlugin_Fixpack_StopServiceLinux_<Time_Stamp>.err
v WASPlugin_Fixpack_StopServiceLinux_<Time_Stamp>.log
The de_processreq.log contains status information. This log file provides
details on which action has failed. The failed action log can be examined
for more information. ProductInstall.log is the native product log. This
log contains IBM HTTP Server fix pack installation information.
IBM HTTP Server WebSphere plug-in configuration
The following IBM HTTP Server WebSphere plug-in configuration logs can
be found in the <workspace>/<machine_name>/deploymentPlan/
MachinePlan_<machine_name>/000XX_IHS_7.0/install/03_CONFIG/
<Time_Stamp>/logs directory:
v configure.webserver.command.out
v ConfigureIHSPlugin.out
v start.http.server.out
v SystemErr.log (produced in the <WAS_HOME>/profiles/ctgDmgr01/logs/
dmgr folder)
v SystemOut.log (produced in the <WAS_HOME>/profiles/ctgDmgr01/logs/
dmgr folder)

Authentication service

Authentication service logs can be found in the <workspace>/<machine_name>/

deploymentPlan/MachinePlan_<machine_name>/000XX_ESS_XX/install/01_CONFIG/
<Time_Stamp>/logs directory:
v configureESS.log
v exportWASLTPAKeys.log
v importLTPAKeys.log
v installESS.log
v installWIM.log
v key.file
v modifyLTPASettings.log
v save.log
v startManager.01.log
v startManager.02.log
v startNode.01.log
v startNode.02.log
v startServer.01.log
v startServer.02.log
v stopManager.01.log
v stopManager.02.log
v stopNode.01.log
v stopNode.02.log
v stopServer.01.log
v stopServer.02.log
v sync.log
v SystemErr.log (produced in the <WAS_HOME>/profiles/ctgDmgr01/logs/dmgr/
folder)

Chapter 2. Deploying with automatic middleware configuration 33

 v SystemOut.log (produced in the <WAS_HOME>/profiles/ctgDmgr01/logs/dmgr/
folder)
v addNode.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
folder)
v runAddNode.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
folder)
v syncNode.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
folder)
v wsadmin.traceout (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
folder)
v SystemErr.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
nodeagent/ folder)
v SystemOut.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
nodeagent/ folder)
v SystemErr.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
MXServer/ folder)
v SystemOut.log (produced in the <WAS_HOME>/profiles/ctgAppSrv01/logs/
MXServer/ folder)

Configuring IBM Tivoli Directory Server user and group

strings
You can configure user and group strings in IBM Tivoli Directory Server to adapt it
to your deployment needs.

About this task

You can manually create user and group strings for Tivoli Directory Server during
installation.

If you configure directory server user and group strings for a system that hosts
only the IBM Tivoli Directory Server , you must manually create properties in the
input.properties file of the ITDS_CONFIGURATION step of the deployment plan.

Procedure
1. Edit the input.properties file that is in the directory server folder at:
Workspace\machine name\deploymentPlan\MachinePlan_machine
shortname\00006_ITDS_Configuration. For example, in Windows, the default
location of the input.properties file is C:\ibm\tivoli\mwi\workspace\
mymachine.ibm.com\deploymentPlan\MachinePlan_mymachine\
00006_ITDS_Configuration.
2. Add the following properties:
was_nd.secure.GroupSuffix=ou\=groups,ou\=SWG,o\=IBM,c\=US
was_nd.secure.UserSuffix=ou\=users,ou\=SWG,o\=IBM,c\=US
3. If Tivoli Directory Server configuration parameters are customized, change the
applicable values to your custom values on the configuration parameters panel.
For example, if your custom values are ou=SWG1 and the Organization
country suffix is o=IBM1,c=US1, you must manually replace all occurrences of
those values in the input.properties file:
was_nd.secure.GroupSuffix=ou\=groups,ou\=SWG1,o\=IBM1,c\=US1
was_nd.secure.UserSuffix=ou\=users,ou\=SWG1,o\=IBM1,c\=US1

34 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Configuring SSL between Microsoft Active Directory and
WebSphere Application Server Network Deployment
Configuring SSL between Microsoft Active Directory and WebSphere Application
Server Network Deployment enables the installation program to automatically
create users and groups.

Before you begin

To enable the installation program to automatically create users and groups within
Microsoft Active Directory, you must configure SSL communication between
Microsoft Active Directory and WebSphere Application Server Network
Deployment. This procedure is only required if you choose to allow the product
installation program to automatically configure WebSphere Application Server
Network Deployment. You also want the product installation program to
automatically create users in Microsoft Active Directory.

You must enable SSL for Microsoft Active Directory, generate a certificate, and then
add that certificate to WebSphere Application Server Network Deployment.

Changing the name or domain of the certificate authority at any point invalidates
certificates previously issued from that authority.

Ensure that you have host name resolution setup properly in your
environment. Communication failures occur if the system hosting Microsoft Active
Directory cannot resolve host names for systems that have been issued certificates.

Ensure that you have already installed Microsoft Internet Information Services with
ASP extensions enabled on the system before configuring the certificate service
required for SSL. Microsoft Internet Information Services are a prerequisite of the
certificate service. Microsoft Internet Information Services can be added as a
Windows component from the Add/Remove Programs dialog. Add this
component by selecting the Internet Information Services or Application Server
component and installing it. If you have IBM HTTP Server installed on the same
system, you cannot use port 80 for IBM HTTP Server. If IBM HTTP Server was
configured to use port 80, you must change it to another value because Microsoft
Internet Information Services must use port 80. After you verify that these two
conditions are met, proceed with setting up certificate services as described in this
procedure.

Procedure
1. Add the Certificate Services component:
a. From the Control Panel of the Microsoft Active Directory server, select
Add or Remove Programs. Then select Add/Remove Windows
Components.
b. From the Windows Components panel, select the Certificate Services
option, and then click Next.
c. From the CA Type panel, select Stand alone root CA, select the Use
custom settings to generate the key pair and CA certificate option, and
then click Next.
d. From the Public and Private Key Pair panel, select Microsoft Strong
Cryptographic Provider for the CSP value, select SHA-1 as the Hash
algorithm, set the Key length to 2048, and then click Next.
e. From the CA Identifying Information panel, enter mymachine.ism75.com in
the Common name for this CA field, enter DC=ism75,DC=com for the

Chapter 2. Deploying with automatic middleware configuration 35

 Distinguished name suffix, set the Validity period to 5 years, and then
click Next. The values used in this step are example values only. Replace
these values with the details of the system hosting Microsoft Active
Directory.
f. From the Certificate Database Settings panel, you can keep the default
value of C:\WINDOWS\system32\CertLog for both the Certificate database
and Certificate database log fields, and then click Next. Configuration of
the component now begins.
g. Click Finish.
h. Restart the system.
2. Download a CA certificate:
a. Start Internet Explorer.
b. Select Tools > Internet Options > Security and click Sites.
c. From the Trusted Sites dialog box, enter http://mymachine.ism75.com in
the Add this Web site to the zone: field, click Add, and then click Close.
d. Enter the following address in the browser: http://mymachine.ism75.com/
certsrv
e. From the Certificate Services page, click Download a CA certificate,
Certificate Chain, or CRL.
f. From the Download a CA Certificate, Certificate Chain, or CRL page, click
install this CA certificate chain. When the task has completed successfully,
click Back.
g. From the Download CA Certificate, Certificate Chain, or CRL page select
Current for the CA certificate value, choose Base 64 for the Encoding
method, and then click Download a CA Certificate.
h. When prompted, specify the type as Security Certificate and save the
security certificate file as serverRootCA.cer.
3. Add the Certificates Snap-in:
a. Start the Microsoft Management Console.
b. Select File > Add/Remove Snap-in.
c. From the Add/Remove Snap-in dialog box, click Add.
d. From the Add stand-alone Snap-in dialog box, select Certificates and then
click Add.
e. Select Computer account and then click Next.
f. Select Local computer: (the computer this console is running on) and click
Finish.
g. From the Add stand-alone Snap-in dialog box, select Certification
Authority and then click Add.
h. Select Local computer: (the computer this console is running on) and
click Finish.
i. Click Close to close the Add stand-alone Snap-in dialog box.
j. Click OK.
4. Transfer certificates to a store:
a. In the Microsoft Management Console, navigate to Console Root >
Certificates (Local Computer) > Third-Party Root Certification
Authorities.
b. Right-click Certificates and select All Tasks > Import.
c. From the File to Import panel of the Certificate Import wizard, browse to
the location of the serverRootCA.cer file, select it, and then click Next.

36 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 d. From the Certificate Store panel, select Place all certificates in the
following store, click Next, and then click Finish.
5. Create and submit a request to the CA:
a. Using Internet Explorer, navigate to http://mymachine.ism75.com/certsrv.
From the Certificate Services page, click Request a certificate.
b. From the Request a Certificate page, click advanced certificate request.
c. From the Advanced Certificate Request page, click Create and submit a
request to this CA.
d. From the Advanced Certificate Request page, enter the following
information and then click Submit.
Identifying Information
Enter the fully qualified name of the machine hosting Microsoft
Active Directory in the Name field. This value must be capitalized,
for example MYMACHINE.ISM75.COM.
Type of Certificate Needed
Select Server Authentication Certificate.
Key Options
For the CSP field, select Microsoft RSA SChannel Cryptographic
Provider.
Select the Automatic key container name, Mark keys as
exportable, and Store certificate in the local computer certificate
store options.
For the Key Size field, you can either accept the default value of
1024, or change it to a more appropriate value.
Additional Options
Set the Request Format option to PKCS10.
For the Hash Algorithm field, select SHA-1.
For the Friendly Name field, enter the same exact value as entered
for the Name field.

Default values are sufficient for the remaining fields on this page.
e. Click Home to return to the home page for Certificate Services.
6. Install the certificate:
a. In the Microsoft Management Console, navigate to Console Root >
Certification Authority (Local) > mycomputer.ism75.com > Pending
Requests.
b. Right-click the ID of the request, and then select All Tasks > Issue.
c. From Internet Explorer, on the Certificate Services page, click View the
status of a pending certificate request.
d. From the View the Status of a Pending Certificate Request page, click the
certificate request you created.
e. From the Certificate Issued page, click Install this certificate.
f. Restart the system.
7. Verify the private key:
a. When the system has restarted, invoke the Microsoft Management Console
and navigate to Console Root > Certificates (Local Computer) > Personal
> Certificates.
b. Double-click the entry displayed in uppercase.

Chapter 2. Deploying with automatic middleware configuration 37

 c. From the Certificate dialog box, ensure you can find the statement You
have a private key that corresponds to this certificate, and then click OK.
d. Double-click the entry displayed in lowercase.
e. From the Certificate dialog box, ensure you can find the statement You
have a private key that corresponds to this certificate, and then click OK.
8. Configure the connection:
a. Launch the Microsoft LDP utility.
b. Select Connection.
c. Select Connect.
d. Enter mymachine.ism72.com for Server, 636 for Port, select SSL, and then
click OK. Review the information displayed to verify your configuration
values.
9. Export certificate files:
a. Launch the Microsoft Management Console and navigate to Console Root
> Certificates (Local Computer) > Personal > Certificates.
b. Right-click the uppercase certificate entry and select All Tasks > Export
c. From the Certificate Export wizard Welcome panel, click Next.
d. From the Export Private Key panel, select No, do not export private key,
and then click Next.
e. From the Export File Format panel, select Base-64 encoded X.509(.CER),
and then click Next.
f. From the File to Export panel, export the certificate as serverRootCA.cer,
click Next, and then click Finish.
g. Right-click the lowercase certificate entry and select All Tasks > Export
h. From the Certificate Export wizard Welcome panel, click Next.
i. From the Export Private Key panel, select No, do not export private key,
and then click Next.
j. From the Export File Format panel, select Base-64 encoded X.509(.CER),
and then click Next.
k. From the File to Export panel, export the certificate as serverAuthCert.cer,
click Next, and then click Finish.
10. Add signer certificates:
a. Copy serverRootCA.cer and serverAuthCert.cer to the WebSphere
Application Server Network Deployment system.
b. Invoke the WebSphere Application Server Network Deployment
administrative console.
c. From the WebSphere Application Server Network Deployment
administrative console, select Security > SSL certificate and key
management.
d. Click Keystores and certificates.
e. Click CellDefaultTrustStore.
f. Click Signer certificates and then click Add.
g. From the Add signer certificate page, enter MSADServerRootCA for the Alias,
enter the path (including the file name) to the serverRootCA.cer file in the
File name field, and then click OK.
h. Click Add.
i. Enter MSADServerAuthCert for the Alias, enter the path (including the file
name) to the serverAuthCert.cer file in the File name field, and then click
OK.

38 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 11. Configure security:
a. From the WebSphere Application Server Network Deployment
administrative console, select Security > Secure administration,
applications, and infrastructure.
b. From the Available realm definitions drop-down list, select Federated
repositories, and then click Configure.
c. Click the repository identifier for Microsoft Active Directory listed in
Repositories in the realm table.
d. Update the following properties and then click OK.
Port Update this value to 636.
Login properties
Set this value to cn.
Requires SSL communications
Ensure that this option is selected.
Use specific SSL alias
Ensure that this option is selected with a value of
CellDefaultSSLSettings.
e. Click Supported entity types and verify that the PersonAccount entity
type is set to cn. If it is not set to cn, click the PersonAccount entity type
and set it and then save the changes.
f. Restart the domain manager.

Uninstalling middleware
To uninstall IBM SmartCloud Control Desk middleware, you must run the
middleware installation program and select the options to remove the previous
deployment.

Before you begin

If you chose to deploy SmartCloud Control Desk middleware with a directory

server, ensure that it is active. You must remove the J2EE server before you can
remove the directory server.

About this task

The middleware installation program creates a registry when installing SmartCloud

Control Desk middleware. Using the native middleware uninstall programs causes
this registry to be out of sync with what is deployed. As a result, errors occur
when you attempt to reinstall middleware with the middleware installation
program.

Procedure
1. Stop and start servers as required:
a. Stop the IBM Tivoli Directory Server (IBM Tivoli Directory Server v6.3 -
idsccmdb).
b. Stop the IBM Tivoli Directory Server daemon (IBM Tivoli Directory Admin
Server v6.3 - idsccmdb).
c. Start DB2.
d. Start the idsccmdb DB2 instance (DB2 - DB2COPY1 - IDSCCMDB).

Chapter 2. Deploying with automatic middleware configuration 39

 e. Start the IBM Tivoli Directory Server daemon (IBM Tivoli Directory Admin
Server v6.3 - idsccmdb)
2. Log in as Administrator on Windows and root on Linux and AIX.
3. Start the launchpad by running the following command from the root
directory of the downloaded installation image:

Option Description
Windows launchpad.exe
Linux launchpad.sh
AIX launchpad.sh

4. In the launchpad navigation pane, click Install Product.

5. In the Install the middleware section, click Middleware and step through the
launchpad panels.
6. When you are prompted to browse to a workspace, specify the workspace
directory that contains the currently deployed plan, and click Next. The
default location for the workspace is the last workspace location specified. If
you did not specify a path previously, the default location for the workspace
isc:\ibm\tivoli\mwi\workspace
7. In the Select Operation panel, select Undeploy the plan, and click Next.
8. From the undeployment preview panel, click Next to undeploy the plan.
9. Exit the middleware installation program.
10. On UNIX systems, remove the following DB2 references from the
/etc/services file:
v db2c_db2insxy 50001/tcp
v db2c_db2inst1 50000/tcp

Reinstalling middleware with IBM DB2

You can run an installation of the middleware with the DB2 user and group
settings from a previous installation.

Before you begin

Remove all middleware products and their components before you reinstall the
middleware.

About this task

When DB2 is uninstalled, users and groups are not removed. You can specify the
same DB2 user and group values or replace them with new users and groups
when you run the installation program.

Procedure
1. Verify that all middleware products were properly removed by examining the
deployment plan log files. The log files are in the subdirectory Workspace
Directory/host name/deploymentPlan/logs/processID. The primary log file for
the deployment plan is DeploymentPlan.log.
2. The middleware installation program creates a default instance for DB2 and
adds the owner of the default instance to the DB2 administrator group that you
specify. Specify the DB2 users and groups that you want to use for this
installation:

40 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 v Provide the same values that were previously used for the DB2
administrators group.
v Remove the existing instance owner and specify a new administrators group.
You cannot specify an existing instance owner with a new DB2
administrators group.
3. Start the middleware installation program from the launchpad.

Installation program overview

The SmartCloud Control Desk installation program provides an interface for
installing and deploying SmartCloud Control Desk, which includes the process
automation engine and process managers.

The SmartCloud Control Desk installation program records choices you make
about your SmartCloud Control Desk deployment. It records configuration
parameters associated with those choices, and then installs and deploys
SmartCloud Control Desk based upon the information you entered.

There are two installation paths available to you when you are installing
SmartCloud Control Desk.
Simple
A simple deployment consists of installing SmartCloud Control Desk
middleware on one system. You do not have the option of using existing
middleware within your organization with SmartCloud Control Desk. All
middleware used with SmartCloud Control Desk must be installed on the
system with the middleware installation program with default values.
SmartCloud Control Desk is installed with default values provided by the
middleware installation program and SmartCloud Control Desk installation
program.
If you intend to override default values used by the simple deployment
path, you must use the custom deployment path instead.
Custom
A custom deployment typically involves deploying SmartCloud Control
Desk across several systems. Some of these systems might already host
middleware products that you want to use with your SmartCloud Control
Desk deployment. You can modify default installation values when you
deploy with the custom installation path.
This deployment option does not require you to spread the SmartCloud
Control Desk deployment across several systems. You can enter the name
of the local host as the destination for all SmartCloud Control Desk
components.

The SmartCloud Control Desk installation program can automate the configuration
of some middleware for use with SmartCloud Control Desk.

If you choose not to have the SmartCloud Control Desk installation program
automatically configure middleware, you must configure that piece of middleware
manually before the installation of SmartCloud Control Desk.

Important: When you are entering LDAP values for SmartCloud Control Desk
installation panel fields, be aware of the product-specific syntax rules for using
special characters in an LDAP string. In most cases, special characters must be
preceded by an escape character in order to make it readable by the directory

Chapter 2. Deploying with automatic middleware configuration 41

 server. Failing to escape special characters contained in an LDAP string used with
SmartCloud Control Desk results in SmartCloud Control Desk errors.

Many directory server products consider a blank space as a special character that is
part of the LDAP string. If you enter an LDAP string with an unescaped blank
character at the end of a field value, you encounter SmartCloud Control Desk
errors.

For more information about special character usage in LDAP strings, see the
product documentation for your directory server.

Information that you enter for the SmartCloud Control Desk installation program
is stored in the maximo.properties and install.properties files and the Maximo
database. These values are populated into the panel fields of the SmartCloud
Control Desk installation program on subsequent uses of the program. If you
cancel the installation program, it recalls most values that you entered the next
time you start it. Values excluded from being saved in this manner are the
SmartCloud Control Desk installation directory and the shortcut option chosen
during the installation. You can restore the default values in the SmartCloud
Control Desk installation program by deleting <Maximo_Home>/applications/
maximo/properties/maximo.properties and <Maximo_Home>/etc/
install.properties. If you cannot locate the maximo.properties file in the
<Maximo_Home> directory, look for it in the system temp file directory.

Simple installation path values

Specific simple path installation values are required by the SmartCloud Control
Desk installation program.

If you elect to install SmartCloud Control Desk through the simple installation
path, the following values are set. You must provide values where indicated.

For simple installations, you supply a single host name for middleware. The
SmartCloud Control Desk installation program expects this host to contain all the
software that works with SmartCloud Control Desk.
Table 4. SmartCloud Control Desk Simple Installation Path Values
Category Field Value Provided by User?
Deployment Option Deployment simple
Database Database type DB2
Configuration
Database Host name Yes
Configuration
Database Port 50005
Configuration
Database Database name maxdb75
Configuration
Database Instance ctginst1
Configuration
Database User ID Yes
Configuration
Database Automate database yes
Configuration configuration

42 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 4. SmartCloud Control Desk Simple Installation Path Values (continued)
Category Field Value Provided by User?
Database Remote access user Yes
Configuration ID
Database Database installation
Windows
Configuration directory
C:\Program
Files\IBM\
SQLLIB
Database Instance Yes
Windows
Configuration administrator user ID
db2admin
Database Windows service db2admin
Configuration user ID
Database Data table space maxdata
Configuration name
Database Data table space size medium
Configuration
Database Temporary table maxtemp
Configuration space name
Database Temporary table 1000
Configuration space size
IBM WebSphere Host name Yes
Application Server
Connectivity
IBM WebSphere SOAP port 8879
Application Server
Connectivity
IBM WebSphere IBM WebSphere
Windows
Application Server Application Server
C:\Program
Configuration server home
Files\IBM\
directory
WebSphere\
AppServer
IBM WebSphere User name wasadmin Yes
Application Server
Configuration
IBM WebSphere Profile name ctgDmgr01
Application Server
Configuration
IBM WebSphere Automate IBM yes
Application Server WebSphere
Configuration Application Server
configuration
IBM WebSphere Remote access user Yes
Application Server ID
Configuration
IBM WebSphere Web server port 80
Application Server
Configuration
IBM WebSphere Web server name webserver1
Application Server
Configuration

Chapter 2. Deploying with automatic middleware configuration 43

 Table 4. SmartCloud Control Desk Simple Installation Path Values (continued)
Category Field Value Provided by User?
IBM WebSphere Node name ctgNode01
Application Server
Configuration
IBM WebSphere Cluster name MAXIMOCLUSTER
Application Server
Configuration
IBM WebSphere Application server MXServer This value
Application Server cannot be changed.
Configuration
Integration Adapter JMS data source meajmsds
JMS Configuration name
Integration Adapter Persist JMS messages no
JMS Configuration
Security Use default schema yes
Configuration
Security Create users yes
Configuration automatically
Maximo Install directory C:\IBM\SMP Yes
Configuration
Configuration Step Run configuration yes
now

Installing the product and automatically configuring

middleware
To install SmartCloud Control Desk, you run the installation program from the
launchpad. The installation procedure automatically configures middleware on
multiple servers, using default values.

Before you begin

Ensure that you meet prerequisite conditions.

v The database server, the directory server, and application server services must be
started and active.
v The /tmp and /var/tmp directories must be present on the system. The
installation program depends on these directories for information during
deployments on IBM WebSphere Application Server Network Deployment.
v On the administrative workstation, temporarily shut down any noncritical
processes that can have a negative effect on the installation, such as antivirus
software.
v Ensure that the Windows DEP setting does not prevent the launchpad from
running: Select Start > Settings > Control Panel > System > Advanced >
Performance > Settings > Data Execution Prevention. Select Turn on DEP for
essential Windows programs and services only and click Apply. You might be
asked to reboot the server.

44 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

v For Linux and UNIX systems with middleware installed, the command hostname
-f must return a fully qualified host name. If necessary, consult the
documentation for your operating system. Alternatively, you can provide the IP
address for the system.
v Enable a remote execution and access service on every system that has
middleware installed. Each remote system must support a remote access
protocol. It must also accept remote logins from a user name and password that
were configured on the target server. Remote access protocols include SSH and
Windows SMB. If the remote system is a Windows server, you must configure
remote execution and access to use SMB.
v The DB2 database must be prepared.
– If DB2 is installed on a Linux or UNIX system, you must create the instance
user and the home directory for the user on the DB2 server.
– The database instance owner home directory must have 8 GB of space
available regardless of whether a database is installed in that location.
– The user ID for the DB2 instance administrator must have SYSADM (system
administration) authority. You specify this user ID during the product
installation program. See the DB2 product documentation for information
about creating a user with SYSADM authority on the DB2 server. You must
add root to a group with SYSADM authority for UNIX systems.

About this task

The instructions are for a multiple server installation that uses default values.

If you experience problems with the user interface of the installation program
when installing on AIX 6.x systems remotely, reattempt the installation locally. Use
the console or an X terminal on the system locally.

Procedure
1. Log in on the administrative system.
2. Start the product installation program from the launchpad.
a. Start the launchpad. Browse to the root directory of the downloaded
installation image, and run the following command:
Windows
launchpad.exe
UNIX launchpad.sh
If the launchpad does not start the installation, you can start the product
installation program directly. On the downloaded installation image, browse
to \Install\\, and run one of the following commands:
Windows
v install.bat
v install_win64.bat
UNIX
v install_aix64.sh
v install_linux32.sh
v install_linux64.sh
3. Select a language for the installation and click OK.
4. On the Choose Installation Folder panel, specify the path to the location
where you want to install SmartCloud Control Desk.

Chapter 2. Deploying with automatic middleware configuration 45

 You can specify a description for the installation. A description is useful for
differentiating between multiple installations that are hosted on the same
administrative workstation.
5. Review the information that is on the Verify Installation Location panel. The
panel shows any previous installation information that was found based on
the installation directory that you specified on the previous panel. After you
advance past this panel, you cannot go back and change the installation
directory for this installation.
If a more recent version of the installation program is found in the specified
target directory, you are notified. The notification means that you are using an
older version of the installation program. The version found on the
administrative workstation is newer and can contain important features and
enhancements. To use the newer version of the installation program, select the
option on the notification panel and click Next. This action exits the current
installation process and restarts the installation process with the newer
installation program. If you do not select the option, you continue the
installation with the older version of the installation program.
6. On the Package Summary panel, review the package deployment information.
This panel lists version information for both new and existing packages on the
system. Target package version information indicates the package version
being currently deployed.
7. On the Choose Deployment panel, specify Simple or Custom as the
deployment type.
8. On the Import Middleware Configuration Information panel, you select
Import middleware configuration information to have the product
installation program reuse the middleware installation program values. These
values are used as default values for the same fields in the product
installation program.
The Workspace location field refers to the location of the topology file that
contains the values that were specified for the middleware installation
program. The file is located in the workspace that was defined during the
middleware installation task. For example, C:\ibm\tivoli\mwi\workspace for
Windows or /root/ibm/tivoli/mwi/workspace for UNIX.
If you selected the simple deployment, the middleware default information is
not used.
9. On the Database Type panel, specify the software to use for the Maximo
database.
10. On the Database panel, specify configuration information for your database
software.
For things such as the database user ID, the database name, the database
instance for SmartCloud Control Desk, and the schema name, if the values do
not exist when you specify them, they are created.
For DB2, the user ID cannot be the same as the instance administrator user ID.
Database users and database instance names cannot contain spaces.
For DB2, the database instance is created if it does not exist, but the user and
its associated home directory must exist on the DB2 server. For DB2, the
schema name can be the same value as the owner of the table spaces that are
defined or it can be a different value, such as maximo.
After you specify configuration information for your database software, the
installation program validates the information with the database server.
11. On the Automate Database Configuration panel, you can specify that database
creation and configuration is to be automated.

46 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 If you do not select the option, you must configure the database manually.
12. On the Remote Access Authorization panel, specify authorization information
for the automatic database configuration feature. Specifying the values enables
remote configuration.
13. On the Database Administration panel, specify configuration information
about the database. The required information varies by database platform.
For DB2, the instance administrator user ID cannot be the same as the
database user ID. And the Windows service user ID must have administrative
authority on the system.
14. On the Database Tablespace panel, specify information about the table space
of the database.
When you click Next, the product installation program connects to the
database server and validates the information that you specified.
15. When the database validation is complete, on the Application Server Type
panel, specify the application server type for the product deployment.
You have the option of configuring WebSphere Application Server Network
Deployment automatically through the product installation program.
16. On the WebSphereConnectivity panel, specify host information for the
WebSphere Application Server Network Deployment.
17. On the WebSphere Remote Access Authorization panel, specify authorization
information for WebSphere Application Server Network Deployment
configuration.
18. On the WebSphere Application Server Network Deployment Configuration
panel, specify configuration information for WebSphere Application Server
Network Deployment.
The web server port must match an existing HTTP server port value that you
configured when you set up WebSphere Application Server Network
Deployment. If you specify a different value for the web server port, you must
restart WebSphere Application Server Network Deployment at the conclusion
of the installation. Restarting the server activates the new port and makes it
available for incoming requests.
The application server name that you specify is created if it does not exist.
19. On the Security panel, specify the method to use for authenticating and
authorizing users.
20. On the Specify Maximo Users panel, enter Maximo database user information.
Maximo administration user
The product administrator user ID that is used for initial configuration
and adding users.
Maximo system registration user
The user ID that is used for the self-registration of users.
Maximo system integration user
The user ID that is used with enterprise adapters.

Custom user ID and password values are stored in the Maximo database. The
default user IDs of maxadmin, maxreg, and maxintadm are also created as
users in the Maximo database. Creation of the default user IDs is done for
internal processing purposes. If you use Maximo database security for
authentication and authorization, the default user IDs can be used to log in to
the application. If you regard this condition as a security risk, you can modify
the passwords for the default user IDs. You modify passwords for the user
IDs in the Users application.

Chapter 2. Deploying with automatic middleware configuration 47

 21. On the Security panel, specify the names of the user and group base entries
and specify how SmartCloud Control Desk users are created.
User base entry
If you do not plan to use the default LDAP schema that is provided
with SmartCloud Control Desk, specify the user base entry that you
want to use.
Group base entry
If you do not plan to use the default LDAP schema , specify the group
base entry that you want to use.
You can specify that the installation program creates the required users.
Otherwise, you must create users manually before continuing.
If you are not using the default LDAP schema that is provided, you must
create it yourself before advancing beyond this panel. The values that are
specified for the User base entry and Group base entry fields are used to
configure the VMMSYNC cron task. To create your own LDAP schema and
create users manually, you can modify the default add-on LDIF data and
import it into your LDAP repository
22. On the Integration Adapter JMS Configuration panel, specify Java Message
Service configuration information. A JMS server requires a DB2 data
repository to be configured to maintain messages. If you are using another
database type, you cannot configure message persistence. If you specify that
JMS messages are not to be persisted, you can configure the JMS
implementation manually later.
Specify the name of the database to be used by JMS. For DB2, you can specify
whether to persist JMS messages within DB2.
Select Do not persist JMS messages if you are deploying SmartCloud Control
Desk with Oracle or Microsoft SQL Server. When you click Next, the
installation wizard skips to the SMTP Configuration panel.
23. If you specified that JMS messages should persist, specify additional JMS
configuration information in the DB2 Database Server Configuration panel.
The JMS data store can be created as a DB2 database only.
24. If you specified that JMS messages should persist, specify authorization
information for the automatic configuration feature in the DB2 Database
Server Remote Access Authorization panel.
For Windows, the user ID must be a member of the DB2ADMNS group.
For Linux or UNIX, the user ID must be root and a member of a group with
SYSADM authority for the database instance.
25. If you specified that JMS messages should persist, specify additional DB2
information in the DB2 Database Instance Configuration panel.
26. On the SMTP Configuration panel, specify the SMTP configuration
information that is used by workflows to communicate with workflow
participants.
The administrator e-mail address is the e-mail address that is used to send
messages. If you leave the fields blank, you must configure the SMTP
parameters through the product interface as a post-installation task.
27. On the Data Integration and Context Menu Services Options panel, click the
option that indicates where the database tables for these functions are created:
in the Maximo ("same") database, or in a separate database instance that you
created for this purpose. If you are installing the Entry edition, choose the
Maximo database. These tables are created but are not used by the Entry
edition.

48 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

28. On the Base Language Selection panel, specify the base language for the
installation.
29. On the Additional Language Selection panel, you can optionally specify one
or more additional languages that the installation is to support.
30. On the Run Configuration Step panel, specify how to perform the
configuration step of the installation. If you do not select an option, the
configuration step proceeds when you click Next.
Copy files now, but perform the installation configuration step later
Select this option to copy files from the installation source to the
administrative workstation. You must perform the configuration step
at a later time to complete the deployment.

Important: Do not install another product before you complete the

configuration step of the original installation. Installing another
product before you run the configuration step for this installation
overwrites the taskstore, which prevents the original installation from
ever being deployed.
The configuration values that you specify are stored in the
install_home\maximo\applications\maximo\properties\
maximo.properties and install_home\etc\install.properties files.
You run the configuration steps outside of the product installation
program by using the taskrunner utility, in the install_home\scripts
directory. Run the taskrunner utility from the command line.
install_home\scripts\taskrunner [CONTINUE <STOPONERROR|NOSTOPONERROR>]

The taskrunner uses the configuration values that are stored in the
maximo.properties and install.properties files to configure
SmartCloud Control Desk.
If you run taskrunner with the NOSTOPONERROR parameter, the
taskrunner continues despite errors. If you run taskrunner with the
STOPONERROR parameter, the taskrunner stops when it encounters an
error. If you used STOPONERROR, you can rectify the conditions that
caused the error. You can then resume the installation where the last
successfully completed task was recorded in the previous attempt by
starting taskrunner with the CONTINUE parameter.
Deploy application files manually later
Select this option to manually deploy application files to the
application server.
Defer the update of the Maximo database
Select this option if you want to manually run the database update
task for the product deployment. This option can be used when there
is a fix pack available that addresses known issues with the updatedb
script. In this scenario, you choose the Defer the update of the
Maximo database option, apply the fix pack, and then run the
updatedb -v1 command manually.
31. On the Choose Shortcut Folder panel, specify where you want SmartCloud
Control Desk icons created.
If you select In the Start Menu and use Internet Explorer, add the
SmartCloud Control Desk URL to the trusted sites web content zone. Disable
the option that requires server verification for all sites in the zone.
Do not select In the Quick Launch Bar. The selection does not create a
shortcut in the Quick Launch bar.

Chapter 2. Deploying with automatic middleware configuration 49

 Attention: Shortcuts are created for Windows systems only. Because
WebLogic Server deployments are a manual process, you must manually
update any shortcuts that you create. You update shortcuts after you
manually deployed the SmartCloud Control Desk EAR files.
32. On the Input Summary panel, review the information that you provided for
the product installation program.
If necessary, use Previous to return to previous panels to change values.
33. On the Pre-Installation Summary panel, review the installation information,
then click Install.
The installation process begins. You can monitor the progress of the
installation by viewing the messages that are shown.
34. On the Installation Completed panel, review any information presented, then
click Done.
Attention: In some cases, on AIX systems, the Installation Completed panel
might appear blank. Click Done to exit the installation program.
“Restarting middleware on Windows” on page 231
This procedure describes how to restart middleware on Windows, if you must
restart any middleware services.
“Restarting middleware on UNIX” on page 232
Middleware services on Linux and AIX platforms occasionally must be
restarted, such as when a reboot occurs. Middleware servers and services must
be active before running the SmartCloud Control Desk installation program.

Installing optional content

Install the relevant optional content package for your edition of the product.

Optional content is often used in development environments as a way to begin

developing your own content.

If you do not install optional content during the product installation process, you
can install it later. If you install it later, you must update the database and rebuild
and deploy the maximo.ear file.

Installing optional integration modules

Install integration module packages in order to set up integrations with other
products.

You can install these integration modules from the Integrations page of the
launchpad:
IBM Tivoli Provisioning Manager Integration Module
This integration module enables you to integrate Tivoli Provisioning
Manager with the release management process. For example, you can use
Tivoli Provisioning Manager as a Definitive Media Library. See the Release
management section of the information center for more information about
this integration.
Deployed Assets CMS LIC Enablement Package
This package is required if you plan to use the Context Menu Service to
manage launch-in-context actions for deployed assets. See the Planning
section of the information center for information about options for
launch-in-context actions.

50 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 CI AppsCMS LIC Enablement Package
This package is required if you plan to use the Context Menu Service to
manage launch-in-context actions for actual configuration items. See the
Planning section of the information center for information about options
for launch-in-context actions.
Rational ClearQuest OSLC Integrations
This integration enables you to use the Open Services for Lifecycle
Collaboration (OSLC) technology to link from the Problems application to
Rational ClearQuest to share information about problems and their
solutions.
Rational Team Concert™ OSLC Integrations
This integration enables you to use the Open Services for Lifecycle
Collaboration (OSLC) technology to link from the Problems application to
Rational Team Concert to share information about problems and their
solutions.

If you do not install integration modules during the product installation process,
you can install them later. If you install them later, you must update the database
and rebuild and deploy the maximo.ear file.

Language deployment after database update deferral

Selecting the option to defer the update of the Maximo database when installing
the product, affects how you deploy languages.

During installation, you have the option to defer the database update task. This
option prevents writing data to the database during the installation. The
installation program is limited to copying files to the administrative system and
registering product process solution packages. You add languages by completing
the installation, manually updating the database, and then updating languages
manually.
“Manually deploying languages after database update deferral”
Languages must be deployed manually if you defer database updates by the
installation program.

Manually deploying languages after database update deferral

Languages must be deployed manually if you defer database updates by the
installation program.

Before you begin

You must have run updatedb command before manually configuring languages for
PSI packages.

About this task

To manually configure languages for PSI packages, complete the following steps:

Procedure
1. Update language support for the core components.
Files for the language selections you made during the installation are extracted
to the C:\IBM\SMP\Maximo\Tools\Maximo\locale\xliff\ directory on the system.

Chapter 2. Deploying with automatic middleware configuration 51

 a. To update a language as the base language to use for the product, run the
following command:
install_home\maximo\tools\maximo\TDToolkit.bat
-IMPORT
-SLEN
-TLlocale
-maxmessfix
b. To add one or more languages as additional languages for use with the
product, run the following command for each language you want to add:
install_home\maximo\tools\maximo\TDToolkit.bat
-ADDLANGlocale
-maxmessfix
2. Update languages for additional packages.
In order to determine which packages you need to update, change directory to
install_home\maximo\tools\maximo\en\xliff. Each folder located in the xliff
directory, with the exception of MAXUPG folder, is used as input for the
-pmpupdate operation of TDToolkit. Unlike the process for updating languages
for SmartCloud Control Desk, you run the TDToolkit command once for each
package. TDToolkit determines which languages are currently deployed and
updates all languages.
a. Change directory to install_home\maximo\tools\maximo\en\xliff. and
identify a package folder to update, for example calibration.
b. Update languages for the chosen package.
C:\IBM\SMP\maximo\tools\maximo\TDToolkit.bat
-pmpupdatepackagedirectory

In this example, pmpupdatepackagedirectory could be pmpupdatecalibration

or pmpupdateconfig_pmp for example.
c. Repeat for each additional package that require language updates.

52 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Chapter 3. Deploying automatically reusing existing
middleware
Use this information to use SmartCloud Control Desk installation programs and
tools to automatically configure existing middleware within your enterprise during
the SmartCloud Control Desk deployment process.

This information provides a high-level overview or road map of tasks you need to
complete in order to deploy SmartCloud Control Desk automatically. You use
middleware already established in your enterprise.

In this scenario, you use the middleware installation program and the SmartCloud
Control Desk installation program to automatically configure existing middleware
resources. Middleware configuration is performed automatically before deploying
the product.

The installation programs are used to automatically configure an existing DB2

server in your environment.

Figure 1. Deploying SmartCloud Control Desk reusing existing middleware

Run the middleware installation program on existing middleware

servers
If you intend to reuse existing middleware servers with SmartCloud Control Desk,
they must be configured before you run the SmartCloud Control Desk installation
program.

This section contains information about configuring existing DB2 servers for use
with SmartCloud Control Desk using the middleware installation program.

Information for using the middleware installation program with IBM Tivoli
Directory Server is included.

Details are provided for using the middleware installation program with Microsoft
Active Directory.

You cannot use the middleware installation program to configure existing Oracle
servers.

The middleware installation program cannot configure an existing WebSphere

Application Server Network Deployment deployment.

Microsoft SQL Server cannot be configured using the middleware installation

program.

Ensure that all of your middleware is at supported levels for SmartCloud Control
Desk.

© Copyright IBM Corp. 2012 53

 When you install and configure middleware in the middleware installation
program and the SmartCloud Control Desk installation program, consider the
following special characters restrictions:
Table 5. Middleware object naming conventions
Naming Convention
DB2 naming conventions for Group names,
user names, and user IDs.
DB2 naming conventions for DB2 instances.
DB2 naming conventions for passwords.
IBM Tivoli Directory Server conventions for
databases and database aliases.
54 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Details
Group names and user IDs on Linux and
UNIX operating systems can contain up to 8
characters and must consist of lowercase
characters only.
Group names and user names on Windows
can contain up to 30 characters.
Names and IDs cannot be any of the
following values: USERS, ADMINS,
GUESTS, PUBLIC, LOCAL, or any
SQL-reserved word.
Names and IDs cannot begin with IBM, SQL
or SYS. They must also not begin with the
underscore (_) character.
Instance names can have up to 8 characters.
On Windows, no instance can have the same
name as a service name.
For UNIX systems, passwords can be a
maximum of 8 characters.
For Windows systems, passwords can be a
maximum of 14 characters.
Database names must be unique within the
location in which they are cataloged. For
Linux and UNIX , this location is a directory
path. For Windows it is a logical disk.
Database alias names must be unique within
the system database directory. When a new
database is created, the alias defaults to the
database name. As a result, you cannot
create a database using a name that exists as
a database alias, even if there is no database
with that name.
Database and database alias names can have
up to 8 characters.
Be mindful that the special characters @, #,
and $ are not common to all keyboards.
Avoid these characters when you create a
database name.
 Table 5. Middleware object naming conventions (continued)
Naming Convention
IBM Tivoli Directory Server conventions for
users, groups, databases, and instances
WebSphere Application Server Network
Deployment conventions
The middleware installation program
Configuring an existing DB2 with the middleware installation
program
An existing DB2 server can be configured with the middleware installation
program.
Chapter 3. Deploying automatically reusing existing middleware (Scenario 2)
Details
Values must not be longer than 8 characters.
Values cannot be any of the following:
USERS, ADMINS, GUESTS, PUBLIC,
LOCAL, or idsldap
Values cannot begin with IBM, SQL, or SYS.
Values must not include accented characters.
Values can include characters A through Z, a
through z, and 0 through 9.
Values must begin with characters A
through Z or a through z.
Double-byte characters cannot be used in
administrator passwords values.
Passwords cannot contain the following
special characters: ` ' \ " |
The administrator name cannot contain the
following characters: / \ * ,: ;=+?|< > & %
'"] [> # $ ~ ( )
The administrator name cannot begin with a
period.
The administrator name cannot contain
leading and trailing spaces.
The administrator password must consist of
8 characters.
The middleware installation program does
not validate that your password is compliant
with the operating system of the target host.
Ensure that the password values you
provide are valid for your environment.
The middleware installation program does
not allow the use of the '%' character on
Windows and the use of the !, $, #, %
characters on UNIX.
The middleware installation program does
not check for accented characters in user
name values. The use of accented characters
can cause errors.
55
 Before you begin

If you plan to configure an existing DB2 server with the middleware installation
program, a set of users and groups must exist. These users and groups are used by
the middleware installation program during configuration.

Default values for users and groups include:

Users
v db2admin
v dasusr1 (UNIX)
v db2fenc1 (UNIX)
Groups
v db2admns (Windows)
v dasadm1 (UNIX)
v dbgrp1 (UNIX)
v db2fgrp1 (UNIX)

These values are default user and group values. These values can be customized if
the values provided to the middleware installation program match the values
found on the system. Again, if these users do not exist on the system, you must
create them before you run the installation program.

About this task

If you have an existing DB2 installation that you would like to reuse for
SmartCloud Control Desk, you can run the middleware installation program on the
system to configure it. The middleware installation program identifies instances of
middleware that exist on the system that are compatible with SmartCloud Control
Desk, and it configures the existing instance for use with SmartCloud Control
Desk.

To have the middleware installation program configure an existing DB instance for

reuse with SmartCloud Control Desk, complete the following steps:

Procedure
1. Log in as a user with administrative authority.
2. Start the middleware installation program from the launchpad.
3. Complete the middleware installation program panels until you reach the
Deployment Choices panel.
4. From the Deployment Choices panel, select Database Server, and then click
Next. The middleware installation program displays any instances of DB2
found on the system.
5. From the Installation menu, select the appropriate instance to reuse, and then
click Next.
6. Complete the remainder of the middleware installation program panels.
“Installing middleware using the middleware installation program” on page 19
You use the middleware installation program to install middleware components
for use with IBM SmartCloud Control Desk. The middleware components that
you choose to install, and the associated configuration parameters, are recorded
in a deployment plan for the target system.

56 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Verifying an existing IBM Tivoli Directory Server using the
middleware installer
If you have an existing IBM Tivoli Directory Server installation that you would like
to reuse for SmartCloud Control Desk, you can verify that it works with
SmartCloud Control Desk using the middleware installer.

About this task

The middleware installer validates the following items:

v The version of IBM Tivoli Directory Server is compatible with SmartCloud
Control Desk.
v The IBM Tivoli Directory Server is running.
v The Base DN information that you supply in the middleware installer panels are
present in the IBM Tivoli Directory Server you are using.
The middleware installer does not create an instance of IBM Tivoli Directory
Server for use with SmartCloud Control Desk. If you want to reuse an existing
instance of IBM Tivoli Directory Server, supply the correct Administrator
Distinguished Name and password, LDAP BASE DN, directory server port, and
the administration port information for that instance on the middleware installer
panels when prompted. If you intend to host a new instance on your existing
IBM Tivoli Directory Server, you must create it before you run the middleware
installer.

Note: While you can technically share a DB2 instance between SmartCloud
Control Desk and the one required by IBM Tivoli Directory Server, it is not a
recommended practice. During the installation, the database instance is restarted,
which might disrupt the availability of IBM Tivoli Directory Server in your
enterprise. If you are using the automated installers, separate instances are
created for use by SmartCloud Control Desk and IBM Tivoli Directory Server.

To have the middleware installer verify an existing instance of IBM Tivoli Directory
Server for reuse with SmartCloud Control Desk, complete the following steps.

Procedure
1. Log in to the system as a user with administrative authority.
2. Start the middleware installer from the product launchpad.
3. Navigate the middleware installer panels up to the point where you reach the
deployment choices panel.
4. In the deployment choices panel, select Directory Server, and then click Next.
The middleware installer displays any instances of IBM Tivoli Directory Server
discovered on the system.
5. In the Installation menu, select the appropriate instance to reuse, and then click
Next.
6. Complete the installation by navigating the rest of the middleware installer
panels.
“Manually configuring the directory server” on page 83
These topics provide details on manually configuring a directory server for use
by SmartCloud Control Desk
“Installing middleware using the middleware installation program” on page 19
You use the middleware installation program to install middleware components
for use with IBM SmartCloud Control Desk. The middleware components that

Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 57

 you choose to install, and the associated configuration parameters, are recorded
in a deployment plan for the target system.

Preparing Microsoft Active Directory for reuse

An existing Microsoft Active Directory instance can be used to secure WebSphere
Application Server Network Deployment. The middleware installation program
can be used to validate Microsoft Active Directory configuration information.

Before you begin

Before running the installation program, manually create the users. You can
complete this task after you run the middleware installation program, but you
must complete it before you run the SmartCloud Control Desk installation
program.

About this task

The middleware installation program prompts you for LDAP configuration
parameters to use with WebSphere Application Server Network Deployment.

To validate Microsoft Active Directory configuration information using the

middleware installation program use, complete the following steps:

Procedure
1. Log in as a user with administrative authority.
2. Start the middleware installation program from the launchpad.
3. Proceed through the middleware installation program panels until you reach
the Deployment Choices panel.
4. From the Deployment Choices panel, clear the Directory Server deployment
option, and then click Next. In the next panel, you are given the choice of
selecting an existing instance of IBM Tivoli Directory Server or Microsoft
Active Directory to secure WebSphere Application Server Network
Deployment.
5. In the Deployment Plan Summary window, click Next to configure
parameters. The deployment plan is generated and you are provided details
about the plan.
6. In the Configurable Host Name panel, you can manually specify the host
name of the system you are running the installation from. Select the Override
the local machine hostname option and enter a host name value in the
Hostname field. Select this option only if you want to manually specify the
host name of the system instead of having the installation program
programmatically detect it. This option is useful when there is more than one
host name assigned to the system. This configuration occurs when a system
has more than one network interface, or it is configured to support virtual IP
addresses. When this option is selected, you are required to provide a
resolvable host name. You cannot clear this option after it is selected.
However, you can still change the value of the Hostname field. If you started
the middleware installation program from the command line using the
forceHostname=true parameter, then you are required to provide an
alphanumeric value in the Hostname field. Use of an IP address causes error
message. When this option is selected, you are not able to clear it. However,
you can change the value you enter in the Hostname field.
7. In the password reuse panel, you can optionally select Use this password as
the value for all subsequent passwords. Select this option to use the same

58 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 password as the default user password value in all panels of the middleware
installation program. If you do not want to use this option, ignore the Use
this password as the value for all subsequent passwords option, and click
Next.
8. Select Secure with Microsoft Active Directory, and click Next.
9. Configure the following values for WebSphere Application Server Network
Deployment security, and then click Next.
LDAP Host name
Enter the fully qualified name of the server hosting Microsoft Active
Directory.
LDAP base entry
Enter the LDAP base entry of the instance. For example,
DC=ism75,DC=com
User suffix
Enter the user suffix for the instance. For example,
OU=Users,OU=SWG,DC=ism75,DC=com
Group suffix
Enter the group suffix for the instance. For example,
OU=Groups,OU=SWG,DC=ism75,DC=com
Organization container suffix
Enter the organization container suffix for the instance. For example,
DC=ism75,DC=com
In this example. ism75 is the domain name. You must replace ism75
with the name of your own domain.
10. Supply the following configuration values for WebSphere Application Server
Network Deployment security, and then click Next.
Bind distinguished name
Enter the bind distinguished name for the instance. For example,
CN=Administrator,CN=Users,DC=ism75,DC=com
This value assumes that the Administrator user is already a member
of the ism75 domain. You must replace ism75 with the name of your
own domain.
Bind password
Enter the password for the Administrator user on the system hosting
Microsoft Active Directory.
11. Finish the installation by completing the remainder of the middleware
installation program panels.
“Installing middleware using the middleware installation program” on page 19
You use the middleware installation program to install middleware components
for use with IBM SmartCloud Control Desk. The middleware components that
you choose to install, and the associated configuration parameters, are recorded
in a deployment plan for the target system.
“Manually configuring Microsoft Active Directory” on page 87
You can manually configure Microsoft Active Directory for use with
SmartCloud Control Desk.

Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 59

Installation program overview
The SmartCloud Control Desk installation program provides an interface for
installing and deploying SmartCloud Control Desk, which includes the process
automation engine and process managers.

The SmartCloud Control Desk installation program records choices you make
about your SmartCloud Control Desk deployment. It records configuration
parameters associated with those choices, and then installs and deploys
SmartCloud Control Desk based upon the information you entered.

There are two installation paths available to you when you are installing
SmartCloud Control Desk.
Simple
A simple deployment consists of installing SmartCloud Control Desk
middleware on one system. You do not have the option of using existing
middleware within your organization with SmartCloud Control Desk. All
middleware used with SmartCloud Control Desk must be installed on the
system with the middleware installation program with default values.
SmartCloud Control Desk is installed with default values provided by the
middleware installation program and SmartCloud Control Desk installation
program.
If you intend to override default values used by the simple deployment
path, you must use the custom deployment path instead.
Custom
A custom deployment typically involves deploying SmartCloud Control
Desk across several systems. Some of these systems might already host
middleware products that you want to use with your SmartCloud Control
Desk deployment. You can modify default installation values when you
deploy with the custom installation path.
This deployment option does not require you to spread the SmartCloud
Control Desk deployment across several systems. You can enter the name
of the local host as the destination for all SmartCloud Control Desk
components.

The SmartCloud Control Desk installation program can automate the configuration
of some middleware for use with SmartCloud Control Desk.

If you choose not to have the SmartCloud Control Desk installation program
automatically configure middleware, you must configure that piece of middleware
manually before the installation of SmartCloud Control Desk.

Important: When you are entering LDAP values for SmartCloud Control Desk
installation panel fields, be aware of the product-specific syntax rules for using
special characters in an LDAP string. In most cases, special characters must be
preceded by an escape character in order to make it readable by the directory
server. Failing to escape special characters contained in an LDAP string used with
SmartCloud Control Desk results in SmartCloud Control Desk errors.

Many directory server products consider a blank space as a special character that is
part of the LDAP string. If you enter an LDAP string with an unescaped blank
character at the end of a field value, you encounter SmartCloud Control Desk
errors.

60 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 For more information about special character usage in LDAP strings, see the
product documentation for your directory server.

Information that you enter for the SmartCloud Control Desk installation program
is stored in the maximo.properties and install.properties files and the Maximo
database. These values are populated into the panel fields of the SmartCloud
Control Desk installation program on subsequent uses of the program. If you
cancel the installation program, it recalls most values that you entered the next
time you start it. Values excluded from being saved in this manner are the
SmartCloud Control Desk installation directory and the shortcut option chosen
during the installation. You can restore the default values in the SmartCloud
Control Desk installation program by deleting <Maximo_Home>/applications/
maximo/properties/maximo.properties and <Maximo_Home>/etc/
install.properties. If you cannot locate the maximo.properties file in the
<Maximo_Home> directory, look for it in the system temp file directory.

Simple installation path values

Specific simple path installation values are required by the SmartCloud Control
Desk installation program.

If you elect to install SmartCloud Control Desk through the simple installation
path, the following values are set. You must provide values where indicated.

For simple installations, you supply a single host name for middleware. The
SmartCloud Control Desk installation program expects this host to contain all the
software that works with SmartCloud Control Desk.
Table 6. SmartCloud Control Desk Simple Installation Path Values
Category Field Value Provided by User?
Deployment Option Deployment simple
Database Database type DB2
Configuration
Database Host name Yes
Configuration
Database Port 50005
Configuration
Database Database name maxdb75
Configuration
Database Instance ctginst1
Configuration
Database User ID Yes
Configuration
Database Automate database yes
Configuration configuration
Database Remote access user Yes
Configuration ID
Database Database installation
Windows
Configuration directory
C:\Program
Files\IBM\
SQLLIB

Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 61

 Table 6. SmartCloud Control Desk Simple Installation Path Values (continued)
Category Field Value Provided by User?
Database Instance Yes
Windows
Configuration administrator user ID
db2admin
Database Windows service db2admin
Configuration user ID
Database Data table space maxdata
Configuration name
Database Data table space size medium
Configuration
Database Temporary table maxtemp
Configuration space name
Database Temporary table 1000
Configuration space size
IBM WebSphere Host name Yes
Application Server
Connectivity
IBM WebSphere SOAP port 8879
Application Server
Connectivity
IBM WebSphere IBM WebSphere
Windows
Application Server Application Server
C:\Program
Configuration server home
Files\IBM\
directory
WebSphere\
AppServer
IBM WebSphere User name wasadmin Yes
Application Server
Configuration
IBM WebSphere Profile name ctgDmgr01
Application Server
Configuration
IBM WebSphere Automate IBM yes
Application Server WebSphere
Configuration Application Server
configuration
IBM WebSphere Remote access user Yes
Application Server ID
Configuration
IBM WebSphere Web server port 80
Application Server
Configuration
IBM WebSphere Web server name webserver1
Application Server
Configuration
IBM WebSphere Node name ctgNode01
Application Server
Configuration
IBM WebSphere Cluster name MAXIMOCLUSTER
Application Server
Configuration

62 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Table 6. SmartCloud Control Desk Simple Installation Path Values (continued)
Category Field Value Provided by User?
IBM WebSphere Application server MXServer This value
Application Server cannot be changed.
Configuration
Integration Adapter JMS data source meajmsds
JMS Configuration name
Integration Adapter Persist JMS messages no
JMS Configuration
Security Use default schema yes
Configuration
Security Create users yes
Configuration automatically
Maximo Install directory C:\IBM\SMP Yes
Configuration
Configuration Step Run configuration yes
now

Installing the product and automatically configuring

middleware
To install SmartCloud Control Desk, you run the installation program from the
launchpad. The installation procedure automatically configures middleware on
multiple servers, using default values.

Before you begin

Ensure that you meet prerequisite conditions.

v The database server, the directory server, and application server services must be
started and active.
v The /tmp and /var/tmp directories must be present on the system. The
installation program depends on these directories for information during
deployments on IBM WebSphere Application Server Network Deployment.
v On the administrative workstation, temporarily shut down any noncritical
processes that can have a negative effect on the installation, such as antivirus
software.
v Ensure that the Windows DEP setting does not prevent the launchpad from
running: Select Start > Settings > Control Panel > System > Advanced >
Performance > Settings > Data Execution Prevention. Select Turn on DEP for
essential Windows programs and services only and click Apply. You might be
asked to reboot the server.
v For Linux and UNIX systems with middleware installed, the command hostname
-f must return a fully qualified host name. If necessary, consult the
documentation for your operating system. Alternatively, you can provide the IP
address for the system.
v Enable a remote execution and access service on every system that has
middleware installed. Each remote system must support a remote access
protocol. It must also accept remote logins from a user name and password that
were configured on the target server. Remote access protocols include SSH and

Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 63

 Windows SMB. If the remote system is a Windows server, you must configure
remote execution and access to use SMB.
v The DB2 database must be prepared.
– If DB2 is installed on a Linux or UNIX system, you must create the instance
user and the home directory for the user on the DB2 server.
– The database instance owner home directory must have 8 GB of space
available regardless of whether a database is installed in that location.
– The user ID for the DB2 instance administrator must have SYSADM (system
administration) authority. You specify this user ID during the product
installation program. See the DB2 product documentation for information
about creating a user with SYSADM authority on the DB2 server. You must
add root to a group with SYSADM authority for UNIX systems.

About this task

The instructions are for a multiple server installation that uses default values.

If you experience problems with the user interface of the installation program
when installing on AIX 6.x systems remotely, reattempt the installation locally. Use
the console or an X terminal on the system locally.

Procedure
1. Log in on the administrative system.
2. Start the product installation program from the launchpad.
a. Start the launchpad. Browse to the root directory of the downloaded
installation image, and run the following command:
Windows
launchpad.exe
UNIX launchpad.sh
If the launchpad does not start the installation, you can start the product
installation program directly. On the downloaded installation image, browse
to \Install\\, and run one of the following commands:
Windows
v install.bat
v install_win64.bat
UNIX
v install_aix64.sh
v install_linux32.sh
v install_linux64.sh
3. Select a language for the installation and click OK.
4. On the Choose Installation Folder panel, specify the path to the location
where you want to install SmartCloud Control Desk.
You can specify a description for the installation. A description is useful for
differentiating between multiple installations that are hosted on the same
administrative workstation.
5. Review the information that is on the Verify Installation Location panel. The
panel shows any previous installation information that was found based on
the installation directory that you specified on the previous panel. After you
advance past this panel, you cannot go back and change the installation
directory for this installation.

64 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 If a more recent version of the installation program is found in the specified
target directory, you are notified. The notification means that you are using an
older version of the installation program. The version found on the
administrative workstation is newer and can contain important features and
enhancements. To use the newer version of the installation program, select the
option on the notification panel and click Next. This action exits the current
installation process and restarts the installation process with the newer
installation program. If you do not select the option, you continue the
installation with the older version of the installation program.
6. On the Package Summary panel, review the package deployment information.
This panel lists version information for both new and existing packages on the
system. Target package version information indicates the package version
being currently deployed.
7. On the Choose Deployment panel, specify Simple or Custom as the
deployment type.
8. On the Import Middleware Configuration Information panel, you select
Import middleware configuration information to have the product
installation program reuse the middleware installation program values. These
values are used as default values for the same fields in the product
installation program.
The Workspace location field refers to the location of the topology file that
contains the values that were specified for the middleware installation
program. The file is located in the workspace that was defined during the
middleware installation task. For example, C:\ibm\tivoli\mwi\workspace for
Windows or /root/ibm/tivoli/mwi/workspace for UNIX.
If you selected the simple deployment, the middleware default information is
not used.
9. On the Database Type panel, specify the software to use for the Maximo
database.
10. On the Database panel, specify configuration information for your database
software.
For things such as the database user ID, the database name, the database
instance for SmartCloud Control Desk, and the schema name, if the values do
not exist when you specify them, they are created.
For DB2, the user ID cannot be the same as the instance administrator user ID.
Database users and database instance names cannot contain spaces.
For DB2, the database instance is created if it does not exist, but the user and
its associated home directory must exist on the DB2 server. For DB2, the
schema name can be the same value as the owner of the table spaces that are
defined or it can be a different value, such as maximo.
After you specify configuration information for your database software, the
installation program validates the information with the database server.
11. On the Automate Database Configuration panel, you can specify that database
creation and configuration is to be automated.
If you do not select the option, you must configure the database manually.
12. On the Remote Access Authorization panel, specify authorization information
for the automatic database configuration feature. Specifying the values enables
remote configuration.
13. On the Database Administration panel, specify configuration information
about the database. The required information varies by database platform.

Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 65

 For DB2, the instance administrator user ID cannot be the same as the
database user ID. And the Windows service user ID must have administrative
authority on the system.
14. On the Database Tablespace panel, specify information about the table space
of the database.
When you click Next, the product installation program connects to the
database server and validates the information that you specified.
15. When the database validation is complete, on the Application Server Type
panel, specify the application server type for the product deployment.
You have the option of configuring WebSphere Application Server Network
Deployment automatically through the product installation program.
16. On the WebSphereConnectivity panel, specify host information for the
WebSphere Application Server Network Deployment.
17. On the WebSphere Remote Access Authorization panel, specify authorization
information for WebSphere Application Server Network Deployment
configuration.
18. On the WebSphere Application Server Network Deployment Configuration
panel, specify configuration information for WebSphere Application Server
Network Deployment.
The web server port must match an existing HTTP server port value that you
configured when you set up WebSphere Application Server Network
Deployment. If you specify a different value for the web server port, you must
restart WebSphere Application Server Network Deployment at the conclusion
of the installation. Restarting the server activates the new port and makes it
available for incoming requests.
The application server name that you specify is created if it does not exist.
19. On the Security panel, specify the method to use for authenticating and
authorizing users.
20. On the Specify Maximo Users panel, enter Maximo database user information.
Maximo administration user
The product administrator user ID that is used for initial configuration
and adding users.
Maximo system registration user
The user ID that is used for the self-registration of users.
Maximo system integration user
The user ID that is used with enterprise adapters.

Custom user ID and password values are stored in the Maximo database. The
default user IDs of maxadmin, maxreg, and maxintadm are also created as
users in the Maximo database. Creation of the default user IDs is done for
internal processing purposes. If you use Maximo database security for
authentication and authorization, the default user IDs can be used to log in to
the application. If you regard this condition as a security risk, you can modify
the passwords for the default user IDs. You modify passwords for the user
IDs in the Users application.
21. On the Security panel, specify the names of the user and group base entries
and specify how SmartCloud Control Desk users are created.
User base entry
If you do not plan to use the default LDAP schema that is provided
with SmartCloud Control Desk, specify the user base entry that you
want to use.

66 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Group base entry
If you do not plan to use the default LDAP schema , specify the group
base entry that you want to use.
You can specify that the installation program creates the required users.
Otherwise, you must create users manually before continuing.
If you are not using the default LDAP schema that is provided, you must
create it yourself before advancing beyond this panel. The values that are
specified for the User base entry and Group base entry fields are used to
configure the VMMSYNC cron task. To create your own LDAP schema and
create users manually, you can modify the default add-on LDIF data and
import it into your LDAP repository
22. On the Integration Adapter JMS Configuration panel, specify Java Message
Service configuration information. A JMS server requires a DB2 data
repository to be configured to maintain messages. If you are using another
database type, you cannot configure message persistence. If you specify that
JMS messages are not to be persisted, you can configure the JMS
implementation manually later.
Specify the name of the database to be used by JMS. For DB2, you can specify
whether to persist JMS messages within DB2.
Select Do not persist JMS messages if you are deploying SmartCloud Control
Desk with Oracle or Microsoft SQL Server. When you click Next, the
installation wizard skips to the SMTP Configuration panel.
23. If you specified that JMS messages should persist, specify additional JMS
configuration information in the DB2 Database Server Configuration panel.
The JMS data store can be created as a DB2 database only.
24. If you specified that JMS messages should persist, specify authorization
information for the automatic configuration feature in the DB2 Database
Server Remote Access Authorization panel.
For Windows, the user ID must be a member of the DB2ADMNS group.
For Linux or UNIX, the user ID must be root and a member of a group with
SYSADM authority for the database instance.
25. If you specified that JMS messages should persist, specify additional DB2
information in the DB2 Database Instance Configuration panel.
26. On the SMTP Configuration panel, specify the SMTP configuration
information that is used by workflows to communicate with workflow
participants.
The administrator e-mail address is the e-mail address that is used to send
messages. If you leave the fields blank, you must configure the SMTP
parameters through the product interface as a post-installation task.
27. On the Data Integration and Context Menu Services Options panel, click the
option that indicates where the database tables for these functions are created:
in the Maximo ("same") database, or in a separate database instance that you
created for this purpose. If you are installing the Entry edition, choose the
Maximo database. These tables are created but are not used by the Entry
edition.
28. On the Base Language Selection panel, specify the base language for the
installation.
29. On the Additional Language Selection panel, you can optionally specify one
or more additional languages that the installation is to support.
30. On the Run Configuration Step panel, specify how to perform the
configuration step of the installation. If you do not select an option, the
configuration step proceeds when you click Next.

Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 67

 Copy files now, but perform the installation configuration step later
Select this option to copy files from the installation source to the
administrative workstation. You must perform the configuration step
at a later time to complete the deployment.

Important: Do not install another product before you complete the

configuration step of the original installation. Installing another
product before you run the configuration step for this installation
overwrites the taskstore, which prevents the original installation from
ever being deployed.
The configuration values that you specify are stored in the
install_home\maximo\applications\maximo\properties\
maximo.properties and install_home\etc\install.properties files.
You run the configuration steps outside of the product installation
program by using the taskrunner utility, in the install_home\scripts
directory. Run the taskrunner utility from the command line.
install_home\scripts\taskrunner [CONTINUE <STOPONERROR|NOSTOPONERROR>]

The taskrunner uses the configuration values that are stored in the
maximo.properties and install.properties files to configure
SmartCloud Control Desk.
If you run taskrunner with the NOSTOPONERROR parameter, the
taskrunner continues despite errors. If you run taskrunner with the
STOPONERROR parameter, the taskrunner stops when it encounters an
error. If you used STOPONERROR, you can rectify the conditions that
caused the error. You can then resume the installation where the last
successfully completed task was recorded in the previous attempt by
starting taskrunner with the CONTINUE parameter.
Deploy application files manually later
Select this option to manually deploy application files to the
application server.
Defer the update of the Maximo database
Select this option if you want to manually run the database update
task for the product deployment. This option can be used when there
is a fix pack available that addresses known issues with the updatedb
script. In this scenario, you choose the Defer the update of the
Maximo database option, apply the fix pack, and then run the
updatedb -v1 command manually.
31. On the Choose Shortcut Folder panel, specify where you want SmartCloud
Control Desk icons created.
If you select In the Start Menu and use Internet Explorer, add the
SmartCloud Control Desk URL to the trusted sites web content zone. Disable
the option that requires server verification for all sites in the zone.
Do not select In the Quick Launch Bar. The selection does not create a
shortcut in the Quick Launch bar.
Attention: Shortcuts are created for Windows systems only. Because
WebLogic Server deployments are a manual process, you must manually
update any shortcuts that you create. You update shortcuts after you
manually deployed the SmartCloud Control Desk EAR files.
32. On the Input Summary panel, review the information that you provided for
the product installation program.
If necessary, use Previous to return to previous panels to change values.

68 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 33. On the Pre-Installation Summary panel, review the installation information,
then click Install.
The installation process begins. You can monitor the progress of the
installation by viewing the messages that are shown.
34. On the Installation Completed panel, review any information presented, then
click Done.
Attention: In some cases, on AIX systems, the Installation Completed panel
might appear blank. Click Done to exit the installation program.
“Restarting middleware on Windows” on page 231
This procedure describes how to restart middleware on Windows, if you must
restart any middleware services.
“Restarting middleware on UNIX” on page 232
Middleware services on Linux and AIX platforms occasionally must be
restarted, such as when a reboot occurs. Middleware servers and services must
be active before running the SmartCloud Control Desk installation program.

Installing optional content

Install the relevant optional content package for your edition of the product.

Optional content is often used in development environments as a way to begin

developing your own content.

If you do not install optional content during the product installation process, you
can install it later. If you install it later, you must update the database and rebuild
and deploy the maximo.ear file.

Installing optional integration modules

Install integration module packages in order to set up integrations with other
products.

You can install these integration modules from the Integrations page of the
launchpad:
IBM Tivoli Provisioning Manager Integration Module
This integration module enables you to integrate Tivoli Provisioning
Manager with the release management process. For example, you can use
Tivoli Provisioning Manager as a Definitive Media Library. See the Release
management section of the information center for more information about
this integration.
Deployed Assets CMS LIC Enablement Package
This package is required if you plan to use the Context Menu Service to
manage launch-in-context actions for deployed assets. See the Planning
section of the information center for information about options for
launch-in-context actions.
CI AppsCMS LIC Enablement Package
This package is required if you plan to use the Context Menu Service to
manage launch-in-context actions for actual configuration items. See the
Planning section of the information center for information about options
for launch-in-context actions.
Rational ClearQuest OSLC Integrations
This integration enables you to use the Open Services for Lifecycle

Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 69

 Collaboration (OSLC) technology to link from the Problems application to
Rational ClearQuest to share information about problems and their
solutions.
Rational Team Concert OSLC Integrations
This integration enables you to use the Open Services for Lifecycle
Collaboration (OSLC) technology to link from the Problems application to
Rational Team Concert to share information about problems and their
solutions.

If you do not install integration modules during the product installation process,
you can install them later. If you install them later, you must update the database
and rebuild and deploy the maximo.ear file.

Language deployment after database update deferral

Selecting the option to defer the update of the Maximo database when installing
the product, affects how you deploy languages.

During installation, you have the option to defer the database update task. This
option prevents writing data to the database during the installation. The
installation program is limited to copying files to the administrative system and
registering product process solution packages. You add languages by completing
the installation, manually updating the database, and then updating languages
manually.
“Manually deploying languages after database update deferral” on page 51
Languages must be deployed manually if you defer database updates by the
installation program.

Manually deploying languages after database update deferral

Languages must be deployed manually if you defer database updates by the
installation program.

Before you begin

You must have run updatedb command before manually configuring languages for
PSI packages.

About this task

To manually configure languages for PSI packages, complete the following steps:

Procedure
1. Update language support for the core components.
Files for the language selections you made during the installation are extracted
to the C:\IBM\SMP\Maximo\Tools\Maximo\locale\xliff\ directory on the system.
a. To update a language as the base language to use for the product, run the
following command:
install_home\maximo\tools\maximo\TDToolkit.bat
-IMPORT
-SLEN
-TLlocale
-maxmessfix
b. To add one or more languages as additional languages for use with the
product, run the following command for each language you want to add:

70 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 install_home\maximo\tools\maximo\TDToolkit.bat
-ADDLANGlocale
-maxmessfix
2. Update languages for additional packages.
In order to determine which packages you need to update, change directory to
install_home\maximo\tools\maximo\en\xliff. Each folder located in the xliff
directory, with the exception of MAXUPG folder, is used as input for the
-pmpupdate operation of TDToolkit. Unlike the process for updating languages
for SmartCloud Control Desk, you run the TDToolkit command once for each
package. TDToolkit determines which languages are currently deployed and
updates all languages.
a. Change directory to install_home\maximo\tools\maximo\en\xliff. and
identify a package folder to update, for example calibration.
b. Update languages for the chosen package.
C:\IBM\SMP\maximo\tools\maximo\TDToolkit.bat
-pmpupdatepackagedirectory

In this example, pmpupdatepackagedirectory could be pmpupdatecalibration

or pmpupdateconfig_pmp for example.
c. Repeat for each additional package that require language updates.

Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 71

72 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Chapter 4. Deploying manually reusing existing middleware
Use this information if you intend to deploy SmartCloud Control Desk by reusing
existing middleware servers and manually configuring them to work with
SmartCloud Control Desk.

This information provides a high-level overview or road map of tasks you need to
complete in order to deploy SmartCloud Control Desk automatically, using
middleware already established in your enterprise.

In this scenario, you manually configure existing middleware resources before

running the SmartCloud Control Desk installation program.

Figure 2. Deploying SmartCloud Control Desk with manual middleware configuration

SmartCloud Control Desk installation with manual middleware

configuration
Manually configured installations involve configuring middleware components, the
database server, the directory server, and the J2EE server, to work with SmartCloud
Control Desk before using the SmartCloud Control Desk installation program.

You can elect to have one or more SmartCloud Control Desk middleware
components configured automatically by the SmartCloud Control Desk installation
program. Alternatively, you can choose to manually configure one or more of the
middleware servers to work with SmartCloud Control Desk.

The information contained in this section provides details on how to manually

configure SmartCloud Control Desk middleware before running the SmartCloud
Control Desk installation program.

Before you begin, ensure you have addressed the following prerequisite conditions:
v You have designated a Windows or UNIX-based server to start the SmartCloud
Control Desk installation program.
v For WebSphere Application Server Network Deployment, ensure that the Cell
and all related nodes are active.

You must complete the manual configuration of each server you plan to not
configure using the autoconfigure feature of the SmartCloud Control Desk
installation program before you actually use the SmartCloud Control Desk
installation program to install SmartCloud Control Desk.

Ensure that all of your middleware is at supported version levels.

Manually configuring the database

You have the option of manually configuring the database server used in
SmartCloud Control Desk deployment. Manual configuration of the database
server must be completed before you use the SmartCloud Control Desk installation
program.

© Copyright IBM Corp. 2012 73

 For DB2 on UNIX and Linux, a minimum of 8 gigabytes (binary) free of space is
required for DB2 table spaces. This space must be available to the database
instance home directory (/home/ctginst1).

For DB2 on Windows, ensure that you have a minimum of 8 gigabytes of free
space in the DB2 installation directory.

Manually configuring DB2 9.x

This section contains instructions for manually configuring DB2 9.x servers for use
by SmartCloud Control Desk.

About this task

To configure an existing DB2 9.x server for use with SmartCloud Control Desk,
complete the following steps before starting the SmartCloud Control Desk
installation program:

Procedure
1. Log in to the system as a user that has administrative permissions on the
system.
2. Create system users if they do not exist on the system.
v Windows
– db2admin
– maximo
v Linux or UNIX
– db2admin
– maximo
– ctgfenc1
– ctginst1
The ctginst1 user ID must be assigned to the db2iadm1 group.
3. Open a console window and set up the DB2 environment:
v Windows
db2cmd
v Linux or UNIX
Ensure that the /opt/ibm/db2/V9.7/bin, /opt/ibm/db2/v9.7/instance, and
/opt/ibm/db2/V9.7/adm directories are added to your PATH.
4. Create the DB2 instance:
v Windows
db2icrt -s ese -u db2admin,myPassword -r 50005,50005 ctginst1
set db2instance=ctginst1
db2start
db2 update dbm config using SVCENAME 50005 DEFERRED
db2stop
db2set DB2COMM=tcpip
db2start

v Linux orUNIX
db2icrt -s ese -u db2fenc1 -p 50005 ctginst1
. /home/ctginst1/sqllib/db2profile
db2start
db2 update dbm config using SVCENAME 50005 DEFERRED
db2stop
db2set DB2COMM=tcpip
db2start

5. Create the database.

db2 create db ’maxdb75’ ALIAS ’maxdb75’ using codeset UTF-8 territory US pagesize 32 K
db2 connect to ’maxdb75’
db2 GRANT DBADM ON DATABASE TO USER db2admin (windows only)
db2 GRANT SECADM ON DATABASE TO USER db2admin (windows only)
db2 connect reset

6. Configure the database.

74 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
 db2 update db cfg for maxdb75 using SELF_TUNING_MEM ON
db2 update db cfg for maxdb75 using APP_CTL_HEAP_SZ 16384 DEFERRED
db2 update db cfg for maxdb75 using APPLHEAPSZ 2048 AUTOMATIC DEFERRED
db2 update db cfg for maxdb75 using AUTO_MAINT ON DEFERRED
db2 update db cfg for maxdb75 using AUTO_TBL_MAINT ON DEFERRED
db2 update db cfg for maxdb75 using AUTO_RUNSTATS ON DEFERRED
db2 update db cfg for maxdb75 using AUTO_REORG ON DEFERRED
db2 update db cfg for maxdb75 using AUTO_DB_BACKUP ON DEFERRED
db2 update db cfg for maxdb75 using CATALOGCACHE_SZ 800 DEFERRED
db2 update db cfg for maxdb75 using CHNGPGS_THRESH 40 DEFERRED
db2 update db cfg for maxdb75 using DBHEAP AUTOMATIC
db2 update db cfg for maxdb75 using LOCKLIST AUTOMATIC DEFERRED
db2 update db cfg for maxdb75 using LOGBUFSZ 1024 DEFERRED
db2 update db cfg for maxdb75 using LOCKTIMEOUT 300 DEFERRED
db2 update db cfg for maxdb75 using LOGPRIMARY 20 DEFERRED
db2 update db cfg for maxdb75 using LOGSECOND 100 DEFERRED
db2 update db cfg for maxdb75 using LOGFILSIZ 8192 DEFERRED
db2 update db cfg for maxdb75 using SOFTMAX 1000 DEFERRED
db2 update db cfg for maxdb75 using MAXFILOP 32768 DEFERRED #32-bit Windows
db2 update db cfg for maxdb75 using MAXFILOP 65335 DEFERRED #64-bit Windows
db2 update db cfg for maxdb75 using MAXFILOP 30720 DEFERRED #32-bit UNIX
db2 update db cfg for maxdb75 using MAXFILOP 61440 DEFERRED #64-bit UNIX
db2 update db cfg for maxdb75 using PCKCACHESZ AUTOMATIC DEFERRED
db2 update db cfg for maxdb75 using STAT_HEAP_SZ AUTOMATIC DEFERRED
db2 update db cfg for maxdb75 using STMTHEAP AUTOMATIC DEFERRED
db2 update db cfg for maxdb75 using UTIL_HEAP_SZ 10000 DEFERRED
db2 update db cfg for maxdb75 using DATABASE_MEMORY AUTOMATIC DEFERRED
db2 update db cfg for maxdb75 using AUTO_STMT_STATS OFF DEFERRED
db2 update db cfg for maxdb75 using STMT_CONC LITERALS DEFERRED
db2 update alert cfg for database on maxdb75 using db.db_backup_req SET THRESHOLDSCHECKED YES
db2 update alert cfg for database on maxdb75 using db.tb_reorg_req SET THRESHOLDSCHECKED YES
db2 update alert cfg for database on maxdb75 using db.tb_runstats_req SET THRESHOLDSCHECKED YES
db2 update dbm cfg using PRIV_MEM_THRESH 32767 DEFERRED
db2 update dbm cfg using KEEPFENCED NO DEFERRED
db2 update dbm cfg using NUMDB 2 DEFERRED
db2 update dbm cfg using RQRIOBLK 65535 DEFERRED
db2 update dbm cfg using HEALTH_MON OFF DEFERRED
#
# Windows: AGENT_STACK_SZ 1000
# Unix : AGENT_STACK_SZ 1000
#
db2 update dbm cfg using AGENT_STACK_SZ 1000 DEFERRED
db2 update dbm cfg using MON_HEAP_SZ AUTOMATIC DEFERRED
db2set DB2_SKIPINSERTED=ON
db2set DB2_INLIST_TO_NLJN=YES
db2set DB2_MINIMIZE_LISTPREFETCH=Y
db2set DB2_EVALUNCOMMITTED=YES
db2set DB2_FMP_COMM_HEAPSZ=65536
db2set DB2_SKIPDELETED=ON
db2set DB2_USE_ALTERNATE_PAGE_CLEANING=ON

7. For Linux orUNIX log in as the ctginst1 user and then restart the DB2
command-line environmen
su - ctginst1
db2
8. Restart DB2.
db2stop force
db2start

9. Reconnect to the database.

db2 connect to ’maxdb75’
10. Create a buffer pool.
db2 CREATE BUFFERPOOL MAXBUFPOOL IMMEDIATE SIZE 4096 AUTOMATIC PAGESIZE 32 K

11. Create table spaces.

db2 CREATE REGULAR TABLESPACE MAXDATA PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE INITIALSIZE 5000 M BUFFERPOOL MAXBUFPOOL
db2 CREATE TEMPORARY TABLESPACE MAXTEMP PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE BUFFERPOOL MAXBUFPOOL
db2 GRANT USE OF TABLESPACE MAXDATA TO USER MAXIMO

12. Grant authority to maximo.

db2 GRANT DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,IMPLICIT_SCHEMA,
LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT,SECADM ON DATABASE TO USER MAXIMO

db2 GRANT USE OF TABLESPACE MAXDATA TO USER MAXIMO

db2 GRANT CREATEIN,DROPIN,ALTERIN ON SCHEMA MAXIMO TO USER MAXIMO

db2 create schema maximo authorization maximo

13. Break the database connection.

db2 connect reset

14. Exit the DB2 command-line environment

15. Install the appropriate fix pack indicated in the prerequisites topic in the
chapter that describes how to prepare for the installation. Ensure that you
review and complete all the installation and post-installation tasks contained
within the fix pack readme file. Failure to do so can potentially cause the
SmartCloud Control Desk installation to fail. See the appropriate product
support page for more information.

Chapter 4. Deploying manually reusing existing middleware 75

 Manually configuring Oracle 11g
Use the following instructions to manually configure Oracle 11g for use with
SmartCloud Control Desk.

Before you begin

Oracle instance names must be limited to eight characters in length. For Oracle
databases, the schema owner must use the same user ID as the database user.

About this task

To configure an existing Oracle 11g server for use with SmartCloud Control Desk,
complete the following steps before you start the SmartCloud Control Desk
installation program:

Procedure
1. Log in as the Oracle software user. Typically this user is named oracle.
2. Create the database listener. The listener manages requests to connect to the
database. This step is only required if you do not already have an existing
listener in place.
a. Open the Oracle Network Configuration Assistant application.
b. From the Welcome panel, select Listener configuration, and then click Next.
c. From the action panel, select Add, and then click Next.
d. Enter a name for the listener or accept the default value, and then click
Next.
e. Accept the default Selected Protocols listed by clicking Next.
f. From the port panel, select Use the standard port of 1521, and then click
Next.
g. Select No to indicate that you are finished configuring listeners, and then
click Next.
h. From the Listener Configuration Done panel, click Next.
i. Click Finish.
3. Create a database for use by SmartCloud Control Desk.
a. Open the Oracle Database Configuration Assistant.
b. Click Next.
c. Select Create a Database, and then click Next.
d. Select General Purpose or Transaction Processing, and then click Next.
e. Enter ctginst1 for both the Global Database Name value and the SID value,
and then click Next.
f. Leave the defaults selected, and click Next.
g. Ensure Use the Same Administrative Password for All Accounts is
selected, enter a password for Oracle users, and then click Next.
h. Ensure File System is selected as the storage mechanism to use for the
database. Ensure Use Database File Locations from Template is selected as
the value to use for database file location, and then click Next.
i. Leave defaults selected for the database recovery options panel, and then
click Next.
j. From the Sample Schemas panel, click Next.
k. From the Initialization Parameters panel, on the Memory tab, select Custom
and provide the following values (measured in Mb):

76 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Memory Management
Set this value to Manual Shared Memory Management.
Shared Pool
Set this value to 152.
Buffer Cache
Set this value to 36.
Java Pool
Set this value to 32.
Large Pool
Set this value to 8.
PGA Size
Set this value to 36.
l. From the Character Sets tab, select Use Unicode (AL32UTF8).
m. Click All Initialization Parameters....
n. Click Show Advanced Parameters.
o. Locate the following parameters, change them to the values indicated, and
then click Close.
nls_length_semantics
Change this value to CHAR.
open_cursors
Change this value to 1000.
cursor_sharing
Set this value to FORCE.
p. From the Initialization Parameters panel, click Next.
q. From the Database Storage panel, click Next.
r. From the Creation Options panel, click Finish.
s. Click Exit to exit the Database Configuration Assistant. The database is
successfully created.

Note: The Oracle Database Configuration Assistant starts the

ORACLE_HOME/ctx/admin/defaults/drdefus.sql script as part of the
configuration of the CTXSYS user. You must start this script manually if the
Oracle Database Configuration Assistant is not used.
4. Create a table space using the following command in SQL*Plus:
Create tablespace maxdata datafile
’C:\oracle\product\11.1.0\db_1\dbs\maxdata.dbf’
size 1000M autoextend on;
Change the directory specified in the example to the database location. If the
directory does not exist, this command fails.
5. Create a temporary table space using the following command in SQL*Plus
create temporary tablespace maxtemp tempfile
’C:\oracle\product\11.1.0\db_1\dbs\maxtemp.dbf’
size 1000M autoextend on maxsize unlimited;
Change the directory specified in the example to the database location. If the
directory does not exist, this command fails.
6. Create the maximo user and grant permissions using the following command
in SQL*Plus:

Chapter 4. Deploying manually reusing existing middleware 77

 create user maximo identified by maximo default tablespace maxdata temporary
tablespace maxtemp;
grant connect to maximo;
grant create job to maximo;
grant create trigger to maximo;
grant create session to maximo;
grant create sequence to maximo;
grant create synonym to maximo;
grant create table to maximo;
grant create view to maximo;
grant create procedure to maximo;
grant alter session to maximo;
grant execute on ctxsys.ctx_ddl to maximo;
alter user maximo quota unlimited on maxdata;
If you created a separate table space for indexing, you must also grant access to
that index table space to the maximo user. For example, use the following
command if you created a separate table space for indexing called
TSI_MAM_OWN.":
alter user maximo quota unlimited on TSI_MAM_OWN
These instructions assume that you did not modify default role sets assigned to
the Oracle DBA user or user IDs created to connect to the database. If you
restricted the default privileges granted to user IDs, you must explicitly grant
them to the maximo user. For example, if you do not grant a role such as the
select_catalog_role role, you must explicitly grant that role to the maximo
user. This assignment can be done by running this SQL*Plus command:
grant select_catalog_role to maximo

Manually configuring Oracle 10g

Oracle 10g can be manually configured for use with SmartCloud Control Desk.

Before you begin

Oracle instance names must be limited to eight characters in length. For Oracle
databases, the schema owner must use the same user ID as the database user.

About this task

To configure an existing Oracle 10g server for use with SmartCloud Control Desk,
complete the following steps before you start the SmartCloud Control Desk
installation program:

Procedure
1. Log in as the Oracle software user. Typically this user is named oracle.
2. Create the database listener. The listener manages requests to connect to the
database.
a. Open the Oracle Network Configuration Assistant application.
b. From the Welcome panel, select Listener configuration, and then click Next.
c. From the action panel, select Add, and then click Next.
d. Enter a name for the listener or accept the default value, and then click
Next.
e. Accept the default Selected Protocols listed by clicking Next.
f. From the port panel, select Use the standard port of 1521, and then click
Next.
g. Select No to indicate that you are finished configuring listeners, and then
click Next.

78 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 h. From the Listener Configuration Done panel, click Next.
i. Click Finish.
3. Create a database for SmartCloud Control Desk.
a. Open the Oracle Database Configuration Assistant.
b. Click Next.
c. Select Create a Database, and then click Next.
d. Select General Purpose, and then click Next.
e. Enter ctginst1 for both the Global Database Name value and the SID value,
and then click Next.
f. Leave the defaults selected, and click Next.
g. Ensure Use the Same Password for All Accounts is selected, enter a
password for Oracle users, and then click Next
h. Ensure File System is selected as the storage mechanism to use for the
database, and then click Next.
i. Ensure Use Database File Locations from Template is selected as the value
to use for database file location, and then click Next.
j. Leave defaults selected for the database recovery options panel, and then
click Next.
k. From the Sample Schemas panel, click Next.
l. From the memory allocation panel, select Custom, provide the following
values (measured in bytes), and then click Next.
Shared Memory Management
Set this value to Manual.
Shared Pool
Set this value to 152.
Buffer Cache
Set this value to 36.
Java Pool
Set this value to 32
Large Pool
Set this value to 8.
PGA Size
Set this value to 36.
m. From the Character Sets tab, select Use Unicode (AL32UTF8),
n. Click All Initialization Parameters....
o. Click Show Advanced Parameters.
p. Locate the following parameters, change them to the values indicated, and
then click Close.
nls_length_semantics
Change this value to CHAR
open_cursors
Change this value to 1000
cursor_sharing
Set this value to FORCE.
q. From the Initialization Parameters panel, click Next.
r. From the Database Storage panel, click Next.

Chapter 4. Deploying manually reusing existing middleware 79

 s. From the Creation Options panel, click Finish.
t. After the database is created, click Password Management.
u. Unlock the CTXSYS account by clearing the check mark in the Lock
Account? column for that entry, enter a password for the account, and then
click OK.
v. Click Exit to exit the Database Configuration Assistant. The database is
successfully created.

Note: The Oracle Database Configuration Assistant uses the

ORACLE_HOME/ctx/admin/defaults/drdefus.sql script as part of the
configuration of the CTXSYS user. This script must be used manually if the
Oracle Database Configuration Assistant is not used.
4. Create a table space using the following command in SQL*Plus:
Create tablespace maxdata datafile
’C:\oracle\product\10.2.0\oradata\ctginst1\maxdata.dbf’
size 1000M autoextend on;
The directory specified in the example must be changed to the installation
location of the database. If the directory does not exist, this command fails.
5. Create a temporary table space.
6. Create the maximo user and grant permissions using the following command
in SQL*Plus:
create user maximo identified by maximo default tablespace maxdata temporary
tablespace maxtemp;
grant connect to maximo;
grant create job to maximo;
grant create trigger to maximo;
grant create session to maximo;
grant create sequence to maximo;
grant create synonym to maximo;
grant create table to maximo;
grant create view to maximo;
grant create procedure to maximo;
grant alter session to maximo;
grant execute on ctxsys.ctx_ddl to maximo;
alter user maximo quota unlimited on maxdata;
If you have elected to create a separate table space for indexing, you must also
grant the maximo user access to that index table space. For example, you must
perform the following additional SQL*plus command if you had created a
separate table space for indexing called TSI_CMDB_OWN:
alter user maximo quota unlimited on TSI_CMDB_OWN
These instructions assume that you did not modify the default role sets that are
assigned to the Oracle DBA user or other database connection user IDs. If you
restrict the default privileges granted to user IDs, you must explicitly grant
them to the maximo user. For example, the select_catalog_role role is required
for user IDs connecting to the database. To deploy SmartCloud Control Desk
successfully, you must explicitly grant that role to the maximo user by using
the SQL*Plus command:
grant select_catalog_role to maximo

Manually configuring Microsoft SQL Server

You can manually configure Microsoft SQL Server for use with SmartCloud
Control Desk.

80 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Before you begin

Because Microsoft SQL Server does not support UTF-8, SmartCloud Control Desk
does not have multilingual support when deployed with Microsoft SQL Server.

Microsoft SQL Server Database Collation settings must be set to the following
options:
v Dictionary order
v Case-insensitive
v For use with 1252 Character set

About this task

To configure an existing Microsoft SQL Server for use with SmartCloud Control
Desk, perform the following steps before starting the SmartCloud Control Desk
installation program:

Procedure
1. Configure the listener port.
If The default instance of the Microsoft SQL Server Database Engine listens on
TCP port 1433. Named instances of the Microsoft SQL Server Database Engine
and Microsoft SQL Server Compact Edition are configured for dynamic ports,
which means they select any available port when the service starts. When
connecting to a named instance across a firewall, configure the Database Engine
to listen on a specific port, to open this port in the firewall.
a. Open Programs > Microsoft SQL Server 2008 > Configuration Tools >
SQL Server Configuration Manager
b. From the Microsoft SQL Server Configuration Manager navigation pane,
expand SQL Server Network Configuration > Protocols for <instance
name>, and then double-click TCP/IP.
c. In the TCP/IP Properties dialog box, click the IP addresses tab.
d. For each IP address listed, ensure that the TCP Dynamic Ports field is blank.
If the TCP Dynamic Ports field contains a value of 0, that IP address is
using dynamic ports. Since SmartCloud Control Desk requires Microsoft
SQL Server to listen on a static port, this field must be blank.
e. For each IP address listed, enter 1433 for the TCP Port field.
f. Click OK.
g. From the SQL Server Configuration Manager navigation pane, click SQL
Server Services.
h. Right-click SQL Server (<instance name>) and then click Restart, to stop,
and restart Microsoft SQL Server.
i. Verify the Microsoft SQL Server instance is running, and then close SQL
Server Configuration Manager.
2. Verify that you enabled the Full-text Search setting during the installation of
Microsoft SQL Server 2008. To determine if Full-text Search is installed on your
existing Microsoft SQL Server database, perform the following steps:
a. Open SQL Server Management Studio, select SQL Server Authentication as
the authentication type, and enter the credentials for the sa user ID, and
then click Connect.
b. Click New Query.
c. Type the following command:

Chapter 4. Deploying manually reusing existing middleware 81

 select FULLTEXTSERVICEPROPERTY ( ’IsFulltextInstalled’ )
If you did not install Full-text Search (the resulting value is zero), you must
do so at this time. To install Full-text Search, insert the Microsoft SQL Server
2008 product media into the system and start the installation wizard.
Navigate through the wizard and enable the Full-Text Search option located
on the Custom portion of the Setup Type dialog box. To finish the
installation process, restart the server.
3. Create a Microsoft SQL Server Database.
a. Open SQL Server Management Studio (Start > Programs > Microsoft SQL
Server 2008 > SQL Server Management Studio)
b. Right-click the Databases folder from the navigation tree , and select New
Database.
c. In the Database name entry field, specify a unique database name (for
example maxdb75)
d. For the maxdb75 Logical Name, change the Initial Size (MB) attribute to 500
(MB), and also set the value of the Autogrowth field to By 1MB,
unrestricted growth.
e. If you prefer, modify the log settings to accommodate your production
environment.
f. Click OK.
4. Create the Maximo User for Microsoft SQL Server.
a. Open Microsoft SQL Server Management Studio (Start > Programs >
Microsoft SQL Server 2008 > SQL Server Management Studio)
b. Click New Query.
c. Select the SmartCloud Control Desk database (maxdb75) from the Available
Databases menu,
d. Enter the following script to create the Maximo database user MAXIMO with a
password of MAXIMO.
sp_addlogin MAXIMO,MAXIMO
go

This value is case-sensitive.

e. Click Execute.
f. Enter the following script to change the database owner to maximo.
sp_changedbowner MAXIMO
go
g. Click Execute.

What to do next

If you add additional logical names to the database and set their file group to a
value other than PRIMARY, you must complete the following steps after you set
up the database and create the Maximo user:
1. Run the SmartCloud Control Desk installation program and choose the Do not
run the configuration step now option.
2. Add the following property to the install_home\etc\install.properties file:
Database.SQL.DataFilegroupName=<your logical name>
3. Run the configuration steps outside of the SmartCloud Control Desk
installation program by using the taskrunner utility, located in the
install_home\scripts directory.

82 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Complete these additional steps only if you added additional logical names to the
database and set their file group to a value other than PRIMARY.

Manually configuring the directory server

These topics provide details on manually configuring a directory server for use by
SmartCloud Control Desk

There are several methods you can use to secure SmartCloud Control Desk.If want
to use a directory server to secure SmartCloud Control Desk, you must complete
the manual configuration of the directory server before you use the SmartCloud
Control Desk installation program. Manual configuration is necessary if you
choose to not have the SmartCloud Control Desk installation program perform
configuration.

Note: The base dn, bind user, and other various node values listed in these
sections are defaults. These values are replaced with values applicable to existing
LDAP hierarchies within your organization.

Important: When entering LDAP values for SmartCloud Control Desk installation
panel fields, entries in LDIF files, or values you enter directly into a directory
instance using directory server tools, be aware of the product-specific syntax rules
for using special characters in an LDAP string. In most cases, special characters
must be preceded by an escape character in order to make it readable by the
directory server. Failing to escape special characters contained in an LDAP string
used with SmartCloud Control Desk results in SmartCloud Control Desk errors.

Many directory server products consider a blank space as a special character that is
part of the LDAP string. If you mistakenly enter an LDAP string that contains a
blank, at the end of a field value, for example, and you do not precede the blank
character with an escape character, you encounter SmartCloud Control Desk errors
that are difficult to troubleshoot.

See the product documentation for your directory server for more information
about special characters in LDAP strings.

Manually configuring IBM Tivoli Directory Server

Use the following instructions to manually configure IBM Tivoli Directory Server
for use with SmartCloud Control Desk.

About this task

To configure IBM Tivoli Directory Server before starting the SmartCloud Control
Desk installation program, you must create an instance of IBM Tivoli Directory
Server.

Note: While you can technically share a DB2 instance between SmartCloud
Control Desk and the one needed by IBM Tivoli Directory Server, it might lead to
problems. During the installation, the database instance is restarted, which might
disrupt the availability of IBM Tivoli Directory Server to your enterprise. If you are
using the automated installation programs, separate instances are created for use
by SmartCloud Control Desk and IBM Tivoli Directory Server.

Procedure
1. Using your preferred method, create a user on the system and assign it to the
appropriate group.

Chapter 4. Deploying manually reusing existing middleware 83

 Windows
Create the user db2admin and make it a member of the following
groups:
v Windows Administrators
v DB2ADMNS
v DB2USERS
UNIX Create the user idsccmdb and make it a member of the following
groups:
v dasadmn1
v idsldap
v dbsysadm
The root user must also be a member of the dasadm1, idsldap, and
dbsysadm groups.
2. If the Instance Administration tool is not already started, ensure that you are
logged in as an administrator on the system, and then start the tool
Windows
Select Programs > IBM Tivoli Directory Server 6.3 > Instance
Administration Tool.
UNIX Type ./opt/IBM/ldap/V6.3/sbin/idsxinst at the command line.
3. In the Instance Administration tool, click Create an instance.
4. In the Create a new instance window, click Create a new directory server
instance, and then click Next.
5. From the Instance details window, enter values for the following fields, and
then click Next.
User name
Select idsccmdb as the system user ID of the user who owns the
instance. This name is also the name of the instance.
Install location
Enter the location where the instance files are stored.
Encryption seed string
Type a string of characters that are used as an encryption seed. This
value must be a minimum of 12 characters.
Instance description
Enter a brief description of the instance.
6. In the DB2 instance details panel, enter idsccmdb as the value for the DB2
instance name field, and then click Next.
7. In the TCP/IP settings for multihomed hosts panel, select Listen on all
configured IP addresses, and then click Next.
8. In the TCP/IP port settings panel, complete the following fields, and then
click Next.
Server port number
Enter 389 as the contact port for the server.
Server secure port number
Enter 636 as the secure port for the server.
Admin daemon port number
Enter 3538 as the administration daemon port.

84 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Admin daemon secure port number
Enter 3539 as the administration daemon secure port.
9. In the Option steps panel, leave the following options selected, and then click
Next.
Configure admin DN and password
You want to configure the administrator DN and password for the
instance now.
Configure database
You want to configure the database for the directory server now.
10. In the Configure administrator DN and password window panel, complete the
following fields, and then click Next.
Administrator DN
Enter cn=root for the administrator distinguished name.
Administrator Password
Enter a password for the Administrator DN.
11. From the Configure database panel, complete the following fields, and then
click Next.
Database user name
Enter idsccmdb as the database user.
Password
Enter the password for the idsccmdb user.
Database name
Enter idsccmdb as the database to be used with this directory instance.
12. In the Database options panel, complete the following fields, and then click
Next.
Database install location
Type the location for the database.
Windows
For Windows platforms, this value must be a drive letter.
UNIX For non-Windows platforms, the location must be a directory
name, such as /home/ldapdb.
Ensure that you have at least 80 MB of free hard disk space in the
location you specify. Additional disk space must be available to
accommodate growth as new entries are added to the directory.
Character-set option
Leave the Create a universal DB2 database (UTF-8/UCS-2) option
selected.
13. In the Verify settings panel, review the instance creation details provided, and
then click Finish to create the idsccmdb instance.
14. Click Close to close the window and return to the main window of the
Instance Administration tool.
15. Click Close to exit the Instance Administration tool.
16. Start the IBM Tivoli Directory Server Configuration tool:
Windows
SelectPrograms > IBM Tivoli Directory Server 6.3 > Instance
Administration Tool.
UNIX Type ./opt/IBM/ldap/V6.3/sbin/idsxcfg at the command line.

Chapter 4. Deploying manually reusing existing middleware 85

 17. Select Manage suffixes.
18. In the Manage suffixes panel, type the following suffix, and then click Add.
o=IBM,c=US
19. Click OK.
20. Create and save an LDIF file.
Add the DN information, for example:
v ou=SWG,o=IBM,c=US
v ou=users

Note: ou=SWG,o=IBM,c=US in this example is an organization unit called

SWG. SWG houses the OU=Users organization units to place the users
created for SmartCloud Control Desk. DC=IBM and DC=COM would indicate
a domain forest of ibm.com®. You can replace the example with the directory
structure of your own organization.
Define the following users and their positions within the ou=users DN's you
created. These users are defined in order for Virtual Member Manager to be
used to secure SmartCloud Control Desk.

Important: Before you begin this procedure, ensure that you have the
following users created in the root of your LDAP repository:
Table 7. Base SmartCloud Control Desk required users
User
wasadmin
maxadmin
mxintadm
maxreg

Here is an example of the default base LDIF data:

dn: o=ibm,c=us
objectClass: top
objectClass: organization
o: IBM

dn: ou=SWG, o=ibm,c=us

ou: SWG
objectClass: top
objectClass: organizationalUnit

dn: ou=users,ou=SWG, o=ibm,c=us

ou: users
objectClass: top
objectClass: organizationalUnit
dn: cn=wasadmin,ou=users,ou=SWG, o=ibm,c=us
uid: wasadmin
userpassword: passw0rd
objectclass: organizationalPerson
objectclass: inetOrgPerson
objectclass: person
objectclass: top
title: WebSphere Administrator
sn: wasadmin
cn: wasadmin
dn: uid=maxadmin,ou=users,ou=SWG, o=ibm,c=us
userPassword: maxadmin
uid: maxadmin

86 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 objectClass: inetorgperson
objectClass: top
objectClass: person
objectClass: organizationalPerson
sn: maxadmin
cn: maxadmin

dn: uid=mxintadm,ou=users,ou=SWG, o=ibm,c=us

userPassword: mxintadm
uid: mxintadm
objectClass: inetorgperson
objectClass: top
objectClass: person
objectClass: organizationalPerson
sn: mxintadm
cn: mxintadm

dn: uid=maxreg,ou=users,ou=SWG, o=ibm,c=us

userPassword: maxreg
uid: maxreg
objectClass: inetorgperson
objectClass: top
objectClass: person
objectClass: organizationalPerson
sn: maxreg
cn: maxreg

Note: If you create the LDIF file on Windows, ensure that you remove the ^M
characters from the file before using.

Note: Before you can import an LDIF file on UNIX systems, you must run
the dos2unix command to format the file.
21. In the IBM Tivoli Directory Server Configuration Tool, click Import LDIF data.
22. Click Browse to locate the LDIF file.
23. Click Import.
24. Close the IBM Tivoli Directory Server Configuration Tool and restart the
server.

Manually configuring Microsoft Active Directory

You can manually configure Microsoft Active Directory for use with SmartCloud
Control Desk.

Before you begin

Use this procedure to manually create users and groups within Microsoft Active
Directory. You have the option to create these users and groups automatically if
you choose the option to configure WebSphere Application Server Network
Deployment automatically using the product installation program. If you do not
want the product installation program to configure WebSphere Application Server
Network Deployment during installation, you must create users manaully. Creating
users automatically requires SSL communication between Microsoft Active
Directory and WebSphere Application Server Network Deployment.

Important: The users and passwords you create in the following steps must match
this exact configuration for the deployment to succeed. It is sometimes necessary to
temporarily alter theMicrosoft Active Directory security policy to create these
accounts in the required format. After installation, you can change these default
passwords to conform to a stricter security policy.

Chapter 4. Deploying manually reusing existing middleware 87

 About this task

Before starting theSmartCloud Control Desk installation program, configure

Microsoft Active Directory. Complete the following steps

Procedure
1. Select Start > Control Panel > Administrative Tools > Microsoft Active
Directory Users and Computers and then select the domain that you are
working with.
2. Edit the functional level of the domain by selecting Action > Raise Domain
Functional Level. The Raise Domain Functional Level dialog box is displayed.
3. Select Microsoft Windows Server 2008 from the Select an available domain
functional level menu, and then click Raise. An alert dialog box is displayed.
4. Click OK.
5. When the domain raise task has completed, click OK.
6. In the Microsoft Active Directory Users and Computers interface, using the
right mouse button, click the domain to work with. Select New >
Organizational Unit.
7. Enter a name for the new Organizational Unit (OU), for example, SWG, and
then click OK.
8. Create a groups object under the SWG organizational unit:
a. Right-click the SWG OU, and select New > Organizational Unit.
b. Enter Groups as the name for the new OU then click OK.
9. Create a users object under the SWG organizational unit:
a. Right-click the SWG OU, and select New > Organizational Unit.
b. Enter Users as the name for the new OU then click OK.
10. Create the wasadmin user:
a. Right click the Users OU and select New > User.
b. From the New Object - User dialog, enter the following values, and then
click Next:
First name
Enter wasadmin.
Initials
Leave this field blank.
Last name
Leave this field blank.
Full name
Enter wasadmin.
User login name
Enter wasadmin in the first field. Leave the default value of the
second field.
User login name (pre-Microsoft Windows 2000)
This field is filled with the same value (wasadmin) entered for the
User login name.
c. From the next panel, enter the following information, and then click Next:
Password
Enter a password for wasadmin.

88 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 User must change password at next logon
Ensure this check box is cleared.
User cannot change password
Ensure this check box is selected.
Password never expires
Ensure this check box is selected.
Account is disabled
Ensure this check box is cleared.
The preceding values are examples. Enter values that comply with the
password policy of your organization.
d. Review the password settings in the summary panel, and click Finish.
11. Create an administrator user, for example maxadmin:
a. Right click the Users OU and select New > User.
b. From the New Object - User dialog, enter the following values, and then
click Next:
First name
Enter maxadmin.
Initials
Leave this field blank.
Last name
Leave this field blank.
Full name
Enter maxadmin.
User login name
Enter maxadmin in the first field. Leave the default value of the
second field.
User login name (pre-Microsoft Windows 2000)
This field is populated with the same value (maxadmin) entered
for the User login name.
c. From the next panel, enter the following information, and then click Next:
Password
Enter maxadmin as the password for the maxadmin user.
User must change password at next logon
Ensure this check box is cleared.
User cannot change password
Ensure this check box is selected.
Password never expires
Ensure this check box is selected.
Account is disabled
Ensure this check box is cleared.
The preceding values are examples. Enter values that comply with the
password policy of your organization.
d. Review the password settings in the summary panel, and click Finish.
12. Create the mxintadm user:
a. Right click the Users OU and select New > User.

Chapter 4. Deploying manually reusing existing middleware 89

 b. From the New Object - User dialog, enter the following values, and then
click Next:
First name
Enter mxintadm.
Initials
Leave this field blank.
Last name
Leave this field blank.
Full name
Enter mxintadm.
User login name
Enter mxintadm in the first field. Leave the default value of the
second field.
User login name (pre-Microsoft Windows 2000)
This field is displayed with the same value (mxintadm) entered for
the User login name.
c. From the next panel, enter the following information, and then click Next:
Password
Enter a value as the password for the mxintadm user.
User must change password at next logon
Ensure this check box is cleared.
User cannot change password
Ensure this check box is selected.
Password never expires
Ensure this check box is selected.
Account is disabled
Ensure this check box is cleared.
The preceding values are examples. You must set these fields to values
that comply with the password policy of your organization.
d. Review the password settings in the summary panel, and click Finish.
13. Create the maxreg user:
a. Right click the Users OU and select New > User.
b. From the New Object - User dialog, enter the following values, and then
click Next:
First name
Enter maxreg.
Initials
Leave this field blank.
Last name
Leave this field blank.
Full name
Enter maxreg.
User login name
Enter maxreg in the first field. Leave the default value of the
second field.

90 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 User login name (pre-Microsoft Windows 2000)
This field is filled with the same value (maxreg) entered for the
User login name.
c. From the next panel, enter the following information, and then click Next:
Password
Enter a value as the password for the maxreg user.
User must change password at next logon
Ensure this check box is cleared.
User cannot change password
Ensure this check box is selected.
Password never expires
Ensure this check box is selected.
Account is disabled
Ensure this check box is cleared.
The preceding values are examples. Enter values that comply with the
password policy of your organization.
d. Review the password settings in the summary panel, and click Finish.
14. You can now exit the Microsoft Active Directory Users and Computers tool.

What to do next

Microsoft Active Directory configuration is finished and you are now ready to
install the remaining SmartCloud Control Desk middleware and configure the J2EE
server to use Microsoft Active Directory.

Manually configuring the J2EE server

This section contains instructions for manually configuring an existing J2EE server
for use by SmartCloud Control Desk.

Manual configuration of the J2EE server is required if you choose to deploy

SmartCloud Control DeskWebSphere Application Server Network Deployment and
you choose to not have the SmartCloud Control Desk installation program
automatically configure it. You must complete the manual configuration before you
use the SmartCloud Control Desk installation program.

Manually configuring WebSphere Application Server Network

Deployment
This section contains instructions for manually configuring an existing WebSphere
Application Server Network Deployment for use by SmartCloud Control Desk.

You must manually configure WebSphere Application Server Network Deployment

before you use the SmartCloud Control Desk installation program if you do not
want the SmartCloud Control Desk installation program to configure it
automatically.

Performing WebSphere Application Server Network Deployment configuration

tasks:

Use this procedure to perform WebSphere Application Server Network

Deployment configuration tasks.

Chapter 4. Deploying manually reusing existing middleware 91

 About this task

If you elect to manually configure SmartCloud Control Desk middleware for use
with SmartCloud Control Desk, you have to manually configure the WebSphere
Application Server Network Deployment.

Procedure
1. Manually copy the keystore file from the WebSphere Application Server
Network Deployment deployment manager host to a temporary directory on
the SmartCloud Control Desk administrative system where you are installing
SmartCloud Control Desk: WAS_HOME/profiles/ctgDmgr01/etc/trust.p12
2. Open a browser and access the administrative console by typing in the
browser address bar: http://server_name:9060/admin. This URL address
depicts the default port number (9060) and context (admin) for the
administrative console. Enter a user name to log in. The browser is redirected
to a secure port (9043).
3. Create the MXServer application server. This step is only necessary if you did
not install WebSphere Application Server Network Deployment v7 using the
middleware installation program. For WebSphere Application Server Network
Deployment v8, you must create the application server.
a. Expand Servers > Server Types > WebSphere application servers.
b. Click New.
c. Type MXServer and click Next.
d. Accept all default settings and click Next.
e. Accept default settings and click Next.
f. Click Finish.
g. Click Preferences.
h. Select the Synchronize changes with Nodes check box, and then click
Apply.
i. Click Save.
j. Click OK.

92 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Figure 3. Manually create the application server

4. Edit JVM Memory Settings and JVM Arguments for the application server.
a. Click MXServer in the main window.
b. From the Server Infrastructure group, expand the Java and Process
Management link.
c. Click Process Definition.
d. Click Java Virtual Machine.
e. For 32-bit platforms, scroll down and type 1536 for Initial Heap Size and
Maximum Heap Size. For 64-bit platforms, set these values to 4096.
f. Enter the following values in the Generic JVM arguments field, using a
space between each argument:
-Dsun.rmi.dgc.ackTimeout=10000
-Djava.net.preferIPv4Stack=true # for Windows
-Xdisableexplicitgc
-Xgcpolicy:gencon
-Xmn320m # -Xmn320m for 32-bit JVM, -Xmn1024m for 64-bit JVM
-Xlp64k # AIX

Chapter 4. Deploying manually reusing existing middleware 93

Figure 4. Manually create the application server

g. Click OK.
h. Click Save in the messages box.
5. Edit thread pool settings for the application server.
a. Click MXServer from the WebSphere application servers panel.
b. From the Additional Properties group, click Thread pools.
c. Click Default. Set Minimum Size to 20. Set Maximum Size to 50. Set
Thread inactivity timeout to 30000. Click OK.
d. Click TCPChannel.DCS. Set Minimum Size to 5. Set Maximum Size to
20. Set Thread inactivity timeout to 5000. Click OK.
e. Click WebContainer. Set Minimum Size to 50. Set Maximum Size to 50.
Set Thread inactivity timeout to 30000. Click OK.

94 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Figure 5. Edit thread pool settings for the application server

6. Edit JVM Memory Settings for the deployment manager.

a. From System administration, click Deployment manager.
b. From the Server Infrastructure group, expand the Java and Process
Management link.
c. Click Process Definition.
d. Click Java Virtual Machine.
e. Scroll down and type 512 for Initial Heap Size and 1024 for Maximum
Heap Size and click OK.

Chapter 4. Deploying manually reusing existing middleware 95

Figure 6. Edit JVM Memory Settings for the deployment manager

f. Click Save in the messages box.

7. Start the application server.
a. From Servers > Server Types > WebSphere application servers, click
Application servers.
b. Select the MXServer check box.
c. Click Start.
8. Identify the HTTP Transfer Port Numbers.
a. Expand Servers > Server Types > WebSphere application servers, and
click MXServer from the main window.
b. Open the Web Container Settings and click Web container transport
chains.
c. Note the default port number as it appears with WCInboundDefault
(9080).

96 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Figure 7. Identify the HTTP Transfer Port Numbers

9. Create the virtual host.

a. Expand Environment.
b. Click Virtual Hosts.
c. Click New.
d. In the General Properties section, type maximo_host in the Name box.
e. Click Apply.
f. Click Save.
g. Click OK.
h. From the Virtual Hosts window, click maximo_host.
i. Click the Host Aliases link.
j. Click New.
k. Type * (asterisk) for host name and type the HTTP port number (by
default 80).
l. Click OK.
m. Click New.
n. Type * (asterisk) for host name and type 9061 for the port number.
o. Click OK.
p. Click New.
q. Type * (asterisk) for host name and type 9443 for the port number.
r. Click OK.
s. Click New.
t. Type * (asterisk) for host name and type 9080 for the port number.
u. Click OK.
v. Click New.
w. Type * (asterisk) for host name and type 9044 for the port number.
x. Click OK and then click Save.

Chapter 4. Deploying manually reusing existing middleware 97

Figure 8. Create the virtual host

10. Enable automatic startup of the application server when the node agent is
started.
a. Expand Servers > Server Types > WebSphere application servers.
b. Click MXServer in the main window.
c. From the Server Infrastructure group, expand Java and Process
Management.
d. Click Monitoring Policy.
e. Set Node restart state to RUNNING and click OK.
f. Click Save in the messages box.

Figure 9. Enable automatic startup of the application server when the node agent is started

If you used the middleware installation program to install WebSphere

Application Server Network Deployment v7, this step has already been
performed by the middleware installation program.

98 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Creating a Windows service for the node agent:

You can create a Windows service for starting the WebSphere Application Server
Network Deployment node agent.

About this task

Although not required, you can optionally start the node agent as a Windows
service.

If you used the middleware installation program to install WebSphere Application

Server Network Deployment v7, this step has already been performed by the
middleware installation program.

Procedure
1. Open a command prompt.
2. Change directory to <WAS_HOME>\bin.
3. Type the following command with no line breaks (case-sensitive).
WASService
-add NodeAgent
-serverName nodeagent
-profilePath "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01"
-wasHome "C:\IBM\WebSphere\AppServer"
-logRoot "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent"
-logFile "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent\
startServer.log"
-restart true
4. Close the Command Prompt.

Configuring the authentication service:

The authentication service is used for authentication purposes when launching in

context to another product that shares credentials with SmartCloud Control Desk.

Manually configuring authentication service:

You can manually configure an authentication service on SmartCloud Control Desk

that provides the authentication for launch in context.

Before you begin

If you used the middleware installation program to install and configure your
middleware, then the authentication service has already been configured
automatically. If you did not use the middleware installation program to install
and configure middleware, you must configure it manually to use this feature.

About this task

The authentication service provides launch in context from SmartCloud Control

Desk to the user interface of another server, for example, TADDM, provided it has
the authentication client installed and shares the same directory server for
authentication. Under this scenario, you are only required to authenticate once to
the server hosting the client.

To configure the authentication service manually, follow these steps:

Chapter 4. Deploying manually reusing existing middleware 99

 Procedure
1. Open a command prompt on the system that hosts WebSphere Application
Server Network Deployment, and change directory to WAS_HOME/bin.
2. Restart Deployment Manager, Application Server, and MXServer using the
correct profile names:
Windows
WAS_HOME/profiles/ctgAppsrv01/bin/stopServer.bat MXServer
-username WebSphere Admin
-password WebSphere Admin password

WAS_HOME/profiles/ctgAppsrv01/bin/stopNode.bat
-username WebSphere Admin
-password WebSphere Admin password

WAS_HOME/profiles/ctgDmgr01/bin/stopManager.bat
-username WebSphere Admin
-password WebSphere Admin password

WAS_HOME/profiles/ctgAppsrv01/bin/startManager.bat
WAS_HOME/profiles/ctgAppsrv01/bin/startNode.bat
WAS_HOME/profiles/ctgDmgr01/bin/startServer.bat MXServer
UNIX
./stopServer.sh MXServer -profileName ctgAppSrv01
-username WebSphere Admin
-password WebSphere Admin password

./stopNode.sh -profileName ctgAppSrv01

-username WebSphere Admin
-password WebSphere Admin password

./stopManager.sh -profileName ctgDmgr01

-username WebSphere Admin
-password WebSphere Admin password

./startManager.sh -profileName ctgDmgr01

./startNode.sh -profileName ctgAppSrv01
./startServer.sh MXServer -profileName ctgAppSrv01

Or:
WAS_HOME/profiles/ctgAppSrv01/bin/stopServer.sh MXServer
-username WebSphere Admin
-password WebSphere Admin password

WAS_HOME/profiles/ctgAppSrv01/bin/stopNode.sh
-username WebSphere Admin
-password WebSphere Admin password

WAS_HOME/profiles/ctgDmgr01/bin/stopManager.sh
-username WebSphere Admin
-password WebSphere Admin password

WAS_HOME/profiles/ctgDmgr01/bin/startManager.sh
WAS_HOME/profiles/ctgAppSrv01/bin/startNode.sh
WAS_HOME/profiles/ctgAppSrv01/bin/startServer.sh MXServer
3. Log on to the wsadmin shell by opening a command prompt and issuing the
following command:
Windows
wsadmin.bat -username WebSphere Admin
-password WebSphere Admin Password

100 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 UNIX
./wsadmin.sh -username WebSphere Admin
-password WebSphere Admin Password
4. Verify that you do not already have authentication services deployed:
wsadmin>$AdminApp view authnsvc_ctges

This command returns an exception like the following sample exception:

WASX7015E: Exception running command: "$AdminApp view authnsvc_ctges";
exception information: com.ibm.ws.scripting.ScriptingException:
WASX7280E: An application with name "authnsvc_ctges" does not exist.
5. Copy the IBMESSAuthnSvc.ear file to your local system. This file is located in
the Operating System\WS-ESS_6.2_GA directory of the SmartCloud Control
Desk middleware DVD.
6. Deploy the IBMESSAuthnSvc.ear file.
wsadmin>$AdminApp install file_path/IBMESSAuthnSvc.ear
{-usedefaultbindings -deployws -appname authnsvc_ctges –node (nodeName)
–server serverName |[-cluster (clustername)]}
If nodeName was set to the default value by the middleware installation
program, the value would be ctgNode01. serverName, if set to the default value
supplied by the SmartCloud Control Desk installation program, would be
MXServer.
7. Save the configuration:
wsadmin>$AdminConfig save
8. Identify the application manager MBean for the server that hosts the
application and assign it to the appManager variable:
set appManager [$AdminControl queryNames cell=myNodeCell,node=myNode,
type=ApplicationManager,process=myServer,*]

You can use the following commands to determine the current values for the
cell, node, and application server:
$AdminConfig list Cell
$AdminConfig list Node
$AdminConfig list Server
9. Start the application:
$AdminControl invoke $appManager startApplication authnsvc_ctges
10. Exit the wsadmin shell by typing exit.
11. Log in to the WebSphere Application Server Network Deployment console.
12. Browse to Applications > Enterprise applications, click authnsvc_ctges, and
then click Manage Modules.
13. Highlight all entries listed in the Clusters and Server list, select
listtokenservice and WSFedPassiveProfile, click Apply, click OK, and then
click Save.
14. Regenerate the WebSphere Application Server Network Deployment plug-in
using the following command:
WAS_HOME/bin/GenPluginCfg.bat –cell.name myNodeCell –node.name myNode
–webserver.name myServer

When the command has completed successfully, you see the following
message:
Plugin-in configuration file generation is complete for the Web server
myNodeCell.myNode.myServer

Chapter 4. Deploying manually reusing existing middleware 101

 15. Copy the regenerated WebSphere Application Server Network Deployment,
for example, plugin-cfg.xml from WAS_HOME\AppServer\profiles\
ctgAppSrv01\config\cells to HTTPServer_HOME\Plugins\config\webserver1.
16. Restart the HTTP Server and the HTTP admin console.
17. Stop WebSphere Application Server Network Deployment and the managed
nodes:
WAS_HOME/profiles/ctgAppSrv01/bin/stopNode.sh -username WebSphere Admin
-password WebSphere Admin password
WAS_HOME/profiles/ctgDmgr01/bin/stopManager.sh -username WebSphere Admin
-password WebSphere Admin password
18. Copy the com.ibm.security.ess.server_config.6.2.0.jar file to the
WAS_HOME/plugins directory on your local system. This file is located in the
Operating System\WS-ESS_6.2_GA directory of the SmartCloud Control Desk
middleware DVD.
19. Restart WebSphere Application Server Network Deployment and the managed
nodes:
WAS_HOME/profiles/ctgDmgr01/bin/startManager.(sh|bat)
WAS_HOME/profiles/ctgAppSrv01/bin/startNode.(sh|bat)
20. Log back in to the wsadmin shell.
21. Configure the service:
wsadmin>$AdminTask configureESS
22. Verify that the service is configured:
wsadmin>$AdminTask isESSConfigured
This command returns a value of true.
23. Create an LTPA Key:
wsadmin>$AdminTask createESSLTPAKeys {-password password}
If the key password is ever lost, you must generate a new key. Ensure all
clients connecting to the service use the new export key file you generate.
24. Synchronize the configuration:
wsadmin>$AdminConfig save
wsadmin>set dmgr [$AdminControl completeObjectName
type=DeploymentManager,*]
wsadmin>$AdminControl invoke $dmgr syncActiveNodes true
25. Stop and restart WebSphere Application Server Network Deployment and the
managed nodes:
Windows
WAS_HOME\profiles\ctgAppSrv01\bin\stopNode.bat
-username WebSphere Admin
-password WebSphere Admin password

WAS_HOME\profiles\ctgDmgr01\bin\stopManager.bat
-username WebSphere Admin
-password WebSphere Admin password

WAS_HOME\profiles\ctgDmgr01\bin\startManager.bat
WAS_HOME\profiles\ctgAppSrv01\bin\startNode.bat
UNIX
WAS_HOME/profiles/ctgAppSrv01/bin/stopNode.sh
-username WebSphere Admin
-password WebSphere Admin password
WAS_HOME/profiles/ctgDmgr01/bin/stopManager.sh
-username WebSphere Admin
-password WebSphere Admin password

WAS_HOME/profiles/ctgDmgr01/bin/startManager.sh
WAS_HOME/profiles/ctgAppSrv01/bin/startNode.sh

102 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

26. Add the role called TrustClientRole to the WebSphere Application Server
Network Deployment administrator user. This user was specified during the
TADDM installation.
a. Browse to Applications > Enterprise applications, click authnsvc_ctges,
and then click Security role to user/group mapping
b. Select TrustClientRole and click Look up Users
c. Move the WebSphere Application Server Network Deployment
administrator user from the Available column to the Selected column. Use
the >> button, click OK, click OK again, and then click Save.
This step provides added security by restricting the users that can authenticate
to the authentication service to those users with the TrustClientRole role.
27. Export the newly created key:
wsadmin>$AdminTask exportESSLTPAKeys {-pathname path_name}
For example:
wsadmin>$AdminTask exportESSLTPAKeys {-pathname /root/
avenESSLTPAKeyFile.exported}

Migrating the authentication service:

This section provides information you can use to migrate the authentication
service.

Before you begin

If you have deployed the 7.5 version of CCMDB and installed WebSphere
Application Server Network Deployment using the middleware installation
program, you already have a version of the authentication service deployed on the
application server. When upgrading to SmartCloud Control Desk 7.5.1, if you
intend to continue to use the launch in context function with IBM Tivoli
Application Dependency Discovery Manager, you need to migrate to a newer
version of the authentication service.

Note: these steps do not provide a restore capability. Make a backup of the system
before you begin.

About this task

To configure the authentication service manually, follow these steps:

Procedure
1. Ensure WebSphere Application Server Network Deployment services and
servers are running.
2. Update the Authentication Service application:
a. Log on to the wsadmin shell using the following command.
Windows
wsadmin.bat
UNIX
./wsadmin.sh

If you did not change the wsadmin user name or password when you first
installed the application server, the default is wsadmin for the user and
wsadmin for the password.
b. Run the following commands:

Chapter 4. Deploying manually reusing existing middleware 103

 $AdminApp update authnsvc_ctges app {-operation update -contents
(install_path)/IBMESSAuthnSvc.ear -usedefaultbindings
-deployws}

$AdminConfig save
3. Stop WebSphere Application Server Network Deployment along with all
wsadmin instances.
4. Replace back-level authentication service configuration JAR file located in the
WebSphere Application Server Network Deployment plug-ins directory with
the updated JAR file.
a. Delete the existing WAS_HOME/plugins/
com.ibm.security.ess.server_config.6.1.0.jar
b. Copy the new com.ibm.security.ess.server_config.6.2.0.jar to the
WAS_HOME/plugins directory
c. Run the following command:
WAS_HOME/profiles/PROFILE/bin/osgicfginit
5. Restart WebSphere Application Server Network Deployment.

Authentication service administrative commands:

There are several administrative commands for the authentication service that can
be used with the wsadmin tool. These commands can help you determine the state
of the currently installed authentication service.

Administrative commands
Action
isESSConfigured
Purpose
Checks for authentication service configuration.
Input None.
Returns
True if authentication service is configured.
False if authentication service is not configured.
Throws
Exception if a system error is encountered.
Syntax
$AdminTask isESSConfigured
Action
isESSConfiguredLTPAKeys
Purpose
Checks for authentication service LTPA Key configuration.
Input None.
Returns
True if authentication service LTPA keys are configured.
False if authentication service LTPA keys are not configured.
Throws
Exception if authentication service is not configured.
Exception if a system error is encountered.

104 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Syntax
$AdminTask isESSConfiguredLTPAKeys
Action
configureESS
Purpose
This command configures the authentication service by creating an
authentication service configuration file in the WebSphere Application
Server Network Deployment configuration repository found in
WAS_PROFILE/config/ibmess/authn/Configuration.xml
Input None.
Returns
None.
Throws
Exception if a system error is encountered.
Syntax
$AdminTask configureESS
Action
unconfigureESS
Purpose
Unconfigures the authentication service by removing authentication service
configuration from the WebSphere Application Server Network
Deployment configuration repository WAS_PROFILE/config/ibmess/authn/
Configuration.xml file.
Input None.
Returns
None.
Throws
Exception if a system error is encountered.
Syntax
$AdminTask unconfigureESS
Action
createESSLTPAKeys
Purpose
Creates new LTPA Keys for use by authentication service. If there are
existing LTPA keys configured for the authentication service, those keys are
overwritten LTPA tokens that have been previously issued using the
replaced keys are invalidated.
Input password
Password that was used to protect the LTPA keys in the file.
Returns
None.
Throws
Exception if authentication service is not configured.
Exception if a system error is encountered.
Exception if authentication service LTPA keys cannot be configured.

Chapter 4. Deploying manually reusing existing middleware 105

 Syntax
$AdminTask createESSLTPAKeys {-password password}
Action
importESSLTPAKeys
Purpose
Import LTPA keys into authentication service from an existing LTPA Key
Export file. If there are existing LTPA keys configured for the
authentication service, those keys are overwritten. LTPA tokens that have
been previously issued using the replaced keys are invalidated.
Input pathname Path and file name of file containing LTPA keys to import into
the authentication service. This file might have been exported by
WebSphere Application Server Network Deployment, or by the
authentication service through the exportESSLTPAKeys command.
password Password that was used to protect the LTPA keys in the file.
Returns
None.
Throws
Exception if the authentication service is not configured.
Exception if a system error is encountered.
Exception if keys cannot be created.
Syntax
$AdminTask importESSLTPAKeys {-pathname path name - password
password}
Reference
This table shows the mapping of LTPA exported key file information to the
authentication service configuration fields.
Table 8. LTPA exported key file mapping
Name Type Description of Value
ltpa.partner.sharedkey String The shared key used for decryption
of the token.

This key can be taken from the

ltpa.partner.publickey
com.ibm.websphere.ltpa. 3DESKey
name-value pair of an exported LTPA
key file. This key was encrypted
when it was exported from the
WebSphere Application Server
Network Deployment server that
created it.
String The public key for the partner that
signed the token.

This key can be taken from the

ltpa.partner.password
com.ibm.websphere.ltpa.PublicKey
name-value pair of an exported LTPA
key file.
String The password that was used to
protect the keys created by the
partner.

106 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 8. LTPA exported key file mapping (continued)
Name Type Description of Value
ltpa.self.sharedkey String The shared key used for the
encryption of the token.

This key can be taken from the

ltpa.self.publickey
com.ibm.websphere.ltpa. 3DESKey
name-value pair of an exported LTPA
key file. This key was encrypted
when it was exported from the
WebSphere Application Server
Network Deployment server that
created it.
String The public key associated with the
ltpa.self.privatekey property.

This key can be taken from the

ltpa.self.privatekey
com.ibm.websphere.ltpa. PublicKey
name-value pair of an exported LTPA
key file.
String The private key that is used for
signing the token.

This key can be taken from the

com.ibm.websphere.ltpa. PrivateKey
name-value pair of an exported LTPA
key file. This key was encrypted
when it was exported from the
WebSphere Application Server
Network Deployment server that
created it.
ltpa.self.password String The password that was used to
protect the keys that the consuming
application created.

Action
exportESSLTPAKeys
Purpose
Export LTPA keys from the authentication service and write to the LTPA
key export file.
Input pathname Path and file name to write LTPA keys to be exported from the
authentication service. After successful export from the authentication
service, this file might be used to import LTPA keys into another the
authentication service server or into WebSphere Application Server
Network Deployment.
Returns
None.
Throws
Exception if the authentication service is not configured.
Exception if a system error is encountered.
Exception if the authentication service LTPA keys have not been
configured.

Chapter 4. Deploying manually reusing existing middleware 107

 Syntax
$AdminTask exportESSLTPAKeys {-pathname path name}
Reference
Here is an example of the LTPA key export file. Note there are no line
breaks in the LTPA key export file.
#IBM WebSphere Application Server key file
#Mon Jun 11 08:05:50 EDT 2007
com.ibm.websphere.CreationDate=Mon Jun 11 08\:05\:50 EDT 2007
com.ibm.websphere.ltpa.version=1.0
com.ibm.websphere.ltpa.3DESKey=
zDtRTqOEsw0F5NNhGpvzdp/xqoFFTyX0WFNxYMEpC10\=
com.ibm.websphere.CreationHost=
PestRHAS3
com.ibm.websphere.ltpa.PrivateKey=
hPyfNkqrClrwpQgRAnvNSRugf/6Su59g5Jh5FR28SrT/
XapX/OOghU3/41dX1HXL496sDKm9kXE/WYhsFvh3L8JVzacEqF3T+57akZZ
/wDJdga6DcDlYMmzLll
91SgjV68dB6lsVgt/
jFtMczYxK+RgBDpKthEurI9rQr2eq73Gm75KehgRSMCaBwew+kQi6aWFdyhWc
OlQLCod8BQtesJt2aTEaQ3NDD0PFQVkDMWVpzoLvBOJBdhwhQFWX9L7gE9gMeS
PoeXr19MlEA780/E
X9w7kEIKYu7UzrUbvTEREoYCUFklJcE2A3Q0rMKlIzlkIJ1QGXwR6EM2sVe9w6M
CPHir32A45rEYyy1
lP0SuA\=
com.ibm.websphere.ltpa.Realm=
VmmLdapRealm
com.ibm.websphere.ltpa.PublicKey=
AKj4wjeYEQoxL76Ph0g1i3gt5Siwgygu3+22xfh6Kh1JR3
LZGsT+nONpAfxY9NfmPTDFxjbrIESIS/
XAdp/0QgWBF9DZJ5vO1Ds0/M356seVtsnvwy3p/VVFQg4Uz
T6j/f1G6SJaqPQjrv2EAZyEn+TL8Okl3CWdKiFtPjtpWdh5AQAB

How ESSLTPAKeys are exported to a file:

com.ibm.websphere.CreationDate=(set to the date/time when the export file is
created)
com.ibm.websphere.ltpa.version=1.0
com.ibm.websphere.ltpa.3DESKey=(set from ltpa.self.sharedkey)
com.ibm.websphere.CreationHost=(set to local host name)
com.ibm.websphere.ltpa.PrivateKey=(set from ltpa.self.privatekey)
com.ibm.websphere.ltpa.Realm=(set to the currently configured VMM realm)
com.ibm.websphere.ltpa.PublicKey=(set from ltpa.self.publickey)
Action
showESSLTPAConfiguration
Purpose
Returns a property object containing the current authentication service
LTPA configuration. The returned properties list contains version,
expiration, and usefips configuration properties. After an initial
configuration, the defaults will be returned.
Input None.
Returns
Properties object.
Throws
Exception if the authentication service is not configured.
Exception if a system error is encountered.
Syntax
$AdminTask showESSLTPAConfiguration

108 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Action
modifyESSLTPAConfiguration
Purpose
Modifies the authentication service LTPA properties.
Input usefips See ltpa.self.usefips in the table.
expiration See ltpa.self.expiration in the table.
version See ltpa.self.version in the table.
Returns
None.
Throws
Exception if the authentication service is not configured.
Exception if a system error is encountered.
Syntax
$AdminTask modifyESSLTPAConfiguration {[-version version] [-expiration
expiration] [-usefips useFips]}
Reference
Table 9. LPTA Configuration Properties
Parameter Type Default Config Type Description Required
ltpa.partner.usefips boolean False partner This determines No
whether the FIPS
enabled flag was
enabled when the
partner created the
token.
ltpa.self.expiration long 120 self The expiration time Yes
that is set on the
token in minutes.
This time is
converted to
milliseconds and
then added to the
current system time
to give an absolute
expiration time.
ltpa.self.usefips boolean False self This determines No
whether the FIPS
enabled flag was
enabled when the
partner created the
token.
ltpa.self.version list (if a list 2 self This determines Yes
exists, String what version of
otherwise) LTPA token to issue:
version 1 or 2.

Action
createESSSigner
Purpose
Configures the authentication service to use response signing keys from the
default keystore.

Chapter 4. Deploying manually reusing existing middleware 109

 Input None.
Returns
None.
Throws
Exception if the authentication service is not configured.
Exception if a system error is encountered.
Syntax
$AdminTask createESSSigner
Action
importESSSigner
Purpose
Configures the authentication service to use response signing keys from the
specified keystore.
Input pathname - Required – File path name of an existing keystore file to import
into Authentication Service configuration.
password - Required - Password to open the imported keystore file.
keyalias - Required - The alias of the signer key in the imported keystore
file.
keypassword - Optional - The password to access the signer key in the
keystore file.
Returns
None.
Throws
Exception if the authentication service is not configured.
Exception if a system error is encountered.
Exception if required parameter is missing.
Exception if the keystore file cannot be located.
Syntax
$AdminTask importESSSigner {-pathname path name -password
password-keyalias alias -keypassword password }
Action
exportESSSigner
Purpose
Export the configured response signer keys to the specified keystore, to be
used for synchronization with other authentication service instances.
Input pathname Required - Path and filename of a keystore into which configured
response signer keys are exported. If the keystore exists it is updated.
password Required - Password for accessing the specified export keystore
file.
keyalias Required - Alias to specify to store the exported response.
keypassword Required - The password to specify to encrypt the signer key
in the keystore file.
Returns
None.

110 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Throws
Exception if the authentication service is not configured.
Exception if a system error is encountered.
Exception if the keystore file cannot be located.
Syntax
$AdminTask exportESSSigner {-pathname path name -password password
-keyalias alias -keypassword password }
Action
exportESSSignerCert
Purpose
Export the configured response signer certificate to the specified keystore,
to be used by an Authentication Client for response signature validation.
Input pathname Required - Path and filename of a keystore into which configured
response signer keys are exported. If the keystore exists it is updated.
password Required - Password for accessing the specified export keystore
file.
certalias Required - Alias of the certificate to export, associated with the
response signer key.
Returns
None.
Throws
Exception if the authentication service is not configured Exception if a
system error is encountered Exception if the keystore file cannot be located
Syntax
$AdminTask exportESSSignerCert {-pathname path name -password
password -certalias alias}
Action
showESSWSFedConfiguration
Purpose
Display the current WS-Federation SSO servlet configuration settings.
Input None.
Returns
Properties object with current SSO redirect WS-Federation servlet
properties
Throws
Exception if the authentication service is not configured.
Exception if a system error is encountered.
Syntax
$AdminTask showESSWSFedConfiguration
Action
modifyESSWSFedConfiguration
Purpose
Modifies SSO redirect WS-Federation servlet cookie properties.
Input domain See domain in the table.
secure See secure in the table.

Chapter 4. Deploying manually reusing existing middleware 111

 maxage See maxage in the table.
Returns
None.
Throws
Exception if the authentication service is not configured.
Exception if a system error is encountered.
Syntax
$AdminTask modifyESSWSFedConfiguration {[-domain domain] [-secure
true|false] [-maxage milliseconds|-1]}
Reference
Table 10. modifyESSWSFedConfiguration parameters
Parameter Type Default Description Required
domain string Default Specifies the domain No.
field of a session
tracking cookie. This
value controls
whether a browser
sends a cookie to
particular servers.

For example, if you

specify a particular
domain, session
cookies are sent to
hosts in that domain.
A browser does not
accept the cookie if
the cookie domain
conflicts with the
domain specified in
the request URL. If
not specified, the
default domain is the
domain of this server.
#Examples:
# domain = .ibm.com
# domain = none
# domain = default
secure boolean True Specifies that the No.
session cookies
include the secure
field. Enabling the
feature restricts the
exchange of cookies
to HTTPS sessions
only.

112 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 10. modifyESSWSFedConfiguration parameters (continued)
Parameter Type Default Description Required
maxage integer / string Session Specifies the amount No.
of time that the
cookie lives on the
client browser.
Specify the maximum
age in seconds.
Setting maxage to
“session” specifies a
lifetime of current
browser session.

Configuring the TrustClientRole for the authentication service:

If single sign-on is enabled, the authnsvc_ctges authentication service application

installs into the WebSphere Application Server Network Deployment server. The
authentication service contains a role called TrustClientRole. If WebSphere
Application Server Network Deployment security is enabled, the WebSphere
Application Server Network Deployment administrator assigns users or groups to
TrustClientRole.

Before you begin

When single sign-on clients are configured and application security is enabled, the
clients are configured with an identity that authenticates the client to WebSphere
Application Server Network Deployment when it calls the authentication service.
That identity needs to be registered with WebSphere Application Server Network
Deployment, and it is either mapped to the TrustClientRole role of the
authentication service, or added to a group that is mapped to the TrustClientRole
role of the authentication service.

Note: This section does not apply to embedded WebSphere. The embedded
WebSphere ISC console does not provide application role mapping capability.
Wsadmin interfaces must be used to map application roles under embedded
WebSphere.

About this task

To add users and groups to the TrustClientRole of the authentication service in the
WebSphere Application Server Network Deployment console, follow these steps:

Procedure
1. Open Applications > Enterprise Applications > authnsvc_ctges > Security role
to user/group mapping.
2. Use Look up users or groups to select the users or groups to add to the
TrustClientRole role. You can, alternatively, select Everyone? or All
authenticated? boxes.
3. Click OK.
4. Save the configuration.

Chapter 4. Deploying manually reusing existing middleware 113

 Results

To query the users and groups currently mapped to the TrustClientRole of the
authentication service, use the wsadmin AdminApp view command:
wsadmin>$AdminApp view authnsvc_ctges

Alternatively, users and groups can be added to the TrustClientRole of the

authentication service using the wsadmin AdminApp edit command. For example, to
set the TrustClientRole to allow access to all authenticated users you would use the
following command:
wsadmin>$AdminApp edit authnsvc_ctges
{-MapRolesToUsers { {"TrustClientRole" no yes "" ""}} }

See the WebSphere Application Server Network Deployment documentation for

more information about the AdminApp edit command and the use of the
–MapRolesToUsers option.

The following sample Jython script called setAuthnSvcRoleAll.py sets the

TrustClientRole role to allow access to all authenticated users:
import sys

global AdminConfig
global AdminControl
# Usage:
# was_profile_dir/bin/wsadmin -lang jython -f setAuthnSvcRoleAll.py
# where was_profile_dir is the WebSphere profile directory

AdminApp.edit("authnsvc_ctges", ["-MapRolesToUsers",
[["TrustClientRole", "No", "Yes", "", ""]]] )
AdminConfig.save()

Clock synchronization:

Verify that the time, date, and time zone are synchronized among all servers
participating in the protected domain.

Because single sign-on authentication uses time-sensitive tokens, you must verify
that the time, date, and time zone are synchronized. This verification must be
done for all servers that are participating in the protected domain, such as the the
WebSphere Application Server Network Deployment server and the Tivoli
Application Dependency Discovery Manager server.

If the time difference is too high between servers, the single sign-on token might
prematurely expire on some servers and cause authentication or validation failures.

WebSphere Application Server Network Deployment and authentication

service-based single sign-on tokens are assigned a lifetime of two hours by default.
For best results, servers must be synchronized to within 5 minutes to ensure that
single sign-on tokens are evaluated consistently.

Authentication service logging:

The authentication service LTPA token provider and the authentication service
token service infrastructure logs can be useful when troubleshooting connection
errors related to the authentication service.

114 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Configuration of the authnsvc_ctges authentication service LTPA token provider
logging
Authentication service LTPA token provider logging is performed using the
java.util.logging.Logger message and trace logging facility. Logging
characteristics can be configured using the WebSphere Application Server
Network Deployment administrator console.
1. From the WebSphere Application Server Network Deployment
administrator console, select Troubleshooting > Logs and trace >
server 1 > Change Log Detail Levels.
2. Set the com.ibm.security.ess.authn.provider log level to All Messages
and Traces under both the Configuration and Runtime tabs.
3. Click OK and then save.
4. Restart the server.
Configuration of authnsvc_ctges authentication service token service
infrastructure logging
Authentication service user name provider and token service infrastructure
logging is performed using the Log4J utility. Logging characteristics can be
configured by modifying the WAS_PROFILE/installedApps/cell
name/authnsvc_ctges.ear/com.ibm.security.ess.war/WEB-INF/classes/
log4j.properties file, then restarting the server.
Format of the log4j.properties file:
### direct log messages to stdout ###

log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.Target=System.out
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{HH:mm:ss,SSS} %5p %C{1}.%M
(%L): %m%n

### set log levels - for more verbose logging change ’info’ to ’debug’ ###

log4j.rootLogger=TRACE, stdout
log4j.logger.org.eclipse=info
log4j.logger.org.apache=info
log4j.logger.org.apache.xml.security=info
log4j.logger.org.xmlsoap.schemas.ws=info
log4j.logger.org.eclipse.higgins=trace
log4j.logger.org.eclipse.alf=info
log4j.logger.org.apache.axis.transport.http.HTTPSender=info
log4j.logger.org.openid=info
log4j.logger.com.ibm.openid=info
log4j.logger.com.ibm.security.ess=trace
In most cases, only the log4j.logger.org.eclipse.higgins and
log4j.logger.com.ibm.security.ess properties must be set to trace.
Logging levels, listed in order of least to most inclusive, are:
1. fatal
2. error
3. warn
4. info
5. debug
6. trace
Authentication service configuration AdminTask command logging
Authentication service configuration AdminTask command logging is
performed using the java.util.logging.Logger message and trace logging

Chapter 4. Deploying manually reusing existing middleware 115

 facility. Logging characteristics can be configured using the WebSphere
Application Server Network Deployment administrator console.
1. From the WebSphere Application Server Network Deployment
administrator console, select Troubleshooting > Logs and trace >
server 1 > Change Log Detail Levels.
2. Set the com.ibm.security.ess.authn.provider log level to All Messages
and Traces under both the Configuration and Runtime tabs.
3. Click OK and then save.
4. Restart the server.

Manually configuring JMS queues:

This procedure provides details on steps to configure JMS queues, which must be
completed before using the product installation program.

About this task

During the installation process, the SmartCloud Control Desk installation program
provides you with the option of automatically configuring SmartCloud Control
Desk middleware. If you elect to have the SmartCloud Control Desk installation
program automatically configure SmartCloud Control Desk middleware, it creates
and configures JMS message queues for you. If you elect to manually configure
SmartCloud Control Desk middleware for use with SmartCloud Control Desk, you
must manually configure these message queues.

To configure the JMS queues, complete the following steps:

Procedure
1. Start the WebSphere Application Server Network Deployment application
server.
2. Start Internet Explorer and open the WebSphere Application Server Network
Deployment administrative console by typing the following URL:
http://<server_name>:<port_number>/ibm/console
For example, enter a URL like the following sample URL:
http://localhost:9060/ibm/console
3. At the login screen, enter your user ID, then click Log in. This action opens
the Welcome screen for the WebSphere Application Server Network
Deployment administrative console.
4. Click Service Integration > Buses to open the Buses dialog. A bus is a group
of interconnected servers and clusters that have been added as members of
the bus.
5. Click New to open the Create a new Service Integration Bus panel where
you can add a new service integration bus.
6. Enter intjmsbus as the name of the new bus in the Name field.
7. Clear the Bus security check box. If you leave this box checked, intjmsbus
inherits the Global Security setting of the cell.

116 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Figure 10. Create a new Service Integration Bus

8. Click Next.
9. Click Finish.
10. Click Save. This step propagates the JMS bus setup to the cluster
configuration.

Adding a server to the service integration bus:

A server must be defined for the service integration bus.

About this task

Complete the following steps to add a server to the service integration bus:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Service Integration > Buses to open the Buses dialog box.
2. Click intjmsbus to open the Buses > intjmsbus dialog box.
3. Under Topology, click Bus members.
4. In the Buses > intjmsbus > Bus members dialog box, click Add to open the
Add a new bus member dialog box.
5. Select the Server option, and select the server name ctgNode01:MXServer to
add to the bus, and then click Next.
6. Check that the Data store radio button is selected, and then click Next.
Alternatively, you can use a file store to store messages by selecting File store.
7. From the Specify data store properties panel, select Use existing data source.
8. For Data source JNDI name , enter jdbc/intjmsds. For Authentication alias,
select ctgCellManager01/maxJaasAlias, and then click Next.
9. From the Tune application server for messaging performance panel, click
Next.
10. Click Finish.
11. Click Save.

Chapter 4. Deploying manually reusing existing middleware 117

Figure 11. Add a server to the service integration bus

Creating the service integration bus destination for the continuous inbound (CQINBD)
queue:

You must create a service integration bus destination for the continuous inbound
(CQINBD) queue.

About this task

To add a logical address for the continuous inbound bus destination queue
(CQINBD) within the JMS bus, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment Administrative
Console, click Service Integration > Buses to open the Buses dialog box.
2. Click intjmsbus to open the Buses > intjmsbus dialog box.
3. Click Destinations under Destination resources to open the Buses >
intjmsbus > Destinations dialog box.
A bus destination, for example CQINBD, is a virtual place within a service
integration bus where applications can attach and exchange messages.
4. Click New to open the Create new destination dialog box.
5. Leave Queue checked as the destination type, and click Next to open the
Create new queue dialog box.
6. Type CQINBD in the Identifier field and Continuous Queue Inbound in the
Description field, then click Next to open the Create a new queue for
point-to-point messaging dialog box.
7. Select the Bus Member pull-down and choose
Node=ctgNode01:Server=MXServer as the bus member that will store and
process messages for the CQINBD bus destination queue.
8. Click Next to open the Confirm queue creation dialog box.
9. Review your selections, then click Finish to complete the creation of the
CQINBD bus destination queue.
10. Navigate the path Buses > intjmsbus > Destinations, then click CQINBD to
open the configuration dialog box.
11. Click None as the Exception destination value.
12. Click Apply.

118 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

13. Click Save.

Creating the service integration bus destination for the sequential inbound (SQINBD)
queue:

You must create the service integration bus destination for the sequential inbound
(SQINBD) queue.

About this task

To add a logical address for the sequential inbound bus destination queue
(SQINBD) within the service integration bus, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment Administrative
Console, click Service Integration > Buses to open the Buses dialog box.
2. Click intjmsbus to open the Buses > intjmsbus dialog box.
3. Click Destinations under Destination resources to open the Buses >
intjmsbus > Destinations dialog box. A bus destination is a virtual place
within a service integration bus where applications can attach and exchange
messages.
4. Click New to open the Create new destination dialog box.
5. Leave Queue checked as the destination type, and click Next to open the
Create new queue dialog box.
6. Enter SQINBD in the Identifier field and Sequential Queue Inbound in the
Description field, then click Next to open the Create a new queue for
point-to-point messaging dialog box. Note that you must use this value and it
must contain only uppercase letters.
7. Select the Bus Member pull-down and choose
Node=ctgNode01:Server=MXServer
8. Click Next to open the Confirm queue creation dialog box.
9. Review your selections, then click Finish to complete the creation of the
SQINBD bus destination queue.
10. Navigate the path Buses > intjmsbus > Destinations, then click SQINBD to
open the configuration dialog box.
11. Click None as the Exception destination value.
12. Click Apply.
13. Click Save.

Chapter 4. Deploying manually reusing existing middleware 119

Figure 12. Add a logical address for the sequential inbound bus destination queue

Creating the service integration bus destination for the sequential outbound (SQOUTBD)
queue:

You must create the service integration bus destination for the sequential outbound
(SQOUTBD) queue.

About this task

To add a logical address for the sequential outbound bus destination queue
(SQOUTBD) within the service integration bus, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Service Integration > Buses to open the Buses dialog box.
2. Click intjmsbus to open the Buses > intjmsbus dialog box.
3. Click Destinations under Destination resources to open the Buses >
intjmsbus > Destinations dialog box. A bus destination, for example
SQOUTBD, is a virtual place within a service integration bus where
applications can attach and exchange messages.
4. Click New to open the Create new destination dialog box.
5. Leave Queue checked as the destination type, and click Next to open the
Create new queue dialog box.
6. Enter SQOUTBD in the Identifier field and Sequential Queue Outbound in the
Description field, then click Next to open the Create a new queue for
point-to-point messaging dialog box. You must use this value and it must
contain only uppercase letters.
7. Select the Bus Member menu and choose Node=ctgNode01:Server=MXServer
as the bus member that stores and processes messages for the SQOUTBD bus
destination queue.
8. Click Next to open the Confirm queue creation dialog box.
9. Review your selections, then click Finish to complete the creation of the
queue.
10. Navigate the path Buses > intjmsbus > Destinations, then click SQOUTBD
to open the configuration dialog box where you must make the following
changes:
11. Click None as the Exception destination value.

120 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 12. Click Apply.
13. Click Save.

Creating the JMS connection factory:

Add a connection factory for creating connections to the associated JMS provider
of point-to-point messaging queues.

About this task

To create the JMS connection factory, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Connection factories.
2. From the Scope drop-down list, select Cell=ctgCell01.
3. Click New.
4. Verify that the Default Messaging Provider is selected and click OK.
5. Enter the following information:
Name Enter intjmsconfact.
JNDI name
Enter jms/maximo/int/cf/intcf.
Bus name
Select intjmsbus.

Figure 13. Create the JMS connection factory

6. Click Apply.

Chapter 4. Deploying manually reusing existing middleware 121

 7. Click Save.

Creating the continuous inbound (CQIN) JMS queue:

You must create a JMS queue (CQIN) as the destination for continuous inbound
point-to-point messages.

About this task

To create the CQIN JMS queue, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Queues.
2. From the Scope drop-down list, select Cell=ctgCell01.
3. Click New.
4. Verify that the Default Messaging Provider is selected and click OK.
5. Enter the following information, and click OK.
Name Enter CQIN.
This value must contain only uppercase letters.
JNDI name
Enter jms/maximo/int/queues/cqin
Bus name
Select intjmsbus.
Queue name
Select CQINBD.

Figure 14. Create the CQIN JMS queue

122 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

6. Click OK.
7. Click Save.

Creating the sequential inbound (SQIN) JMS queue:

You must create a JMS queue (SQIN) as the destination for sequential inbound
point-to-point messages.

About this task

To create the SQIN JMS queue, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Queues.
2. From the Scope drop-down list, select Cell=ctgCell01.
3. Click New.
4. Verify that the Default Messaging Provider is selected and click OK.
5. Enter the following information, and click OK.
Name Enter SQIN.
This value must contain only uppercase letters.
JNDI name
Enter jms/maximo/int/queues/sqin
Bus name
Select intjmsbus.
Queue name
Select SQINBD.

Chapter 4. Deploying manually reusing existing middleware 123

Figure 15. Create the SQIN JMS queue

6. Click OK.
7. Click Save.

Creating the sequential outbound (SQOUT) JMS queue:

You must create a JMS queue (SQOUT) as the destination for sequential outbound
point-to-point messages.

About this task

To create the SQOUT JMS queue, complete the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Queues.
2. From the Scope drop-down list, select Cell=ctgCell01.
3. Click New.
4. Verify that the Default Messaging Provider is selected and click OK.
5. Enter the following information, and click OK.
Name Enter SQOUT.
This value must contain only uppercase letters.
JNDI name
Enter jms/maximo/int/queues/sqout
Bus name
Select intjmsbus.
Queue name
Select SQOUTBD.

124 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Figure 16. Create the SQOUT JMS queue

6. Click OK.
7. Click Save.

Creating JMS activation specification for the continuous inbound queue (CQIN):

You must activate the continuous inbound queue (CQIN) before it can receive
messages.

About this task

Complete the following steps to activate the CQIN queue:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Activation Specifications.
2. From the Scope drop-down list, select Cell=ctgCell01.
3. Click New.
4. Select Default messaging provider and then click OK.
5. Enter the following information, and then click OK.
Name intjmsact
This value is case-sensitive. This value must be lowercase.
JNDI name
intjmsact
Destination type
Queue
Destination JNDI name
jms/maximo/int/queues/cqin

Chapter 4. Deploying manually reusing existing middleware 125

 Bus name
intjmsbus
Maximum concurrent MDB invocations per endpoint
10

Figure 17. Activate the CQIN queue

6. Click OK, and then click Save.

Error queues:

You must create an error queue that receives redirected messages from the
continuous queue (CQIN).

When the messages go in error, the error queue receives redirected messages from
the continuous queue (CQIN).

Creating the service integration bus destination for the inbound error queue
(CQINERRBD) queue:

You must add a logical address for the inbound error queue (CQINERRBD) queue
within the JMS bus.

About this task

Perform the following steps:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Service Integration > Buses to open the Buses dialog box.

126 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 2. Click intjmsbus to open the Buses > intjmsbus dialog box.
3. Click Destinations under Destination resources to open the Buses >
intjmsbus > Destinations dialog box. A bus destination is a virtual place
within a service integration bus where applications can attach and exchange
messages.
4. Click New to open the Create new destination dialog box.
5. Leave Queue checked as the destination type, and click Next to open the
Create new queue dialog box.
6. Enter CQINERRBD in the Identifier field and Error Queue Inbound in the
Description field, then click Next to open the Create a new queue for
point-to-point messaging dialog box. You must use this value and it must
contain only uppercase letters.
7. From the Bus Member menu, select Node=ctgNode01:Server=MXServer
8. Click Next to open the Confirm queue creation dialog box.
9. Review your selections, then click Finish to create the CQINERRBD bus
destination queue.
10. Select Buses > intjmsbus > Destinations, then click CQINERRBD to open the
configuration dialog box where you must make the following changes:
a. Select the Specify option and enter CQINERRBD as the exception destination
value.
b. Change the Maximum failed deliveries value to 5.
This option is the maximum number of times you want the system to
process a failed messaging attempt before forwarding the message to the
exception destination.

Figure 18. Creating the service integration bus destination for the inbound error queue

11. Click Apply.

12. Click Save.
13. From the WebSphere Application Server Network Deployment administrative
console, click Service Integration > Buses to open the Buses dialog box.
14. Click intjmsbus to open the Buses > intjmsbus dialog box.
15. Click Destinations under Destination resources to open the Buses >
intjmsbus > Destinations dialog box.
16. Select CQINBD.

Chapter 4. Deploying manually reusing existing middleware 127

 17. Specify CQINERRBD as the exception destination. Set the Maximum failed
deliveries value to 5.

Figure 19. Set the exception destination

18. Click OK.

19. Click Save.

Creating the error (CQINERR) JMS queue:

After creating the Error Queue Bus Destination, you create the Error queue.

About this task

To create the Error queue, complete the following steps.

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Queues.
2. From the Scope drop-down list, select Cell=ctgCell01.
3. Click New.
4. Verify that the Default Messaging Provider is selected and click OK.
5. Enter the following information, and click OK.
Name Enter CQINERR.
This value must contain only uppercase letters.
JNDI name
Enter jms/maximo/int/queues/cqinerr

128 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Bus name
Select intjmsbus.
Queue name
Select CQINERRBD.

Figure 20. Create the Error queue

6. Click OK.
7. Click Save.

Creating JMS activation specification for the inbound error queue (CQINERR):

You must activate the continuous inbound queue (CQINERR) before it can receive
messages.

About this task

Complete the following steps to activate the CQINERR queue:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Resources > JMS > Activation Specifications.
2. From the Scope menu, select Cell=ctgCell01, and then click Apply.
3. Click New to complete the General Properties section for the new JMS
activation specification.
4. Click OK.
5. Enter the following information, and click OK.
Name Enter intjmsacterr.
This value must only contain lowercase letters.

Chapter 4. Deploying manually reusing existing middleware 129

 JNDI name
Enter intjmsacterr.
This value must be the same as the one used for the Name field.
Destination type
Enter Queue.
Destination JNDI name
jms/maximo/int/queues/cqinerr
Bus name
intjmsbus
Maximum concurrent MDB invocations per endpoint
10

Figure 21. Activate the continuous inbound queue

6. Click OK.
7. Click Save.
8. Ensure that you stop all IBM-related processes and daemons.
9. You must now restart these processes for the update to take effect.
10. Start the bus member for the ctgNode MXServer intjmsbus if it is not started.
If you cannot start ctgNode MXServer intjmsbus, restart MXServer under
Servers > Application servers.

Manually creating a data source for the persistent store:

If you chose to manually configure WebSphere Application Server Network

Deployment, you must create a data source in order to store JMS messages in a
DB2 database.

130 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

About this task

You have the option of having WebSphere Application Server Network

Deployment use a DB2 database to store JMS messages. For more information
about WebSphere Application Server Network Deployment message storage,
including the usage of products other than DB2, see http://
publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/
com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tjm0045_.html.

To create a data source for the persistent store, complete the following steps:

Procedure
1. Create a system user and password on the server hosting the database server.
For example, a user named mxsibusr with a password of mxsibusr.
2. Create and configure the database.
a. Open DB2 Control Center.
b. Browse to the Databases folder listed under your system.
c. Right-click the Databases folder and select Create Database > Standard.
d. Create a database named maxsibdb using default settings.
e. After the database has been created, expand the maxsibdb database and
select User and Group objects.
f. Right-click DB Users and select Add.
g. Select mxsibusr from the User menu.
h. Grant all authorities to the mxsibusr except Security administrator authority.
i. Click Apply.
j. Verify that you can connect to the database using the mxsibusr user by
right-clicking maxsibdb and selecting Connect.
3. Configure J2C authentication data and JDBC provider in WebSphere
Application Server Network Deployment.
a. Open and login to the WebSphere Application Server Network Deployment
administrative console.
b. Browse to Security > Global Security.
c. Under the Authentication header, click Java Authentication and
Authorization Service > J2C authentication data.
d. Click New.
e. Complete the following fields in the User identity form.
Alias maxJaasAlias
User ID
mxsibusr
Password
Password you created for mxsibusr.
Description
SIB database user alias.
f. Click Apply, and then click Save.
g. From the WebSphere Application Server administrative console, browse to
Resources > JDBC > JDBC Providers.
h. Under Scope, click Show scope selection drop-down list with the all
scopes option, select Cell=ctgCell01, and then, under Preferences, click
Apply.

Chapter 4. Deploying manually reusing existing middleware 131

 i. Click New.
j. Specify the following values, and then click Apply:
Database type
DB2
Provider type
DB2 Universal JDBC Driver Provider
Implementation type
XA data source
Name maxJdbcProvider
k. Click Next.
l. Complete the WebSphere Application Server variable
${DB2UNIVERSAL_JDBC_DRIVER_PATH} field with a value of
<WAS_HOME>ctgMX\lib. For example, C:\Program Files\IBM\WebSphere\
AppServer\ctgMX\lib.
m. Click Next.

Figure 22. Create a new JDBC provider

n. Click Finish.
o. Click Save.
4. Open a command prompt and copy <DB2_HOME>/java/db2jcc.jar and
<DB2_HOME>/java/db2jcc_license_cu.jar to the <WAS_HOME>\ctgMX\lib
directory. Go back to Resources > JDBC > JDBC Providers >
maxJdbcProvider, and correct the class path if required for both db2jcc.jar
and db2jcc_license_cu.jar. Ensure that each jar file has the full path from
${DB2UNIVERSAL_JDBC_DRIVER_PATH}
5. Configure WebSphere Application Server:
a. From the WebSphere Application Server Network Deployment
administrative console, browse to Resources > JDBC > Data sources.
b. Under Scope, click Show scope selection drop-down list with the all
scopes option, select Cell=ctgCell01, and then, under Preferences, click
Apply.
c. Click New.

132 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 d. Specify the following values:
Data source name
intjmsds
JNDI name
jdbc/intjmsds
e. From the Component-managed authentication alias and XA recovery
authentication alias menu, select maxJaasAlias
f. Click Next.
g. Choose Select an existing JDBC provider, and then select maxJdbcProvider
from the menu.
h. Click Next.
i. Specify the following values:
Database name
maxsibdb
Driver type
4
Server name
Specify the DB2 server host name.
Port number
Specify the DB2 port number. For example, 50005.
j. Ensure the Use this data source in container managed persistence (CMP)
option is selected, and then click Next.
k. Click Finish.
l. Click Save.
6. Verify the data source by selecting intjmsds, and then clicking Test
Connection.

Installing the product and manually configuring middleware

You can deploy SmartCloud Control Desk with configured middleware before the
installation begins. You use this procedure if your organization has specific policies
and procedures that govern how you create databases, database instances, and
users within your organization.

Before you begin

Ensure that you meet prerequisite conditions.

v The database server, the directory server, and application server services must be
started and active.
v The /tmp and /var/tmp directories must be present on the system. The
installation program depends on these directories for information during
deployments on IBM WebSphere Application Server Network Deployment.
v On the administrative workstation, temporarily shut down any noncritical
processes that can have a negative effect on the installation, such as antivirus
software.
v Ensure that the Windows DEP setting does not prevent the launchpad from
running: Select Start > Settings > Control Panel > System > Advanced >
Performance > Settings > Data Execution Prevention. Select Turn on DEP for
essential Windows programs and services only and click Apply. You might be
asked to reboot the server.

Chapter 4. Deploying manually reusing existing middleware 133

 v For Linux and UNIX systems with middleware installed, the command hostname
-f must return a fully qualified host name. If necessary, consult the
documentation for your operating system. Alternatively, you can provide the IP
address for the system.
v Enable a remote execution and access service on every system that has
middleware installed. Each remote system must support a remote access
protocol. Each system must accept remote logins from a user name and
password that were configured on the target server. Remote access protocols
include SSH and Windows SMB. If the remote system is a Windows server, you
must configure remote execution and access to use SMB.
v The DB2 database must be prepared.
– If DB2 is installed on a Linux or UNIX system, you must create the instance
user and the home directory for the user on the DB2 server.
– The database instance owner home directory must have 8 GB of space
available regardless of whether a database is installed in that location.
– The user ID for the DB2 instance administrator must have SYSADM (system
administration) authority. You specify this user ID during the product
installation program. See the DB2 product documentation for information
about creating a user with SYSADM authority on the DB2 server. You must
add root to a group with SYSADM authority for UNIX systems.
– To avoid high system memory usage by DB2, you can set the following DB2
property and then restart the DB2 server:
db2 update dbm cfg using KEEPFENCED NO
v If you use DB2 on UNIX systems with SmartCloud Control Desk, you must add
root to a group with SYSADM authority for the database instance. This
membership must be in place before you start the SmartCloud Control Desk
installation program.

About this task

The instructions are for a multiple server installation that uses default values.

If you experience problems with the user interface of the installation program
when you install on AIX 6.x systems remotely, reattempt the installation locally.
Use the console or an X terminal on the system locally.

Procedure
1. Log in on the administrative system.
2. Start the product installation program from the launchpad.
a. Start the launchpad. Browse to the root directory of the downloaded
installation image, and run the following command:
Windows
launchpad.exe
UNIX launchpad.sh
If the launchpad does not start the installation, you can start the product
installation program directly. On the downloaded installation image, browse
to \Install\\, and run one of the following commands:
Windows
v install.bat
v install_win64.bat
UNIX
134 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
 v install_aix64.sh
v install_linux32.sh
v install_linux64.sh
3. Select a language for the installation and click OK.
4. On the Choose Installation Folder panel, specify the path to the location
where you want to install SmartCloud Control Desk.
You can specify a description for the installation. A description is useful for
differentiating between multiple installations that are hosted on the same
administrative workstation.
5. Review the information that is on the Verify Installation Location panel. The
panel shows any previous installation information that was found based on
the installation directory that you specified on the previous panel. After you
advance past this panel, you cannot go back and change the installation
directory for this installation.
If a more recent version of the installation program is found in the specified
target directory, you are notified. The notification means that you are using an
older version of the installation program. The version found on the
administrative workstation is newer and can contain important features and
enhancements. To use the newer version of the installation program, select the
option on the notification panel and click Next. This action exits the current
installation process and restarts the installation process with the newer
installation program. If you do not select the option, you continue the
installation with the older version of the installation program.
6. On the Package Summary panel, review the package deployment information.
This panel lists version information for both new and existing packages on the
system. Target package version information indicates the package version
being currently deployed.
7. On the Choose Deployment panel, specify Simple or Custom as the
deployment type.
8. On the Import Middleware Configuration Information panel, you select
Import middleware configuration information to have the product
installation program reuse the middleware installation program values. These
values are used as default values for the same fields in the product
installation program.
The Workspace location field refers to the location of the topology file that
contains the values that were specified for the middleware installation
program. The file is located in the workspace that was defined during the
middleware installation task. For example, C:\ibm\tivoli\mwi\workspace for
Windows or /root/ibm/tivoli/mwi/workspace for UNIX.
If you selected the simple deployment, the middleware default information is
not used.
9. On the Database Type panel, specify the software to use for the Maximo
database.
10. On the Database panel, specify configuration information for your database
software.
For things such as the database user ID, the database name, the database
instance for SmartCloud Control Desk, and the schema name, if the values do
not exist when you specify them, they are created. Database users and
database instance names cannot contain spaces.
For DB2, the user ID cannot be the same as the instance administrator user ID.
For DB2, the database instance is created if it does not exist, but the user and
its associated home directory must exist on the DB2 server. For DB2, the

Chapter 4. Deploying manually reusing existing middleware 135

 schema name can be the same value as the owner of the table spaces that are
defined or it can be a different value, such as maximo.
After you specify configuration information for your database software, the
installation program validates the information with the database server.
11. On the Automate Database Configuration panel, select The database has
already been created and configured and click Next.
This step assumes that you created a database instance, a database, table
spaces, a user, and schema for use with SmartCloud Control Desk. See
“Manually configuring the database” on page 73. If you have not manually
configured the database before selecting The database has already been
created and configured you are prompted to complete them before you restart
the installation program.
12. On the Database Tablespace panel, specify information about the table space
of the database.
When you click Next, the product installation program connects to the
database server and validates the information that you specified.
13. When the database validation is complete, on the Application Server Type
panel, specify the application server type for the product deployment.
You have the option of configuring WebSphere Application Server Network
Deployment automatically through the product installation program.
14. On the WebSphere Connectivity panel, specify host information for the
WebSphere Application Server Network Deployment.
15. On the WebSphere Remote Access Authorization panel, specify authorization
information for WebSphere Application Server Network Deployment
configuration.
16. On the WebSphere Application Server Network Deployment Configuration
panel, specify configuration information for WebSphere Application Server
Network Deployment.
The web server port should match an existing HTTP server port value that
you configured when you set up WebSphere Application Server Network
Deployment. If you specify a different value for the web server port, you must
restart WebSphere Application Server Network Deployment at the conclusion
of the installation. Restarting the server activates the new port and makes it
available for incoming requests.
The application server name that you specify is created if it does not exist.
17. On the Security panel, specify the method to use for authenticating and
authorizing users.
18. On the Specify Maximo Users panel, enter Maximo database user information.
Maximo administration user
The product administrator user ID that is used for initial configuration
and adding users.
Maximo system registration user
The user ID that is used for the self-registration of users.
Maximo system integration user
The user ID that is used with enterprise adapters.

Custom user ID and password values are stored in the Maximo database. The
default user IDs of maxadmin, maxreg, and maxintadm are also created as
users in the Maximo database. Creation of the default user IDs is done for
internal processing purposes. If you use Maximo database security for
authentication and authorization, the default user IDs can be used to log in to

136 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 the application. If you regard this condition as a security risk, you can modify
the passwords for the default user IDs. You modify passwords for the user
IDs in the Users application.
19. On the Security panel, specify the names of the user and group base entries
and specify how SmartCloud Control Desk users are created.
User base entry
If you do not plan to use the default LDAP schema that is provided
with SmartCloud Control Desk, specify the user base entry that you
want to use.
Group base entry
If you do not plan to use the default LDAP schema, specify the group
base entry that you want to use.
You can specify that the installation program creates the required users.
Otherwise, you must create users manually before you continue.
If you are not using the default LDAP schema that is provided, you must
create it yourself before you advance beyond this panel. The values that are
specified for the User base entry and Group base entry fields are used to
configure the VMMSYNC cron task. To create your own LDAP schema and
create users manually, you can modify the default add-on LDIF data and
import it into your LDAP repository
20. On the Integration Adapter JMS Configuration panel, specify Java Message
Service configuration information. A JMS server requires a DB2 data
repository to be configured to maintain messages. If you are using another
database type, you cannot configure message persistence. If you specify that
JMS messages are not to be persisted, you can configure the JMS
implementation manually later.
Specify the name of the database to be used by JMS. For DB2, you can specify
whether to persist JMS messages within DB2.
Select Do not persist JMS messages if you are deploying SmartCloud Control
Desk with Oracle or Microsoft SQL Server. When you click Next, the
installation wizard skips to the SMTP Configuration panel.
21. If you specified that JMS messages should persist, specify additional JMS
configuration information in the DB2 Database Server Configuration panel.
The JMS data store can be created as a DB2 database only.
22. If you specified that JMS messages should persist, specify authorization
information for the automatic configuration feature in the DB2 Database
Server Remote Access Authorization panel.
For Windows, the user ID must be a member of the DB2ADMNS group.
For Linux or UNIX, the user ID must be root and a member of a group with
SYSADM authority for the database instance.
23. If you specified that JMS messages should persist, specify additional DB2
information in the DB2Database Instance Configuration panel.
24. In the WebSphere Application Server Network Deployment keystore file panel,
browse to where you copied the trust.p12 keystore, and then click Next.
25. On the SMTP Configuration panel, specify the SMTP configuration
information that is used by workflows to communicate with workflow
participants.
The administrator e-mail address is the e-mail address that is used to send
messages. If you leave the fields blank, you must configure the SMTP
parameters through the product interface as a post-installation task.

Chapter 4. Deploying manually reusing existing middleware 137

 26. On the Data Integration and Context Menu Services Options panel, select the
option that indicates where the database tables for these functions should be
created: in the Maximo ("same") database, or in a separate database instance
that you have already created for this purpose. If you are installing the Entry
edition, choose the Maximo database. These tables are created but are not by
the Entry edition.
27. On the Base Language Selection panel, specify the base language for the
installation.
28. On the Additional Language Selection panel, you can optionally specify one
or more additional languages that the installation is to support.
29. On the Run Configuration Step panel, specify how to perform the
configuration step of the installation. If you do not select an option, the
configuration step proceeds when you click Next.
Copy files now, but perform the installation configuration step later
Select this option to copy files from the installation source to the
administrative workstation. You must perform the configuration step
at a later time to complete the deployment.

Important: Do not install another product before completing the

configuration step of the original installation. Installing another
product before running the configuration step for this installation
overwrites the taskstore, which prevents the original installation from
ever being deployed.
The configuration values that you specify are stored in the
install_home\maximo\applications\maximo\properties\
maximo.properties and install_home\etc\install.properties files.
You run the configuration steps outside of the product installation
program by using the taskrunner utility, in the install_home\scripts
directory. Run the taskrunner utility from the command line.
install_home\scripts\taskrunner [CONTINUE <STOPONERROR|NOSTOPONERROR>]

The taskrunner uses the configuration values that are stored in the
maximo.properties and install.properties files to configure
SmartCloud Control Desk.
If you run taskrunner with the NOSTOPONERROR parameter, the
taskrunner continues despite errors. If you run taskrunner with the
STOPONERROR parameter, the taskrunner stops when it encounters an
error. If you used STOPONERROR, you can rectify the conditions that
caused the error. You can then resume the installation at the point
where the last successfully completed task was recorded in the
previous attempt by starting taskrunner with the CONTINUE parameter.
Deploy application files manually later
Select this option to manually deploy application files to the
application server.
Defer the update of the Maximo database
Select this option if you want to manually run the database update
task for the product deployment. This option can be used when there
is a fix pack available that addresses known issues with the updatedb
script. In this scenario, you choose the Defer the update of the
Maximo database option, apply the fix pack, and then run the
updatedb -v1 command manually.

138 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 30. On the Choose Shortcut Folder panel, specify where you want SmartCloud
Control Desk icons created.
If you select In the Start Menu and use Internet Explorer, add the
SmartCloud Control Desk URL to the trusted sites web content zone. Disable
the option that requires server verification for all sites in the zone.
Do not select In the Quick Launch Bar. The selection does not create a
shortcut in the Quick Launch bar.
Attention: Shortcuts are created for Windows systems only.
31. On the Input Summary panel, review the information that you have provided
for the product installation program.
If necessary, use Previous to return to previous panels to change values.
32. On the Pre-Installation Summary panel, review the installation information,
then click Install.
The installation process begins. You can monitor the progress of the
installation by viewing the messages that are shown.
33. On the Installation Completed panel, review any information presented, then
click Done.
Attention: In some cases, on AIX systems, the Installation Completed panel
might appear blank. Click Done to exit the installation program.

What to do next

Complete the post installation tasks that are required for installing with manual
middleware configuration.

If you selected the Deploy application files manually later option, you must now
deploy the maximo.ear and maximoiehs.ear files.

You can install optional content and integration modules from the launchpad.
“Maintaining EAR files” on page 266
This section contains information about maintaining SmartCloud Control Desk
EAR files.

Installing optional content

Install the relevant optional content package for your edition of the product.

Optional content is often used in development environments as a way to begin

developing your own content.

If you do not install optional content during the product installation process, you
can install it later. If you install it later, you must update the database and rebuild
and deploy the maximo.ear file.

Installing optional integration modules

Install integration module packages in order to set up integrations with other
products.

You can install these integration modules from the Integrations page of the
launchpad:
IBM Tivoli Provisioning Manager Integration Module
This integration module enables you to integrate Tivoli Provisioning

Chapter 4. Deploying manually reusing existing middleware 139

 Manager with the release management process. For example, you can use
Tivoli Provisioning Manager as a Definitive Media Library. See the Release
management section of the information center for more information about
this integration.
Deployed Assets CMS LIC Enablement Package
This package is required if you plan to use the Context Menu Service to
manage launch-in-context actions for deployed assets. See the Planning
section of the information center for information about options for
launch-in-context actions.
CI AppsCMS LIC Enablement Package
This package is required if you plan to use the Context Menu Service to
manage launch-in-context actions for actual configuration items. See the
Planning section of the information center for information about options
for launch-in-context actions.
Rational ClearQuest OSLC Integrations
This integration enables you to use the Open Services for Lifecycle
Collaboration (OSLC) technology to link from the Problems application to
Rational ClearQuest to share information about problems and their
solutions.
Rational Team Concert OSLC Integrations
This integration enables you to use the Open Services for Lifecycle
Collaboration (OSLC) technology to link from the Problems application to
Rational Team Concert to share information about problems and their
solutions.

If you do not install integration modules during the product installation process,
you can install them later. If you install them later, you must update the database
and rebuild and deploy the maximo.ear file.

Language deployment after database update deferral

Selecting the option to defer the update of the Maximo database when installing
the product, affects how you deploy languages.

During installation, you have the option to defer the database update task. This
option prevents writing data to the database during the installation. The
installation program is limited to copying files to the administrative system and
registering product process solution packages. You add languages by completing
the installation, manually updating the database, and then updating languages
manually.
“Manually deploying languages after database update deferral” on page 51
Languages must be deployed manually if you defer database updates by the
installation program.

Manually deploying languages after database update deferral

Languages must be deployed manually if you defer database updates by the
installation program.

Before you begin

You must have run updatedb command before manually configuring languages for
PSI packages.

140 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

About this task

To manually configure languages for PSI packages, complete the following steps:

Procedure
1. Update language support for the core components.
Files for the language selections you made during the installation are extracted
to the C:\IBM\SMP\Maximo\Tools\Maximo\locale\xliff\ directory on the system.
a. To update a language as the base language to use for the product, run the
following command:
install_home\maximo\tools\maximo\TDToolkit.bat
-IMPORT
-SLEN
-TLlocale
-maxmessfix
b. To add one or more languages as additional languages for use with the
product, run the following command for each language you want to add:
install_home\maximo\tools\maximo\TDToolkit.bat
-ADDLANGlocale
-maxmessfix
2. Update languages for additional packages.
In order to determine which packages you need to update, change directory to
install_home\maximo\tools\maximo\en\xliff. Each folder located in the xliff
directory, with the exception of MAXUPG folder, is used as input for the
-pmpupdate operation of TDToolkit. Unlike the process for updating languages
for SmartCloud Control Desk, you run the TDToolkit command once for each
package. TDToolkit determines which languages are currently deployed and
updates all languages.
a. Change directory to install_home\maximo\tools\maximo\en\xliff. and
identify a package folder to update, for example calibration.
b. Update languages for the chosen package.
C:\IBM\SMP\maximo\tools\maximo\TDToolkit.bat
-pmpupdatepackagedirectory

In this example, pmpupdatepackagedirectory could be pmpupdatecalibration

or pmpupdateconfig_pmp for example.
c. Repeat for each additional package that require language updates.

Chapter 4. Deploying manually reusing existing middleware 141

142 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Chapter 5. Silent installation
SmartCloud Control Desk provides the option of installing silently.

The SmartCloud Control Desk silent installation option allows you to interface
with the SmartCloud Control Desk installation program using a command prompt
(not the SmartCloud Control Desk launchpad), and a response file.

Installing SmartCloud Control Desk silently

SmartCloud Control Desk can be installed silently by using an installation response
file.

Before you begin

You must complete a successful SmartCloud Control Desk installation to produce a

response file that can be used for a silent installation. Alternatively, you can use
one of the sample response files that are provided on the product media and
modify it according to your needs.

You must verify that all response file paths are formatted correctly. For example, a
UNIX style path statement in the response file might look like the following
statement: USER_INSTALL_DIR=K:/IBM/max_dev. If a path such as
USER_INSTALL_DIR=K:/IBM/max_dev is contained in a response file that is used with
a Windows administrative system, an error occurs. The Windows equivalent in this
example must be formatted for a Windows system: USER_INSTALL_DIR=K:\\IBM\\
max_dev

Note: You can use a silent installation response file to populate SmartCloud
Control Desk installation program fields during an attended installation. Remove
the INSTALLER_UI=silent property from the response file before you use it with the
SmartCloud Control Desk installation program. The installation program uses
default values by reading from the response file. The SmartCloud Control Desk
installation program uses the response file automatically when it is named
installer.properties or install.properties and it is in the same directory. You
do not have to specify the response file name when you start the SmartCloud
Control Desk installation program.

Note: This response file can also be used with the SmartCloud Control Desk
uninstallation program to uninstall SmartCloud Control Desk silently.

About this task

To install SmartCloud Control Desk silently, complete the following steps:

Procedure
1. Make configuration choices by using the SmartCloud Control Desk installation
program, and record those choices in a response file:
a. Start the SmartCloud Control Desk installation program from the product
image. Use the following command for 32–bit systems:
install.exe -r <response file path and name>

© Copyright IBM Corp. 2012 143

 For 64–bit systems, use the following command:
install_win64.exe -r <response file path and name>
The SmartCloud Control Desk installation program executable files are in
the SmartCloud Control Desk directory of the SmartCloud Control Desk
7.5.1 product image.
Response files must have a file extension of .properties, for example,
response.properties.
You must include the full path when you specify the response file.
b. Proceed through the SmartCloud Control Desk installation program, making
configuration choices.
c. Exit the SmartCloud Control Desk installation program after SmartCloud
Control Desk is successfully installed.
There are several sample response files provided on the IBM SmartCloud
Control Desk 7.5.1 product image.
Table 11. SmartCloud Control Desk installation program sample silent response files
File Description
simple_response.properties This file contains a sample response file that
would be used to install a simple
deployment of SmartCloud Control Desk.
custom_response_win.properties This file contains a sample response file that
would be used to install a custom
deployment of SmartCloud Control Desk on
Windows.
custom_response_unix.properties This file contains a sample response file that
would be used to install a custom
deployment of SmartCloud Control Desk on
UNIX.

The files are in the SmartCloud Control Desk\samples directory of the product
image.
If the response file is created by recording an actual installation, you must add
an entry for LICENSE_ACCEPTED=true. If you are using a sample response
file, you must change the entry from false to true. If a silent installation is
started and this entry is not included in the response file then the installation
ends immediately. No messages or log file are created.
If you plan to deploy SmartCloud Control Desk using middleware hosted on
both Windows and UNIX operating systems, your response file contains both
Windows and UNIX values. These values include directory paths and
executable file names. In some cases, the response file is not generated because
the user who starts the installation program does not have write access to the
target directory. In this scenario, the installation program does not report an
error. The response file is not written to the target directory and the log file is
not produced in the ibm\smp\logs directory. To resolve this issue, ensure that
the user who starts the installation program has write access to the target
directory before they run the installation program.
2. Open the response file in a text editor and change the INSTALLER_UI property
to INSTALLER_UI=silent. Passwords are stored in clear text format. You must
edit the CONFIRM_PASSWORD fields contained in the response file to match
its corresponding password value used for each task. For example, ensure that
CONFIRM_PASSWORD matches RXA_PASSWORD in the following example:

144 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 #Middleware Server Information
#-----------------------------
MIDDLEWARE_SERVER=myserver.mydomain.com
RXA_USER_ID=root
RXA_PASSWORD=mypassword
CONFIRM_PASSWORD=mypassword
3. Copy the response file to the target system.
4. Start the SmartCloud Control Desk installation program silently and identify
the response file to be used.
install.exe -f <response file path and name>

You must include the full path when you specify the response file and it must
be on the C:\ drive of your system.

Results

The installation proceeds silently with the values that you provided in the response
file.

Response files that include fields for Oracle configuration must be edited to
remove extraneous backslashes. A response file that includes Oracle as a
deployment option is generated with fields like the following excerpt:
DB_INSTALL_DIR=C\:/oracle/product/10.2.0/db_1
INSTANCE_LOCATION=C\:/oracle/product/10.2.0/db_1/dbs
WAS_HOME_DIR=C\:/Program Files/IBM/WebSphere/AppServerUSER_INSTALL_DIR=C\:/IBM/
USER_SHORTCUTS=C\:/Documents and Settings/All Users/Start Menu/Programs
/process automation engine
MAXIMO_INSTALL_DIR=C\:/IBM/maximo

You must remove the backslash that is directly after the drive letter, so that your
response file looks like following excerpt:
DB_INSTALL_DIR=C:/oracle/product/10.2.0/db_1
INSTANCE_LOCATION=C:/oracle/product/10.2.0/db_1/dbs
WAS_HOME_DIR=C:/Program Files/IBM/WebSphere/AppServerUSER_INSTALL_DIR=C:/IBM/
USER_SHORTCUTS=C:/Documents and Settings/All Users/Start Menu/Programs
/process automation engine
MAXIMO_INSTALL_DIR=C:/IBM/maximo

If you attempt to install SmartCloud Control Desk silently and the installation UI
is shown, check inside the response file to ensure that it contains this line:
INSTALLER_UI=silent

Silent installation properties

Silent installation properties are recorded in an installation response file. Silent
installation response files are generated when the installation program is started
with the parameters described in the silent installation procedure. Alternatively, a
silent installation response file can be created and populated manually.

Chapter 5. Silent installation 145

 Common silent installation properties

The following properties are common to all deployments.

Table 12. Common silent installation response file properties
Category Property Definition
File header INSTALLER_UI=SILENT This property must be set so the
file can be used with the product
installation program.
Package INSTALL_SOME_PACKAGES=0 If only a subset of packages can be
deployment set installed, set this value to 1. This
setting allows the product
installation program to continue.
License LICENSE_ACCEPTED=TRUE Set this value to true to accept the
Agreement license agreement or false to reject
it.
Installation folder USER_INSTALL_DIR=installation path Set an installation path. For
example, for UNIX, /opt/IBM/SMP
or for Windows, C:\\IBM\\SMP.
Installation INSTALLATION_DESCRIPTION Description of the installation
description location.
Deployment type SIMPLE=0 Installation is set to a type of
SIMPLE. Set to 0 to disable. Set to
1 to enable. If SIMPLE is enabled,
ADVANCED must be disabled.
ADVANCED=1 Installation is set to a type of
ADVANCED, which is a Custom
installation. Set to 0 to disable. Set
to 1 to enable. If ADVANCED is
enabled, SIMPLE must be disabled.
Middleware MIDDLEWARE_SERVER=host name Set the host name of the system
Server that is hosting all middleware.
Information (only
used for Simple
installations)
RXA_USER_ID=user name Set the user ID for accessing the
system that is hosting all
middleware.
RXA_PASSWORD=password Set a password for the user ID for
accessing the system that is hosting
all middleware.
Import MWI_IMPORT_DATA=0 Set this parameter to import
Middleware configuration data from the
installation middleware installation program.
program
information Set to 0 to disable. Set to 1 to
enable.
MWI_HOSTNAME=host name Set the host name of the system
that is hosting the middleware
installation program workspace.
MWI_USER_ID=user name Set a user ID used to access the
system that is hosting the
middleware installation program
workspace. For example, root.

146 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 12. Common silent installation response file properties (continued)
Category Property Definition
MWI_PASSWORD=passsword Set a password for the user ID
used to access the system that is
hosting the middleware installation
program workspace.
MWI_LOCATION=path Set a path for the location of the
middleware installation program
workspace. For example, for UNIX,
/root/ibm/tivoli/mwi/workspace
or for Windows,
C:\\ibm\\tivoli\\mwi\\workspace.
SMTP SMTP_SERVER=host name Set the name of the system that is
Configuration hosting the SMTP server
responsible for distributing
administration messages to the
SmartCloud Control Desk
administrator.
ADMIN_EMAIL=email address Set the email address for the
SmartCloud Control Desk
administrator.
Run RUN_CONFIG_NO=0 Set the behavior of the run
Configuration configuration step.
Step
Set to 0 to disable (run the
configuration step at installation
time). Set to 1 to enable (defer the
configuration step).
DEPLOY_EAR_NO=0 Set the behavior of the EAR
deployment step.

Set to 0 to disable (deploy the EAR

at installation time). Set to 1 to
enable (defer deployment of the
EAR).
DEFER_DB_UPDATE=0 Set the behavior of the database
update step.

Set to 0 to disable (run updateDB

at installation time). Set to 1 to
enable (defer updateDB).
Shortcut Folder USER_SHORTCUTS=path Set a path for shortcuts. For
example, for Windows,
C:\\Documents and
Settings\\Administrator\\
Desktop\\process automation
engine.

Chapter 5. Silent installation 147

Table 12. Common silent installation response file properties (continued)
Category Property Definition
Installer version LAUNCH_NEW_INSTALLER=TRUE If a more recent version of the
installation program was found in
the target installation directory
specified. This circumstance
indicates that you are using an
older version of the installation
program. In order to use the
newer version of the installation
program, set this value to TRUE. If
you set this value to FALSE, the
older version of the installation
program is used to perform the
installation.

Users silent installation properties

The following properties are for users created by or identified to the installation
program.
Table 13. Users silent installation properties
Category Property Definition
User Information MAXADMIN_USER_NAME=user name Set a user name for the Maximo
administrator. For example,
maxadmin.
MAXADMIN_PASSWORD=password Set a password for the Maximo
administrator. For example,
maxadmin.
MAXREG_USER_NAME=user name Set a user name for the self
registration user. This user is
responsible for the process by
which users can create their own
accounts. For example, maxreg.
MAXREG_PASSWORD=password Set a password for the self
registration user. For example,
maxreg.
MXINTADM_USER_NAME=user name Set a user name for the internal
user. For example, mxintadm.
MXINTADM_PASSWORD=password Set a password for the internal
user. For example, mxintadm.

Common database silent installation properties

The following properties contain common information about the database used for
the deployment.
Table 14. Common database silent installation response file properties
Category Property Definition
Database Type DB_TYPE_DB2=1 Set the database type to DB2. Set
to 0 to disable. Set to 1 to
enable. Only one Database Type
can be enabled.

148 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 14. Common database silent installation response file properties (continued)
Category Property Definition
DB_TYPE_ORACLE=0 Set the database type to Oracle. Set
to 0 to disable. Set to 1 to enable.
Only one Database Type can be
enabled.
DB_TYPE_SQLSERVER=0 Set the database type to Microsoft
SQL Server. Set to 0 to disable. Set
to 1 to enable. Only one Database
Type can be enabled.
Database DB_HOST_NAME=host name Set the host name of the database
server.
DB_PORT=port Set the database port. For
example, 50005.
DB_NAME=name Set a name for the database. For
example, maxdb75.

DB2
DB_NAME=name Set a name for the database. For
example, maxdb75.

Microsoft SQL Server

DB_INSTANCE=instance Set a name for the database
instance to use with the product.
For example, ctginst1.

DB2
DB_INSTANCE=instance Set a name for the database
instance to use with the product.
For example, ctginst1.

Oracle

DB_USER=user name Set the name of the user ID to

access the database. For example,
maximo.
DB_PASSWORD=password Set a password for the database
user ID. For example, maximo.
Database AUTOMATE_DB=1 Configure the automatic
Configuration configuration of the database by
Automation the installation program. Set to 0 to
disable. Set to 1 to enable. Either
AUTOMATE_DB or
DO_NOT_AUTOMATE_DB can be
enabled at one time.
DO_NOT_AUTOMATE_DB=0 Configure the automatic
configuration of the database by
the installation program. Set to 0 to
disable. Set to 1 to enable. Either
AUTOMATE_DB or
DO_NOT_AUTOMATE_DB can be
enabled at one time.

Chapter 5. Silent installation 149

Table 14. Common database silent installation response file properties (continued)
Category Property Definition
Remote Access DB_RXA_USER=user name Set the name of the user ID to
Authorization access the remote database server
system. For example, root.

Only required if AUTOMATE_DB

was enabled.

DB2
Remote Access DB_RXA_USER=user name Set the name of the user ID to
Authorization access the remote database server
system. For example, root.

Only required if AUTOMATE_DB

was enabled.

Oracle
DB_RXA_PASSWORD=password Set a password for the remote
access user ID.

Only required if AUTOMATE_DB

was enabled.

DB2
DB_RXA_PASSWORD=password Set a password for the remote
access user ID.

Only required if AUTOMATE_DB

was enabled.

Oracle
Database DB_INSTALL_DIR=path Enter the database server
Administration installation path. For example,
UNIX /opt/IBM/db2/V9.7
/opt/oracle/product/
11.2.0/db_1
Windows
C:\Program
Files\oracle\product\
11.2.0\db_1

Only required if AUTOMATE_DB

was enabled.

DB2

150 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 14. Common database silent installation response file properties (continued)
Category Property Definition
Database DB_INSTALL_DIR=path Enter the database server
Administration installation path. For example,
UNIX /opt/IBM/db2/V9.7
/opt/oracle/product/
11.2.0/db_1
Windows
C:\Program
Files\oracle\product\
11.2.0\db_1

Only required if AUTOMATE_DB

was enabled.

Oracle
DB_ADMIN_USER=user name Set the name of the database
administrator. For example:
db2admin.

DB2
DB_ADMIN_USER=user name Set the name of the database
administrator. For example, Sys.

Oracle
DB_ADMIN_PASSWORD=password Set a password for the remote
access database administrator.

DB2
DB_ADMIN_PASSWORD=password Set a password for the remote
access database administrator.

Oracle
Database Table DB_TABLE_SPACE_NAME=table space name Set the name of the database table
Space space. For example, MAXDATA.

DB2
Database Table DB_TABLE_SPACE_NAME=table space name Set the name of the database table
Space space. For example, MAXDATA.

Oracle
DB_TABLE_SPACE_SIZE=table space size in Mb Set the size of the database table
space, in Mb. For example, 5000. y.

Only required if AUTOMATE_DB

was enabled.
DB_TEMP_TABLE_SPACE_NAME=temporary table space Set the name of the database
name temporary table space. For
example, MAXTEMP.

DB2
DB_TEMP_TABLE_SPACE_NAME=temporary table space Set the name of the database
name temporary table space. For
example, MAXTEMP.

Oracle

Chapter 5. Silent installation 151

Table 14. Common database silent installation response file properties (continued)
Category Property Definition
DB_TEMP_TABLE_SPACE_SIZE=temporary table space size in Set the size of the temporary
Mb database table space, in Mb. For
example, 1000.

Only required if AUTOMATE_DB

was enabled.

DB2
DB_TEMP_TABLE_SPACE_SIZE=temporary table space size in Set the size of the temporary
Mb database table space, in Mb. For
example, 1000.

Only required if AUTOMATE_DB

was enabled.

Oracle
DB_INDEX_TABLE_SPACE_NAME=index table space name Set the name of the database index
table space. For example, MAXDATA.

DB2
DB_INDEX_TABLE_SPACE_NAME=index table space name Set the name of the database index
table space. For example, MAXDATA.

Oracle
DB_INDEX_TABLE_SPACE_SIZE=index table space size in Mb Set the size of the index database
table space, in Mb. For example,
5000.

Only required if AUTOMATE_DB

was enabled.

DB2
DB_INDEX_TABLE_SPACE_SIZE=index table space size in Mb Set the size of the index database
table space, in Mb. For example,
5000.

Only required if AUTOMATE_DB

was enabled.

Oracle only.

DB2 silent installation properties

The following properties contain information about an DB2 database used for the
deployment. These properties are only necessary if you are using a DB2 database
for deployment.
Table 15. DB2 silent installation response file properties
Category Property Definition
DB2 DB_SCHEMA=schema Designate the database
schema. For example, maximo.

152 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 15. DB2 silent installation response file properties (continued)
Category Property Definition
DB_WIN_SERVICE_USER=user name Set the name of the database
service owner in Windows. For
example, ctginst1.

Only required if AUTOMATE_DB

was enabled.
DB_WIN_SERVICE_PASSWORD=password Set a password for the database
service owner in Windows.

Only required if AUTOMATE_DB

was enabled.
DB2_VARCHAR=0 Configure varchar or vargraphic in
the database by the installation
program. Set to 0 to use vargraphic
formatting. Set to 1 to use varchar.

varchar formatting supports

English only.

Oracle silent installation properties

The following properties contain information about an Oracle database used for
the deployment. These properties are only necessary if you are using an Oracle
database for deployment.
Table 16. Oracle silent installation response file properties
Category Property Definition
Oracle ORACLE_OWNER_ID=user name Set the Oracle software owner user
ID. For example, oracle.

Only required if AUTOMATE_DB

was enabled.
ORACLE_OWNER_PASSWORD=password Set the Oracle software owner
password.

Only required if AUTOMATE_DB

was enabled.
INSTANCE_LOCATION=instance location Set the Oracle database instance
location. For example,
/opt/oracle/product/11.2.0/db_1.

Only required if AUTOMATE_DB

was enabled.

Microsoft SQL Server silent installation properties

The following properties contain information about a Microsoft SQL Server

database used for the deployment. These properties are only necessary if you are
using a Microsoft SQL Server database for deployment.

Chapter 5. Silent installation 153

Table 17. Microsoft SQL Server silent installation response file properties
Category Property Definition
Microsoft SQL SQL_DATA_FILE_NAME=data file name Set the file name for the Microsoft
Server SQL Server data source. For
example, maxdb75_dat.

Only required if AUTOMATE_DB

was enabled.
DB_TABLE_SPACE_SIZE=data source size in Mb Set the size of the Microsoft SQL
Server data source, in Mb. For
example, 1000.

Only required if AUTOMATE_DB

was enabled.
SQL_ADMIN=user name Set the name of the Microsoft SQL
Server administrator. For example,
sa.

Only required if AUTOMATE_DB

was enabled.
SQL_ADMIN_PW=password Set a password for the Microsoft
SQL Server administrator.

Only required if AUTOMATE_DB

was enabled.
SQL_LOG_FILE_NAME Microsoft SQL Server log
name. For example, maxdb75_log

Only required if AUTOMATE_DB

was enabled.

Common application server silent installation properties

The following properties contain common information about the application server
used for the deployment.
Table 18. Common application server silent installation response file properties
Category Property Definition
Application APPLICATION_SERVER_TYPE_WAS=1 Configure the application server
Server Type used for the deployment. Set to 0
to disable. Set to 1 to enable.

Only one Application Server Type

can be enabled.

IBM WebSphere Application Server Network Deployment silent

installation properties

The following properties contain information about a IBM WebSphere Application

Server Network Deployment application server used for the deployment. These
properties are only necessary if you are using an IBM WebSphere Application
Server Network Deployment application server for deployment.

154 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 19. IBM WebSphere Application Server Network Deployment silent installation response file properties
Category Property Definition
IBM WAS_HOSTNAME=host name Set the host name of the IBM
WebSphere WebSphere Application Server
Application Network Deployment server.
Server Network
Deployment
Connectivity
WAS_SOAP_PORT=port Set the SOAP port. For example,
8879.
Automate AUTOMATE_WAS_CLIENT=1 Automatic configuration of the
WebSphere WebSphere Application Server
Application Network Deployment thin client by
Server Network the SmartCloud Control Desk
Deployment installation program. Set to 0 to
Configuration disable. Set to 1 to enable.
WebSphere WAS_CLIENT_RXA_USER=user name Set the name of the user ID to
Application access the remote WebSphere
Server Network Application Server Network
Deployment Deployment server system. For
Remote Access example, root.
Authorization
WAS_CLIENT_RXA_PASSWORD=passsword Set a password for the remote
access user ID.
WebSphere WAS_HOME_DIR=path Enter the installation path for
Application WebSphere Application Server
Server Network Network Deployment. For
Deployment example, for UNIX,
Deployment /opt/IBM/WebSphere/AppServer or
Manager for Windows, C:\\Program
Configuration Files\\IBM\\WebSphere\\
AppServer.
WAS_USER=user name Set the name of the user ID used to
access the WebSphere Application
Server Network Deployment
server. For example, wasadmin.
WAS_PASSWORD=passsword Set a password for the WebSphere
Application Server Network
Deployment user ID.
WAS_PROFILE=profile name Set a name for the domain
manager profile. For example,
ctgDmgr01.
WebSphere WAS_VIRTUAL_HOST_PORT=port Set a port for the virtual host. For
Application example, 80.
Server Network
Deployment
Application
Server
Configuration
WAS_WEB_SERVER_NAME=Web server name Set a name for the Web server. For
example, webserver1.
WAS_NODE_NAME=node name Set a name for the node. For
example, ctgNode01.

Chapter 5. Silent installation 155

Table 19. IBM WebSphere Application Server Network Deployment silent installation response file
properties (continued)
Category Property Definition
WAS_APPLICATION_SERVER_NAME=host name Set a name for the application
server. For example, MXServer.
Integration WAS_SIB_DS_NAME=data source name Set a name for the data source that
Adapter JMS is used to persist JMS messages.
Configuration For example, intjmsds.
WAS_JMS_PERSIST_DATASTORE=1 Persist JMS messages in a data
source. Set to 0 to disable. Set to 1
to enable.

Only one parameter between

WAS_JMS_PERSIST_DATASTORE
and
WAS_JMS_DO_NOT_PERSIST_
DATASTORE can be enabled.
WAS_JMS_DO_NOT_PERSIST_DATASTORE=0 Do not persist JMS messages. Set to
0 to disable. Set to 1 to enable.

Only one parameter between

WAS_JMS_PERSIST_DATASTORE
and
WAS_JMS_DO_NOT_PERSIST_
DATASTORE can be enabled.
DB2 Database WAS_SIB_DB_SERVER_NAME=host name Set the name of the system that is
Server hosting the database used to persist
Configuration JMS messages.

Only required if
WAS_JMS_PERSIST_DATASTORE
was enabled.
WAS_SIB_DB_SERVER_PORT=port Set the access port of the database
used to persist JMS messages. For
example, 50005.

Only required if
WAS_JMS_PERSIST_DATASTORE
was enabled.
WAS_SIB_DB_NAME=database name Set a name for the database used to
persist JMS messages. For example,
maxsibdb.

Only required if
WAS_JMS_PERSIST_DATASTORE
was enabled.
WAS_SIB_DB_USER_NAME=user name Set the name of the user ID used to
access the database used to persist
JMS messages. For example,
maximo.

Only required if
WAS_JMS_PERSIST_DATASTORE
was enabled.

156 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 19. IBM WebSphere Application Server Network Deployment silent installation response file
properties (continued)
Category Property Definition
WAS_SIB_DB_USER_PASS=passsword Set a password for the data source
database user ID.

Only required if
WAS_JMS_PERSIST_DATASTORE
was enabled.
DB2 Database WAS_SIB_DB_REMOTE_ACCESS_USER=user name Set a name for the user ID used to
Server Remote access the remote database server
Access used to persist JMS messages. For
Authorization example, Administrator.

Only required if
WAS_JMS_PERSIST_DATASTORE
was enabled.
WAS_SIB_DB_REMOTE_ACCESS_PASSWORD= Set a password for the user ID
used to access the remote database
passsword server used to persist JMS
messages.

Only required if
WAS_JMS_PERSIST_DATASTORE
was enabled.
DB2 Database WAS_DB_HOME_DIR=path Enter the installation path for
Instance DB2. For example, for UNIX,
Configuration /opt/IBM/db2/V9.7 or for
Windows, C:\\Program
Files\\IBM\\SQLLIB.

Only required if
WAS_JMS_PERSIST_DATASTORE
was enabled.
WAS_SIB_DB_INSTANCE=database instance name Set a name for the database
instance used to persist JMS
messages. For example, ctginst1.

Only required if
WAS_JMS_PERSIST_DATASTORE
was enabled.
WAS_SIB_DB_INSTANCE_ADMIN_USER=user name Set a name for the administrator of
the database instance used to
persist JMS messages. For example,
db2admin.

Only required if
WAS_JMS_PERSIST_DATASTORE
was enabled.
WAS_SIB_DB_INSTANCE_ADMIN_PASSWORD= Set a password for the
administrator of the database
passsword instance used to persist JMS
messages.

Only required if
WAS_JMS_PERSIST_DATASTORE
was enabled.

Chapter 5. Silent installation 157

 Security silent installation properties

The following properties are used to configure security.

Table 20. Security silent installation response file properties
Category Property Definition
Security LDAP_OPTION1=1 Configure security so that an LDAP
resource is used for user
authorization and authentication.

Set to 0 to disable. Set to 1 to

enable.

Only one LDAP_OPTION

parameter can be enabled at one
time.

If LDAP_OPTION1 is enabled, then

the VMM_USER_RDN,
VMM_GROUP_RDN and
CREATE_DEFAULT_USERS
properties are also required to have
valid values.
LDAP_OPTION2=0 Configure security so that an LDAP
resource is used for user
authentication only. Group
management is managed from the
SmartCloud Control Desk
application. Authorization data is
stored in the database.

Set to 0 to disable. Set to 1 to

enable.

Only one LDAP_OPTION

parameter can be enabled at one
time.
LDAP_OPTION3=0 Configure security so that user
authentication and authorization
are both managed from the
SmartCloud Control Desk
application. Authentication and
authorization data is stored in the
database.

Set to 0 to disable. Set to 1 to

enable.

Only one LDAP_OPTION

parameter can be enabled at one
time.
VMM_USER_RDN=user RDN Set a relative distinguished name
for users for VMM. For example,
ou=users,ou=SWG,o=IBM,c=US.
VMM_GROUP_RDN=group RDN Set a relative distinguished name
for groups for VMM. For example,
ou=groups,ou=SWG,o=IBM,c=US.

158 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 20. Security silent installation response file properties (continued)
Category Property Definition
CREATE_DEFAULT_USERS=1 Have the SmartCloud Control Desk
installation program create default
users automatically.

Set to 0 to disable. Set to 1 to

enable.

Language silent installation properties

The following properties are used to configure languages.

Table 21. Language silent installation response file properties
Category Property Definition
Base BASE_ARABIC=0 Set this language
Language as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_BRAZILIAN_PORTUGUESE=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_CROATIAN=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_CZECH=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.

Chapter 5. Silent installation 159

Table 21. Language silent installation response file properties (continued)
Category Property Definition
BASE_DANISH=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_DUTCH=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_ENGLISH=1 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_FINNISH=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_FRENCH=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.

160 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 21. Language silent installation response file properties (continued)
Category Property Definition
BASE_GERMAN=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_HEBREW=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_HUNGARIAN=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_ITALIAN=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_JAPANESE=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.

Chapter 5. Silent installation 161

Table 21. Language silent installation response file properties (continued)
Category Property Definition
BASE_KOREAN=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_NORWEGIAN=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_POLISH=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_RUSSIAN=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_SIMPLIFIED_CHINESE=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.

162 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 21. Language silent installation response file properties (continued)
Category Property Definition
BASE_SLOVAK=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_SLOVENIAN=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_SPANISH=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_SWEDISH=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
BASE_TRADITIONAL_CHINESE=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.

Chapter 5. Silent installation 163

Table 21. Language silent installation response file properties (continued)
Category Property Definition
BASE_TURKISH=0 Set this language
as the base
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
Additional ADD_ARABIC=0 Set this language
Languages as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_BRAZILIAN_PORTUGUESE=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_CROATIAN=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_CZECH=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.

164 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 21. Language silent installation response file properties (continued)
Category Property Definition
ADD_DANISH=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_DUTCH=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_ENGLISH=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_FINNISH=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_FRENCH=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.

Chapter 5. Silent installation 165

Table 21. Language silent installation response file properties (continued)
Category Property Definition
ADD_GERMAN=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_HEBREW=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_HUNGARIAN=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_ITALIAN=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_JAPANESE=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.

166 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 21. Language silent installation response file properties (continued)
Category Property Definition
ADD_KOREAN=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_NORWEGIAN=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_POLISH=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_RUSSIAN=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_SIMPLIFIED_CHINESE=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.

Chapter 5. Silent installation 167

Table 21. Language silent installation response file properties (continued)
Category Property Definition
ADD_SLOVAK=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_SLOVENIAN=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_SPANISH=1 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_SPANISH=1 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.
ADD_TRADITIONAL_CHINESE=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.

168 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 21. Language silent installation response file properties (continued)
Category Property Definition
ADD_TURKISH=0 Set this language
as an additional
language used by
the SmartCloud
Control Desk
application.

Set to 0 to
disable. Set to 1
to enable.

Chapter 5. Silent installation 169

170 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Chapter 6. Programmatically verifying that the installation was
successful
After you have exited the SmartCloud Control Desk installation program without
encountering any errors, you can verify that the installation completed successfully.
The installation is programmatically verified through the use of post installation
validation utilities.

Before you begin

The JAVA_HOME environment variable must be set on the system before you can
use the verification utilities.

About this task

During installation, the SmartCloud Control Desk installation program performs a

simple health check. This health check consists of logging in to the application to
verify availability. This health check might not be sufficient to verify a successful
installation in all deployment scenarios. For example, if, during installation, you
select the option to deploy the application EAR file at a later date, this health
check cannot verify the installation. This simple health check is also insufficient for
verifying an upgrade.

Post installation validation utilities are available after the product has been
deployed.

The middlewareValidate utility is used to verify the middleware.

The installValidation utility is used to validate the product installation. These

command-line utilities are used to verify the installation and configuration of the
product in a more complete manner. These utilities can also be used to verify an
existing deployment after changes in the environment, such as changes to host
names, user IDs, and passwords.

Results of the installValidation utility are logged in

installValidationTrace00.log. This log is found in the \ibm\smp\logs directory
on the administrative workstation.

Procedure
1. Log in to the server using the user ID that was used to run the installation
program. If you intend to use the installValidation utility, log in to the
administrative workstation. If you intend to use the middlewareValidate
utility, log in to the server hosting the middleware.
2. Ensure the JAVA_HOME environment variable is set properly to the location of
a JRE 1.6 installation.
3. To verify product installation, from the administrative workstation, change
directory to \ibm\smp\scripts and run the installValidation.bat command.
For either command, use the parameters described below: To verify
middleware installation, from the middleware image, update the
middleware.properties file with the installation parameter values for
middleware components to be verified, change directory to \HealthCheck and
run the middlewareValidate.[sh|bat] command.

© Copyright IBM Corp. 2012 171

Table 22. Verification utilities parameters
Program Syntax parameters Input
installValidation.bat -action Use -action validate to start the
validation of the product installation.

The -action parameter is the only

mandatory parameter when using the
installValidation utility.
-trace Verification progress information is
written to the screen during the
verification process. You can modify
the output using the -tracing
parameter.
v minimal
Progress information is limited to
error information.
v normal
Information includes individual
test progress, individual test
results, and overall progress of the
entire verification process.
This is the default mode of tracing.
v verbose
In addition to providing normal
progress information, verbose
tracing includes the test class
name, test method name, and
corrective action information.
-confirm You are prompted before each test is
started. You must confirm each test
to be performed. There is no input
for this parameter.
-component You can provide a comma-delimited
list of directories containing the test
objects to limit testing to a specific
set of tests.

These test objects must be located in

the \ibm\smp\HealthValidation\
directory. For the product installation
program, only the CTGIN folder is
provided.
-dbuser Provide the user ID used to access
the database.
-dbpwd Provide the password of the user ID
used to access the database.
-wasuser Provide the WebSphere Application
Server Network Deployment user.
-waspwd Provide the password for the
WebSphere Application Server
Network Deployment user.
-maxuser Provide the SmartCloud Control
Desk administrator user ID. For
example, maxadmin.

172 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 22. Verification utilities parameters (continued)
Program Syntax parameters Input
-maxpwd Provide the password for the
SmartCloud Control Desk
administrator user ID.
middlewareValidate.[sh|bat] -middlewareproperties Use
-middlewareproperties file

where file is the location of the

middleware.properties file. By
default, this file is found on the
middleware installation media in the
\HealthCheck directory.

The middleware.properties contains

the middleware installation
properties, such as installation
locations and ports. User names and
passwords are not stored in this
plain-text file. Some of the properties
common to all platforms have been
defined default values, but
platform-specific properties like
installation locations need to be
updated in this file before starting
the middlewareValidate utility.

The -middlewareproperties
parameter is the only mandatory
parameter when using the
middlewareValidate utility.
-trace Verification progress information is
written to the screen during the
verification process. You can modify
the output using the -trace
parameter.
v minimal
Progress information is limited to
error information.
v normal
Information includes individual
test progress, individual test
results, and overall progress of the
entire verification process.
v verbose
In addition to providing normal
progress information, verbose
tracing includes the test class
name, test method name, and
corrective action information.

If this option is not provided, by

default, no output displayed.

Chapter 6. Programmatically verifying that the installation was successful 173

Table 22. Verification utilities parameters (continued)
Program Syntax parameters Input
-component Specify the middleware components:
v DBSERVER - verify installation of
the IBM DB2 server.
v DIRSERVER - verify installation of
the optional IBM Tivoli Directory
Server.
v LDAPSERVER - verify
configuration of the optional IBM
Tivoli Directory Server.
v J2EESERVER - verify installation of
the WebSphere Application Server
server

One or more of these keywords can

be specified as comma separated list.
If this argument is skipped, the tool
assumes all the components are
selected to verify.
-bindUser Provide the bind user.

Required to verify LDAPSERVER.

The bind user credentials, bind
Distinguished Name and bind
password are required to be specified
with the -bindUser and -bindPass
options.
-bindPass Provide the password for the bind
user.

Required to verify LDAPSERVER.

The bind user credentials, bind
Distinguished Name and bind
password are required to be specified
with the -bindUser and -bindPass
options.
-wasuser Provide the WebSphere Application
Server user.

WebSphere Application Server

administrative user credentials are
required for the LDAPSERVER and
J2EESERVER component checks.
-waspwd Provide the password for the
WebSphere Application Server user.

WebSphere Application Server

administrative user credentials are
required for the LDAPSERVER and
J2EESERVER component checks.

For example,
installValidation.bat -action validate

174 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Results

The installValidation.bat validation utility results are logged in

ctginstallvalidationtrace00.log. This log is found in the \ibm\smp\logs
directory on the administrative workstation.

The middlewareValidate.[sh|bat] validation utility results are logged in

CTGInstallValidationTrace.log. This log is found in the HealthCheck directory.

Chapter 6. Programmatically verifying that the installation was successful 175

176 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Chapter 7. Verifying the installation manually
After you exit the SmartCloud Control Desk installation program without errors,
you can further verify that the installation completed successfully. The installation
is manually verified by locating key artifacts and performing a few simple tasks.

Before you begin

The product installation program performs installation verification, or a health

check, by logging on to the product before exiting the installation. The product
installation program returns a success message if all installation steps, including
the product log in task, are successful. If the health check task is unsuccessful, a
HealthCheckFailed error is thrown for the getUrlContentString function. This
error is in the install_home\logs\CTGInstallTraceXX.log file, where XX is a
two-digit number such as 00.

About this task

To further verify that the SmartCloud Control Desk installation was completed
successfully, perform the following verification procedures:

Procedure
1. Examine the CTGInstallTrace00.log file for success messages.
The following success messages are found in the CTGInstallTrace00.log file
and can be used to verify which phases of the installation were successful:
v CTGIN2114I: The database was created successfully
v CTGIN2135I: Tablespace maxdata created successfully
v CTGIN2135I: Tablespace maxtemp created successfully
v CTGIN2079I: process automation engine database configuration completed
successfully (This message indicates that maxinst finished successfully.)
v CTGIN2222I: WebSphere Application Server creation successful
v CTGIN2188I: Creation and configuration of service integration bus
successfully completed
v CTGIN2184I: Creation and configuration of JMS resources successfully
completed
v CTGIN2310I: Application server security was successfully enabled for process
automation engine
v CTGIN2253I: buildmaximoear.cmd completed successfully
v CTGIN2224I: Deployment of application MAXIMO was successful
v CTGIN2253I: buildhelpear.cmd completed successfully
v CTGIN2224I: Deployment of application MAXIMOIEHS was successful
v CTGIN2208I: runConfigurationStep completed successfully
v CTGIN2370I: The installation finished successfully
If you automatically configured WebSphere Application Server Network
Deployment certain messages indicate success. The following messages, found
in CTGInstallTrace00.log, indicate that the configuration was successful:

© Copyright IBM Corp. 2012 177

 <symptom>CTGIN2228I.*client</symptom>
<symptom>CTGIN2230I.*node</symptom>
<symptom>CTGIN2232I.*NodeAgent</symptom>
<symptom>CTGIN2240I.*server</symptom>
<symptom>CTGIN2238I.*security</symptom>
Search the CTGInstallTrace00.log file for the following message, which
indicates that the maxinst task completed successfully:
CTGIN2079I, maxinst.*completed
2. Compare the packages chosen for installation with the packages that were
installed. The Package Summary panel of the SmartCloud Control Desk
installation program provides a summary of all the packages to be installed.
You can compare the contents of that panel with a listing of what was installed
on the system. Use the solutioninstaller command to list installed packages:
install_home\bin\setupPSIenv.bat
install_home\bin\solutionInstaller.bat -action showInstalled -type all

The resulting list matches the packages listed in the Package Summary panel.
3. Log in to the product and verify that applications are present. Being able to log
in to the product manually is a good indicator that the installation was
successful. Once you have logged in, verify that you can access expected
applications. If you experience access problems with the product, clear the
cache of your browser and try again.

178 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Chapter 8. Configuring the HTTPOnly attribute
If applications do not start from the user interface in IBM WebSphere Application
Server Network Deployment 8 environments, the problem can often be attributed
to a security setting within IBM WebSphere Application Server Network
Deployment. In particular, if the HTTPOnly attribute is set for session cookies, the
applications are not accessible.

Procedure
1. Log on to the administrative console for IBM WebSphere Application Server
Network Deployment.
2. From the navigation pane, browse to Servers > Server Types > WebSphere
spplication servers.
3. Click the application server created for the product you want to update, for
example, MXServer.
4. From the Configuration panel, under Container Settings, click Session
management.
5. Under General properties, click Enable cookies. Do not clear this option. Click
the label only.
6. Clear the Set session cookies to HTTPOnly check box to help prevent
cross-site scripting attacks.
7. Click OK, save the changes, and then click OK.
8. Click Save and then click OK.
9. Navigate back to the Application servers table, and select the application
server required.
10. Click Restart to restart the application server in order to apply the changes
made.

© Copyright IBM Corp. 2012 179

180 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Chapter 9. Installing Integration Composer
After you have successfully installed the IBM
SmartCloud Control Desk components, you can
optionally install (or upgrade) Integration Composer, an
integration tool that imports information technology (IT)
data into the Maximo database.

IBM SmartCloud Control Desk installations use the

Launchpad as an interface for installing Integration
Composer. However, if necessary, you can install
Integration Composer on a UNIX operating system in
console mode, from the command line.

When you install Integration Composer and IBM

SmartCloud Control Desk from the Launchpad, the
installer automatically updates the Integration Composer
database tables in the Integration Composer repository
for you.

Integration Composer overview

Integration Composer is the IBM application for transforming and importing
inventory data about deployed hardware and software. This inventory data is
imported from a discovery or system management tool database into the Maximo
database tables for deployed assets or configuration items.

With Integration Composer, an enterprise can aggregate data collected by external

discovery tools and integrate it into the Maximo database, creating a central
repository for enterprise IT asset management, reporting, and decision support.
The Maximo database is the repository used by:
v IBM Tivoli Asset Management for IT
v IBM Tivoli Service Request Manager®
v IBM Tivoli Change and Configuration Management Database

To collect the data about deployed assets or configuration items, a discovery tool
scans computers, network devices, and network printers deployed in an enterprise
and records information about the hardware and software it finds there.
Integration Composer uses an integration adapter to transform the data collected
by the discovery tool and move it from the discovery tool database into the
Maximo database. (For more about creating your own integration adapter, see the
book Integration Composer Administrator Guide.)

You can view imported data from various applications on your system. The data is
also used to generate reports.

Note: Integration Composer is used to import hardware and software inventory

data from a discovery tool database into the Deployed Asset, Actual CI, or (for the
purposes of asset initialization) Asset tables in the Maximo database. The import or
export of data into or out of other tables within the Maximo database is
accomplished using a different tool, the integration framework. Refer to the related
book, Integration Guide, for more on this subject.

© Copyright IBM Corp. 2012 181

Hardware and software requirements
This section describes the products and versions supported by Integration
Composer, plus the hardware and software requirements for the corequisite
applications.

The hardware and software requirements for Integration Composer and its
corequisites are as follows:

Integration Integration Composer 7.5.1 has the following minimum requirements:

Composer v 3 GB memory
v 70 MB disk space
v IBM Java Software Development Kit 6.0 for the appropriate operating system

A compatible asset One of the following compatible products is required and must be installed before
management you can use Integration Composer. For details about version compatibility, see the
product documentation for the specific product:
v IBM Tivoli Unified Service Center
v IBM Tivoli Asset Management for IT
v IBM Tivoli Service Request Manager
v IBM Tivoli Change and Configuration Management Database

182 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

IBM Tivoli A dedicated server is required for running the Integration Composer application
Integration and Java components. Integration Composer can run on any of the following
Composer server operating systems:
v HP-UX 11i 3 (on Intel Itanium hardware)
v IBM AIX 5L™ 6.1 (32-bit)
v IBM AIX 5L 6.1 (64-bit)
v IBM AIX 5L 7.1 on Power Systems™ hardware (32-bit)
v IBM AIX 5L 7.1 on Power Systems hardware (64-bit)
v Microsoft Windows Server 2003 Enterprise Edition (on x86-32 hardware)
v Microsoft Windows Server 2003 Enterprise Edition (on x86-64 hardware)
v Microsoft Windows Server 2008 Enterprise Edition, Release 2 (on x86-64
hardware)
v Microsoft Windows Server 2008 Standard Edition, Release 2 (on x86-64
hardware)
v Red Hat Enterprise Linux 5 (on x86-32 hardware)
v Red Hat Enterprise Linux 5 (on x86-64 hardware)
v Red Hat Enterprise Linux 5 (on zSeries and System z hardware)
v Red Hat Enterprise Linux 6 (on x86-32 hardware)
v Red Hat Enterprise Linux 6(on x86-64 hardware)
v Sun Solaris 9 (on SPARC processor-based systems)
v Oracle Solaris 10 (on SPARC processor-based systems)
v SUSE Linux Enterprise Server (SLES) 10 (on System z hardware)
v SUSE Linux Enterprise Server (SLES) 10 (on x86-32 hardware)
v SUSE Linux Enterprise Server (SLES) 10 (on x86-64 hardware)
v SUSE Linux Enterprise Server (SLES) 11 (on System z hardware)
v SUSE Linux Enterprise Server (SLES) 11 (on x86-32 hardware)
v SUSE Linux Enterprise Server (SLES) 11 (on x86-64 hardware)
v SUSE Linux Enterprise Server (SLES) 11 (for IBM POWER® processors)
v VMWare ESX Server 3

Note: Bidirectional languages are not supported on the Sun Solaris platform.

Chapter 9. Installing Integration Composer 183

Database servers The customer is responsible for the database servers, which contain and manage
one or more source databases and a target (Maximo) database.

The following databases are supported:

v IBM DB2 Enterprise Server Edition 9.5 (on all supported operating
systems—does not support 32-bit Linux)
v IBM DB2 Enterprise Server Edition 9.7
v Microsoft SQL Server 2008 Enterprise Edition (on Microsoft Windows operating
systems only)
v Oracle Database 9i Enterprise Edition Release 2.9.2.0.8 (on all supported
operating systems)
v Oracle Database 10g Enterprise Edition Release 1 (on all supported operating
systems)
v Oracle Database 10g Enterprise Edition Release 2 (on all supported operating
systems)
v Oracle Database 11g Enterprise Edition Release 1 (on all supported operating
systems)
v [Upgrade only] Oracle Database 11g Enterprise Edition Release 2 (on all
supported operating systems)
See the appropriate database documentation for the database server hardware
requirements.

Web browser To display its help information, Integration Composer requires a Web browser.

Installation prerequisites
Before installing, you must have the IBM Java Software Development Kit
prerequisite for Integration Composer on your system, and any software that
adversely affects the InstallAnywhere installation program must be removed.

IBM Java SDK 6.0 for the appropriate operating system is an installation
prerequisite that must be present on the Integration Composer computer. The IBM
Java SDK is provided on the product DVDs.

The installation or upgrade has to run on JRE 1.6, so it must be set as the system's
Java virtual machine (JVM). If more than one JRE is installed on the computer, the
PATH and CLASSPATH system variables must indicate JRE 1.6.

UNIX On UNIX-based operating systems, be sure the PATH environment

variable includes the location of the Java Virtual Machine (for example, Java60).

Because the following software can adversely affect InstallAnywhere—the

installation program used by Integration Composer—disable the following
programs before attempting to install Integration Composer:
v Antivirus software, such as Norton Antivirus or Symantec Client Firewall
v Dell OpenManage
v Search software, such as pcAnywhere

184 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Use of these software programs affects the ability of InstallAnywhere to install
programs; however, the problem is not specific to Integration Composer.

[Installation only] Before beginning your installation, make sure you have on hand
the information on the target (Maximo) database described in Table 23 on page 186.

Performing an Integration Composer installation

SmartCloud Control Desk installations that want to use Integration Composer
should install it from the Launchpad, as described herein. If you need to install
Integration Composer on a UNIX operating system in console mode, instructions
to do that are also described.

Results

When the installation completes successfully, you can access Integration Composer
as follows:

Windows From the Start menu, or by entering the command: itic_installation_dir\

bin\startFusion.bat

The default Integration Composer installation directory for Windows

operating systems is C:\Integration Composer.
UNIX By entering the command: itic_installation_dir/bin/startFusion.sh

The default Integration Composer installation directory for UNIX operating

systems is /home/user/Integration_Composer.

Installing Integration Composer using the Launchpad

Windows UNIX For IBM SmartCloud Control Desk installations, the
recommended way to install Integration Composer is from the Launchpad. Use the
Launchpad to install Integration Composer on Windows or UNIX operating
systems.

Before you begin

Make sure that you have up to 70 MB of free space for the installation directory.

Procedure
1. Insert the Launchpad DVD into the server where you install Integration
Composer.
If you are installing on a UNIX operating system, you might have to start the
Launchpad manually by running the launchpad.sh command, which is located
in the root directory of the Launchpad DVD. (On Windows operating
systems, the launchpad.exe command runs automatically.)

Note: Confirm that the java -version command returns 1.6 before starting
the installation. IBM Java SDK 6.0 with JRE 1.6 is provided on the product
DVDs.
2. From the Launchpad, launch the Integration Composer installation program
by clicking the link under Install IBM Tivoli Integration Composer.
3. In the IBM Tivoli Integration Composer window, select your language from
the drop-down list at the bottom and click OK.

Chapter 9. Installing Integration Composer 185

 4. [UNIX only] In the Select Install Type window, select New Install and click
Next.
5. In the Introduction window, review the information and click Next.
6. In the Choose IBM SDK Location window, type the directory where IBM Java
SDK 6.0 is located, or click Choose to browse and select the directory. Then
click Next.
7. In the Choose Install Folder window, accept the default location or type a file
path to specify where you want to install the product. (Or you can click
Choose to browse and select the location you want.) Then click Next.
8. In the Database Type window, select your Maximo database type (the Maximo
database is where the Integration Composer repository is installed) and click
Next. IBM DB2 is the default.
The Database Login Information window is displayed.
9. On the Database Login Information window, type login specifications for the
database and click Next.
The Database Login Information window is where you define the parameters
for connecting to the Maximo database. The fields displayed in this window
vary slightly, depending on the type of database you chose in the previous
step. The following table defines the fields that the installation program
displays for the supported databases.
Table 23. Login specifications for the Maximo database
Field Description
Database Server Name Name of the server on which the Maximo database
resides
Port Number Port number of the server on which the Maximo
database resides
Database Name (SID) For Oracle databases, this is the session identifier
(SID) for the database; that is, the database
or instance

Database Name For SQL Server or IBM databases, this is simply

the name of the database
Database Username Valid user name for signing in to the Maximo
database
Database/Schema Owner Database or schema owner

Tip: Make note of the values that you specified here. Later, when you launch
Integration Composer, use the values entered in these fields to define
connection parameters for the Maximo database.
10. On the Update Software Instances window, select one of the following options
and click Next:
Yes, disable software updates
If you select this option, when Integration Composer imports data into
the Maximo database, Integration Composer inserts or deletes
software records but does not update software records. This option is
preferred.
No, don't disable software updates
If you select this option, when Integration Composer imports data into
the Maximo database, Integration Composer updates existing software
records.

186 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 In the Software Class Name field, it is recommended to accept the default
value Software. The Software Class name is used to identify the class that you
do not want to update based on the choice you made. In the Deployed Assets
target schema, the name is Software.
11. [UNIX only] In the Choose Internet Browser File window, accept the default
browser or choose another browser to be used for displaying the Integration
Composer online help, then click Next.
12. On the Preinstallation Summary window, review the installation details. (If
necessary, use the Previous buttons to go back and make corrections, and use
the Next buttons to return to this window.) When satisfied with the summary
data, click Install.
The Installing Integration Composer progress window displays during
installation. When installing is finished, the Installation Complete window is
displayed.
13. In the Installation Complete window, click Done.

Installing Integration Composer on UNIX operating systems in

console mode
UNIX Use the procedure described here if you have to install Integration
Composer on a UNIX computer in console (command line) mode.

Before you begin

Make sure you have up to 70 MB of free space for the installation directory.

About this task

The Integration Composer files are located in either the \ITIC or \Install\ITIC
directory on the version 7.5.1 product DVD. Use the setup.bin command from the
DVD layout to start the upgrade process:
setup.bin ←
setup.exe

The steps for installing Integration Composer on a UNIX-based operating system

follow.

Procedure
1. Sign on to the server as an administrator (for example, as root).
2. Save the binary Integration Composer installation file, setup.bin, on the
server where you intend to install Integration Composer.
3. Make sure JRE 1.6 is in your system path.
To add JRE 1.6 to the path, enter the following commands (where JRE_location
is the path for your IBM JRE; for example, /opt/ibm/java-i386-60/jre/
bin:$PATH):
JAVA_HOME=JRE_location
export JAVA_HOME
PATH=$JAVA_HOME:$PATH
export PATH
4. Navigate to the location where you saved the setup.bin file.
5. Enter the following command to make the binary installation file executable:
chmod +x setup.bin

Chapter 9. Installing Integration Composer 187

 6. Run the Integration Composer installation program in console mode by
entering the following command at the shell prompt:
sh ./setup.bin -i console
In console mode, you are prompted to enter information line by line.

Note: Confirm that the java -version command returns 1.6 before starting
the installation. IBM Java SDK 6.0 with JRE 1.6 is provided on the product
DVDs.
7. In the Choose Locale step, type the number of your locale from the list of
locales and press Enter.
8. In the Introduction step, review the Introduction information and press Enter.
9. In the Select Install Type step, press Enter to accept the default (New Install).
10. In the IBM SDK Location step, specify the file path where IBM Java SDK 6.0 is
installed by doing one of the following:
v Accept the default location and press Enter.
v Type a different file path for the location and press Enter.
11. In the Choose Install Folder step, specify where you want to install Integration
Composer by doing one of the following:
v Accept the default location and press Enter.
v Type a different file path for the location and press Enter; then type y to
confirm the new location, and press Enter again.
12. In the Database Type step, indicate your Maximo database type (the Maximo
database is where the Integration Composer repository will be installed) by
typing the associated number; then press Enter. The Database Login
Information step is displayed.
This Database Login Information step is where you define the parameters for
connecting to the Maximo database. The fields displayed in this step vary
slightly, depending on the type of database you chose in the previous step.
The following table defines the fields that the installation program displays
for the supported databases.

Field Description
Database Server Name Name of the server on which the target database
resides
Port Number Port number of the server on which the target
database resides
Database Name (SID) For Oracle databases, this is the session identifier
(SID) for the database; that is, the database instance
or
For SQL Server or databases provided by IBM, this
Database Name is simply the name of the database
Database Username Valid user name for signing in to the target
database
Database/Schema Owner Database or schema owner

13. In the Database Login Information step, type each login specification for the
database, one at a time, pressing Enter after each entry to advance to the next
specification.

188 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Tip: Make note of the values that you specified here. Later, when you launch
Integration Composer, use the values entered in these fields to define
connection parameters for the target data source.
14. In the Update Software Instances step, type a number to select one of the
following options, and press Enter:
v Yes, disable software updates
If you select this option, when Integration Composer imports data into the
target database, Integration Composer inserts or deletes software records
but does not update software records. This option is preferred for
performance reasons.
v No, don't disable software updates
If you select this option, when Integration Composer imports data into the
target database, Integration Composer updates existing software records.
15. In the Software Class Name step, accept the default and press Enter.
16. In the Choose Internet Browser File step, accept the default browser, Netscape
(only the Netscape browser is supported on UNIX-based operating systems);
then press Enter.
17. In the Preinstallation Summary step, review the installation details and press
Enter to begin installing Integration Composer. The Installing progress bar
displays during installation.
When installation is complete, the Installation Complete step is displayed.
18. In the Installation Complete step, press Enter. The installation is done and you
are returned to the UNIX command prompt.

Performing an Integration Composer upgrade

IBM SmartCloud Control Desk installations that want to upgrade Integration
Composer should do so from the Launchpad, as described herein. If you need to
upgrade Integration Composer on a UNIX operating system in console mode,
instructions to do that are also described.

About this task

This upgrade is for any Integration Composer 7.2.1 or later release, including
Integration Composer 7.2.1, 7.2.2, and 7.2.2.1. The installation program does not
permit upgrades from earlier releases. On Windows operating systems, the
installation program automatically checks for a valid current release prior to
upgrading.

Results

When the upgrade completes successfully, you can access Integration Composer as
follows:

Windows From the Start menu, or by entering the command: itic_installation_dir\

bin\startFusion.bat

The default Integration Composer installation directory for Windows

operating systems is C:\Integration Composer.

UNIX By entering the command: itic_installation_dir/bin/startFusion.sh

The default Integration Composer installation directory for UNIX operating

systems is /home/user/Integration_Composer.

Chapter 9. Installing Integration Composer 189

 Upgrading Integration Composer using the Launchpad
Windows UNIX For SmartCloud Control Desk installations, the recommended
way to upgrade Integration Composer is from the Launchpad. Use the Launchpad
to upgrade Integration Composer on Windows or UNIX operating systems.

Before you begin

To avoid losing any of your current data, back up your Integration Composer
data\dataschema and data\mappings directories before upgrading.

Attention: For this release, the Naming and Reconciliation Service (NRS) was
upgraded to Data Integration Services (DIS). As part of this Integration Composer
installation, the nameReconciliation.logging.properties file is removed from the
properties subdirectory in the Integration Composer installation directory, and the
removed file is replaced with the dis.logging.properties file. As a result, any
customizations that were made to the original
nameReconciliation.logging.properties file are lost.

Before upgrading to this release of Integration Composer, note your current

customization information if you plan to to reuse any of that information in the
new dis.logging.properties file. For additional details about these properties
files, see the book IBM Tivoli Integration Composer Administrator Guide.

Make sure that you have up to 70 MB of free space for the installation directory.

Procedure
1. Insert the Launchpad DVD into the server where you upgrade Integration
Composer.
If you are upgrading on a UNIX operating system, you might have to start the
Launchpad manually by running the launchpad.sh command, which is located
in the root directory of the Launchpad DVD. (On Windows operating systems,
the launchpad.exe command runs automatically.)

Note: Confirm that the java -version command returns 1.6 before starting the
upgrade. IBM Java SDK 6.0 with JRE 1.6 is provided on the product DVDs.
2. From the Launchpad, launch the Integration Composer upgrade program by
clicking the link under Install IBM Tivoli Integration Composer.
3. In the IBM Tivoli Integration Composer window, select your language from the
drop-down list at the bottom and click OK.
4. Read the information in the Introduction window and click OK.
5. [UNIX only] In the Select Install Type window, select Upgrade and click Next.
6. In the Choose Install Folder window, accept the default location or type a file
path to specify where you want to upgrade the product. (Or you can click
Choose to browse and select the location you want.) Then click Next.
7. In the Choose IBM SDK Location window, type the directory where IBM Java
SDK 6.0 is located, or click Choose to browse and select the directory. Then
click Next.
8. On the Preinstallation Summary window, review the upgrade details. (If
necessary, use the Previous buttons to go back and make corrections, and use
the Next buttons to return to this window.) When satisfied with the summary
data, click Install.

190 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 The Installing Integration Composer progress window displays during
upgrade. When upgrading is finished, the Installation Complete window is
displayed.
9. In the Installation Complete window, click Done.

Upgrading Integration Composer on UNIX operating systems

in console mode
UNIX Use the procedure described here if you have to upgrade Integration
Composer on a UNIX computer in console (command line) mode.

Before you begin

Installing Integration Composer 7.5.1, as described in this section, will upgrade the
previous version of Integration Composer. You do not need to remove the previous
version first. To avoid losing any of your current data, back up your Integration
Composer data\dataschema and data\mappings directories before upgrading.

Attention: For this release, the Naming and Reconciliation Service (NRS) was
upgraded to Data Integration Services (DIS). As part of this Integration Composer
installation, the nameReconciliation.logging.properties file is removed from the
properties subdirectory in the Integration Composer installation directory, and the
removed file is replaced with the dis.logging.properties file. As a result, any
customizations that were made to the original
nameReconciliation.logging.properties file are lost.

Before installing this release of Integration Composer, note your current

customization information if you plan to to reuse any of that information in the
new dis.logging.properties file. For additional details about these properties
files, see the book IBM Tivoli Integration Composer Administrator Guide.

Make sure you have up to 70 MB of free space for the installation directory.

About this task

The Integration Composer files are located in either the \ITIC or \Install\ITIC
directory on the version 7.5.1 product DVD. Use the setup.bin command from the
DVD layout to start the upgrade process:
setup.bin ←
setup.exe

The steps for upgrading Integration Composer on a UNIX-based operating system

follow.

Procedure
1. Sign on to the server as an administrator (for example, as root).
2. Save the binary Integration Composer installation file, setup.bin, on the
server where you intend to install Integration Composer.
3. Make sure JRE 1.6 is in your system path.
To add JRE 1.6 to the path, enter the following commands (where JRE_location
is the path for your IBM JRE; for example, /opt/ibm/java-i386-60/jre/
bin:$PATH):

Chapter 9. Installing Integration Composer 191

 JAVA_HOME=JRE_location
export JAVA_HOME
PATH=$JAVA_HOME:$PATH
export PATH
4. Navigate to the location where you saved the setup.bin file.
5. Enter the following command to make the binary installation file executable:
chmod +x setup.bin
6. Run the Integration Composer installation program in console mode by
entering the following command at the shell prompt:
sh ./setup.bin -i console
In console mode, you are prompted to enter information line by line.

Note: Confirm that the java -version command returns 1.6 before starting
the upgrade. IBM Java SDK 6.0 with JRE 1.6 is provided on the product
DVDs.
7. In the Choose Locale step, type the number of your locale from the list of
locales and press Enter.
8. In the Introduction step, review the Introduction information and press Enter.
9. In the Select Install Type step, type the number for the Upgrade selection and
press Enter. This indicates that you want to upgrade Integration Composer
from the previous release.
10. In the Choose Install Folder step, type the location (absolute path) where
Integration Composer is currently installed and press Enter. Or just press
Enter to accept the displayed path.
11. In the IBM SDK Location step, specify the file path where IBM Java SDK 6.0 is
installed by doing one of the following:
v Accept the default location and press Enter.
v Type a different file path for the location and press Enter.
12. In the Preinstallation Summary step, review the installation details and press
Enter to begin installing Integration Composer. The Installing progress bar
displays during installation.
When installation is complete, the Installation Complete step is displayed.
13. In the Installation Complete step, press Enter. The installation is done and you
are returned to the UNIX command prompt.

Confirming the installation

This section explains how to verify that your new Integration Composer
installation (or upgrade) is installed correctly.

Procedure
1. Open the Integration Composer application by doing one of the following
things:

Windows From the Windows Start menu, select Start > Programs > IBM Tivoli >
Integration Composer > IBM Tivoli Integration Composer

or

from the command line, enter the command: startFusion.bat

192 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 UNIX Enter the command: ./startFusion.sh.

2. Sign in to the Integration Composer application using the database (or schema
owner) username and password that you supplied during the installation.
3. From the Help menu in the Integration Composer main window, select About.
4. On the About Integration Composer window, check that the number in the
Version field is 7.5.1. If this number is displayed, Integration Composer was
successfully installed.

Post-installation tasks
This section provides instructions for verifying that Integration Composer is
configured correctly after you install or upgrade.

Verifying the settings in the Integration Composer

fusion.properties file
The fusion.properties file is the properties file for Integration Composer. Among
other things, these properties specify Maximo and Integration Composer
database-related properties and application properties. This verification task is to
ensure that, after you have installed or upgraded Integration Composer, critical
property settings in the fusion.properties file are correct.

Before you begin

The Integration Composer fusion.properties file is located as follows:

itic_install_dir\data\properties\fusion.properties

Procedure
1. Locate the Integration Composer fusion.properties file in your Integration
Composer installation directory, itic_install_dir.
2. In the IBM Tivoli Integration Composer (ITIC) Mapping Execution Properties
section, verify that NRS is enabled (set to true) if you are using NRS:
mxe.fusion.mapping.nrs.enable=true
or disabled (set to false) if you are not using NRS:
mxe.fusion.mapping.nrs.enable=false
Naming and Reconciliation Service (NRS), which is part of Data Integration
Services (DIS), is an optional component that Integration Composer works with
to uniquely identify deployed assets or actual CIs (configuration items) and
avoid duplication of asset or CI records in your database.
By default, Integration Composer is configured to use this component, which
assigns a globally unique identifier, the DIS GUID, to a deployed asset or actual
CI based on defined naming rules. However, Integration Composer will not
operate successfully if it is configured to use NRS (if the NRS property is set to
true) but NRS is not installed and running. So, if you do not use NRS, be sure
to set the NRS property to false so that Integration Composer will run
successfully.
DIS/NRS is required to perform automated linking of their authorized asset and
CI counterparts. If you use this function, you should have DIS/NRS running
and have the NRS property in the fusion.properties file set to true.

Chapter 9. Installing Integration Composer 193

 Integration Composer recommends that DIS/NRS be installed and enabled. The
NRS property is enabled (set to true) by default.
3. In the IBM Tivoli Maximo Database Related Properties section, verify that the
database schema owner, JDBC driver specification, and JDBC URL specification
are correct. Use the following table as a guide:

Property Description Value

mxe.db.schemaowner Database schema Enter the appropriate schema for your database; for example, dbo.
owner

mxe.db.driver JDBC driver This varies depending on the database, for example:
specification
IBM DB2:
com.ibm.db2.jcc.DB2Driver
Oracle JDBC Thin driver:
oracle.jdbc.driver.OracleDriver
Microsoft JDBC driver (SqlServer):
com.microsoft.sqlserver.jdbc.SQLServerDriver
i-net Opta driver (SqlServer):
com.inet.tds.TdsDriver
Note: Users upgrading from a previous release and who
already have this (deprecated) driver can still use it for
Microsoft SQL Server support. However, in the future, using
the Microsoft JDBC driver for your SQL Server is
recommended.

mxe.db.url JDBC database URL This varies depending on the database, for example:
IBM DB2:
jdbc:db2://host_name:host_port/database_name
Oracle JDBC Thin driver:
jdbc:oracle:thin:@host_name:host_port:host_SID
Microsoft JDBC driver (SqlServer):
jdbc:sqlserver://host_name:host_port;databaseName=
database_name;integratedSecurity=false;
i-net Opta driver (SqlServer 7.0 or higher):
jdbc:inetdae7:host_name:host_port?database=database_name
Note: Users upgrading from a previous release and who
already have this (deprecated) driver can still use it for
Microsoft SQL Server support. However, in the future, using
the Microsoft JDBC driver for your SQL Server is
recommended.

mxe.db.user Database user login

name

4. UNIX In the Integration Composer (ITIC) Application Properties section,

users of UNIX-based operating systems should check that the
mxe.fusion.browser property specifies netscape. For UNIX, Netscape is the only
supported Web browser for Integration Composer:
mxe.fusion.browser=netscape

194 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Note: Windows For Windows operating systems, the browser always defaults
to Microsoft Windows Explorer.

Changing the memory allocation in the startFusion file

(optional)
The startFusion file, named startFusion.bat in Windows operating systems or
startFusion.sh in UNIX-based operating systems, is the startup file for the
Integration Composer graphical user interface. This verification task is to ensure
that, after you have installed or upgraded Integration Composer, the memory
allocation in the startFusion file is correct.

Before you begin

This task is optional. You need to perform it only if the Integration Composer
graphical user interface does not start as described in “Confirming the installation”
on page 192.

About this task

The Integration Composer startFusion file is located in the Windows and UNIX
installation directories, as follows:

Windows itic_install_dir\bin\startFusion.bat

UNIX itic_install_dir/bin/startfusion.sh

When you install Integration Composer, the installation program assigns 1536
megabytes as the default amount of virtual RAM to allocate to the application. But,
for example, if your server only has 1GB of physical memory, the 1536M setting will
not work for you.

Procedure

If the Integration Composer graphical user interface does not start, check the
memory setting for the start javaw.exe command in the startFusion file, and
decrease memory as necessary.

Example

For example, change -Xmx1536M to -Xmx1024M.

Changing the memory allocation in the executeMapping file

(optional)
The executeMapping file, named executeMapping.bat in Windows operating systems
or executeMapping.sh in UNIX-based operating systems, is the Integration
Composer script for running a mapping. This verification task is to ensure that,
after you have installed Integration Composer, the memory allocation in the
executeMapping file is correct.

Before you begin

This task is optional. You need to perform it only if the Integration Composer
mapping does not run, or if you just upgraded and had increased the amount of

Chapter 9. Installing Integration Composer 195

 memory allocated to Integration Composer in your previously installed version.

About this task

The Integration Composer executeMapping file is located in the Windows and

UNIX-based installation directories, as follows:

Windows itic_install_dir\bin\executeMapping.bat

UNIX itic_install_dir/bin/executeMapping.sh

When you install Integration Composer, the installation program assigns 1536 MB
as the default amount of virtual RAM to allocate to the application. But, for
example, if your server only has 1 GB of physical memory, the 1536M setting will
not work for you.

Procedure
v If the Integration Composer mapping does not run, check the memory setting
for the java command in the executeMapping file, and decrease memory. To do
so, edit the executeMapping file and change the –Xmx parameter in the java
command.
For example, change -Xmx1536M to -Xmx1024M
v [Upgrade only] If you previously increased the amount of memory allocated to
Integration Composer imports, verify that your memory settings have not
changed. If you have to increase the amount of memory assigned, edit the
executeMapping file and change the –Xmx parameter in the java command.
For example: change -Xmx1536M to -Xmx2048M

Uninstalling Integration Composer

This section provides instructions for removing Integration Composer from
Microsoft Windows and UNIX-based operating systems.

Uninstalling Integration Composer on Windows operating

systems
Use the procedure described here to remove Integration Composer from
Windows
a Windows-based operating system.

Procedure
1. In Microsoft Windows Explorer, go to the uninstall folder, installation_dir\
Uninstall_Integration_Composer, where Integration Composer 7.5.1 was
installed.
2. In the uninstall folder, double-click the uninstall file,
Uninstall_Integration_Composer.exe. The Integration Composer utility for
uninstalling the application displays the Uninstall IBM Tivoli Integration
Composer window.
3. Click Uninstall. The Uninstall IBM Tivoli Integration Composer progress
window is displayed as the uninstall utility removes the application.

Note: If necessary, you can click Cancel to stop the uninstallation.

196 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 When the removal of Integration Composer is finished, the Uninstall Complete
window is displayed.
4. Click Done. The removal of Integration Composer is completed.
5. Optional: When the utility removes Integration Composer, one or more files
sometimes remain in the installation directory. (For example, these files might
be files that someone manually put into the directory, such as mapping files or
schema files that the user imported, or they might be log files that Integration
Composer created.) You can delete these files manually.

Uninstalling Integration Composer on UNIX operating systems

UNIX Use the procedure described here to remove Integration Composer from
a UNIX-based operating system.

Procedure
1. Go to the uninstall folder, itic_install_dir\Uninstall_Integration_Composer,
where Integration Composer 7.5.1 was installed.
2. In the uninstall folder, do one of the following options:
v If you installed the Integration Composer using the X Window System
application, type:
sh ./Uninstall_IBM_Tivoli_Integration_Composer
v If you installed the Integration Composer using console mode, type:
sh ./Uninstall_IBM_Tivoli_Integration_Composer -i console
The instructions that follow describe the remaining uninstallation steps using
console mode.
3. Press Enter to initiate the command from the previous step. The Uninstalling
progress bar is displayed as the uninstall utility removes the application.
When the removal of Integration Composer is finished, you are returned to the
command prompt.
4. Optional: After the utility removes Integration Composer, one or more files
sometimes remain in the installation directory. (For example, these files might
be files that someone manually put into the directory, such as mapping files or
schema files that the user imported, or they might be log files that Integration
Composer created.) You can delete these files manually.

Chapter 9. Installing Integration Composer 197

198 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Chapter 10. Installing the Deployer's Workbench
The Deployer's Workbench is a separately installed, Eclipse-based workbench that
is the best-practice tool for creating authorized CI spaces. Install it on a Windows
workstation that can connect to your SmartCloud Control Desk server.

About this task

If you are installing the Entry edition of SmartCloud Control Desk, you do not
need to install the Deployer's Workbench.

You can install the Deployer's Workbench using either the SmartCloud Control
Desk launchpad or the native installer. In either case, the DVD1 image or physical
DVD must be accessible from the workstation where you want to install the
Deployer's Workbench.

Procedure
1. Start the Deployer's Workbench installer. Either start the SmartCloud Control
Desk launchpad, click Install the Product, and click Install Deployer's
Workbench, or to use the native installer, cd to the DW directory and run
install.exe.
2. You might see a message saying that Install Anywhere is preparing to install.
When the Deployer's Workbench screen appears, choose a language from the
drop-down list and click OK.
3. Review the information on the Introduction screen. Click Next to continue.
4. Choose the installation folder and where to install icons.
5. Review the pre-installation summary. Click Previous to make any changes.
Click Install to begin the installation.
6. You will see a progress bar indicating the progress of the installation procedure.
After the installation has completed, click Done to exit the installer.

© Copyright IBM Corp. 2012 199

200 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Chapter 11. Installing IBM SmartCloud Control Desk
Everyplace
Use the information in this section to install the optional component IBM
SmartCloud Control Desk Everyplace®.

IBM SmartCloud Control Desk Everyplace comes with its own launchpad, which
you can use to install it on the same administrative workstation where you
installed SmartCloud Control Desk. The installation process does not create a new
EAR file; it updates the maximo.ear file, which you must then rebuild and
redeploy. The installation process does not update the maximoiehs.ear file, so you
do not need to rebuild and redeploy this file. The installation procedure depends
on your scenario. Choose the link that matches your situation.

Installing as part of a new product installation

Follow these steps if you are installing IBM SmartCloud Control Desk Everyplace
as part of a fresh installation of SmartCloud Control Desk.

About this task

When you begin the installation of SmartCloud Control Desk, be sure to defer the
update of the database and the deployment of the ear file. You must complete
these steps after running the SmartCloud Control Desk installer and before
updating the database.

Procedure
1. Insert the IBM SmartCloud Control Desk Everyplace installation DVD or link to
the installable image.
2. Issue the command to start the launchpad that is appropriate for your
administrative workstation:
launchpad.exe
Use this command for 32-bit Windows workstations.
launchpad64.exe
Use this command for 64-bit Windows workstations.
launchpad.sh
Use this command for workstations running other operating systems.
3. To install IBM SmartCloud Control Desk Everyplace, open the Install Product
page and click the link to start the installer.
4. As you run the installer, be sure to choose Deploy application files manually
later and Defer the update of the Maximo database. This causes the IBM
SmartCloud Control Desk Everyplace code to be added to the SmartCloud
Control Desk files whose installation will be completed in subsequent steps.
5. When the installation is complete, in the Package Successfully Deployed
window, click Done.

What to do next

After you have installed IBM SmartCloud Control Desk Everyplace, you must
return to the product installer to complete the installation of all components, the

© Copyright IBM Corp. 2012 201

 updating of the database, and the building and deployment of the EAR file.

Installing as part of a product upgrade

If you are installing IBM SmartCloud Control Desk Everyplace as part of an
upgrade to SmartCloud Control Desk, follow the steps in the Upgrade Guide.

About this task

The Upgrade guide includes information on installing IBM SmartCloud Control

Desk Everyplace as part of an upgrade. You can find the Upgrade Guide on the
Installing, Migrating and Upgrading page of the SmartCloud Control Desk wiki.

Installing after SmartCloud Control Desk has been installed

Follow these steps if you are installing IBM SmartCloud Control Desk Everyplace
after you have completed the installation of SmartCloud Control Desk.

About this task

You can install IBM SmartCloud Control Desk Everyplace as an addition to an

existing installation of SmartCloud Control Desk.

The following procedure assumes that you want to minimize the time for which
your J2EE server is down.

Procedure
1. Insert the IBM SmartCloud Control Desk Everyplace installation DVD or link to
the installable image.
2. Issue the command to start the launchpad that is appropriate for your
administrative workstation:
launchpad.exe
Use this command for 32-bit Windows workstations.
launchpad64.exe
Use this command for 64-bit Windows workstations.
launchpad.sh
Use this command for workstations running other operating systems.
3. To install IBM SmartCloud Control Desk Everyplace, open the Install Product
page and click the link to start the installer.
4. Select the installation path for SmartCloud Control Desk from the drop-down
menu.
5. Do not choose Deploy application files manually later or Defer the update of
the Maximo database. Instead, allow the installer to complete all steps.
6. When the installation is complete, in the Package Successfully Deployed
window, click Done.

202 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Chapter 12. Post installation tasks
There are several post installation tasks required in order to complete the
SmartCloud Control Desk deployment.

Accessing product documentation

Accessing the SmartCloud Control Desk information center documentation and
product online help.

Important: The WebSphere Application Server deployment manager must be

restarted after the installation of SmartCloud Control Desk. Restarting enables the
full function of the information center and online help.

In order to be able to access the product documentation system with the product,
complete the following steps after you install SmartCloud Control Desk.
1. Stop the deployment manager by running the following command:
c:\Program Files\IBM\WebSphere\AppServer\profiles\<dmgr profile>\bin\stopManager
-username wasadmin -password <password>
2. Start the deployment manager by running the following command:
c:\Program Files\IBM\WebSphere\AppServer\profiles\<dmgr profile>\bin\startManager

If you manually configured the application server after you ran the product
installation program, you must set the property for the product documentation
server. For more information, see https://www.ibm.com/support/
docview.wss?uid=swg21508594.

Important: The deployment manager (a component of WebSphere Application

Server Network Deployment) allows for remote management and deployment
operations. While the deployment manager is stopped, all management and
deployment operations, including outside of SmartCloud Control Desk, are affected
(stopped).

Initial data configuration

After you have successfully installed and configured SmartCloud Control Desk
components, there are several data configuration tasks you must complete before
using SmartCloud Control Desk.

Signing in using a default user ID

User management can be managed through the Maximo application or though the
directory server you have configured to use with SmartCloud Control Desk

Before you begin

When first installed, SmartCloud Control Desk contains the following default user
IDs:
Table 24. SmartCloud Control Desk users
User
wasadmin

© Copyright IBM Corp. 2012 203

 Table 24. SmartCloud Control Desk users (continued)
User
maxadmin
mxintadm
maxreg

Important: Before you begin this procedure, if you are using a directory server as
part of your deployment, ensure that these users are created in your LDAP
repository.

Note: User names and passwords are case-sensitive. The defaultuser names are
lowercase.

About this task

To sign in, complete the following steps:

Procedure
1. Open a browser window.
2. Navigate to the SmartCloud Control Desk login URL. For example: http://host
name:port/maximo.
3. Enter the user name maxadmin (lower case).
4. Enter the password you entered during the installation, and click Enter. The
default start center for maxadmin is displayed.

Configuring SMTP
Installation panels provide an opportunity to configure an SMTP server to send an
administrator, or other users, e-mail notifications of system events. If you skip
these panels when you install SmartCloud Control Desk, you can use the
SmartCloud Control Desk interface to configure SMTP parameters.

Before you begin

This task must be completed before you apply changes to the database.

About this task

To configure SMTP for SmartCloud Control Desk, complete the following steps.

Procedure
1. Log in to the console as maxadmin.
2. Open the System Configuration > Platform Configuration > System
Properties application.
3. Using the Filter feature, search for the mail.smtp.host Property Name.
4. Expand the mail.smtp.host property and set the Global Value attribute to
your SMTP host.
5. Select the mail.smtp.host record check box.
6. Click the Live Refresh icon in the toolbar.
7. From the Live Refresh dialog, click OK.
8. Using the Filter feature, search for the mxe.adminEmail Property Name.

204 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 9. Expand the mxe.adminEmail property and set the Global Value attribute to
your e-mail address.
10. Select the mxe.adminEmail record check box.
11. Click the Live Refresh icon in the toolbar.
12. From the Live Refresh dialog, click OK.
“Applying changes to the database” on page 206
When you create a general ledger account component, it must be applied to the
Maximo database.

Create currency codes

You must define a currency code for an organization.

About this task

To define a currency code for an organization, complete the following steps.

Procedure
1. Open the Financial > Currency Code application.
2. Click New Row.
3. Enter a currency name. For example, USD.
4. Click the Save icon.

Create item and company sets

You must define item and company sets for an organization.

About this task

To define item and company sets for an organization, complete the following steps:

Procedure
1. Open the Administration > Sets application.
2. Click New Row.
3. Enter an item name. For example, IT Items.
4. Enter ITEM in the Type field.
5. Click New Row.
6. Enter a company set name. For example, IT Comps.
7. Enter COMPANY in the Type field.
8. Click the Save icon.

Create an organization
You must define at least one organization for SmartCloud Control Desk.

About this task

To define an organization, complete the following steps.

Procedure
1. Open the Administration > Organizations application.
2. Click the New Organization icon in the toolbar.
3. Enter an organization name in the Organization field. For example, ENGLENA.

Chapter 12. Post installation tasks 205

 4. Enter the base currency you defined in the Base Currency 1 field. For
example, USD.
5. Enter the item set you defined in the Item Set field. For example, IT Items.
6. Enter the company set you defined in the Company Set field. For example,
IT Comps.
7. Enter the default item status of PENDING in the Default Item Status field.
8. Click theSites tab.
9. Click New Row.
10. Enter a site name in the Site field. For example, B901.
11. Click the Save icon.

Create a general ledger account component

You must create a general ledger account component for SmartCloud Control Desk.

About this task

To create a general ledger account component, complete the following steps.

Procedure
1. Open the System Configuration > Platform Configuration > Database
Configuration application.
2. Choose the GL Account Configuration action.
3. Click New Row.
4. Enter a component name in the Component field. For example, MYCOMPONENT.
5. Enter a numeric length for the component. For example, 5.
6. Enter a type for the component. For example, ALN.
7. Click OK.

Applying changes to the database

When you create a general ledger account component, it must be applied to the
Maximo database.

About this task

To apply configuration changes to the Maximo database, complete the following

steps.

Procedure
1. Log in to the Maximo console as maxadmin
2. Open the System Configuration > Platform Configuration > Database
Configuration application. Every object that must be updated in the Maximo
database has a status of To Be Added.
3. Choose the Manage Admin Mode action.
4. Click Turn Admin Mode ON, and then click OK when prompted. This task
takes several minutes to complete. You can use the Refresh Status button to
view progress.
5. After Admin Mode has been enabled, select Apply Configuration Changes, to
apply the changes to the Maximo database. To Be Changed must not appear in
the status column for objects listed.
6. Turn Admin Mode OFF.

206 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 a. Open the System Configuration > Platform Configuration > Database
Configuration application.
b. Choose the Manage Admin Mode action.
c. Click Turn Admin Mode OFF, and then click OK when prompted. Failing
to turn off Admin Mode within the application causes cron tasks to fail.

Create a general ledger account

You must create a general ledger account for SmartCloud Control Desk.

About this task

To create a general ledger account, complete the following steps:

Procedure
1. Open the Financial > Chart of Accounts application.
2. Click the name of your organization to select it. For example, click
ENGLENA.
3. Choose the GL Component Maintenance action.
4. Click New Row.
5. Add a GL Component value and a description and then click OK. For
example, 1234.
6. Click New Row.
7. Select your General Ledger Account.
8. Click Save.
9. Open the Goto > Administration > Organizations application.
10. Click the organization name you created. For example, ENGLENA.
11. From the Clearing Account field, select the General Ledger Account you just
created.
12. Select Active.
13. Click the Save icon.

Update General Ledger Component Type Authorization

You must update the general ledger component type authorization for SmartCloud
Control Desk.

About this task

To authorize a Security Group to change a general ledge component type, complete

the following steps:

Procedure
1. Open the Security > Security Groups application.
2. Select the Group that provides authorization (for example, PMSCOA).
3. Click the GL Components tab.
4. Click the Authorized check box for each GL Component.
5. Click Save

Update Company-Related Accounts

You must update the company-related accounts for SmartCloud Control Desk.

Chapter 12. Post installation tasks 207

 About this task

To update the company-related accounts, complete the following steps:

Procedure
1. Open the Financials > Chart of Accounts application.
2. From the action menu, select Company-Related Accounts.
3. On the dialog click New Row.
4. Select company type 'C'.
5. Set the RBNI Account, AP Suspense Account, and AP Control Account to the
components you created.
6. Click OK.
7. From the action menu, select Update Database.
8. Click OK.

Create default insert site

You must create a default insert site for SmartCloud Control Desk.

About this task

To create a default insert site, complete the following steps.

If you encounter an error message that indicates that the record is being updated
by another user, log out as maxadmin and then log back in.

Procedure
1. Open the Security > Users application.
2. Search for maxadmin and then select it to open the record for maxadmin.
3. Enter the site you created earlier in the Default Insert Site field. For example,
B901.
4. Enter the site you created earlier in the Storeroom Site for Self-Service
Requisitions field. For example, B901.
5. Click Save.

Create worktypes
You must create worktypes for SmartCloud Control Desk.

About this task

To create a worktype, complete the following steps.

Procedure
1. Open the Administration > Organizations application.
2. Search for the organization you created. For example, ENGLENA.
3. Click the name of the organization to open the record for that organization.
4. Select Work Order Options > Work Type from the Select Action menu.
5. Click New Row.
6. Select PMCFGWO as the Work Order class.
7. Set the Work Type as AR.
8. Set Start Status as INPRG.

208 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 9. Set Complete Status as COMP.
10. Click New Row.
11. Select PMCFGWO as the Work Order class.
12. Set the Work Type as UR.
13. Set Start Status as INPRG.
14. Set Complete Status as COMP.
15. Click OK.
16. Click Save.
17. Restart the MXServer application server.

Create a classification structure for IT assets

Before you can implement IT asset management, you need to define a classification
structure for IT assets.

About this task

You can use the Classifications application to set up a nested, hierarchical structure
in which to classify information about your company's assets. This structure lets
you group assets with similar or common characteristics into categories or classes.
You can use the classification to retrieve instances of assets that belong to the class.
For example, you can specify that the class computers has the following subclasses:
notebooks, servers, desktops. If you want to analyze or review data about all
notebooks in your enterprise, you can search for all assets classified as notebooks
and retrieve instances of notebooks.

Best practices content for creating classifications is provided in the Open Process
Automation Library.

The steps for creating classifications follow.

Procedure
1. On the navigation bar in SmartCloud Control Desk, open the Administration >
Classifications application.
2. In the Classifications application, create classifications as needed. For
instructions about creating classifications and other information related to
classifications, see the integrated online help for the Classifications application
in the SmartCloud Control Desk user interface.

What to do next

After you create an IT asset classification structure, specify the top-level IT asset
classification and the top-level software classification in the Organizations
application.

Specify a top-level class for IT assets and software

To distinguish IT assets from other types of assets, specify a top-level class for IT
assets. Any asset that belongs to the hierarchy of the top-level IT asset class is an
IT asset. Also, define a top-level class for software.

Chapter 12. Post installation tasks 209

 Before you begin

Before you can specify top-level classifications for IT assets and software, create a
classification structure for IT assets and software in the Classifications application.

About this task

The class structure ID that is displayed in the System Settings window is a value
stored in the database. If the classifications structure changes such that the
top-level IT asset class no longer exists at the same place in the hierarchy, the IT
Asset Class Structure ID field will remain populated, but the IT Asset Top-Level
Class field will be blank or show the wrong class. Consequently, if changes are
made to the database, and the classification is moved within the classification
structure, or deleted and re-added, repeat this procedure to update the class
structure ID.

Procedure
1. Open the Administration > Organizations application.
2. From the Select Action menu in the Organizations application, select System
Settings.
3. To specify the top-level IT asset, complete the following steps:
a. In the IT Options section in the Systems Settings window, in the IT Asset
Top-Level Class field, click the Detail Menu and select Classify. If
necessary, you can select Clear Classification to clear the value displayed
and then click Classify.
b. In the Classify window, select the top-level asset class for IT assets by
clicking the blue square to the left of the classification name. The
application closes the Classify dialog box and populates the IT Asset
Top-Level Class field.
4. To specify the top-level software classification, complete the following steps:
a. In the IT Options section in the Systems Settings window, in the IT
Software Top-Level Class field, click the Detail Menu and select Classify.
b. In the Classify window, select the top-level asset class for IT assets by
clicking the blue square to the left of the classification name. The
application closes the Classify dialog box and populates the IT Software
Top-Level Class field.
5. Click OK to save the settings and close the dialog box.

Signing out and signing in

When you change a security group that includes your user ID, you must sign out
and sign in to see the changes. For example, even though you have granted a
group permission to create start center templates, the actions are not visible until
you sign in again.

Procedure
1. Sign out.
2. Sign in as the same user.

Before working with BIRT reports

Before running any reports, you need to set up manually the
mxe.report.birt.tempfolder in JVM system Properties in the BIRT report engine.

210 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Before you begin

The mxe.report.birt.tempfolder property specifies the location of a temporary

folder on the reporting server for BIRT.

About this task

To configure BIRT, set up JVM System Properties mxe.report.birt.tempfolder.

Procedure
1. Log in to WebSphere Application Server.
2. Go to Servers > Application servers.
3. From the right panel, click the server name where you have deployed
SmartCloud Control Desk.
4. Go to Process Definition under Server Infrastructure.
5. Click Java Virtual Machine under Additional Properties.
6. Add -Dmxe.report.birt.tempfolder=c:\tempReport\BIRT-TEMP to Generic JVM
Argument, and then click Save.
7. Restart the server.

Generating xml request pages

Perform this task after you install SmartCloud Control Desk and before you run
request pages. This procedure needs to be performed for every language that is
enabled on your system.

Before you begin

When multiple languages are enabled in Maximo applications, request pages have
to be generated in each of the enabled languages.

Procedure
1. Log in as a maxadmin user.
2. From the Start menu, go to Administrator > Reporting > Report
Administration.
3. Review all rows in the list view then in the bottom right corner click Generate
Request Page button. Wait a couple of minutes for the process to complete.

Synchronizing users and groups

When you select application server security, the scheduled synchronization of users
and groups that occurs between LDAP repositories and SmartCloud Control Desk
is governed by the federated repositories.

About this task

LDAP repositories managed by IBM WebSphere Application Server Network

Deployment through Virtual Member Manager are synchronized through the
VMMSYNC cron task.

To configure the synchronization schedule between LDAP repositories and

SmartCloud Control Desk, complete the following steps:

Chapter 12. Post installation tasks 211

 Procedure
1. Open a web browser and point to http://host name:port/maximo.
2. Log in to SmartCloud Control Desk using the maxadmin user ID.
3. From the SmartCloud Control Desk interface, open the System Configuration >
Platform Configuration > Cron Task Setup application.
4. Search for the appropriate cron task in the Cron Task field and configure it.
5. Set the task to active.

What to do next

By default, the cron task performs its task every 5 minutes. Change the Schedule
field of the cron task if you want to change the interval.

Understanding and configuring security

You must configure security to ensure that only authorized users can log on to
SmartCloud Control Desk. You must also ensure that the appropriate users have
access to their applications and configuration items.

The Security information contained in the SmartCloud Control Desk information

center provides an overview of the following information:
v How security is implemented.
v The steps you perform to configure security.

212 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Chapter 13. Middleware clean up scripts
Middleware clean up scripts are available to remove middleware components and
objects installed and created by the middleware installation program.

Middleware clean up scripts are provided to clean up components that were

installed on a system by the middleware installation program. These scripts can be
used after experiencing a middleware installation program failure, as well as
successful install. These scripts work with the middleware installation program
uninstall feature and are capable of removing one or more middleware installation
components. These components include middleware installed, the workspace,
installation directories, and users created by the middleware installation program.

Using the middleware cleanup scripts

Middleware clean up scripts can be used to remove all artifacts and components
installed on a system by the middleware installation program.

About this task

When using the middleware cleanup scripts, you are prompted to confirm that you
want to remove the component specified. A timestamped log file is created in the
working directory for each action. If the script detects that the installation of a
component experienced an error, you might have to uninstall that product
manually by using the uninstallation program provided with that program.
Table 25. Middleware clean up script parameters
Parameter Description
-default This is the default option for cleaning up
objects created by the middleware
installation program. This option removes
any middleware that was installed, the
workspace, and the deployment engine.

This option does not remove users and

groups created by the middleware
installation program.
-workspace This option reads the middleware
installation program workspace. The
deployment plan contained in the workspace
serves as a roadmap for the clean up script.
-all This option removes all components and
objects from the system that were installed
and created by the middleware installation
program.

This option also removes middleware users

and groups. This is true for users and
groups created by the middleware
installation program and also users and
groups created manually that were used for
configuration during use of the middleware
installation program.

© Copyright IBM Corp. 2012 213

 Table 25. Middleware clean up script parameters (continued)
Parameter Description
-mw This option refers to the middleware
installation program workspace for objects
to remove.

You must provide extra confirmations to

remove users, groups, and DB2 instances.
-db2 This option removes DB2. All DB2 instances
are dropped, the DB2 server is stopped, DB2
is uninstalled, and the DB2 installation
directories are removed.
-itds This option removes IBM Tivoli Directory
Server. All IBM Tivoli Directory Server
instances are dropped, the IBM Tivoli
Directory Server server is stopped, IBM
Tivoli Directory Server is uninstalled, and
the IBM Tivoli Directory Server installation
directories are removed.
-was This option removes WebSphere Application
Server. All WebSphere Application Server
instances are dropped, the WebSphere
Application Server server is stopped,
WebSphere Application Server is uninstalled,
and the WebSphere Application Server
installation directories are removed.

This option also removes IBM HTTP Server

and the WebSphere Application Server
update installer.
-deMWI This option removes the deployment engine.
If there are entries in the deployment engine
registry that were not deployed by the
middleware installation program, you are
warned and asked to confirm that you still
want to remove the deployment engine.

Once the deployment engine has been

removed, you are given the option to
remove the workspace.
-users This option removes users and groups
created by the middleware installation
program. It removes the default users
created by the program and also prompts
you to enter additional user and group
names associated with the middleware
installation that you want removed.
-prop This option allows you to use the
mwi.properties file to supply input to the
clean up scripts.
-f This option allows you to skip confirmation
by confirming all prompts y or n.

Procedure
1. From the product installation image, change directory to the
MWICleanupScripts\operating_system directory.

214 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

2. Start the clean up script and provide input parameters:
v Windows
mwiclean.bat
v Linux and UNIX
mwiClean.sh
For example:
mwiclean.bat -deMWI
3. Type y or n when prompted for confirmation.
4. When prompted, reboot the system. Rebooting the system removes the
temporary entries which can remain after the cleanup procedure has completed.

Chapter 13. Middleware clean up scripts 215

216 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Chapter 14. Uninstalling the product
Uninstalling SmartCloud Control Desk 7.5.1 is dependant upon how it was
deployed.

The procedures and instructions provided here are based upon a scenario in which
the SmartCloud Control Desk installation program has experienced an error or
failure.

SmartCloud Control Desk uninstallation is a comprehensive procedure and does

not support partial removal of individual components or process managers,
including process managers deployed by other products. Process managers of
previously deployed products are also removed when you uninstall SmartCloud
Control Desk.

The SmartCloud Control Desk uninstallation program can only be run once. If
there are errors, messages are generated that indicate conditions that you must
resolve manually before attempting a reinstall. Resolution includes manually
removing files from the administrative workstation.

SmartCloud Control Desk can only be uninstalled using the SmartCloud Control
Desk uninstallation program as directed. Do not use other methods to attempt to
uninstall SmartCloud Control Desk, such as using the Add/Remove Programs
panel.

The uninstall procedure you follow depends on the type of SmartCloud Control
Desk deployment you are uninstalling. For uninstallation purposes, SmartCloud
Control Desk deployments falls into one of the following categories:
Fully-automated configuration
In this scenario, you selected the option to allow the SmartCloud Control
Desk installation program to automatically configure middleware during
deployment.
Manual configuration
In this scenario, you selected the option to manually configure middleware.
You did not allow the SmartCloud Control Desk installation program to
automatically configure middleware during deployment.

After the SmartCloud Control Desk uninstall process is complete, you can reinstall
SmartCloud Control Desk by restarting the SmartCloud Control Desk installation
program.
“Uninstalling an automatically configured deployment”
Uninstalling a SmartCloud Control Desk deployment that was deployed using
the automatic middleware configuration options is an automated process.
“Uninstalling a manually configured deployment” on page 219
Uninstalling a SmartCloud Control Desk deployment that was deployed with
middleware that you configured manually includes additional manual tasks.

Uninstalling an automatically configured deployment

Uninstalling a SmartCloud Control Desk deployment that was deployed using the
automatic middleware configuration options is an automated process.

© Copyright IBM Corp. 2012 217

 Deployments consisting of automatic middleware configuration can be uninstalled
using automated methods.

Running the product uninstallation program for automatically

configured middleware
Running the SmartCloud Control Desk uninstallation program reverts the
administrative system and middleware servers back to their previous state.

Before you begin

Ensure that all applicable services are running and all middleware servers are
accessible.

The SmartCloud Control Desk uninstallation program must be able to access the
database used with SmartCloud Control Desk to fetch installation properties and
configuration data. If the uninstallation program cannot access an unavailable,
corrupted, or otherwise inaccessible database, it removes files from the
administrative workstation. It then informs you that some manual recovery might
be required before another SmartCloud Control Desk installation can be successful.

The uninstallation program uses values entered during the initial installation
during uninstallation. If credentials used to access the database and J2EE server are
still valid, you are not prompted to enter them again. If the uninstallation program
is unable to validate these credentials you are prompted to supply the updated
information. The uninstallation program would not be able to validate credentials
if you updated passwords since the original installation.

Procedure
1. To run the SmartCloud Control Desk uninstallation program, from the
administrative workstation, open a command prompt and issue the following
command:
v Windows
install_home\_uninstall\uninstall.bat
v UNIX
install_home\_uninstall\uninstall.sh
2. From the application server information panel, enter the following information
and then click Next.
Remote user ID
Enter a user ID in order to access the system hosting the application
server. The remote user ID must be able to access the server using the
remote access protocol enabled on that system.
Remote password
Enter a password for the remote user ID.
User ID
Enter the password for the application server administrator.
Password
Enter the password for the application server administrator user ID.
3. From the database administration panel, enter the information requested, and
then click Next. For DB2, enter the following information:
Remote user ID
Enter a user ID in order to access the system that is hosting the

218 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 database. The remote user ID must be able to access the server using
the remote access protocol enabled on that system.
Remote password
Enter a password for the remote user ID.
Instance administrator user ID
Enter the database instance administrator user ID that you entered
during the installation.
Instance administrator password
Enter the password for the database instance administrator user ID.

For Oracle, supply credentials for the Administrator user ID and the Oracle
software owner ID. For Microsoft SQL Server, supply the Microsoft SQL Server
administrator user ID and password.
4. Review the components that are listed in the uninstallation summary panel,
and then click Uninstall.
5. After the uninstallation process completes, specify whether you want to restart
the computer now or later, and click Done to exit the program.
6. Remove the SmartCloud Control Desk installation directory, for example,
c:\ibm\smp. You must manually remove this directory before you proceed to
the reinstallation process.

Uninstalling a manually configured deployment

Uninstalling a SmartCloud Control Desk deployment that was deployed with
middleware that you configured manually includes additional manual tasks.

Uninstalling a manually configured SmartCloud Control Desk deployment consists

of two tasks:
v Running the SmartCloud Control Desk uninstallation program
v Manually dropping and recreating the database you intend to use with the
reinstall process

Running the product uninstall program for manually

configured middleware
Running the SmartCloud Control Desk uninstall program reverts the
administrative system and middleware servers back to a state where you can rerun
the SmartCloud Control Desk installation program.

Before you begin

Ensure that all applicable services are running and all middleware servers are
accessible.

The SmartCloud Control Desk uninstall program must be able to access the
database used with SmartCloud Control Desk to fetch installation properties and
configuration data. If the uninstall program cannot access an unavailable,
corrupted, or otherwise inaccessible database, it removes files from the
administrative workstation. It then informs you that some manual recovery might
be required before another SmartCloud Control Desk installation can be successful.

The uninstall program uses values entered during the initial installation during
uninstall. If credentials used to access the database and J2EE server are still valid,

Chapter 14. Uninstalling the product 219

 you are not prompted to enter them again. If the uninstall program is unable to
validate these credentials you are prompted to supply the updated information.
The uninstall program would not be able to validate credentials if you updated
passwords since the original installation.

Procedure
1. To run the SmartCloud Control Desk uninstall program, from the
administrative workstation, open a command prompt and issue the following
command:
Windows
install_home\_uninstall\uninstall.bat
UNIX
install_home\_uninstall\uninstall.sh
2. From the Introduction panel, read the introductory information and then click
Next.
3. From the application server information panel, enter the following information
and then click Next.
User ID
Enter the password for the application server administrator.
Password
Enter the password for the application server administrator user ID.
4. Review the components that are listed in the uninstall summary panel, and
then click Uninstall.
5. After the uninstall process has completed, click Done to exit the program.
6. Remove the SmartCloud Control Desk installation directory, for example,
c:\ibm\smp. You must manually remove this directory before you proceed to
the reinstallation process.

What to do next

You can now proceed with recovery of your manually configured database.

Database configuration recovery

Database objects created before running the SmartCloud Control Desk installation
program must be deleted after a failed installation before the SmartCloud Control
Desk installation program is run again.

Before rerunning the SmartCloud Control Desk installation program, you must
drop the SmartCloud Control Desk database and recreate it.

Note: Alternatively, if you want to preserve the instance, you can examine the
database for objects (tables, views, and procedures, for example) that were created
by the maxadmin user. You can then drop those objects individually.

Restoring the DB2 database server

In order to rerun the SmartCloud Control Desk installation program, you must first
restore the DB2 database server to the same state as before SmartCloud Control
Desk was installed.

220 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Before you begin

Ensure that the MXServer application server on the IBM WebSphere Application
Server Network Deployment is stopped before you drop the database.

About this task

To restore the DB2 database server to its previous state, drop the SmartCloud
Control Desk database that you manually created. You then recreate it before you
rerun the SmartCloud Control Desk installation program.

To restore the SmartCloud Control Desk database, complete the following steps:

Procedure
1. Log on to the system that hosts the DB2 server.
2. Start a DB2 command session or run db2cmd from the command prompt.
3. First list and then force all applications connected to the database to close using
the following commands:
a. To list applications, type this command:
db2 list applications

You might see output like the following sample output:

Table 26. DB2 list command sample output
Application Appl.
Auth Id Name Handle Application ID DB Name # of Agents
CTGINST1 db2taskd 507 *LOCAL.DB2.071113150237 MAXDB75 1
CTGINST1 db2stmm 506 *LOCAL.DB2.071113150236 MAXDB75 1
CTGINST1 db2bp 504 *LOCAL.ctginst1.071113150234 MAXDB75 1

b. If any connections exist, close the connect application using a command like
the following sample command:
db2 force application ’( 507,506,504 )’
4. Drop the SmartCloud Control Desk database (MAXDB75, by default):
db2 drop database MAXDB75
5. Manually recreate the maxdb75 database.
“Manually configuring DB2 9.x” on page 74
This section contains instructions for manually configuring DB2 9.x servers for
use by SmartCloud Control Desk.

Restoring the Oracle database

In order to rerun the SmartCloud Control Desk installation program, you must first
restore the Oracle database server to the same state as before SmartCloud Control
Desk was installed.

Before you begin

The MXServer application server must be stopped before deleting the database.

About this task

Drop the SmartCloud Control Desk database schema user to restore the Oracle
database server to its previous state. This task must be completed before you rerun
the SmartCloud Control Desk installation program.

Chapter 14. Uninstalling the product 221

 To restore the SmartCloud Control Desk database, complete the following steps:

Procedure
1. Log in to the Oracle database server as the Oracle software owner.
2. Log in to the Oracle instance with SQLPlus as a DBA user: The Oracle SID for
a clean installation is ctginst1. If you are using an existing Oracle instance with
SmartCloud Control Desk, use the Oracle SID associated with the existing
instance.
AIX, Linux, HP-UX, Solaris
a. Set the environment variable from the command line:
ORACLE_SID=<your sid>
export ORACLE_SID
b. Start SQLPlus from the command line:
sqlplus /nolog
c. Login to SQLPlus as a DBA user:
connect sys/<sys password> as sysdba
Windows
a. Set the environment variable from the command line:
set ORACLE_SID=<your sid>
b. Start SQLPlus from the command line:
sqlplus /nolog
c. Login to SQLPlus as a DBA user:
connect sys/<sys password> as sysdba
3. Delete the SmartCloud Control Desk database user (maximo, by default) using
an SQL command like the following sample command:
drop user maximo cascade;

Do not disconnect from the database. If you receive an error that you cannot
drop a currently connected user, issue the following commands and use the
SQL drop command:
shutdown immediate;
startup;
4. Manually recreate the database.
“Manually configuring Oracle 11g” on page 76
Use the following instructions to manually configure Oracle 11g for use with
SmartCloud Control Desk.
“Manually configuring Oracle 10g” on page 78
Oracle 10g can be manually configured for use with SmartCloud Control Desk.

Restoring the Microsoft SQL Server database

In order to rerun the SmartCloud Control Desk installation program, you must first
restore the Microsoft SQL Server database server to the same state as before
SmartCloud Control Desk was installed.

Before you begin

Stop the MXServer application server before you delete the database.

222 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 About this task

To restore the Microsoft SQL Server database server to its previous state, drop the
SmartCloud Control Desk database that you manually created. You then recreate it
before you rerun the SmartCloud Control Desk installation program.

To restore the SmartCloud Control Desk database, complete the following steps:

Procedure
1. Open the Microsoft SQL Server Management Studio.
2. Log in to the instance of Microsoft SQL Server that is used by SmartCloud
Control Desk installation using the sa user ID, and then click Connect.
3. Expand the instance tree down to the databases node. Using the right mouse
button, click the database name you created during installation (MAXDB75 for
example). Click Delete to delete the database.
4. In the Delete Object window, select Delete backup and restore history
information for databases and Close existing connections, and then click OK.
5. Manually recreate the maxdb75 database.
“Manually configuring Microsoft SQL Server” on page 80
You can manually configure Microsoft SQL Server for use with SmartCloud
Control Desk.

Uninstalling the product without the uninstallation program

Uninstalling the product when a failed installation does not produce an
uninstallation program.

If the installation program has experienced a failure that causes it to not produce
the product uninstallation program, you must perform alternative uninstallation
tasks.

If uninstallation program was not produced, you must complete one of the
following tasks in order to uninstall the product:
v Run the uninstallation recovery tool described in “Uninstall program recovery
tool.”
v Complete the uninstallation manually using the following steps:
1. “Recovering WebSphere Application Server configuration” on page 227.
2. Recover the database as described in “Database configuration recovery” on
page 220.
3. Manually remove files from the system as described in “Removing files from
the system” on page 230.

Uninstall program recovery tool

The uninstall program recovery tool is used to automatically uninstall SmartCloud
Control Desk when the installation program fails to produce the product
uninstallation program.

The uninstall program recovery tool is run on the administrative workstation

following a failed installation. This tool performs the same functions of the
SmartCloud Control Desk uninstallation program. This tool is intended to restore
the administrative workstation and middleware servers so the SmartCloud Control
Desk installation can be run again. The uninstall program recovery tool is
available on the product media and also from the product support site.

Chapter 14. Uninstalling the product 223

 Using the uninstallation program recovery tool
Use the uninstallation program recovery tool to restore the administrative
workstation and middleware servers so the SmartCloud Control Desk installation
can be run again.

About this task

The uninstallation program recovery tool is a command line tool that prompts you
for input. This information is used as input for a collection of scripts that are run
serially. These scripts perform the steps necessary to restore the administrative
workstation and middleware servers so the installation program can be rerun. If
you choose to skip any of the uninstallation program recovery tool tasks, you can
run the tool at a later time to perform that task.

The uninstallation program recovery tool must be run on each system that hosts a
component of the SmartCloud Control Desk deployment. For example, to remove
the database associated with the deployment, you must run the program on the
server hosting the database.

Procedure
1. Open a command prompt on the administrative workstation and start the
uninstallation program recovery tool.
v For Windows, use cleanupPAE.bat.
v For UNIX, use cleanupPAE.sh.
2. Provide input for the scripts responsible for recovering the IBM WebSphere
Application Server Network Deployment server used in the deployment.
a. Supply information for the IBM WebSphere Application Server Network
Deployment used in the deployment.
1) At the Would you like to cleanup WebSphere Application Server?
[y/n]: prompt, select y.
2) At the Would you like to enter a custom install directory for
WebSphere? [y/n]: prompt, select n if you installed IBM WebSphere
Application Server Network Deployment in the default directory.
If you installed IBM WebSphere Application Server Network
Deployment in a custom directory, you are prompted to enter that
directory.
3) At the Enter your WebSphere admin user ID: prompt, enter the user ID
of the IBM WebSphere Application Server Network Deployment
administrator.
4) At the Enter your WebSphere admin password: prompt, enter the
password of the IBM WebSphere Application Server Network
Deployment administrator user ID.
b. Remove SmartCloud Control Desk applications from IBM WebSphere
Application Server Network Deployment.
1) At the Would you like to remove the MAXIMO and MAXIMOIEHS
applications? [y/n]: prompt, select y.
This step indicates that you want to remove both the Maximo and
Maximo help applications.
2) At the Enter the name of the node where MAXIMO and MAXIMOIEHS are
located: prompt, enter the node associated with the Maximo and
Maximo help applications.

224 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 3) At the Enter the name of the server where MAXIMO and MAXIMOIEHS
are located: prompt, enter the name of the web server hosting the
Maximo and Maximo help applications.
4) At the Are you sure you want to remove the MAXIMO and MAXIMOIEHS
applications? [y/n]: prompt, select y.
c. Remove JMS message queue objects.
1) At the Would you like to remove the JMS resources? [y/n]: prompt,
select y.
2) At the Are you sure you would like to remove the JMS resources?
[y/n]: prompt, select y.
d. Remove Service Integration Bus objects.
1) At the Would you like to remove the Service Integration Bus and
SIB destinations? [y/n]? prompt, select y.
2) At the Enter the name of the node where MAXIMO was installed:
prompt, enter the node associated with the Maximo application.
3) At the Enter the name of the server where MAXIMO was installed:
prompt, enter the name of the web server hosting the Maximo
application.
4) At the Are you sure you would like to remove the Service
Integration Bus and SIB destinations? [y/n]: prompt, select y.
e. Remove IBM WebSphere Application Server Network Deployment
properties.
1) At the Would you like to remove the Deployment Manager custom
properties? [y/n]: prompt, select y.
2) At the Are you sure you would like to remove the Deployment
Manager custom properties? [y/n]: prompt, select y.
f. Remove IBM WebSphere Application Server Network Deployment
environment variables.
1) At the Would you like to remove the WebSphere Application Server
environment variables? [y/n]: prompt, select y.
2) At the Are you sure you would like to remove the WebSphere
Application Server environment variables? [y/n]: prompt, select y.
g. Remove the IBM WebSphere Application Server Network Deployment
virtual host.
1) At the Would you like to remove the Maximo Virtual Host? [y/n]:
prompt, select y.
2) At the Are you sure you would like to remove the Maximo Virtual
Host? [y/n]: prompt, select y.
h. Remove the IBM WebSphere Application Server Network Deployment Java
Authentication and Authorization Service.
1) At the Would you like to remove the Java Authentication and
Authorization Service (JAAS) Alias? [y/n]: prompt, select y.
2) At the Are you sure you would like to remove the JAAS Alias?
[y/n]: prompt, select y.
i. Remove IBM WebSphere Application Server Network Deployment JDBC
data sources and providers.
1) At the Would you like to remove the JDBC data sources and
providers? [y/n]: prompt, select y.
2) At the Are you sure you would like to remove the JDBC data sources
and providers? [y/n]: prompt, select y.

Chapter 14. Uninstalling the product 225

 j. Remove IBM WebSphere Application Server Network Deployment
application server custom properties.
1) At the Would you like to remove the application server custom
properties? [y/n]: prompt, select y.
2) At the Are you sure you would like to remove the application server
custom properties?[y/n]: prompt, select y.
k. Remove users and groups.
1) At the Would you like to remove the Maximo users and groups?
[y/n]: prompt, select y.
2) At the Enter the Maximo administration user(Default = maxadmin):
prompt, enter the user ID.
3) At the Enter the Maximo system registration user(Default =
maxreg): prompt, enter the user ID.
4) At the Enter the Maximo system integration user(Default =
mxintadm): prompt, enter the user ID.
5) At the Are you sure you would like to remove the Maximo users and
groups? [y/n]: prompt, select y.
3. Provide input for the scripts responsible for recovering the database server
used in the deployment.
v DB2
a. Supply information for the database used in the deployment.
1) At the Would you like to cleanup the database? [y/n]: prompt,
select y.
2) At the Which database type would you like to cleanup? [DB2,
Oracle, SQLServer (BAT only)]: prompt, select DB2.
3) At the Enter database name: prompt, enter the name of the database
used in the deployment.
4) At the Enter database instance administrator user ID: prompt,
enter the database instance administrator user ID.
5) At the Enter database instance administrator password: prompt,
enter the password for the database instance administrator user ID.
6) At the Enter database instance name: prompt, enter the name of the
database instance.
b. Confirm you want to drop the database.
1) At the Are you sure you would like to drop the <database name>
database? [y/n]: prompt, select y.
2) Verify the database was dropped.
v Oracle
a. Supply information for the database used in the deployment.
1) At the Would you like to cleanup the database? [y/n]: prompt,
select y.
2) At the Which database type would you like to cleanup? [DB2,
Oracle, SQLServer (BAT only)]: prompt, select Oracle.
3) At the Enter the SID of the Oracle instance: prompt, enter the
Oracle System ID of the Oracle instance used in the deployment.
4) At the Enter the Oracle install directory: prompt, enter the
Oracle installation path.
b. Supply user information.
1) At the Enter the SYSDBA user: prompt, enter the SYSDBA user ID.

226 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 2) At the Enter the SYSDBA password: prompt, enter the password for
the SYSDBA user ID.
3) At the Enter database user: prompt, enter the Oracle database user
ID.
4) At the Would you like to delete the <database user name>
database user? [y/n]: prompt, select y.
c. Delete the Oracle table spaces and the Oracle instance.
1) At the Would you like to delete the 'maxdata', 'maxtemp', and
'maxindex' tablespaces? [y/n]: prompt, select y.
2) At the Would you like to delete the oracle instance? [y/n]:
prompt, select y.
v Microsoft SQL Server
a. At the Enter database name: prompt, enter the name of the database
used in the deployment.
b. At the Are you sure you would like to drop the <database name>
database? [y/n]: prompt, select y.
4. Provide input for the scripts responsible for recovering the administrative
workstation used in the deployment.
a. At the Would you like to cleanup the administrator workstation?
[y/n]: prompt, select y.
b. At the Would you like to enter a custom install directory? [y/n]:
prompt, select n if you installed SmartCloud Control Desk in the default
directory. If you installed SmartCloud Control Desk in a custom directory,
you are prompted to enter that directory.
c. At the Are you sure you would like to cleanup the following directory:
<install directory>? [y/n]: prompt, select y.

Manual uninstallation
Manual uninstallation steps are sometimes necessary to uninstall SmartCloud
Control Desk when the installation program fails to produce the product
uninstallation program.

Manual uninstallation steps are performed following a failed installation. These

steps are used to remove the same objects as the SmartCloud Control Desk
uninstallation program. These steps are intended to restore the administrative
workstation and middleware servers so the SmartCloud Control Desk installation
can be run again.

Recovering WebSphere Application Server configuration

Follow these instructions to delete WebSphere Application Server objects that are
created or changed by the installation program and restore WebSphere Application
Server to the same state as when first installed by the middleware installation
program.

About this task

As the result of a failed installation, it is possible that not all of the objects listed in
these instructions were created or configured. Steps apply only to relevant objects
that were created by the installation process. In addition, if you have manually
created or configured WebSphere Application Server objects, you must take your
own actions to ensure that they remain intact before attempting this recovery
process.

Chapter 14. Uninstalling the product 227

 Assuming that the middleware installation failure caused WebSphere Application
Server to be in a nonworking state, ensure that the deployment manager and the
node are running.

When you complete the WebSphere Application Server recovery process, you can
proceed to the next step of the uninstall process which involves database recovery
steps.

Procedure
1. Using the WebSphere Application Server administrator ID, log in to the IBM
Console for WebSphere Application Server. https://<dmgr
host>:9043/ibm/console.
2. Delete the installed Enterprise Applications:
a. Expand Applications.
b. Select Enterprise Applications.
c. Select MAXIMO and MAXIMOIEHS.
d. Click Stop.
e. If not already selected, reselect MAXIMO and MAXIMOIEHS.
f. Click Uninstall.
g. Click OK.
3. Delete JMS resources:
a. Delete Activation Specs
1) Expand Resources.
2) Expand JMS.
3) Select Activation specifications.
4) Select intjmsact.
5) Click Delete.
b. Delete Queues
1) Expand Resources.
2) Expand JMS.
3) Select Queues.
4) Select CQIN, SQIN and SQOUT.
5) Click Delete.
c. Delete Connection Factories
1) Expand Resources.
2) Expand JMS.
3) Select Connection factories.
4) Select intjmsconfact.
5) Click Delete.
4. Delete the Service Integration Bus intjmsbus.
a. Expand the Service integration link.
b. Click Buses.
c. Select the intjmsbus check box.
d. Click Delete.
5. Remove the CTG_MAXIMO_SERVLET_URL custom property from the
Deployment Manager:
a. Expand the System administration link.

228 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 b. Click Deployment manager.
c. Select the Configuration tab
d. Click Java and Process Management.
e. Click Process Definition.
f. Click Java Virtual Machine (JVM).
g. Click Custom Properties.
h. Select the CTG_MAXIMO_SERVLET_URL check box.
i. Click Delete.
6. Delete the CTG_MAXIMO_SERVLET_URL and ctg_JDBC_DRIVER_PATH
WebSphere Application Server Environment Variables:
a. Expand the Environment link.
b. Select WebSphere Variables.
c. Select Cell=ctgCell01 from the Scope menu.
d. Click Apply. If you have Scope set for WebSphere Application Server
variables, you are not required to click Apply to apply changes.
e. Select the CTG_MAXIMO_SERVLET_URL and
ctg_JDBC_DRIVER_PATH check boxes.
f. Click Delete.
7. Delete the Virtual Host maximo_host:
a. Expand the Environment link.
b. Select Virtual Hosts.
c. Select maximo_host.
d. Click Delete.
8. Delete the existing Java Authentication and Authorization Service (JAAS) Alias
(maxJaasAlias):
a. Expand the Security link.
b. Select Secure administration, applications, and infrastructure.
c. Select the Configuration tab.
d. Select Java Authentication and Authorization Service.
e. Select J2C authentication data.
f. Select maxJaasAlias.
g. Click Delete.
9. Delete created JDBC data sources:
Delete V 4.0 data sources:
a. Expand Resources.
b. Expand JDBC.
c. Select Data sources (WebSphere Application Server V4).
d. Select DB2 Universal JDBC Driver - 4.0 XA Data Source.
e. Click Delete.
Delete data sources:
a. Expand Resources.
b. Expand JDBC.
c. Select Data sources.
d. Select DB2 Universal JDBC Driver XA Data Source and intjmsds.
e. Click Delete.

Chapter 14. Uninstalling the product 229

 Delete JDBC providers:
a. Expand Resources.
b. Expand JDBC.
c. Select JDBC providers.
d. Select maxJdbcProvider.
e. Click Delete.
10. Remove added properties associated with Application server MXServer:
a. Expand Servers.
b. Select Application servers.
c. Select MXServer.
d. Select the Configuration tab.
e. Expand Java and Process Management.
f. Select Process Definition
g. Select Java Virtual Machine.
h. Select Custom Properties.
i. Select com.collation.home and sun.rmi.dgc.ackTimeout.
j. Click Delete.
11. Delete Maximo users:
a. Expand Users and Groups.
b. Click Manage Users.
c. Click Search and search by user ID.
d. Locate and select the maxadmin, maxreq and mxintadm user IDs, and
then click Delete.
12. From the message dialog box, click Save to save all configuration changes.
Ensure that you are synchronizing all changes with nodes.
13. Remove the IBM DB2 JDBC driver JAR files from the file system by deleting
the db2jcc.jar and db2jcc_license_cu.jar files from the ctgMX\lib folder
which is in the WebSphere Application Server home directory. For example,
C:\Program Files\IBM\WebSphere\AppServer.
“Database configuration recovery” on page 220
Database objects created before running the SmartCloud Control Desk
installation program must be deleted after a failed installation before the
SmartCloud Control Desk installation program is run again.

Removing files from the system

If an uninstallation program is unavailable due to failed installation, product files
must be manually removed from the system.

About this task

Remove files from the system by completing the following steps:

Procedure
1. Ensure that you are logged in to the system with the same user ID used to start
the product installation program.
2. Manually delete the SmartCloud Control Desk home directory. For Windows,
the default location of this directory is C:\IBM\SMP. For UNIX systems, this
directory is /opt/IBM/SMP.

230 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Chapter 15. Starting and stopping middleware
Use this information to start and stop middleware when necessary.

There might be occasions when you have to stop or restart middleware.

Restarting middleware on Windows

This procedure describes how to restart middleware on Windows, if you must
restart any middleware services.

About this task

To properly start middleware products on Windows, use the following scripts in

the order in which they are listed:

Procedure
1. Log in as a user with Administrative permissions.
2. If you installed DB2, start ctginst1.
a. Click Start, and select Run.
b. Type services.msc, and click OK.
c. Select DB2 - DB2COPY1 - CTGINST1-0, and click Start the service.
Alternatively, you can use the db2start command from a command line to start
CTGINST1.
3. If you installed IBM Tivoli Directory Server, start the IBM Tivoli Directory
Server Admin Daemon.
a. Click Start, and select Run.
b. Type services.msc, and click OK.
c. Select IBM Tivoli Directory Admin Daemon V6.3 - idsccmdb, and click Start
the service.
Alternatively, you can use the following command from the command line to
start the IBM Tivoli Directory Server admin daemon:
idsdiradm -I idsccmdb
4. If you installed IBM Tivoli Directory Server, start the IBM Tivoli Directory
Server instance.
a. Click Start, and select Run.
b. Type services.msc, and click OK.
c. Select IBM Tivoli Directory Server Instance V6.3 - idsccmdb, and click
Start the service.
Alternatively, you can use the following command to start the IBM Tivoli
Directory Server instance:
idsslapd -I idsccmdb

Important: The IBM Tivoli Directory Server Instance must remain as a manual
startup type. It must be started manually to synchronize correctly with the
database in the context of SmartCloud Control Desk.
5. If you installed WebSphere Application Server, start Domain Manager

© Copyright IBM Corp. 2012 231

 a. Click Start, and select Run.
b. Type services.msc, and click OK.
c. Select IBMWAS70Service - ctgCellManager01, and click Start the service.
Alternatively, you can use the following command from the command line to
start the domain manager:
WAS_HOME\profiles\ctgDmgr01\bin\startManager.bat
6. If you installed WebSphere Application Server, start Node
a. Click Start, and select Run.
b. Type services.msc, and click OK.
c. Select IBMWAS70Service - nodeagent, and click Start the service.
Alternatively, you can use the following command from the command line to
start the node:
WAS_HOME\profiles\ctgAppSvr01\bin\startNode.bat
7. If you installed WebSphere Application Server, start MXServer. If you created a
service for starting the MXServer application server, you can use the Services
control panel to start and stop it. Alternatively, you can use the following
command from the command line to start the application server:
WAS_HOME\profiles\ctgAppSrv01\bin\startServer.bat MXServer
8. If you installed WebSphere Application Server, start IBM HTTP Server and
webserver1.
a. Click Start and select Run.
b. Type services.msc, and click OK.
c. Select IBM HTTP Server 7.0, and click Start the service.
Alternatively, you can type apache from the command line to start the HTTP
Server.

Restarting middleware on UNIX

Middleware services on Linux and AIX platforms occasionally must be restarted,
such as when a reboot occurs. Middleware servers and services must be active
before running the SmartCloud Control Desk installation program.

About this task

To properly start middleware products on UNIX, perform the following steps:

Procedure
1. Log in as root.
2. Start servers by using the following scripts in the order in which they are
listed:
If you installed DB2, start ctginst1 instance
su - ctginst1 -c db2start
If you installed IBM Tivoli Directory Server, start IBM Tivoli Directory
Server Admin Daemon
<ITDS_HOME>/sbin/idsdiradm -I idsccmdb
If you installed IBM Tivoli Directory Server, start IBM Tivoli Directory
Server daemon
<ITDS_HOME>/sbin/idsslapd -I <instancename>

232 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 So this command would look like the following example:
<ITDS_HOME>/sbin/idsslapd -I idsccmdb

Important: The instance of IBM Tivoli Directory Server must remain as

a manual startup type. It must be started manually to synchronize
correctly with the database in the context of SmartCloud Control Desk.
If you installed WebSphere Application Server, start Deployment Manager
<WAS_HOME>/profiles/ctgDmgr01/bin/startManager.sh
If you installed WebSphere Application Server, start Node
<WAS_HOME>/profiles/ctgAppSrv01/bin/startNode.sh
If you installed WebSphere Application Server, start webserver1
<WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.sh webserver1
-username <username> -password <password>
If you installed WebSphere Application Server, start MXServer
<WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.sh MXServer
-username <username> -password <password>
If you installed WebSphere Application Server, start HTTP Server and
webserver1
Linux, Solaris, HP-UX
/opt/IBM/HTTPServer/bin/apachectl start
AIX /usr/IBM/HTTPServer/bin/apachectl start

Stopping middleware on Windows

This procedure describes how to stop the middleware on Windows , if you must
stop any middleware services.

About this task

To properly stop middleware products on Windows, complete the following steps:

Procedure
1. If you installed DB2, stop ctginst1.
a. Click Start, and select Run.
b. Type services.msc, and click OK.
c. Select DB2 - DB2COPY1 - CTGINST1-0, and click Stop the service.
2. If you installed IBM Tivoli Directory Server, stop the IBM Tivoli Directory
Server Admin Daemon.
a. Click Start, and select Run.
b. Type services.msc, and click OK.
c. Select IBM Tivoli Directory Admin Daemon V6.3 - idsccmdb, and click Stop
the service.
3. If you installed IBM Tivoli Directory Server, start the IBM Tivoli Directory
Server instance.
a. Click Start, and select Run.
b. Type services.msc, and click OK.
c. Select IBM Tivoli Directory Server Instance V6.3 - idsccmdb,, and click
Stop the service.

Chapter 15. Starting and stopping middleware 233

 4. If you installed WebSphere Application Server, stop IBM HTTP Server and
webserver1.
a. Click Start and select Run.
b. Type services.msc, and click OK.
c. Select IBM HTTP Server 7.0, and click Stop the service.
5. If you installed WebSphere Application Server, start Domain Manager
a. Click Start, and select Run.
b. Type services.msc, and click OK.
c. Select IBMWAS70Service - ctgCellManager01, and click Stop the service.
6. If you installed WebSphere Application Server, stop servers by using the
following scripts in the order in which they are listed:
Stop Node
<WAS_HOME>\profiles\ctgAppSvr01\bin\stopNode.bat

Note: If this process is configured to run as a service, then stop the

service:
a. Click Start > Services > Control Panel.
b. Click IBM WebSphere Application Server V7.0 - nodeagent.
c. Right click and click Stop.
Stop MXServer
<WAS_HOME>\profiles\ctgAppSrv01\bin\stopServer.bat MXServer
-username <username> -password <password>

Note: Unless you changed the installation locations, the following are the
default values:
<HTTP_SERVER_HOME> is C:\Program Files\IBM\HTTPServer\bin
<WAS_HOME> is C:\Program Files\IBM\WebSphere\AppServer
“Configuring the WebSphere Application Server Network Deployment
application server to run as a Windows service” on page 264
Configuring the WebSphere Application Server Network Deployment to run as
a Windows service can make it more convenient to manage.

Stopping middleware on Linux and AIX

This procedure describes how to stop the middleware on Linux and AIX platforms,
if you must stop any middleware services.

About this task

To properly stop middleware products on Linux and AIX, perform the following
steps:

Procedure
1. Log in as root.
2. If you installed WebSphere Application Server, stop servers by using the
following scripts in the order in which they are listed:
If you installed DB2, stop ctginst1 instance
su - ctginst1 -c db2stop

234 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

If you installed IBM Tivoli Directory Server, stop IBM Tivoli Directory
Server Admin Daemon
<ITDS_HOME>/sbin/idsdiradm -h idsccmdb
If you installed IBM Tivoli Directory Server, stop IBM Tivoli Directory
Server daemon
<ITDS_HOME>/sbin/ibmslapd -I <instancename> -k

Important: The instance of IBM Tivoli Directory Server must remain as

a manual startup type. It must be started manually to synchronize
correctly with the database in the context of SmartCloud Control Desk.
If you installed WebSphere Application Server, stop HTTP Server and
webserver1
Linux, Solaris, HP-UX
/opt/IBM/HTTPServer/bin/apachectl stop
AIX /usr/IBM/HTTPServer/bin/apachectl stop
If you installed WebSphere Application Server, stop Deployment Manager
<WAS_HOME>/profiles/ctgDmgr01/bin/stopManager.sh
If you installed WebSphere Application Server, stop node
<WAS_HOME>/profiles/ctgAppSrv01/bin/stopNode.sh -username
<username> -password <password>
If you installed WebSphere Application Server, stop webserver1
<WAS_HOME>/profiles/ctgAppSrv01/bin/stopServer.sh webserver1
-username <username> -password <password>
f you installed WebSphere Application Server, stop MXServer
<WAS_HOME>/profiles/ctgAppSrv01/bin/stopServer.sh MXServer
-username <username> -password <password>

Chapter 15. Starting and stopping middleware 235

236 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Chapter 16. Process solution package installation methods
Included within SmartCloud Control Desk are common installation programs that
provide you with the ability to manage the software life cycle of SmartCloud
Control Desk process solutions, including functions to query, install, upgrade, and
uninstall process solution packages. These common installation programs are
collectively known as the process solution installation programs.

SmartCloud Control Desk provides a flexible approach for incremental deployment

of service management functionality using separately packaged process solutions.
Process solutions can be partitioned into Process Manager Products and Integration
Modules.

Process solution packages can be installed and deployed using two mechanisms:
Process Solution Installation Wizard
The process solution installation wizard provides you with an interface for
installing process solution packages.
Process Solution Command Line Interface
The process solution command-line interface allows you to install process
solution packages from a command line.

SmartCloud Control Desk must have been deployed, including post-installation

steps, before the installation and deployment of additional process managers.

Software life cycle operations

Process solutions are software components with versions. The process solution
installation programs support various software life cycle operations that can be
applied against process solutions.

The following software life cycle operations are available:

v The Base Install operation installs and deploys a new process solution into your
SmartCloud Control Desk environment.
v The Add Feature and Modify Feature operations add or remove specific features of
a package after the package has been installed.
v Once installed, a process solution can be updated in several ways. An
Incremental Update or Upgrade operation modifies the existing installed process
solution and changes its version. Often a process solution fix pack is applied
using the Incremental Update operation.
v Another operation that can be used to update an installed process solution is the
Apply Fix operation. This operation is used to install individual interim fixes or
patches to a currently installed process solution.
v Some Incremental Updates or Fixes are designed to be able to be removed or
backed off. The Undo operation is used to remove the effects of an Incremental
Update operation and return the process solution to its previous version and
state. The Undo Fix operation removes a currently installed interim fix from a
process solution.
v The Uninstall operation removes a currently installed process solution.

© Copyright IBM Corp. 2012 237

Process solution packages
A process solution package is a self-contained archive file of installation artifacts and
deployment logic that can be deployed using the process solution installation
programs.

Installation artifacts are the files and content that are installed into your
SmartCloud Control Desk environment. These artifacts enable the services
management functionality of the Process Manager Product or Integration Module.
For example, a Process Manager Product provides J2EE application content and
database content.

The deployment logic consists of the actions that are carried out in order to deploy
the process solution into the SmartCloud Control Desk environment. These actions
include building and deploying J2EE applications, running database scripts that
load the process solution content into the database, and adding users and groups
for security. Additionally, optional sample data can be installed.

SmartCloud Control Desk packages are automatically installed when SmartCloud

Control Desk is installed.

Package types
Closely related to the concept of the software life cycle operation is software
package type.

The process solution installation programs are able to process the following
package types:
v A Base Install Package is required to install a new process solution using the Base
Install operation.
v An Incremental Update Package is required when performing an Upgrade
operation.
v A Fix Package is required when applying an interim fix to a process solution.
v A Full Update Package can be used in two separate operations. It can be used to
perform a Base Install operation if no instance of the process solution is
currently installed or it can be used to perform an Upgrade operation on a
currently installed process solution.
v An Aggregation package consist of multiple PSI installable packages that can be
deployed as one package in a single process solution installation client CLI or
interface session.

The process solution installation programs ensure that the appropriate package
type is processed for any given operation.

The Process Solution Command Line Interface issues appropriate messages when
an inappropriate package type is specified for a life cycle operation. For example, a
message would be issued if a Fix Package was specified for a Base Install
operation. You can use the showavail action of the Process Solution Command Line
Interface to determine the package type associated with a process solution
installable package.

The Process Solution Installation Wizard determines the operation to employ based
on the type of the package and the current state of the installed components. For
example, if you select to deploy a Full Update Package, the Process Solution
Installation Wizard performs an Upgrade operation if a suitable base version of the
238 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
 process solution is already installed and a Base Install operation if no suitable base
version is detected. When using the Process Solution Installation Wizard, you can
view the package type for the package you selected on the Package Validation
Results panel.

The following table highlights the supported operations with their required
package types:
Table 27. Operations and package types
Operation Package Type
Base Install Base Install Package or Full Update Package
Incremental Update/Fix Pack Incremental Update Package or Full Update
Package
Apply Interim Fix Fix Package

Aggregation packages
This section contains information about aggregation packages.

A process solution package can be composed from other process solution packages.
This technique allows construction of single offering-level packages that may be
deployed using a single session with the process solution installation programs.
Such a package is known as a process solution aggregate package. The sub
packages that are bundled within a process solution aggregate package are known
as child packages.

Process solution aggregate packages are deployed using the same mechanisms
used to deploy non-aggregate packages. All actions defined within the process
solution command-line interface can be applied to a process solution aggregate
package. Similarly, the process solution installation wizard can be used to base
install, upgrade, and apply fixes to a process solution aggregate package.

Process solution aggregate packages support the same package types (Base Install,
Full Update, Incremental Update, and Fix) and the same life cycle operations as
non-aggregate packages.

Process solution aggregate packages often expose their child packages as selectable
features of the aggregate. You can selectively deploy only the pieces of the
aggregate that you prefer.

A process solution aggregate has a version, unique identifier, and display name
information just like a non-aggregate package. When you use the showinstalled
action of the process solution command-line interface, the output includes
information about the installed parent aggregate package. Out also contains
information about the child packages within that parent aggregate package that
have also been installed.

Determining which process solution installation program to use

The process solution installation programs provided each have unique benefits and
both must be used in the appropriate scenario.

Consider the following facts when deciding which process solution installation
program to use.

Chapter 16. Process solution package installation methods 239

 v The Process Solution Installation wizard provides a user experience typical of
most software installation programs. You select the process solution package to
install and provide additional installation options from wizard panels. The
Process Solution Installation wizard is an attended installation.
v The Process Solution Command Line Interface provides a simple command-line
syntax for specifying the life cycle operation to perform and the package against
which the operation is performed. You enter the Process Solution Command
Line Interface command and messages and command output are displayed to
the command line as the command is processed.
v All functions and operations are available in the Process Solution Command
Line Interface program. Only a subset of those functions is supported in the
Process Solution Installation Wizard. Generally, use the Process Solution
Installation wizard if it supports the operation you must perform.
v The Process Solution Installation Command Line Interface is useful where you
require an unattended or silent installation. The Process Solution Installation
Command Line Interface passes return codes detailing the success of the
command back to the operating system. The Process Solution Installation
Command Line Interface is suitable for use in a higher-level deployment
automation package or script.

Supported operations for the process solution installation programs

There are multiple operations and functions that are supported by the Process
Solution Installation wizard and Process Solution Command Line Interface.

The following table highlights the operations and functions that are supported by
the Process Solution Installation wizard and Process Solution Command Line
Interface.
Table 28. Process solution operations
Supported by Command Supported by Installation
Operation Line Interface wizard
List Installed Packages Yes No
List Available Packages Yes No
Base Installation Yes Yes
Incremental Update/Fix Pack Yes Yes
Full Update Yes Yes
Undo Incremental Yes No
Update/Fix Pack
Uninstall Yes No
Apply interim fix Yes Yes
Undo interim fix Yes No
List Installed Fixes for a Yes No
Package
Refresh language support Yes No
Load Language Support Files Yes Yes
Add Features Yes Yes
Remove Features Yes Yes
Show Available Features Yes Yes

240 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Note: The process solution installation programs allow an uninstall action to be
initiated against a package. However, not all packages support the uninstall
action. If an uninstall action is initiated against a package that does not support
this action, a message detailing this condition is shown. If you want to restore your
environment to the state before the installation of the SmartCloud Control Desk
process managers, you must back up your affected middleware servers before
running the SmartCloud Control Desk installation program.

Before using the process solution installation programs

Review the following prerequisite information before using process solution
installation programs.

When you perform a deployment operation using the process solution installation
programs, you are running actions that modify the configuration and content of
your J2EE, database, and directory middleware servers. Review the following steps
before starting the process solution installation programs.
Have Middleware Login Information Available
The process solution installation programs require access to middleware
servers in order to automate the deployment of the process solution
package. You must know the administrative user IDs and passwords for
the affected middleware servers. The actual middleware servers whose
login information is required depends on the process solution package
being installed. The process solution installation programs ensure that any
required login information is specified before continuing with the
deployment operation.
Backup Middleware Servers and Administrative Workstation
You should create backups for affected J2EE, database, and directory
servers before you deploy a process solution package using the process
solution installation programs. Backup the installation folder of the
administrative workstation, C:\IBM\SMP, for example. Also, backup the
deployment engine registry.
Ensure Middleware Servers Are Started
Start any affected middleware servers before running the process solution
installation programs. Before the actions associated with a package are
started, the process solution installation programs attempts to connect to
the middleware servers using the middleware login information that you
specify. If the targeted middleware servers are not started or if connections
to the middleware servers cannot be established with the specified
middleware login information, then the process solution installation
programs displays error messages and not continue on with the
deployment actions.
“Backing up the Deployment Engine database” on page 15
These instructions are for backing up the Deployment Engine database.
Backups are used to restore the database to the state it was before installing.

Managing process solution deployment from the administrative

workstation
Process solution deployment is managed from the administrative workstation.

Chapter 16. Process solution package installation methods 241

 Process solution installation programs are installed on the administrative
workstation when the SmartCloud Control Desk is installed. In addition to starting
process solution installation programs from the administrative workstation, you
must also have access to any process solution packages from the administrative
workstation.

The administrative workstation provides a deployment hub from which the

process solution packages are deployed. In order to automate deployment, the
process solution installation programs connects to either local or remote
middleware servers from the administrative workstation

Typical deployment operation

Process solution deployment is integrated tightly with SmartCloud Control Desk
deployment

Process solutions use the SmartCloud Control Desk deployment model. In this
model, as process solution packages are deployed, database content and metadata
in the package is loaded into the Maximo database and the Maximo core J2EE
applications are redeployed with Java code provided in the process solution
package. This model effectively merges the features of the process solution package
into the Maximo database and Maximo J2EE application.

High-level deployment steps are:

1. Files in the process solution package are unpacked onto the Maximo
installation directory on the SmartCloud Control Desk administrative
workstation. The Maximo installation directory contains the Maximo content
for the process solution being deployed and any other currently installed
SmartCloud Control Desk process solutions or Maximo applications and
industry solutions.
2. J2EE applications are rebuilt on the SmartCloud Control Desk administrative
workstation to contain the features of the process solution package. This feature
includes Java classes, report definitions, and other artifacts.
3. The process solution installation programs deploy the update J2EE applications
to the J2EE application server. This server can be local or remote to the
SmartCloud Control Desk administrative workstation.
4. Database content scripts associated with the package being installed are
processed on the SmartCloud Control Desk administrative workstation. This
results in updates to the database.

Important: When you deploy process solution packages, the updates are made to
the J2EE and database servers, which include redeploying the SmartCloud Control
Desk application. Deployment must be scheduled for a time when a brief
interruption of service can be tolerated, such as during a scheduled maintenance
period.

Selectable features
This section contains information about managing selectable content using features.

A process solution package might define one or more features that represent
user-selectable, optional content. Examples of typical features include globalization
and samples. Process solution installation methods support operations on features,
including capabilities for querying, adding, and removing features.

242 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Feature support in a process solution package is optional. Features are also
package-specific. The process solution installation methods examine the process
solution install package and ensure that only features defined within the package
are able to be manipulated.

Attributes of a Feature

Associated with every feature are the following attributes:

v Feature Identifier represents a non-localized name by which the feature is
uniquely identified within its package. When using the process solution
command-line interface, the Feature Identifier is used to specify the feature to
add or remove.
v Feature Display Name is a localized label for the feature.
v Parent Identifier identifies the parent feature associated with a feature. A feature
with no parent is termed a top-level feature.
v Install State indicates whether the feature is installed.
v Required Attribute indicates whether the feature is a required feature. A required
feature is a feature that must be installed if its parent feature is installed and can
not be installed if its parent feature is not installed. A top-level feature that is
required is always installed.

Operations Associated with Features

Both the process solution command-line interface and process solution installation
wizard provide features for managing features associated with a process install
package. This section describes those capabilities.
Installing Features during a Base Install
If a process solution package defines features, you can select the features to
installation during the base installation of the package.
Installing Features Using the wizard
For the process solution installation wizard, a Feature Selection
Panel is displayed after license acceptance processing if the
package being deployed supports features. The Feature Selection
Panel displays a tree where the nodes in the tree are features and
the tree nesting represents parent feature and child feature
relationships. Each node has a check box that indicates the
selection state of the feature. You select a feature to be installed by
selecting the check box for the feature.
Installing Features Using the Command Line Interface
For the process solution command-line interface, the -addfeatlist
parameter on the install action allows you to specify the features
to be installed during the base installation of the package. The
value specified for this parameter is a colon separated list of
Feature Identifiers representing the features to install.
Adding Features
After the base installation of a package, you can incrementally add features
if there exists at least one feature not already installed for that package.
Adding Features Using the wizard
When using the process solution installation wizard, if the package
is already installed but has at least one feature not already
installed, you can elect to install additional features after the
Package Validation Panel is displayed.

Chapter 16. Process solution package installation methods 243

 Note that the Deployment Engine does not support both
incremental feature add and removal in the same deployment
operation. If the state of the installed features on a package is such
that features can be both added or removed, then the Add or
Remove Features Panel is displayed that allows you to select
whether you want to add or remove features from the package.
If you select to install additional features from the Add or Remove
Features Panel, the Feature Selection Panel is again displayed with
the currently installed features checked and disabled. You cannot
uninstall currently installed features in this mode, but you can
select additional features for installation.
Adding Features Using the Command Line Interface
For the process solution command-line interface, a new
modfeatures action allows you to install features to an already
installed process solution package. The parameters on this action
are like the install action. You specify the path of the process
solution package and required middleware user IDs and
passwords. The -addfeatlist parameter on the modfeatures action
allows you to specify the features to be added. The value specified
for this parameter is a colon separated list of Feature Identifiers
representing the features to be installed.
Removing Features
After the base installation of a package, you can incrementally remove or
uninstall features if there exists at least one feature already installed for
that package.
Feature uninstallation is Optional
Support for uninstallation of features is optional. A process
solution package that supports incremental feature installation
might not support uninstallation of its features. If the process
solution package does not support uninstallation of its features,
then the process solution installation programs do not permit you
to uninstall features on the package. The process solution
installation wizard does not allow you to initiate feature
uninstallation operations against the package. The process solution
command-line interface will issue messages if uninstallation
operations are attempted against a package that does not support
feature uninstallation.
Removing Features Using the wizard
When using the process solution installation wizard, if the package
is already installed and has at least one feature already installed,
you can elect to uninstall features after the Package Validation
Panel is displayed.
As described above, if the state of the installed features on a
package is such that features can be both added or removed, then
the Add or Remove Features Panel is displayed that allows you to
select whether you want to add or remove features from the
package.
If you select to uninstall currently installed features from the Add
or Remove Features Panel, the Feature Selection Panel is again
displayed with the currently installed features checked. You may

244 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 not install new features in this mode, but you can clear currently
installed features to trigger the uninstallation operation against
those features.
Removing Features Using the Command Line Interface
For the process solution command-line interface, the modfeatures
action described above also allows you to uninstall features that
are already installed on a currently installed process solution
package. The -delfeatlist parameter on the modfeatures action
allows you to specify the features to be uninstalled. The value
specified for this parameter is a colon separated list of Feature
Identifiers representing the features to be uninstalled.
Showing Feature Information for a Package
The process solution installation programs allow you to display
information about the supported and installed features for a process
solution package.
Showing Feature Information Using the Wizard
The Feature Selection Panel of the process solution installation
wizard displays the feature tree of a process solution package. This
panel depicts the parent-child relationships between the features
and also displays whether the features are currently installed.
Showing Feature Information Using the Command Line Interface
For the process solution command-line interface, the showfeatures
action allows you to display information about the features
associated with a process solution package. Input to the action is
the path to the process solution package. The output lists the
feature attributes for the features defined for the package. Those
attributes are detailed in “Attributes of a Feature” on page 243.

Feature Selection Processing Rules and Behavior

When using the process solution installation programs to manage the features, the
actual collection of features to install or uninstall are derived using a combination
of the input selections/deselections you specify and a set of feature selections
rules. For example, you can select a single feature for installation, but, due to
feature selection rule processing, additional features can also be installed.

When you install or uninstall features, the process solution installation programs
enforce these feature selection rules to ensure that the derived set of feature
selections are valid and meet all the feature selection rules.

This section highlights the feature selection rules that are enforced by the process
solution installation programs.
Summary of Feature Selection Rules
1. Features can be arranged in a parent-child tree structure. Child features
cannot be installed unless their parent feature is installed.
2. A feature can be marked as required which indicates that the feature
must be installed if its parent is installed. A top-level feature that is
marked required is always installed.
3. Features that are marked required can never be selected/deselected
explicitly by you. The selection state of a required feature is always
derived from the selection state of their parent feature.

Chapter 16. Process solution package installation methods 245

 4. A feature can have real content (files/actions) or can be a nesting
feature which acts as a parent feature for other child features.
5. A Nesting Feature cannot be installed unless at least one of its child
features (with content) is also installed. This violation is detected
during Feature Selection Validation. Message CTGIN0200E is issued
when this rule is violated.
6. Special select-if-selected rules can be coded into the package to assert
prerequisite dependencies between features. These rules are specific to
a particular package. For example, select-if-selected rules can be defined
in a package that ensures that Feature A is installed if Features B or C
are installed.
Feature Selection Processing
1. When a child feature is selected, all its ancestor features (Parent,
Grandparent, and so on) are selected as well.
2. When a parent feature is selected, any of its required child features are
automatically selected.
3. When a feature is selected, select-if-selected rules are evaluated and any
dependent features are automatically selected.
4. The rules are applied against all features in the tree until there are no
more features to select.
Feature Deselection Processing
1. When a parent feature is cleared, all its descendant features (Child
features, Grandchild features, and so on) are cleared as well.
2. When a feature is cleared, all select-if-selected rules targeting that
feature are evaluated and any dependent features are cleared.
3. These rules are applied against all features in the tree until there are no
more features to clear.
Feature Selection Validation
The process solution installation programs enforce feature selection rules
by performing a feature selection validation process. This is the process of
deriving the complete set of features that are to be processed and
determining if the user input violates any rules. If any feature rule
violations are detected, then the operation to install or uninstall features is
not carried out by the process solution installation programs.
Feature Validation Using the Wizard
When you use the process solution installation wizard, most rules
are dynamically enforced as selections/deselections are made
against the feature tree on the Feature Selection Panel. For
example, when you select a child feature, all of its ancestor features
are automatically selected.
Additional rules are validated when you have finished making
your selections and attempt to move to the next panel. If any
violations of the rules are detected, messages describing the
violations are displayed on the Feature Selection Panel and you
must correct your input before proceeding.
Feature Validation Using the Command Line Interface
For the process solution command-line interface, the same feature
selection rules are enforced and the complete set of features to
install or uninstall is derived using those rules.

246 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 For example, if you specify only a child feature in your -addfeatlist
parameter, the PSI CLI adds all ancestor features to the list that are
actually installed. Similarly, if you specify a parent Feature on the
-delfeatlist parameter, then any installed child features under that
parent feature is also uninstalled.
Additionally, the process solution command-line interface also
performs additional checks against the features you specify. These
checks include:
1. Ensuring that any feature identifier specified is a valid
identifier for the package.
2. Ensuring that features specified using the -addfeatlist
parameter are not already installed for the package.
3. Ensuring that features specified using the -delfeatlist parameter
are already installed for the package.

Deferring J2EE and database configuration

You can defer the automated redeployment of J2EE applications and updates to the
Maximo database for process solution packages.

There are several reasons for why you might want to elect to skip automated
deployment.
v Your organization might have policies that prohibit remote access and update of
the J2EE application, database, or directory servers from the SmartCloud Control
Desk administrative workstation.
v You might not have the authority to perform administrative functions against
the targeted middleware servers.
v Your organization might have existing procedures in place for how applications
get deployed to middleware servers.
Using the Installation Wizard
When using the Process Solution Installation wizard, you can defer J2EE
and database-related configuration steps. You defer them by selecting the
defer options on the Package Installation Options panel.
Using the Command Line Interface
When using the Process Solution Command Line Interface, you can defer
J2EE and database-related configuration steps by specifying the
-skipj2eecfg and -skipdbcfg command-line flags.

You might want to defer the automatic J2EE deployment if you are installing
multiple process solution packages in sequence. The regeneration and
redeployment of the Maximo J2EE applications is processing and time intensive.

You can improve overall deployment time by performing the regeneration and
redeployment of J2EE applications after all packages have been unpacked to the
administrative workstation.

For example, assume that you are installing Process Manager Products A, B, and C
as part of your deployment scenario. You would skip the regeneration/
redeployment of the J2EE applications when deploying Process Manager Products
A and B. When deploying Process Manager Product C, you would specify the
options to perform the redeployment of the Maximo J2EE applications.

Chapter 16. Process solution package installation methods 247

 If you do not automate the update of the Maximo database, do not use the process
solution installation program with the -loadsampdata option. The sample data is
not loaded.

Always defer the configuration of the J2EE and database together. Never defer one
and not the other.

Deferring J2EE configuration while configuring the database causes the database to
be updated updated with the content of the process solution package. However,
the J2EE applications are not regenerated and redeployed with the content of that
process solution package. You can browse to the application associated with the
process solution package. However, when you create records with those
applications, you get errors. The applications contained in the installed package
remain unusable until the Maximo J2EE applications are regenerated and
redeployed. Deferring database configuration while configuring the J2EE server
causes J2EE applications to be regenerated and redeployed with the content of the
process solution package. However, the database is not updated with the content
of that process solution package. Applications associated with the process solution
package appear under the list of applications displayed from Help → System. These
applications do not appear in the list of selectable applications. The applications
contained in the installed package remain unusable until the database
configuration task is completed.

If you must manually rebuild and redeploy the Maximo EAR file, see the System
Administrator Guide for instructions.

Manually completing deployment

This procedure provides task information for manually deploying the process
solution package when opting out of automatic middleware configuration.

About this task

When you elect to defer automated configuration, you are responsible for manually
starting the configuration operations required to complete the deployment of the
process solution package. Until the manual configuration steps are completed, the
process solution package is in an incomplete and unusable state.

The following procedure assumes that you have run the process solution
installation program and deferred the J2EE and database configuration during
package deployment.

To manually deploy the process solution package, complete the following steps:

Procedure
1. Log in to WebSphere Application Server Network Deployment, browse to
Servers > Application Servers, and stop the MXServer server.
2. Update the Maximo database:
<MAXIMO_HOME>\tools\maximo\updatedb -sl
3. Rebuild the maximo.ear and maximoiehs.ear files.
<MAXIMO_HOME>\deployment\buildmaximoear
<MAXIMO_HOME>\deployment\buildmxiehsear
4. Uninstall the MAXIMO and MAXIMOIEHS applications from within
WebSphere Application Server Network Deployment.

248 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 5. Reinstall the MAXIMO and MAXIMOIEHS applications within WebSphere
Application Server Network Deployment.
6. Restart the MXServer.

Pre-deployment system check

Before the actions associated with a software life cycle operation are initiated, the
process solution installation programs perform a system check activity. Associated
with each process solution package are a set of requirements that must be satisfied
before the deployment operation is carried out. The system check is a process that
analyzes the requirements to determine that all requirements have been satisfied
before continuing on with the deployment operation.

The actual requirements are specific to each process solution package.

Requirements include disk space and memory consumption checks for the package
and dependency checks between a process solution package and other process
solution packages. When unsatisfied requirements are detected during the system
check, the process solution installation programs display messages that describe
the failed requirements. Before trying the deployment operation again, you must
update your environment such that all requirements associated with the process
solution package are satisfied.
Bypassing Unsatisfied Requirements
Under certain circumstances, you may find it necessary to bypass the
system check processing and carry out a deployment operation even if one
or more requirements associated with the process solution package are not
satisfied. For example, a process solution package might have embedded
an incorrectly specified disk space check which would prohibit the package
from being installed on a system that has adequate free disk space required
by the package.
Both process solution installation programs provide mechanisms that allow
you to bypass failed requirements and continue with the deployment
operation.
Using the Installation wizard
When using the Process Solution Installation wizard, a System
Check Failed panel displays messages for any failed requirements.
From this panel, you can bypass the system check failures by
selecting the check box entitled Ignore System Check Failures.
When you select this check box, the Process Solution Installation
wizard continues with the deployment of the process solution
package.
Using the Command Line Interface
When using the Process Solution Command Line Interface, you can
bypass unsatisfied system check requirements by specifying the
-force command-line flag.
Package requirements represent criteria put in place to ensure a successful
deployment. While you must not bypass any requirements normally, the
process solution installation programs permit the following types of
requirements to be bypassed:
v Capacity and consumption checks, for example, disk space and memory
requirements for a package.
v Prerequisite, corequisite, and exrequisite relationships defined for a root
package. For example, Package B might require that Package A is

Chapter 16. Process solution package installation methods 249

 installed before Package B can be installed. You can force processing of
the installation operation for Package B even if Package A is not
currently installed.
v Property checks defined for the package, for example, a check of the
type of operating system on which the installation is being performed.
v Any custom checks defined for the package.

Note: Prerequisite, corequisite, and exrequisite dependencies defined

between fix packages cannot be overridden.
System check progress messages
During the processing of the system check, the IBM Autonomic Computing
Deployment Engine publishes events detailing the progress of the system
check. The process solution installation programs receive the events and
convert them into localized messages with identifier CTGIN0146I which
are displayed to the user. The messages include the label for the check
being performed, the number of completed checks, and the total number of
checks that are to be performed.
The IBM Autonomic Computing Deployment Engine is not able to
compute the total number of checks to be carried out before any checks are
processed. The counter associated with the total number of checks to be
performed can increase during system check processing. For example, the
following set of messages might be issued during the system check
processing. The counter associated with the total number of checks is not
fixed, but recalculated and increased during system check processing.
CTGIN0146I: Completed system check for check "1" of "2". Check display name:
"Check_Common_PMP_Installed".
CTGIN0146I: Completed system check for check "2" of "3". Check display name:
"Check_LTA_WAR_Package_Installed".
CTGIN0146I: Completed system check for check "3" of "4". Check display name:
"Check_Foundation_PM_Package_Installed".
CTGIN0146I: Completed system check for check "4" of "4". Check display name:
"MaximoDiskSpaceCheck".

Installing process managers using the process solution installation

wizard
Process managers can be installed using the process solution installation wizard

About this task

Complete the following steps to install a process solution package into SmartCloud
Control Desk using the process solution installation wizard:

Procedure
1. Start the process solution installation program by navigating to the
<install_home>\bin directory of your SmartCloud Control Desk installation,
and using solutionInstallerGUI.bat. As with the Process Solution Installation
Command Line Interface Client, the Process Solution Installation Install
Anywhere installation program starts on the administrative workstation. The
launch script is deployed and configured by the SmartCloud Control Desk
installation program. No post-installation configuration is required. Start
solutionInstallerGUI.bat and the wizard is started.

250 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Alternatively, if you elected to create program shortcuts during the
SmartCloud Control Desk installation, a link to the Process Solution
installation program UI can be available from the Start menu, a desktop icon,
or a quick launch bar.
2. Select a language for your installation, and then click OK.
3. From the Introduction panel, click Next.
4. From the Choose PSI Package panel, click Choose and navigate to the package
file you want to deploy, select it, and then click Open. The PSI package
selected can be a base install, incremental update, full update, or fix package
Once a package has been selected and you click Next, the process solution
installation program performs a series of validation checks to verify that the
package you selected is valid. The system is checked to ensure that the
package has not already been deployed, or, if the package is intended as an
upgrade, the system is checked to ensure that the base package has already
been installed.
5. From the Package Validation Results panel, review and verify the information
displayed, and then click Next.
6. If this is the first time you have installed this process manager, the process
solution installation program license agreement window is displayed. Read
the license information and select I accept the terms in the license agreement
if you agree with the terms. Click Next. If you are incrementally adding or
removing features from a previously installed process manager, you encounter
an Add or Remove Features? panel where you declare whether you are
adding or removing features from the process manager, followed by another
panel where you select which specific features you are adding or removing.
7. If this is the first time you have installed this process manager and it has
selectable features, you are prompted by the Feature Selection panel to select
or clear features you would like to install or uninstall from the previously
deployed package.
8. From the Middleware Login Information panel, enter the credentials for which
you are being prompted, and then click Next. The contents of this panel are
constructed dynamically, depending on the type of package you are installing.
The package is queried to determine what middleware login credentials are
necessary to complete the installation of the package.
Once you have entered the requested user IDs and passwords, the process
solution installation wizard validates the credentials by connecting to the
middleware servers using the supplied credentials.
9. After the credentials have been verified, a package options panel is displayed
that details the deployment options that the package supports. If the PSI
installable package supports the Overwrite Customer Modified Data during
Update option, you can select it from this page. After you specify which
options are used, the process solution installation program will perform a
system check. to ensure that all system requirements necessary for the
package to be installed are present. Click Next to advance.
10. From the Pre-Install Summary panel, review and verify the information
displayed, and then click Next. The process solution installation program
begins the package installation process. A progress panel informs you of the
deployment progress of the installation.
11. When the installation has completed successfully, from the Package
Successfully Deployed panel, click Next. If there is a package failure, a
message appears for the step that failed. If this was a Feature Add, or
Removal, a message displays indicating the feature was added or removed
successfully.

Chapter 16. Process solution package installation methods 251

 12. From the Install Another Package panel, select Install Another Package? and
click Done, to install another package. Otherwise, ensure that Install Another
Package? is cleared and click Done to exit the process solution installation
wizard.

Results

You might see an installation progress bar displayed briefly after you click Done.
The Process Solution Installation wizard is actually terminating and no installation
activities are being performed. The deployment of the Process Solution Package
you were installing has already completed and the progress bar can be safely
ignored.

Process solution installation client command-line interface

Use the process solution installation client command-line interface (CLI) to query,
install, upgrade, and uninstall process solution packages.

Process solution packages can consist of process modules and integration modules.

Starting the process solution installation client CLI

A launch script is provided for starting the Process Solution Command Line
Interface. The script is named solutionInstaller.bat and is deployed and
configured in the <install_home>\bin directory. The Process Solution Command
Line Interface is used on the administrative workstation. The launch script is
deployed and configured by the SmartCloud Control Desk installation program.
No post-installation configuration is required. Start solutionInstaller.bat with
the preferred command string and the action is performed.

During processing of the command, the Process Solution Command Line Interface
writes messages to the standard output of the command window from which the
command was launched.

General syntax
General syntax of starting the solution installation program.

solutionInstaller syntax

The syntax for starting solutionInstaller is:

solutionInstaller.bat parameter-clause-1 parameter-clause-2 ... parameter-clause-n
v Each parameter-clause consists of either -parameterName parameterValue or
-parameterName.
v -parameterName parameterValue is used for parameters that require a parameter
value.
v -parameterName is used for parameters that represent switches or flags which do
not require a parameter value.
v parameterName represents the name of one of the supported parameters.
v parameterNames are always prefaced with a dash.
v parameterValue represents the value associated with a particular parameter name.
v parameterValues that contained embedded spaces must be enclosed in double
quotation marks

252 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Perform action
The solution installation program uses an action parameter when interfacing with
packages.

A special parameter, -action, must be specified on each invocation of

solutionInstaller. This parameter specifies the action or software life cycle
operation to be performed. Based on the value specified for this parameter,
additional parameters can be specified. For example, when -action showinstall is
specified, the type parameter must also be provided. The following table identifies
the supported actions that can be specified for the Process Solution Command Line
Interface.
Table 29. Process solution command-line interface actions
Operation Value of -action Parameter
List Installed Packages showinstalled
List Available Packages showavail
Base Install install
Incremental Update/Fix Pack upgrade
Undo Incremental Update/Fix Pack undo
Uninstall uninstall
Apply interim fix applyfix
Undo interim fix undofix
List Installed Fixes for a Package showfixes
Refresh Language Support Files for a refreshlangs
Package
Add or Remove Features modfeatures
Show Available Features showfeatures

Summary of supported parameters

This section contains a summary of parameters supported by the command-line
interface.

The collection of supported parameters for the Process Solution Command Line
Interface is described in the following table.
Table 30. Process solution command-line interface supported parameters
Parameter Name Description
-action Specify the function or software life cycle
operation to perform.
-addfeatlist Specifies the list of features to be installed. A
feature is identified by its untranslated
English Feature Identifier. Multiple features
in the list are separated by a colon character.
If any of the Feature Identifiers includes a
space, then the entire value for this
parameter must be enclosed in double
quotation marks.
-dbpwd Specifies the password of the database user
ID that is used to access the Maximo
database.

Chapter 16. Process solution package installation methods 253

 Table 30. Process solution command-line interface supported parameters (continued)
Parameter Name Description
-dbuser Specifies the database user ID that is used to
access the Maximo database.
-delfeatlist Specifies the list of features to be deleted. A
feature is identified by its untranslated
English Feature Identifier. Multiple features
in the list are separated by a colon character.
If any of the Feature Identifiers includes a
space, then the entire value for this
parameter must be enclosed in double
quotation marks.
-fixid Specifies the unique identifier of an interim
fix/patch that you want processed.
-force Specifies whether to continue on with a
deployment operation even if there are one
or more unsatisfied requirements associated
with the package being processed.
-license Automatically accept the license agreement
or be prompted for the acceptance or
rejection of the license agreement by using
one of the following values: accept or
prompt.
-loadlanguages Specifies whether options Language Support
files for the package must be loaded into the
Maximo Database
-loadsampdata Specifies whether to load sample or
demonstration data associated with the
package being processed.
-maxpwd Specifies the password of the SmartCloud
Control Desk administrative user that is
used to access the SmartCloud Control Desk
application.
-maxuser Specifies the SmartCloud Control Desk
administrative user ID that is used to access
the Maximo console.
-pkgpath Specifies the file path of a process solution
package. Paths that have embedded spaces
must be enclosed in double quotation marks.
-pkguuid Specifies the unique identifier of the process
solution package that you want processed.
-pkgver Specifies the version of the process solution
package that you want processed.
-skipdbcfg Specifies whether to defer the update of the
Maximo database during package
deployment.
-skipj2eecfg Specifies whether to defer the regeneration
and redeployment of the Maximo J2EE
Applications during package deployment.

254 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 Table 30. Process solution command-line interface supported parameters (continued)
Parameter Name Description
-type Specify one of the following types of
solution element package to be returned
when the showavail or showinstalled actions
are used. Valid values are processmodule,
integrationmodule, or all.
-waspwd Specifies the IBM WebSphere Application
Server Network Deployment administrator
password.
-wasrxapwd Specifies the password for the user ID under
which remote access to the IBM WebSphere
Application Server Network Deployment
system is performed.
-wasrxauser Specifies the user ID under which remote
access to the IBM WebSphere Application
Server Network Deployment system is
performed.
-wasuser Specifies the IBM WebSphere Application
Server Network Deployment administrator
user ID.

Process solution command-line interface reference

See the following sections for process solution command-line interface reference
information.

Several of the command-line interface actions reference a syntax element named

[<middleware login information>].

The syntax for the middleware login element is:

[-wasuser <userid> -waspwd <password>]
[-dbuser <userid> -dbpwd <password>]
[-maxuser <userid> -maxpwd <password>]
[-wasrxauser <userid> -wasrxapwd <password>].

The actual user IDs and passwords that are required depend on the package being
processed. For example, a package that only deploys content to the Maximo
database would only require the -dbuser and -dbpwd parameters.
Table 30 on page 253

install action - install\ a package

Description of the action used to install packages.

install
Action
install
Purpose
Perform an installation of a process solution package not already installed.
Syntax
solutionInstaller
-action install
-pkgpath <path-to-base-install-package-file>

Chapter 16. Process solution package installation methods 255

 [<middleware login information>]
[-license <accept|prompt>]
[-skipj2eecfg] [-skipdbcfg] [-loadlanguages] [-loadsampdata] [-force]
Description
The install action is used to install a process solution package. When
installing a package, the file name of the process solution package archive
file to be installed is specified using the -pkgpath parameter.
Preconditions
Before using this action, you must ensure that:
v The process solution package archive file you specify is a valid Base
Install package.
v The package is not already installed. You can check by using the
showinstalled action.
v All additional requirements associated with the package specified are
satisfied.
Sample Usage

modfeatures action - modify existing features of a deployed

package
Description of the action used to modify existing features of a deployed package.

modfeatures
Action
modfeatures
Purpose
Modify features of a currently installed process solution package.
Syntax
solutionInstaller
-action modfeatures
-pkgpath <path-to-base-install-package-file>
[-addfeatlist FeatA:FeatB:¦:Featn]
[-delfeatlist FeatA:FeatB:¦:Featn]
[<middleware login information>]
[-skipj2eecfg] [-skipdbcfg] [-force]
Description
The modfeatures action is used to modify the installed features for a
currently installed process solution package. When modifying features, the
file name of the process solution package archive file containing the
features to be modified is specified using the -pkgpath parameter. To add
new features not already installed, you use the –addfeatlist parameter. To
remove currently installed features, you use the –delfeatlist parameter.
You cannot both add and remove features with one invocation. One and
exactly one of either the –addfeatlist or the –delfeatlist parameters
must be provided when this command is started.

256 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Process solution installation logs
If you experience any problems or encounter any error messages during the use of
the process solution installation program, see these log files.

Log files are kept in the following locations:

Table 31. Process solution installation logs
Log type Description Location
Package log These are log files containing <install_home>\solutions\
the StdOut/StdErr output of logs\<PACKAGE_NAME>\
external commands launched
by the package as it is
processed by the
Deployment Engine. These
log files are typically vital to
the proper debugging of
package issues.

In general, logs have two

parts, a ".out" and ".err" file,
both with the same
pre-extension file name. .out
files contain the contents of
the Standard Output stream
as output by the external
command. .err files contain
the contents of the Standard
Error stream. It is normal for
one to be blank, provided
there was no error output (or
there was ONLY error
output).

Note that you might discover

numerous (10-20) package
log files generated for any
particular package installed.

Chapter 16. Process solution package installation methods 257

 Table 31. Process solution installation logs (continued)
Log type Description
SmartCloud Control Desk These are logs kept by the
log PSI subsystem.
Solution Install/Deployment These are logs kept by the
Engine Logs IBM Solution installation
program/Deployment engine
run time. PSI utilizes the
IBM technology as the means
to install and track installed
packages. This run time has
its own logging system.
Note: After an installation
these logs contain sensitive
credentials. Remove logs
after a successful installation. logs\Administrator\
258 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Location
<install_home>\logs\
CTGInstallMessageXX.log
<install_home>\logs\
CTGInstallTraceXX.log
XX is a two-digit number
such as 00. These logs
contain the trace output of
the PSI subsystem.
Note: You might encounter
messages like the following
in the
MAXIMO_DEPLOY_ERR.err file
found in the
<install_home>\solutions\
logs directory for a process
manager once it has been
installed:
v *sys-package-mgr*:
processing new jar,
'C:\IBM\SMP\lib\icl.jar'
v *sys-package-mgr*:
processing new jar,
'C:\IBM\SMP\lib\
CTGInstallCommon.jar'
v *sys-package-mgr*:
processing new jar,
'C:\IBM\SMP\lib\
CTGInstallResources.jar'
Although these messages
appear in an error log file,
they are informational only,
and do not represent
deployment errors. These
messages can be safely
ignored.
C:\IBM\SMP\CTG_DE\acsi\
logs\<USERNAME>\de_msg.log
C:\IBM\SMP\CTG_DE\acsi\
logs\<USERNAME>\
de_trace.log
So for instance, if you
installed under the user
name "Administrator", the
logs would be found under:
C:\IBM\SMP\CTG_DE\acsi\
de_msg.log
Table 31. Process solution installation logs (continued)
Log type Description
WebSphere Application These are logs kept of
Server Logs connections, exceptions, and
other failures experienced by
the WebSphere Application
Server in its day-to-day
running. These logs are often
helpful in the diagnosis of
errors in particular EAR files
or other operations, such as
database connections.
Maximo Logs There are also a few logs
kept by Maximo itself. These
are useful in tracking the
progress, success, and failure
of a few commands provided
by Maximo.
Chapter 16. Process solution package installation methods
Location
<WAS_HOME>\profiles\
<PROFILE>\logs\
AboutThisProfile.txt
<WAS_HOME>\profiles\
<PROFILE>\logs\
<SERVER_NAME>\
startServer.log
<WAS_HOME>\profiles\
<PROFILE>\logs\
<SERVER_NAME>\
stopServer.log
<WAS_HOME>\profiles\
<PROFILE>\logs\
<SERVER_NAME>\
SystemErr.log
<WAS_HOME>\profiles\
<PROFILE>\logs\
<SERVER_NAME>\
SystemOut.log
So for instance, if your
WebSphere Application
Server was installed in
"C:\IBM\WebSphere\
AppServer\", your profile
name was "AppSrv01", and
your server name was
"server1", you would provide
the following
logs:C:\IBM\WebSphere\
AppServer\profiles\
AppSrv01\logs\
AboutThisProfile.txt
<install_home>\maximo\
tools\maximo\log\
updatedb<TIMESTAMP>.log
So if your Maximo
installation location was
"C:\IBM\SMP\Maximo", and the
package executed the
"UpdateDB" command on
April 19th at approximately
5:06:07PM, the logging
information would be
written to the file:
C:\IBM\SMP\Maximo\tools\
maximo\log\
updatedb20070419170607.log
259
 Table 31. Process solution installation logs (continued)
Log type
WebSphere Thin Client Logs
Description
The WebSphere thin client is
the mechanism by which the
process manager packages
communicate with the
WebSphere Application
Server. If this automated
deployment fails, the exact
actions the Thin Client took
and the associated responses
from the WebSphere
Application Server are stored
in logs.
Location
<install_home>\wasclient\
logs\
CTGIN_wsadmin.traceout
<install_home>\wasclient\
logs\wsadmin.traceout
<install_home>\wasclient\
logs\wsadmin.valout
So if your SmartCloud
Control Desk installation
location were C:\IBM\SMP, the
following log files would
contain the Thin WebSphere
Client tracing information:

C:\IBM\SMP\wasclient\logs\
CTGIN_wsadmin.traceout

C:\IBM\SMP\wasclient\logs\
wsadmin.traceout

C:\IBM\SMP\wasclient\logs\
wsadmin.valout

It is a good practice to rename existing logs before attempting a package install. It

is useful to have a log composed of only the information related to the success or
failure of current package installation to facilitate problem determination.

260 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Chapter 17. Advanced installation topics
This section contains information useful for advanced SmartCloud Control Desk
deployment scenarios.

Refer to this information for installation and configuration information in advanced

deployments.

WebSphere Application Server Network Deployment management

Perform these tasks if you installed WebSphere Application Server Network
Deployment, or used an existing server.

Comprehensive information about running and administering can be found on the

WebSphere Application Server Network Deployment support site.

Starting the application server from the command line

An application server named MXServer is created during SmartCloud Control
Desk deployment, either manually, or automatically by the SmartCloud Control
Desk installation program.

About this task

To start the MXServer application server from the command line, complete the
following steps:

Procedure
1. Start the deployment manager:
UNIX and Linux
<WAS_HOME>/AppServer/profiles/ctgDmgr01/bin/startManager.sh
Windows
<WAS_HOME>\profiles\ctgDmgr01\bin\startManager.bat
2. Start the node:
UNIX and Linux
<WAS_HOME>r/profiles/ctgAppSrv01/bin/startNode.sh
Windows
<WAS_HOME>\profiles\ctgAppSrv01\bin\startNode.bat
3. Start the web server:
UNIX and Linux
<WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.sh webserver1
Windows
<WAS_HOME>\profiles\ctgAppSrv01\bin\startServer.bat webserver1
4. Start the application server:
UNIX and Linux
<WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.sh MXServer
Windows
<WAS_HOME>\profiles\ctgAppSrv01\bin\startServer.bat MXServer

© Copyright IBM Corp. 2012 261

 Starting the application server from the administrative console
An application server named MXServer is created during SmartCloud Control
Desk deployment, either manually, or automatically by the SmartCloud Control
Desk installation program.

About this task

To start the MXServer application server from the administrative console, complete
the following steps:

Procedure
1. Before you start the administrative console, verify that the following server
processes are running. If necessary, use the commands shown from a command
prompt in order to start them.
Table 32. Server processes
Server Go To
HTTP Server
Windows
<HTTP_SERVER_HOME>\bin\apache -k start
<HTTP_SERVER_HOME>\bin\apache -k stop
UNIX <HTTP_SERVER_HOME>/bin/apachectl start
<HTTP_SERVER_HOME>/bin/apachectl stop
Deployment
Windows
Manager
<WAS_HOME> \profiles\ctgDmgr01\bin\startManager.bat
<WAS_HOME> \profiles\ctgDmgr01\bin\stopManager.bat
UNIX <WAS_HOME>/profiles/ctgDmgr01/bin/startManager.sh
<WAS_HOME>/profiles/ctgDmgr01/bin/stopManager.sh
Node Agent
Windows
<WAS_HOME>\profiles\ctgAppSrv01\bin\startNode.bat
<WAS_HOME>\profiles\ctgAppSrv01\bin\stopNode.bat
UNIX <WAS_HOME>/profiles/ctgAppSrv01/bin/startNode.sh
<WAS_HOME>/profiles/ctgAppSrv01/bin/stopNode.sh
Tivoli Directory
Windows
Server Instance
1. Click Start, and select Run.
2. Type services.msc, and click OK.
3. Select IBM Tivoli Directory Server Instance V6.1 -
idsccmdb, and click Start the service.
UNIX /ldap/V6.1/sbin/ibmslapd -I idsccmdb
Directory
Windows
Server
Database 1. Click Start, and select Run.
2. Type services.msc, and click OK.
3. Select DB2 - DB2COPY1 - CTGINST1-0, and click Start the
service.
UNIX su - idsccmdb -c db2start

262 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 2. To start the administrative console, open a browser window and enter the
following URL: http://<server_name>:9060/ibm/console Where <machine_name>
is the host name of the WebSphere Application Server Network Deployment
and 9060 is the default port number for the administrative console.
3. Enter an administrative user ID and password to log in, if one is required.
4. From the administrative console, click Servers > Server Types > Application
Servers.
5. Select the check box next to MXServer, the name of the WebSphere Application
Server Network Deployment.
6. Click Start. Notice that the icon in the Status column changes to running. To
stop the WebSphere Application Server Network Deployment, you can click
Stop, which causes the icon in the Status column to change to stopped.

Securing the WebSphere Application Server Network

Deployment administrative console
You can secure the administrative console so that only authenticated users can use
it.

About this task

After enabling Virtual Member Manager for WebSphere Application Server

Network Deployment security, you complete several steps to secure the console.
First you identify users (or groups) that are defined in the active user registry.
After you decide which users you want to access the console, you can determine
their level of access by assigning roles. The roles determine the administrative
actions that a user can complete. After you enable security, a user must enter a
valid administrator user ID and password to access the console.

You can use the Administrative Group Roles page to give groups-specific authority
to administer application servers using the administrative console. Click Security
> Secure administration, applications, and infrastructure > Administrative Group
Roles to view the available administrative group roles.
Table 33. Administrative group roles
Admin Role Description
Administrator Has operator permissions, configurator permissions, and the
permission that is required to access sensitive data.
Operator Has monitor permissions and can change the run time state. For
example, the operator can start or stop services.
Configurator Has monitor permissions and can change the application server
configuration.
Monitor Has the least permissions. This role primarily confines the user
to viewing the application server configuration and current state.
deployer Users granted this role can configuration and run applications.
adminsecuritymanager Fine-grained administrative security is available using wsadmin
only. However, you can assign users and groups to the
adminsecuritymanager role on the cell level using wsadmin
scripts and the administrative console. Using the
adminsecuritymanager role, you can assign users and groups to
the administrative user roles and administrative group roles.
However, an administrator cannot assign users and groups to the
administrative user roles and administrative group roles
including the adminsecuritymanager role.

Chapter 17. Advanced installation topics 263

 Table 33. Administrative group roles (continued)
Admin Role Description
iscadmins Has administrator privileges for managing users and groups
from within the administrative console only.

Note: To manage users and groups, click Users and Groups in the console and
then click either Manage Users or Manage Groups.

Complete the following steps to map users and groups to security roles:

Procedure
1. Select Applications > Enterprise applications > application_name.
2. Under Detail properties, click Security role to user/group mapping.
3. Select the role and click either Look up users or Look up groups. Different
roles can have different security authorizations. Mapping users or groups to a
role authorizes those users or groups to access applications defined by the role.
Users and groups are associated with roles defined in an application when the
application is installed or configured. Use the Search pattern field to display
users in the Available list. Click >> to add users from the Available list to the
Selected list.
4. Restart all the application servers.

Configuring Windows services

Creating the WebSphere Application Server Network Deployment application
server and node agent to run as Windows services.

These services must be created so that they start in the correct order. Use the
following procedures to create these services. First create the node agent service,
then create the MXServer service.

Configuring the WebSphere Application Server Network

Deployment application server to run as a Windows service
Configuring the WebSphere Application Server Network Deployment to run as a
Windows service can make it more convenient to manage.

About this task

To configure the WebSphere Application Server Network Deployment application

server to run as a Windows service, complete the following steps:

Procedure
1. Start the WebSphere Application Server Network Deployment administrative
console by opening a browser window and entering the following URL
http://<server_name>:9060/ibm/console
2. Enter an administrative user ID and password
3. Click Servers > Application Servers.
4. In the Application Servers pane, select MXServer and click Start. This action
creates a server log folder used by the WASService command.
5. Select MXServer, and click Stop.
6. Open a command prompt window.

264 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 7. Navigate to the bin folder where you installed the Maximo application server.
For example: C:\Program Files\IBM\WebSphere\AppServer\bin
8. Run the WASService command with the following parameters:
serverName
Name of Maximo application server, MXServer
profilePath
The profile directory of the server, for example, C:\Program
Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01
wasHome
Home folder for MXServer, for example, C:\Program
Files\IBM\WebSphere\AppServer\profiles
logRoot
Folder location of MXServer log file, for example, C:\Program
Files\IBM\WebSphere\AppServer\logs\ manageprofiles\ctgAppSrv01
logFile
Log file name for MXServer (startServer.log)
restart Restarts the existing service automatically if the service fails when set
to true.
9. Enter the WASService command using the following syntax:
WASService
-add MXServer
-serverName MXServer
-profilePath "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01"
-wasHome "C:\IBM\WebSphere\AppServer"
-logRoot "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\MXServer"
-logFile "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\MXServer\
startServer.log"
-restart true
10. Press Enter after you type the WASService command, and you see a
confirmation message.
11. Open a Services window and double-click MXServer. Then perform the
following actions:
a. Change the Startup type field value to Automatic.
b. Click Start to start the service.
c. Click OK.

Changing the middleware installation program configuration

parameters
You can change the configuration parameters you have entered for a deployment
plan before deploying the plan. You would use this option if you chose to cancel
the deployment of the deployment plan you developed by exiting the middleware
installation program. Configuration parameters for a plan can be changed only
before deploying the deployment plan.

About this task

These instructions assume that you have developed a deployment plan, entered
configuration parameters for the plan, and then exited the middleware installation
program before actually deploying the deployment plan.

Chapter 17. Advanced installation topics 265

 Procedure
1. Relaunch the middleware installation program from the launchpad and
advance along the installation program panels until you reach the Choose
Workspace panel.
2. From the Choose Workspace panel, specify the directory you previously used
as the middleware installation program workspace, and then click Next.
3. Select Edit the configuration parameters, and then click Next.
4. Advance along the middleware installation program panels and make changes.
5. When you reach the Deployment Plan Operation panel, select Deploy the plan,
and then click Next.
6. From the Deployment Plan and Parameter Configuration summary panel,
review the contents of the summary, and then click Next to initiate the
installation and configuration of the middleware you selected.
7. From the Select Middleware Image Directories panel, enter the location for
compressed images for the middleware contained in the deployment plan, and
a directory to use to hold the uncompressed images. After you have entered the
two locations, click Next. During deployment, the middleware images are
uncompressed onto the system.
8. Click Finish to exit.

Maintaining EAR files

This section contains information about maintaining SmartCloud Control Desk
EAR files.

The following instructions are used to manually build or uninstall the SmartCloud
Control Desk maximo.ear and maximoiehs.ear files on WebSphere Application
Server Network Deployment.

Although the SmartCloud Control Desk installation program deploys these EAR
files when you install, there might be a few instances where it would be desirable
to rebuild these EAR files manually:
v If you modify any database connection parameters in the maximo.properties file
after the initial installation, you must rebuild of the maximo.ear file, and then
redeploy it in WebSphere Application Server Network Deployment. In this
scenario, you would likely only rebuild and redeploy the maximo.ear file. You
would not be required to rebuild and redeploy the maximoiehs.ear file.
v SmartCloud Control Desk must be installed into a WebSphere Application Server
Network Deployment application server. However, SmartCloud Control Desk
can be run within the framework of a WebSphere Application Server Network
Deployment cluster. If you want to deploy SmartCloud Control Desk in a
cluster, you can either redeploy the SmartCloud Control Desk EAR files into a
cluster, or, create a cluster from the application server used during the install. If
you have already installed SmartCloud Control Desk into an application server
but would like to redeploy into a cluster, then you must either uninstall the
MAXIMO application (“Manually uninstalling applications from WebSphere
Application Server Network Deployment” on page 267), or provide a new name
for the application when installing the MAXIMO application into a cluster
(“Manually installing applications in WebSphere Application Server Network
Deployment” on page 267).
v If you have installed SmartCloud Control Desk into a development environment,
you might at some point like to migrate the deployment into a test or

266 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 production environment. In this scenario, you must deploy both the maximo and
maximo help applications into the new environment.
The steps outlined in “Manually installing applications in WebSphere
Application Server Network Deployment” should be performed for both
applications.

Building EAR files

You can manually build SmartCloud Control Desk EAR files if, for example, you
modify a database connection parameter in the maximo.properties file after the
initial installation.

About this task

To manually build SmartCloud Control Desk EAR files, complete the following
steps:

Procedure
1. Build the maximo EAR file:
Windows
install_home\maximo\deployment\buildmaximoear.cmd
Linux and UNIX
install_home/maximo/deployment/buildmaximoear.sh
2. Build the maximo help system EAR file:
Windows
install_home\maximo\deployment\buildmxiehsear.cmd
Linux and UNIX
install_home/maximo/deployment/buildmxiehsear.sh

Manually uninstalling applications from WebSphere

Application Server Network Deployment
This section contains information about uninstalling SmartCloud Control Desk
applications from WebSphere Application Server Network Deployment.

Procedure
1. Log in to the WebSphere Application Server Network Deployment
administrative console, select Servers > Server Types > WebSphere application
servers, select MXServer and click Stop.
2. Click the Applications link.
3. Select the check box next to the application you are uninstalling. By default, the
SmartCloud Control Desk applications are named maximo and maximoiehs.
4. Click Uninstall.

Manually installing applications in WebSphere Application

Server Network Deployment
SmartCloud Control Desk applications can be added to WebSphere Application
Server Network Deployment.

Procedure
1. Log on to the WebSphere Application Server Network Deployment
administrative console.

Chapter 17. Advanced installation topics 267

 2. Browse to Applications > New Application > New Enterprise Application.
3. From the Specify the EAR, WAR, JAR, or SAR module to upload and install
page, select Local file system.
4. Browse to the location on your system of the maximo.ear file and click Next.
5. Select Detailed and then click Next.
6. From the Application Security Warnings panel, click Continue.
7. Click Step 2: Map modules to servers.
8. Highlight all entries listed in the Clusters and servers field, check all check
boxes for Modules listed in the table, and click Apply.
9. Click Step 11: Map virtual hosts for Web modules.
10. Check all check boxes for web modules listed in the table.
11. Expand Apply Multiple Mappings.
12. Select a virtual host, for example, maximo_host, from the Virtual Host menu,
and click Apply.
13. Click Step 15: Map security roles to users or groups.
14. Select the check box for maximouser in the Role table, and then select
Everyone from the Map Special Subjects menu.
15. Click Step 17: Summary, review the summary information, and click Finish.

268 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Chapter 18. Middleware on Solaris and HP-UX
Middleware versions that are not installable by the middleware installation
program are installed by using graphical installation programs that are provided
with each middleware product.

The procedures in this document can be used to manually install the following
products on the following operating systems:

Solaris 11 SPARC and HP-UX 11i v2+3 64 bit

v IBM DB2 Enterprise Server Edition 9.7
v IBM Tivoli Directory Server 6.3.
IBM Tivoli Directory Server 6.3 is only supported for Solaris 11.
v IBM WebSphere Application Server Network Deployment 7
v IBM HTTP Server 7

Operating system preparation

Some operating system default configuration settings must be change to provide
an environment that can host middleware operations.

The steps needed to prepare each newly supported operating system are operating
system dependent.

Perform the operating system preparation steps before installing any middleware.

Middleware installation on Solaris

Some of the default kernel configuration parameters on Solaris might not be
sufficient to run IBM DB2 9.7.

Ensure that your Solaris system includes required kernel parameters by running
the db2osconf utility after you install IBM DB2, but before you create any database
objects.
Related information:
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp

HP-UX
In order for IBM DB2 9.7 to run correctly on HP-UX, certain group membership
requirements must be addressed following the installation of IBM DB2.

After IBM DB2 9.7 is installed, you must ensure that the root user is assigned as a
member of the db2iadm1 group.

Run the db2osconf utility to ensure that your HP-UX system has required kernel
parameters in place. This utility must be run after you install IBM DB2, but before
you create any database objects.

© Copyright IBM Corp. 2012 269

 Related information:
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp

Installing the components

After the operating system is configured as needed, install the middleware
components.

Middleware components are installed in the following order:

1. IBM DB2
2. IBM Tivoli Directory Server
3. IBM WebSphere Application Server Network Deployment
4. IBM HTTP Server

Note: The media or web site you use to install middleware has directory-specific
locations for each supported operating system. The directory structure is
os/product.

These commands display the contents of the os/product directory.

cd os
ls

Within each os subdirectory are the installation directories for each middleware
product.
ls solaris
DB2-ESE_9.7_FP3a
TIV-DirectoryServer_6.3
WS-ESS_6.2.1
WS-WAS_IHS_7.0_FP15
WS-WAS_ND_7.0_Custom_FP15
WS-WAS_ND_7.0_Supplemental
WS-WAS_Plugins_7.0_FP15
WS-WAS_UpdateInstaller_7.0.0.15

Installing DB2
Run the db2setup program to install DB2.

Before you begin

Before you install DB2, review the requirements.

There are a number of things you must check to ensure a successful installation.
Before you start the DB2 setup wizard, consider the following prerequisite
conditions:
v If you choose to automate database configuration when you install SmartCloud
Control Desk, the user maximo is typically created for you on the system that
hosts the database server. For Solaris and HP-UX systems, you must manually
create the user even if the SmartCloud Control Desk installation program
configures the database automatically. Before you install SmartCloud Control
Desk, ensure that you create the maximo user on the database server.
v db2setup starts a wizard installer so X Window System must be installed and
running before you start the DB2 installer program. Export your display:
export DISPLAY= your_ip_address:0

270 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

v If NIS, NIS+, or similar security software is used in your environment, you must
manually create the required DB2 users, before you start the DB2 setup program.
See the centralized user-management considerations topic in the DB2
information center, before you begin.
v In general, you can choose to defer some installation activities. For example, if
you choose to not set up email notifications of database events at installation
time. If you want to defer specific installation activities, select that option, and
configure them later.
v Some middleware products have specific requirements or conventions for
account names and other settings. Override the installation defaults as shown if
the defaults provided are not satisfactory. On panels that prompt for passwords,
both the password and its confirmation entry must be specified before the
installer can continue to the next panel.

About this task

This procedure describes how to perform a typical installation of DB2 on a single

computer. If you want to install DB2 components on multiple computers, see the
DB2 information center for those instructions.

Databases must contain a single partition and Unicode data (UTF-8).

DB2 is installed, by default, in the /opt/IBM/db2/V9.7 directory.

The /opt/IBM/db2/V9.7/logs directory contains a db2install.history file. This file

contains the installation settings used, and errors that occurred during the
installation process. The vmrfis.history file contains information about
maintenance that has been applied to DB2, such as fix packs that have been
installed.

The db2setup.log file captures all DB2 installation information including errors.
The db2setup.err file captures any error output that is returned by Java (for
example, exceptions and trap information). By default, both logs are created in the
/tmp directory unless you change that location during the installation process.

Procedure
1. Log in as root.
2. Copy the DB2 Enterprise Server Edition tar file to a writable disk.
For Solaris
Copy solaris/DB2-ESE_9.7_FP3a/v9.7fp3a_sun64_server.tar.gz
For HP-UX
Copy hpux-ia64/DB2-ESE_9.7_FP3a/v9.7fp3a_hpipf64_server.tar.gz
3. Change to the directory where you copied the compressed file and
uncompress it.
4. Extract the file DB2_Enterp_Svr_OEM_Activation.zip into an appropriate
directory. For example, for Solaris, solaris/DB2-ESE_9.7/
5. Start the installer. Type ./db2setup.
6. From the launchpad, select Install a Product.
7. Click Install New.
8. Accept the license agreement.
9. In general, accept all defaults, except where you must provide custom values.
For example, the email address of the recipient of email notifications of

Chapter 18. Middleware on Solaris and HP-UX 271

 database events defaults to host name@local_server_name. This value must be
changed to a valid email address if you choose to enable SMTP notifications.
This value can also be changed at a later time.
10. Leave the check boxes for the GUI and UID options selected; the system
assigns them for you.
11. On the Start copying files and create response file panel, click Finish to initiate
the installation.
12. Start the DB2 instance.
13. Register the DB2 server license:
a. Extract the license file.
b. Use the DB2 license management tool command to apply the license:
DB2_HOME/adm/db2licm -a full path to the license file

The license file can be found in the appropriate folder for your operating
system. For Solaris, the license file is in solaris/DB2-ESE_9.7/
DB2_Enterp_Svr_OEM_Activation/db2/license/db2ese_o.lic.
c. Stop and then restart the DB2 instance by using the db2stop and db2start
commands.
d. Verify that the license was installed successfully:
DB2_HOME/adm/db2licm -l

This command results in output like the following information:

Product name: "DB2 Enterprise Server Edition"
License type: "Restricted"
Expiry date: "Permanent"
Product identifier: "db2ese"
Version information: "9.7"

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/
com.ibm.db2.luw.qb.server.doc/doc/r0007059.html

Installing IBM Tivoli Directory Server on Solaris

You typically install IBM Tivoli Directory Server on a computer that does not host
other middleware products.

Procedure
1. Login as root.
2. Copy the tar files for IBM Tivoli Directory Server to a writable disk. For
Solaris, copy the tds63-solaris-sparc-base.tar and tds63-solaris-sparc-
gskit.tar files from solaris64/TIV-DirectoryServer_6.3.
3. Unpack the files:
tar -xvf tds63-solaris-sparc-base.tar
tar -xvf tds63-solaris-sparc-gskit.tar
4. Change to the /tdsV6.3/tds directory and then type ./install_tds.bin
If you prefer, you can specify a temporary directory other than the system
temporary directory. Change to the appropriate directory and type the
following command at a command prompt:
./install_tds.bin -is:tempdir directory

272 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 . The variable directory is the directory you want to use for temporary space.
Be sure that you have at least 400 MB of free space in this directory. For
example:
./install_tds.bin -is:tempdir /opt/tmp
5. When the installation wizard starts, select a language to use for the
installation process, accept the license agreement, and choose a Custom
installation.
6. Select the Proxy Server, Server, C Client, Java Client, and Web
Administration Tool options, and then click Next.
7. Select Do not specify. I will manually deploy at a later time, then click Next.
8. Click Install.
9. Close the Instance Administration tool.
10. Click Finish.
11. Create the idsccmdb instance.
12. Start the directory server, type the following commands:
a. /opt/ibm/ldap/V6.3/sbin/idsdiradm -I idsccmdb
b. /opt/ibm/ldap/V6.3/sbin/idsdirctl -D admin user ID -w admin user
password

Installing WebSphere Application Server Network Deployment

You must install WebSphere Application Server Network Deployment and create
two profiles that are required at a later stage.

Procedure
1. Login as root.
2. Copy the WebSphere Application Server compressed file to a writable disk.
The file is in the WS-WAS_ND_7.0_Custom_FP15 directory.
v For Solaris, copy the WS-WAS_ND_7.0_Custom_FP15/WAS-ND_Solaris-Sparc-
Custom_v7015.tar.gz file.
v For HP-UX, copy the WS-WAS_ND_7.0_Custom_FP15/WAS-
ND_HpuxIA64_Custom_v7015.tar.gz file.
3. Uncompress and unpack the file:
gzip -dfv filename.gz | tar xvf -
4. Remove the compressed files.
5. Change to the directory where you unpacked the tar file.
6. Change to the WAS directory.
7. Type ./install
8. Proceed through the initial panels, accepting the license agreement. Accept
defaults provided unless you have a specific reason to change them.
9. On the Installation directory panel, accept the default installation directory.
The default directory is /opt/IBM/WebSphere/AppServer.
If you change the installation directory, do not use symbolic links as the
destination directory and do not add space characters to the path.
10. From the WebSphere Application Server Network Deployment environments
panel, select None as your environment, and then click Next.
Selecting None means that you plan to create the deployment cell,
deployment manager profile, and the application server profile with the
profile management tool.
11. Click Yes to indicate that you want to proceed.

Chapter 18. Middleware on Solaris and HP-UX 273

 12. Advance to the end of the installation and click Finish.

Creating WebSphere Application Server Network Deployment

profiles
When manually installing WebSphere Application Server Network Deployment,
profiles must be created before starting the SmartCloud Control Desk installation.
The 64-bit version of WebSphere Application Server Network Deployment includes
the manageprofiles command-line tool which you use to create profiles.

Before you begin

Ensure that you are familiar with the character limitations for commands or the
shell you are using. In some cases, you might have to enter commands in order to
avoid exceeding these limitations. See WebSphere Application Server Network
Deployment product documentation for more information about entering lengthy
commands on more than one line.

You cannot use the Profile Management tool to create WebSphere Application
Server Network Deployment v7.0 profiles for 64-bit platforms. You must use the
manageprofiles command-line tool.

About this task

The following commands can be useful for managing profiles:

Table 34. Profile commands
Task
Delete a profile
Refresh the profile registry (for example,
after deleting a profile)
List existing profiles
Command
WAS_HOME/bin/manageprofiles.[sh|bat]
-delete -profileName profile name
WAS_HOME/bin/manageprofiles.[sh|bat]
-validateAndUpdateRegistry
WAS_HOME/bin/manageprofiles.[sh|bat]
-listProfiles

WAS_HOME is equal to where WebSphere Application Server Network

Deployment is installed, for example, /opt/IBM/WebSphere/AppServer/ or
C:\Program Files\IBM\WebSphere\AppServer\

To create WebSphere Application Server Network Deployment profiles, follow

these steps:

Procedure
1. Source the setupCmdLine.[sh|bat] script in the bin directory of the WAS_HOME
folder to set the WebSphere Application Server Network Deployment
environment to the configuration instance. WAS_HOME is typically in
/opt/IBM/WebSphere/AppServer or C:\Program Files\IBM\WebSphere\
AppServer\.
2. Create a profile ports file for the ctgDmgr01 profile. This file is used with the
manageprofiles command to set the ports used by this profile.

Note: It is important that you ensure no spaces appear after any value in this
file. This circumstance can sometimes occur when cutting and pasting an
example. If there is an extra space trailing any of the values WebSphere uses
that space as the last character of that value. For example, you specify the

274 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 value WC_adminhost=9060, but an extra space is typed after 9060. The value is
interpreted as WC_adminhost=9060&ltsp> (where <sp> represents a space
character).
a. Open a new text file named _portdef_DMgr.props and enter the following
text:
CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=9403
WC_adminhost=9060
DCS_UNICAST_ADDRESS=9352
BOOTSTRAP_ADDRESS=9809
SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=9401
CELL_DISCOVERY_ADDRESS=7277
SOAP_CONNECTOR_ADDRESS=8879
ORB_LISTENER_ADDRESS=9100
CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=9402
WC_adminhost_secure=9043
b. Place the file in the WAS_HOME directory.
3. Create the ctgDmgr01 profile using the manageprofiles command. Type the
following command, all on one line, with a space between each entry:
WAS_HOME/bin/manageprofiles.[sh|bat]
-create
-templatePath WAS_HOME/profileTemplates/dmgr
-hostName yourfullyqualifiedhost
-profileName ctgDmgr01
-profilePath WAS_HOME/profiles/ctgDmgr01
-portsFile WAS_HOME/_portdef_DMgr.props
-cellName ctgCell01
-nodeName ctgCellManager01
-enableAdminSecurity "false"
4. Start the ctgDmgr01 server:
WAS_HOME/profiles/ctgDmgr01/bin/startManager.[sh|bat]
5. Create a profile ports file for the ctgAppSrv01 profile. This file is used by the
manageprofiles command to set the ports that are used by this profile.
a. Open a new text file named _portdef_AppSvr.props and enter the
following text:
CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=9201
DCS_UNICAST_ADDRESS=9353
NODE_DISCOVERY_ADDRESS=7272
NODE_IPV6_MULTICAST_DISCOVERY_ADDRESS=5001
BOOTSTRAP_ADDRESS=2809
SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=9901
SOAP_CONNECTOR_ADDRESS=8878
NODE_MULTICAST_DISCOVERY_ADDRESS=5000
ORB_LISTENER_ADDRESS=9101
CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=9202
b. Place the file in the WAS_HOMEdirectory.
6. Create the ctgAppSrv01 profile using the manageprofiles command:
WAS_HOME/bin/manageprofiles.[sh|bat]
-create
-templatePath WAS_HOME/profileTemplates/managed
-hostName yourfullyqualifiedhost
-profileName ctgAppSrv01
-profilePath WAS_HOME/profiles/ctgAppSrv01
-cellName ctgNodeCell01
-nodeName ctgNode01
-portsFile WAS_HOME/_portdef_AppSvr.props
-dmgrHost yourfullyqualifiedhost
-dmgrPort 8879
-isDefault
7. Start the ctgAppSrv01 node.

Chapter 18. Middleware on Solaris and HP-UX 275

 WAS_HOME/profiles/ctgAppSrv01/bin/startNode.[sh|bat]
8. Augment the ctgDmgr01 profile:
WAS_HOME/bin/manageprofiles.[sh|bat]
-augment
-templatePath WAS_HOME/profileTemplates/iscae71
-profileName ctgDmgr01
-serverName dmgr
9. Restart servers.
WAS_HOME/profiles/ctgDmgr01/bin/stopManager.[sh|bat]
WAS_HOME/profiles/ctgDmgr01/bin/startManager.[sh|bat]
WAS_HOME/profiles/ctgAppSrv01/bin/stopNode.[sh|bat]
WAS_HOME/profiles/ctgAppSrv01/bin/startNode.[sh|bat]
10. Start firststeps.[sh|bat] and select the Installation Verification option to
confirm that your server has been properly installed and started.
WAS_HOME/profiles/ctgDmgr01/firststeps/firststeps.[sh|bat]
“Manually configuring Virtual Member Manager on WebSphere Application
Server Network Deployment”
Some deployment environments require the manual configuration of Virtual
Member Manager to secure SmartCloud Control Desk.

Manually configuring Virtual Member Manager on WebSphere

Application Server Network Deployment
Some deployment environments require the manual configuration of Virtual
Member Manager to secure SmartCloud Control Desk.

Before you begin

For a review of SmartCloud Control Desk security options, see the security
planning information in this document.

Important: Before you begin this procedure, ensure that you have a wasadmin
user created in your LDAP repository.

If you intend to configure Virtual Member Manager to use SSL with a federated
LDAP repository, it must be done only after a successful SmartCloud Control Desk
installation. If Virtual Member Manager is configured to use SSL with a federated
LDAP repository before completing the SmartCloud Control Desk installation, the
installation fails. Do not configure a Virtual Member Manager LDAP federated
repository to use SSL with an LDAP directory before installing SmartCloud Control
Desk. Configure SSL after the SmartCloud Control Desk installation program has
completed successfully.

About this task

During the installation process, the SmartCloud Control Desk installation program
provided you with the option of automatically configuring SmartCloud Control
Desk middleware. If you elected to have the SmartCloud Control Desk installation
program automatically configure SmartCloud Control Desk middleware, then it
will, among other tasks, perform Virtual Member Manager configuration for you. If
you elected to manually configure SmartCloud Control Desk middleware for use
with SmartCloud Control Desk, you must manually configure Virtual Member
Manager.

Virtual Member Manager provides you with the ability to access and maintain user
data in multiple repositories, and federate that data into a single virtual repository.
The federated repository consists of a single named realm, which is a set of

276 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

independent user repositories. Each repository can be an entire external repository
or, in the case of LDAP, a subtree within that repository. The root of each
repository is mapped to a base entry within the federated repository. The root is a
starting point within the hierarchical namespace of the virtual realm.

To add an LDAP directory to the Virtual Member Manager virtual repository, you
must first add the LDAP directory to the list of repositories available for
configuration for the federated repository. You must then add the root of
baseEntries to a search base within the LDAP directory. Multiple base entries can
be added with different search bases for a single LDAP directory.

The values provided here are example purposes only. If you are using IBM Tivoli
Directory Server, enter the values used during the installation and configuration of
IBM Tivoli Directory Server. If you are configuring Virtual Member Manager to use
Microsoft Active Directory, substitute values where appropriate in this procedure.
You must modify the VMMCRONTASK accordingly.

To add the IBM Tivoli Directory Server or Microsoft Active Directory to VMM,
complete the following steps:

Procedure
1. Start the WebSphere Application Server Network Deployment application
server.
2. Start Internet Explorer and open the WebSphere Application Server Network
Deployment administrative console by typing the following URL:
http://<server_name>:<port_number>/ibm/console
For example, enter a URL like the following sample URL:
http://localhost:9060/ibm/console
3. At the login screen, enter your user ID, then click Log in. This action opens
the Welcome screen for the WebSphere Application Server Network
Deployment administrative console.
4. Select Security > Secure administration, applications, and infrastructure.
5. Locate the User account repository area and pick Federated repositories from
the Available realm definition field, and then click Configure.
6. Click Manage repositories, located under Related Items.
7. Click Add to create new repository definition under the current default realm.
8. Enter the following values, click Apply, and then click Save.
Repository identifier
For IBM Tivoli Directory Server, enter ISMITDS.
For Microsoft Active Directory, enter ISMMSAD .
Directory type
For IBM Tivoli Directory Server, select IBM Tivoli Directory Server.
For Microsoft Active Directory, select Microsoft Windows Server 2003
Active Directory.
Primary host name
Enter the fully qualified host name or IP address of the directory
server.
Port Enter 389.
Support referrals to other LDAP servers
Set this value to ignore.

Chapter 18. Middleware on Solaris and HP-UX 277

 Bind distinguished name
For IBM Tivoli Directory Server, enter cn=root.
For Microsoft Active Directory, enter
CN=Administrator,CN=Users,DC=ism75,DC=com.
Bind password
Enter the password for the bind distinguished name.
Login properties
Leave this value blank.
Certificate mapping
Select EXACT_DN
9. Return to the Federated repositories panel by clicking Security > Secure
administration, applications, and infrastructure, selecting Federated
repositories from the Available realm definitions menu, and then clicking
Configure.
10. Locate the Repositories in the realm area and click Add Base entry to Realm.
If there is an existing file repository entry in the Repositories in the realm
table, you must select it click Remove. Save the change after creating the
entry.
11. Enter the following values, click Apply, and then click Save.
Repository
For IBM Tivoli Directory Server, select ISMITDS.
For Microsoft Active Directory, select ISMMSAD .
Distinguished name of a base entry that uniquely identifies this set of
entries in the realm
For IBM Tivoli Directory Server, enter ou=SWG,o=IBM,c=US.
For Microsoft Active Directory, enter DC=ism75,DC=com.
Distinguished name of a base entry in this repository
For IBM Tivoli Directory Server, enter ou=SWG,o=IBM,c=US.
For Microsoft Active Directory, enter DC=ism75,DC=com.
12. From the Federated repositories configuration area, enter the following values,
click Apply, and then click Save:
Realm name
Enter ISMRealm.
Primary administrative user name
Enter wasadmin. This value must be a valid user from the configured
LDAP repository.
Server user identity
Select Automatically generated server identity.
Ignore case for authorization
Select this check box.
13. Click Supported entity types, and then click PersonAccount.
14. From the PersonAccount configuration area, enter the following values:
Entity type
Verify that the value is PersonAccount.
Base entry for the default parent
For IBM Tivoli Directory Server, enter ou=users,ou=SWG,o=IBM,c=US.

278 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 For Microsoft Active Directory, enter CN=Users,DC=ism75,DC=com.
Relative Distinguished Name properties
Enter uid.
15. Click OK and then click Save.
16. Click Supported entity types, and then click Group.
17. From the Group configuration area, enter the following values:
Entity type
Verify that the value is Group.
Base entry for the default parent
For IBM Tivoli Directory Server, enter ou=groups,ou=SWG,o=IBM,c=US.
For Microsoft Active Directory, enter
ou=groups,CN=Groups,DC=ism75,DC=com.
Relative Distinguished Name properties
Enter cn.
18. Click OK and then click Save.
19. Click Supported entity types, and then click OrgContainer.
20. From the OrgContainer configuration area, enter or verify the following
values:
Entity type
Verify that the value is OrgContainer.
Base entry for the default parent
For IBM Tivoli Directory Server, enter ou=SWG,o=IBM,c=US.
For Microsoft Active Directory, enter DC=ism75,DC=com.
Relative Distinguished Name properties
Enter o;ou;dc;cn.
21. Click OK and then click Save.
22. Browse to Security > Secure administration, applications, and infrastructure.
23. From the Secure administration, applications, and infrastructure configuration
page, complete the following:
a. Enable Enable administrative security.
b. Enable Enable application security.
c. Clear the option for Use Java 2 security to restrict application access to
local resources.
d. From Available realm definition, select Federated repositories.
e. Click Set as current.
24. Click Apply, and then click Save.
25. Restart WebSphere Application Server Network Deployment and the managed
nodes by running the following commands:
a. <WAS_HOME>\profiles\ctgDmgr01\bin\stopManager.bat
b. <WAS_HOME>\profiles\ctgAppSrv01\bin\stopNode.bat
c. <WAS_HOME>\profiles\ctgDmgr01\bin\startManager.bat
d. <WAS_HOME>\profiles\ctgAppSrv01\bin\startNode.bat

Note: Substitute UNIX path and file extension values where appropriate.

Chapter 18. Middleware on Solaris and HP-UX 279

 “Performing WebSphere Application Server Network Deployment configuration
tasks” on page 91
Use this procedure to perform WebSphere Application Server Network
Deployment configuration tasks.
“Preparing Microsoft Active Directory for reuse” on page 58
An existing Microsoft Active Directory instance can be used to secure
WebSphere Application Server Network Deployment. The middleware
installation program can be used to validate Microsoft Active Directory
configuration information.
“Manually configuring Microsoft Active Directory” on page 87
You can manually configure Microsoft Active Directory for use with
SmartCloud Control Desk.

Installing the WebSphere update installer

This procedure uses the update installer to apply maintenance. \

Before you begin

Complete documentation for the update installer is at http://

publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/
com.ibm.websphere.base.doc/info/aes/ae/tins_updi_install.html. Review the
prerequisites before you install the update installer.

About this task

The update installer simplifies maintenance of WebSphere Application Server

Network Deployment and related components. These components include things
such as the HTTP server plug-in and fix packs.

Procedure
1. Copy the update installer compressed file to a writable disk. The file is in the
WS-WAS_UpdateInstaller_7.0.0.15 directory.
v For Solaris, copy the 7.0.0.15-WS-UPDI-SolarisSparc64.tar.gz file.
v For HP-UX, copy the 7.0.0.15-WS-UPDI-HpuxIA64.tar.gz file.
2. Uncompress the file. Type unzip fileName.zip.
3. Change to the directory that contains the uncompressed files and type
./install.
4. Accept the license agreement.
5. The default installation directory is opt/IBM/WebSphere/UpdateInstaller.
Change this value if required; otherwise accept the default location.
6. Before you finish the installation, clear the option to Launch IBM Update
Installer for WebSphere software on exit.

Installing and configuring IBM HTTP Server

This procedure provides task information for manually installing and configuring
IBM HTTP Server.

Procedure
1. Log on as root, on the system where you installed WebSphere Application
Server Network Deployment.
2. Log in to the administrative console. Ensure the ctgDmgr01 deployment
manager is running and that the SOAP port is set to listen at the correct port
(8879 is the default).

280 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 If the deployment manager must be started, use the following command:
<WAS_HOME>/profiles/ctgDmgr01/bin/startManager.sh
3. Copy the IBM HTTP Server compressed file to a writable disk.
For Solaris
Copy solaris64/WS-WAS_ND_7.0_Supplemental/C1G3IML.tar.gz
For HP-UX
Copy hpux-ia64/WS-WAS_ND_7.0_Supplemental/C1G2XML.tar.gz
4. Uncompress the C1G3IML.tar.gz or C1G2XML.tar.gz file.
5. Extract the contents of the C1G3IML.tar or C1G2XML.tar file.
6. Change to the IHS directory and start the installation program:
./install
7. From the Welcome panel, click Next.
8. Accept the license agreement and click Next to display the installation root
directory panel.
9. From the System prerequisites check panel, click Next.
10. Specify the installation location, the default is /opt/IBM/HTTPServer, and click
Next.
11. From the Port Values Assignment panel, specify the following values, and
click Next.
HTTP Port
80
HTTP Administration Port
8008
12. From the HTTP Administration Server Authentication panel, specify the
following values, and click Next.
Create a user ID for IBM HTTP administration server authentication
Enable this option by selecting this check box.
User ID
Specify wasadmin
Password
Specify the password for the wasadmin user.
13. From the Setup HTTP Administration Server panel, specify the following
values, and click Next.
Set up IBM HTTP administration server to administer IBM HTTP Server
Enable this option by selecting this check box.
Create a unique user ID and group for IBM HTTP Server administration
Enable this option by selecting this check box.
User ID
Specify wasadmin.
Group Specify ihsadmin
14. From the IBM HTTP Server plug-in for WebSphere Application Server panel,
specify the following values, and click Next.
Install the IBM HTTP Server plug-in for IBM WebSphere Application
Server Enable or clear this check box to disable this option as is appropriate
for your configuration. In an environment where you have multiple
deployment manager profiles, it is more practical to run the web
server plug-ins installation task separately. This task is done by

Chapter 18. Middleware on Solaris and HP-UX 281

 running the plug-in installation program after exiting the IBM HTTP
Server installation program. However, if your WebSphere environment
only contains a single deployment manager profile, you can leave the
WebSphere plug-in option selected. When it is selected, the web server
plug-ins installation task starts when you click Next.
If you decide to install the IBM HTTP Server plug-in now, you must
configure it. Perform the following steps to configure the plug-in.
a. Stop and start the deployment manager:
WAS_HOME/profiles/ctgDmgr01/bin/stopManager.sh
WAS_HOME/profiles/ctgDmgr01/bin/startManager.sh
b. Copy the /opt/IBM/HTTPServer/Plugins/bin/configurewebserver1.sh file
to WAS_HOME/bin/
c. Change directory to WAS_HOME/bin and then use the following command:
./configurewebserver1.sh
d. Start the IBM HTTP Server servers:
/opt/IBM/HTTPServer/bin/adminctl start
/opt/IBM/HTTPServer/bin/apachectl start
e. Log in to the WebSphere administrator console and ensure that webserver1
has started.
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/
com.ibm.websphere.ihs.doc/info/welcome_ihs.html

Installing IBM HTTP Server fix packs:

IBM HTTP Server fix pack must be installed. This fix pack updates the base
installation of the IBM HTTP Server to the latest maintenance level.

Procedure
1. Copy the fix pack file to the /opt/IBM/HTTPServer/maintenance directory.
Create this directory if it does not exist.
v For Solaris, copy the solaris/WS-WAS_IHS_7.0_FP15/7.0.0-WS-IHS-
SolarisSparc64-FP0000015.pak file.
v For HP-UX, copy the hpux-ia64/WS-WAS_IHS_7.0_FP15/7.0.0-WS-IHS-
HpuxIA64-FP0000015.pak file.
2. Stop IBM HTTP Server. Type /opt/IBM/HttpServer/bin/apachectl stop.
3. Stop the admin server. Type /opt/IBM/HttpServer/bin/adminctl stop.
4. Stop WebSphere Application Server and the managed nodes using the
following commands.
a. WAS_HOME/profiles/ctgAppSrv01/bin/stopNode.sh
b. WAS_HOME/profiles/ctgDmgr01/bin/stopManager.sh
5. Install the fix pack.
a. Start the update installer wizard:
/opt/IBM/WebSphere/UpdateInstaller/update.sh
b. Click Next.
c. From the Product Selection panel, select the IBM HTTP Server directory by
browsing to the /opt/IBM/HTTPServer directory, and then clicking Next.
d. From the Maintenance Operation Selection panel, select Install maintenance
package, and then click Next.

282 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 e. From the Maintenance Package Directory Selection panel, browse to the
/opt/IBM/HTTPServer/maintenance directory, and then click Next.
f. From the Available Maintenance Package to Install panel, click Select
Recommended Updates, select the target update, and click Next.
g. On the Installation Summary screen, click Next to begin the installation of
the critical fixes.
6. Start IBM HTTP Server. Type /opt/IBM/HTTPServer/bin/apachectl start.
7. Start the admin server. Type /opt/IBM/HTTPServer/bin/adminctl start.
8. Restart WebSphere Application Server and the managed nodes:
a. WAS_HOME/profiles/ctgDmgr01/bin/startManager.sh
b. WAS_HOME/profiles/ctgAppSrv01/bin/startNode.sh

Installing the WebSphere plug-in

This procedure provides task information for manually installing and configuring
WebSphere plug-in for IBM HTTP Server. This procedure is optional if you chose
to install and configure the WebSphere plug-in when you installed the IBM HTTP
Server.

Procedure
1. Logon as root to the system where you WebSphere is installed.
2. Change to the directory where you previously extracted the C1G3IML or
C1G2XML tar file (when you installed IBM HTTP Server). For example, for
Solaris, this path might be solaris64/WS-WAS_ND_7.0_Supplemental/plugin.
3. Change to the plugin directory.
4. From a command line, start the WebSphere plug-in installation program.
./install
5. On the Welcome panel, clear the option to learn more about the Installation
roadmap: Overview and installation scenarios. Click Next.
6. Accept the license agreement and click Next.
7. From the plug-in selection panel, select the IBM HTTP Server V7 plug-in, and
then click Next.
8. From the installation scenario panel, select WebSphere Application Server
machine (local), and then click Next.
9. Accept or change the installation directory; the default is /opt/IBM/
HTTPServer/Plugins because you chose to install after exiting the installation
for IBM HTTP Server. Click Next.
10. Specify the location where you installed the application server; the default is
/opt/IBM/WebSphere/AppServer. Click Next.
11. From the select profile panel, select ctgDmgr01 from the list, and then click
Next.
12. From the web server configuration file panel, specify the following
information:
Select the existing IBM HTTP Server httpd.conf file
Browse to the location of the httpd.conf file; the default is
/opt/IBM/HTTPServer/conf/httpd.conf.
Specify the Web server port
The default is port 80.

Chapter 18. Middleware on Solaris and HP-UX 283

 Clicking Next might produce warning message that indicates that the selected
IBM HTTP Server configuration file already contains plug-in entries. If you
proceed, this configuration file is updated with a new plugin-cfg xml file
location. You can click OK to proceed.
13. From the web server definition panel, specify a unique web server definition
name; the default name (webserver1) is satisfactory.
14. Accept the default web server plug-in configuration file name
(plugin-cfg.xml) and location.
15. Click Next to acknowledge the manual configuration steps.
16. From the installation summary panel, click Next.
17. When the installation is complete, click Finish.
18. Stop and start the deployment manager:
WAS_HOME/profiles/ctgDmgr01/bin/stopManager.sh
WAS_HOME/profiles/ctgDmgr01/bin/startManager.sh
19. Copy the /opt/IBM/HTTPServer/Plugins/bin/configurewebserver1.sh file to
WAS_HOME/bin/
20. Change directory to <WAS_HOME>/bin and then run the following command:
./configurewebserver1.sh
21. Start the IBM HTTP Server servers:
/opt/IBM/HTTPServer/bin/adminctl start
/opt/IBM/HTTPServer/bin/apachectl start
22. Login to the WebSphere administrator console and ensure that webserver1 is
started.

Installing WebSphere Application Server Network Deployment plug-in fix

packs:

The WebSphere Application Server Network Deployment plug-in fix pack 17 is

required. This task updates the base installation of the plug-in to the latest
maintenance level.

Procedure
1. Copy the fix pack file to the /opt/IBM/WebSphere/UpdateInstaller/maintenance
directory. Create this directory if it does not exist.
v For Solaris, copy the solaris64/WS-WAS_Plugins_7.0_FP17/7.0.0-WS-PLG-
SolarisSparc64-FP0000017.pak file.
v For HP-UX, copy the hpux-ia64/WS-WAS_Plugins_7.0_FP17/7.0.0-WS-PLG-
HpuxIA64-FP0000017.pak file.
2. Stop the IBM HTTP Server. Type /opt/IBM/HTTPServer/bin/apachectl stop.
3. Stop WebSphere Application Server Network Deployment and the managed
nodes. Use the following commands.
a. WAS_HOME/profiles/ctgAppSrv01/bin/stopNode.sh
b. WAS_HOME/profiles/ctgDmgr01/bin/stopManager.sh
4. Install the fix pack.
a. Launch the update installer wizard:
/opt/IBM/WebSphere/UpdateInstaller/update.sh
b. Click Next.
c. From the Product Selection panel, select the IBM HTTP Server Plugin
directory by browsing to the /opt/IBM/HTTPServer/Plugin directory, and
then clicking Next.

284 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 d. From the Maintenance Operation Selection panel, select Install maintenance
package, and then click Next.
e. From the Maintenance Package Directory Selection panel, browse to the
/opt/IBM/WebSphere/UpdateInstaller/maintenance directory, and then click
Next.
f. From the Available Maintenance Package to Install panel, click Select
Recommended Updates, select the target update, and click Next.
g. On the Installation Summary screen, click Next to begin the installation of
the critical fixes.
5. Start the IBM HTTP Server. Type /opt/IBM/HTTPServer/bin/apachectl start
6. Restart WebSphere Application Server Network Deployment and the managed
nodes:
a. WAS_HOME/profiles/ctgDmgr01/bin/startManager.sh
b. WAS_HOME/profiles/ctgAppSrv01/bin/startNode.sh

Configuring Virtual Member Manager on IBM WebSphere Application

Server Network Deployment
Virtual Member Manager (VMM) provides you with the ability to access and
maintain user data in multiple repositories. You can also federate that data into a
single virtual repository.

Before you begin

Before configuring VMM, you might consider creating a system backup image.
Having a backup allows you to restore the system to a pre-VMM state. If you
chosoe to relocate your LDAP data in the future, you can reconfigure VMM to use
a different LDAP server

About this task

See “Manually configuring Virtual Member Manager on WebSphere Application

Server Network Deployment” on page 276 to add an IBM Tivoli Directory Server
repository to VMM. This task is required and must be performed.

The federated repository managed by VMM consists of a single named realm,

which is a set of independent user repositories. Each repository can be an entire
external repository or, in the case of LDAP, a subtree within that repository. The
root of each repository is mapped to a base entry within the federated
repository. The root is a starting point within the hierarchical namespace of the
virtual realm.

Procedure
1. To add an LDAP directory to the VMM virtual repository, you must first add
the LDAP directory to the list of repositories. This list consists of the
repositories that are available for configuration for the federated repository.
2. Add the root of baseEntries to a search base within the LDAP directory.
Multiple base entries can be added with different search bases for a single
LDAP directory.

Chapter 18. Middleware on Solaris and HP-UX 285

286 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Chapter 19. Backup and restoration
Like all important business data, it is a good idea to establish a process and
schedule for backing up SmartCloud Control Desk data.

Back up and restore middleware application data using the methods described in
the documentation for that product is important. Also, establish a process for
backing up data contained on the SmartCloud Control Desk administrative
workstation.

The default installation directory on the SmartCloud Control Desk administrative

workstation is C:\ibm. This directory contains the critical files for your SmartCloud
Control Desk deployment, which includes all class files and customizations that
have been performed in your environment, the current Enterprise Archive (EAR)
file, and the properties files and installation tools used for your environment. Plan
to back up SmartCloud Control Desk administrative workstation data just after
initial deployment and schedule periodic backups on an ongoing basis.

Backing up the administrative workstation

It is recommended that you back up all SmartCloud Control Desk middleware
applications and SmartCloud Control Desk administrative workstation on a regular
basis.

About this task

The default installation directory on the administrative workstation is C:\ibm. This

directory contains the critical files for your SmartCloud Control Desk deployment.

Specifically, the administrative workstation contains the following items:

v Class files and customizations performed in your environment.
v The current Enterprise Archive (EAR) file that was deployed to the application
server..
v The properties files and installation tools used for your environment.

It is important to make a back up of the database at the same time that you back
up the administrative workstation. During restoration, you restore the database
back up at the same time you restore the administrative workstation back up it
was paired with.

To back up critical SmartCloud Control Desk information, complete the following

steps:

Procedure
1. Back up the SmartCloud Control Desk database, J2EE server, and
authentication server information using the instructions provided by your
middleware vendors.
2. Create a backup of the installation directory. By default, this directory is
C:\IBM\SMP. Ensure that all file permissions are preserved.

© Copyright IBM Corp. 2012 287

Restoring the administrative workstation
This section details how to restore previously backed up SmartCloud Control Desk
administrative workstation information to a Windows workstation. This
information can be used to return an existing SmartCloud Control Desk
administrative workstation to a previous state.

Before you begin

It is important to restore the back up of the database that was made when you
backed up the administrative workstation. A database back up should be restored
with the administrative workstation back up it was paired with.

About this task

To restore SmartCloud Control Desk information to an administrative workstation,

complete the following steps:

Procedure
1. Restore the database back up that was paired with the administrative
workstation back up you are restoring.
2. Log on to the target administrative system with the same user ID that was used
to install the product on the existing administrative workstation.
3. Copy the SmartCloud Control Desk installation files and directories to the file
system of the target administrative system. You must maintain the directory
structure of the original installation. For example, if the SmartCloud Control
Desk installation directory on the existing administrative system is C:\IBM\SMP,
you cannot copy those files to a C:\NewAdminWS\IBM\SMP directory on the target
administrative workstation.

Installation properties
Installation properties are recorded in properties files during a deployment and are
used as input by future install-related actions. Installation properties are found in
the install.properties and maximo.properties files as well as the database. You
should only modify properties found in the install.properties file that are
related to host names or user IDs. Changing values for other properties can
severely impact your ability to perform future installation actions, upgrades and fix
pack installations.
Table 35. Installation properties
Category Property Definition
MAXIMO Properties Maximo.InstallLocation Install location of the maximo directory.

For example, C:\\IBM\\SMP\\maximo

mxe.db.user Database user that the server uses to attach
to the database server.

For example, maximo

mxe.db.schemaowner Owner of the database schema.

For example, maximo

This value must be dbo for Microsoft SQL

Server.

288 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 35. Installation properties (continued)
Category Property Definition
mxe.db.password Password for the database user name.
mail.smtp.host SMTP host server.
mxe.workflow.admin E-mail account of the workflow
administrator.
mxe.adminEmail Valid e-mail address used by workflows to
communicate with workflow participants.
mxe.name Name to bind the MXServer server object to
in the RMI registry.

For example, mxserver.

mxe.hostname Name of the machine and port hosting
MXServer.
mxe.rmi.port RMI communication port. If set at zero, RMI
uses any available port. You can select
another available port number.
mxe.registry.port The port number used to bind RMI/JRMP
communications.

For example, 13400.

The RMI registry is started by the first

instance of the maximo application to run.
An environment could have multiple
instances of the product application running.
This registry coordinates these instances.
There is a single central RMI registry server.
This value is the port available for the other
application instances to communicate with
the central server.
mxe.allowLocalObjects Set to true in production environments, to
improve system performance. Set to false for
development work, or for custom
applications.

The default is false.

mxe.useAppServerSecurity Indicates whether to use LDAP or native
authentication. Setting this value to 1
indicates you are using LDAP for security.
mxe.MLCacheLazyLoad By default, the multi-language metadata
cache loads one object at a time. Set this flag
to 1 to load all objects simultaneously for
one language.
mxe.UserLicenseKey The product enabler (license key) is used
during installation. If the product enabler
changes this value must be updated.
mxe.adminuserid The administrative user. Used by the server
for administrative tasks and to run cron
tasks. This user must have access to all Sites
in the system.
mxe.adminuserloginid Defines the default login user ID for the
product application.

The default value is maxadmin.

Chapter 19. Backup and restoration 289

Table 35. Installation properties (continued)
Category Property Definition
mxe.adminPasswd The password for the mxe.adminuserloginid
user.
mxe.system.reguser Self registration user. This user is
responsible for the process by which users
can create their own accounts.

The default value is maxreg.

mxe.system.regpassword User registration login password. This value
is the password for the user listed for
mxe.system.reguser.
mxe.email.charset The character set for e-mail notifications sent
from the product.

When this property is defined, it is the

mxe.reorder.previewtimeout
charset that is used to encode the subject
and message when an e-mail notification is
sent.
The reorder preview time out period (in
minutes). This value must be set to the same
value as the Web server session time out.

The default value is 30 minutes.

mxe.security.provider The security provider is obtained from the
policy file, which is normally
com.sun.crypto.provider.SunJCE.

To use a different provider, you can specify

a value for this parameter.
mxe.mbocount Displays the number of business objects
created by the server.

The default is 1. Changing the value to 0

disables this feature.
mxe.esig.defaultuserid Set this flag to true if you want the
Esignature login dialog to default to the
login ID.

The default value is true.

maximo.min.required.db.version Defines what the minimum level of database
is required for an upgrade. An example
value would be 7100.
mxe.encrypted Property used by the application to
determine if property files are encrypted.

This value is set to true if the file is

encrypted.
mxe.LDAPUserMgmt Indicates whether LDAP owns user
management when
mxe.userAppServerSecurity = 1.

The default value is 1.

SmartCloud Control CCMDB.InstallLocation Product install location.
Desk specific
Properties For example, C:\\IBM\\SMP.

290 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 35. Installation properties (continued)
Category Property
CCMDB.JREInstallLocation
CCMDB.SDKInstallLocation
CCMDB.PMP
CCMDB.Locale
CCMDB.BaseLanguage
CCMDB.AdditionalLanguages
CCMDB.DeploySampleData
CCMDB.UserShortcuts
CCMDB.InstallType
CCMDB.DeployEar
process automation BASE.DeployOptionalContent
engine specific
properties
BASE.DeployOptionalContentSet
BASE.VersionUpgradingFrom
WebSphere Application WAS.ThinClientInstallLocation
Server Network
Deployment Thin
Client specific
Properties
WAS.SOAPConnectorPort
Definition
JRE install location.
For example, C:\\IBM\\SMP\\JRE.
SDK install location.
For example, C:\\IBM\\SMP\\SDK.
Unused property.
The locale setting of the administrative
workstation system.
For example, en.
Base language that was set for the product.
For example, en.
Additional languages installed for the
product.
Binary value that determines whether
sample data is to be loaded during the
installation.
For example, false.
Location of the menu for process solution
installer and the product console shortcuts.
Type of installation, which includes fix pack,
upgrade, or new installation.
For example, Install.
Binary value that indicates if EAR files are
deployed during the installation.
For example, true.
Binary value that indicates if optional
content is deployed during the installation.
For example, true.
Indicates whether you selected to deploy
optional content during the initial upgrade.
This value, once set, is a fixed value and
cannot be changed. This value will be used
for all future upgrades and fix packs.
The previous version of process automation
engine that was installed.
WebSphere Application Server Network
Deployment thin client install location.
For example, C:\\IBM\\SMP\\WASClient.
SOAP port of the WebSphere Application
Server Network Deployment deployment
manager.
For example, 8879.
Chapter 19. Backup and restoration 291
Table 35. Installation properties (continued)
Category Property Definition
WAS.ThinClientFullyAutomatedConfig Binary value that indicates if the installation
program downloaded the keystore from the
WebSphere Application Server Network
Deployment deployment manager.

If this value is set to false, the user has to

copy it manually.
WAS.ThinClientLocalKeystore Location of the keystore file.

For example, C:\\ibm\\WebSphere\\

AppServer\\profiles\\ctgDmgr02\\etc\\
trust.p12.
WAS.Scripts.Location Location of scripts used by the installation
program.

For example, C:\\IBM\\SMP

WebSphere Application WAS.RMIConnectorPort RMI port on the WebSphere Application
Server Network Server Network Deployment deployment
Deployment RMI port manager. This port is used if SOAP is not
being used.

Needed when using IPV6

WebSphere Application WAS.AutomateConfig Binary value that indicates if WebSphere
Server Network Application Server Network Deployment is
Deployment specific automatically configured by the installation
properties program.

A value of false indicates WebSphere

Application Server Network Deployment
was manually configured before running the
installation program.
WAS.InstallLocation Installation location for WebSphere
Application Server Network Deployment.

For example, C:\\IBM\\WebSphere\\

AppServer
WAS.DeploymentManagerHostName Host name of the WebSphere Application
Server Network Deployment deployment
manager.
WAS.CellName WebSphere Application Server Network
Deployment CELL name.

For example, ctgCell01.

WAS.DeploymentManagerProfileName WebSphere Application Server Network
Deployment profile name.

For example, ctgDmgr01

WAS.DeploymentManagerProfileRoot Location of the WebSphere Application
Server Network Deployment profile.

For example, C:/IBM/WebSphere/AppServer/

profiles/ctgDmgr01

292 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 35. Installation properties (continued)
Category Property Definition
WAS.ServerProfileName WebSphere Application Server Network
Deployment application server profile name.

For example, ctgAppSrv01

WAS.NodeName WebSphere Application Server Network
Deployment node name.

For example, ctgNode01

WAS.ApplicationServerName WebSphere Application Server Network
Deployment application server name.

For example, MXServer

WAS.ClusterName WebSphere Application Server Network
Deployment cluster name.

For example, MAXIMOCLUSTER.

This property is designated for future use.

WAS.AdminUserName WebSphere Application Server Network
Deployment administrator name.

For example, wasadmin

WAS.AdminPassword WebSphere Application Server Network
Deployment administrator password.
WAS.RemoteAccessUserName WebSphere Application Server Network
Deployment deployment manager system
user ID used for tasks such as copying ISC
WAR files and fetching the keystore.
WAS.RemoteAccessPassword WebSphere Application Server Network
Deployment deployment manager system
user password.
WAS.VirtualHost Name of the WebSphere Application Server
Network Deployment virtual host.

For example, maximo_host.

WAS.VirtualHostPort Port for virtual host for listening for HTTP
server.

For example, 80.

WAS.WebServerHostName Host name where the HTTP server is
located.
WAS.AppServerJvmHeapMin Minimum heap size setting for the
application server JVM.

For example, 512.

WAS.AppServerJvmHeapMax Maximum heap size setting for the
application server JVM.

For example, 1024.

WAS.SibName Name of the service integration bus.

For example, intjmsbus.

Chapter 19. Backup and restoration 293

Table 35. Installation properties (continued)
Category Property Definition
WAS.SibHiMsg Service integration bus high message count.

For example, 500000.

WAS.WebServerName Name of the WebSphere Application Server
Network Deployment web server. Used to
manage HTTP server from within
WebSphere Application Server Network
Deployment.

For example, webserver1.

WAS.SibPersistMessages Binary value that indicates if service
integration bus messages are persisted in
either the product database or a local derby
database.

A value of true indicates that the messages

are persisted.
WAS.SibDSName Service integration bus data source name
created to access the service integration bus
persistence store.

For example, intjmsds.

WAS.SibDBType Database type where the service integration
bus messages are being stored.

For example, DB2.

WAS.SibDBName Name of the service integration bus
messages database.
WAS.SibDBInstance Instance name of the service integration bus
database.
WAS.SibDBServerName Server name of the system hosting the
service integration bus message database.
WAS.SibDBServerPort Database server port for the database
containing the service integration bus
messages.

For example, 50005.

WAS.SibDBUserName User ID used to access the persistence data
store database for service integration bus
messages.
WAS.SibDBUserPass Password for user ID named in
WAS.SibDBUserName.
WAS.SibDBInstallDir Where the service integration bus database
is installed.

For example, C:\Program Files\IBM\SQLLIB.

WAS.SibDbFencedUser Fenced user ID for the service integration
bus database. This property is only used for
databases hosted on UNIX systems.

For example, db2fenc1.

WAS.SibDbInstanceAdminUser Instance owner for the service integration
bus database.

294 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 35. Installation properties (continued)
Category Property
WAS.SibDbInstanceAdminPassword
WAS.SibDbRemoteAccessUser
WAS.SibDbRemoteAccessPassword
WAS.UseDefaultVmmSchema
WAS.VmmFullyAutomatedConfig
WAS.VmmUserRDN
WAS.VmmGroupRDN
LDAP Server-specific LDAP.AutomateConfig
Properties
LDAP.Vendor
LDAP.ServerHostName
LDAP.AdminDN
LDAP.AdminPassword
LDAP.ServerPort
LDAP.InstallLocation
Database-specific Database.AutomateConfig
Properties
Database.Vendor
Database.RemoteAccessUserName
Database.RemoteAccessPassword
Definition
Password for the instance owner of the
service integration bus database.
Database server system user used to
configure the service integration bus
remotely.
Password for user ID named in
WAS.SibDbRemoteAccessUser.
Unused property.
Binary value that indicates if the installation
program creates users and directories.
For example, true.
LDAP tree where users are stored.
For example, ou=users,ou=SWG,o=IBM, c=US.
LDAP tree where groups are stored.
For example, ou=groups,ou=SWG,o=IBM,
c=US.
Binary value that indicates whether the
installation program automatically
configures the directory server.
For example, true.
The type of LDAP repository.
Host name of the LDAP system host.
Administrator distinguished name.
For example, cn=root.
Password for user ID named in
LDAP.AdminDN.
Port listening for connection requests.
For example, 389.
Install location of the directory server.
For example, C:\Program
Files\IBM\LDAP\V6.2.
Binary value that indicates whether the
installation program automatically
configures the database.
For example, true.
Database type.
For example, DB2.
Database server system user ID that is used
for configure the database remotely.
Password for user ID named in
Database.RemoteAccessUserName.
Chapter 19. Backup and restoration 295
Table 35. Installation properties (continued)
Category Property Definition
mxe.db.driver Java class name of the JDBC driver.

For example, com.ibm.db2.jcc.DB2Driver.

For example, oracle.jdbc.OracleDriver.

For example com.inet.tds.TdsDriver.

mxe.db.url JDBC URL of the database.

For example,
jdbc:
db2://mymachine.mydomain.com:
50005/maxdb75
jdbc:
inetdae7a:mymachine.mydomain.com:
1433?
database=maxdb75&
language=us_english&
nowarnings=true&mars=false
jdbc:
oracle:thin:@mymachine.mydomain.com:
1521:ctginst1
mxe.db.initialConnections Number of database connections to create
when the application server is started.

For example, 8.
mxe.db.maxFreeConnections Maximum number of free database
connections available in the connection pool.

mxe.db.minFreeConnections
For example, 8.
Minimum number of free database
connections needed in the connection pool
in order for more connections to be
allocated.

For example, 5.
mxe.db.newConnectionCount Number of new connections to be created
when the minimum free connections are
available in the connection pool.

For example, 3.
mxe.db.transaction_isolation The system install sets the value to:
TRANSACTION_READ_COMMITTED.

This value cannot be modified.

mxe.db.format.upper This value defines the database uppercase
function for the system.

This value cannot be modified.

mxe.db.autocommit This value sets the autocommit mode used
for the Write connections. Can be either true
or false. The default is false.

This value cannot be modified.

296 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 35. Installation properties (continued)
Category Property
mxe.db.systemdateformat
mxe.db.format.nullvalue
mxe.db.sqlserverPrefetchRows
mxe.db.logSQLTimeLimit
mxe.db.fetchResultLogLimit
Oracle Properties Database.Oracle.InstanceName
Database.Oracle.SoftwareOwner
Database.Oracle.SoftwareOwnerPassword
Database.Oracle.InstallLocation
Definition
System date format.
For DB2, the value is current timestamp.
For Oracle, the value is sysdate, and the
default value cannot be edited.
For Microsoft SQL Server, the value is
getdate().
The database-specific format of the null
value function.
For DB2 the value is COALESCE, and the
default value cannot be edited.
The value for Oracle is NVL, and the default
value cannot be edited.
The value for Microsoft SQL Server must be
set to ISNULL.
Setting to reduce lock contention.
Optimal setting is 200 rows. Setting a value
larger than 500 can degrade performance.
The default value is 0.
This value is only valid for SQL Server.
The system logs the SQL statements that
take longer than the specified time limit. The
time is measured in milliseconds
(thousandths of a second).
The default value is 1000 milliseconds.
To disable, edit the file to read:
mxe.db.logSQLTimeLimit=0.
When this setting is enabled, a stack trace is
printed in the log for every business object
set that fetches beyond the set limit of rows.
The stack trace log is also repeated for every
multiple of such fetches.
The default is 200 rows.
To disable, edit the file to read:
mxe.db.fetchResultLogLimit=0.
Oracle instance name.
Owner of the software installation.
For example, oracle.
Password for the user ID listed in
Database.Oracle.SoftwareOwner.
Oracle installation location. For example,
/opt/app/oracle/product/10.2.0/db_1.
Chapter 19. Backup and restoration 297
Table 35. Installation properties (continued)
Category Property Definition
Database.Oracle.DataTablespaceName Oracle table space name for the product
database.

For example, maxdata.

Database.Oracle.InstanceLocation Oracle instance location.

For example, /opt/app/oracle/

product/10.2.0/db_1.
Database.Oracle.DataTablespaceLocation Location of Oracle database table space.
Database.Oracle.DataTablespaceSize Tablespace size, measured in Mb.

For example, 1000.

Database.Oracle.DataTablespaceMaxSize Maximum size of the table space, measured
in Mb.

For example, 8000.

Database.Oracle.TempTablespaceName Temporary table space name.

For example, maxtemp.

Database.Oracle.TempTablespaceLocation Location of temporary table space.
Database.Oracle.TempTablespaceSize Temporary table space size, measured in Mb.

For example, 1000.

Database.Oracle.TempTablespaceMaxSize Maximum size of the temporary table space,
measured in Mb.

For example, 8000.

Database.Oracle.IndexTablespaceName Index table space name.

For example, maxdata.

Database.Oracle.IndexTablespaceLocation Location of index table space.
Database.Oracle.IndexTablespaceSize Index table space size, measured in Mb.

For example, 1000.

Database.Oracle.IndexTablespaceMaxSize Maximum size of the index table space,
measured in Mb.

For example, 8000.

mxe.db.schemaowner
Database.Oracle.SchemaPassword
Database.Oracle.ServerHostName
Database.Oracle.ServerPort
Owner of the database schema.
Password for user listed in
mxe.db.schemaowner.
Host name of the Oracle server.
Port number used by Oracle.

For example, 1521.

Database.DBAUserName Oracle DBA user name.

For example, sys.

Database.DBAPassword Password for user ID listed for
Database.DBAUserName.
DB2 Properties mxe.db.schemaowner Owner of the database schema.

298 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Table 35. Installation properties (continued)
Category Property Definition
Database.DB2.ServerHostName Host name of the DB2 server.

For example, mymachine.mydomain.com.

Database.DB2.ServerPort Database server port.

For example, 50005.

Database.DB2.InstanceName Name of the database instance.

For example, ctginst1.

Database.DB2.DatabaseName Name of the database.

For example, maxdb75.

Database.DB2.InstallLocation Install location of the database.

For example, /opt/IBM/db2/V9.7

Database.DB2.LogFileSize Set the size for transaction logs.

For example, 4096

Database.DB2.AppCtlHeapSize Application control heap size.

For example, 1024

Database.DB2.ApplHeapSize Application heap size.

For example, 1024

Database.DB2.LockListSize Size allocated to the lock list.

For example, 30000

Database.DB2.LogSecond Number of secondary log files allowed.

For example, 4
Database.DB2.ServiceUser User ID used to autostart.
Database.DB2.ServicePassword Password for Database.DB2.ServiceUser.
Database.DB2.PageSize Page size setting.

Measured in kb. For example, 32

Database.DB2.ExtentSize Number of pages per extent (group of
pages).

For example, 32
Database.DB2.FencedUser Fenced user ID for DB2 on Linux or UNIX
systems.

For example, db2fenc1.

Database.DB2.AuthType Method DB2 uses to authenticate users.

For example, server.

Database.DB2.DataTablespaceName DB2 table space name for the product
database.

For example, maxdata.

Database.DB2.BufferPoolName DB2 buffer pool name.

For example, MAXBUFPOOL.

Chapter 19. Backup and restoration 299

Table 35. Installation properties (continued)
Category Property
Database.DB2.BufferPoolLocation
Database.DB2.BufferPoolSize
Database.DB2.DataTablespaceLocation
Database.DB2.DataTablespaceSize
Database.DB2.DataTablespaceMaxSize
Database.DB2.TempTablespaceName
Database.DB2.TempTablespaceLocation
Database.DB2.TempTablespaceSize
Database.DB2.TempTablespaceMaxSize
Database.DB2.IndexTablespaceName
Database.DB2.IndexTablespaceLocation
Database.DB2.IndexTablespaceSize
Database.DB2.IndexTablespaceMaxSize
Database.DB2.InstanceAdminUserName
Database.DB2.InstanceAdminPassword
Microsoft SQL Server mxe.db.schemaowner
Properties
Database.SQL.DatabaseName
Database.SQL.InstallLocation
Database.SQL.DataFileLocation
Database.SQL.DataFileName
Database.SQL.DataFileMaxSize
300 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Definition
Location of the buffer pool.
Size of the buffer pool.
For example, 32
Location of DB2 database table space.
Tablespace size, measured in Mb.
For example, 1000.
Maximum size of the table space, measured
in Mb.
For example, 8000.
Temporary table space name.
For example, maxtemp.
Location of temporary table space.
Temporary table space size, measured in Mb.
For example, 1000.
Maximum size of the table space, measured
in Mb.
For example, 8000.
Index table space name.
For example, maxdata.
Location of index table space.
Temporary table space size, measured in Mb.
For example, 1000.
Maximum size of the index table space,
measured in Mb.
For example, 8000.
Administrative user or the database instance.
Password for the user ID specified for
Database.DB2.InstanceAdminUserName
Owner of the database schema.
Name of the database.
For example, maxdb75.
Microsoft SQL Server installation
location. For example,C:\\Program
Files\\Microsoft SQL Server\\90.
Location for database data file
A way to specify the name of the data file
used for the database. For example,
maxdb75_dat.
Maximum size for data file for database.
Table 35. Installation properties (continued)
Category Property
Database.SQL.DataFileSize
Database.SQL.LogFileName
Database.SQL.LogFileSize
Database.SQL.DataFilegroupName
Database.SQL.ServerHostName
Database.SQL.ServerPort
Database.SQL.InstanceAdminUserName
Database.SQL.InstanceAdminPassword
ADE (DE) Properties DE.InstalllLocation
Application Server ApplicationServer.Vendor
Type Properties
Definition
Initial size for data file for database.
A way to specify the name for the database
transaction log file. For example,
maxdb75_log.
Microsoft SQL Server Database transaction
log file size.
Database logical name file group. For
example, PRIMARY.
Host name of the database server. For
example, myhost.mydomain.com.
Database server port. For example, 1433.
Administrative user for the Microsoft SQL
Server instance. used during install for
creating database, creating database user,
and modifying the database.
Administrative users password.
Location of the deployment engine.
Indicates which application server was
chosen during installation. For example,
WebSphere.

Updating environment data

When you install a second product on the same administrative workstation, or
upgrade a single product, the installation program uses values recorded from the
previous deployment. These values are stored on the administrative system in the
install.properties and maximo.properties files, and also in the database. If you
made any environmental changes to any of the systems used for the original
deployment, they must be recorded in the install.properties and
maximo.properties files. They also must be updated in the database. Typically,
these types of changes include changing a host name or updating a password.

Before you begin

During a follow-up installation task, the installation program uses values found in
the install.properties and maximo.properties files to complete the upgrade or
installation of an additional product. Pending successful use of these credentials,
you are not prompted to provide them again. If the installation program fails to
log on to the system with the credentials from the properties files, you are
prompted to supply current credentials. These values are then written to the
appropriate property file.

This method of updating credential information in property files has one exception.
Database connection and credential information must always be current before you
attempt an upgrade operation. Information for the database connection and
credentials are stored in the maximo.properties file. Any changes to this
information from the time of the original deployment must be recorded manually
in the maximo.properties file before you upgrade.

Passwords are encrypted within properties files. Update the encrypted values in
the properties files with clear text values and then re-encrypt the property file.

Chapter 19. Backup and restoration 301

 About this task

Updates to properties files can be performed by manually editing the appropriate

value in a property file. There is a reconfiguration tool available from the
Integrated Service Management Library that can be used to update properties. See
the Integrated Service Management Library (https://www.ibm.com/software/
brandcatalog/ismlibrary/) and search for IBM Maximo Reconfiguration Tool for
Administrative Workstations.

Procedure
1. Update the property value in the database by using the System Properties
application in SmartCloud Control Desk.
2. Update the database properties in the maximo.properties file:
a. As a precaution, create a backup of the c:\ibm\smp\maximo\applications\
maximo\properties\maximo.properties file.
b. Delete the c:\ibm\smp\maximo\applications\maximo\properties\
maximo.properties file.
c. Copy c:\ibm\smp\etc\maximo.properties_orig to c:\ibm\smp\maximo\
applications\maximo\properties\maximo.properties
d. Rename c:\ibm\smp\maximo\applications\maximo\properties\
maximo.properties_orig to c:\ibm\smp\maximo\applications\maximo\
properties\maximo.properties.
e. Edit c:\ibm\smp\maximo\applications\maximo\properties\
maximo.properties and update the credential or connection information for
the target database server.
f. Encrypt the file c:\ibm\smp\maximo\tools\maximo\encryptproperties.bat
file.
3. Update the c:\ibm\smp\etc\install.properties file on the administrative
workstation with any properties that changed. Do not change encrypted
password properties. Encrypted password properties are prefixed by [enc] in
the installation.properties file. Passwords can be updated during the next
upgrade. If you must update the host name for the IBM WebSphere Application
Server Network Deployment server, complete the steps in step 4.
4. Optional: Update the host name for the WebSphere Application Server Network
Deployment server.
a. Copy the keystore file from the WebSphere Application Server Network
Deployment deployment manager host to the c:\ibm\smp\wasclient\etc
directory of the administrative system. The keystore file can be found in
WAS_HOME/profiles/ctgDmgr01/etc/trust.p12.
b. Update the WAS.DeploymentManagerHostName property in the
install.properties file of the administrative system in the target
environment.
c. Edit the C:\ibm\smp\wasclient\thinwasadmin.bat file and update the
following line with the host name of the WebSphere Application Server
Network Deployment server:
set wsadminHost=-Dcom.ibm.ws.scripting.host=fully_qualified_host_name
d. Run C:\ibm\smp\wasclient\thinwasadmin.bat:
thinwsadmin.bat -domain manager user name -password

302 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Results

After completing these updates, you can upgrade, install a fix pack, or install
another product with the corrected values.

Chapter 19. Backup and restoration 303

304 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Notices
This information was developed for products and services offered in the U.S.A.

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

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

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

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

Intellectual Property Licensing

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

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.

This information could include technical inaccuracies or typographical errors.

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

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

© Copyright IBM Corp. 2012 305

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

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

IBM Corporation
Software Interoperability Coordinator, Department 49XA
3605 Highway 52 N
Rochester, MN 55901
U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

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

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

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

All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to
change before the products described become available.

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

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,

306 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

 modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:

© IBM Corp. 2013. Portions of this code are derived from IBM Corp. Sample
Programs. © Copyright IBM Corp. 2012. All rights reserved.

If you are viewing this information softcopy, the photographs and color
illustrations may not appear.

Trademarks
For trademark attribution, visit the IBM Terms of Use Web site
(http://www.ibm.com/legal/us/)

The following terms are trademarks of International Business Machines

Corporation in the United States, other countries, or both:

IBM, the IBM logo, AIX, Tivoli, the Tivoli logo, and WebSphere are trademarks or
registered trademarks of International Business Machines Corporation in the
United States, other countries, or both.

Intel, the Intel logo, and Pentium are trademarks of Intel Corporation in the United
States, other countries, or both.

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

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

both.

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

Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.

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

Notices 307
308 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)
Index
A deployment engine
backing up 15
install
automatic middleware
action deployment operations configuration 19
install 252 typical 242 simple
showavail 252 deployment plan path values 42, 61
showinstalled 252 overview 19 install action 255
undo 252 directory server install silently 143
uninstall 252 manually configuring 83 installation
upgrade 252 advanced topics 261
administrative workstation automatically configuring existing
backing up 287
restoring 288 E middleware 53
deploying using manual middleware
aggregation packages 239 EAR files
configuration 73
AIX building manually 267
deploying with manually configured
large page size support 10 maintaining 266
middleware 73
application server environmental data
Integration Composer
starting from the administrative updating 301
with Launchpad 181
console 262 error queue 126
preparing 1
starting from the command line 261 executeMapping command 195
product, automatically configured
authentication service 99, 103, 113 middleware 44, 63
product, manually configured
F middleware 133
B fonts properties 288
backup 287 AIX 8 Tivoli Integration Composer 185, 190
Installation
post installation tasks 203
C G installation prerequisites, Integration
Composer 184
company related accounts general ledger account
installing 99, 103
updating 208 creating 207
prerequisite software products 19,
configure 204 general ledger account component
143
configure SMTP 204 creating 206
silent 143
configuring 113 general ledger component type
Integration Composer
database server 74 authorization
installing
configuring Windows services 264 updating 207
with process solution installation
confirming the Integration Composer group 34
package 187, 191
installation 192 UNIX systems 187, 191
continuous inbound (CQIN) JMS queue Integration Composer installation
creating 122 H prerequisites 184
CQINERR JMS queue hardware and software requirements, Integration Composer installation,
creating 128 Integration Composer 182 confirming 192
currency codes help 203 Integration Composer overview 181
creating 205 HTTP server 14 Integration Composer requirements,
HTTPOnly hardware and software 182
configuring 179 Integration Composer, uninstalling 196
D item and company sets
data source creating 205
manually creating for the persistent I
store 131 IBM HTTP Server
database installing and configuring 280 J
applying changes 206 installing fix packs 282 J2EE server
database server 74 IBM Tivoli Directory Server 34 defer configuration 247
defer configuration 247 install on Solaris 272 manually configuring 91
DB2 manually configuring 83 JMS activation specification
configuring existing server with the verifying existing server using the creating for the continuous inbound
middleware installation middleware installation queue (CQIN) 125
program 56 program 57 creating for the inbound error queue
install on Solaris and HP-UX 270 IBM WebSphere Application Server (CQINERR) 129
manual configuration, 9.x 74 Network Deployment JMS connection factory
default insert site HTTPOnly 179 creating 121
creating 208

© Copyright IBM Corp. 2012 309

JMS queues
manually configure 116
O sequential inbound (SQIN) JMS queue
creating 123
JRE online help 203 sequential outbound (SQOUT) JMS queue
configuring in Linux 11 Oracle creating 124
manual configuration, 10g 78 service integration bus
manual configuration, 11g 76 adding a server 117
restoring 221
L organization
service integration bus destination
creating for the continuous inbound
language enablement 211 creating 205 (CQINBD) queue 118
languages overview, Integration Composer 181 creating for the inbound error queue
deploying after database update
(CQINERRBD) queue 126
deferral 51, 70, 140
creating for the sequential inbound
launchpad
overview 17
P (SQINBD) queue 119
package types 238 creating for the sequential outbound
starting 18
packages 238 (SQOUTBD) queue 120
libraries
page size support 10 shared memory
Linux 11
port availability setting 12
logs
checking 7 signing in 203
middleware installation program 22,
post installation 203 signing in and out 210
24
post-installation tasks 193 silent install 143
process solution installation
top-level class for IT silent product installation
program 257
assets 210 properties 146
software 210 simple install
pre-deployment system check path values 42, 61
M process solution installation SMTP 204
memory allocation program 249 software life cycle operations 237
changing 195 prerequisite 19, 143 solution installation program
Microsoft Active Directory process managers command line interface supported
configuring 87 installing using the process solution parameters 253
configuring with middleware installation wizard 250 solution installer program
installation program 58 process solution command line interface action 253
Microsoft SQL Server reference 255 solution package deployment
manual configuration 81 process solution deployment manually completing 248
restoring 222 managing from the administrative solution packages
middleware 19, 143 workstation 242 command line interface 252
changing configuration process solution installation solutionInstaller
parameters 265 packages 238 syntax 252
install on Solaris and HP-UX 269, process solution installation client 252 solutionInstaller script
270 process solution installation solutionInstaller.bat 252
install preparation on Solaris and program 255, 256 solutionInstaller.sh 252
HP-UX 269 before you begin 241 SSL
installing on HP-UX 269 choosing 239 client authentication workaround 14
installing on Solaris 269 logs 257 configuring 35
remote configuration 13 supported operations 240 startFusion file
starting and stopping 231 process solution package memory allocation 195
starting on UNIX 232 installation methods 237 swap size
starting on Windows 231 product installation setting 12
stopping on Linux and AIX 234 before you begin 1 system directories
stopping on Windows 233 product installation program accessing 7
uninstalling 39 overview 41, 60 system password policy
middleware clean up scripts 213 properties considerations 15
middleware cleanup scripts 213 installation 288
middleware installation silent product installation 146
before you begin 1
middleware installation program
T
tar command
log reference 24
logs 22
R AIX 8
recovery tool Tivoli Integration Composer
modfeatures action 256
uninstall 223 installation 185
restoration 287 upgrade 190

N
node agent
creating as a Windows service 99
S U
security ulimit
nstallation
configuring 212 setting 12
before you begin 1
selectable features 242

310 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

uninstall WebSphere plug-in
automatically configured See installing
deployment 218 WebSphere plug-in fix packs
database configuration recover 220 installing 284
manual 227 Windows services
manually configured configuring 264
deployment 219 worktypes
manually configured creating 208
middleware 219
manually removing files 230
product 217
without uninstallation
X
xml request pages 211
program 223
recovery tool 223
uninstall program recovery tool 224
uninstallation
automatically configured
middleware 218
uninstalling Integration Composer 196
uninstalling Integration Composer on
Unix-based operating systems 197
uninstalling Integration Composer on
Windows operating systems 196
user 34
users
groups
synchronizing 211
synchronizing 211

V
verifying prerequisites
programmatically 3
verifying the installation
manually 177
programmatically 171
Virtual Member Manager
configuring 285
VMM
manual configuration 276

W
WebSphere Application Server
recovering configuration 227
WebSphere Application Server Network
Deployment
See also management
configuration tasks 92
configuring to run as a Windows
service 264
install on Solaris and HP-UX 273
install SmartCloud Control Desk
applications 267
installing the update installer 280
manually configuring 91
manually creating profiles 274
manually uninstalling 267
WebSphere Application Server Network
Deployment administrative console
See securing
WebSphere Application Server Network
Deployment Application Server
(MXServer) 264
WebSphere node agent 264

Index 311
312 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)



Printed in USA