...
Code Block |
---|
[tmax@dev ~]$ ./jeus60_unix_generic_ko.bin Preparing to install... |
6. Check the license part that appears when running the file, and then accept the agreement.
Code Block |
---|
PRESS <ENTER> TO CONTINUE: DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT? (Y/N): Y |
7. Select the type of operating system.
Code Block |
---|
Choose Platform --------------- Choose current system ( platform-architecture ) 1)HP-UX PA-RISC 2)HP-UX ITANIUM 3)Solaris Ultra-Sparc 4)Solaris x86 5)Solaris x64 6)AIX 5.x PowerPC 7)Linux ITANIUM 8)Linux x86 9)Linux x64 Quit) Quit Installer Choose Current System (DEFAULT: 9): |
8. Select the installation directory. Press <Enter> to use as default or enter the installation path if the user wants to change the directory.
Code Block |
---|
Choose Install Folder --------------------- Where would you like to install? Default Install Folder: $HOME/jeus6 ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT : /app/was/jeus6 |
9. Choose the install set to install JEUS.
Code Block |
---|
Choose Install Set ------------------ Please choose the Install Set to be installed by this installer. ->1- Full Install 2- Typical ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS <ENTER> TO ACCEPT THE DEFAULT : |
10. Enter the location of the JDK.
Code Block |
---|
Choose JDK Folder ----------------- Please Choose a Folder: Input User JDK Folder (DEFAULT: /usr/jdk1.6.0_15): |
11. Enter the password
Code Block |
---|
Enter the Password for the administrator account. This password will be registered in JEUS as the first user. Input Password:: Confirm Password:: |
12. Entering the password shows a summary of the basic information to install JEUS. Press <Enter> to complete the installation.
Code Block |
---|
Pre-Installation Summary ------------------------ Please Review the Following Before Continuing: Product Name: JEUS6.0 Install Folder: /app/was/jeus6 Install Set Full Install Disk Space Information (for Installation Target): Required: 308,147,759 bytes Available: 45,215,862,784 bytes PRESS <ENTER> TO CONTINUE: |
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
Environment variable | Description | Setting value |
---|---|---|
PATH | System path | This should contain: |
JEUS_LIBPATH | JEUS library file | $JEUS_HOME/lib/system |
JEUS_HOME | JEUS installation directory | $HOME/jeus6/ |
JEUS_BASSPORT | The most basic port to use for JEUS (default: 9763) | 9763 |
JAVA_HOME | JAVA2 installation directory | $JAVA_HOME |
JEUS Directories
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.
Code Block |
---|
[tmax@dev ~]$ jeus *************************************************************** - JEUS Home : /app/was/jeus6 - JEUS Base Port : 9736 - Java Vendor : Sun - Added Java Option : *************************************************************** . . . [2014.10.22 11:01:21][0][b396] [dev-1] [MGR-0248] JEUS Manager is READY |
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.
Code Block |
---|
[tmax@dev jeus6]$ jeusadmin dev Login name>administrator Password> JEUS 6.0 (Fix#9) administration tool dev> |
3. After login into the jeusadmin tool, the user can control the JEUS server with commands such as boot and down.
Code Block |
---|
dev>boot dev boot done dev_container1 dev> [2014.10.27 14:36:15][2][b396] [dev-18] [MGR-0205] command : boot() [2014.10.27 14:36:15][2][b396] [dev-18] [MGR-0567] trying to start engine container[dev_container1] [2014.10.27 14:36:15][2][b396] [dev-18] [MGR-0128] start engine container[dev_container1] with command … [2014.10.27 14:36:36][2][b396] [container1-83] [WEB-3384] WebtoB connection[unix(hth-0:9900:139)] established [2014.10.27 14:36:36][2][b396] [container1-84] [WEB-3384] WebtoB connection[unix(hth-0:9900:138)] established [2014.10.27 14:36:36][2][b396] [container1-85] [WEB-3384] WebtoB connection[unix(hth-0:9900:140)] established [2014.10.27 14:36:36][2][b396] [container1-87] [WEB-3384] WebtoB connection[unix(hth-0:9900:135)] established [2014.10.27 14:36:36][2][b396] [container1-86] [WEB-3384] WebtoB connection[unix(hth-0:9900:141)] established [2014.10.27 14:36:36][0][b396] [dev-67] [MGR-0303] engine container[dev_container1] initialization successfully done [pid : 1891] |
If the message “connect successful” is displayed, JEUS is booted properly.
Code Block |
---|
dev>down Do you really want to shutdown the node [dev]? (y : n):>y The JEUS node [dev] is down. dev> [2014.10.27 14:38:17][0][b396] [dev-18] [MGR-0207] command : down() [2014.10.27 14:38:17][2][b396] [dev-18] [MGR-0261] shutting down the jeus server ... [2014.10.27 14:38:17][2][b396] [dev-18] [MGR-0566] attempt to shutdown all running container [2014.10.27 14:38:17][2][b396] [dev-18] [MGR-0568] trying to shutdown container dev_container1 [2014.10.27 14:38:17][2][b396] [container1-18] [MGR-0103] engine container[dev_container1] is STOPPING … [2014.10.27 14:38:17][2][b396] [container1-18] [JMXR-0102] JMXConnector is shutting down [2014.10.27 14:38:17][1][b396] [container1-18] [Network-1023] OnePortServer virtual listener /JEUSMP_dev_container1 unregistered [2014.10.27 14:38:17][1][b396] [container1-11] [Network-1009] OnePortServer unknown virtual listener(/JEUSMP_dev_container1). socket discarded. [2014.10.27 14:38:17][2][b396] [container1-18] [MGR-0097] Container security manager uninstalled [2014.10.27 14:38:17][2][b396] [container1-18] [JNDI.Local-0012] Successfully stopped. (ID 127.0.0.1:9736(JNSServer)) [2014.10.27 14:38:17][2][b396] [container1-18] [MGR-0103] engine container[dev_container1] is SHUTDOWN [2014.10.27 14:38:17][0][b396] [container1-1] [MGR-0099] container dev_container1 shutdown [2014.10.27 14:38:17][0][b396] [container1-9] [MGR-0565] JVM process is shutting down [2014.10.27 14:38:17][0][b396] [container1-9] [MGR-0566] JVM process will be terminated [2014.10.27 14:38:18][0][b396] [dev-18] [MGR-0141] engine container[dev_container1] successfully stopped [2014.10.27 14:38:18][0][b396] [dev-18] [MGR-0558] all containers in the node shutdown successfully [2014.10.27 14:38:18][0][b396] [dev-18] [MGR-0262] all containers successfully shutdowned |
When the message “all containers successfully shutdown” is displayed, JEUS is down normally.
4. After JEUS is started, check the process.
Code Block |
---|
[tmax@dev ~]$ ps -ef | grep jeus
tmax 1729 1705 0 14:35 pts/0 00:00:00 /bin/sh /app/was/jeus6/bin/jeus
tmax 1735 1729 8 14:35 pts/0 00:00:23 /app/java/jdk1.6/bin/java -server -Xmx512m -Xbootclasspath/p:/app/was/jeus6/lib/system/extension.jar -classpath /app/was/jeus6/lib/system/bootstrap.jar -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.library.path=/app/was/jeus6/lib/system -Djava.endorsed.dirs=/app/was/jeus6/lib/endorsed -Djava.naming.factory.initial=jeus.jndi.JNSContextFactory -Djava.naming.factory.url.pkgs=jeus.jndi.jns.url -Djava.net.preferIPv4Stack=true -Djava.util.logging.config.file=/app/was/jeus6/bin/logging.properties -Djava.util.logging.manager=jeus.util.logging.JeusLogManager -Djeus.home=/app/was/jeus6 -Djeus.log.home=/app/was/jeus6/logs -Djeus.baseport=9736 -Djeus.jvm.version=hotspot -Djeus.tm.checkReg=true -Djeus.tool.webadmin.locale.language=ko -Djeus.net.reuseAddress=true -Djeus.properties.replicate=jeus,sun.rmi,java.util,java.net jeus.server.JeusBootstrapper
tmax 2016 1799 0 14:40 pts/1 00:00:00 grep jeus
[tmax@dev ~]$ |
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
Code Block |
---|
java.lang.UnsatisfiedLinkError: $HOME /jeus6/lib/system/libRunner.so: $HOME /jeus6/lib/system/libRunner.so: cannot open shared object file: No such file or directory (Possible cause: architecture word width mismatch)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1751)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1676)
at java.lang.Runtime.loadLibrary0(Runtime.java:822)
at java.lang.System.loadLibrary(System.java:993)
at jeus.util.Runner.<clinit>(Runner.java:31)
at jeus.server.JeusServer.main(JeusServer.java:916)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at jeus.server.Bootstrapper.callMainMethod(Bootstrapper.java:299)
at jeus.server.Bootstrapper.callMain(Bootstrapper.java:371)
at jeus.server.Bootstrapper.main(Bootstrapper.java:365)
at jeus.server.JeusBootstrapper.main(JeusBootstrapper.java:8) |
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.
Info |
---|
Code Block |
---|
$~ ] rpm -qa |grep glibc
compat-glibc-2.3.4-2.26
compat-glibc-2.3.4-2.26
glibc-2.5-34
glibc-devel-2.5-34
compat-glibc-headers-2.3.4-2.26
glibc-common-2.5-34
glibc-headers-2.5-34
glibc-2.5-34
glibc-devel-2.5-34 |
Ex) GLIBC version is 2.3
Code Block |
---|
java.lang.UnsatisfiedLinkError: $HOME/jeus6/lib/system/libRunner.so: /lib64/tls/libc.so.6: version `GLIBC_2.4' not found (required by $HOME/jeus6/lib/system/libRunner.so)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1751)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1676)
at java.lang.Runtime.loadLibrary0(Runtime.java:822)
at java.lang.System.loadLibrary(System.java:993)
at jeus.util.Runner.<clinit>(Runner.java:31)
at jeus.server.JeusServer.main(JeusServer.java:916)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at jeus.server.Bootstrapper.callMainMethod(Bootstrapper.java:299)
at jeus.server.Bootstrapper.callMain(Bootstrapper.java:371)
at jeus.server.Bootstrapper.main(Bootstrapper.java:365)
at jeus.server.JeusBootstrapper.main(JeusBootstrapper.java:8) |