Right-click on the registered Agent from [ADMIN] > [SysMaster] > [Resource] and [Add Resource] menu will appear. Select [Add Resource] to go to the following input screen.

[Figure 4.1] WAS Resource Registration (1)

Enter the 'Resource Name(*)' and select 'WAS' as the 'Resource Type'. The following properties will appear below. Enter all the required fields and click [Save]. The result of resource registration can be seen from the Working Set menu on the left.

[Figure 4.2] WAS Resource Registration (2)

The following is description of the fields. Required fields are marked with (*).

Right-click on the registered resource and click [Add Node] to display the following input screen.

[Figure 4.3] WAS Resource Registration (3)

The following is description of the fields. Required fields are marked with (*).

Right-click on the registered resource and click [Add Container] to display the following input screen.

[Figure 4.4] WAS Resource Registration (4)

Enter all the required fields and click [Save] to register each one. In the previous versions, the user was able to choose any Container name. Starting from SysMaster 3.2 SP2, the following Container name syntax must be used to support the added functionality of JEUS Admin. Up to 30 Containers can be added.

Full name of the Container (Node Name_Container Name) must be used for registration.

Container Name = Node_Container

Copy the was_dc folder to a desired path (generally in 'AGENT_HOME/was_dc')

If sm.home directory is used, create as many sm.properties files as the number of containers in the 'sm.home/sm_properties' directory. Each sm.properties file name should be unique. (e.g., sm.properties1, sm.properties2, etc.)

Configure each sm.properties file according to its container environment.

The following is an example that shows the properties that must be modified for each sm.properties file.

################################################################################
# Sysmaster home
#       - Data Collector's Home directory
################################################################################
# sm.home=/data1/apmqam/agent_5x/sm1007/dc_was/sm_properties/extendbci.propertie
sm.home=/data1/apmqam/agent_5x/sm1007/dc_was


################################################################################
# Network config
#
#       - Data Collector's network properties
#       - net.master.host    : Master's ip
#       - net.master.port    : Master's socket port
#       - net.collector.host : Collector's ip
#       - net.history.port   : Collector's history socket port
#       - net.stat.port      : Collector's statistic socket port
#
################################################################################

# Master Network Config
net.master.host=192.168.1.87
net.master.port=22002

# Collector Network Config
net.collector.host=192.168.1.87
net.history.port=22007
net.stat.port=22006

################################################################################
# Container props
#
#       - Set Resource id
#       - Set cfg path "sm3.properties" 240 lines, 8837 characters
#       - Set Resource id
#       - Set cfg path
#       - Set OutOfMemory Error detect enable : defaule true
#       - Set Socket Trace enable       : defaule true
#       - Set File Trace enable         : defaule true
#       - Set sun's thread cpu time bug enable (linux & sun jdk1.4.x)
#       - Set ClassLoader Trace enable  : defaule true
#
################################################################################
resource.id=R012
container.path=tmaxi7_was.container3

#oomerror.detect.enable=false
#socket.trace.enable=false
#file.trace.enable=false
#sun.threadtime.bug.enable=false
#bci.classloader.enable=false
.... continued

The following is description of the properties.

Check that the library file that retrieves the Java Resource information executes successfully.

apmqam@dc_home]$ java -agentlib:/data1/apmqam/agent/sm1007/dc_was/dcagent/jvmti/aix6L_64/dcagent64 CheckEnv
success jvmti_interface=110206288
sun.boot.library.path:/usr/java5_64/jre/bin

* Enter the path of the folder that contains the libdcagent file. For 64 bit machines, use the 'dsagent64' notation for testing.

Check that the DC environment information has been properly applied to the built sminst JAR file.

apmqam@dc_home]$ java -javaagent:/data1/apmqam/agent/sm1007/dc_was/sminst15_rt.jar CheckEnv

[SMDC] All stdout,stderr will be redirect to: /data1/apmqam/resourceid_node.container1/logs/smlog_resourceid_node.container1

        **************************************************************
               SysMaster Provider(WAS DC) 5.0 
        **************************************************************

         - Property path       : /data1/apmqam/agent/smagent/dc_was/sm_properties/sm2.properties
         - Extend BCI path     : 
         - Resource ID         : R012
         - Container PATH      : tmaxi7_was.container2
         - Master IP           : 192.168.1.87
         - Collector IP        : 192.168.1.87
         - Req Port            : 22002
         - Tx  Port            : 22007
         - Mon Port            : 22006
         - OOM Detect          : true
         - SQL PARAM TRACE     : true
         - Thread Command      : true
         - Socket Trace        : true
         - TX His threshold    : 3000 ms
         - TX View threshold   : 100 ms
         - TX His send rate    : 0.05
         - TX view send rate   : 0.2
         - TX header send rate : 0.2
         - User profile enable : true
         - User profile filter : included packages and classes

sun.boot.library.path:/usr/java5_64/jre/bin

Check that the built library file has been successfully loaded.

apmqam@dc_home]$java -Xbootclasspath/p:/data1/apmqam/agent/sm1007/dc_was/sminst15_rt.jar:
/data1/apmqam/agent/sm1007/dc_was/sminst_15.jar CheckEnv
sun.boot.library.path:/usr/java5_64/jre/bin

Check that the configured properties file has been successfully loaded.

apmqam@dc_home]$java -Dsm.property=/data1/apmqam/agent/sm1007/dc_was/properties/sm1.properties CheckEnv
sun.boot.library.path:/usr/java5_64/jre/bin

Add to server xml

Add settings in C:\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\starkohNode01Cell\nodes \starkohNode01\servers\server1\server.xml

