Chapter 3. Starting JEUS Server

3.1. Overview

The following are commands used to start a JEUS server.

startDomainAdminServer starts the Domain Administrator Server (hereafter DAS).

startManagedServer starts a Managed Server (hereafter MS).

These commands execute the launcher of the corresponding server. The launcher completes preparations for starting the server and starts the server JVM. DAS is a server that manages running MSs and works as an agent to send administrator commands to the MSs.

The commands are in the following directory.

JEUS_HOME/bin/

3.2. Usage

This section describes how to start DAS and MS.

In order to manage MSs using tools, such as jeusadmin or WebAdmin, DAS must be started first.

DAS communicates with each MS that runs on a HOST machine. All servers in a domain share the following configuration file. Each server reads necessary configurations from the file and runs according to those configurations.

JEUS_HOME/domains/DOMAIN_NAME/config/domain.xml

Starting DAS

The following is the process for starting DAS using the startDomainAdminServer command.

Choose and execute the command according to the OS.
- UNIX or Linux
```
startDomainAdminServer
```
- Windows
```
startDomainAdminServer.cmd
```

Enter startDomainAdminServer with the following configurations at the command prompt.

The server can run in DEBUG mode by changing the setting in the domain.xml file. For more information, refer to "3.4. Executing JEUS Server in Debug Mode".

startDomainAdminServer [-h] 
                       [-domain <domain-name> -server <das-name>]
                       [-u <username> -p <password>] 
                       [-cachelogin]
                       [-f <filename>] 
                       [-force]
                       [-standby]
                       [-rolling]
                       [-verbose]

The following describes the command options.

Option	Description
[-h]	Displays command help information.
[-domain <domain-name>]	Domain name of DAS.
[-server <das-name>]	Name of DAS to start.
[-u <username>] [-p <password>]	Server startup account. [-u] is the administrator ID and [-p] is its password, which are required to start the server.
[-cachelogin]	Option to cache the login information entered with the [-u] and [-p] options. If cached login information exists, the user information is automatically filled. This option is not recommended. For more information, refer to "JEUS Security Guide".
[-f <filename>]	Path to the file that contains administrator login information. This can be used instead of the [-u] and [-p] options.
[-force]	Option to forcibly change the server state to RUNNING, even if all the registered applications are not in the RUNNING state.
[-standby]	Option to start the server in the STANDBY state.
[-rolling]	Internal option for Rolling Patch. This option must not be set by the user at startup.
[-verbose]	Option to display server logs on the launcher screen without terminating the launcher.

Most of the options required to start MS are similar to the options required to start DAS. MS contains the dasurl option, which is used to get the configuration file from DAS.

Starting MS

The following is the process for executing the startManagedServer command to start an MS.

Execute the following command to start the MS.
- UNIX or Linux
```
startManagedServer
```
- Windows
```
startManagedServer.cmd
```

Enter startManagedServer with the following configurations in the command prompt.

startManagedServer [-h]
                   [-domain <domain-name> -server <das-name>]
                   [-u <username> -p <password>] 
                   [-cachelogin]
                   [-f <filename>]
                   [-force]
                   [-standby]
                   [-rolling]
                   [-verbose]
                   [-dasurl <das-url>]

The following describes the command options.

Option	Description
[-h]	Displays command help information.
[-domain <domain-name>]	Domain name of DAS.
[-server <das-name>]	Name of DAS to start.
[-u <username>] [-p <password>]	Server startup account. [-u] is the administrator ID and [-p] is its password, which are required to start the server.
[-cachelogin]	Option to cache the login information entered with [-u] and [-p] options. If cached login information exists, the user information is automatically filled. This option is not recommended. For more information, refer to "JEUS Security Guide".
[-f <filename>]	Path to the file that contains administrator login information. This can be used instead of the [-u] and [-p] options.
[-force]	Option to forcibly change the server state to RUNNING, even if all registered applications are not in the RUNNING state.
[-standby]	Option to start the server in the STANDBY state.
[-rolling]	Internal option for Rolling Patch. This option must not be set by the user at startup.
[-verbose]	Option to display server logs on the launcher screen without terminating the launcher.
[-dasurl <das-url>]	URL address of the DAS that manages the domain that the MS belongs to. It is recommended to set this address to use it for getting a new configuration file from DAS.

3.3. Entering Master Password

When starting the server, the master password is required if the security.key file is encrypted with the master password through an encryption tool. The security.key file contains a symmetric encryption algorithm key. For more information about encryption tools, refer to "4.6. encryption".

When starting the server, if the security.key file is encrypted, the following console screen appears, which prompts for the master password. The master password must match to start the server.

The encryption key file is encrypted. Enter the master password.
Password>

3.4. Executing JEUS Server in Debug Mode

If a JEUS server runs in the DEBUG mode, servlets and EJB applications can be debugged using the JPDA support debugger. In order to run a JEUS server in the DEBUG mode, add the following debug option to the jvm-config file of each server.

-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8888

Use the debug port, “8888”, to run a JEUS server in the DEBUG mode. The debug port is used when JPDA debugger accesses the JVM.

Start a JEUS server with the changed configurations. Next, use the IDE (Integrated Development Environment) that supports JPDA to debug EJB and servlet applications.

The system environment variables can be set by using the jvm-config file of each server. For more information about the system environment variables used in JEUS, refer toPart I, "System Properties"."1.1. Overview" describes the "-D" option used by the JVM.

Note

The jvm-option only applies to the corresponding server.

Prev	Up	Next
Chapter 2. Command Rules	Home	Chapter 4. Console Tools

Chapter 3. Starting JEUS Server
Prev	Part II. Console Commands and Tools	Next