IBM Tivoli Composite Application Manager for J2EE V6.1.0.0

Multi Platform Data Collector

Distributed

 

Interim Fix 0001 Post-Installation Steps for Weblogic

 

January 18, 2007

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Contents

1      Abstract.. 2

2      Change History.. 2

3      Prerequisites.. 2

4      Installing Updates for Co-existence with ITCAMfRTT.. 2

4.1    Preparation Steps on Weblogic for Co-existence with ITCAMfRTT.. 3

4.2    Post-Installation Steps on Weblogic for Co-existence with ITCAMfRTT.. 4

4.3    Post-Installation Steps on Weblogic Admin Server in Cluster Environment.. 5

4.4    Rollback if Post-Installation Steps Failed.. 8

5      Installing Updates on Weblogic if Admin Server and Managed Server are Monitored by Same DC   8

5.1    Post-Installation Steps on Weblogic Admin Server in Cluster Environment.. 8

1         Abstract

 

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

 

This manual describes how to apply post-installation modifications.

2         Change History

 

6.1.0                January 18, 2007

 

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 for Co-existence with ITCAMfRTT

 

This section describes how to apply post-installation modifications.

 

4.1      Preparation Steps on Weblogic for Co-existence with ITCAMfRTT

 

If ITCAMfRTT Monitoring Agent is installed with ITCAMfJ2EE on same Weblogic 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 Weblogic 9 standalone environment, the application server script you need modify is located in <Domain Home>\bin\startWeblogic.cmd, and find “@REM <your server>”

 

For Weblogic 9 cluster environment, please complete the update process on Weblogic Admin server as standalone if it’s monitored by Data Collector.

 

Next, if managed server can be started by node manager, you need apply following change by web admin console, navigate to “Environment->Servers-><your server>”, open panel "Configuration->Server Start", update field "Arguments" as describe following and save. If the managed server can be started from command also, there is another application server script you need modify, which is located in <Domain Home>/bin/startWeblogic.cmd, between the tags “@REM <your server>***DC for Weblogic support--begin” and “@REM <your server>***DC for Weblogic support--end”.

 

All managed configuration is saved in <Domain Home>\config\config.xml on Weblogic Admin Server, it’s recommended to backup it first.

 

Before you change scripts manually, please backup following files:

 

Ÿ           <Domain Home>\bin\startWeblogic.cmd on standalone Weblogic server or Admin/managed server.

Ÿ           <Domain Home>\config\config.xml on Weblogic Admin server.

                   

            Unix or Linux:

 

For Weblogic 9 standalone environment, the application server script you need modify is located in <Domain Home>/bin/startWeblogic.sh

 

For Weblogic 9 cluster environment, please complete the update process on Weblogic Admin server as standalone if it’s monitored by Data Collector.

 

Next, if managed server can be started by node manager, you need apply following change by web admin console, navigate to “Environment->Servers-><your server>”, open panel "Configuration->Server Start", update field "Arguments" as describe following and save. If the managed server can be started from command also, there is another application server script you need modify, which is located in <Domain Home>/bin/startWeblogic.cmd, between the tags “#<your server>***DC for Weblogic support--begin” and “#<your server>***DC for Weblogic support--end”.

 

All managed configuration is saved in <Domain Home>/config/config.xml on Weblogic Admin Server, it’s recommended to backup first.

 

Before you change scripts manually, please backup following files:

 

Ÿ           <Domain Home>/bin/startWeblogic.sh on standalone Weblogic server or Admin/managed server.

Ÿ           <Domain Home>/config/config.xml on Weblogic Admin server.

 

4.2      Post-Installation Steps on Weblogic 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\weblogic\61\appServers\weblogic_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/weblogic/61/appServers/weblogic_256/config/jiti.properties in JITI_OPTIONS

 

4.3      Rollback if Post-Installation Steps Failed

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

 

5         Installing Updates on Weblogic if Admin Server and Managed Server are Monitored by Same DC

 

If Admin Server and Managed Server are monitored by same DC, i.e. under same <DC Home>, you need do following manual steps.

 

5.1      Post-Installation Steps on Weblogic Admin Server in Cluster Environment

 

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

 

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

 

            Windows:

 

All managed configuration is saved in <Domain Home>\config\config.xml on Weblogic Admin Server, it’s recommended to backup it first.

 

Before you change scripts manually, please backup following files:

Ÿ           <Domain Home>\config\config.xml on Weblogic Admin server.

 

Step1. Start admin server, and make sure managed server(s) shutdown.

 

