JEUS Configuration

This chapter describes the methods and required configurations for adding servers to a domain. It also describes how to change the server configuration.

1. Overview

In JEUS, you can use the console tool to change server configurations. If applications that run on the server engine do not require security authentication and authorization checks, the security functions should be disabled on JEUS.

In addition, tuning of the sub-components must be checked separately. For more information, refer to the relevant chapter for each component.

2. Adding Servers

This section describes how to add servers to a domain by using the console tool. It also describes the minimum required configurations for adding a server. For more information, refer to Server Configuration.

2.1. Using the Console Tool

A server can be added through the add-server command in the console tool. Since only some configurations can be added through this command, other commands must be used to add additional configurations after the server has been added. To change the engine configuration, use the web engine, EJB engine, and JMS engine commands.

In JEUS Reference Guide, see Web Engine Commands for information about commands to modify web engine settings, EJB Engine Commands for commands to modify EJB engine settings, and JMS Engine Commands for commands to modify JMS engine settings.

The following is an example of adding a server using jeusadmin.

[MASTER]domain1.adminServer>server-info
Information about Domain (domain1)
================================================================================
+--------+---------+-----+-----+-----+-----------+--------+-----------+--------+
| Server |  Status |Node | PID | Clu |   Latest  |  Need  |   Listen  |Running |
|        |         |Name |     |ster |Start Time |   to   |   Ports   |Engines |
|        |         |     |     |     |     /     |Restart |           |        |
|        |         |     |     |     | Shutdown  |        |           |        |
|        |         |     |     |     |   Time    |        |           |        |
+--------+---------+-----+-----+-----+-----------+--------+-----------+--------+
| adminS | RUNNING | nod | 572 | N/A |2024-09-25 | false  | base-0.0. | jms,   |
|erver   |(00:18:2 |e1   |02   |     |(Thu) PM   |        |0.0:9736   |web, ejb|
|(*)     |0)       |     |     |     |01:28:24   |        | http-serv |        |
|        |         |     |     |     |KST        |        |er-0.0.0.0 |        |
|        |         |     |     |     |           |        |:8088      |        |
+--------+---------+-----+-----+-----+-----------+--------+-----------+--------+
| server1| RUNNING | nod | 589 | N/A |2024-09-25 | false  | base-0.0. | jms,   |
|        |(00:00:0 |e1   |25   |     |(Thu) PM   |        |0.0:9836   |web, ejb|
|        |8)       |     |     |     |01:46:36   |        | http-serv |        |
|        |         |     |     |     |KST        |        |er-0.0.0.0 |        |
|        |         |     |     |     |           |        |:8188      |        |
+--------+---------+-----+-----+-----+-----------+--------+-----------+--------+
================================================================================


[MASTER]domain1.adminServer>add-server server2 -addr 192.168.15.59 -port 9936 -node node1 -jvm "-Xmx512m -XX:MaxPermSize=128m"
Successfully performed the ADD operation for server (server2).
 NOTICE : base-addr [192.168.15.59] base-port [9936] http-port [8088]
Check the results using "list-servers or add-server".

[MASTER]domain1.adminServer>modify-system-thread-pool server2 -max 200
Successfully performed the MODIFY operation for the system thread pool of the server (server2), but all changes were non-dynamic. They will be applied after restarting.
Check the results using "modify-system-thread-pool server2 or show-system-thread-pool server2".

