Installation guide (web sphereapplication server,db2,tivoli directory

IBM Maximo Asset Management
Version 7 Release 6
Installation Guide
(WebSphere Application Server, DB2, Tivoli Directory
Server)

Note
Before using this information and the product it supports, read the information in “Notices” on page 163.
This edition applies to version 7, release 6, modification 0 of IBM Maximo Asset Management and to all subsequent
releases and modifications until otherwise indicated in new editions.
© Copyright IBM Corporation 2007, 2014.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.

Contents
Chapter 1. Preparing for installation . . 1
Software installation images . . . . . . . . . 1
Before you begin . . . . . . . . . . . . . 1
Programmatically verifying prerequisites from the
command-line.. . . . . . . . . . . . . 1
Checking port availability . . . . . . . . . 6
AIX tar command requirements . . . . . . . 7
AIX font requirements . . . . . . . . . . 7
Verifying large page size support for AIX. . . . 7
Enabling asynchronous I/O on AIX. . . . . . 8
Checking for required libraries on Linux . . . . 8
Configuring the JRE in Linux . . . . . . . . 9
Setting the ulimit . . . . . . . . . . . . 9
Setting the swap size . . . . . . . . . . 10
Setting shared memory . . . . . . . . . 10
Remote configuration enablement . . . . . . 10
Enabling SSL client authentication . . . . . . 12
Microsoft SQL Server preparation . . . . . . 12
System password policy settings . . . . . . 13
Starting the launchpad . . . . . . . . . . 13
Installation program overview . . . . . . . . 14
Configuration program overview . . . . . . . 15
Chapter 2. Automatically configuring
middleware during deployment . . . . 19
Installing DB2 v10.5 using the Maximo Asset
Management version 7.6 installation program . . . 20
Installing WebSphere Application Server Network
Deployment v8.5 using the Maximo Asset
Preparing WebSphere Application Server Network
Management configuration program . . . . . . 23
Running the Maximo Asset Management 7.6
installation program . . . . . . . . . . . 23
Configuring Maximo Asset Management version 7.6
using the Maximo Asset Management version 7.6
configuration program. . . . . . . . . . . 24
Chapter 3. Automatically configuring
existing middleware during deployment 27
Configuring Maximo Asset Management version 7.6
using the Maximo Asset Management version 7.6
Chapter 4. Manually configuring
existing middleware during deployment 33
Maximo Asset Management installation with
manual middleware configuration . . . . . . . 34
Manual configuration of the database. . . . . 35
Manually configuring DB2 v10.5 . . . . . 35
Manual configuration of the directory server . . 37
Manually configuring IBM Tivoli Directory
Server . . . . . . . . . . . . . . 38
Manual configuration of the J2EE server. . . . 42
Manually configuring WebSphere Application
Server Network Deployment . . . . . . 42
installation program . . . . . . . . . . 67
Configuring Maximo Asset Management version
7.6 with manually configured middleware . . . 68
Chapter 5. Deploying in a cluster
environment . . . . . . . . . . . . 71
Installing DB2 v10.5 using the Maximo Asset
Installing WebSphere Application Server Network
Deployment and configuring application server
cluster profiles using the Maximo Asset
Configuring cluster members on additional
WebSphere Application Server Network
Deployment nodes . . . . . . . . . . . 76
Configuring Maximo Asset Management in a cluster
environment using the Maximo Asset Management
Chapter 6. Silent installation . . . . . 81
Creating silent response files for installation . . . 81
Sample silent installation response files . . . . 82
Updating password values in silent response files 83
Silently installing the Installation Manager software 83
Silently installing Maximo Asset Management and
related middleware . . . . . . . . . . . . 84
Silently uninstalling Maximo Asset Management
and related middleware . . . . . . . . . . 85
Chapter 7. Silent configuration . . . . 87
Creating silent response files for middleware
configuration . . . . . . . . . . . . . . 87
Sample silent middleware configuration response
files . . . . . . . . . . . . . . . . 87
Creating a response file for silent Maximo Asset
Management configuration . . . . . . . . . 88
Silently configuring middleware . . . . . . . 89
Silently configuring Maximo Asset Management . . 89
Silently remove middleware configuration . . . . 90
Remove product configuration silently . . . . . 90
© Copyright IBM Corp. 2007, 2014 iii

Chapter 8. Programmatically verifying
that the installation was successful . . 93
Chapter 9. Verifying the installation
manually . . . . . . . . . . . . . . 97
Chapter 10. Configuring the HTTPOnly
attribute . . . . . . . . . . . . . . 99
Chapter 11. Installation and
configuration programs log
information . . . . . . . . . . . . 101
Chapter 12. Post installation tasks 103
Accessing product documentation . . . . . . 103
Installing help information in a new language . . 103
Configuring initial data . . . . . . . . . . 104
Synchronizing users and groups . . . . . . . 107
Adding sample data to the Maximo Asset
Management database post configuration . . . . 107
Chapter 13. Installing Version 7.5
industry solutions . . . . . . . . . 111
Installing version 7.5 industry solutions from the
launchpad . . . . . . . . . . . . . . 111
Installing version 7.5 industry solutions from the
command line . . . . . . . . . . . . . 111
Installing version 7.5 industry solutions silently . . 112
Chapter 14. Maintaining EAR files . . 115
Building EAR files. . . . . . . . . . . . 115
Manually uninstalling applications from
Deployment . . . . . . . . . . . . . . 116
Manually installing applications in WebSphere
Application Server Network Deployment . . . . 116
Chapter 15. Command line
configuration . . . . . . . . . . . 119
Configuration parameter validation . . . . . . 119
Input properties files . . . . . . . . . . . 120
Command line interface parameters . . . . . . 121
Command line configuration program actions . . 128
action updateDatabaseConfiguration . . . . 128
action validateDatabaseConfiguration . . . . 128
action
validateAndUpdateDatabaseConfiguration . . 129
action deployDatabaseConfiguration. . . . . 129
action removeDatabaseConfiguration . . . . 130
action enableDB2TextSearch . . . . . . . 130
action updateJ2eeConfiguration . . . . . . 130
action validateJ2eeConfiguration . . . . . . 130
action validateAndUpdateJ2eeConfiguration . . 130
action deployJ2eeConfiguration . . . . . . 131
action removeJ2EEConfiguration . . . . . . 131
action deployConfiguration. . . . . . . . 131
action removeConfiguration . . . . . . . 131
action reapplyAppServerTuning . . . . . . 132
action enableAppSecurity . . . . . . . . 132
action disableAppSecurity . . . . . . . . 132
action updateApplication . . . . . . . . 132
action addLanguages . . . . . . . . . . 132
action configureProducts . . . . . . . . 133
action deployMiddlewareConfiguration . . . 133
Configuration program properties . . . . . . 134
Chapter 16. Configuring your product
with performance analysis data . . . 157
Chapter 17. Backup and restoration 159
Backing up the administrative workstation . . . 159
Restoring the administrative workstation . . . . 160
Chapter 18. Uninstalling the product 161
Remove Maximo Asset Management configuration 161
Removing WebSphere Application Server Network
Deployment configuration . . . . . . . . . 162
Uninstalling Maximo Asset Management and
middleware . . . . . . . . . . . . . . 162
Notices . . . . . . . . . . . . . . 163
Trademarks . . . . . . . . . . . . . . 164
Index . . . . . . . . . . . . . . . 167
iv IBM Maximo Asset Management: Installation Guide (WebSphere Application Server, DB2, Tivoli Directory Server)

Chapter 1. Preparing for installation
These topics provide information about product media, preinstallation
considerations, overview of the installation procedure, and instructions on using
the Maximo®
Asset Management launchpad.
Use the planning information to familiarize yourself with the overall process of a
Maximo Asset Management deployment before you use this information to
conduct the installation.
Software installation images
You access the IBM®
Maximo Asset Management product software from IBM
Passport Advantage.
The installation images that you download from Passport Advantage can comprise
multiple downloadable files. Download all files in the package to a single directory
and extract the files for execution.
For instructions and a full list of installation images, see the IBM Maximo Asset
Management 7.6 Download Document (http://www.ibm.com/support/
docview.wss?uid=swg24038431).
Before you begin
You must prepare your environment before you install Maximo Asset
Management. In some cases, to perform steps for preparation, 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 Maximo Asset
Management installation on the system. You must temporarily shut down any
noncritical processes before running the Maximo Asset Management installation
program.
Make a copy of the image of the system, database, and application server on which
you are planning to install the product.
Ensure that you have adequate disk space for the future on the systems being used
for the Maximo Asset Management deployment. Filling up the disk space on a
Maximo Asset Management deployment system can cause problems with Maximo
Asset Management 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.
Programmatically verifying prerequisites from the
command-line.
You can use the prerequisite verification utility from the command-line to verify
that installation program prerequisites are present on a system. Use this utility
before you start the product installation programs.
© Copyright IBM Corp. 2007, 2014 1

About this task
When started from the command line, the prerequisite verification utility accepts
various parameters. The prerequisite verification utility must be run on the system
that hosts the prerequisite to check. 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 to verify. 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.
j2eeserver
Use the j2eeserver parameter to have the prerequisite verification utility
check for WebSphere®
Application Server Network Deployment prerequisites.
pip
Use the pip parameter to have the prerequisite verification utility check for
prerequisites that are required by Maximo Asset Management. Run the
prerequisite verification utility with the pip parameter on the administrative
workstation.
asset_mgt_upg
Use the asset_mgt_upg parameter to have the prerequisite verification utility
check for prerequisites that are required to connect remotely during
configuration. .
rxa
Use the rxa parameter to have the prerequisite verification utility check for
prerequisites that are required by Maximo Asset Management.
performance
Use the performance parameter to have the prerequisite verification utility
check for prerequisites performance settings for Maximo Asset Management.
Syntax example:
tpae_req_check.bat -component pip
If you do not use the -component parameter, you are prompted to specify
components when you use the utility.
Multiple components can be specified as comma-separated values.
2 IBM Maximo Asset Management: Installation Guide (WebSphere Application Server, DB2, Tivoli Directory Server)

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 that are 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. Several
sample property files are found in the SystemRequirements
sample_property_files directory. These sample property files contain custom
values that are defined for particular operating systems. You can copy these
property files to the system and modify them, or create your own, before you run
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.
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
-trace Parameter that is used to specify trace output statements while the utility is
running.
None
Selecting this qualifier results in no trace information that is generated while
the utility is running.
Verbose
Selecting this qualifier results in detailed trace information that is generated
while the utility is running.
Normal
Selecting this qualifier results in default trace information that is generated
while the utility is running.
Syntax example:
tpae_req_check.bat
-component dbserver
-trace None
Chapter 1. Preparing for installation 3

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 that are found in the default tpae.properties
file to verify that a system is suitable to host DB2 for a Maximo Asset
Management 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 to check and
the property file to use.
tpae_req_check.bat
-component dbserver
-input d:SystemRequirementstpae.properties
In this example, the tpae.properties file is in the same directory as the
tpae_req_check.bat script.
Results
After the prerequisite verification utility successfully completes the verification
task, 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...
======== ====== ===== ===...
os.totalPhysicalMemory PASS 2.00GB 1.90GB
network.hasFQDN FAIL False True
Disk#1 (C:ibmtivolimwiworkspace) PASS 27.99GB 300MB
Disk#2 (C:Temp1) PASS 27.99GB 1000MB
Disk#3 (C:Temp1) 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 FilesIBMSQLLIB) 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 you start the command from the
command line.
If any of the verification steps report a failure, resolve the issue and rerun the
verification utility before you install Maximo Asset Management components.

The Table 2 table contains a list of the properties checked. Use this information to
analyze prerequisite verification utility results.
Table 2. Prerequisite verification utility properties
Property Description
browser.Version Checks browser version.
CpuArchitecture Verifies that the machine architecture is supported.
network.availablePorts.* Verifies that required ports are available.
The following example checks to ensure a port that is required by DB2 is
available.
network.availablePorts.db2inst=50000
network.dns Verifies that 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 that the operating system architecture is supported.
os.dir.tmp/home Verifies required permissions for the system directories
os.FreePagingSpace Verifies that adequate free paging space is available on the system.
os.iodevicestatus Verifies the I/O device status of the system.
os.kernelversion Checks kernel version.
os.lib.* Verifies that a prerequisite library is available on the system.
os.mountcheck Checks for the existence of nosuid on the file system.
os.MozillaVersion Checks browser version.
os.package.atk Verifies a prerequisite library that is required for GTK on AIX®
is available on
the system.
os.package.cairo Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.expat Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.fontconfig Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.freetype2 Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.gettext Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.glib2 Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.gtk2 Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.libjpeg Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.libpng Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.libtiff Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.pango Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.pixman Verifies a prerequisite library that is required for GTK on AIX is available on
the system.

Table 2. Prerequisite verification utility properties (continued)
Property Description
os.package.rpm Verifies that prerequisite packages are available on the system.
os.package.xcursor Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.xft Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.xrender Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.package.zlib Verifies a prerequisite library that is required for GTK on AIX is available on
the system.
os.RAMSize Reports system RAM available.
os.SeaMonkeyVersion Checks browser version.
os.SELinux Determines whether selinux is enabled.
os.ServicePack Verifies that required service packs are installed on the system.
os.shell.default Determines the default shell for users.
os.space.* Determines disk space availability for various file systems.
The following example shows the check that is made for the middleware
installation program workspace.
os.space.var=[dir:root=/var,unit:MB]512
os.totalPhysicalMemory Reports physical RAM available to the operating system.
os.ulimit Identifies user limits that are configured on the system.
OS.Version Reports the operating system type and version.
Checking port availability
Before you use the product installation programs, you must ensure that certain
ports in your environment are available for use with the middleware that you are
installing. You can either use the prerequisite verification utility to check for port
availability or you can check manually.
About this task
Default port values are assigned for the middleware that you deploy.
For example, port 50000 or an alternative port must be made available for DB2.
Port 9060 or an alternative port must be made available for IBM WebSphere
Application Server Network Deployment.
For a full list of port requirements, see the System requirements information on the
Maximo Asset Management wiki.

Procedure
1. Check the available ports on the host system:
Option Description
Automatic Run the prerequisite verification utility. The
network.availablePorts.* parameter
indicates the availability of the required
ports.
Manual Run the following command to see a list of
active connections:
netstat -ao
2. If you find that a port is already assigned, specify the value of an open port
when you are prompted to by the installation program.
AIX tar command requirements
Both the native UNIX tar command and the GNU version of the tar command are
required by the installation and configuration programs. 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 to produce reports.
About this task
When you produce 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.
Verifying large page size support for AIX
For Maximo Asset Management 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 Maximo Asset Management 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 4 K and 64 K page sizes that are 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
Asynchronous I/O must be enabled on AIX systems if the system hosts IBM Tivoli
Directory Server.
Without asynchronous I/O, DB2 database instances cannot be started successfully.
To enable asynchronous I/O, follow these steps:
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. Restart the system to enable the changes.
Checking for required libraries on Linux
The Maximo Asset Management deployment requires certain Linux system
libraries.

Procedure
1. Locate the libstdc++.so.5, libstdc++.so.6, and libaio.so.1 libraries in the
/usr/lib64/ directory. If these libraries are not installed, the Maximo Asset
Management installation program produces an error when run in graphical
mode. If you cannot locate this library on your system, locate the Red Hat
Package Manager package for your system that contains these libraries and
install the packages.
2. Ensure that you have the libstdc++33-32bit-3.3.3-11.9.x86_64.rpm package
that is installed before you run the product installation program. SUSE Linux
Enterprise Server 10 64-bit systems that host manually configured middleware
must host this package.
Configuring the JRE in Linux
In some cases, the Maximo Asset Management installation or configuration
program fails on Red Hat Enterprise Linux systems, or other systems with
Security-Enhanced Linux (SELinux) enabled.
About this task
In one scenario, the Maximo Asset Management installation or configuration
program fails with an error that states that the Java™
Runtime Environment (JRE)
cannot be found. In another scenario, the Maximo Asset Management installation
or configuration program fails stating that it cannot find the VM.
Procedure
1. Temporarily disable SELinux by using the setenforce 0 command.
2. Run the Maximo Asset Management installation or configuration program.
3. Re-enable SELinux by using the setenforce 1 command.
4. Manually issue the chcon command.
chcon -R -t textrel_shlib_t install_home/jvm/jre
Results
The Maximo Asset Management installation or configuration 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
Set the ulimit in Linux. The ulimit setting 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 you use the
Maximo Asset Management installation program.
If you set the ulimit in .profile for root, the ulimit setting applies to all processes.
Procedure
1. From a command line, type ulimit -f unlimited
2. From a command line, type ulimit -n 8192

Setting the swap size
Maximo Asset Management can be a resource-intensive application. Configure and
tune your system for maximum performance. Set the size of the swap space that is
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.
More swap space can be made available to the system.
Procedure
v Increase the size of the existing swap partition.
v Create a new, extra swap partition.
v Create a swap file.
Setting shared memory
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 you use the Maximo Asset Management installation program.
Procedure
1. From a command line, type sysctl kernel.shmmax and determine whether 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 Maximo Asset Management configuration program can automatically
configure middleware. You must enable a remote access protocol for each system
on which you intend to configure the middleware.
Use SSH for accessing remote Linux and UNIX systems. Use Windows SMB
accessing remote Windows systems. Windows SMB is a Windows protocol. The
IBM JRE on the Maximo Asset Management administrative workstation includes
SSH.
Before you start the Maximo Asset Management configuration 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 Maximo Asset Management
configuration program.
For remote Windows systems, ensure that the following requirements are met
before you configure the software.
v The user name that you provide to the Maximo Asset Management
configuration 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 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
firewall software 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.
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 you configure the software.
v For AIX systems, set the following SSH parameters in the /etc/ssh/sshd_config
file.
– ClientAliveInterval 900
– ClientAliveCountMax 10
Stop the SSH daemon with 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 configuration.
v The user name that you provide to the Maximo Asset Management
configuration 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. 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 Maximo Asset Management configuration program produces an error 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
configuration.
Before you begin
The Maximo Asset Management configuration programs use HTTP client requests
for various configuration actions. The Maximo Asset Management configuration
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. Maximo Asset Management configuration and
standard deployment procedures do not work correctly when the client
authentication feature of SSL is enabled in 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.
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 Maximo Asset Management configuration program.
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.
Microsoft SQL Server preparation
Microsoft SQL Server must be configured using specific options before you can use
it with Maximo Asset Management.
Ensure you have the following options set for the Microsoft SQL Server database
you intend to use with Maximo Asset Management. These settings must be
configured before you use the Maximo Asset Management configuration program
to configure Maximo Asset Management.
v Use the SQL Server Configuration Manager to disable TCP/IP dynamic ports
usage on the server.
v Verify that you enabled the Full-text Search setting during the installation of
Microsoft SQL Server.
v Set Microsoft SQL Server Database Collation settings to the following options:
– Dictionary order
– Case-insensitive
– For use with 1252 Character set

System password policy settings
Familiarize yourself with the password policies of systems you are using as part of
a Maximo Asset Management deployment.
Your organization might have password policy regulations that are enforced on
systems on your network. Before deploying Maximo Asset Management, be sure
that you are familiar with the password policies of systems that are used in the
deployment.
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 Maximo Asset Management. This error occurs
when you create users on a Microsoft Windows Server 2008 system.
Password values that you provide during the Maximo Asset Management
installation and configuration 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 and configuration
program panels. If your passwords do not conform to the password policies, errors
occur when the installation or configuration program attempts to create these
passwords.
Starting the launchpad
The IBM Maximo Asset Management launchpad serves as a centralized interface
for starting the product installation and configuration programs. The launchpad
also contains links to product information.
Before you begin
Before you start the launchpad, ensure that you meet the middleware prerequisites.
Ensure that you have the correct service pack levels for your environments.
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.
1. Download and extract the launchpad images which is described in the
download document.
2. Modify th e/user_dir/launchpad/Firefox.sh file and remove the following
lines
typeset +r LOGNAME 2>/dev/null
LOGNAME=lp_user_$$; export LOGNAME
3. Run the launchpad from /user_dir.
About this task
The launchpad generates messages that are captured in a hidden log frame while
the launchpad is running. To show the log frame on the launchpad panels, hold
the Ctrl key and simultaneously click 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 save the messages from a session by clicking Save at
the bottom of the log frame.

Always use fully qualified domain names when you enter values for the
installation and configuration programs.
Procedure
1. Log on to an account with system administration privileges on the system
where you want to install Maximo Asset Management.
2. Start the launchpad from the root directory of the installation image.
Option Description
Windows Start the launchpad by using the
launchpad64.exe program.
AIX and Linux Start the launchpad from the root directory
by using the launchpad.sh program, for
example,
./launchpad.sh
Related information:
Software Product Compatibility Reports
Installation program overview
You use the Maximo Asset Management installation program to install Maximo
Asset Management, IBM WebSphere Application Server, and IBM DB2.
Select packages to install from the Figure 1 on page 15 user interface.

You must run the installation program on the target system to install the
component. For example, to install IBM WebSphere Application Server, you start
the installation program locally on the system that is designated as the IBM
WebSphere Application Server server.
Use the Check for Other Versions, Fixes, and Extensions button to search for
fixes, updates, and extensions for the packages listed. The installation program
downloads the latest version of the packages listed from IBM Fix Central.
Configuration program overview
You use the Maximo Asset Management configuration program to configure
Maximo Asset Management and associated middleware.
The Maximo Asset Management configuration program is used to perform the
following configuration tasks.
v Prepare IBM WebSphere Application Server for configuration of your product
v Configure a new Maximo Asset Management deployment
v Update database access credentials
v Change the Maximo Asset Management security model
v Change the database server host
v Update IBM WebSphere Application Server access credentials
v Change IBM WebSphere Application Server host
Figure 1. Maximo Asset Management installation program

v Update database and build and deploy application EAR files
v Install product help information in another language
v Remove IBM WebSphere Application Server configuration
v Remove Maximo Asset Management configuration
The Maximo Asset Management configuration program records configuration
choices that you make about your Maximo Asset Management deployment and
then deploys Maximo Asset Management based on the information that you
entered.
Information that you enter for the Maximo Asset Management configuration
program is stored in the maximo.properties and install.properties files. Some of
this information is also written to the Maximo database. These values are
displayed in the panel fields of the Maximo Asset Management configuration
program during an upgrade or fix pack application.
The Maximo Asset Management configuration program validates the values that
you enter in configuration item fields. Some configuration item fields are validated
as a pair, for example, user name and password fields.
In most cases, you can run the configuration program locally or remotely. You are
required to run the configuration program locally on the IBM WebSphere
Application Server server when you are preparing it for Maximo Asset
Management configuration.
If you choose not to have the Maximo Asset Management configuration program
automatically configure middleware, you must configure that piece of middleware
manually before the configuration of Maximo Asset Management.
Figure 2. Maximo Asset Management configuration program

Note: If you are using a directory server to secure Maximo Asset Management, be
aware of the product-specific syntax rules for using special characters in LDAP
strings that you enter. In most cases, special characters must be preceded by an
escape character to make them readable by the directory server.
Many directory server products consider a blank space to be a special character in
an LDAP string. If you enter an LDAP string with an unescaped blank character at
the end of a field value, you encounter Maximo Asset Management errors.
For more information about special character usage in LDAP strings, see the
product documentation for your directory server.

Chapter 2. Automatically configuring middleware during
deployment
Use the Maximo Asset Management installation and configuration programs to
install and automatically configure a Maximo Asset Management deployment
within your enterprise.
About this task
This information provides a high-level overview or road map of tasks you need to
complete in order to deploy Maximo Asset Management with automatic
middleware configuration.
In this scenario, you use the Maximo Asset Management installation and
configuration programs to install and automatically configure new instances of the
following components:
v DB2
v WebSphere Application Server Network Deployment
v Maximo Asset Management
Asset Management and the middleware you want to use in your deployment. You
then use the Maximo Asset Management configuration program to configure both
middleware and Maximo Asset Management.
You can use the Maximo Asset Management installation program to install DB2.
You then use the Maximo Asset Management configuration program to
automatically configure it.

Installing DB2 v10.5 using the Maximo Asset Management version 7.6
installation program
Use the Maximo Asset Management version 7.6 installation program to install DB2
v10.5.
Procedure
1. Log in to the target system as a user with administrative authority. If you are
running the IBM Maximo Asset Management version 7.6 installation program
from a Linux or UNIX terminal window, you must be logged in as the root
user.
2. Start the IBM Maximo Asset Management version 7.6 installation program
from the launchpad.
a. Start the launchpad.
Install Maximo Asset Management using
the installation program
Configure Maximo Asset Management
using the configuration program
Verify the installation
Perform post installation tasks
Prepare WebSphere for Maximo Asset
Management using the
configuration program
Install DB2 using the
Maximo Asset Management
Install WebSphere using the
Figure 3. Deploying Maximo Asset Management using automatic middleware configuration

Windows
From the downloaded installation image, browse to the root
directory and run the following command: launchpad64.exe.
Linux and UNIX
directory and run the following command: launchpad.sh.
b. Select a language for the installation and click OK.
c. In the launchpad navigation pane, click Install Product.
d. From the Install Product panel, select IBM DB2 v10.5 and then click
Install IBM Maximo Asset Management components.
3. In the package selection panel, click Next.
4. In the package prerequisite validation panel, review the results of the
prerequisite check and then click Next. If any errors are reported on this
panel, resolve the issue and then click Recheck Status before continuing.
5. In the license agreement panel, review the license information for each
package being installed, select I accept the terms in the license agreements if
you agree with the terms, and then click Next.
6. In the Installation Manager installation location panel, specify path
information for the shared resources directory and the Installation Manager
installation directory, and then click Next. Installation Manager is the
installation framework that is used to install Maximo Asset Management
version 7.6 components. The shared resources directory is a common
workspace directory used by Installation Manager when installing packages.
7. In the package installation location panel, select a package group, specify the
path information for its installation directory, and then click Next. Repeat this
process for each package group listed.
8. In the package translations panel, specify language support for DB2, and then
click Next.
9. In the package features panel, leave all default options checked, and then click
Next.
10. In the package configuration panel, specify configuration information for DB2
v10.5, and then click Next.
11. In the package summary panel, review the information for the planned
installation, and then click Install.
Installing WebSphere Application Server Network Deployment v8.5
using the Maximo Asset Management version 7.6 installation program
Use the Maximo Asset Management version 7.6 installation program to install
WebSphere Application Server Network Deployment v8.5.
Procedure
user.
from the launchpad.
Chapter 2. Automatically configuring middleware during deployment 21

Windows
Linux and UNIX
d. From the Install Product panel, select IBM WebSphere Application
Server Network Deployment v8.5.5 and then click Install IBM Maximo
Asset Management components. During the installation of WebSphere
Application Server Network Deployment, install Java v7. When you install
Java v7, the configuration program configures IBM Maximo Asset
Management to use Java v7.
prerequisite check, and then click Next. If any errors are reported on this
package that is to be installed, select I accept the terms in the license
agreements if you agree with the terms, and then click Next.
6. In the Installation Manager installation location panel, specify the path
7. In the package installation location panel, select a package group, specify path
information for its installation directory, and then click Next. Repeat this
process for each package group that is listed.
8. In the package translations panel, specify language support for WebSphere
Application Server Network Deployment, and then click Next.
9. In the package features panel, leave all default options selected, and then click
Next.
10. In the package configuration panel, specify configuration information for IBM
HTTP Server, and then click Next.
12. After the installation is complete, select the option to start the Maximo Asset
Management version 7.6 configuration program, and then click Finish.
What to do next
Use the Maximo Asset Management version 7.6 configuration program to prepare
WebSphere Application Server Network Deployment for Maximo Asset
Management version 7.6 configuration.

Preparing WebSphere Application Server Network Deployment v8.5
using the Maximo Asset Management configuration program
WebSphere Application Server Network Deployment v8.5 for Maximo Asset
Procedure
1. If the Maximo Asset Management configuration program is not open, start it
from the Maximo Asset Management launchpad. In the launchpad navigation
pane, click Configure Product and then click Launch the Tivoli’s Process
Automation Suite configuration program.
2. In the IBM Maximo Asset Management version 7.6 configuration operations
page, click Prepare WebSphere Application Server Network Deployment for
configuration.
3. In the Configure the Application for WebSphere panel, specify the installation
location and configuration information for WebSphere Application Server
Network Deployment and associated components. Select the option to
automate the configuration of IBM HTTP Server.
4. In the Configure Application Server Profiles panel, specify information to use to
create the WebSphere Application Server Network Deployment deployment
manager and application server profiles.
5. Optional: In the Configure Application Server Advanced Options panel, specify
additional configuration information, if required.
6. If you chose to use a directory server for WebSphere Application Server
Network Deployment administrative security, specify information about the
directory server host, credentials and directory structure from the Configure
Administrative Security panel.
7. In the Apply Deployment Operations panel, select all deployment operation
options, and then click Finish.
Results
WebSphere Application Server Network Deployment v8.5 is ready for Maximo
Asset Management.
Running the Maximo Asset Management 7.6 installation program
Maximo Asset Management version 7.6.
About this task
In order to install Maximo Asset Management version 7.6, run the Maximo Asset
Management version 7.6 installation program on the Maximo Asset Management
administrative system.
Procedure
1. Log in to the Maximo Asset Management administrative workstation. If you
run the IBM Maximo Asset Management version 7.6 installation program from
a Linux or UNIX terminal window, you must be logged in as the root user.
2. Launch the IBM Maximo Asset Management version 7.6 installation program
from the launchpad.

Windows
Linux and UNIX
b. Select a language for the installation session and click OK.
d. From the Install Product panel, select IBM Maximo Asset Management
v7.6 and then click Install IBM Maximo Asset Management components.
7. In the package installation location panel, select the IBM Tivoli’s process
automation suite package group, specify the path information for the Maximo
Asset Management version 7.6 installation directory, and then click Next.
Next.
installation, and then click Install. If you install in a non-English environment,
you might notice the environment summary is listed as English. You configure
supported languages for Maximo Asset Management later with the Maximo
Asset Management configuration program.
Management version 7.6 configuration program, and then click Finish. The
Maximo Asset Management version 7.6 installation program exits and the
Maximo Asset Management version 7.6 configuration program is started
automatically.
What to do next
Use the Maximo Asset Management version 7.6 configuration program to configure
Configuring Maximo Asset Management version 7.6 using the Maximo
Asset Management version 7.6 configuration program

Procedure
1. If the Maximo Asset Management version 7.6 configuration program is not
open, start it from the Maximo Asset Management launchpad. In the
launchpad navigation pane, click Configure Product, specify Maximo Asset
Management installation location, and then click Launch the Tivoli’s Process
2. In the IBM Maximo Asset Management configuration operations page, click
Configure a New Deployment.
3. In the Define Deployment Environment panel, specify information about the
your database and application server, in this example, DB2 and WebSphere
Application Server Network Deployment servers that you installed and
prepared. Select Create and configure the database to automatically configure
WebSphere Application Server Network Deployment and DB2. After you
define your deployment environment, click Finish.
4. In the Configure General Product Information panel, review summary details
about the product components that you are installing. Specify the appearance
and navigation features for your product, add an e-mail address to receive
workflow messages, and choose whether or not to deploy sample data.
5. In the Configure the DB2 Instance panel, specify information about the DB2
instance to create for Maximo Asset Management.
6. In the Configure the DB2 Database panel, specify information about the DB2
database to create for Maximo Asset Management.
7. In the Configure the Application Server panel, specify information for the
WebSphere Application Server Network Deployment server that you installed.
If you chose to persist messages, indicate whether you want to store JMS
messages that originate from the integration adapter.
8. In the Configure Application Security panel, choose a security model for
Maximo Asset Management. If you choose a security model that includes a
directory server, specify information about the directory for the virtual
member manager. Enter the user names and passwords for users that must be
created for Maximo Asset Management. Do not use the user name as a
password value.
9. Choose the base language and any additional languages you want to install.
10. In the Apply Deployment Operations panel, select all available deployment
operations, and then click Finish.
Results
Maximo Asset Management version 7.6 is installed and configured to use
WebSphere Application Server Network Deployment and DB2.

Chapter 3. Automatically configuring existing middleware
during deployment
Use the Maximo Asset Management configuration program to automatically
configure existing middleware within your enterprise for use with Maximo Asset
Management
About this task
This information provides a high-level overview or roadmap of tasks you must
complete to deploy Maximo Asset Management automatically. You use middleware
that is already established in your enterprise.
In this scenario, you use the Maximo Asset Management configuration program
automatically configure existing middleware resources.
The Maximo Asset Management configuration program is used to automatically
configure an existing DB2 and IBM WebSphere Application Server server in your
environment.

Preparing WebSphere Application Server Network Deployment v8.5
using the Maximo Asset Management configuration program
WebSphere Application Server Network Deployment v8.5 for Maximo Asset
Procedure
pane, click Configure Product and then click Launch the Tivoli’s Process
page, click Prepare WebSphere Application Server Network Deployment for
configuration.
3. In the Configure the Application for WebSphere panel, specify the installation
Network Deployment and associated components. Select the option to
automate the configuration of IBM HTTP Server.
Install Maximo Asset Management using
the installation program
Configure Maximo Asset Management
using the configuration program
Verify the installation
Perform post installation tasks
Set up SSL for Microsoft Active
Directory if using directory server
for security (optional)
Prepare WebSphere for Maximo Asset
Management using the
configuration program
Figure 4. Deploying Maximo Asset Management reusing existing middleware

4. In the Configure Application Server Profiles panel, specify information to use to
create the WebSphere Application Server Network Deployment deployment
manager and application server profiles.
5. Optional: In the Configure Application Server Advanced Options panel, specify
additional configuration information, if required.
7. In the Apply Deployment Operations panel, select all deployment operation
Results
Asset Management.
About this task
Procedure
from the launchpad.
Windows
Linux and UNIX
Chapter 3. Automatically configuring existing middleware during deployment 29

Next.
automatically.
What to do next
Configuring Maximo Asset Management version 7.6 using the Maximo
Asset Management version 7.6 configuration program
Procedure
3. In the Define Deployment Environment panel, specify information about the
your database and application server, in this example, DB2 and WebSphere
Application Server Network Deployment servers that you installed and
prepared. Select Create and configure the database to automatically configure
WebSphere Application Server Network Deployment and DB2. After you
about the product components that you are installing. Specify the appearance
and navigation features for your product, add an e-mail address to receive

WebSphere Application Server Network Deployment server that you installed.
If you chose to persist messages, indicate whether you want to store JMS
messages that originate from the integration adapter.
password value.
10. In the Apply Deployment Operations panel, select all available deployment
operations, and then click Finish.
Results
Chapter 3. Automatically configuring existing middleware during deployment 31

Chapter 4. Manually configuring existing middleware during
deployment
You can deploy Maximo Asset Management by reusing existing middleware
servers and manually configuring them to work with Maximo Asset Management.
This information provides a high-level overview or road map of tasks you need to
complete in order to deploy Maximo Asset Management automatically, using
middleware already established in your enterprise.
In this scenario, you manually configure existing middleware resources before
running the Maximo Asset Management configuration program.

Maximo Asset Management 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 Maximo
Asset Management before you use the Maximo Asset Management installation and
configuration programs.
Figure 5. Deploying Maximo Asset Management with manual middleware configuration

You can automatically configure one or more Maximo Asset Management
middleware components with the Maximo Asset Management configuration
program. Alternatively, you can manually configure middleware servers to work
with Maximo Asset Management before you run the Maximo Asset Management
installation and configuration programs..
Before you begin, ensure that the following prerequisite conditions are met:
v You designate a Windows or UNIX server to start the Maximo Asset
Management configuration 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 middleware server before
you use the Maximo Asset Management configuration program to configure
Maximo Asset Management to work with the servers.
Ensure that the middleware you intend to use with Maximo Asset Management is
supported.
Manual configuration of the database
You can manually configure the database server that is used with Maximo Asset
Management. You must manually configure the database server before you use the
Maximo Asset Management installation and configuration programs.
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 v10.5
Manually configuring DB2 v10.5 servers for use by Maximo Asset Management.
About this task
To configure an existing DB2 v10.5 server for use with Maximo Asset Management,
complete the following steps before you start the Maximo Asset Management
installation and configuration programs:
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
Chapter 4. Manually configuring existing middleware during deployment 35

The ctginst1 user ID must be assigned to db2iadm1 as its primary 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/V10.5/bin, /opt/ibm/db2/v10.5/instance, and
/opt/ibm/db2/V10.5/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 ctgfenc1 -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 ’maxdb76’ ALIAS ’maxdb76’ using codeset UTF-8 territory US pagesize 32 K
db2 connect to ’maxdb76’
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.
db2 update db cfg for maxdb76 using SELF_TUNING_MEM ON
db2 update db cfg for maxdb76 using APPGROUP_MEM_SZ 16384 DEFERRED
db2 update db cfg for maxdb76 using APPLHEAPSZ 2048 AUTOMATIC DEFERRED
db2 update db cfg for maxdb76 using AUTO_MAINT ON DEFERRED
db2 update db cfg for maxdb76 using AUTO_TBL_MAINT ON DEFERRED
db2 update db cfg for maxdb76 using AUTO_RUNSTATS ON DEFERRED
db2 update db cfg for maxdb76 using AUTO_REORG ON DEFERRED
db2 update db cfg for maxdb76 using AUTO_DB_BACKUP ON DEFERRED
db2 update db cfg for maxdb76 using CATALOGCACHE_SZ 800 DEFERRED
db2 update db cfg for maxdb76 using CHNGPGS_THRESH 40 DEFERRED
db2 update db cfg for maxdb76 using DBHEAP AUTOMATIC
db2 update db cfg for maxdb76 using LOCKLIST AUTOMATIC DEFERRED
db2 update db cfg for maxdb76 using LOGBUFSZ 1024 DEFERRED
db2 update db cfg for maxdb76 using LOCKTIMEOUT 300 DEFERRED
db2 update db cfg for maxdb76 using LOGPRIMARY 20 DEFERRED
db2 update db cfg for maxdb76 using LOGSECOND 100 DEFERRED
db2 update db cfg for maxdb76 using LOGFILSIZ 8192 DEFERRED
db2 update db cfg for maxdb76 using SOFTMAX 1000 DEFERRED
db2 update db cfg for maxdb76 using MAXFILOP 32768 DEFERRED #32-bit Windows
db2 update db cfg for maxdb76 using MAXFILOP 65335 DEFERRED #64-bit Windows
db2 update db cfg for maxdb76 using MAXFILOP 30720 DEFERRED #32-bit UNIX
db2 update db cfg for maxdb76 using MAXFILOP 61440 DEFERRED #64-bit UNIX
db2 update db cfg for maxdb76 using PCKCACHESZ AUTOMATIC DEFERRED
db2 update db cfg for maxdb76 using STAT_HEAP_SZ AUTOMATIC DEFERRED
db2 update db cfg for maxdb76 using STMTHEAP AUTOMATIC DEFERRED
db2 update db cfg for maxdb76 using UTIL_HEAP_SZ 10000 DEFERRED
db2 update db cfg for maxdb76 using DATABASE_MEMORY AUTOMATIC DEFERRED
db2 update db cfg for maxdb76 using AUTO_STMT_STATS OFF DEFERRED
db2 update db cfg for maxdb76 using STMT_CONC LITERALS DEFERRED
db2 update alert cfg for database on maxdb76 using db.db_backup_req SET THRESHOLDSCHECKED YES
db2 update alert cfg for database on maxdb76 using db.tb_reorg_req SET THRESHOLDSCHECKED YES
db2 update alert cfg for database on maxdb76 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 into the system as the ctginst1 user, and then restart
the DB2 command-line environment.
su - ctginst1
db2
8. Restart DB2.

db2stop force
db2start
9. Reconnect to the database.
db2 connect to ’maxdb76’
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 CREATE REGULAR TABLESPACE MAXINDEX PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE INITIALSIZE 5000 M BUFFERPOOL MAXBUFPOOL
db2 GRANT USE OF TABLESPACE MAXDATA TO USER MAXIMO
12. Create Schema
db2 create schema maximo authorization maximo
13. 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
14. Break the database connection.
db2 connect reset
15. Exit the DB2 command-line environment
16. Install the appropriate fix pack that is 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 postinstallation tasks that are
contained within the fix pack readme file. Failure to do so can potentially
cause the Maximo Asset Management installation to fail.
Manual configuration of the directory server
You can manually configure a directory server for Maximo Asset Management to
manage authentication and authorization.
There are several methods to secure Maximo Asset Management.If want to use a
directory server to secure Maximo Asset Management, you must complete the
manual configuration of the directory server before you use the Maximo Asset
Management installation and configuration programs.
Note: The base dn, bind user, and other various node values that are listed are
default values. These values are replaced with values applicable to existing LDAP
hierarchies within your organization.
Important: When you enter LDAP values for Maximo Asset Management
configuration panel fields, entries in LDIF files, or values you enter directly into a
directory instance with 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 to make it readable by the
directory server. Failing to escape special characters that are contained in an LDAP
string that is used with Maximo Asset Management results in Maximo Asset
Management 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 Maximo Asset Management
errors that are difficult to troubleshoot.
For more information about special characters in LDAP strings, see the product
documentation for your directory server.

Manually configuring IBM Tivoli Directory Server
Manually configure IBM Tivoli Directory Server for use with Maximo Asset
Management.
About this task
If you choose the option to configure WebSphere Application Server Network
Deployment automatically with the Maximo Asset Management configuration
program, then you can create these users and groups automatically. If you do not
want the Maximo Asset Management configuration program to configure
WebSphere Application Server Network Deployment, you must create users
manually.
To configure IBM Tivoli Directory Server before you start the Maximo Asset
Management installation and configuration programs, you must create an instance
of IBM Tivoli Directory Server.
Note: While you can technically share a DB2 instance between Maximo Asset
Management 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 Maximo Asset Management and IBM Tivoli Directory Server.
Procedure
1. Using your preferred method, create a user on the system and assign it to the
appropriate group.
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.
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 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 systems, 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. More 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 that are
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.
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 that
are created for Maximo Asset Management. 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 Maximo Asset Management.
Important: Before you begin this procedure, create the following users in the
root of your LDAP repository:
Table 3. Base Maximo Asset Management users
User
wasadmin
maxadmin
mxintadm

Table 3. Base Maximo Asset Management users (continued)
User
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: wasadmin
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
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: top
objectClass: person
sn: mxintadm
cn: mxintadm
dn: uid=maxreg,ou=users,ou=SWG, o=ibm,c=us
userPassword: maxreg
uid: maxreg
objectClass: top
objectClass: person
sn: maxreg
cn: maxreg
Note: If you create the LDIF file on Windows, ensure that you remove the ^M
characters from the file before you use it.

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.
Manual configuration of the J2EE server
Manually configuring an existing J2EE server for use by Maximo Asset
Management.
Manual configuration of the J2EE server is required if you choose to deploy
Maximo Asset ManagementWebSphere Application Server Network Deployment
and you choose to not have the Maximo Asset Management configuration program
automatically configure it. You must complete the manual configuration before you
use the Maximo Asset Management configuration program.
Maximo Asset Management requires Java 7. Java 7 must be installed and
configured on the J2EE server you want tu use with Maximo Asset Management.
Manually configuring WebSphere Application Server Network
Deployment
This section contains instructions for manually configuring an existing WebSphere
Application Server Network Deployment for use by Maximo Asset Management.
You must manually configure WebSphere Application Server Network Deployment
before you use the Maximo Asset Management configuration program if you do
not want the Maximo Asset Management configuration program to configure it
automatically.
Creating WebSphere Application Server Network Deployment profiles:
When manually installing WebSphere Application Server Network Deployment,
profiles must be created before starting the Maximo Asset Management
installation. 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.
About this task
The following commands can be useful for managing profiles:
Table 4. Profile commands
Task Command
Delete a profile WAS_HOME/bin/manageprofiles.[sh|bat]
-delete -profileName profile name

Table 4. Profile commands (continued)
Task Command
Refresh the profile registry (for example,
after deleting a profile)
WAS_HOME/bin/manageprofiles.[sh|bat]
-validateAndUpdateRegistry
List existing profiles 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 FilesIBMWebSphereAppServer
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 FilesIBMWebSphere
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
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:
-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. Ensure the ctgDmgr01 profile is configured to use Java 7.

a. List available Java JDKs to ensure Java 7 is installed on the system.
WAS_HOME/bin>managesdk.[sh|bat]
-listAvailable
-verbose
b. List the version of Java associated with ctgDmgr01.
WAS_HOME/bin/managesdk.[sh|bat]
-listEnabledProfile
-verbose
c. If required, enable the ctgDmgr01 profile to use Java 7.
-enableProfile
-sdkName 1.7_32
-enableServers
5. Start the ctgDmgr01 server:
WAS_HOME/profiles/ctgDmgr01/bin/startManager.[sh|bat]
6. 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.
7. Create the ctgAppSrv01 profile using the manageprofiles command:
-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
8. Ensure the ctgAppSrv01 profile is configured to use Java 7.
a. List available Java JDKs to ensure Java 7 is installed on the system.
-listAvailable
-verbose
b. List the version of Java associated with ctgAppSrv01.
WAS_HOME/bin/managesdk.[sh|bat]
-listEnabledProfile
-verbose
c. If required, enable the ctgAppSrv01 profile to use Java 7.

-enableProfile
-sdkName 1.7_32
-enableServers
9. Start the ctgAppSrv01 node.
WAS_HOME/profiles/ctgAppSrv01/bin/startNode.[sh|bat]
10. 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]
11. 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” on page 63
Some deployment environments require the manual configuration of Virtual
Member Manager to secure Maximo Asset Management.
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.
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://www-01.ibm.com/
support/knowledgecenter/SSLKT6/sslkt6_welcome.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
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.
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>ctgMXlib. For example, C:Program FilesIBMWebSphere
AppServerctgMXlib.
m. Click Next.
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>ctgMXlib
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.
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.
Performing WebSphere Application Server Network Deployment configuration
tasks:
Use this procedure to perform WebSphere Application Server Network
Deployment configuration tasks.
About this task
If you elect to manually configure Maximo Asset Management middleware for use
with Maximo Asset Management, you have to manually configure the WebSphere
Procedure
1. Manually copy the keystore file from the WebSphere Application Server
Network Deployment deployment manager host to a temporary directory on

