IBM Tivoli Composite Application Manager for J2EE V6.1.0.0

Multi Platform Data Collector

Distributed

Interim Fix 0001 Post-Installation Steps for JBoss

January 18, 2007

Contents

1 Abstract.. 2

2 Change History.. 2

3 Prerequisites.. 2

4 Installing Updates.. 2

4.1 Preparation Steps on JBoss for Co-existence with ITCAMfRTT.. 2

4.2 Post-Installation Steps on JBoss for Co-existence with ITCAMfRTT.. 3

4.3 Rollback if Post-Installation Steps Failed.. 4

1 Abstract

The Post-installation Steps for IBM Tivoli Composite Application Manager for J2EE V6.1 provides the following sections:

• Prerequisites
• Preparation steps on JBoss for co-existence with ITCAMfRTT
• Post-installation steps on JBoss for co-existence with ITCAMfRTT

This manual describes how to apply post-installation modifications.

2 Change History

6.1.0 January 18, 2007

• First release.

3 Prerequisites

1. Application server for Java 1.5

2. IBM Tivoli Composite Application Manager for J2EE V6.1, Distributed.

3. All steps are completed successfully as described in 6.1.0.0-TIV-ITCAMfJ2EE_MP-IF0001.README

4 Installing Updates

This section describes how to apply post-installation modifications.

4.1 Preparation Steps on JBoss for Co-existence with ITCAMfRTT

If ITCAMfRTT Monitoring Agent is installed with ITCAMfJ2EE on same JBoss server, you needs upgrade to ITCAMfRTT 6.1.0.0 FP0001 first

After installing the update, you should do manual steps on application server scripts.

Note1: It’s recommended to backup application server scripts before you change them

Note2: you need redo manual steps if product is reinstalled or reconfigured with tool in <DC Home>/installer/config_dc.

Windows:

For JBoss, the application server script you need modify is located in <JBoss Server Home>\bin\run.bat.

Before you change scripts manually, please backup following files:

Ÿ <JBoss Server Home>\bin\run.bat

Unix or Linux:

For JBoss, the application server script you need modify is located in <JBoss Server Home>/bin/run.sh.

Before you change scripts manually, please backup following files:

Ÿ <JBoss Server Home>/bin/run.sh

4.1 Post-Installation Steps on JBoss for Co-existence with ITCAMfRTT

Windows:

Edit application server script (please refer to section 4.1)

i. Change JVM option from JITI_OPTIONS="-Xbootclasspath/a:%MA_INSTRUMENT%\lib\bootic.jar;%MA_INSTRUMENT%\ic\config;<RTT Server Instance path>\config" to JITI_OPTIONS="-Xbootclasspath/a:%MA_INSTRUMENT%\lib\jiti.jar;%MA_INSTRUMENT%\lib\bootic.jar;%MA_INSTRUMENT%\ic\config;<RTT Server Instance Path>\config"

For example,

Change

JITI_OPTIONS=”-Xbootclasspath/a:%MA_INSTRUMENT%\lib\bootic.jar;%MA_INSTRUMENT%\ic\config;…”

To

JITI_OPTIONS="-Xbootclasspath/a:%MA_INSTRUMENT%\lib\jiti.jar;%MA_INSTRUMENT%\lib\bootic.jar;%MA_INSTRUMENT%\ic\config;…"

ii. Append -Xrunjvmpi:<RTT Server Instance path>\config\jiti.properties in JITI_OPTIONS

For example,

Append -Xrunjvmpi:\opt\IBM\itcam\RTT\MA2\MA\app\jboss\61\appServers\jboss_256\config\jiti.properties in JITI_OPTIONS

Unix or Linux:

Edit application server script (please refer to section 4.1)

i. Change JVM option from JITI_OPTIONS="-Xbootclasspath/a:${MA_INSTRUMENT}/lib/bootic.jar:${MA_INSTRUMENT}/ic/config:<RTT Server Instance path>/config" to JITI_OPTIONS="-Xbootclasspath/a:${MA_INSTRUMENT}/lib/jiti.jar:${MA_INSTRUMENT}/lib/bootic.jar:${MA_INSTRUMENT}/ic/config:<RTT Server Instance path>/config"

For example,

Change

JITI_OPTIONS="-Xbootclasspath/a:${MA_INSTRUMENT}/lib/bootic.jar:…”

To

JITI_OPTIONS="-Xbootclasspath/a:${MA_INSTRUMENT}/lib/jiti.jar:${MA_INSTRUMENT}/lib/bootic.jar:${MA_INSTRUMENT}/ic/config:…"

ii. Append -Xrunjvmpi:<RTT Server Instance path>/config/jiti.properties in JITI_OPTIONS

For example,

Append -Xrunjvmpi:/opt/IBM/itcam/RTT/MA2/MA/app/jboss/61/appServers/jboss_256/config/jiti.properties in JITI_OPTIONS

4.2 Rollback if Post-Installation Steps Failed

If post-installation failed, you can copy all backup files back to original path.