JEUS has the following directory structure after a successful installation. For detailed information about each directory, refer to "JEUS 6.0 Installation Guide".

$MASTER_HOME
    +- jeus
        +- bin
        +- config
        +- lib
        +- license
        +- logs
        +- path
        +- webhome
        +- webserver

Verify the license of the installed product.

$SYSMASTER_HOME/jeus/license/license.dat

If there is a problem with the license, contact the sales representative or submit a license request to the department in charge.

Check the files in the JEUS binary directory.

Checking the Files in the 'JEUS_HOME/lib/application' Directory

Verify that the following files are located in the 'JEUS_HOME/lib/application' directory.

US_export_policy.jar
activation.jar
common-util.jar
commons-cli.jar
commons-codec.jar
commons-collections.jar
commons-configuration.jar
commons-dbcp.jar
commons-fileupload.jar
commons-httpclient.jar
commons-io.jar
commons-lang.jar
commons-lang3.jar
commons-logging.jar
commons-net.jar
commons-pool.jar
commons-primitives.jar
freemarker.jar
javassist.jar
jmxri.jar
json_simple.jar
libsmlic.so
libsmlic64.so
local_policy.jar
log4j.jar
mail.jar
ognl.jar
oro.jar
poi.jar
sqlbuilder.jar
struts2-core.jar
struts2-json-plugin.jar
sysmaster-base-bootstrap.jar
sysmaster-base.jar
webt30.jar
xwork-core.jar

Checking the webhome Directory

Verify the sysmaster directory after the Master server is started.

$SYSMASTER_HOME/jeus/webhome/app_home/sysmaster

Check the SysMaster v5.0 settings in the JEUS environment configuration file. For detailed information about the configurations, refer to each relevant section.

Checking JEUSMain.xml

Checking WEBMain.xml

The WEBMain.xml file is located in the following location.

$JEUS_HOME/config/{hostname}_servlet_engine1 // Master Container(Container1)
$JEUS_HOME/config/{hostname}_servlet_engine2 // UI Container(Container2)

<{hostname}_servlet_engine1/cat WEBMain.xml>

<?xml version="1.0"?>
<web-container xmlns="http://www.tmaxsoft.com/xml/ns/jeus" version="6.0">
    <context-group>
        <group-name>SysMaster</group-name>
        <webserver-connection>
            <http-listener>
                <listener-id>http1</listener-id>
                <port>9488</port>
                <thread-pool>
                    <min>10</min>
                    <max>20</max>
                    <step>1</step>
                </thread-pool>
            </http-listener>
        </webserver-connection>
        <encoding>
            <request-url-encoding>
                <forced>UTF-8</forced>
            </request-url-encoding>
            <request-encoding>
                <default>EUC-KR</default>
            </request-encoding>
            <response-encoding>
                <default>UTF-8</default>
            </response-encoding>
        </encoding>
    </context-group>
</web-container>

<{hostname}_servlet_engine2/cat WEBMain.xml>

The access log in the logging section is set to false due to its disk usage, but the <enable> setting can be changed to true to check the Container's log.

<?xml version="1.0"?>
<web-container xmlns="http://www.tmaxsoft.com/xml/ns/jeus" version="6.0">
    <context-group>
        <group-name>SysMaster</group-name>
        <webserver-connection>
            <webtob-listener>
                <listener-id>webtob1</listener-id>
                <port>9900</port>
                <thread-pool>
                    <min>10</min>
                    <max>10</max>
                    <step>1</step>
                    <max-idle-time>30000</max-idle-time>
                </thread-pool>
                <webtob-address>localhost</webtob-address>
                <registration-id>MyGroup</registration-id>
            </webtob-listener>
        </webserver-connection>
        <encoding>
            <request-url-encoding>
                <forced>UTF-8</forced>
            </request-url-encoding>
            <request-encoding>
                <default>EUC-KR</default>
            </request-encoding>
            <response-encoding>
                <default>UTF-8</default>
            </response-encoding>
        </encoding>
        <logging>
          <access-log>
              <enable>false</enable>
          </access-log>
        </logging>
    </context-group>
