Installing and Uninstalling JEUS on UNIX
This chapter describes how to install and uninstall JEUS.
1. Overview
Follow these steps to install/uninstall JEUS on UNIX/Linux in console mode.
The following are the steps for installing JEUS in console mode.
-
Install JDK 8, 11 or 17.
-
Install JEUS. (Copy files)
-
Verify the installation.
-
Verify that JEUS starts.
-
Configure and verify the environment variables.
-
|
2. Installing
This section describes how to install JEUS in console mode.
This section describes how to install JEUS in console mode (command line). First, execute the console installer.
The following are the steps for installing JEUS in console mode.
-
Insert and mount the installation CD. Go to the directory where jeus9000_unix_generic_ko.bin exists.
-
Open a console window and execute the following command to grant execution permissions for jeus9000_unix_generic_ko.bin.
[was@localhost jeus]$ chmod u+x jeus9000_unix_generic_ko.bin
-
Enter the following command in the console and press <Enter>.
[jeususer@matrix jeus]$ ./jeus9000_unix_generic_ko.bin Preparing to install Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... Launching installer... =============================================================================== JEUS 9 (created with InstallAnywhere) ------------------------------------------------------------------------------- Preparing CONSOLE Mode Installation...
-
The JEUS License Agreement appears.
=============================================================================== License Agreement ----------------- Installation and Use of JEUS 9 Requires Acceptance of the Following License Agreement: JEUS (Java Enterprise User Solution) Release JEUS 9 TmaxSoft Co., Ltd. (hereafter, TmaxSoft) End-User License Agreement Product : JEUS This is a legal agreement between you (either an individual or an company) and TmaxSoft, Incorporated. By opening the sealed software package and/or by using the software, you agree to be bound by the terms of this agreement. TmaxSoft License 1. Grant of License: This TmaxSoft License Agreement ("License") permits you to use one copy of the TmaxSoft product JEUS, on any single computer, provided the software is in use on only one computer at any one time. If this package is a license pack, you may make and use additional copies of the software up to the number of licensed copies authorized. If you have multiple licenses for the software, then at any time you may have as many copies of the software in use as you have licenses. The software is "in use" on a computer when it is loaded into the temporary memory (i.e., RAM) or installed into the permanent memory (e.g., hard disk, CD-ROM, or other storage devices) of that computer, except that a copy installed on a network server for the sole purpose of distribution to other computers is not "in use". If the anticipated number of users of the software will exceed the number of applicable licenses, then you must have a reasonable -
To read the remainder of the JEUS license agreement, press <ENTER>.
PRESS <ENTER> TO CONTINUE: mechanism or process in place to ensure that the number of persons using the software concurrently does not exceed the number of licenses. 2. Copyright: The software (including any images, "applets," photographs, animations, video, audio, music and text incorporated into the software) is owned by TmaxSoft or its suppliers and international treaty provisions. Therefore, you must treat the software like any other copyrighted materials (e.g., a book or musical recording) except that you may either (a) make one copy of the software solely for backup or archival purposes, or (b) transfer the software to a single hard disk provided you keep the original solely for backup or archival purposes. You may not copy the printed materials accompanying the software, nor print copies of any user documentation provided in "online" or electronic form. 3. Other restrictions: This license is your proof of license to exercise the rights granted herein and must be retained by you. You may not rent, lease, or transfer your rights under this license on a permanent basis provided you transfer this license, the software, and all accompanying printed materials, retain no copies, and the recipient agrees to the terms of this license. You may not reverse engine, decompile, or disassemble the software, except to the extent that the foregoing restriction is expressly prohibited by applicable law.
-
Accept or decline the license agreement. Enter 'y' to accept or 'n' to decline the agreement, and then press <ENTER>.
PRESS <ENTER> TO CONTINUE: DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT? (Y/N): Y
-
Choose the platform on which to install JEUS.
=============================================================================== Choose Platform --------------- Choose the operating system and architecture : 1)AIX 5.x, 6.x, 7.x PowerPC 2)Linux x64 Quit) Quit Installer Choose Current System (Default: 2):
-
Choose the installation folder. Use the default path by pressing <ENTER>, or enter another path.
=============================================================================== Installation Folder ------------------- Enter the installation folder. Default Install Folder: /home/jeus ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT : -
Enter the JDK path. If <ENTER> is pressed without specifying the path, the default JDK path will be used. Enter another path, if desired.
=============================================================================== Enter the JDK path. ------------------- Enter the JDK path: Enter the JDK path (Default: /home/jdk-17.0.2):
-
Choose the installation type. Choose one of Master Server and Managed Server. The default is Master Server.
=============================================================================== Installation type ----------------- Please choose the Install Set to be installed by this installer. ->1- Master Server 2- Managed Server ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS <ENTER> TO ACCEPT THE DEFAULT :The following describes each installation type.
Item Description Master Server
Installs Master Server. Master Server manages Managed Servers.
Managed Server
Installs Managed Server.
-
In case of choosing Master Server in the step 10, choose an installation mode. The default is Production Mode.
=============================================================================== Installation Mode ----------------- * Production Mode. - Disables JEUS Hot Swap. - Disables Automatic Reloading. - Displays a warning message and recommends using a full license if a demo license is used. * Development Mode. - Enables JEUS Hot Swap. - Enables Automatic Reloading. ->1- Production Mode 2- Development Mode 3- Cancel ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT:The following describes each installation type.
Item Description Production Mode
Install JEUS in Production Mode. JEUS Hot Swap and Automatic Reloading are disabled. A warning message is displayed when a demo license is used.
Development Mode
Install JEUS in Development Mode. JEUS Hot Swap and Automatic Reloading are enabled.
-
In case of choosing Master Server in the step 10, enter the domain name.
=============================================================================== input JEUS Environments :: JEUS Domain Name ------------------------------------------- Enter the - JEUS Domain Name - Enter alphanumeric characters (case-sensitive). Domain Name (Default: jeus_domain):
-
In case of choosing Master Server in the step 10, enter the JEUS administrator password. This password is used for the account, "administrator".
=============================================================================== Password Input -------------- Enter the Password for the administrator account. Input Password:
Enter the password carefully. It is saved in memory and required to start JEUS.
-
Check the installation summary. Press <ENTER> to start the installation.
=============================================================================== Pre-Installation Summary ------------------------ Review the Following Before Continuing: Product Name: JEUS 9 Install Folder: /home/jeus Disk Space Information (for Installation Target): Required: 840,921,580 Bytes Available: 549,948,723,200 Bytes PRESS <ENTER> TO CONTINUE: -
Monitor the installation progress.
=============================================================================== Installing... ------------- [==================|==================|==================|==================] [------------------|---------------
-
Confirm that the installation is completed successfully.
=============================================================================== Installation Complete --------------------- JEUS 9 has been successfully installed to: /home/jeus PRESS <ENTER> TO EXIT THE INSTALLER:
3. Verifying Installation
After installing JEUS, you need to configure the environment variables and start JEUS to verify that it has been installed properly. Verify the following directory structure before setting the environment variables.
3.1. Directory Structure
The following is the directory structre of the installed JEUS.
{JEUS_HOME}
|-- bin
| |--[01]startMasterServer
| |--[01]startManagedServer
| |--[01]stopServer
| |--[01]jeusadmin
|--derby
|--docs
|--lib
| |--shared
| |--[X]libraries.xml
|--license
|--setup
|--templates
|--samples
|--webserver
|--domains
|--<domain_name>
|--.applications
|--.deploymentplans
|--.libraries
|--bin
|--config
|--lib
| |--application
|--servers
|--<server_name>
|--.workspace
| |--deployed
| |--tmp
| |--web-nio
| |--tmlog
|--bin
|--lib
| |--application
|--logs
* Legend
- [01]: binary or executable file
- [X] : XML document
- [J] : JAR file
- [T] : Text file
- [C] : Class file
- [V] : java source file
- [DD] : deployment descriptor
The following describes each directory and file.
- {JEUS_HOME}
-
The root directory of JEUS. The actual directory name and location are selected during installation.
- bin
-
Contains the scripts to start and stop servers. The scripts are startMasterServer, startManagedServer, and stopServer. This directory also contains the executable files including the JEUS console tool 'jeusadmin'.
- derby
-
Contains Apache Derby, which helps users build sample applications or perform tests.
- docs
-
Contains Javadoc documentations for the APIs provided by JEUS.
- lib
-
Contains the libraries used to start JEUS. Users only need to access the shared directory.
Directory Description shared
Contains the libraries used by applications. Library information must be added to libraries.xml in order to use the libraries in the shared directory. Reference information about the library must also be specified in the JEUS deployment descriptor of the application that will use the library.
For more information about shared libraries, refer to Shared Libraries in JEUS Applications & Deployment Guide.
- license
-
Contains JEUS license files that are needed to execute JEUS.
- setup
-
Contains the files needed to set up the environment to use JEUS after JEUS has been installed.
- templates
-
Contains configuration file templates.
- samples
-
Contains example files for JEUS.
- webserver
-
Directory where the JEUS Web server is installed during the JEUS installation. For details, refer to JEUS Web Engine Guide.
- domains
-
Each domain contains a file named nodes.xml that contains the information about the nodes used from DOMAIN_HOME and JEUS_HOME.
DOMAIN_HOME contains the following files and directories:
-
.applications
Contains application files managed by the domain.
These can only be added or deleted by using the install-application and uninstall-application commands. This is a JEUS system directory with restricted user access. For detailed information about each command, refer to install-application and uninstall-application in JEUS Reference Guide.
-
.deploymentplans
Contains deployment plan files managed by the domain.
These can only be added or deleted by using the install-deployment-plan and uninstall-deployment-plan commands. This is a JEUS system directory with restricted user access. For detailed information about each command, refer to install-deployment-plan and uninstall-deployment-plan in JEUS Reference Guide.
-
.libraries
Contains library files managed by the domain.
These can only be added or deleted by using the install-library and uninstall-library commands. This is a JEUS system directory with restricted user access. For detailed information about each command, refer to install-library and uninstall-library in JEUS Reference Guide.
-
bin
Contains the scripts to start or stop the Master Server and Managed Server of the domain. The functions of the scripts are the same as startMasterServer, startManagedServer, and stopServer scripts in the 'JEUS_HOME/bin' directory, except that the users don’t need to specify the file names.
-
config
Contains backup files that store changes to domain.xml, a domain configuration file. For detailed information about domain configurations, refer to Changing Domain Settings in JEUS Domain Guide.
Directory Description security
-
SYSTEM_DOMAIN: Contains security domain files, including accounts.xml and policies.xml. Each XML file can be dynamically modified by using jeusadmin. For detailed information about security domain configurations, refer to Configuring the Security System Domain in JEUS Security Guide.
-
security-domains.xml: Contains security domain configuration for JEUS.
-
security.key: Contains the keys for symmetric key encryption. They are created when 'JEUS_HOME/bin/encryption' is executed. For detailed information about the security.key file, refer to Configuring Password Security in JEUS Security Guide.
-
policy: Contains the Java permissions configuration file. This is used by Java SE Security Manager, separate from the JEUS security system.
servlet
-
web.xml: This file is used when a web module does not have a separate web.xml file. By default, the file is empty.
-
webcommon.xml: Settings that apply to all Web modules of the Web engines in the domain. For detailed information about the file, refer to Directory Structure in JEUS Web Engine Guide.
-
-
lib/application
Contains the shared application libraries for the domain.
If a library conflicts with an application library in the SERVER_HOME directory, it is overridden by 'SERVER_HOME/lib/application' and a warning message appears. For detailed information about the 'lib/application' directory, refer to lib/application Directory in JEUS Applications & Deployment Guide.
-
servers
Create the SERVER_HOME directory by using the server name in this directory. For detailed information about the directory structure, refer to Server Directory Structure in JEUS Server Guide.
Directory Description .workspace
Contains workspaces used by each JEUS server. Cannot be modified by the user.
bin
Contains scripts for starting and stopping the server. The scripts execute the same functions as those in 'JEUS_HOME/bin', but they do not require the domain and server names.
-
Master Server: uses startMasterServer and stopServer.
-
Managed Server: uses startManagedServer and stopserver.
lib/application
Contains application libraries for the server. This directory takes precedence over the domain-level library directory (DOMAIN_HOME/lib/application). If a library conflicts with an application library in the DOMAIN_HOME/lib/application, the file in this directory overrides that in DOMAIN_HOME and a warning message appears.
For detailed information about lib/application, refer to lib/application Directory in JEUS Applications & Deployment Guide.
logs
Includes launcher logs, server logs, and access log files. For detailed information, refer to Logging in JEUS Server Guide.
-
-
3.2. Environment Configurations
The environment variables must be configured in order to use JEUS. Some environment variables are set during the installation, but they can be changed if needed. The PATH variable is set in the .profile/.cshrc file and other environment variables are set in the $JEUS_HOME/bin/jeus.peoperties file. If you want to set different environment variables for each server, create a $JEUS_HOME/bin/<SERVER_NAME>.properties file. When starting the server, use the [-server] option to specify the server name.
The following describes each environment variable.
| Environment Variable | Description |
|---|---|
PATH |
System path. It must include:
|
JEUS_HOME |
JEUS installation directory. (Example: /home/jeus) |
JEUS_LIBPATH |
JEUS library file path. (Example: /home/jeus/lib/system) |
VM_TYPE |
Option to use the Java HotSpot JVM. (Example: hotspot or old) |
USERNAME |
Administrator account ID. |
PASSWORD |
Administrator account password. |
JAVA_HOME |
Path to JDK. (Example: /usr/jdk17) |
ANT_HOME |
ANT installation directory. (Example: home/jeus/lib/etc/ant) |
JAVA_ARGS |
JDK parameters. |
JAVA_VENDOR |
JDK vendor. (Example: Sun, IBM, or HP) |
The 'setenv' command is used to set the JEUS_HOME variables in the console.
setenv JEUS_HOME “/home/jeus”
The following is an example of setting the system path.
setenv PATH “${PATH}:/home/jeus/bin:
/home/jeus/lib/system”
|
Since the Java executable directory (/usr/jdk17/bin) is used by JEUS, it must be added before other environment variables. |
3.3. Starting JEUS
Use the following steps to start JEUS in order to verify that JEUS has been installed properly.
-
Start the Master Server (MASTER) by entering 'startMasterServer' command at the console prompt. Default ID is 'administrator' and password is the input value during JEUS installation.
The following is how to start the Master Server (MASTER) by executing the command.
startMasterServer -u <user_name> -p <password>
Once the Master Server is started, you will see the message saying, 'Successfully started the server. The server state is now RUNNING'.
[was@localhost ~]$ startMasterServer -u administrator -p <password> *************************************************************** - JEUS Home : /home/jeus - Added Java Option : -Djeus.io.buffer.size-per-pool=81920 -Djeus.cdi.enabled=false -Djeus.jms.server.manager.produce-wait-strategy-type=blocking -Djeus.servlet.sortWebinfLibraries=name_asc *************************************************************** =============== JEUS LICENSE INFORMATION ================ == VERSION : JEUS 9 (9.0.0.0-b15) == EDITION: Enterprise (Trial License) == NOTICE: This license restricts the number of allowed clients. == Max. Number of Clients: 5 ========================================================== [2024.09.25 17:54:09][1] [launcher-1] [Config-0153] DomainConfigServiceProvider is jeus.service.descriptor.JEUSDomainDescriptorFile. This license is not appropriate for product runtime mode. Replace the license with an appropriate one. [2024.09.25 17:54:10][1] [launcher-1] [Config-0157] SecurityDomainsConfigServiceProvider is jeus.service.descriptor.SecurityDomainsDescriptorFile. [2024.09.25 17:54:10][2] [launcher-1] [Launcher-0012] Starting the server [server1] with the command /home/jdk-17.0.2/bin/java -Dserver1 -Xms1024m -Xmx1024m -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=512m -Djeus.io.buffer.size-per-pool=81920 -Djeus.cdi.enabled=false -Djeus.jms.server.manager.produce-wait-strategy-type=blocking -Djeus.servlet.sortWebinfLibraries=name_asc -server -Xbootclasspath/p:/home/jeus/lib/system/extension.jar -classpath /home/jeus/lib/system/bootstrap.jar -Djava.security.policy=/home/jeus/domains/jeus_domain/config/security/policy -Djava.library.path=/home/jeus/lib/system:/home/webtob5004_B231_0_38//lib:/home/webtob5004_B231_0_38//lib:/home/webtob5004_B231_0_38//lib: -Djava.endorsed.dirs=/home/jeus/lib/endorsed -Djeus.properties.replicate=jeus,sun.rmi,java.util,java.net -Djava.util.logging.config.file=/home/jeus/bin/logging.properties -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.util.logging.manager=jeus.util.logging.JeusLogManager -Djeus.home=/home/jeus -Djava.net.preferIPv4Stack=true -Djeus.tm.checkReg=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Djeus.domain.name=jeus_domain -Djava.naming.factory.initial=jeus.jndi.JNSContextFactory -Djava.naming.factory.url.pkgs=jeus.jndi.jns.url -Djeus.server.protectmode=false -Dis.jeus.master=true -Dsun.net.http.errorstream.enableBuffering=true -XX:+UnlockDiagnosticVMOptions -XX:+LogVMOutput -XX:LogFile=/home/jeus/domains/jeus_domain/servers/server1/logs/jvm.log jeus.server.admin.MasterServerBootstrapper -domain jeus_domain -u administrator -verbose -server server1 . [2024.09.25 17:54:10][2] [launcher-1] [Launcher-0014] The server[server1] is being started ... [2024.09.25 17:54:10][1] [server1-1] [Config-0153] DomainConfigServiceProvider is jeus.service.descriptor.JEUSDomainDescriptorFile. [2024.09.25 17:54:10][1] [server1-1] [Config-0157] SecurityDomainsConfigServiceProvider is jeus.service.descriptor.SecurityDomainsDescriptorFile. [2024.09.25 17:54:12][2] [server1-1] [SERVER-0248] The JEUS server is STARTING. [2024.09.25 17:54:12][0] [server1-1] [SERVER-0000] Version information - JEUS 9 (9.0.0.0-b15). ... Omitted [2024.09.25 17:54:13][2] [server1-1] [SERVER-0248] The JEUS server is STANDBY. [2024.09.25 17:54:13][2] [server1-1] [SERVER-0248] The JEUS server is STARTING. [2024.09.25 17:54:13][2] [server1-1] [WEB-3413] The web engine is ready to receive requests. [2024.09.25 17:54:13][2] [server1-1] [NET-0002] Beginning to listen to NonBlockingChannelAcceptor: qpsp1:8808. [2024.09.25 17:54:13][2] [server1-1] [UNIFY-0100] Listener information +------------+-------+--------------+-----------+----------------------------------------+ | Name | SSL | Address:Port | Protocol | Virtual Listener | +------------+-------+--------------+-----------+----------------------------------------+ | base | false | 0.0.0.0:9736 | VIRTUAL | ClassFTP | | | | | | SecurityServer | | | | | | JMXConnectionServer/JEUSMP_adminServer | | | | | | JMXConnectionServer/JeusMBeanServer | | | | | | TransactionManager | | | | | | JMSServiceChannel-default | | | | | | FileTransfer | | | | | | JNDI | | | | | HTTP | | +------------+-------+--------------+-----------+----------------------------------------+ | http-server| false | 0.0.0.0:8088 | ProObject | | | | | | HTTP | | +------------+-------+--------------+-----------+----------------------------------------+ ... Omitted [2024.09.25 17:54:29][2] [launcher-13] [Launcher-0034] The server[server1] initialization completed successfully[pid : 473]. [2024.09.25 17:54:29][0] [launcher-1] [Launcher-0040] Successfully started the server[server1]. The server state is now RUNNING..**
-
If an "Invalid License" message is displayed, there is a problem with the license. Obtain a license from TmaxSoft and copy it to the '$JEUS_HOME/license' directory.
-
Verify that all the steps have been completed successfully and that the environment variables have been configured correctly. In particular, check that the '/jeus/bin' directory is included in the system path so that the startMasterServer script can be executed.
-
-
Start Managed Server (MS). You can start the Managed Server by executing the 'startManagedServer' command.
-
startManagedServer command
The following shows how to start the Managed Server (MS) using the startManagedServer command.
startManagedServer -domain <domain_name> -server <server_name> -u <user_name> -p <password>
When you enter the command at the console prompt, the following message is displayed. Generally, the default ID is 'administrator' and the password is the value entered during the JEUS installation. If the JEUS MS successfully boots and starts, you will see the message, saying 'Successfully started the server. The server state is now RUNNING'.
[was@localhost ~]$ startManagedServer -domain jeus_domain -server server2 -u administrator -p <password> *************************************************************** - JEUS Home : /home/jeus - Added Java Option : -Djeus.io.buffer.size-per-pool=81920 -Djeus.cdi.enabled=false -Djeus.jms.server.manager.produce-wait-strategy-type=blocking -Djeus.servlet.sortWebinfLibraries=name_asc *************************************************************** =============== JEUS LICENSE INFORMATION ================ == VERSION : JEUS 9 (9.0.0.0-b15) == EDITION: Enterprise (Trial License) == NOTICE: This license restricts the number of allowed clients. == Max. Number of Clients: 5 ========================================================== [2024.09.25 17:55:40][2] [launcher-1] [SERVER-0201] Successfully connected to the JEUS Master Server(localhost:9736). [2024.09.25 17:55:40][2] [launcher-1] [Launcher-0058] All local configurations are up-to-date. [2024.09.25 17:55:40][1] [launcher-1] [Config-0157] SecurityDomainsConfigServiceProvider is jeus.service.descriptor.SecurityDomainsDescriptorFile. [2024.09.25 17:55:41][1] [launcher-1] [Config-0153] DomainConfigServiceProvider is jeus.service.descriptor.JEUSDomainDescriptorFile. This license is not appropriate for product runtime mode. Replace the license with an appropriate one. [2024.09.25 17:55:41][2] [launcher-1] [Launcher-0012] Starting the server [server2] with the command /home/jdk-17.0.2/bin/java -Dserver2 -Djeus.io.buffer.size-per-pool=81920 -Djeus.cdi.enabled=false -Djeus.jms.server.manager.produce-wait-strategy-type=blocking -Djeus.servlet.sortWebinfLibraries=name_asc -server -Xbootclasspath/p:/home/jeus/lib/system/extension.jar -classpath /home/jeus/lib/system/bootstrap.jar -Djava.security.policy=/home/jeus/domains/jeus_domain/config/security/policy -Djava.library.path=/home/jeus/lib/system:/home/webtob5004_B231_0_38//lib:/home/webtob5004_B231_0_38//lib: -Djava.endorsed.dirs=/home/jeus/lib/endorsed -Djeus.properties.replicate=jeus,sun.rmi,java.util,java.net -Djava.util.logging.config.file=/home/jeus/bin/logging.properties -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.util.logging.manager=jeus.util.logging.JeusLogManager -Djeus.home=/home/jeus -Djava.net.preferIPv4Stack=true -Djeus.tm.checkReg=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Djeus.domain.name=jeus_domain -Djava.naming.factory.initial=jeus.jndi.JNSContextFactory -Djava.naming.factory.url.pkgs=jeus.jndi.jns.url -Djeus.server.protectmode=false -Djeus.master.port=9736 -Djeus.master.host=localhost -Djeus.master.protocol=http -XX:+UnlockDiagnosticVMOptions -XX:+LogVMOutput -XX:LogFile=/home/jeus/domains/jeus_domain/servers/server2/logs/jvm.log jeus.server.ServerBootstrapper -domain jeus_domain -server server2 -u administrator -verbose . [2024.09.25 17:55:41][2] [launcher-1] [Launcher-0014] The server[server2] is being started ... [2024.09.25 17:55:42][1] [server2-1] [Config-0153] DomainConfigServiceProvider is jeus.service.descriptor.JEUSDomainDescriptorFile. [2024.09.25 17:55:42][1] [server2-1] [Config-0157] SecurityDomainsConfigServiceProvider is jeus.service.descriptor.SecurityDomainsDescriptorFile. [2024.09.25 17:55:43][2] [server2-1] [SERVER-0248] The JEUS server is STARTING. [2024.09.25 17:55:43][0] [server2-1] [SERVER-0000] Version information - JEUS 9 (9.0.0.0-b15). ... Omitted [2024.09.25 17:55:45][2] [server2-50] [WEB-3484] ServletContext[name=healthcheck, path=/health, ctime=Mon Sep 25 17:55:45 KST 2024, apptime=1682326357716, index=1682326357716] started successfully. [2024.09.25 17:55:45][2] [server2-50] [Deploy-0099] Successfully started the application[healthcheck, 1682326357716]. [2024.09.25 17:55:45][0] [server2-1] [SERVER-0242] Successfully started the server. [2024.09.25 17:55:45][2] [server2-1] [SERVER-0248] The JEUS server is RUNNING. [2024.09.25 17:55:45][2] [server2-1] [SERVER-0401] The elapsed time to start: 3626ms. [2024.09.25 17:55:45][2] [launcher-14] [Launcher-0034] The server[server2] initialization completed successfully[pid : 792]. [2024.09.25 17:55:45][0] [launcher-1] [Launcher-0040] Successfully started the server[server2]. The server state is now RUNNING.**
-
If an "Invalid License" message is displayed, there is a problem with the license. Obtain a license from TmaxSoft and copy it to the '$JEUS_HOME/license' directory.
-
Verify that all the steps have been completed successfully and that the environment variables have been configured correctly. In particular, check that the '/jeus/bin' directory is included in the system path so that the startManagedServer script can be executed.
-
-
-
Execute the jeusadmin command in another console window. Default ID is 'administrator' and password is the input value during JEUS installation.
[was@localhost ~]$ jeusadmin -u administrator -p <password> Attempting to connect to 127.0.0.1:9736. The connection has been established to JEUS Master Server [adminServer] in the domain [jeus_domain]. JEUS 9 Administration Tool To view help, use the 'help' command. [MASTER]jeus_domain.adminServer>
-
A message that JEUS has been started successfully will be displayed and the prompt shows that it is ready to accept user input.
-
Log in to jeusadmin at the console. The JEUS server can be controlled by using the local-start-server and local-shutdown commands of the tool. To terminate a JEUS server, enter local-shutdown command.
[MASTER]jeus_domain.adminServer>local-shutdown Executing this command affects the service. Do you want to continue? (y/n)y The server [adminServer] has been shut down successfully.
-
Enter exit to exit jeusadmin.
offline>exit
4. Uninstallation
This section explains how to uninstall JEUS in console mode.
The following describes the steps for uninstalling JEUS in console mode.
-
Execute '$JEUS_HOME/UninstallerData/Uninstall' from where JEUS is installed to remove JEUS Core and the installation directories as shown in the following.
[was@localhost ~ UninstallerData]$./Uninstall
-
JEUS will be uninstalled. When the uninstallation is complete, a message that the uninstallation is complete is displayed.
=============================================================================== JEUS 9 (created with InstallAnywhere) ------------------------------------------------------------------------------- Preparing CONSOLE Mode Uninstallation... =============================================================================== Uninstall JEUS 9 ------------------- About to uninstall... JEUS 9 This will remove features installed by InstallAnywhere. It will not remove files and folders created after the installation. PRESS <ENTER> TO CONTINUE: =============================================================================== Check JEUS process... - =============================================================================== Uninstalling... --------------- ...* * ************************* ************************* ************************* ************************ ...* * ************************* ************************* ************************* ************************ ...* * ************************* ************************* ************************* ************************ ... =============================================================================== Uninstallation Complete ----------------------- All items were successfully uninstalled.