Cloning Am Am 75 Env

Cloning a Maximo Asset Management 7.5environment

ii Cloning a Maximo Asset Management 7.5 environment

ContentsCloning a Maximo Asset Management7.5 environment . . . . . . . . . . . 1

iii

iv Cloning a Maximo Asset Management 7.5 environment

Cloning a Maximo Asset Management 7.5 environmentMaximo Asset Management 7.5 deployments can be copied into multipleenvironments. This allows you to duplicate environments for the purposes ofdevelopment, testing, and prototyping.

You can refine best practices for your product in development and testenvironments. You can then apply the best practices to the productionenvironment.

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

This scenario provides details on cloning a Maximo Asset Management 7.5environment based upon WebSphere Application Server, DB2, and Tivoli

Directory Server. For other supported middleware, such as Oracle and MicrosoftSQL Server, refer to the product documentation provided for migration information

Installing WebSphere Application Server, DB2, and TivoliDirectory Server in the target environment

The first step of establishing the target environment is installing WebSphereApplication Server, DB2, and optionally Tivoli Directory Server. New software canbe installed using the middleware installation program supplied with the 7.5version of your product. Alternatively, you can reuse existing servers that arealready established in your enterprise provided they are at supported softwareversion levels.

Install and configure WebSphere Application Server, DB2, and optionally TivoliDirectory Server, as described in the installation information for the 7.5 version ofyour product.

Cloning the source environment administrative workstation

To establish an administrative workstation in the target environment, first create abackup 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 aclone of the source environment administrative workstation in the targetenvironment.

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

1

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

This procedure references c:\ibm\smp as the installation home directory. If you didnot use the default installation path during installation, use the custom value inplace 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, andcreate a user named maximo. The newly created user must be a member of theDB2 administrator group.

4. Move the copy of the 7.5 installation directory to the target environmentadministrative workstation file system. Ensure that you maintain the samedrive letter and directory structure of the source environment installation. Forexample, if the 7.5 installation directory on the source environmentadministrative workstation is c:\ibm\smp, you cannot copy those files toc:\NewAdminWS\ibm\smp directory on the target environment administrativeworkstation. If you are reusing the source administrative workstation system tohost the target administrative workstation, the directories must be different. Forexample, c:\ibm\smp\TargetAdminWS

5. Log on to the target environment administrative workstation with the sameuser ID you used in step 1.

6. Update the deployment engine host name. This step is required if the targetenvironment administrative workstation is hosted on a different system fromthe source environment administrative workstation.c:\ibm\smp\ctg_de\acsi\setenvc:\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 beenabled on the source database to ensure that database log entries are notoverwritten.

For detailed information about enabling archive logging, see the IBM DB2Database 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:

Windowsset 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. Ifthe phrase (LOGRETAIN) = RECOVERY is included in the output, archive logging isalready configured for the database. If the phrase (LOGRETAIN) = OFF, isincluded 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 formaxdatabase 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 tothe target environment.

For detailed information about creating database backups, see the IBM DB2Database 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:



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 targetenvironment

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

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

For detailed information about creating database backups, see the IBM DB2Database 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:


Cloning a Maximo Asset Management 7.5 environment 3


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. Ifyou run this command on a Linux or UNIX system, you must precede theparentheses 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 beupdated in the install.properties and maximo.properties files of the targetenvironment administrative workstation, primarily to configure the deployment towork 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 youcan use the reconfiguration command line interface tool to update them. Propertiesspecified when using the reconfiguration command line interface tool, either asparameters, or in an input properties file, replace existing properties in themaximo.properties and install.properties files. Properties are encrypted uponsaving.

The reconfiguration command line interface tool can be downloaded from theIntegrated 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. TheMaximo_750x_ReconfigurationTool_for_AdminWorkstation.zip file includes thereconfiguration command line interface tool that can be used with v7.5Maximo-based products.

Uncompress the appropriate zipped file into the product installation directory.Within the newly created reconfig directory. The reconfiguration command lineinterface tool are launched on the administrative workstation:

WindowsreconfigurePae.bat command-line-parameters


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

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

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

As a precaution, create a backup of the maximo.properties andinstall.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.propertiesfiles.a. Create an input properties file to use with the reconfigpae command for

database resources. In addition to copying values from themaximo.properties and install.properties files from the sourceenvironment, you must define the following properties:v Database.DB2.InstanceAdminGroupv Database.DB2.InstanceAdminUserName (Windows only)v Database.DB2.InstanceAdminPassword (Windows only)v Database.DB2.FencedUserv Database.DB2.FencedUserPasswordv Database.DB2.FencedGroupNamev Database.DB2.InstanceUserPassword

b. Run the reconfigpae command with the updateDatabaseConfigurationaction 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 andupdate configuration properties in the maximo.properties andinstall.properties files.a. Create an input properties file to use with the reconfigpae command for

application server resources. Copy values from the maximo.properties andinstall.properties files from the source environment.

Cloning a Maximo Asset Management 7.5 environment 5

b. Run the reconfigpae command with the deployJ2eeConfiguration action tocreate 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 followingsteps:1. Build the maximo EAR file:

Windowsinstall_home\maximo\deployment\buildmaximoear.cmd

2. Build the maximo help system EAR file:

Windowsinstall_home\maximo\deployment\buildmxiehsear.cmd

Manually installing applications in WebSphere Application ServerNetwork Deployment

Manually install Maximo Asset Management the rebuilt applications to WebSphereApplication 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.


ContentsCloning a Maximo Asset Management 7.5 environment

Cloning Am Am 75 Env

Documents

Transcript of Cloning Am Am 75 Env