[MASTER]domain1.adminServer>server-info
Information about Domain (domain1)
================================================================================
+--------+---------+-----+-----+-----+-----------+--------+-----------+--------+
| Server |  Status |Node | PID | Clu |   Latest  |  Need  |   Listen  |Running |
|        |         |Name |     |ster |Start Time |   to   |   Ports   |Engines |
|        |         |     |     |     |     /     |Restart |           |        |
|        |         |     |     |     | Shutdown  |        |           |        |
|        |         |     |     |     |   Time    |        |           |        |
+--------+---------+-----+-----+-----+-----------+--------+-----------+--------+
| adminS | RUNNING | nod | 572 | N/A |2024-09-25 | false  | base-0.0. | jms,   |
|erver   |(00:38:1 |e1   |02   |     |(Thu) PM   |        |0.0:9736   |web, ejb|
|(*)     |1)       |     |     |     |01:28:24   |        | http-serv |        |
|        |         |     |     |     |KST        |        |er-0.0.0.0 |        |
|        |         |     |     |     |           |        |:8088      |        |
+--------+---------+-----+-----+-----+-----------+--------+-----------+--------+
| server1| RUNNING | nod | 589 | N/A |2024-09-25 | false  | base-0.0. | jms,   |
|        |(00:19:5 |e1   |25   |     |(Thu) PM   |        |0.0:9836   |web, ejb|
|        |9)       |     |     |     |01:46:36   |        | http-serv |        |
|        |         |     |     |     |KST        |        |er-0.0.0.0 |        |
|        |         |     |     |     |           |        |:8188      |        |
+--------+---------+-----+-----+-----+-----------+--------+-----------+--------+
| server2| SHUTDOWN| nod | N/A | N/A |2024-09-25 | N/A    | N/A       | N/A    |
|        |         |e1   |     |     |(Thu) PM   |        |           |        |
|        |         |     |     |     |02:04:50   |        |           |        |
|        |         |     |     |     |KST        |        |           |        |
+--------+---------+-----+-----+-----+-----------+--------+-----------+--------+
===============================================================================

3. Server Configuration

You can change server configuration using the console tool in JEUS.

3.1. Environment Variable Configuration

This section describes the environment variables necessary for the operation of various console tools provided by the server and JEUS. Environment variables cannot be configured by using console tools.

The environment variables required for JEUS operation are automatically set as default values in the JEUS_HOME/bin/jeus.properties file for UNIX during the installation process. The files are written in a shell script supported by the OS. If necessary, the user can modify the file to add or edit environment variables.

The following describes the key environment variables used in JEUS.

Environment Variable Description

JEUS_HOME

JEUS installation directory. (Example: /home/jeus)

JEUS_LIBPATH

JEUS library file path. (Example: /home/jeus/lib/system)

VM_TYPE

Virtual machine type. (Example: hotspot or old)

JEUS_USERNAME

Administrator account ID.

JEUS_PASSWORD

Administrator account password.

JAVA_HOME

JDK installation directory. (Example: /usr/jdk17)

JAVA_ARGS

JDK parameters.

JAVA_VENDOR

JDK vendor. (Example: Sun, IBM, or HP)

The environment variables specified in jeus.properties apply to all servers and tools that reference the script.

To specify different environment variables for each server, proceed as follows:

  1. Create an environment variable file or a shell script file in the following path.

    JEUS_HOME/bin/<DOMAIN_NAME>.<SERVER_NAME>.properties

  2. Modify the file created in step 1 to set environment variables by referring to the jeus.properties or jeus.properties.cmd file. When specifying an environment variable, remove the comment prefix ('#') before it.

    The following is a sample environment variable file.

    ###############################################################################
# This part is for booting JEUS automatically.                                #
# BE CAREFUL!! THIS IS ONLY FOR TEST AND DEVELOPMENT ENVIRONMENT.             #
###############################################################################

# Set up administrator name
# JEUS_USERNAME=

# Set up administrator password
# JEUS_PASSWORD=

The following is an example of starting the server.

JEUS_HOME/bin$startMasterServer -server adminServer

3.2. Basic Configuration

This section describes the basic configurations. For configurations that are not described here, refer to the relevant guides.

3.2.1. Dynamically Changing Basic Configuration

Among the basic settings of the server, Class FTP, Use MEJB, and Log Stdout To Raw Format can be changed dynamically. The settings that are applied dynamically can be checked by executing the modify-server command through the help command in the console tool. For detailed information on each command, JEUS Reference Guide.

Using the Console Tool

The following is an example of dynamically changing the basic configurations by using the console tool.

