򔻐򗗠򙳰

Cloning a Maximo Asset Management 7.5

environment
ii Cloning a Maximo Asset Management 7.5 environment
Contents
Cloning a Maximo Asset Management
7.5 environment . . . . . . . . . . . 1

iii
iv Cloning a Maximo Asset Management 7.5 environment
Cloning a Maximo Asset Management 7.5 environment
Maximo Asset Management 7.5 deployments can be copied into multiple
environments. This allows you to duplicate environments for the purposes of
development, testing, and prototyping.

You can refine best practices for your product in development and test
environments. You can then apply the best practices to the production
environment.

For the purposes of cloning, the currently installed product is referred to as the
source environment. A parallel environment is created that is the same as the source
environment in structure. The parallel environment is referred to as the target
environment. The database is copied from the source environment and deployed in
the target environment.

This scenario provides details on cloning a Maximo Asset Management 7.5

environment based upon WebSphere® Application Server, DB2®, and Tivoli®
Directory Server. For other supported middleware, such as Oracle and Microsoft
SQL Server, refer to the product documentation provided for migration information

Installing WebSphere Application Server, DB2, and Tivoli

Directory Server in the target environment

The first step of establishing the target environment is installing WebSphere

Application Server, DB2, and optionally Tivoli Directory Server. New software can
be installed using the middleware installation program supplied with the 7.5
version of your product. Alternatively, you can reuse existing servers that are
already established in your enterprise provided they are at supported software
version levels.

Install and configure WebSphere Application Server, DB2, and optionally Tivoli
Directory Server, as described in the installation information for the 7.5 version of
your product.

Cloning the source environment administrative workstation

To establish an administrative workstation in the target environment, first create a

backup image of the 7.5 administrative workstation from the source environment.
The image is copied to a system in the target environment. This process creates a
clone of the source environment administrative workstation in the target
environment.

The target environment administrative workstation must have the same operating
system, major version, and be of the same hardware type as the source
environment administrative workstation. The user ID used to install the product on
the source environment administrative workstation must also exist on the target
environment administrative workstation. This user ID must have the same
permissions defined for it in both environments. If you prefer, you can also reuse
the source environment administrative workstation system to serve as the target
environment administrative workstation.

1
 This procedure is for an installation of version 7.5 of your product that was
installed in a local deployment engine environment.

This procedure references c:\ibm\smp as the installation home directory. If you did
not use the default installation path during installation, use the custom value in
place of c:\ibm\smp.
1. Log on to the source environment administrative workstation with the user ID
that was used to install the product.
2. Create a copy of the 7.5 installation directory. Ensure that all file permissions
are preserved. For default installations, this directory is C:\IBM\SMP.
3. If you are using DB2, log on to the target environment administrative
workstation using a user ID with the authority to create new system users, and
create a user named maximo. The newly created user must be a member of the
DB2 administrator group.
4. Move the copy of the 7.5 installation directory to the target environment
administrative workstation file system. Ensure that you maintain the same
drive letter and directory structure of the source environment installation. For
example, if the 7.5 installation directory on the source environment
administrative workstation is c:\ibm\smp, you cannot copy those files to
c:\NewAdminWS\ibm\smp directory on the target environment administrative
workstation. If you are reusing the source administrative workstation system to
host the target administrative workstation, the directories must be different. For
example, c:\ibm\smp\TargetAdminWS
5. Log on to the target environment administrative workstation with the same
user ID you used in step 1.
6. Update the deployment engine host name. This step is required if the target
environment administrative workstation is hosted on a different system from
the source environment administrative workstation.
c:\ibm\smp\ctg_de\acsi\setenv
c:\ibm\smp\ctg_de\acsi\bin\de_chghostname

Enabling archive logging in the source environment

Archive logging is a requirement of DB2 online backup operations and must be
enabled on the source database to ensure that database log entries are not
overwritten.

For detailed information about enabling archive logging, see the IBM® DB2
Database for Linux, UNIX, and Windows information center (https://
publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.doc/
welcome.html). Search for "Configuring database logging options.
1. Log on to the system that hosts the source environment database.
2. Set the DB2INSTANCE environment variable:
Windows
set DB2INSTANCE=CTGINST1
Linux and UNIX
/home/db2admin> export DB2INSTANCE=CTGINST1
3. Start the DB2 command line processor.
4. Check whether archive logging is already enabled on the source database with
the following command:
db2 get database configuration for maxdatabase

2 Cloning a Maximo Asset Management 7.5 environment

 Replace maxdatabase with the name of your database, for example, MAXDB75. If
the phrase (LOGRETAIN) = RECOVERY is included in the output, archive logging is
already configured for the database. If the phrase (LOGRETAIN) = OFF, is
included in the output, archive logging must be configured for the database.
5. Enable archive logging on the source database with the following command:
db2 update database configuration for
maxdatabase using LOGARCHMETH1 LOGRETAIN

Replace maxdatabase with the name of your database, for example, MAXDB71.

Backing up the source environment database

A backup of the source environment database must be created and then copied to
the target environment.

For detailed information about creating database backups, see the IBM DB2
Database for Linux, UNIX, and Windows information center (https://
publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.doc/
welcome.html), and search for BACKUP DATABASE.
1. Log on to the system that hosts the source environment database.
2. Set the DB2INSTANCE environment variable:
Windows
set DB2INSTANCE=CTGINST1
Linux and UNIX
/home/db2admin> export DB2INSTANCE=CTGINST1
3. Start the DB2 command line processor.
4. Create a backup of the source database with the following command:
db2 backup database maxdatabase ONLINE to backupdir INCLUDE LOGS;

Replace maxdatabase with the name of your database, for example, MAXDB75.
Replace backupdir with the full path to the destination of the backup image file.