</web-container>

Checking vhost.properties

Check the JEUS_BASEPORT setting in the vhost.properties file.

The file is located in the following directory.

$JEUS_HOME/config/vhost.properties

The following are the settings in vhost.properties.

jeus.vhost.enabled=true
{hostname}={hostname}:9736

Checking jeus.properties

The jeus.properties file is located in the following directory.

$JEUS_HOME/bin/jeus.properties

The following is an example of jeus.properties.

#
# For customizing JEUS environment.
#

# set up JEUS_BASEPORT.
JEUS_BASEPORT=9736

# set up JEUS_WSDIR.
JEUS_WSDIR="${JEUS_HOME}/webserver"

# set up JEUS_LIBPATH.
JEUS_LIBPATH="${JEUS_HOME}/lib/system:${JEUS_HOME}/lib/application"

# Select language for JEUS. Available value can be jp.
JEUS_LANG=ko

# set up SESSION_MEM
SESSION_MEM=-Xmx512m

# set up
JAVA_HOME="/home/daehun2/java6"

# setup JAVA_ARGS.
JAVA_ARGS="$SYSMASTER_JAVA_ARGS"

# set up JDK vendor. Possible values are Sun, HP, IBM, etc. Default, Sun.
JAVA_VENDOR=IBM

export JEUS_HOME JEUS_BASEPORT JEUS_LIBPATH JEUS_LANG
export JEUS_WSDIR JAVA_HOME JAVA_ARGS JAVA_VENDOR SESSION_MEM

Checking the changes in the JEUS file

Check that sysmaster has been added to the '-Djeus.properties.replicate' option in the jeus file.

The jeus file is located in the following directory.

$JEUS_HOME/bin/jeus 

The following are the contents of the jeus file.

"${JAVA_HOME}/bin/java" $VM_OPTION  $SESSION_MEM                            \
    -Xbootclasspath/p:"${JEUS_HOME}/lib/system/extension.jar"               \
    -classpath "${JEUS_HOME}/lib/system/bootstrap.jar"                      \
    -Dsun.rmi.dgc.client.gcInterval=3600000                                 \
    -Dsun.rmi.dgc.server.gcInterval=3600000                                 \
    -Djava.library.path="${JEUS_LIBPATH}"                                   \
    -Djava.endorsed.dirs="${JEUS_HOME}/lib/endorsed"                        \
    -Djava.naming.factory.initial=jeus.jndi.JNSContextFactory               \
    -Djava.naming.factory.url.pkgs=jeus.jndi.jns.url                        \
    -Djava.net.preferIPv4Stack=true                                         \
    -Djava.util.logging.config.file="${JEUS_HOME}/bin/logging.properties"   \
    -Djeus.home="${JEUS_HOME}"                                              \
    -Djeus.baseport=${JEUS_BASEPORT}                                        \
    -Djeus.jvm.version=${VM_TYPE}                                           \
    -Djeus.tm.checkReg=true                                                 \
    -Djeus.tool.webadmin.locale.language=${JEUS_LANG}                       \
    -Djeus.tm.checkReg=true                                                 \
    -Djeus.tool.webadmin.locale.language=${JEUS_LANG}                       \
    -Djeus.net.reuseAddress=true                                            \
    -Djeus.properties.replicate=sysmaster,jeus,sun.rmi,java.util,java.net   \
    ${JAVA_ARGS}                                                            \
    jeus.server.JeusBootstrapper ${BOOT_PARAMETER}

Checking the changes in policies.xml

Check the <resource-permissions> section in policies.xml.

The policies.xml file is located in the following directory.

$JEUS_HOME/config/hostname/security/SYSTEM_DOMAIN/policies.xml

The following are the contents of policies.xml.