the Maximo Asset Management administrative system where you are
installing Maximo Asset Management: 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.
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.
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 Initial Heap Size and Maximum Heap Size, set these values to 4096.
f. Enter the following values in the Generic JVM arguments field, using a
space between each argument:
Figure 6. Manually create the application server

-Dsun.rmi.dgc.ackTimeout=10000
-Djava.net.preferIPv4Stack=true # for Windows
-Xdisableexplicitgc
-Xgcpolicy:gencon
-Xmn1024m # Xmn1024m for 64-bit JVM
-Xlp64k # AIX
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.
Figure 7. Manually create 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 1024 for Initial Heap Size and 1024 for Maximum
Heap Size and click OK.
Figure 8. Edit thread pool settings for the application server

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 check box for MXServer.
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).
Figure 9. Edit JVM Memory Settings for the deployment manager

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.
Figure 10. Identify the HTTP Transfer Port Numbers

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 11. Create the virtual host
Figure 12. Enable automatic startup of the application server when the node agent is started

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:IBMWebSphereAppServerprofilesctgAppSrv01"
-wasHome "C:IBMWebSphereAppServer"
-logRoot "C:IBMWebSphereAppServerprofilesctgAppSrv01logsnodeagent"
-logFile "C:IBMWebSphereAppServerprofilesctgAppSrv01logsnodeagent
startServer.log"
-restart true
4. Close the Command Prompt.
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 Maximo Asset Management installation
program provides you with the option of automatically configuring Maximo Asset
Management middleware. If you elect to have the Maximo Asset Management
installation program automatically configure Maximo Asset Management
middleware, it creates and configures JMS message queues for you. If you elect to
manually configure Maximo Asset Management middleware for use with Maximo
Asset Management, 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.
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 File store radio button is selected, and then click Next.
7. From the Configure file store panel, click Next.
8. From the Tune application server for messaging performance panel, click
Next.
9. Click Finish.
10. Click Save.
11. Select intjmsbus.
12. Change the value of the Default messaging engine high message threshold
field to a minimum value of 500,000 messages, and then click Apply.
If the number of messages awaiting processing exceeds the High Message
Threshold you set, the application server limits the addition of new messages
in the processing queues.
Depending on your message requirements, you can to enter a higher message
threshold value. You can determine an optimal message threshold setting by
monitoring the messaging in/out queues and the impact of the message
threshold setting on system performance. You might, for example, lower the
threshold value if a higher value is degrading system performance.

