IBM Tivoli Composite Application Manager for J2EE V6.1.0.0

Multi Platform Data Collector

Distributed

 

Interim Fix 0002 Post-Installation Steps for Weblogic

 

February 28, 2007

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


 

Contents

1      Abstract.. 2

2      Change History.. 2

3      Prerequisites.. 2

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

4.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                February 26, 2007

 

3         Prerequisites

 

1. Application server for Java 1.4

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-IF0002.README

4         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.

 

4.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.   If there is no following GC option in JVM options, then user need add GC option in JVM option.

                   

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

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

                     For Bea JRockit 1.4, -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.   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.4, -Xloggc:<log file path>

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

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