Restoring the source environment database backup to the target

environment

After you install DB2 in the target environment, you can restore the backup image
that you created of the source environment database.

When you run the RESTORE DATABASE command with the backup image, the source
environment database is re-created on the target environment database. During the
restoration process, you also use the rollforward command which applies
transactions recorded in the database log files. This process includes transactions
that occurred after the database backup image has been restored.

For detailed information about creating database backups, see the IBM DB2
Database for Linux, UNIX, and Windows information center (https://
publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.doc/
welcome.html), and search for RESTORE DATABASE.
1. Log on to the system that hosts the target environment database.
2. Set the DB2INSTANCE environment variable:
Windows
set DB2INSTANCE=CTGINST1

Cloning a Maximo Asset Management 7.5 environment 3

 Linux and UNIX
/home/db2admin> export DB2INSTANCE=CTGINST1
3. Copy the MAXDB75 backup file to a directory on the system, for example, db2bak.
4. Change directory to db2bak, and start the DB2 command line processor.
5. Run the following command to restore the target environment database image.
db2 restore database maxdatabase from .

Replace maxdatabase with the name of your database, for example, MAXDB75.
6. Create a new temporary directory, for example, tmpdir, and extract the
database archive logs that are bundled with the backup image.
db2 restore database maxdatabase LOGS from . LOGTARGET tmpdir

Replace maxdatabase with the name of your database, for example, MAXDB75.
7. Apply all the transactions stored in the database archive log files to the restored
database.
db2 rollforward database maxdatabase to end of logs and complete overflow log path
(tmpdir)

Replace maxdatabase with the name of your database, for example, MAXDB75. If
you run this command on a Linux or UNIX system, you must precede the
parentheses with escape characters. For example,
db2 rollforward database maxdatabase to end of logs and complete overflow log path
\(/home/ctginst1/tmpdir\)

Updating properties in the target environment

Configuration properties copied over from the source environment must be

updated in the install.properties and maximo.properties files of the target
environment administrative workstation, primarily to configure the deployment to
work with the new middleware of the target environment. In addition,
middleware resources must be recreated on servers in the target environment.

You can update configuration values for the target environment manually, or you
can use the reconfiguration command line interface tool to update them. Properties
specified when using the reconfiguration 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 upon
saving.

The reconfiguration command line interface tool can be downloaded from the
Integrated Service Management Library located at https://www.ibm.com/
software/brandcatalog/ismlibrary/.

Once downloaded, uncompress the archive on the administrative workstation.

Inside the archive are two additional compressed files. The
Maximo_750x_ReconfigurationTool_for_AdminWorkstation.zip file includes the
reconfiguration command line interface tool that can be used with v7.5
Maximo-based products.

Uncompress the appropriate zipped file into the product installation directory.
Within the newly created reconfig directory. The reconfiguration command line
interface tool are launched on the administrative workstation:
Windows
reconfigurePae.bat command-line-parameters

4 Cloning a Maximo Asset Management 7.5 environment

There are sample input property files that can be used as input for the
reconfiguration command line interface tool. These files contain comments and
properties you can update with values used in the source environment
deployment, and then use as input for the reconfiguration command line interface
tool using the –input parameter. In addition, there property files contain properties
that can only be updated through the use of this input file. Most properties cannot
be used as parameters from the command line.

Four input sample files are found in the reconfig/samples directory of the
reconfiguration command line interface tool packages.
v DB2_Sample_input.properties
v Oracle_Sample_input.properties
v SQLServer_Sample_input.properties
v WebSphere_App_Server_Sample_input.properties

Each of these sample files contain properties associated with a specific database or
application server type. You must define configuration property values for a new
database and new application server to be used with the deployment in the target
environment.

As a precaution, create a backup of the maximo.properties and

install.properties files on the target environment administrative workstation.
1. Create database resources in the target environment database and update
configuration properties in the maximo.properties and install.properties
files.
a. Create an input properties file to use with the reconfigpae command for
database resources. In addition to copying values from the
maximo.properties and install.properties files from the source
environment, you must define the following properties:
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
b. Run the reconfigpae command with the updateDatabaseConfiguration
action to update database objects in the target environment database.
reconfigurePae.bat
-action updateDatabaseConfiguration
-dbserverhost fullyqualifiedDBhostname
-dbserverport port
-dbname name
-dbpwd password
-dbrxauser remoteuser
-dbrxapwd remotepassword
-inputfile fullyqualifiedpath
2. Create application resources in the target environment application server and
update configuration properties in the maximo.properties and
install.properties files.
a. Create an input properties file to use with the reconfigpae command for
application server resources. Copy values from the maximo.properties and
install.properties files from the source environment.

Cloning a Maximo Asset Management 7.5 environment 5

 b. Run the reconfigpae command with the deployJ2eeConfiguration action to
create database objects in the target environment database.
reconfigurePae.bat
-action deployJ2eeConfiguration
-createResourcesIfMissing
-j2eeserverhost fullyqualifiedtargetenvironmentDMgrhostname
-j2eeserverport port
-wasuser WebSphereuser
-waspwd WebSphereuserpassword
-applicationServerNode NodeName
-applicationServerName applicationserverhostname
-inputfile fullyqualifiedpath

Building EAR files

To manually rebuild Maximo Asset Management EAR files, complete the following
steps:
1. Build the maximo EAR file:
Windows
install_home\maximo\deployment\buildmaximoear.cmd
2. Build the maximo help system EAR file:
Windows
install_home\maximo\deployment\buildmxiehsear.cmd

Manually installing applications in WebSphere Application Server

Network Deployment

Manually install Maximo Asset Management the rebuilt applications to WebSphere

Application Server Network Deployment.
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.

6 Cloning a Maximo Asset Management 7.5 environment