If you decide to change the High message threshold setting after the initial
configuration, you must open the Additional Properties menu in the
administrative console and change the threshold value for each child
configuration.
13. Click Save.
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.
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. Verify Keep count of failed deliveries per message is enabled.
13. Click Apply.
14. 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.
intjmsbus > Destinations dialog box. A bus destination is a virtual place
within a service integration bus where applications can attach and exchange
messages.
6. Enter SQINBD in the Identifier field and Sequential Queue Inbound in the
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
SQINBD bus destination queue.
10. Navigate the path Buses > intjmsbus > Destinations, then click SQINBD to
open the configuration dialog box.
13. Click Apply.
14. Click Save.
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
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.

6. Enter SQOUTBD in the Identifier field and Sequential Queue Outbound in the
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.
queue.
10. Navigate the path Buses > intjmsbus > Destinations, then click SQOUTBD
to open the configuration dialog box where you must make the following
changes:
13. Click Apply.
14. 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
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.
6. Click Apply.
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
console, click Resources > JMS > Queues.
3. Click New.
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.
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
About this task
To create the SQIN JMS queue, complete the following steps:
Procedure
3. Click New.
Name Enter SQIN.
JNDI name
Enter jms/maximo/int/queues/sqin
Bus name
Select intjmsbus.
Queue name
Select SQINBD.
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
About this task
To create the SQOUT JMS queue, complete the following steps:
Procedure
3. Click New.
Name Enter SQOUT.
JNDI name
Enter jms/maximo/int/queues/sqout
Bus name
Select intjmsbus.
Queue name
Select SQOUTBD.
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
console, click Resources > JMS > Activation Specifications.
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
Bus name
intjmsbus
Maximum concurrent MDB invocations per endpoint
10
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
intjmsbus > Destinations dialog box. A bus destination is a virtual place
within a service integration bus where applications can attach and exchange
messages.
6. Enter CQINERRBD in the Identifier field and Error Queue Inbound in the
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
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.
c. Verify Keep count of failed deliveries per message is enabled.
11. Click Apply.
12. Click Save.
intjmsbus > Destinations dialog box.
16. Select CQINBD.
17. Specify CQINERRBD as the exception destination. Set the Maximum failed
deliveries value to 5.
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
3. Click New.
Name Enter CQINERR.
JNDI name
Enter jms/maximo/int/queues/cqinerr
Bus name
Select intjmsbus.
Queue name
Select CQINERRBD.
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
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.
Name Enter intjmsacterr.
This value must only contain lowercase letters.
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
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 configuring Virtual Member Manager on WebSphere Application
Server Network Deployment:
Some deployment environments require the manual configuration of Virtual
Member Manager to secure Maximo Asset Management.
Before you begin
For a review of Maximo Asset Management security options, see the security
planning information.
Important: Before you begin this procedure, ensure that you have a wasadmin
user ID 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 Maximo Asset
Management installation and configuration. If Virtual Member Manager is

configured to use SSL with a federated LDAP repository before completing the
Maximo Asset Management configuration, the configuration fails. Do not configure
a Virtual Member Manager LDAP federated repository to use SSL with an LDAP
directory before configuration Maximo Asset Management. Configure SSL after the
Maximo Asset Management configuration program has completed successfully.
About this task
During the configuration process, the Maximo Asset Management configuration
program provided you with the option of automatically configuring Maximo Asset
Management middleware. If you elected to have the Maximo Asset Management
configuration program automatically configure Maximo Asset Management
middleware, then it will, among other tasks, perform Virtual Member Manager
configuration for you. If you elected to manually configure Maximo Asset
Management middleware for use with Maximo Asset Management, 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
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>/admin
For example, enter a URL like the following sample URL:
http://localhost:9060/admin
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 > Global security.
5. Locate the User account repository area and pick Federated repositories from
the Available realm definitions field, and then click Configure.

6. Click Add repositories located under Repositories in the realm.
7. Click New repositoryLDAP repository 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.
Directory type
For IBM Tivoli Directory Server, select IBM Tivoli Directory Server.
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.
Bind distinguished name
For IBM Tivoli Directory Server, enter cn=root.
Bind password
Enter the password for the bind distinguished name.
Certificate mapping
Select EXACT_DN
9. Enter the following values, click Apply, and then click Save.
Repository
For IBM Tivoli Directory Server, select ISMITDS.
Figure 13. New Repository

Unique distinguished name of the base entry (or parent) entry in federated
repositories
For IBM Tivoli Directory Server, enter ou=SWG,o=IBM,c=US.
Distinguished name in the repository is different
This value is optional. You need to provide this value if it differs from
the base entry in the repository you are adding.
10. 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.
11. Click Supported entity types, and then click PersonAccount.
12. 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.
Relative Distinguished Name properties
Enter uid.
13. Click OK and then click Save.
14. Click Supported entity types, and then click Group.
15. From the Group configuration area, enter the following values:
Entity type
Verify that the value is Group.
For IBM Tivoli Directory Server, enter ou=groups,ou=SWG,o=IBM,c=US.
Enter cn.
17. Click Supported entity types, and then click OrgContainer.
18. From the OrgContainer configuration area, enter or verify the following
values:
Entity type
Verify that the value is OrgContainer.
Enter o;ou;dc;cn.

20. Browse to Security > Global security.
21. From the Global security 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.
22. Click Apply, and then click Save.
23. Restart WebSphere Application Server Network Deployment and the managed
nodes by running the following commands:
a. <WAS_HOME>profilesctgDmgr01binstopManager.bat
b. <WAS_HOME>profilesctgAppSrv01binstopNode.bat
c. <WAS_HOME>profilesctgDmgr01binstartManager.bat
d. <WAS_HOME>profilesctgAppSrv01binstartNode.bat
Note: Substitute UNIX path and file extension values where appropriate.
“Performing WebSphere Application Server Network Deployment configuration
tasks” on page 47
Use this procedure to perform WebSphere Application Server Network
Deployment configuration tasks.
Running the Maximo Asset Management 7.6 installation
program
About this task
Procedure
from the launchpad.
Windows
Linux and UNIX

Next.
automatically.
What to do next
Configuring Maximo Asset Management version 7.6 with
manually configured middleware
This procedure explains how to use the Maximo Asset Management version 7.6
configuration program to configure Maximo Asset Management version 7.6.
Procedure
3. In the Define Deployment Environment panel, specify information about DB2
and WebSphere Application Server Network Deployment servers you installed

and prepared. Select the WebSphere is already configured option. After you
about the product components you are installing. Specify the appearance and
navigation features for your product, add an e-mail address to receive
instance for Maximo Asset Management.
database for Maximo Asset Management.
WebSphere Application Server Network Deployment server you installed.
Indicate whether you want to store JMS messages originating from the
integration adapter.
created for Maximo Asset Management.
10. In the Apply Deployment Operations panel, specify user interface preferences,
select all available deployment operations, and then click Finish.
Results

Chapter 5. Deploying in a cluster environment
Use the Maximo Asset Management installation and configuration programs to
install and automatically configure Maximo Asset Management in a WebSphere
Application Server Network Deployment cluster configuration.
About this task
In this scenario, you use the Maximo Asset Management installation and
configuration programs to install and automatically configure new instances of the
following components in a cluster configuration:
v DB2
v WebSphere Application Server Network Deployment
v Maximo Asset Management
Asset Management and the middleware you want to use in your deployment. You
then use the Maximo Asset Management configuration program to configure both
middleware and Maximo Asset Management.
You can use the Maximo Asset Management installation program to install DB2.
You then use the Maximo Asset Management configuration program to
automatically configure it.
You can use the roadmap of tasks to automatically configure middleware and
deploy Maximo Asset Management in a cluster environment.

Installing DB2 v10.5 using the Maximo Asset Management version 7.6
Use the Maximo Asset Management version 7.6 installation program to install DB2
v10.5.
Figure 14. Deploying Maximo Asset Management using automatic middleware configuration

Procedure
user.
from the launchpad.
Windows
Linux and UNIX
d. From the Install Product panel, select IBM DB2 v10.5 and then click
Install IBM Maximo Asset Management components.
prerequisite check and then click Next. If any errors are reported on this
7. In the package installation location panel, select a package group, specify the
path information for its installation directory, and then click Next. Repeat this
process for each package group listed.
8. In the package translations panel, specify language support for DB2, and then
click Next.
Next.
10. In the package configuration panel, specify configuration information for DB2
v10.5, and then click Next.
Installing WebSphere Application Server Network Deployment v8.5
using the Maximo Asset Management version 7.6 installation program
WebSphere Application Server Network Deployment v8.5.
Chapter 5. Deploying in a cluster environment 73

