IBM Support

ITCAM J2EE 7.1.1 - Weblogic Managed Server configuration

Technical Blog Post


Abstract

ITCAM J2EE 7.1.1 - Weblogic Managed Server configuration

Body

IBM Tivoli Composite Application Agent for J2EE, Version 7.1.1

Detailed Configuration steps for WebLogic servers

Additional information regarding Weblogic Managed Server Instances:

Documented in the Knowledge Center via the following link,

http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.itcamfapps_ad.doc_7211/itcam_j2ee_711_install/ch_config/config_weblogic.html?lang=en

There is a note stating the following,

"Important: If the server instance to be configured is a managed server started by Node Manager, do not select Modify Startup Script File."

The above notation applies to Weblogic Managed servers that are started via a Node Manager using the Weblogic Administration Console.  

In some Weblogic environments, there are Managed Servers running without the use of a node manager.  In this case, the Managed Servers are started using the ‘startManagedWeblogic.sh’ script.

This type of situation requires a startup script to be specified, but NOT the ‘startManagedWeblogic.sh’ script.

The two Weblogic Managed Server environments explained above will now be covered.

1.  Node Manager running and Managed Servers started using the Weblogic Admin Console.

During the configuration you will reach this point and as the ‘Important’ note states, the ‘Modify Startup Script File’ will NOT be checked.

image

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The reason you do not select a startup script is due to the configuration GUI connecting to the Weblogic Admin Server specified on a previous screen,

image

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

At this point, after you select the Managed Servers, the ITCAM configs will be added to the “Server Start”  JVM Arguments.  Upon completion of the configuration, you can log into the Weblogic Admin Console and then navigate to the Managed Server.  Select the ‘Server Start’  Tab and you will see the ITCAM configs in the ‘Arguments’ section,

image

 

 

 

 

 

 

 

 

 

 

The config.xml from the Weblogic Admin Server can also be viewed in order to see the ITCAM configs. 

In addition, any time the Managed Servers are started using the Weblogic Admin console, the ITCAM configs are picked up from the Arguments, thus starting the Data Collector at the same time as the managed server.

** Note: When using a Node Manager, the ITCAM LD_LIBRARY_PATH will be set via the commEnv.sh script located in the WL_HOME/common/bin directory.  The following is added during the configuration,

#********************DC for Weblogic support--begin****************************

# Add DC native library path to ENV

if [ -z "${DC_NATIVE_PATH}" ] ; then

DC_NATIVE_PATH="1"

# Add DC native library path to ENV LD_LIBRARY_PATH

if [ -n "${LD_LIBRARY_PATH}" ]; then

    LD_LIBRARY_PATH=/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/toolkit/lib/lx8266:${LD_LIBRARY_PATH}

else

    LD_LIBRARY_PATH=/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/toolkit/lib/lx8266

fi

export LD_LIBRARY_PATH

#exit

fi

#********************DC for Weblogic support--end ****************************

2.  Weblogic Managed Servers running without a Node Manager and started using the ‘startManagedWeblogic.sh’ script.

In typical cases where the Managed Servers are started using the ‘startManagedWeblogic.sh’ script, the command would look similar to the following,

‘startManagedWeblogic.sh cp_ManagedServer_1 http://<admin_server_host>:7001

If running the Managed servers in the above stated manner, the ITCAM J2EE configuration should be done as follows.

Rather than NOT check the ‘Modify Startup Script File’ check box when running with a Node Manager, the box WILL be checked.  Also, the actual startup script file will need to be specified.  A person would think that the ‘startManagedWeblogic.sh script should be the script to point to, but that is NOT the case.

The script that should be specified is the ‘startWeblogic.sh’ script, which is also used to start the Weblogic Admin Server.  The ITCAM configs for each Managed Server will be added directly to the ‘startWeblogic.sh’

image

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

After the configuration completes, navigate to the ‘startWeblogic.sh’ script which was specified and the following ITCAM configuration stanzas are added.  Note, there will be a stanza for each Managed Server selected during the configuration.  For example, the startWeblogic.sh script will have the following,

 

