Appendix B. SysMaster DC Configuration

Table of Contents

B.1. JEUS Environment Configuration
B.2. WebLogic Configuration
B.3. sm.properties File Configuration

This appendix describes how to configure SysMaster DC.

B.1. JEUS Environment Configuration

SysMaster settings must be included in JEUSMain.xml, the default JEUS configuration file. SysMaster settings are added to the engine container's <command-option> element by either manually editing the file or using JEUS WebManager.

The following settings need to be configured.

Boot Classpath Setting

Use -Xbootclasspath/p option of JVM to set SysMaster files, sminst_rt.jar.

The following is an example.
```
 -Xbootclasspath/p:/smagent/dc/sminst_rt.jar
```
System Property Setting

Set the path of the sm.properties file that contains the configuration properties for SysMaster.

The following is an example.
```
–Dsm.property=/smagent/dc/properties/sm.properties
```

Configuring Using JEUS WebManager

When a target monitoring container is selected from JEUS node tree, Engine Container screen is displayed.

Select Engine Container screen from [Configuration] > [General] tab.

[Figure B.1] Configuring Using JEUS WebManager

Enter the settings in the 'Command Option' field.

 -Xbootclasspath/p:/smagent/dc/sminst_rt.jar –Dsm.property=/smagent/dc/properties/sm.properties

Click [OK] to save, and then restart the engine container to apply the changes.

Modifying JEUSMain.xml File

Open the JEUSMain.xml file in a text editor, and add settings in the <command-option> element inside the <engine-container> element.

<?xml version="1.0" encoding="utf-8"?>
<jeus-system xmlns="http://www.tmaxsoft.com/xml/ns/jeus">
    <node>
        <name>jeuswas</name>
        <engine-container>
            <name>container1</name>
            <command-option>
            -Xbootclasspath/p:/smagent/dc/sminst_rt.jar
            -Dsm.property=/smagent/dc/properties/sm.properties
            ....
            </command-option>
            <engine-command>
                <type>ws</type>
                <name>engine1</name>
            </engine-command>
...

Save the changed settings, and then restart the engine container.

B.2. WebLogic Configuration

For WebLogic WAS configuration, add options to the start up shell (Oracle/Middleware1036/usr_projects/domains/[domain name]/bin/startWebLogic.sh).

export JAVA_OPTIONS="${JAVA_OPTIONS}
 -agentpath:/home/daehun/sysmaster/agents/was_dc/dcagent/jvmti/linux2.x/libdcagent64.so
 -javaagent:/home/daehun/sysmaster/agent/was_dc/sminst_rt.jar
 -Xbootclasspath/p:/home/daehun/sysmaster/agent/was_dc/sminst_rt.jar
 -Dsm.property=/home/daehun/sysmaster/agent/was_dc/sm_properties/weblogic.properties"

Save the settings, and then restart WebLogic.

B.3. sm.properties File Configuration

To collect container data, container-specific settings must be configured in WAS Node tab as well as in the sm.porperties file.

Note

For more detailed information, refer to "SysMaster Installation Guide".

Each container's sm.properties file is referenced by the environment file of the target WAS during startup. For JEUS, add settings to the JEUSMain.xml environment file.

<engine-container>
<name>container1</name>
<command-option>
…
     -Dsm.property=/data/ apmqas/agent3011/dc/sm.properties1
 </command-option>

Locate and open the sm.properties file to configure various monitoring related settings. Save the changed settings, and then restart WAS to apply the changes. Set each option value to true or false. (Default value : false)

sm.home=/data1/tmaxqas/agent3009/dc
…
#oomerror.detect.enable=true
socket.trace.enable=true
file.trace.enable=true
sun.threadtime.bug.enable=true
bci.classload.trace.enable=true

Prev		Next
Appendix A. Data Collection	Home	Appendix C. Thread Dump Configuration