Procedure
user.
from the launchpad.
Windows
Linux and UNIX
d. From the Install Product panel, select IBM WebSphere Application
Server Network Deployment v8.5.5 and then click Install IBM Maximo
Asset Management components. During the installation of WebSphere
Application Server Network Deployment, install Java v7. When you install
Java v7, the configuration program configures IBM Maximo Asset
Management to use Java v7.
package that is to be installed, select I accept the terms in the license
agreements if you agree with the terms, and then click Next.
6. In the Installation Manager installation location panel, specify the path
7. In the package installation location panel, select a package group, specify path
information for its installation directory, and then click Next. Repeat this
process for each package group that is listed.
8. In the package translations panel, specify language support for WebSphere
Application Server Network Deployment, and then click Next.
9. In the package features panel, leave all default options selected, and then click
Next.
10. In the package configuration panel, specify configuration information for IBM
HTTP Server, and then click Next.
Management version 7.6 configuration program, and then click Finish.

What to do next
WebSphere Application Server Network Deployment for Maximo Asset
Management version 7.6 configuration.
Preparing WebSphere Application Server Network Deployment and
configuring application server cluster profiles using the Maximo Asset
Management configuration program
You can use the Maximo Asset Management version 7.6 configuration program to
prepare WebSphere Application Server Network Deployment v8.5 for Maximo
Asset Management configuration and configure application server cluster profiles.
About this task
When you configure Maximo Asset Management for a cluster environment, you
must first prepare the WebSphere Application Server Network Deployment server
and configure application server cluster profiles. You then configure Maximo Asset
Management to work with the defined clusters.
You must define and configure clusters on the WebSphere Application Server
Network Deployment deployment manager. If you want the cluster configuration
to include members on other WebSphere Application Server Network Deployment
nodes, you must log onto the server and run the Maximo Asset Management
configuration program to configure a WebSphere Application Server Network
Deployment profile and node to host those cluster members.
For performance reasons, you are encouraged to define a minimum of four
clusters, each of which hosts a single product function. You can create additional
clusters based on your needs. Refer to the Best Practices for System Performance
guide for detailed performance information.
Procedure
1. Log on to the system hosting the WebSphere Application Server Network
Deployment deployment manager server.
2. Start the Maximo Asset Management configuration program from the Maximo
Asset Management launchpad. In the launchpad navigation pane, click
Configure Product and then click Launch the Tivoli’s Process Automation
Suite configuration program.
page, click Prepare WebSphere Application Server for configuration.
4. In the Configure WebSphere Application Server panel, specify the installation
Network Deployment and associated components. Select the options to
configure the system for clusters and to automate the configuration of IBM
HTTP Server.
5. In the Configure Application Server Cluster Profiles panel, specify
information to use to create WebSphere Application Server Network
Deployment deployment manager and application server profiles.
a. Select Configure a new Deployment Manager at this server.
b. Specify the profile name, node name, cell name, and SOAP port for the
deployment manager profile.

c. Optional: Click Advanced to access the Deployment Manager Profile
Advanced Options page where you can assign custom port values used by
the deployment manager profile.
d. Specify the WebSphere Application Server Network Deployment
administrator user credentials.
e. Click New cluster to create a new cluster. Specify a name and assign a
single product function to the cluster.
f. Click New Managed Node to create a managed node. Specify a node name
and a name for the profile that contains information about the new managed
node. You can create more than one managed node, but you must have at
least one managed node defined.
g. Select the managed node and click New Server.
h. From the WebSphere Managed Node Server Definition page, select Web
server, and specify a name for the web server the managed node will use.
Only one web server can be defined for a managed node.
i. Click New Server. From the WebSphere Managed Node Server Definition
page, select Application server cluster member. Specify a name for the
cluster member and select the cluster to associate with the cluster member.
You can create as many cluster members as you need, but you must create at
least one.
j. Repeat the process to create four clusters in total, and assign each a unique
product function.
6. Specify additional configuration information in the Configure Application
Server Advanced Options panel, if required.
8. In the Apply Deployment Operations panel select all deployment operation
Results
Asset Management.
https://www.ibm.com/developerworks/community/files/form/anonymous/
api/library/75dbdf46-1a08-429c-9742-bd340d7d1fd3/document/c51d5f5b-dea3-
4043-a81f-d5213fc10063/media/Best%20Practices%20for%20System%20Performance
%207.5.x.pdf
Configuring cluster members on additional WebSphere
Application Server Network Deployment nodes
You can use the Maximo Asset Management version 7.6 configuration program to
configure cluster members on additional WebSphere nodes.
About this task
After you have defined clusters on the WebSphere Application Server Network
Deployment deployment manager, you can configure cluster members on
additional WebSphere Application Server Network Deployment nodes.

Procedure
1. Log on to the system serving as the WebSphere Application Server Network
Deployment nodes.
2. Start the Maximo Asset Management configuration program from the Maximo
Asset Management launchpad. In the launchpad navigation pane, click
Configure Product and then click Launch the Tivoli’s Process Automation
Suite configuration program.
page, click Configure WebSphere Application Server Network Deployment
for a new deployment.
4. In the Configure WebSphere Application Server panel, specify the installation
Network Deployment and associated components. Select the options to
configure the system for clusters and to automate the configuration of IBM
HTTP Server.
5. In the Configure Application Server Cluster Profiles panel, specify
information to use to create additional cluster members on this nodes.
a. Select Use an existing Deployment Manager.
b. Specify connection information for the remote WebSphere Application
Server Network Deployment deployment manager system.
c. Specify the WebSphere Application Server Network Deployment
administrator user credentials.
d. Click Load clusters to load cluster information from the remote WebSphere
Application Server Network Deployment deployment manager.
e. Click New Managed Node to create a managed node. Specify a node name
and a name for the profile that contains information about the new
managed node. You can create more than one managed node, but you must
have at least one managed node defined.
f. Select the managed node and click New Server.
g. From the WebSphere Managed Node Server Definition page, select
Application server cluster member. Specify a name for the cluster member
and select the cluster to associate with the cluster member. You can create as
many cluster members as you need, but you must create at least one. You
cannot create a new web server for the cluster because it was defined when
the cluster was created on the remote WebSphere Application Server
Network Deployment deployment manager
h. Repeat the process to create new cluster members and assign them to
clusters defined on the remote WebSphere Application Server Network
Deployment deployment manager.
6. Specify additional configuration information in the Configure Application
Server Advanced Options panel, if required.
7. In the Apply Deployment Operations panel select all deployment operation

About this task
Procedure
from the launchpad.
Windows
Linux and UNIX
Next.
automatically.

What to do next
Configuring Maximo Asset Management in a cluster environment using
the Maximo Asset Management configuration program
You can use the Maximo Asset Management configuration program to configure
Maximo Asset Management in a cluster environment after WebSphere Application
Server Network Deployment has been configured for clustering.
Procedure
3. In the Define Deployment Environment panel, specify information about DB2
and WebSphere Application Server Network Deployment servers you installed
and prepared. Select the Create and configure the database, the Complete
configuration of WebSphere for your product, and the Deploy the product
into a clustered environment options to automatically configure WebSphere
Application Server Network Deployment and DB2. After you define your
deployment environment, click Finish.
about the product components you are installing. Specify the appearance and
navigation features for your product, add an e-mail address to receive
WebSphere Application Server Network Deployment domain manager where
the clusters were defined, and then click Load cluster information.
8. Create an application for a function managed by a cluster, configure JMS for
the application, and configure the Maximo Asset Management help
application. You must create at least one application for each function in a
cluster.
a. Click Add application.
b. Specify a name for the application and select the cluster name and web
server associated with the function.
c. Optional: Change the function associated with the selected cluster.
d. Enable and configure JMS message handling for the application. The
Maximo Integration Framework function requires JMS. The Reporting
function does not support JMS. If you do not choose to use DB2 to store
JMS data, a derby database is created to store the information.

9. Configure the Maximo Asset Management help application by supplying a
name for the help application, selecting a cluster to assign it to, and selecting
the web server to use for the application.
password value.
11. Select languages.
12. In the Apply Deployment Operations panel, specify user interface preferences,
select all available deployment operations, and then click Finish.

Chapter 6. Silent installation
The Maximo Asset Management silent installation option interacts with the
Maximo Asset Management installation program by using a command prompt and
a response file.
You must install the Installation Manager software before you can silently install
the Maximo Asset Management or related middleware packages
Creating silent response files for installation
A response file records selections that you make and values that you provide when
using the Maximo Asset Management installation program. The Maximo Asset
Management installation program can then be run silently using the response file
for input.
Before you begin
You can create a silent installation response file by setting the record environment
variable, and then starting the installation program through the Maximo Asset
Management launchpad. The response file is generated in the home directory of
the user that started the program. You can determine the home directory of the
current user the command appropriate for your operating system by using the
following commands.
Windows
set HOMEPATH
UNIX
echo $HOME
The name of the file is tpaeInstallerRspdate_and_time_stamp.xml, for example,
tpaeInstallerRsp20130716105258.xml
Procedure
1. Open a command prompt and set the record environment variable.
Option Description
Windows set record=true
Linux or UNIX export record=true
2. Start the Maximo Asset Management launchpad.
Option Description
Windows launchpad64.exe
Linux or UNIX ./launchpad.sh
3. Click Install Product.
4. Select the components that you want to install, and then click Install to start
the Maximo Asset Management installation program.

5. Select the packages you want to install silently, and specifying the shared
resources and installation directories. When you are satisfied with your
installation choices, click Install to install the packages.
6. Click Finish to exit the Maximo Asset Management installation program.
Sample silent installation response files
Instead of using the tpaeInstallerRspdate_and_time_stamp.xml file, you can use a
sample response file and modify it according to your needs.
Sample files
Sample response files are provided in the directory where you extracted the IBM
Maximo Asset Management 7.6 launchpad. If you update the values that are used
in the sample response files, limit your updates to parameters such as installation
locations, host names, port numbers, and user names. If you need to update
non-environmental values, such as the main product name or the Installation
Manager repository, create your own silent response file with the Installation
Manager software.
Table 5. Samples of silent response files
File Description
launchpad_directorySilentResponseFiles
InstallerUnix
ResponseFile_MAM_Install_Unix.xml
Install Maximo Asset Management on
Linux and UNIX.
InstallerUnix
ResponseFile_MAM_Uninstall_Unix.xml
Uninstall Maximo Asset Management on
Linux and UNIX.
InstallerWindows
ResponseFile_MAM_Install_Windows.xml
Install Maximo Asset Management on
Windows.
InstallerWindows
ResponseFile_MAM_Uninstall_Windows.xml
Uninstall Maximo Asset Management on
Windows.
InstallerUnix
ResponseFile_DB2_Install_Unix.xml
Install IBM DB2 on Linux and UNIX.
InstallerWindows
ResponseFile_DB2_Install_Windows.xml
Install IBM DB2 on Windows.
InstallerUnix
ResponseFile_DB2_Uninstall_Unix.xml
Uninstall IBM DB2 on Linux and UNIX.
InstallerWindows
ResponseFile_DB2_Uninstall_Windows.xml
Uninstall IBM DB2 on Windows.
InstallerUnix
ResponseFile_TPAE_WAS_Install_Unix.xml
Install base components of WebSphere
Application Server on Linux and UNIX.
InstallerWindows
ResponseFile_TPAE_WAS_Install_Windows.xml
Install base components of WebSphere
Application Server on Windows.

Table 5. Samples of silent response files (continued)
File Description
InstallerUnix
ResponseFile_TPAE_WAS_Uninstall_Unix.xml
Uninstall base components of
WebSphere Application Server on Linux
and UNIX.
InstallerWindows
ResponseFile_TPAE_WAS_Uninstall_Windows.xml
Uninstall base components of
WebSphere Application Server on
Windows.
Updating password values in silent response files
The Maximo Asset Management installation program requires the encryption of
password values that are in the response files. If you need to update encrypted
password values in a response file, use the Installation Manager string encryption
utility.
About this task
The Installation Manager string encryption utility accepts a plain text password
value and produces an encrypted version of that password. You must then copy
and paste the encrypted value into the password field of the response file.
Procedure
1. Start the Installation Manager string encryption utility from the command line.
Option Description
Windows c:Program FilesIBM
InstallationManagereclipsetools
imutilsc newpasswordvalue
AIX or Linux /opt/IBM/InstallationManager/eclipse/
tools/imutilsc encryptString
newpasswordvalue
Replace newpasswordvalue with your new plain text password value.
2. Copy the string in the Encrypted version of the string field.
3. Open the response file in a text editor, replace the password value with the
copied encrypted password, and then save the file.
Silently installing the Installation Manager software
In order to install Maximo Asset Management and related middleware silently, the
Installation Manager software must first be installed.
Procedure
1. Open a command prompt on the system and change to the directory where
you unzipped the launchpad files.
2. Change directory to the folder that contains the installation manager program
for your operating system, for example, InstallIMinstaller.win64.
3. Optional: Open the silent-install.ini file in a text editor and update default
values.
4. Start the Installation Manager silent installation process.
Chapter 6. Silent installation 83

Option Description
Windows installc –acceptLicense
Other operating systems ./installc –acceptLicense
Results
The Installation Manager software is successfully installed on the system. You can
now proceed with silently installing Maximo Asset Management.
Silently installing Maximo Asset Management and related middleware
You can deploy Maximo Asset Management and associated middleware silently to
perform an unattended installation based on predefined settings.
Before you begin
You must complete a successful installation to produce a response file that can be
used to silently install Maximo Asset Management and related
middleware. Alternatively, you can use one of the sample response files that are
provided on the product media and modify the sample file.
If the response file was created on a different system, ensure that all values that are
recorded in the response file are valid for the target system. Ensure that the path
values that were defined when the response file was created are still valid for the
target system. For example, you might need to update the repository location
parameter values to indicate the correct path for product and middleware
installation images.
If you are installing the product in a directory different from the path used during
creation of the response file, update the installLocation parameter value. If you
update the value for the installLocation parameter, you must also provide a new
value for the profile id parameter.
Procedure
1. Copy the response file that you generated earlier and the Maximo Asset
Management files to the target system.
2. Open a command prompt and change directory to the location of the
Installation Manager program that is appropriate for your operating system, for
example, cd /opt/IBM/InstallationManager/eclipse/tools/.
3. Silently start the Installation Manager program.
imcl -input responsefilename
-log logfilename-acceptLicense
The -input parameter determines the response file to use, for example,
/SI/tpaeInstallerRsp20130716105258.xml. The -log parameter determines
where log files are written, for example, /tmp/linuxDB2WASMAM_Log.xml. You
must include the full path when you specify the response and log files.
Results
The installation proceeds silently with the values that you provided in the response
file. Using different response files as input, you can silently install middleware on
separate systems. You can then use another response file to silently install Maximo

Asset Management on the system that is designated as the administrative
workstation.
Silently uninstalling Maximo Asset Management and related
middleware
You can silently uninstall Maximo Asset Management and associated middleware
based on settings that were used during the installation.
Procedure
1. Open a command prompt and change to the launchpad_home
SilentResponseFilesInstaller directory, which contains the sample
uninstallation response file.
2. Update the sample uninstallation response file with values that are used in
your environment.
3. Silently start the Maximo Asset Management uninstallation program.
imcl -input responsefilename
-log logfilename-acceptLicense
The default home directory for the imcl command is c:Program
FilesIBMInstallation Managereclipsetools on Windows systems and
/opt/IBM/InstallationManager/eclipse/ on Linux and UNIX systems.
The -input parameter determines the response file to use, for example,
C:tmpinstall_response.xml.
The -log parameter determines where log files are written, for example,
C:tmpsilent.log.
You must include the full path when you specify the response and log files.
The -acceptLicense parameter is used to accept the license automatically.
4. You can remove the Installation Manager software from the system using the
uninstall program.
uninstallc
Table 6. Location of uninstallc command
Windows Other operating systems
Admin
64-bit C:ProgramDataIBMInstallation
Manageruninstall
Admin
var/ibm/InstallationManager/uninstall
User
64-bit C:UsersUser IDAppData
RoamingIBMInstallation
Manageruninstall
User
User Home/var/ibm/InstallationManager/
uninstall
Chapter 6. Silent installation 85

Chapter 7. Silent configuration
The silent configuration option allows you to interact with the Maximo Asset
Management configuration program by using a command prompt and a response
file.
The following tasks are required for silent configuration:
1. “Creating silent response files for middleware configuration”
2. “Creating a response file for silent Maximo Asset Management configuration”
on page 88
3. “Silently configuring middleware” on page 89
4. “Silently configuring Maximo Asset Management” on page 89
Creating silent response files for middleware configuration
You create a response file by modifying one of the sample response files that is
provided. The configuration program can then be run silently using the response
file for input.
Procedure
1. Create a copy of the sample file, for example, my-cfg-silent-win.properties.
Sample response files are in launchpad_homeSilentResponseFilesConfigTool.
2. Open the response file in a text editor, update values as required, and save the
file.
Ensure that all values listed in the response file are valid for the target system,
particularly path values. For example, you might need to update the
WAS.InstallLocation parameter value to indicate the correct path for
WebSphere Application Server Network Deployment relative to the target
system.
If there are any Maximo Asset Management components you do not want to
automatically configure, set the appropriate property value to false. For
example, if you do not want to configure WebSphere Application Server
Network Deployment on the system, set the WAS.ND.AutomateConfig value to
false.
What to do next
After you have completed silent middleware configuration, you can proceed with
silently configuring Maximo Asset Management.
Related tasks:
“Silently configuring middleware” on page 89
Middleware used with Maximo Asset Management can be configured silently by
using a configuration response file.
Sample silent middleware configuration response files
Several sample response files are provided on the IBM Maximo Asset
Management7.6 product image. You can use a sample response file and modify it
according to your needs.

Sample files
Silent response files are in the launchpad_homeSilentResponseFilesConfigTool
directory of the product image.
Table 7. Samples of silent response files for middleware
File Description
cfg-silent-aix.properties Configure Maximo Asset Management
middleware on AIX.
cfg-silent-linux.properties Configure Maximo Asset Management
middleware on Linux.
Creating a response file for silent Maximo Asset Management
configuration
You create a response file by modifying one of the sample response files provided
according to your needs. The configuration program can then be run silently using
the response file for input.
Before you begin
There are several sample response files provided on the IBM Maximo Asset
Management product image. The files are in the directory where you
uncompressed the product image under the SilentResponseFileConfigTool
directory.
About this task
When you run the configuration program in silent mode, it uses the data in the
response file to configure the product.
Procedure
1. Create a copy of the sample file and name it something appropriate, for
example, my-maximocfg-silent-win.properties.
2. Open the response file in a text editor, update values as required, and save the
file.
Ensure that all values listed in the response file are valid for the target system,
particularly path values. For example, you might need to update the
WAS.InstallLocation parameter value to indicate the correct path for
WebSphere Application Server Network Deployment relative to the target
system.
If there are any Maximo Asset Management components you do not want to
automatically configure, set the appropriate property value to false. For
example, if you do not want to configure WebSphere Application Server
Network Deployment virtual member manager on the system, set the
WAS.VmmFullyAutomatedConfig value to false.
Related tasks:
“Silently configuring Maximo Asset Management” on page 89
Maximo Asset Management can be configured silently by using an configuration
response file.

