There are two methods to install JEUS: console mode and GUI mode. In this chapter,JEUS is installed in Unix/Linux console mode and Windows GUI mode. JEUS6.0 requires JDK 5.0 Update 4 (1.5.0_04) or later to be installed and also requires at least 300M of free hard disk space.
Basic Installation (Console mode)
The following section describes how to run in a text-based shell.
1. Download the Unix/Linux version of the JEUS package from the Tmaxsoft homepage.
2. After uploading JEUS to the server to be installed, go to the location of the jeus60_unix_generic_ko.bin file.
3. Give the execution permission of the jeus60_unix_generic_ko.bin file so that the installation console installer located elsewhere can execute it.
4. chmod +x jjeus60_unix_generic_ko.bin).
5. Run jeus60_unix_generic_ko.bin from the console.
6. Check the license part that appears when running the file, and then accept the agreement.
7. Select the type of operating system.
8. Select the installation directory. Press <Enter> to use as default or enter the installation path if the user wants to change the directory.
9. Choose the install set to install JEUS.
10. Enter the location of the JDK.
11. Enter the password
12. Entering the password shows a summary of the basic information to install JEUS. Press <Enter> to complete the installation.
Setting environment variables
JEUS requires the following system environment variables. These variables are applied during the installation. The environment variable PATH is recorded in the environment variable files .profile, .cshrc, etc., and the remaining environment variables are set in the $JEUS_HOME/bin/jeus.properties file.
- By default, it is automatically added to the default shell when installing
This should contain:
JEUS library file
JEUS installation directory
The most basic port to use for JEUS (default: 9763)
JAVA2 installation directory
The following are subdirectories of the installed JEUS home directory.
Bin: Directory containing JEUS execution files
Config: Directory containing XML descriptor file, node configuration file, and security configuration file
Derby: Database used to run and test the examples
Docs: Folder containing JEUS manuals and API files
Lib: Fold for library files used by JEUS. The JEUS class library archive is included in jeus.jar
License: Folder of JEUS license file
Logs: Folder of log files
Samples: Folder of samples
Sessiondb: Folder created when using session server in JEUS
UninstallerData: Folder for uninstalling
Webhome: Deployment folder of EJB, Servlet, JSP applicaiton
Webserver: Folder for Servlet Engine listener JEUS web server folder
Workspace: Temporary folder used by JEUS. Just like the Sessiodbfolder, this folder is created after JEUS is booted more than once.
Confirming if JEUS has started
To confirm that JEUS installation is completed normally, perform the following steps.
Type “jeus” at the console prompt.
1. When the message “JEUS Manager is READY” is displayed, it indicates that JEUS Manager is properly loaded and that JEUS is in standby.
2. Run jeusadmin <node name> in another console window. Here, <node name> is the host machine name. The password for logging in can be accessed using the password specified when installing JEUS.
3. After login into the jeusadmin tool, the user can control the JEUS server with commands such as boot and down.
If the message “connect successful” is displayed, JEUS is booted properly.
When the message “all containers successfully shutdown” is displayed, JEUS is down normally.
4. After JEUS is started, check the process.
Considerations when installing JEUS
This section describes the considerations when installing JEUS.
1. An error occurs if the wrong operating system is selected.
If operating system that does not fit the characteristics of the server is selected in the step of selecting the operating system when installing JEUS, installation will not be possible.
Ex) When Linux x86 is selected on a Linux x64 device
2. When the GLIBC version is low
If the GLIBC version of the server is lower than 2.4, an error occurs during installation. The version of GBLIC can be checked by the following command.
Ex) GLIBC version is 2.3