[MASTER]domain1.adminServer>modify-server server2
Shows the current configuration.
server (server2)
================================================================================
+-----------------------------------+------------------------------------------+
| Node                              | node1                                    |
| JVM Configs                       | -Xmx512m -XX:MaxPermSize=128m            |
| Action On Resource Leak           | WARNING                                  |
| Stdout to Raw Format              | true                                     |
| MEJB                              | false                                    |
| Class FTP                         | false                                    |
| Server Log Home Directory         | none                                     |
+-----------------------------------+------------------------------------------+
================================================================================

[MASTER]domain1.adminServer>modify-server server2 -logStdoutToRawFormat false -mejb true -classFtp true
Successfully performed the MODIFY operation for server (server2).
Check the results using "list-servers server2 or modify-server server2"

[MASTER]domain1.adminServer>modify-server server2
Shows the current configuration.
server (server2)
================================================================================
+-----------------------------------+------------------------------------------+
| Node                              | node1                                    |
| JVM Configs                       | -Xmx512m -XX:MaxPermSize=128m            |
| Action On Resource Leak           | WARNING                                  |
| Stdout to Raw Format              | false                                    |
| MEJB                              | true                                     |
| Class FTP                         | true                                     |
| Server Log Home Directory         | none                                     |
+-----------------------------------+------------------------------------------+
===============================================================================

3.2.2. Action On Resource Leak

The 'Action On Resource Leak' setting allows the user to know when there is resource leak and performs the configured operations by checking whether the resources that are used on the server are closed. This server function is called the invocation manager.

On the server, the invocation manager tracks the external resources like JDBC Connections and Webt Con nections that are used during a call of stateless methods such as Servlet/JSP, EJB Stateless Session Bean, and MDB. It leaves a log or returns the resource depending on the mode configured among the following three modes:

Mode Description

NoAction

No action is taken even if there are unreturned resources.

Warning

Logs about unreturned resources after the component call (default value).

Add an SMTP handler to receive email notifications.

AutoClose

Logs about unreturned resources and closes them after the component call.

Add an SMTP handler to receive email notifications.

The following is an example of changing the 'Action On Resource Leak' setting by executing the modify-server command in the console tool.

  1. Check the current server configurations that need to be modified by using the modify-server command before booting the server.

    [MASTER]domain1.adminServer>modify-server server2
Shows the current configuration.
server (server2)
================================================================================
+-----------------------------------+------------------------------------------+
| Node                              | node1                                    |
| JVM Configs                       | -Xmx512m -XX:MaxPermSize=128m            |
| Action On Resource Leak           | WARNING                                  |
| Stdout to Raw Format              | false                                    |
| MEJB                              | true                                     |
| Class FTP                         | true                                     |
| Server Log Home Directory         | none                                     |
+-----------------------------------+------------------------------------------+
===============================================================================

  2. Set the 'Action On Resource Leak' setting of server2 to 'AutoClose'.

    [MASTER]domain1.adminServer>modify-server server2 -actionOnResourceLeak AutoClose
Successfully performed the MODIFY operation for server (server2).
Check the results using "list-servers server2 or modify-server server2".

    When options are not dynamically applied, they must be modified before starting the server. If static configurations are modified at runtime, the server must be restarted to apply the changes.

  3. Verify that the modified configurations have been applied correctly by using the modify-server or list-servers command.

    [MASTER]domain1.adminServer>modify-server server2
Shows the current configuration.
server (server2)
================================================================================
+-----------------------------------+------------------------------------------+
| Node                              | node1                                    |
| JVM Configs                       | -Xmx512m -XX:MaxPermSize=128m            |
| Action On Resource Leak           | AUTO_CLOSE                               |
| Stdout to Raw Format              | false                                    |
| MEJB                              | true                                     |
| Class FTP                         | true                                     |
| Server Log Home Directory         | none                                     |
+-----------------------------------+------------------------------------------+
================================================================================

  4. Change the 'Action On Resource Leak' setting of server2 from 'AUTO_CLOSE' to 'WARNING'.

    This configuration cannot be applied while the server is running. To apply the modified configuration, restart the server.

    [MASTER]domain1.adminServer>modify-server server2 -actionOnResourceLeak Warning