Silently configuring middleware
Middleware used with Maximo Asset Management can be configured silently by
using a configuration response file.
Procedure
1. Copy the response file you created earlier to the target system.
2. Open a command prompt and start the configuration program silently.
reconfigurePae
-action deployMiddlewareConfiguration
-inputFile responsefilename
The responsefilename parameter determines the response file to use, for example,
C:tmpmy-cfg-silent.properties. You must include the full path when you
specify the response and log files.
Results
The configuration proceeds silently with the values that you provided in the
response file.
What to do next
You can modify the silent configuration response file, copy it to another server, and
perform further configuration. For example, you can use the configuration
program to silently configure WebSphere Application Server Network Deployment
on one server, and then modify the response file to configure IBM Tivoli Directory
Server on another server.
Silently configuring Maximo Asset Management
Maximo Asset Management can be configured silently by using an configuration
response file.
Procedure
1. Copy the response file you created earlier to the target system.
2. Open a command prompt and start the Maximo Asset Management
configuration program silently.
reconfigurePae
-action deployConfiguration
-inputFile responsefilename middlewarecomponents
C:tmpmy-cfg-silent.properties. The middlewarecomponents parameter
indicates which middleware component to configure, for example, -dbvendor
DB2 or -j2eevendor WebSphere. In most cases, you configure middleware
components together. You must include the full path when you specify the
response files.
Results
The configuration proceeds silently with the values that you provided in the
response file.
Chapter 7. Silent configuration 89

What to do next
You can modify the silent configuration response file, copy it to another server, and
perform further configuration. For example, you can use the configuration
program to silently configure WebSphere Application Server Network Deployment
on one server, and then modify the response file to configure IBM Tivoli Directory
Server on another server.
Silently remove middleware configuration
You can use the same file you used to silently configure middleware to remove the
configuration information.
About this task
Maximo Asset Management middleware configuration can be removed silently
using the same configuration response file that was used to configure the product
previously. You must edit the configuration response file that was used to
configure the product previously before it can be used to remove configuration
information from the product.
Procedure
1. Change to the directory containing the response file used to silently configure
previously.
2. Make a copy of the response file and rename it. For example, rename the file to
my-uncfg-silent.properties.
3. Open the file in a text editor and change the MW.Operation property value to
unconfigure, and then save the file.
4. Open a command prompt and start the Maximo Asset Management
unconfiguration program silently.
reconfigurePae
-action deployMiddlewareConfiguration
-inputFile responsefilename
C:tmpmy-uncfg-silent.properties. You must include the full path when you
specify the response file.
Remove product configuration silently
You can use the removeConfiguration action of the reconfigurePae command to
remove Maximo Asset Management configuration information.
About this task
The removeConfiguration action is used to remove Maximo Asset Management
configuration from the database and application server that was performed by the
configuration tool. This action is equivalent to running the
removeJ2EEConfiguration and removeDatabaseConfiguration actions together.
Procedure
1. Log on to the Maximo Asset Management administrative workstation.
2. Open a command prompt and change directory to Install_HomeConfigTool
scripts.

3. Start the Maximo Asset Management configuration program silently.
reconfigurePae -action removeConfiguration
-dbuser userid
-dbpwd password
-wasuser userid
-waspwd password
The -dbuser and -dbpwd parameters are the user ID and password used to
configure the database. The -wasuser and -waspwd parameters are the user ID
and password used to configure IBM WebSphere Application Server Network
Deployment.
Chapter 7. Silent configuration 91

Chapter 8. Programmatically verifying that the installation was
successful
After you have exited the Maximo Asset Management 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 Maximo Asset Management 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 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 smpconfigtoolslogs
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.
2. Ensure the JAVA_HOME environment variable is set properly to the location of
a JRE 1.7 installation.
3. To verify product installation, from the administrative workstation, change
directory to ibmsmpconfigtoolscripts and run the
installValidation.[sh|bat] command. For either command, use the
parameters in Table 1.

Table 8. 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 ibmsmpHealthValidation
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 Maximo Asset
Management administrator user
ID. For example, maxadmin.

Table 8. Verification utilities parameters (continued)
Program Syntax parameters Input
-maxpwd Provide the password for the
administrator user ID.
For example,
installValidation.bat -action validate
Results
The installValidation.bat validation utility results are logged in
ctginstallvalidationtrace00.log. This log is found in the smpconfigtoolslogs
directory on the administrative workstation.
Chapter 8. Programmatically verifying that the installation was successful 95

Chapter 9. Verifying the installation manually
After you exit the Maximo Asset Management 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_homeconfigtoolslogsCTGConfigurationXX.log file.
About this task
To further verify that the Maximo Asset Management installation was completed
successfully, perform the following verification procedures:
Procedure
1. Examine the CTGConfigurationXX.log files for success messages.
The following success messages are found in the CTGConfigurationTraceXX.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 CTGConfigurationTraceXX.log, indicate that the configuration was successful:

<symptom>CTGIN2228I.*client</symptom>
<symptom>CTGIN2230I.*node</symptom>
<symptom>CTGIN2232I.*NodeAgent</symptom>
<symptom>CTGIN2240I.*server</symptom>
<symptom>CTGIN2238I.*security</symptom>
Search the CTGConfigurationTraceXX.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 Maximo Asset Management
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 by using the configuration tool and selecting the update database
task. 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, navigate through the GoTo menu to
verify that it has been populated with the applications you expect. If you
experience access problems with the product, clear the cache of your browser
and try again.

Chapter 10. 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.

Chapter 11. Installation and configuration programs log
information
Log files generated by the Maximo Asset Management and configuration programs
can provide details on completed and configuration tasks and any errors that
might occur.
Maximo Asset Management installation and configuration
programs log locations
Maximo Asset Management and associated middleware is installed through
Installation Manager. The log files of Installation Manager are common to any
installation, regardless of which components you choose to install. Log files for the
Maximo Asset Management installation program are found on the system where it
is run.
Table 9. Log file directories
Log file directory
C:ProgramDataIBMInstallation Managerlogs
/var/ibm/InstallationManager/logs
C:IBMSMPConfigToollogs
opt/IBM/SMP/ConfigTool/logs
In addition, if you receive an error credited to the J2EE server, examine the logs in
the log directories for the deployment manager, node agent, and WebSphere
Application Server application server.
When engaging IBM product support services, be prepared to provide these log
files in an archive file. The LogZipper utility provided in the install_home
configtoolscripts directory can be used for this task. If you use the LogZipper
utility, all relevant log files are archived in install_home/configtool/debug/
YYYYMMDD_hhmmss.zip.

Chapter 12. Post installation tasks
There are several post installation tasks required in order to complete the Maximo
Asset Management deployment.
Accessing product documentation
Accessing the Maximo Asset Management Knowledge Center documentation and
product online help.
Important: The WebSphere Application Server deployment manager must be
restarted after the installation of Maximo Asset Management. Restarting enables
the full function of the Knowledge 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 Maximo Asset Management.
1. Stop the deployment manager by running the following command:
c:Program FilesIBMWebSphereAppServerprofiles<dmgr profile>binstopManager
-username wasadmin -password <password>
2. Start the deployment manager by running the following command:
c:Program FilesIBMWebSphereAppServerprofiles<dmgr profile>binstartManager
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 Maximo Asset Management, are
affected (stopped).
Installing help information in a new language
Help information is available in multiple languages. If you need to support
multiple languages for Maximo Asset Management, you optionally install the help
information for other languages. Before you can use multi-language help
information in Maximo Asset Management, you must first install it using the
About this task
Multi-language help information for Maximo Asset Management is available on Fix
Central as a fix pack that includes multiple language plug-ins. The fix pack must
be downloaded from Fix Central and then applied with the Maximo Asset
Management configuration program.
Procedure
1. Download the fix pack that contains the multi-language Maximo Asset
Management documentation from the Fix Central support site to a temporary
location on the administrative workstation.

2. Start the Maximo Asset Management launchpad.
3. Click Configure Product.
4. Select the location of the Maximo Asset Management installation you want to
configure, and then click Launch the Tivoli's Process Automation Suite
5. From the Configuration Actions page, click Add Additional Help Plug-ins.
6. Click Browse to locate the fix pack file that you downloaded.
7. Optional: Select Deploy the product help EAR to the application server to
install the updated help information to Maximo Asset Management now. If you
do not select this option, the Maximo Asset Management help information EAR
file is rebuilt, but not deployed to the application server.
8. Click Finish to rebuild the Maximo Asset Management help information EAR
file. If you selected the Deploy the product help EAR to the application server
option, the help information EAR file is deployed to the application server.
Configuring initial data
After you successfully install and configure Maximo Asset Management
components, you must complete several data configuration tasks before you use
Maximo Asset Management.
Before you begin
v Create security groups and add users to the security groups.
v If you are using a directory server as part of your deployment, ensure that the
user names are created in your LDAP repository.
v To ensure that you have the accounting information that you need, consult the
Financial department of your organization.
Procedure
1. Log in to Maximo Asset Management by entering the user name maxadmin and
the password that you specified during the installation.
2. If you didn't set the SMTP server by using the Configuration tool, configure
the SMTP server to send users email notifications of system events. To learn
about the range of system properties in Maximo Asset Management, see the
System properties information.
a. From the Go To menu, select System Configuration > Platform
Configuration > System Properties.
b. In the Global Properties table window, use the filter feature to search for
and expand the mail.smtp.host property.
c. In the Global Value field, specify the SMTP host name.
d. Select the mail.smtp.host check box.
e. From the Common Actions menu, click Live Refresh.
f. In the Live Refresh window, click OK.
g. In the Global Properties table window, use the filter feature to search for
the mxe.adminEmail property.
h. Expand the mxe.adminEmail property and in the Global Value field,
specify your email address.
i. Select the mxe.adminEmail record check box.
j. From the Common Actions menu, click Live Refresh.
k. In the Live Refresh window, click OK.

3. Define a currency code.
a. From the Go To menu, select Financial > Currency Codes
b. Click New Row and specify a currency code and a description. For
example, enter USD for United States of America Dollar.
c. Click Save Currency.
4. Define item sets and company sets.
a. From the Go To menu, select Administration > Sets.
b. Click New Row.
c. Specify an item set name. For example, enter IT Items.
d. In the Type field, specify ITEM.
e. Click New Row.
f. Specify a company set name. For example, enter IT Comps.
g. In the Type field, specify COMPANY.
h. Click Save Sets.
5. Create an organization.
a. From the Go To menu, select Administration > Organizations.
b. From the toolbar, click New Organization.
c. Specify an organization name. For example, enter EAGLENA, and enter a
long description.
d. Specify the base currency that you defined in step 3.
e. Specify the item set and the company set that you defined in step 4.
f. In the Default Item Status field, set the status to PENDING.
g. Click the Sites tab and select New Row under the Sites table window.
h. Specify a site name. For example, enter Factory01 and enter a long
description.
i. Click Save Organization.
6. Create a general ledger account component.
a. From the Go To menu, select System Configuration > Platform
Configuration > Database Configuration.
b. From the More Actions menu, select GL Account Configuration.
c. Click New Row.
d. Specify a component name. For example, enter MYCOMPONENT.
e. Specify a length for the component. For example, enter 5.
f. Specify a type for the component. For example, select Alphanumeric.
g. Click OK.
7. Apply changes to the database.
a. From the More Actions menu, select Manage Admin Mode.
b. Select Turn Admin Mode ON and click OK. This task takes several
minutes to complete. You can click Refresh Status to view the progress.
c. From the More Actions menu, select Apply Configuration Changes.
Ensure that the status To Be Changed does not appear in the status column
of the listed objects.
d. From the More Actions menu, select Manage Admin Mode.
e. Select Turn Admin Mode OFF and click OK. If you do not turn off Admin
Mode, cron tasks fail.
8. Create a general ledger account.

a. From the Go To menu, select Financial > Chart of Accounts.
b. In the Organizations table window, select your organization.
c. From the More Actions menu, select GL Component Maintenance.
d. In the Components table window, select the component that you entered
in step 6 and click New Row.
e. Specify a GL Component value and a description, and then click OK.
f. In the GL Accounts table window, click New Row.
g. Specify a General Ledger Account and click Save GL Account.
h. From the Go To menu, select Administration > Organizations.
i. Find your organization and select the record.
j. In the Clearing Account field, specify the general ledger account that you
created.
k. Select Active.
l. Click Save Organization.
9. Authorize a security group to modify a general ledger component type.
a. From the Go To menu, select Security > Security Groups.
b. Select the group that provides authorization. For example, select
FINANCE.
c. Click the GL Components tab.
d. For each GL Component that is listed, select the Authorized check box. As
a shortcut, you can select Authorize Group to Change All GL Component
Types.
e. Click Save Group.
10. Update the company-related accounts.
a. From the Go To menu, select Financials > Chart of Accounts.
b. Select your organization and from the More Actions menu, select
Company-Related Accounts.
c. Click New Row and specify the company type Courier.
d. Enter an account number in the RBNI Account, AP Suspense Account,
and AP Control Account fields. You can specify the same account number
in each field.
e. Click OK.
f. From the More Actions menu, select Update Database and click OK.
11. Create a default insert site.
a. From the Go To menu, select Security > Users.
b. Find maxadmin and select the record.
c. In the Default Insert Site field, specify the site name that you created in
step 5.
d. In the Storeroom Site for Self-Service Requisitions field, specify the same
site name.
e. Click Save User.
12. Define work types. Work types denote the importance of the work task.
a. From the Go To menu, select Administration > Organizations.
b. Find your organization and select the record.
c. From the More Actions menu, select Work Order Options > Work Type.
d. Click New Row.
e. In the Work Order Class field, select WORKORDER.

f. Specify a Work Type. For example, enter MAJOR.
g. Set the Start Status to In Progress.
h. Set the Complete Status to Completed.
i. Click New Row and repeat steps f-i to create another work order class with
a different work type. For example, enter MINOR.
j. Click New Row and repeat steps f-i to create a CHANGE work order class
with a different work type. For example, enter SIG to represent a significant
change.
k. Click OK and click Save Organization.
Integrating data with external applications
System properties
Synchronizing users and groups
When you select application server security, the scheduled synchronization of users
and groups that occurs between LDAP repositories and Maximo Asset
Management is governed by the federated repositories.
Before you begin
View the cron task configuration information in the Administering section of the
Knowledge Center.
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 Maximo
Asset Management, complete the following steps:
Procedure
1. Open a web browser and point to http://host name:port/maximo.
2. Log in to Maximo Asset Management using the maxadmin user ID.
3. From the Maximo Asset Management interface, navigate to Go To > System
Configuration > Platform Configuration > Cron Task Setup.
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.
Adding sample data to the Maximo Asset Management database post
configuration
Using the maxinst command, you can add sample data to the Maximo Asset
Management database after the initial installation and configuration of Maximo
Asset Management.

Before you begin
The maxinst command does not provide default values for table space parameters.
You must specify the data table space name and the index table space name that
you specified during the installation. The maxinst command replaces the current
database schema and data. Do not add sample data to the Maximo Asset
Management database if you want to preserve records currently stored in the
database.
About this task
If you created a database either automatically or manually during the installation,
you can use the maxinst command to create a sample data in that database
instance.
Procedure
1. Back up the existing database.
2. Unzip the install_homeIBMSMPMaximotoolsmaximoenmaxdemo.dbtype.zip
file. Replace the dbtype variable with the extension that is appropriate for the
type of database you used for the Maximo Asset Management deployment.
Available options are ora, sqs, or db2.
3. Change the install_homeIBMSMPMaximotoolsmaximoenmaxdemo.dbtype file
to the name of the Maximo Asset Management database you configured during
the initial deployment. For example, rename the file to max76db.db2
4. Open a command prompt and change to the install_homeIBMSMPMaximo
toolsmaximo directory.
5. Populate the database with sample data. You must specify the table space name
parameters when you run the maxinst command.
maxinst -stablespacename -ttablespacename -imax76db For example, for
Oracle Database or for DB2, enter maxinst -sMAXDATA -tMAXDATA -imax76db.
The system reads the maximo.properties file for database connectivity
information. The maximo.properties file is in the install_homeIBMSMP
MaximoApplicationsMaximoProperties directory.
6. Populate the database by running commands with specific parameter values.
Use the following maxinst database parameters:
Parameter Description
-a Database alias. If not specified, the alias
mxe.db.url.property is used.
-d Log file directory. If you are using the -l
parameter, the log file is sent to the specified
directory. Otherwise, the log file is sent to
the log directory, for example
install_homeIBMSMPMaximotools
maximologs.
-e Runs the SQL. This parameter is required
and already present in the maxinst.bat file.
-f File name for the properties file. If not
specified, maximo.properties is used.
-i File name of the input file (without path or
extension). If not specified, the default file
name Unlcvt is used.
-k Directory of the properties file.

Parameter Description
-l Creates a detailed log file. This parameter is
already present in the maxinst.bat file.
-o If you are using the -l parameter, the -o
parameter specifies the file name for the log
file.
-p Password for the database connection. If not
specified, the mxe.db.password property or
MAXIMO is used. If MAXIMO is used, it must be
entered in uppercase letters.
-s Required value: Table space for index
storage.
-t Required value: Table space for table
storage.
-u User name for database connection. If not
specified, the mxe.db.user property or
MAXIMO is used. If MAXIMO is used, it must be
entered in uppercase letters.
-x Required value for UNIX: Fixes the doclink
file separators in UNIX environments. Note:
If a UNIX environment is deployed without
using this parameter, the attached
documents do not function properly.
-y Multiplies the column width for strings by 2.
This value is required for double-byte
character sets.
7. From the install_homeIBMSMPETC directory, open the install.properties
file and specify the installation-related properties. You can add these properties
to the database from the System Properties application.
Results
The Maximo Asset Management database is populated with sample data.
If an error occurs when you run the maxinst command, check the log file in the
install_homeIBMSMPMaximotoolsmaximologs directory. If the maxinst
command fails, you must correct the error and rerun the maxinst command to
complete the Maximo database schema deployment before you can start the
application.
.

Chapter 13. Installing Version 7.5 industry solutions
Version 7.5 of industry solutions can be installed on Maximo Asset Management
7.6.
Version 7.5 of industry solutions can be installed on Maximo Asset Management
7.6 using several methods. The industry solution can be installed from the
launchpad if one is included with the industry solution package. The industry
solution can also be installed from the command-line. Silent installation is also
supported.
Ensure that you download the latest version and fixes available for the industry
solution or add-on before you install it. Refer to the Maximo Upgrade Resources
support page for the latest information about industry solution and add-on
requirements.
http://www.ibm.com/support/docview.wss?uid=swg21266217
Installing version 7.5 industry solutions from the launchpad
If a launchpad is included with an industry solution package, you can use it to
install the industry solution on Maximo Asset Management 7.6.
Procedure
1. Log on to the administrative workstation.
2. Create a backup image of your Maximo Asset Management 7.6 administrative
workstation. When you install version 7.5 industry solutions in Maximo Asset
Management 7.6, you do not have an automated uninstallation method that
returns the system to its previous state.
3. Open the archive for your industry solution package, and start the launchpad.
4. Click Install from the menu of options.
5. Follow the steps in the installation program.
6. When the installation is complete, click Done. After the industry solution
installation program exits, the Maximo Asset Management 7.6 configuration
tool starts.
7. From the Deployment Operations panel, select the options for applying changes
to the database, and building and deploying application EAR files to complete
the deployment.
Installing version 7.5 industry solutions from the command line
Version 7.5 industry solutions can be installed in Maximo Asset Management 7.6
from the command line.
Procedure

