Chapter 10. Practice

Following the steps in this chapter will allow the user to easily become familiar with JEUS.

The following example assumes that the JEUS server is named "server1". Change this to the actual name of the JEUS server that is installed.

  1. Verify that JEUS is installed properly and that the system paths and variables are set properly. Verify that the directory "JEUS_HOME/bin/" is included in the system path.

    Note

    In this guide, "JEUS_HOME" refers to the root of the JEUS installation directory. For example, “/home/user/jeus7”.

    Refer to "JEUS Installation & Getting Started" for more information about installing JEUS.

  2. At least one connection must exist on a web engine of a managed server. Refer to "Chapter 2. Web Connection Management" for more information about configuring web connections.

    An HTTP listener with a port set to '8088' can be added as described in "2.3.3. HTTP Listeners".

  3. After completing the configurations, enter the following command to execute the JEUS launcher. The arguments '-u' and '-p' are used to specify the administrator name and password that were set during the installation.

    The following example assumes that the administrator name and password have been set to 'jeus'.

    startDomainAdminServer -domain domain1 -server server1 -u jeus -p jeus

  4. Open a different command window and execute 'jeusadmin -u jeus -p jeus'. (If '-u' and '-p' values are missing, enter 'login' again).

    user1@jeus$jeusadmin
    JEUS7 Administration Tool
    To view help, use the 'help' command.
    offline>login

  5. After entering the server address, administrator name, and password that were set during the installation, the console tool will start.

    offline>login
    Enter the server address: localhost
    User name: jeus
    Password: 
    Attempting to connect to 127.0.0.1:9736.
    The connection has been established to Domain Administration Server adminServer in the domain domain1.
    [DAS]domain1.adminServer>

  6. Execute the following command to list the commands that can monitor and control the web engine.

    [DAS]domain1.adminServer>help -g Web
    [ Web]______________________________________________________________________
    add-response-header             Add an HTTP response custom header.
    add-tmax-connector              Add Tmax Connector.
    add-virtual-host                A virtual host was dynamically added to
    domain.xml, but this was only applied to
    the XML file, not to a server.
    add-web-cookie-policy           Add the cookie policy configuration.
    add-web-encoding                Add web engine characterset encoding.
    add-web-listener                Add HTTP listener, AJP13 listener, or TCP
    listener. If the type is not specified,
    anHTTP Listener will be added by default.
    add-web-properties              Add web engine properties.
    add-webtob-connector            Add the WebtoB Connector.
    clear-web-statistics            Resets the web engine statistics.
    list-session                    Show session list sorted by idle time.
    list-webtob-connections         List the WJP connections of specified
    webtob-connector.
    modify-jsp-engine               Modify JSP engine configurations.
    modify-response-header          Modify the HTTP response custom header.
    modify-session-configuration    Modifies the session configuration.
    modify-tmax-connector           Modify the thread pool number of the
    tmax-connector.
    modify-virtual-host             Modify the access log format of a virtual
    host dynamically. The access log must be
    enabled.
    modify-web-cookie-policy        Modify the cookie policy configuration.
    modify-web-encoding             Modify the web engine characterset
    encoding configurations.
    modify-web-engine-configuration Modify some parts of the web engine
    configuration dynamically.
    modify-web-listener             Modify the thread pool number of the web
    listener (http-listener, tcp-listener, or
    ajp13-listener).
    modify-web-properties           Modify web engine properties.
    modify-webtob-connector         Modify the thread pool number of the
    webtob-connector.
    reload-web-context              Forcibly reloads the servlet context.
    remove-response-header          Remove the HTTP response custom header.
    remove-session                  Remove session.
    remove-tmax-connector           Remove the tmax-connector.
    remove-virtual-host             A virtual host was dynamically removed
    from domain.xml, but this was only
    appliedto the XML file, not to a server.
    remove-web-cookie-policy        Remove the HTTP cookie policy
    configuration.
    remove-web-encoding             Remove the web engine characterset
    encoding configurations.
    remove-web-listener             Remove a web listener (http-listener,
    tcp-listener, or ajp13-listener).
    remove-web-properties           Remove web engine properties.
    remove-webtob-connector         Remove webtob-connector.
    resume-web-component            Temporarily resumes the given component
    (servlet element of context or given
    web-connection name).
    show-request-processing-flow    Shows the request processing flow of
    mapped URL patterns and the specified
    hostname.
    show-session-configuration      Shows the session configuration.
    show-web-engine-configuration   Show web engine configurations, including
    the monitoring period and access-logs.
    show-web-statistics             Shows the web engine statistics.
    suspend-web-component           Temporarily suspends the servlet.
    precompile-jsp                  Precompile JSP files for a deployed web
    module. Connect to Domain Administration
    Server or a server.
    
    To show detailed information for a command, use 'help [COMMAND_NAME]'.
    ex) help connect
    
            

  7. Execute a web engine control or monitoring command.

    Refer to "JEUS Reference Guide" for more information about web engine commands.

  8. WebAdmin can be used to perform the same operations.

    Refer to JEUS WebAdmin Guide. "2.2. Logging In" for more information about how to execute WebAdmin.

If a problem occurs in the previous steps, check and adjust the JEUS environment configurations. To find the source of the problem, refer to the log records in the JEUS manager console log.

Note

Refer to "JEUS Installation and Getting Started" and "JEUS Server Guide" for more information about configuring a JEUS environment.