Successfully performed the MODIFY operation for server (server2), but all changes were non-dynamic. They will be applied after restarting.
Check the results using "list-servers server2 or modify-server server2".

  5. Verify that the modified configurations have been applied correctly by using the modify-server or list-servers command.

    [MASTER]domain1.adminServer>modify-server server2
Shows the current configuration.
server (server2)
================================================================================
+-----------------------------------+------------------------------------------+
| Node                              | node1                                    |
| JVM Configs                       | -Xmx512m -XX:MaxPermSize=128m            |
| Action On Resource Leak           | WARNING                                  |
| Stdout to Raw Format              | false                                    |
| MEJB                              | true                                     |
| Class FTP                         | true                                     |
| Server Log Home Directory         | none                                     |
+-----------------------------------+------------------------------------------+
================================================================================

For detailed explanations of the console tool commands used above, see Server Management Commands in JEUS Reference Guide.

3.2.3. JVM Config

JVM Config is used to define parameters that are added to an individual JVM to start a server. Before starting the server with the launcher process, values specified in this section are read and added as parameters to create the server JVM. Refer to Server System Properties for the list of available JEUS parameters. The standard JVM parameters can also be configured.

JVM Config also includes JVM options that are applied to the server, system properties, and the system properties provided by JEUS. JVM memory or options are usually configured with values that are suitable for the server operating environment. For more information about JVM Config, refer to Changing JVM Configuration in Server in JEUS Domain Guide.

JVM config values cannot be applied while a server is running because they are not dynamic configurations. The server must be restarted in order to apply the changes.
Using the Console Tool

You can change the JVM configurations on the server using the modify-server, add-jvm-option, modify-jvm-option, and remove-jvm-option commands of the console tool. For more information about the commands, see Changing JVM configuration in Server in JEUS Domain Guide and Server Management Commands in JEUS Reference Guide.

The following is an example of changing the JVM configurations of a server by using the modify-server command.

  1. Check the current server configurations that need to be modified by using the modify-server command before booting the server.

    [MASTER]domain1.adminServer>modify-server server1
Shows the current configuration.
server (server1)
=====================================================================
+---------------------------------------------------------+---------+
| Node                                                    | node1   |
| Action On Resource Leak                                 | WARNING |
| Stdout to Raw Format                                    | true    |
| MEJB                                                    | false   |
| Class FTP                                               | false   |
| Server Log Home Directory                               | none    |
+---------------------------------------------------------+---------+
=====================================================================

  2. Add the JVM option to server1.

    Set the maximum heap memory of JVM to 512MB and the maximum permanent memory to 128MB.

    [MASTER]domain1.adminServer>modify-server server1 -jvmOptions "-Xmx512m -XX:MaxPermSize=128m"
Successfully performed the MODIFY operation for server (server1).
Check the results using "list-servers server1 or modify-server server1".

    Options that cannot be dynamically applied must be changed before starting the server. When the configuration is changed while the server is running, the server must be restarted to apply the changes.

  3. Check that the configurations changed by executing modify-server or list-servers have been applied correctly.

    [MASTER]domain1.adminServer>modify-server server1
Shows the current configuration.
server (server1)
================================================================================
+-----------------------------------+------------------------------------------+
| Node                              | node1                                    |
| JVM Configs                       | -Xmx512m -XX:MaxPermSize=128m            |
| Action On Resource Leak           | WARNING                                  |
| Stdout to Raw Format              | true                                     |
| MEJB                              | false                                    |
| Class FTP                         | false                                    |
| Server Log Home Directory         | none                                     |
+-----------------------------------+------------------------------------------+
================================================================================

  4. Add the JVM option to server1.

    An option that creates a Heap Dump file has been added for when OutOfMemoryError occurs on the server. Since this configuration cannot be applied to the server while the server is running, the server must be restarted to apply the changes.

    [MASTER]domain1.adminServer>modify-server server1 -jvmOptions "-XX:+HeapDumpOnOutOfMemoryError"