3. Start the process solution installation program by changing to the
install_homebin directory of your Maximo Asset Management 7.6 installation
and use the solutionInstaller command.
solutioninstaller.bat -pkgpath path_to_industry_solution_package
-license accept
The -pkgpath option specifies the path to the industry solution package.
Replace path_to_industry_solution_package with the path to the industry solution
package file you are installing. The -license option is used to accept license
terms. For example,
solutioninstaller.bat -pkgpath
C:TEMPSpatial75_launchpadInstallSPATIALSpatial75.zip
-license accept
installation program exits, the Maximo Asset Management 7.6 configuration
tool starts.
the deployment.
Installing version 7.5 industry solutions silently
Version 7.5 industry solutions can be installed in Maximo Asset Management 7.6
silently from the command line.
Procedure
3. Start the process solution installation program by changing to the
install_homebin directory of your Maximo Asset Management 7.6 installation
and use the solutionInstallerGUI command.
solutioninstallerGUI.bat -pkgpath path_to_industry_solution_package -nl locale
-S -license accept
The -pkgpath option specifies the path to the industry solution package.
Replace path_to_industry_solution_package with the path to the industry solution
package file you are installing. The -nl option specifies the language that is
used during the installation. Replace locale with the abbreviation for the
language to use. The -s option indicates that the installation is processed
silently. The -license option is used to accept license terms. For example,
solutioninstallerGUI.bat -pkgpath
C:TEMPSpatial75_launchpadInstallSPATIALSpatial75.zip
-nl es -S -license accept
.
installation program exits, configure it with the Maximo Asset Management 7.6
configuration tool.

the deployment.
Chapter 13. Installing Version 7.5 industry solutions 113

Chapter 14. Maintaining EAR files
This section contains information about maintaining Maximo Asset Management
EAR files.
The following instructions are used to manually build or uninstall the Maximo
Asset Management maximo.ear and maximoiehs.ear files on WebSphere Application
Server Network Deployment.
Although the Maximo Asset Management 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 Maximo Asset Management must be installed into a WebSphere Application
Server Network Deployment application server. However, Maximo Asset
Management can be run within the framework of a WebSphere Application
Server Network Deployment cluster. If you want to deploy Maximo Asset
Management in a cluster, you can either redeploy the Maximo Asset
Management EAR files into a cluster, or, create a cluster from the application
server used during the install. If you have already installed Maximo Asset
Management 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
116), 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 116).
v If you have installed Maximo Asset Management into a development
environment, you might at some point like to migrate the deployment into a test
or 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” on page 116 should be performed for
both applications.
Building EAR files
You can manually build Maximo Asset Management 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 Maximo Asset Management EAR files, complete the following
steps:
Procedure
1. Build the maximo EAR file:

Windows
install_homemaximodeploymentbuildmaximoear.cmd
Linux and UNIX
install_home/maximo/deployment/buildmaximoear.sh
2. Build the maximo help system EAR file:
Windows
install_homemaximodeploymentbuildmxiehsear.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 Maximo Asset Management
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
Maximo Asset Management applications are named maximo and maximoiehs.
4. Click Uninstall.
Manually installing applications in WebSphere Application Server
Network Deployment
Maximo Asset Management applications can be added to WebSphere Application
Procedure
1. Log on to the WebSphere Application Server Network Deployment
administrative console.
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.
Figure 15. Map virtual hosts for Web modules
Chapter 14. Maintaining EAR files 117

Chapter 15. Command line configuration
Maximo Asset Management includes a configuration program that is accessed from
the command line. This command line configuration program performs the same
duties as the Maximo Asset Management configuration program user interface.
Command line configuration is used to quickly update configuration values when
you choose to not use the configuration tool user interface.
When you install a fix pack or upgrade Maximo Asset Management, the
configuration program uses values that are recorded from the previous
deployment. These values are stored on the administrative system in the
install.properties and maximo.properties files that are located under the
install_homeetc and install_homemaximoapplicationsmaximoproperties
directories.
If you make any environmental changes to any of the systems that are used for the
original deployment, they must be recorded in the install.properties and
maximo.properties files. Typically, these types of changes would include changing
a host name or updating a password, for example.
You can update these values manually, or you can use the configuration command
line interface tool to update configuration values for your existing deployment
when they change. Properties that are specified for the configuration command line
interface tool, either as parameters, or in an input properties file, replace existing
properties in the maximo.properties and install.properties files. Properties are
encrypted when they are saved.
You can complete the following tasks with the configuration command line
interface tool:
v Change the security model for the original deployment. For example, you can
migrate from Maximo Asset Management-based security to WebSphere
Application Server security. This option is not available for Oracle WebLogic
Server.
v Confirm that updated property values conform to required input domains.
Validate credentials, host names, and available ports.
v Update database or application server configuration settings without the server
available. These values cannot be validated in this scenario.
v Clone an existing environment and use the configuration command line interface
tool to reconfigure the administrative workstation to use the new servers. The
cloned environment must use the same directory structure as the original.
v Create an environment (non-cloned) and use the configuration command line
interface tool to create all required artifacts database, table spaces, and
application server objects, for example.
v Remove configuration from a previously configured database.
Configuration parameter validation
Use the Maximo Asset Management command line configuration program to
validate input in the same way the Maximo Asset Management configuration
program validates input in the user interface.

You can validate the following items with the Maximo Asset Management
command line configuration program.
v Host names or IP addresses are correctly formatted and are reachable.
v User IDs and passwords meet length and character set criteria.
v Specified credentials are used to authenticate to WebSphere Application Server.
v Specified port values are listening on the corresponding host. Port values contain
numbers only and are within a valid range.
v Middleware installation directories that are supplied exist.
v Preconfigured middleware can authenticate to the product database.
v Required objects such as JMS queues, SIB destinations, databases, and table
spaces exist.
v Required WebSphere Application Server virtual member manager users exist.
v Sufficient authority is available to create WebSphere Application Server virtual
member manager users.
v Remote login credentials are valid.
v There is enough space in the supplied directories to create database objects.
Input properties files
You can use property files as input for the Maximo Asset Management
command-line configuration program.
The following sample input property files are provided with the Maximo Asset
Management command-line configuration program.
v DB2_Sample_input.properties
v Oracle_Sample_input.properties
v SQLServer_Sample_input.properties
v WebSphere_App_Server_Sample_input.properties
These sample files are in the ibmsmpconfigtoolssamples directory. Each of these
sample files contains properties that are associated with a specific database or
application server type. They contain comments and properties you can update
with values from your environment. You can then use the updated file as input for
the configuration command line interface tool with the –input parameter.
All input properties, introduced from either the command line or in the input
properties file, are validated before they are used. After validation is successful, the
maximo.properties and install.properties files are updated with the values you
provided.

Command line interface parameters
The following parameters can be used with the configuration command line
program to configure your environment.
Table 10. Maximo Asset Management command line configuration program parameters
Parameter name Description
-action Configuration action.
v addLanguages – Adds additional languages to a current
deployment.
v configureProducts - Configures more products after an initial
installation and configuration. This action can configure multiple
products after they are installed and can also be used in an
upgrade scenario.
v deployConfiguration - Configures initial installation. This action
can configure multiple products after they are installed. This
action is used for new installations only.
v deployDatabaseConfiguration - Validates command input and
defines configuration property values for a new database for the
current product.
v deployJ2eeConfiguration - Validates command input and
defines configuration property values for a new application
server for the current product.
v deployMiddlewareConfiguration – Configures initial middleware
installation.
v disableAppSecurity - Disables application security for the
application. Security is handled entirely through Maximo Asset
Management. This action sets the mxe.useAppServerSecurity
property to a value of 0. This value is written to the database
when updated.
v disableDB2TextSearch - Enable the full text search feature on a
DB2 database.
v enableAppSecurity – Enables application security for the
application. This action sets the mxe.useAppServerSecurity
property to a value of 1, and updates the
mxe.ldapUserManagement flag. This value is written to the
database when the database is updated.
v enableDB2TextSearch – Enables the full text search feature on a
DB2 database.
v reapplyAppServerTuning – Reapplies tuning configuration to an
application server.
v removeDatabaseConfiguration – Removes product configuration
information from a previously configured database.
v removeJ2EEConfiguration – Removes application server
configuration that was added by the configuration tool.
v updateApplication – Updates the Maximo Asset Management
application by updating the database and redeploying
application EAR files.
Chapter 15. Command line configuration 121

Table 10. Maximo Asset Management command line configuration program parameters (continued)
v updateDatabaseConfiguration – Updates existing database
configuration values.
v updateJ2eeConfiguration - Updates existing application server
v validateAndUpdateDatabaseConfiguration – Validates
reconfiguration command line interface tool input and then
updates existing database configuration property values.
v validateAndUpdateJ2eeConfiguration - Validates reconfiguration
command line interface tool input and then updates existing
database configuration property values.
v validateDatabaseConfiguration - Validates database
configuration values specified as input for the reconfiguration
command line interface tool.
v validateJ2eeConfiguration - Validates application server
configuration values that are specified as input for the
reconfiguration command line interface tool.
v removeConfiguration - Removes database and application
configuration performed by the configuration tool.
The actions that modify the security setting for Maximo Asset
Management also updates Maximo Asset Managementweb.xml
files.
-additionalLangs Adds one or more additional languages to the deployment.
This parameter requires one or more locale abbreviations for input.
For example, ES for Spanish.
-allowUpdateDB The database update task is run to add the languages that are
specified to the database.
-applicationServerName Name of the application server.
-applicationServerNode Name of the application server node.
-automatedbconfig Automates the configuration of the database. Use this parameter to
create the database instance, database users, the database, table
spaces, and creates database schema.
-automatej2eeconfig Automates the configuration of WebSphere Application Server.
Using this parameter creates, for example, JMS queues and
profiles.
-buildAndDeployEAR Rebuilds and deploys application EAR files. Application EAR files
must be rebuilt and redeployed for configuration changes to take
effect in the application.
-buildears Rebuilds application EAR files.

-bypassJ2eeValidation Skips the validation and configuration of the application server.
If you use this parameter, then you must manually configure the
application server before you can deploy Maximo Asset
Management.
Validation of a manually configured application server requires
logging in to the application server with application server
administrative credentials. If you do not want to provide those
credentials to the configuration program, you can skip the
validation task.
If you use the bypassJ2eeValidation parameter, you cannot also
use the following parameters:
v applicationServerName
v applicationServerNode
v automatej2eeconfig
v buildAndDeployEAR
v createResourcesIfMissing
v deployhelpear
v deploymaximoear
v enableappsecurity
v enableEnhancedNavigation
v enableSkin
v inputfile
v j2eeserverport
v usermanagement
v wasuser
v waspwd
-bypassUpdateDB Specifies that the database update task is not run and the
installation program does not update the database.
Languages files for the locales that are specified are built into the
application EAR file.
Use this parameter if you have run the database update task and
included the language files in the database through another
method.
-createResourcesIfMissing Creates any resources that are not found during configuration.
-db2_english_only Specifies that alphanumeric data is stored as a varchar data type.
Using this parameter limits you to using English in the user
interface.
If you do not use this parameter, alphanumeric data is stored as a
vargraphic data type.
-db2textsearchport Port that is used by the DB2 server for full text search.
-dbname Name of the database.
-dbpwd Password for the user ID that accesses the database.
-dbrxapwd Password for the user ID used to access a remote middleware
server.
-dbrxauser User ID used to access a remote middleware server.

-dbserverhost Host name of the database server.
-dbserverport Port name of the database server.
-dbuser User ID that accesses the database.
-dbvendor Database software name.
v DB2
v Oracle
v SQLServer
-deleteInstanceUsersAndGroups Removes the instance owner and database user IDs and associated
groups from the DB2 server. This parameter has cannot be used
with and Microsoft SQL Server.
The deleteInstanceUsersAndGroups parameter requires the
dbrxauser and dbrxapwd and the dbuser and dbpwd parameters.
-deleteWASprofiles Deletes the WebSphere Application Server profiles that are created
for the application.
-deployDemoData Includes sample data.
-deployhelpear Deploys Maximo help application EAR file.
-deploymaximoear Deploys Maximo application EAR file.
-enableappsecurity Enables application security for the application. This parameter
works the same as the enableAppSecurity action.
This action sets the mxe.useAppServerSecurity property to a value
of 1, and updates the mxe.ldapUserManagement flag. This value is
written to the database when updated.
-enableEnhancedNavigation Enables enhanced navigational elements in the user interface,
including enhancements for switching between applications and
viewing record lists.
The enableEnhancedNavigation parameter must be used with the
enableSkin parameter.
If you enable enhanced navigation, and then you enable a different
user interface skin with the –enableSkin parameter, you must
re-enable enhanced navigation.
-enableMultiTenancy Enables the multitenancy feature.
Multitenancy refers to software or services that can be configured
to serve multiple groups of clients referred to as tenants. Each
group of tenants is served by an instance of the software that uses
data that only they can access.

-enableRestrictivePasswordPolicy Enables a more restrictive password policy for Maximo Asset
Management users.
v Login attempts
Standard policy allows 10 login attempts before the account is
locked.
Restrictive policy allows 3 login attempts before the account is
locked.
v Number of times that the forgotten password link can be used
Standard policy allows 5 uses of the forgotten password link
before locking the account.
Restrictive policy allows 3 uses of the forgotten password link
before locking the account.
v Password duration (days)
Standard policy passwords never expire.
Restrictive policy passwords expire after 90 days.
v Password expiration warning (days)
Standard policy does not warn the user that the account
password is about to expire.
Restrictive policy warns the user that the account password is
about to expire seven days before it expires.
v Password threshold
Standard policy does not enforce a password threshold.
Restrictive policy enforces a password threshold of 270
characters.
v Password minimum character length
Standard policy passwords must be at least six characters.
Restrictive policy passwords must be at least eight characters.
v Limit of allowed consecutive characters
Standard policy has no restrictions to the amount of times a
character can be repeated consecutively in a password.
Restrictive policy allows a character to be repeated two times
consecutively in a password value.
v Password can be same value as user name
Standard policy allows you to use the same value for the user
name and password.
Restrictive policy does not allow you to use the same value for
the user name and password.
v Number of numeric characters required in the password
Standard policy does not require numeric characters in a
password value.
Restrictive policy requires one or more numeric characters in a
password value.
v Number of alphabetic characters required in the password
Standard policy does not require alphabetic characters in a
password value.
Restrictive policy requires one or more alphabetic characters in a
password value.

-enableSkin Change the appearance of the user interface.
v Classic
Removes settings for the following properties:
– mxe.webclient.homeButtonHeaders
– mxe.webclient.systemNavBar
– mxe.webclient.tabBreadCrumbs
– mxe.webclient.verticalLabels
– mxe.webclient.skin
v tivoli09
Removes settings for the following properties:
Sets the following property:
– mxe.webclient.skin=tivoli09
v tivoli13
Sets the following properties to a value of 1:
Sets the following property:
– mxe.webclient.skin=tivoli13
-force Indicates that an input property file updates the properties file and
skips the validation of parameters input to the command line tool
through an input properties file.
When you use this parameter, you are not prompted for
confirmation of the property update task.
-inputfile Fully qualified path to the properties file that is used to set
properties in an environment.
Values that are specified as command line parameters for the
configuration command line interface tool supersede values from
the input file.
-j2eeserverhost Host name of the domain manager of the application server.
If deployment manager host name or server port is specified the
thinwsadmin scripts are updated accordingly.
-j2eeserverport Port name of the application server domain manager server.
If deployment manager host name or server port is specified the
thinwsadmin scripts are updated accordingly.
-j2eevendor Application server software.
v WebSphere
v WebLogic
-mtadminpwd Password for the user ID of the multitenancy configuration
manager.

-mtadminuser User ID of the multitenancy configuration manager.
-mtdbpwd Password for the user ID of the multitenancy configuration
manager that is used to connect to the database.
-mtdbuser User ID of the multitenancy configuration manager that is used to
connect to the database.
-removeCreatedArtifacts Removes any artifacts that are created by the configuration tool.
Examples include directories that are created by the configuration
program, JMS objects, and the application server.
-removeInstance Removes the database instance for DB2 and Oracle. This parameter
cannot be used with Microsoft SQL Server.
The removeInstance parameter requires the dbrxauser and
dbrxapwd, and the dbuser and dbpwd parameters.
-setjdbcurl Sets the JDBC connection URL string.
-stopAppServer The application server must be stopped when you add languages.
If you do not use the stopAppServer parameter with the
addLanguages action, you must stop the application server
manually before you use the addLanguages action.
This parameter is used for WebSphere Application Server only.
-unsetjdbcurl Removes the currently used JDBC connection URL string.
-updatedb Runs the updatedb configuration task.
-usermanagement Changes the security configuration of the existing Maximo
deployment.
v j2ee
Change the security setting in Maximo so that both Maximo
users and Maximo groups are managed through application
server security mechanisms.
v mixed
Manage users through application server security mechanisms,
and manage groups using Maximo.
-validateForNewDeploy Validate middleware configuration.
When this parameter is specified, validation is performed as if the
tool was configuring the middleware. Additional configuration
details are checked, including disk space availability and remote
access credentials.
If this parameter is not specified, validation is performed in the
context of a component that is already established in the
environment.
-validateUsers Used with the enableAppSecurity action to validate users exist in
the LDAP repository.
If the users do not exist, the existing security model is not
modified.
-waspwd WebSphere Application Server administrator user ID password.
-wasrxapwd Password for user ID to access remote WebSphere Application
Server server host.

-wasrxauser Operating system user ID used to access remote WebSphere
Application Server host. Typically this user ID is defined either as
Administrator or root.
-wasuser WebSphere Application Server administrator user ID.
This is the user ID that is used to log in to the WebSphere
Application Server administrative client application. Typically, this
user ID is defined as wasadmin.
Command line configuration program actions
Use the command line configuration program to configure new or existing
deployments of Maximo Asset Management.
action updateDatabaseConfiguration
The updateDatabaseConfiguration action is used to update existing database
-action updateDatabaseConfiguration [-force] [-buildAndDeployEAR]
[-dbserverhost hostname] [-dbserverport port number]
[-dbname database name] [-dbuser userid]
[-dbpwd password] [-dbrxauser userid]
[-dbrxapwd password] [-setjdbcurl jdbcurl]
[-unsetjdbcurl] [-inputfile path to input properties file]
action validateDatabaseConfiguration
Use the validateDatabaseConfiguration action to validate current database
configuration properties. This action can be used to verify database properties
before they are updated, or following an update action.
-action validateDatabaseConfiguration [-validateForNewDeploy]
[-dbserverhost hostname]
[-dbserverport port number]
[-dbname database name]
[-dbuser userid] [-dbpwd password]
[-dbrxauser userid]
[-dbrxapwd password] [-setjdbcurl jdbcurl]
[-unsetjdbcurl] [-enableMultiTenancy]
[-mtadminuser userid] [-mtadminpwd password]
[-mtdbuser userid] [-mtdbpwd password]
[-inputfile path to input properties file]
The following properties are required if the -validateForNewDeploy parameter is
used.
v Database.DB2.InstanceAdminGroup
v Database.DB2.InstanceAdminUserName (Windows only)
v Database.DB2.InstanceAdminPassword (Windows only)
v Database.DB2.FencedUser
v Database.DB2.FencedUserPassword
v Database.DB2.FencedGroupName
v Database.DB2.InstanceUserPassword
These properties must be added manually to the install.properties file.