...
genericJvmArguments="-Dwas.vendor=websphere -javaagent:C:\TmaxSoft\SysMaster\agent\was_dc\sminst16_rt_ws85.jar -Dsm.property=C:\TmaxSoft\SysMaster\agent\was_dc\sm_properties/sm.properties_ws85 -agentpath:C:\TmaxSoft\SysMaster\agent\was_dc\dcagent\jvmti\win64\dcagent64.dll" executableJarFileName="" disableJIT="false">
      <bootClasspath>C:\TmaxSoft\SysMaster\agent\was_dc\sminst16_rt_ws85.jar</bootClasspath>
...

Configure the webadmin property: configure the JVM boot class path.

Select [Application Server] > [server Name] > Server Infrastructure – Manage Java and Process – Define Process > JVM. Configure directory information in the 'Boot Class Path' field of the General Features section.

$WEBLOGIC _HOME/server/bin

[Figure 4.5] WebSphere Web Console – General JVM Property Configuration

Configure the webadmin property: configure the values in sm.properties.

Select [Application Server] > [server Name] > Server Infrastructure – Manage Java and Process – Define Process > JVMUser Defined Features. Set the sm.properties path to the 'Value' field of the General Features section.

PATH/sm.properties

[Figure 4.6] WebSphere Web Console – sm.properties Path Configuration

[Figure 4.7] WebSphere Web Console – sm.properties Configuration

JBOSS AS 7.0 and 7.1

Pool information cannot be collected because the pool information is not exposed through MBean.

Add java options to JBOSS AS 7.3 $JBOSS_HOME/bin/standalone.conf as in the following.

...
JAVA_OPTS="$JAVA_OPTS -agentpath:/home/gmrcb/sysmaster/jboss/was_dc/dcagent/jvmti/linux2.x/libdcagent64.so 
-javaagent:/home/gmrcb/sysmaster/jboss/was_dc/sminst_rt.jar -Xbootclasspath/p:/home/gmrcb/sysmaster/jboss/was_dc/sminst_rt.jar 
-Dsm.property=/home/gmrcb/sysmaster/jboss/was_dc/sm_properties/sm.properties2 -Djava.util.logging.manager=org.jboss.logmanager.LogManager"
...

Add a package to JBOSS AS 7.3

OracleAS can execute a multi-process instance. The following shows how to configure a single-instance for a single process and a multi-instance for multiple processes.

Specify the directory that contains the property files used by the DC.

Similar to other configurations, 'PATH' represents an absolute path and 'properties' is the directory that contains the configuration file. The 'properties' directory contains property files that use the following naming conventions.

sm.propertiesID  e.g., sm.properties1, sm.properties2

Configure the libdcagent.so file. Place the libdcagent file according to the JDK as shown in the following.

Restart WAS

Restart the SysMaster Agent. For more information about restarting the agent process, refer to "3.5. Starting and Terminating Agent".

Check if libdcagent.so generates an error, and then execute the following command from the directory of the sminst.jar file and verify that the cputime is correctly displayed.

If CPU Time is displayed correctly, it means that the libdcagent.so executes normally. Hence, check the DC settings inside WAS section for issues.

Right-click on the registered Agent from [ADMIN] > [SysMaster] > [Resource] and [Add Resource].

Select [Add Resource] to go to the following screen.

[Figure 4.8] Oracle Resource Registration (1)

Enter the 'Resource Name(*)' and select 'Oracle' as the 'Resource Type'. The following properties will appear below. Enter all the required fields and click [Save]. The result of resource registration can be seen from the Working Set menu on the left.

[Figure 4.9] Oracle Resource Registration (2)

The following is description of the fields. Required fields are marked with (*).

select instance_name from v$instance;

Right-click on the registered resource and click [Add Node] to display the following input screen.

[Figure 4.10] Oracle Resource Registration (3)

The following is description of the fields. Required fields are marked with (*).

Configure the properties in the $SMORADC/config/oradc.cfg file.

If Oracle DC is configured while installing the Agent, the user can only configure the oradc.resource_id, oradc.resource_name, and oradc.sga.* items.

oradc.db.address=192.168.32.199
oradc.db.port=1521
oradc.db.user=SMADM
oradc.db.password=SMADM
oradc.db.sid=ora11g
oradc.db.priv=

oradc.resource_id=R019
oradc.resource_name=ubun_ora11g
oradc.master.address=192.168.32.199
oradc.master.monitor.port=22006
oradc.master.request.port=22002
oradc.master.transaction.port=22007

oradc.sga.shm_num=1
oradc.sga.shm_ids=720899
oradc.sga.shm_keys=
oradc.sga.shm_addrs=

The following is description of the properties.

select instance_name from v$instance;

Restart Oracle DC.

Restart the SysMaster Agent. For more information about restarting an Agent, refer to "3.5. Starting and Terminating Agent".

Right-click on the registered Agent from [ADMIN] > [SysMaster] > [Resource] and [Add Resource].

Select [Add Resource] to go to the following screen.

[Figure 4.11] Tibero Resource Registration (1)

Enter the 'Resource Name(*)' and select 'Tibero' as the 'Resource Type'. The following properties will appear below. Enter all the required fields and click [Save]. The result of resource registration can be seen from the Working Set menu on the left.

[Figure 4.12] Tibero Resource Registration (2)

The following is description of the fields. Required fields are marked with (*).

select instance_name from v$instance;

sql.elapsed.threshold1 : 10
sql.elapsed.threshold2 : 50
sql.elapsed.threshold3 : 200
sql.elapsed.threshold4 : 400

Right-click on the registered resource and click [Add Node] to display the following input screen.

[Figure 4.13] Tibero Resource Registration (3)

The following is description of the fields. Required fields are marked with (*).

Restart Tibero DC.

Restart the SysMaster Agent. For more information about restarting an Agent, refer to "3.5. Starting and Terminating Agent".