Successfully performed the MODIFY operation for server (server1).
Check the results using "list-servers server1 or modify-server server1".

  5. Verify that the modified configurations have been applied correctly by using the modify-server or list-servers command.

    [MASTER]domain1.adminServer>modify-server server1
Shows the current configuration.
server (server1)
================================================================================
+---------------------------+--------------------------------------------------+
| Node                      | node1                                            |
+---------------------------+--------------------------------------------------+
| JVM Configs               | -Xmx512m -XX:MaxPermSize=128m,                   |
|                           |-XX:+HeapDumpOnOutOfMemoryError                   |
+---------------------------+--------------------------------------------------+
| Action On Resource Leak   | WARNING                                          |
+---------------------------+--------------------------------------------------+
| Stdout to Raw Format      | true                                             |
+---------------------------+--------------------------------------------------+
| MEJB                      | false                                            |
+---------------------------+--------------------------------------------------+
| Class FTP                 | false                                            |
+---------------------------+--------------------------------------------------+
| Server Log Home Directory | none                                             |
+---------------------------+--------------------------------------------------+
================================================================================

3.2.4. Classpath

To add the classpath to the server, you need to change the configuration in domain.xml.

<server>
    ...
    <user-interceptor>
        <jeus-classloader-append-class-path>/home/jeus/lib/mylib.jar</jeus-classloader-append-class-path>
        <jeus-classloader-append-dirs>/home/jeus/lib/append</jeus-classloader-append-dirs>
        <boot-classloader-append-class-path>/home/jeus/boot/classes:/home/jeus/boot/a.jar</boot-classloader-append-class-path>
    </user-interceptor>
</server>

The following describes each setting item. If you have multiple items to add to the classpath, separate each item using a path separator.

Item Description

jeus-classloader-append-class-path

Specifies items to add to the class path of the JEUS top-level class loader (JEUS Root Classloader).

jeus-classloader-append-dirs

Adds all classpath entries belonging to the specified directory to the classpath of the JEUS top-level classloader (JEUS Root Classloader).

boot-classloader-append-class-path

Specifies items to add to the system classloader classpath of the server JVM.

3.3. Listener Configuration

This section describes the network listener configuration that is used on a server.

The network listener configuration is referenced by system services or various types of engines. Since port-integrated services are applied to this listener, it can be shared and used by different services or engines. As a simplified example, a basic listener can be used to provide all services.

Since this configuration cannot be applied to the server while the server is running, the server must be restarted to apply the changed configuration.
Using the Console Tool

You can set a default listener using the add-listener command in jeusadmin.

[MASTER]domain1.adminServer>add-listener -server server1 -name TestListener -addr 192.168.14.145 -port 8188
Executed successfully, but some configurations were not applied dynamically. It might be necessary to restart the server.
Check the result using 'list-server-listeners -server server1 -name TestListener.

3.4. Thread Pool Configuration

This section describes how to configure common thread pools used on a server.

If the services used on a server are not configured with a dedicated thread pool, then they all use the common thread pool. The transaction service, JDNI service, and scheduler service use the common thread pool. These services can either use the common thread pool or a dedicated thread pool depending on the configuration. If the common thread pool is used, the allowed minimum number of threads for use can be assigned in advance.

The engine that handles requests from applications does not use a common thread pool. For more information about how to use a dedicated thread pool for a service, refer to JNDI Naming Server, Transaction Manager, and JEUS Scheduler Guide.
Using the Console Tool

This section shows how to check and modify a common thread pool by using the console tool.

For more information about the commands used in the examples, see Thread Management Commands in JEUS Reference Guide. For details on how to configure the thread pool dedicated to a service, refer to relevant documentation of each service.

The following is an example of changing the 'Max' from 100 to 200 and 'Keep Alive Time' from 5 minutes to 10 minutes for the thread pool.