action validateAndUpdateDatabaseConfiguration
The validateAndUpdateDatabaseConfiguration action is used to both validate
reconfiguration command-line interface tool input and then update existing
database configuration property values.
-action validateAndUpdateDatabaseConfiguration [-validateForNewDeploy] [-force]
[-buildAndDeployEAR] [-dbserverhost hostname]
[-dbserverport port number] [-dbname database name]
[-dbuser userid] [-dbpwd password]
[-dbrxauser userid] [-dbrxapwd password]
[-setjdbcurl jdbcurl] [-unsetjdbcurl] [-enableMultiTenancy]
[-mtadminuser userid] [-mtadminpwd password] [-mtdbuser userid]
[-mtdbpwd password] [-inputfile path to input properties file]
used.
These properties that must be added manually to the install.properties file.
The -enableMultiTenancy parameter must be used with the -validateForNewDeploy
parameter.
action deployDatabaseConfiguration
The deployDatabaseConfiguration action is used to validate command-line
configuration program input and define configuration property values for a new
database for the currently deployed product. This action can be run after a
successful deployConfiguration action.
-action deployDatabaseConfiguration [-buildAndDeployEAR] [-createResourcesIfMissing]
[-dbserverhost hostname] [-dbserverport port number]
[-dbname database name] [-dbuser userid]
[-dbpwd password] [-dbrxauser userid] [-dbrxapwd password]
[-setjdbcurl jdbcurl] [-unsetjdbcurl] [-enableMultiTenancy]
[-mtadminuser userid] [-mtadminpwd password] [-mtdbuser userid]
[-mtdbpwd password] [-deployDemoData]
[-inputfile path to input properties file] [-enableRestrictivePasswordPolicy]
The following properties are required if the -createResourcesIfMissing parameter
is used.

action removeDatabaseConfiguration
The removeDatabaseConfiguration action is used to remove configuration settings
from a previously configured database.
-action removeDatabaseConfiguration [-removeInstance] [-dbrxauser userid]
[-dbrxapwd password] [-dbuser userid]
[-dbpwd password] [-deleteInstanceUsersAndGroups]
action enableDB2TextSearch
The enableDB2TextSearch action is used to enable the full text search feature for a
DB2 database.
-action enableDB2TextSearch [-db2textsearchport port number]
action updateJ2eeConfiguration
The updateJ2eeConfiguration action is used to update existing application server
-action updateJ2eeConfiguration [-force] [-buildAndDeployEAR]
[-j2eeserverhost hostname] [-j2eeserverport port number]
[-wasuser userid] [-waspwd password]
[-applicationServerNode nodeName] [-applicationServerName appServerName]
action validateJ2eeConfiguration
The validateJ2eeConfiguration action is used to validate application server
configuration values specified as input for the reconfiguration command-line
interface tool.
-action validateJ2eeConfiguration [-validateForNewDeploy] [-j2eeserverhost hostname]
[-j2eeserverport port number] [-wasuser userid]
[-waspwd password] [-applicationServerNode nodeName]
[-applicationServerName appServerName] [-inputfile path to input properties file]
The following properties are required if the –validateForNewDeploy parameter is
used and the WAS.SibPersistMessages property is set to true.
action validateAndUpdateJ2eeConfiguration
The validateAndUpdateJ2eeConfiguration action is used to both validate
reconfiguration command-line interface tool input and then update existing
application server configuration property values.
-action validateAndUpdateJ2eeConfiguration [-force] [-validateForNewDeploy]
[-buildAndDeployEAR] [-j2eeserverhost hostname]
[-applicationServerName appServerName]
The following properties are required if the –validateForNewDeploy parameter is

These properties must be added manually to the install.properties file.
action deployJ2eeConfiguration
The deployJ2eeConfiguration action is used to validate command line
configuration program input and define configuration property values for a new
application server for the currently deployed product. This action can be run after
a successful deployConfiguration action.
-action deployJ2eeConfiguration [-bypassJ2eeValidation] [-buildAndDeployEAR]
[-createResourcesIfMissing] [-j2eeserverhost hostname]
[–enableSkin Classic|tivoli09|tivoli13] [-enableEnhancedNavigation]
action removeJ2EEConfiguration
The removeJ2EEConfiguration action is used to remove configuration settings from
a previously configured application server. Items removed include domain
manager and application server profiles, and JMS objects.
-action removeJ2EEConfiguration [-wasuser userid] [waspwd password]
[-wasrxauser userid] [-wasrxapwd password]
[-removeCreatedArtifacts] [-deleteWasProfiles]
action deployConfiguration
Use the deployConfiguration action to configure the initial installation. This action
is used for new Maximo Asset Management installation scenarios only. This action
can configure multiple middleware products after they are installed. The
deployConfiguration action requires the inputfile parameter and an input
properties file populated with the configuration values you want to use.
-action deployConfiguration [-inputfile path to input properties file]
[-dbvendor Oracle|DB2|SQLServer] [-j2eevendor WebSphere|WebLogic]
[-bypassJ2eeValidation][-automatedbconfig] [-automatej2eeconfig]
[-usermanagement j2ee|mixed] [-buildears] [-deploymaximoear] [-deployhelpear]
[-enableappsecurity] [-deployDemoData] [-enableMultiTenancy] [-db2_english_only]
[-enableRestrictivePasswordPolicy]
action removeConfiguration
The removeConfiguration action is used to removes database and application
configuration that is performed by the configuration tool. This action is equivalent
to running the removeJ2EEConfiguration and removeDatabaseConfiguration actions
together
-action removeConfiguration -dbuser userid
-dbpwd password -wasuser userid
-waspwd password [-wasrxauser userid]

[-wasrxapwd password] [-dbrxauser userid]
[-dbrxapwd password] [-removeInstance] [-deleteInstanceUsersAndGroups]
[-removeCreatedArtifacts] [-deleteWasProfiles]
action reapplyAppServerTuning
The action is used to reapply application server tuning.
-action reapplyAppServerTuning [-wasuser userid]
action enableAppSecurity
The enableAppSecurity action is used to enable application security for the
application. This action sets the mxe.useAppServerSecurity property to a value of
1, and updates the mxe.ldapUserManagement property according to the setting of the
–usermanagement parameter. This value is written to the database when updated.
The maximouiweb, maxrestweb, meaweb, and mboweb web.xml files are updated during
this action.
-action enableAppSecurity -usermanagement {j2ee,mixed}
[-buildAndDeployEAR] [-validateUsers] [-force]
action disableAppSecurity
The disableAppSecurity action is used to disable application security for the
application. This action sets the mxe.useAppServerSecurity property to a value of
0. This value is written to the database when updated. Using this action reverts the
security implementation to Maximo security for users and groups. The
maximouiweb, maxrestweb, meaweb, and mboweb web.xml files are updated during this
action.
-action disableAppSecurity [-buildAndDeployEar] [-force]
action updateApplication
The updateApplication action is used to update the application by updating the
database and redeploying application EAR files.
-action updateApplication [-updatedb] [-deploymaximoear] [-deployhelpear]
[-wasuser userid] [-waspwd password]
[-enableRestrictivePasswordPolicy]
action addLanguages
Use the addLanguages action to configure additional languages for a deployment.
-action addLanguages [-additionalLangs locale1,locale2,locale3]
[-buildAndDeployEAR] [-allowUpdateDB | -bypassUpdateDB] [-stopAppServer]
The application server must be stopped when you add languages. If you do not
use the stopAppServer parameter with the addLanguages action, you must stop the
application server manually before you use the addLanguages action.
The following locale values are supported.
Table 11. Locales supported by the configuration program
Language Locale
Arabic ar
Brazilian Portuguese pt_BR

Table 11. Locales supported by the configuration program (continued)
Language Locale
Croatian hr
Czech cs
Danish da
Dutch nl
Finnish fi
French fr
German de
Hebrew he
Hungarian hu
Italian it
Japanese ja
Korean ko
Norwegian no
Polish pl
Russian ru
Simplified Chinese zh_CN
Slovak sk
Slovenian sl
Spanish es
Swedish sv
Traditional Chinese zh_TW
Turkish tr
action configureProducts
The configureProducts action is used to configure more products that are installed
after an initial installation and configuration. This action verifies a full installation
and configuration of an existing product was completed successfully before it
continues. This action can configure multiple products after they are installed. This
action can also be used in an upgrade scenario.
-action configureProducts [-updatedb] [-buildears] [-deploymaximoear]
[-deployhelpear] [-wasuser userid] [-waspwd password]
action deployMiddlewareConfiguration
The deployMiddlewareConfiguration action is used to configures middleware after
it is installed.
-action deployMiddlewareConfiguration [-inputfile path to input properties file]
The following properties can be included in the input properties file used with the
deployMiddlewareConfiguration action.
Table 12. Properties that can be used in the deployMiddlewareConfiguration action input file
Category Property
HTTP Server properties IHS.HTTPPort

Table 12. Properties that can be used in the deployMiddlewareConfiguration action input
file (continued)
Category Property
IHS.InstallLocation
IHS.WebserverName
LDAP server properties LDAP.AdminDN
LDAP.AdminPassword
LDAP.BaseEntry
LDAP.GroupSuffix
LDAP.OrgContainerSuffix
LDAP.ServerHostName
LDAP.ServerPort
LDAP.UserSuffix
LDAP.Vendor
General middleware configuration properties MW.Operation
WebSphere properties PLG.InstallLocation
WAS.AdminPassword
WAS.AdminUserName
WAS.ApplicationServerName
WAS.CellName
WAS.DeploymentManagerNodeName
WAS.DeploymentManagerProfileName
WAS.InstallLocation
WAS.LDAPAutomatedConfig
WAS.ND.AutomateConfig
WAS.NodeName
WAS.ServerProfileName
WAS.SOAPConnectorPort
WCT.InstallLocation
Configuration program properties
Maximo Asset Management properties can be modified with the command line
configuration program by using an input.properties file. When you set a property
value to a Windows path, you must use two consecutive backslashes, for example,
C:IBMWebSphereAppServer. When you set property values to a Linux or
UNIX path, use single forward slashes. For example, /opt/IBM/db2/V10.5.
Table 13. Maximo Asset Management properties
Category Property Definition
Shared database
properties
mxe.db.schemaowner Owner of the database schema.
For example, maximo.
This value is written to the database
when updated.

Table 13. Maximo Asset Management properties (continued)
mxe.db.user User ID that accesses the database.
mxe.db.password Password for the user ID that accesses
the database.
Database.RemoteAccessUserName Database server system user ID that is
used for configure the database
remotely.
This property is only required if the
createResourcesIfMissing,
validatefornewdeploy, or
automatedbconfig parameters are
specified.
Database.RemoteAccessPassword Password for user ID named in
Database.RemoteAccessUserName.
specified.
DB2 Properties Database.DB2.ServerHostName Fully qualified host name of the DB2
server.
For example, mymachine.mydomain.com.
when updated.
Database.DB2.ServerPort Database server port.
For example, 50005.
when updated.
Database.DB2.InstanceName Name of the database instance.
For example, ctginst1.
when updated.
specified.
Database.DB2.InstanceUserPassword Password for the database instance
owner
specified.

Database.DB2.InstanceAdminGroup Group for the instance administrator.
For example, ctgiadm1.
specified.
Database.DB2.DatabaseName Name of the database.
For example, maxdb76.
when updated.
Database.DB2.InstallLocation Install location of the database.
For example, /opt/IBM/db2/V10.5.
specified.
Database.DB2.LogFileSize Set the size for transaction logs.
For example, 8192.
specified.
Database.DB2.AppCtlHeapSize Application control heap size.
For example, 1024.
specified.
Database.DB2.ApplHeapSize Application heap size.
For example, 1024.
specified.

Database.DB2.LockListSize Size that is allocated to the lock list.
For example, AUTOMATIC.
specified.
Database.DB2.LogSecond Number of secondary log files allowed.
For example, 100.
specified.
Database.DB2.ServiceUser User ID used to autostart.
specified.
This property is only required if DB2 is
installed on a Windows system.
Database.DB2.ServicePassword Password for
Database.DB2.ServiceUser.
specified.
installed on a Windows system.
Database.DB2.ExtentSize Number of pages per extent (group of
pages).
For example, 32.
specified.

Database.DB2.FencedUser Fenced user ID for DB2 on Linux or
UNIX systems.
For example, db2fenc1.
specified.
Database.DB2.FencedUserPassword Password for the fenced user ID for
DB2 on Linux or UNIX systems.
specified.
Database.DB2.FencedGroupName Default group for database fenced user.
For example, ctgfgrp1.
specified.
installed on a Linux or UNIX system.
Database.DB2.AuthType Method DB2 uses to authenticate users.
For example, server.
specified.
Database.DB2.DataTablespaceName DB2 table space name for the product
database.
For example, maxdata.
Database.DB2.BufferPoolName DB2 buffer pool name.
For example, MAXBUFPOOL.
specified.

Database.DB2.BufferPoolSize Size of the buffer pool.
For example, 4096.
specified.
Database.DB2.DataTablespaceLocation Location of DB2 database table space
data files.
For example, CTGDAT.
specified.
Database.DB2.DataTablespaceSize Table space size, which is measured in
Mb.
For example, 5000.
specified.
Database.DB2.TempTablespaceName Temporary table space name.
For example, maxtemp.
specified.
Database.DB2.TempTablespaceLocation Location of temporary table space.
For example, CTGTMP.
specified.
Database.DB2.TempTablespaceSize Temporary table space size, which is
measured in Mb.
For example, 1000.
specified.

Database.DB2.IndexTablespaceName Index table space name.
Database.DB2.IndexTablespaceLocation Location of index table space.
For example, CTGDAT.
specified.
Database.DB2.IndexTablespaceSize Index table space size, which is
measured in Mb.
For example, 5000.
specified.
Database.DB2.InstanceAdminUserName Administrative user or the database
instance.
For example, db2admin.
specified.
For Unix and Linux platforms, this
value must be the same as the instance
owner.
Database.DB2.InstanceAdminPassword Password for the user ID specified for
Database.DB2.InstanceAdminUserName.
specified.createResourcesIfMissing
Oracle Database.Oracle.SchemaPassword Password for the schema owner.
Database.Oracle.InstanceName Oracle instance name.
when updated.

Database.Oracle.SoftwareOwner Owner of the software installation.
For example, oracle.
specified.
Database.Oracle.SoftwareOwnerPassword Password for the user ID listed in
Database.Oracle.SoftwareOwner.
specified.
Database.Oracle.InstallLocation Oracle installation location. For
example, /opt/app/oracle/product/
10.2.0/db_1.
specified.
Database.Oracle.DataTablespaceName Oracle table space name for the
product database.
Database.Oracle.InstanceLocation Oracle instance location.
For example, /opt/app/oracle/
product/10.2.0/db_1.
specified.
Database.Oracle.DataTablespaceSize Table space size, which is measured in
Mb.
For example, 5000.
specified.

Database.Oracle.TempTablespaceName Temporary table space name.
For example, maxtemp.
specified.
Database.Oracle.TempTablespaceSize Temporary table space size, which is
measured in Mb.
For example, 1000.
specified.
Database.Oracle.IndexTablespaceName Index table space name.
Database.Oracle.IndexTablespaceSize Index table space size, which is
measured in Mb.
For example, 1000.
specified.
Database.Oracle.ServerHostName Fully qualified host name of the Oracle
server.
Database.Oracle.ServerPort Port number that is used by Oracle.
For example, 1521.
when updated.
Database.DBAUserName Oracle DBA user name.
For example, sys.
specified.
Database.DBAPassword Password for user ID listed for
Database.DBAUserName.
specified.

Microsoft SQL Server Database.SQL.DatabaseName Name of the database.
For example, maxdb76.
when updated.
Database.SQL.DataFileName A way to specify the name of the data
file used for the database.
For example, maxdb76_dat.
specified.
Database.SQL.DataFileMaxSize Maximum size for data file for the
database.
Database.SQL.DataFileSize Initial size for data file for the database
in kb.
For example, 5000.
specified.
Database.SQL.LogFileName A way to specify the name for the
database transaction log file.
For example, maxdb76_log.
specified.
Database.SQL.LogFileSize Microsoft SQL Server transaction log
file size.
specified.
Database.SQL.DataFilegroupName Database logical name file group.
For example, PRIMARY.
specified.

Database.SQL.ServerHostName Host name of the database server.
For example, myhost.mydomain.com.
Database.SQL.ServerPort Database server port.
For example, 1433.
when updated.
Database.SQL.InstanceAdminUserName Administrative user for the Microsoft
SQL Server instance. Used during
installation for creating and modifying
the database and database user.
For example, sa.
specified.
Database.SQL.InstanceAdminPassword Administrative user password.
specified.
WebSphere Application
Server Network
Deployment
WAS.InstallLocation Installation location for WebSphere
Application Server Network
Deployment.
For example, C:IBMWebSphere
AppServer.
This property is required if the
WAS.SibPersistMessages property is set
to true.
This property is required in the
properties file that is specified in one
of the following properties.
v WAS.MIFSIBPropertiesFile
v WAS.CronSIBPropertiesFile
v WAS.UISIBPropertiesFile
WAS.DeploymentManagerHostName Host name of the WebSphere
Application Server Network
Deployment deployment manager.
when updated.

WAS.DeploymentManagerProfileName WebSphere Application Server
Network Deployment profile name.
For example, ctgDmgr01.
to true.
WAS.DeploymentManagerProfileRoot Location of the WebSphere Application
Server Network Deployment profile.
For example, C:
IBMWebSphereAppServer
profilesctgDmgr01
to true.
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.
when updated.
WAS.CellName WebSphere Application Server
Network Deployment cell name.
For example, ctgCell01.
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 Integrated Solutions
Console web archive files and fetching
the keystore.
to true.
WAS.RemoteAccessPassword WebSphere Application Server
Network Deployment deployment
manager system user password.
to true.
WAS.SOAPConnectorPort SOAP port for WebSphere Application
Server Network Deployment
deployment manager.
For example, 8879.
WAS.VirtualHost Name of the WebSphere Application
Server Network Deployment virtual
host.
For example, maximo_host.
WAS.WebServerHostName Host name where the HTTP server is
located.
WAS.SibName Name of the service integration bus.
For example, intjmsbus.

WAS.SibHiMsg Service integration bus high message
count.
For example, 500000.
automatej2eeconfig parameters are
specified.
WAS.WebServerName Name of the WebSphere Application
Server Network Deployment web
server. Used to manage HTTP server
from within WebSphere Application
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.
automatej2eeconfig parameters are
specified.