Step2. Modify managed server startup script. You need apply following change by web admin console, navigate to “Environment->Servers-><your server>”, open panel "Configuration->Server Start", update field "Arguments" as describe following and save.

 

i.   Change JVM option "-Xrun<native library name>:<DC Home>\toolkit\etc\jiti.properties" to "-agentlib:<native library name>"

     

For example,

 

                    Change "-Xrunam_ibm_15:%PRODUCT_HOME%\toolkit\etc\jiti.properies" to "-agentlib:am_ibm_15"

                   

ii.   Remove JVM option "<DC Home>\toolkit\lib\jiti.jar from -Xbootclasspath/p:<DC Home>\toolkit\lib\bcm-bootstrap.jar;<DC Home>\toolkit\lib\jiti.jar;<DC Home>\toolkit\lib\ppe.probe-bootstrap.jar...

                   

For example,

 

                    Change

                            "-Xbootclasspath/p:%PRODUCT_HOME%\toolkit\lib\bcm-bootstrap.jar;%PRODUCT_HOME%\toolkit\lib\jiti.jar;%PRODUCT_HOME%\toolkit\lib\ppe.probe-bootstrap.jar"

                        To

                            "-Xbootclasspath/p:%PRODUCT_HOME%\toolkit\lib\bcm-bootstrap.jar;%PRODUCT_HOME%\toolkit\lib\ppe.probe-bootstrap.jar"

                       

iii.   Remove JVM option "-Dcom.ibm.tivoli.jiti.injector.IProbeInjectorManager=…"

                   

iv.   Remove JVM option "-Dcom.ibm.tivoli.jiti.injector.ProbeInjectorManagerChain.primaryInjectorFile=<DC Home>\runtime\<Server Instance Path>\probeinjectormanagerchain.properties"

                   

v.   If there is no following GC option in JVM options, then user need add GC option in JVM option.

                   

                     For Sun JDK 1.5, -Xloggc:<log file path>

                     For IBM JDK 1.5, -Xverbosegclog:<log file path> -verbose:gc

                     For Bea JRockit 1.5, -verbose:gc -Xverboselog:<log file path>

 

            Unix or Linux:

 

 

All managed configuration is saved in <Domain Home>/config/config.xml on Weblogic Admin Server, it’s recommended to backup first.

 

Before you change scripts manually, please backup following files:

Ÿ           <Domain Home>/config/config.xml on Weblogic Admin server.

 

Step1. Start admin server, and make sure managed server(s) shutdown.

 

Step2. Modify managed server startup script. You need apply following change by web admin console, navigate to “Environment->Servers-><your server>”, open panel "Configuration->Server Start", update field "Arguments" as describe following and save.

 

               

i.    Change "-Xrun<native library name>:<DC Home>/toolkit/etc/jiti.properties" to "-agentlib:<native library name>"

               

For example,

                   

              Change "-Xrunam_ibm_15:$PRODUCT_HOME/toolkit/etc/jiti.properies" to "-agentlib:am_ibm_15"

                   

ii.    Remove "<DC Home>/toolkit/lib/jiti.jar" from -Xbootclasspath/p:<DC Home>/toolkit/lib/bcm-bootstrap.jar:<DC Home>/toolkit/lib/jiti.jar:<DC Home>/toolkit/lib/ppe.probe-bootstrap.jar

                   

For example,

                   

               Change

                       "-Xbootclasspath/p:$PRODUCT_HOME/toolkit/lib/bcm-bootstrap.jar:$PRODUCT_HOME/toolkit/lib/jiti.jar:$PRODUCT_HOME/itcamdc/lib/ppe.probe-bootstrap.jar"

               To

                            "-Xbootclasspath/p:$PRODUCT_HOME/toolkit/lib/bcm-bootstrap.jar:$PRODUCT_HOME/itcamdc/lib/ppe.probe-bootstrap.jar"

                    

iii.   Remove "-Dcom.ibm.tivoli.jiti.injector.IProbeInjectorManager=com.ibm.tivoli.itcam.toolkit.ai.bcm.bootstrap.ProbeInjectorMananger"

                   

iv.   Remove "-Dcom.ibm.tivoli.jiti.injector.ProbeInjectorManagerChain.primaryInjectorFile=<DC Home>/runtime/<Server Instance Path>/probeinjectormanagerchain.properties"

                   

v.    If there is no following GC options in JVM option turned on, then user needs add GC option in JVM option.

                   

               For Sun JDK 1.5, -Xloggc:<log file path>

               For IBM JDK 1.5, -Xverbosegclog:<log file path> -verbose:gc

               For Bea JRockit 1.5, -verbose:gc -Xverboselog:<log file path>