<policies xmlns="http://www.tmaxsoft.com/xml/ns/jeus" version="6.0">
    <policy>
        <role-permissions>
            <role-permission>
                <principal>administrator</principal>
                <role>AdministratorsRole</role>
            </role-permission>
            <role-permission>
                <principal>anonymous</principal>
                <role>jndiUser</role>
            </role-permission>
        </role-permissions>
        <resource-permissions>
            <context-id>default</context-id>
            <resource-permission>
                <role>AdministratorsRole</role>
                <resource>jeus.*</resource>
                <actions>*</actions>
            </resource-permission>
            <resource-permission>
                <role>jndiUser</role>
                <resource>jeus.jndi.*</resource>
                <actions>*</actions>
            </resource-permission>
        </resource-permissions>
    </policy>
</policies>
~

Check the SysMaster settings in the environment configuration file (modify ws_engine.m) of the embedded WebtoB in JEUS.

ws_engine.m

Modify JSVPORT and group name in the WebtoB configuration file as specified in the JEUS WEBMain.xml file. Because excessive amounts of access.logs tend to accumulate on the Web server, the log1 setting has been commented out. Uncomment the setting to use the access.log setting. For more information, refer to the "WebtoB Administrator's Guide".

<ws_engine.m>

*DOMAIN
jeuservice

*NODE
ubunqa
  WEBTOBDIR = "/home/daehun2/sysmaster/master5/jeus/webserver",
  SHMKEY    = 65000,
  DOCROOT   = "/home/daehun2/sysmaster/master5/jeus/webserver/docs",
  PORT      = "9488",
#  LOGGING   = "log1",
  ERRORLOG  = "log2",
  JSVPORT   = 9900,
  HTH       = 1

*SVRGROUP
htmlg       NODENAME = "ubunqa", SVRTYPE = HTML
#cgig       NODENAME = "ubunqa", SVRTYPE = CGI
#ssig       NODENAME = "ubunqa", SVRTYPE = SSI
jsvg        NODENAME = "ubunqa", SVRTYPE = JSV

*SERVER
html        SVGNAME  = htmlg, MinProc = 10,  MaxProc = 20, ASQCount = 10
#cgi        SVGNAME  = cgig,  MinProc = 1,  MaxProc = 2
#ssi        SVGNAME  = ssig,  MinProc = 1,  MaxProc = 2
MyGroup     SVGNAME  = jsvg,  MinProc = 10,  MaxProc = 50

*URI
htmlUrl   Uri = "/sysmaster/resource/",  Svrtype = HTML

*ALIAS
alias1     URI = "/cgi-bin/", 
           RealPath = "/home/daehun2/sysmaster/master5/jeus/webserver/cgi-bin/"

*LOGGING
#log1        Format   = "DEFAULT",   
#            FileName = "/home/daehun2/sysmaster/master5/jeus/webserver/log/access.log", 
#            Option = "sync"
log2        Format   = "ERROR",     
            FileName = "/home/daehun2/sysmaster/master5/jeus/webserver/log/error.log",  
            Option = "sync"

*EXT
htm         MimeType = "text/html",  SvrType = HTML
jsp         Mimetype ="application/jsp",  Svrtype=JSV,  SvrName=MyGroup
action      Mimetype ="application/jsp",  Svrtype=JSV,  SvrName=MyGroup

Execute the created configuration file.

[daehun2:/home/daehun2/sysmaster/master5/jeus/webserver/config]$wscfl -i ws_engine.m
        Current configuration:
                Number of client handler(HTH) = 1
                Supported maximum user per node = 8162
                Supported maximum user per handler = 8162
CFL is done successfully for node(ubunqa(ubunqa))
[daehun2:/home/daehun2/sysmaster/master5/jeus/webserver/config]$wsgst
SVC tables are successfully generated 
GST is successfully done 

If the file executes successfully, start WebtoB by using the following command.

wsboot

The following are the steps for starting the Master Server.

Terminating the SysMaster server is same as terminating an active process of a WAS server, JEUS. After terminating all processes of each container, the WAS Administrator process can be terminated.

The following are the steps for terminating the Master Server.