WAS.SibDSName Service integration bus data source
name that is created to access the
service integration bus persistence
store.
For example, intjmsds.
to true.
WAS.SibDBName Name of the service integration bus
messages database.
WAS.SibDBInstance Instance name of the service
integration bus database.
to true.
WAS.SibDBInstancePassword IBM DB2 instance users password for
the SIB IBM DB2 data store.
to true.

WAS.SibDBServerName Server name of the system that is
hosting the service integration bus
message database.
to true.
WAS.SibDBServerPort Database server port for the database
that contains the service integration
bus messages.
For example, 50005.
to true.
WAS.SibDBUserName User ID used to access the persistence
data store database for service
integration bus messages.
to true.

WAS.SibDBUserPass Password for user ID named in
WAS.SibDBUserName.
to true.
WAS.SibDBInstallDir Where the service integration bus
database is installed.
For example, c:program
filesibmsqllib.
to true.
WAS.SibDbFencedUser Fenced user ID for the service
integration bus database. This property
is only used for databases that are
hosted on Linux and UNIX systems.
For example, db2fenc1.
to true.
database is hosted on a Linux or UNIX
system.

WAS.SibDbFencedPassword Password for the fenced user ID for the
service integration bus database.
to true.
database is hosted on a Linux or UNIX
system.
WAS.SibDbInstanceAdminUser Instance owner for the service
integration bus database.
to true.
database is hosted on a Windows
system.
WAS.SibDbInstanceAdminPassword Password for the instance owner of the
service integration bus database.
to true.
database is hosted on a Windows
system.

WAS.SibDbRemoteAccessUser Database server system user that is
used to configure the service
integration bus remotely.
to true.
WAS.SibDbRemoteAccessPassword Password for user ID named in
WAS.SibDbRemoteAccessUser.
to true.
WAS.VmmGroupRDN Relative Distinguished Name of the
location of virtual member manager
groups.
For example,
ou=groups,ou=SWG,o=IBM,c=US.
WAS.VmmUserRDN Relative Distinguished Name of the
location of virtual member manager
users.
For example,
ou=users,ou=SWG,o=IBM,c=US.
WAS.UseClustersForDeploy Deploy the application EAR to a
cluster.
For example, true.
WAS.UIClusterName Name of the cluster that manages UI
tasks.
Set a value for this parameter if
WAS.UseClustersForDeploy is set to
true.

WAS.WAS.UIEnableJMS Enable or disable JMS for Maximo
Enterprise Adapter for the UI cluster.
For example, true.
true.
WAS.UISIBPropertiesFile File that contains SIB persistence
properties if you are persisting
messages in the UI clusters bus.
For example, c:sibdb_ui.properties.
true.
WAS.CronClusterName Name of the cluster that manages cron
tasks.
For example, maximocron.
true.
WAS.CronEnableJMS Enable JMS for Maximo Enterprise
Adapter for the cron task cluster.
For example, true.
true.
WAS.CronSIBPropertiesFile File that contains SIB persistence
messages in the cron clusters bus.
For example, c:sibdb_cr.properties.
true.
WAS.ReportingClusterName Name of the cluster that manages
reporting tasks.
For example, maximorpt.
true.

WAS.MIFClusterName Name of the cluster that manages
Maximo Integration Framework tasks.
For example, maximomea.
true.
WAS.MIFEnableJMS Enable JMS for Maximo Enterprise
Adapter for the Maximo Integration
Framework task cluster.
For example, true.
true.
WAS.MIFSIBPropertiesFile File that contains SIB persistence
messages in the Maximo Integration
Framework clusters bus.
For example, c:
sibdb_mif.properties.
true.
Multi-tenancy mt.sysprovider.tenantcode Tenant code identifier for the
multi-tenancy system provider.
For example, MTM.
This property is required to enable
multi-tenancy.
mt.sysprovider.desc Description of the multi-tenancy
manager.
mt.configmanager.adminuserid User ID of the multi-tenancy
configuration manager.
For example, maxadmin.
multi-tenancy.
This value can be the same value used
for the mtadminuser user.
mt.configmanager.adminpassword Password for the User ID of the
multi-tenancy configuration manager.
multi-tenancy.
for the mtadminpwd value.

mt.configmanager.tenantcode Tenant code identifier for the
multi-tenancy configuration manager.
For example, GA.
This is property is required to enable
multi-tenancy.
mt.configmanager.desc Description of the multi-tenancy global
administrator.
mt.configmanager.dbuser User ID of the multi-tenancy
configuration manager used to connect
to the database.
For example, ADMIN.
multi-tenancy.
for the mtdbuser user.
mt.configmanager.dbpassword Password for the user ID of the
multi-tenancy configuration manager
that is used to connect to the database.
multi-tenancy.
for the mtdbpwd value.
mxe.mt.enabled Value that indicates whether
multi-tenancy is enabled.
For example, a value of 1 indicates that
multi-tenancy is enabled. A value of 0
indicates that multi-tenancy is not
enabled for the product.
mxe.mt.db.adminuser This value is the same as the value set
for the mtdbuser parameter.
This property is set in the
maximo.properties file during the
maxinst operation.
mxe.mt.demo.extratenants Number of sample tenants to create
when you enable multi-tenancy.
For example, 10.
This property is set in the
maximo.properties file during the
maxinst operation.

Chapter 16. Configuring your product with performance
analysis data
Configure Maximo Asset Management with optimized settings.
About this task
The IBM Performance Analysis Suite checks Maximo Asset Management for
compliance with best practices and optimized performance settings. The IBM
Performance Analysis Suite collects configuration data about the database, host
operating system settings, WebSphere Application Server Network Deployment
and IBM HTTP Server, applies a set of performance metrics to the data, and then
generates a report.
The system tuner utility takes IBM Performance Analysis Suite data and
automatically configures your environment and middleware.
Procedure
1. Click the link on the Maximo Asset Management launchpad to download the
IBM Performance Analysis Suite from the IBM developerWorks community and
install it on the Maximo Asset Management administrative workstation.
2. Analyze your Maximo Asset Management deployment with the IBM
Performance Analysis Suite and export the IBM Performance Analysis Suite
workspace. Refer to the IBM Performance Analysis Suite developerWorks
community for information about using IBM Performance Analysis Suite.
3. Log on to the Maximo Asset Management administrative workstation, open a
command prompt, and change to the install_homescripts directory.
4. Run the tuneSystem command. All parameters listed are required.
tuneSystem -d install_dir -e env_name -w workspace_zip_file
-r [generate|update] -c [warning|critical] -o output_dir -p plugin_name
--debug
Use this parameter to turn on debug logging.
-d install_dir
Use this parameter to specify where the IBM Performance Analysis Suite is
installed on the system.
-e env_name
Use this parameter to enter the name of the environment you defined when
you used the IBM Performance Analysis Suite to collect data about your
environment.
-w workspace_zip_file
Use this parameter to enter the name of the zipped file containing the data
that was collected when you used the IBM Performance Analysis Suite.
-r [generate|update]
Use this parameter to generate scripts to update Maximo Asset
If you use generate, the scripts are generated in the output directory you
specify. You must manually run these scripts to re-configure Maximo Asset
Management. A file with an extension of .sql is generated to update the
Maximo Asset Management database. A file with an extension of .py is

generated to update the Maximo Asset Management application server. A
file with an extension of .sh or .bat is generated to update the Maximo
Asset Management administrative workstation.
If you use update, the scripts are generated and then run on the system to
update Maximo Asset Management configuration.
-c [warning|critical]
Use this parameter to specify which conditions identified by the IBM
Performance Analysis Suite to update in Maximo Asset Management. If you
use critical, configuration values that were categorized as critical by the
IBM Performance Analysis Suite are updated by the Maximo Asset
Management system tuner utility. If you use warning, configuration values
that were categorized as either critical or warnings by the IBM Performance
Analysis Suite are updated by the Maximo Asset Management system tuner
utility.
-o output_dir
Use this parameter to specify where to output the scripts generated by the
Maximo Asset Management system tuner utility.
-p plugin_name
Use this parameter to enter the name of the plugin you specified when you
used the IBM Performance Analysis Suite.
-h Use this parameter to display help for the tuneSystem command.
tuneSystem -d install_dir -e env_name -w workspace_zip_file
-r [generate|update] -c [warning|critical] -o output_dir -p plugin_name
What to do next
You should use the IBM Performance Analysis Suite and the tuneSystem command
to perform Maximo Asset Management configuration updates as part of your
regularly scheduled maintenance program.
https://www.ibm.com/developerworks/community/blogs/28cb6d68-ab67-
4203-96f9-5538e654a5ff/entry/june_16_2013_11_07_pm
https://www.ibm.com/developerworks/community/wikis/home?lang=en-
us#!/wiki/W16f314e69702_46b3_9252_04023c060b9a

Chapter 17. Backup and restoration
Like all important business data, it is a good idea to establish a process and
schedule for backing up Maximo Asset Management 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 Maximo Asset Management administrative
workstation.
The default installation directory on the Maximo Asset Management administrative
workstation is C:ibm. This directory contains the critical files for your Maximo
Asset Management 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 Maximo Asset Management 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 Maximo Asset Management middleware
applications and Maximo Asset Management administrative workstation on a
regular basis.
About this task
The default installation directory on the administrative workstation is ibm. This
directory contains the critical files for your Maximo Asset Management
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 Maximo Asset Management information, complete the following
steps:
Procedure
1. Back up the Maximo Asset Management 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
IBMSMP. Ensure that all file permissions are preserved.

Restoring the administrative workstation
This section details how to restore previously backed up Maximo Asset
Management administrative workstation information. This information can be used
to return an existing Maximo Asset Management 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 Maximo Asset Management 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 Maximo Asset Management 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 Maximo Asset
Management installation directory on the existing administrative system is
IBMSMP, you cannot copy those files to a NewAdminWSIBMSMP directory on
the target administrative workstation.

Chapter 18. Uninstalling the product
Uninstalling Maximo Asset Management version 7.6 includes removing
configuration values from Maximo Asset Management and associated middleware,
and then uninstalling Maximo Asset Management.
Maximo Asset Management uninstallation is a comprehensive procedure and does
not support partial removal of individual components or process managers,
including process managers that are deployed by other products. Process managers
of previously deployed products are also removed when you uninstall Maximo
Asset Management.
Maximo Asset Management can only be uninstalled using the Maximo Asset
Management installation and configuration programs as directed. Do not use other
methods to attempt to uninstall Maximo Asset Management, such as using the
Add/Remove Programs panel.
After the Maximo Asset Management uninstallation process is complete, you can
reinstall Maximo Asset Management by using the Maximo Asset Management
installation and configuration programs.
Remove Maximo Asset Management configuration
The first step to uninstall Maximo Asset Management is to remove configuration
values using the Maximo Asset Management configuration program.
About this task
If you choose the option to delete the database instance, table spaces, the database,
and the database instance are removed. The instance user, database users, and
system users that were created with the configuration program can also be
removed. For WebSphere Application Server Network Deployment, specify
credentials for the WebSphere administrative user to uninstall the Maximo Asset
Management application. If you choose the option to delete WebSphere artifacts,
the application server and JMS queue information are removed.
Procedure
1. Log on to the WebSphere Application Server Network Deployment server with
the WebSphere Application Server admin console and stop all of the Maximo
Asset Management applications.
pane, click Configure Product, specify Maximo Asset Management installation
location, and then click Launch the Tivoli’s Process Automation Suite
Remove Product Configuration Information.
4. In the Remove Product Configuration Information panel, specify credentials to
access the database and WebSphere Application Server Network Deployment
servers you previously configured for Maximo Asset Management.
5. Click Finish, and then OK to confirm.

Removing WebSphere Application Server Network Deployment
configuration
Removing WebSphere Application Server Network Deployment configuration with
the Maximo Asset Management configuration program deletes all configuration
data.
Procedure
pane, click Configure Product, specify Maximo Asset Management installation
location, and then click Launch the Tivoli’s Process Automation Suite
Unconfigure WebSphere Application Server.
3. In the Unconfigure WebSphere panel, specify credentials for the WebSphere
administrative user to remove WebSphere Application Server Network
Deployment profile information, and then click Next.
4. In the Unconfigure Middleware panel, select the Unconfigure WebSphere
Application Server Network Deployment option, click Finish, and then OK to
confirm.
Uninstalling Maximo Asset Management and middleware
Use the Installation Manager software to uninstall Maximo Asset Management and
any middleware that was installed with the Maximo Asset Management
installation program.
About this task
After you use the Maximo Asset Management configuration program to
unconfigure Maximo Asset Management and associated middleware, use the
Installation Manager software to uninstall previously installed components. You
must run Installation Manager locally on the system that hosts the component you
want to uninstall.
Procedure
1. Stop all DB2 and WebSphere Application Server Network Deployment
processes on the system.
2. Open a command prompt and start Installation Manager.
Windows UNIX
C:Program FilesIBMInstallation
ManagereclipseIBMIM.exe
IBMIM.sh
3. From the IBM Installation Manager interface, select Uninstall.
4. Select the packages that you want to remove and then click Next.
5. Review the package summary information and click Uninstall to remove the
selected packages.

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
websites. The materials at those websites are not part of the materials for this IBM
product and use of those websites is at your own risk.

IBM may use or distribute any of the information you 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
2Z4A/101
11400 Burnet Road
Austin, TX 78758 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 document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to 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,
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. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at “Copyright and
trademark information” at www.ibm.com/legal/copytrade.shtml.

Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.
Linux is a registered trademark of Linus Torvalds in the United States, other
countries, or both.
Microsoft, Windows, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Notices 165

Index
A
action addLanguages 132
action configureProducts 133
action deployConfiguration 131
action deployDatabaseConfiguration 129
action deployJ2eeConfiguration 131
action
deployMiddlewareConfiguration 133
action disableAppSecurity 132
action enableAppSecurity 132
action enableDB2TextSearch 130
action reapplyAppServerTuning 132
action removeConfiguration 131
action
removeDatabaseConfiguration 130
action removeJ2EEConfiguration 131
action updateApplication 132
action updateDatabaseConfiguration 128
action updateJ2eeConfiguration 130
action validate And Update Database
Configuration 129
action validate And Update J2ee
Configuration 130
action
validateDatabaseConfiguration 128
action validateJ2eeConfiguration 130
administrative workstation
backing up 159
restoring 160
AIX
asynchronous I/O, enabling 8
fonts 7
large page size support 7
tar command 7
asynchronous I/O
enabling on AIX 8
B
backup 159
C
command line configuration program
input properties files 120
parameters 121
Command line configuration program
actions 128
configuration 104
configuration actions
addLanguages 132
configureProducts 133
deployConfiguration 131
deployDatabaseConfiguration 129
deployJ2eeConfiguration 131
deployMiddlewareConfiguration 133
disableAppSecurity 132
enableAppSecurity 132
enableDB2TextSearch 130
reapplyAppServerTuning 132
configuration actions (continued)
removeConfiguration 131
removeDatabaseConfiguration 130
removeJ2EEConfiguration 131
updateApplication 132
updateDatabaseConfiguration 128
updateJ2eeConfiguration 130
validate And Update Database
Configuration 129
validate And Update J2ee
Configuration 130
validateDatabaseConfiguration 128
validateJ2eeConfiguration 130
configure Maximo Asset Management
silently 89
configure middleware silently 89
configuring
database server 35
silent 87
configuring Maximo Asset Management
command line configuration
program 119
validate configuration parameters
from the command line 120
continuous inbound (CQIN) JMS queue
creating 59
CQINERR JMS queue
creating 62
D
data source
manually creating for the persistent
store 45
database server 35
DB2
manual configuration, v10.5 35
DB2 v10.5
installing 20, 73
directory server
manually configuring 37
E
EAR files
building manually 115
maintaining 115
error queue 61
F
fonts
AIX 7
H
help 103
help information
installing in multiple languages 103
HTTP server 12
HTTPOnly
configuring 99
I
IBM Tivoli Directory Server
IBM WebSphere Application Server
Network Deployment
HTTPOnly 99
industry solutions 111
installing from command-line 111
installing silently 112
installing with launchpad 111
install
automatic middleware
configuration 19
clustered environment 71
install silently 84
installation
automatically configuring existing
middleware 27
deploying using manual middleware
configuration 35
deploying with manually configured
middleware 33
preparing 1
program logs 101
Installation
post-installation tasks 104
Installation Manager
installing silently 83
logs 101
installing
silent 81
J
J2EE server
JMS activation specification
creating for the continuous inbound
queue (CQIN) 60
creating for the inbound error queue
(CQINERR) 63
JMS connection factory
creating 58
JMS queues
manually configure 54
JRE
configuring in Linux 9
L
launchpad
starting 13
libraries
Linux 9

libraries (continued)
required libraries 9
Linux
JRE, configuring 9
shared memory, setting 10
swap size, setting 10
ulimit, setting 9
M
configuring in a cluster
environment 79
configuring with the Maximo Asset
Management configuration
program 25, 30, 68
installing version 7.6 23, 29, 67, 78
remove configuration 161
uninstalling 162
Media
Installation 1
middleware 81, 87
remote configuration 10
remove configuration silently 90
middleware installation
before you begin 1
middlware configuration
silent sample response files 88
multi-language help information 103
N
node agent
creating as a Windows service 54
nstallation
before you begin 1
O
online help 103
P
page size support
AIX 7
password
updating in response files 83
password policies 13
performance analysis data
importing 157
port availability
check 6
post installation 103
prerequisite 81, 87
product
remove configuration silently 90
product configuration program
overview 15
product installation
before you begin 1
product installation program
overview 14
profiles
creating in WebSphere 42
properties
Maximo Asset Management 134
R
remove configuration
WebSphere Application Server
Network Deployment 162
restoration 159
S
sequential inbound (SQIN) JMS queue
creating 59
sequential outbound (SQOUT) JMS queue
creating 60
service integration bus
adding a server 55
service integration bus destination
creating for the continuous inbound
(CQINBD) queue 56
creating for the inbound error queue
(CQINERRBD) queue 61
creating for the sequential inbound
(SQINBD) queue 57
creating for the sequential outbound
(SQOUTBD) queue 57
shared memory
setting in Linux 10
silent install 84, 89
sample response files 82
silent installation
uninstallation 85
silent response file
installation 81
configuration 88
middleware configuration 87
SQL Server
preparing 12
SSL
client authentication workaround 12
swap size
setting in Linux 10
T
tar command
AIX 7
U
ulimit
setting in Linux 9
uninstall
middleware 162
product 161
users
groups
synchronizing 107
synchronizing 107
V
verifying prerequisites
command-line 2
verifying the installation
manually 97
programmatically 93
VMM
manual configuration 63
W
WebSphere
manually creating profiles 42
Deployment
configuration tasks 47
install Maximo Asset Management
applications 116
manually uninstalling 116
remove configuration 162
Deployment servers
configuring application server cluster
profiles 75
configuring cluster members on
additional WebSphere nodes 76
preparing for Maximo Asset
Management configuration 23, 28,
75, 76
Deployment v8.5
installing 21, 74

Installation guide (web sphereapplication server,db2,tivoli directory

Installation guide (web sphereapplication server,db2,tivoli directory

More Related Content

What's hot (20)

Similar to Installation guide (web sphereapplication server,db2,tivoli directory (20)

Recently uploaded (20)

Installation guide (web sphereapplication server,db2,tivoli directory