#cp_ManagedServer_1********************DC for Weblogic support--begin****************************

if [ "${SERVER_NAME}" = "cp_ManagedServer_1" ] ; then

# only for AIX

AIXTHREAD_SCOPE=S

AIXTHREAD_MUTEX_DEBUG=OFF

AIXTHREAD_RWLOCK_DEBUG=OFF

AIXTHREAD_COND_DEBUG=OFF

AIXTHREAD_ENRUSG=ON

# Add DC native library path to ENV LD_LIBRARY_PATH

if [ -n "${LD_LIBRARY_PATH}" ]; then

    LD_LIBRARY_PATH=/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/toolkit/lib/lx8266:${LD_LIBRARY_PATH}

else

    LD_LIBRARY_PATH=/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/toolkit/lib/lx8266

fi

export LD_LIBRARY_PATH

JAVA_OPTIONS="-Xbootclasspath/p:/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/toolkit/lib/bcm-bootstrap.jar:/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/itcamdc/lib/ppe.probe-bootstrap.jar:/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/itcamdc/lib/ext/wls/weblogicBcm.jar -agentlib:am_bea_16=/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/runtime/wls10.cp_domain.cp_Machine_1.cp_ManagedServer_1/dc.env.properties -verbosegc -Xverboselog:/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/runtime/wls10.cp_domain.cp_Machine_1.cp_ManagedServer_1/gc.log   -Xmanagement -Dsun.lang.ClassLoader.allowArraySyntax=true ${JAVA_OPTIONS}"

export JAVA_OPTIONS

#exit

fi

#cp_ManagedServer_1********************DC for Weblogic support--end ****************************

#cp_ManagedServer_2********************DC for Weblogic support--begin****************************

if [ "${SERVER_NAME}" = "cp_ManagedServer_2" ] ; then

# only for AIX

AIXTHREAD_SCOPE=S

AIXTHREAD_MUTEX_DEBUG=OFF

AIXTHREAD_RWLOCK_DEBUG=OFF

AIXTHREAD_COND_DEBUG=OFF

AIXTHREAD_ENRUSG=ON

# Add DC native library path to ENV LD_LIBRARY_PATH

if [ -n "${LD_LIBRARY_PATH}" ]; then

    LD_LIBRARY_PATH=/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/toolkit/lib/lx8266:${LD_LIBRARY_PATH}

else

    LD_LIBRARY_PATH=/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/toolkit/lib/lx8266

fi

export LD_LIBRARY_PATH

JAVA_OPTIONS="-Xbootclasspath/p:/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/toolkit/lib/bcm-bootstrap.jar:/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/itcamdc/lib/ppe.probe-bootstrap.jar:/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/itcamdc/lib/ext/wls/weblogicBcm.jar -agentlib:am_bea_16=/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/runtime/wls10.cp_domain.cp_Machine_1.cp_ManagedServer_2/dc.env.properties -verbosegc -Xverboselog:/opt/IBM/ITM/lx8266/yj/j2eedc/7.1.1.0.0/runtime/wls10.cp_domain.cp_Machine_1.cp_ManagedServer_2/gc.log   -Xmanagement -Dsun.lang.ClassLoader.allowArraySyntax=true ${JAVA_OPTIONS}"

export JAVA_OPTIONS

#exit

fi

#cp_ManagedServer_2********************DC for Weblogic support--end ****************************

# START WEBLOGIC

echo "starting weblogic with Java version:"

 

At this point, when the Managed Servers are started using the ‘startManagedWeblogic.sh’ the ITCAM configs will be picked up from the Admin Server’s ‘startWeblogic.sh’ script.

**Note: Also in this case, the ‘LD_LIBRARY_PATH’ is picked up from the script itself rather than the commEnv.sh script when using a node manager.

[{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"","label":""},"Component":"","Platform":[{"code":"","label":""}],"Version":"","Edition":""}]

UID

ibm11084101