[MASTER]domain1.adminServer>show-system-thread-pool server1
Shows the current configuration.
the system thread pool of the server (server1)
================================================================================
+---------------------------------------------------------+--------------------+
| Min                                                     | 0                  |
| Max                                                     | 100                |
| Keep-Alive Time                                         | 300000             |
| Queue Size                                              | 4096               |
| Max Stuck Thread Time                                   | 3600000            |
| Action On Stuck Thread                                  | IGNORE_AND_REPLACE |
| Stuck Thread Check Period                               | 300000             |
| Reserved Threads for the Service transaction            | 0                  |
| Reserved Threads for the Service namingserver           | 0                  |
+---------------------------------------------------------+--------------------+
================================================================================

[MASTER]domain1.adminServer>modify-system-thread-pool server1 -max 200 -keep 600000
Successfully performed the MODIFY operation for the system thread pool of the server (server1), but all changes were non-dynamic. They will be applied after restarting.
Check the results using "modify-system-thread-pool server1 or show-system-thread-pool server1".

[MASTER]domain1.adminServer>show-system-thread-pool server1
Shows the current configuration.
the system thread pool of the server (server1)
================================================================================
+---------------------------------------------------------+--------------------+
| Min                                                     | 0                  |
| Max                                                     | 200                |
| Keep-Alive Time                                         | 600000             |
| Queue Size                                              | 4096               |
| Max Stuck Thread Time                                   | 3600000            |
| Action On Stuck Thread                                  | IGNORE_AND_REPLACE |
| Stuck Thread Check Period                               | 300000             |
| Reserved Threads for the Service transaction            | 0                  |
| Reserved Threads for the Service namingserver           | 0                  |
+---------------------------------------------------------+--------------------+
================================================================================

The following is an example of configuring the thread to be preallocated in the common thread pool of the JNDI service.

[MASTER]domain1.adminServer>show-system-thread-pool server1
Shows the current configuration.
the system thread pool of the server (server1)
================================================================================
+---------------------------------------------------------+--------------------+
| Min                                                     | 0                  |
| Max                                                     | 200                |
| Keep-Alive Time                                         | 600000             |
| Queue Size                                              | 4096               |
| Max Stuck Thread Time                                   | 3600000            |
| Action On Stuck Thread                                  | IGNORE_AND_REPLACE |
| Stuck Thread Check Period                               | 300000             |
| Reserved Threads for the Service transaction            | 0                  |
| Reserved Threads for the Service namingserver           | 0                  |
+---------------------------------------------------------+--------------------+
================================================================================

[MASTER]domain1.adminServer>modify-system-thread-pool server1 -service namingserver -r 10
Successfully performed the MODIFY operation for The namingserver thread pool of the server (server1)., but all changes were non-dynamic. They will be applied after restarting.
Check the results using "show-system-thread-pool server1 -service namingserver or modify-system-thread-pool server1 -service namingserver".

[MASTER]domain1.adminServer>show-system-thread-pool server1 -service namingserver
Shows the current configuration.
the system thread pool of the server (server1)
================================================================================
+---------------------------------------------------------+--------------------+
| Min                                                     | 0                  |
| Max                                                     | 200                |
| Keep-Alive Time                                         | 600000             |
| Queue Size                                              | 4096               |
| Max Stuck Thread Time                                   | 3600000            |
| Action On Stuck Thread                                  | IGNORE_AND_REPLACE |
| Stuck Thread Check Period                               | 300000             |
| Reserved Threads for the Service transaction            | 0                  |
| Reserved Threads for the Service namingserver           | 10                 |
+---------------------------------------------------------+--------------------+
================================================================================

[MASTER]domain1.adminServer>modify-system-thread-pool server1 -service namingserver
Shows the current configuration.
The namingserver thread pool of the server (server1).
================================================================================
+----------------------------------------------------------------------+-------+
| Reserved Threads for the Service namingserver                        | 10    |
+----------------------------------------------------------------------+-------+
================================================================================

3.5. Lifecycle Invocation Configuration

JEUS offers Lifecycle Invocation to allow users to perform tasks in accordance with the server lifecycle. The server invokes the user-configured event when the computer starts up or shuts down.

If you change the class name while the server is running, the server must be restarted to apply the changes. Other invocation settings are applied dynamically.

The following is an example of registering a typical Java class for Lifecycle Invocation.

Class for Lifecycle Invocation: <LifeCycleTester.java>
package lifecycle;

public class LifeCycleTester {
    public void boot() {
        System.out.println("Boot");
        // do somethig
    }

    public void beforeDeploy() {
        System.out.println("Before Deploy");
        // do somethig
    }

    public void afterDeploy() {
        System.out.println("After Deploy");
        // do somethig
    }

    public void ready() {
        System.out.println("Ready");
        // do somethig
        try {
            System.out.println("Sleeping for 15 seconds ....");
            Thread.sleep(15000L);
        } catch (Exception e) {
            //ignored
        }
    }

    public void beforeUndeploy() {
        System.out.println("Before Undeploy");
        // do somethig
    }

    public void afterUndeploy() {
        System.out.println("After Undeploy");
        // do somethig
    }
}
Using the Console Tool

The following describes the process of configuring the Lifecycle Invocation class of the server by using the previous example.

In the console tool, you can add a Lifecycle Invocation of the server by using the add-lifecycle-invocation command, and add the library reference and Invocation with the add-invocation-library and add-invocation commands. For detailed information, see add-lifecycle-invocation, add-invocation-library, and add-invocation in JEUS Reference Guide.

[MASTER]domain1.adminServer>add-lifecycle-invocation lifecycle.LifeCycleTester -s adminServer -m boot -type BOOT
Successfully performed the ADD operation for Lifecycle Invocation Class [lifecycle.LifeCycleTester] and Invocation [boot](Invocation ID = 0), but all changes were non-dynamic. They will be applied after restarting.
Check the results using "list-lifecycle-invocations".
[MASTER]domain1.adminServer>list-lifecycle-invocations
List of Lifecycle invocations
================================================================================
+---------------+-------------------------------+-----------------+------------+
|     Target    |   Lifecycle Invocation Class  |    Invocation   | Invocation |
|               |                               |   Library Ref   |            |
+---------------+-------------------------------+-----------------+------------+
| [Server]admin | test.lifecycle.invocation.Lif | lib1            | [1]boot    |
|Server         |eCycleInvocation               |                 |            |
+---------------+-------------------------------+-----------------+------------+
| [Server]admin | lifecycle.LifeCycleTester     |                 | [0]boot    |
|Server         |                               |                 |            |
+---------------+-------------------------------+-----------------+------------+
================================================================================
Use the "lifecycle-invocation-info" command for more information about Lifecycle invocation.

3.6. Resource Reference Configuration

Configure the common mapping information for the resources used by the applications on the server.

The names of the resources that are used in the applications are registered in the JNDI storage of the server where each application is serviced. When resource mapping is configured, regardless of the registered name, the applications can always use the resource by using the same name.

When a server is in a cluster, the value configured in the cluster is applied first to the resource reference setting.

You can configure resource references by editing domain.xml as follows:

<server>
    <name>server1</name>
    ...
    <res-ref>
        <jndi-info>
            <ref-name>/jdbc/DB1</ref-name>
            <export-name>db1</export-name>
        </jndi-info>
    </res-ref>
</server>

4. Server Template Configuration

Common configurations of the servers to be used when creating a cluster can be stored as a server template. By doing so, multiple servers with a common configuration can be automatically created when creating a cluster, which allows for easy creation of a server cluster environment.

Using the Console Tool

A server template can be added by using the console tool. Add a server template by using the add-server-template command, and then configure detailed items via various options. For more information about add-server-template, refer to add-server-template in JEUS Reference Guide.

[MASTER]domain1.adminServer>add-server-template template1 -m true
Successfully performed the ADD operation for server template (template1).
 NOTICE : base-addr [0.0.0.0] base-port [9736] http-port [8088]
Check the results using "list-servers or show-server-template or add-server-template".

[MASTER]domain1.adminServer>show-server-template
Shows the current configuration.
Server template list
=============================================================
+-----------------------------------------------+-----------+
| server templates                              | template1 |
+-----------------------------------------------+-----------+
============================================================