Table of Contents
This chapter describes the configurations to be aware of when upgrading from JEUS 6.x version to JEUS 7, and a detailed description of migrating the configurations. As well, this chapter will describe the process of migrating via the upgrade tool.
The following is the procedure for migrating from JEUS 6 to JEUS 7.
Configure the JEUS 7 domain based on the node-container configuration configured in the JEUS 6 environment.
Create JEUS 7 configuration files by using various configuration files used in the JEUS 6 environment.
Install and deploy applications running in the JEUS 6 environment in the newly configured JEUS 7 domain.
The succeeding sections will describe the information necessary for domain creation and configuration.
Detailed information about the usage and options of the upgrade tool (upgrading from 6 to 7) is described in "Appendix A. Upgrade Tool", and this section will briefly describe its usage. The upgrade tool basically runs with the JEUS 6 installation directory and the JEUS 7 installation directory as arguments. It reads all the information and configurations for all configured nodes by searching the JEUS 6 installation directory, and then uses them to configure the JEUS 7 domain.
upgrade6to7 -source ${JEUS6_HOME} -target ${JEUS7_HOME}
Server configuration migration refers to the conversion of files (such as XML) that make up a server configuration, and includes configuration files such as JEUSMain.xml, EJBMain.xml, WEBMain.xml, JMSMain.xml, accounts.xml, and policies.xml. In JEUS 7, the configuration that was divided into JEUSMain.xml, EJBMain.xml, WEBMain.xml, and JMSMain.xml are merged into domain.xml. Therefore, the user must configure them in domain.xml.
The following are the files that needed to be converted for server configuration migration.
JEUS6_HOME/config/NODE_NAME/JEUSMain.xml
→ JEUS7_HOME/domains/DOMAIN_NAME/config/domain.xml
JEUS6_HOME/config/NODE_NAME/EJB_ENGINE_NAME/EJBMain.xml
→ JEUS7_HOME}/domains/DOMAIN_NAME/config/domain.xml
JEUS6_HOME/config/NODE_NAME/JMS_ENGINE_NAME/JMSMain.xml
→ JEUS7_HOME/domains/DOMAIN_NAME/config/domain.xml
JEUS6_HOME/config/NODE_NAME/SERVLET_ENGINE_NAME/WEBMain.xml
→ JEUS7_HOME/domains/DOMAIN_NAME/config/domain.xml
The following are the files that do not need to be converted, but need to be copied to applicable directories.
JEUS6_HOME/config/NODE_NAME/SERVLET_ENGINE_NAME/web.xml
→ JEUS7_HOME/domains/DOMAIN_NAME/config/servlet/SERVER_NAME/web.xml
JEUS6_HOME/config/NODE_NAME/SERVLET_ENGINE_NAME/webcommon.xml
→ JEUS7_HOME/domains/DOMAIN_NAME/config/servlet/SERVER_NAME/webcommon.xml
The upgrade tool configures domain.xml by reading each configuration files.
Since the Java EE standard supports backward compatibility, applications written in compliance with the Java EE standard can be used in JEUS 7 without major problems as long as the JEUS deployment descriptor is converted. If there is any problems in deploying applications due to compatibility issues with the JEUS deployment descriptor, the user can deploy the application by using the 'upgrade' option of the deploy-application command. For detailed information about the command, refer to
Scripts provided in JEUS (6.x and 7) are all located in the JEUS_HOME/bin directory. This section describes the scripts not provided in JEUS 7 but provided in JEUS 6.x as well as how to modify the scripts if they are written separately.
The following scripts are no longer provided in JEUS 7.
jmsadmin
In JEUS 7, the functions provided in jmsadmin are combined into jeusadmin.
JEUS boot script
In JEUS 6.x, JEUS was booted up by using the jeus script as follow.
jeus -U<user_name> -P <password>
JEUS 7 provides boot scripts as shown below. Please note that different scripts are used for booting Domain Admin Server (DAS) and
Managed server.
startDomainAdminServer -u <user_name> -p <password> (DAS boot-up) startManagedServer -u <user_name> -p <password> ... (Managed server boot-up)
JEUS server shutdown script
In JEUS 6, jeusadmin was used for shutdown.
jeusadmin <node_name> -U<user_name> -P<password> jeusexit
In JEUS 7, a script is provided for shutdown.
stopServer -host <host:port> -u <user_name> -p <password>
When executing the server shutdown script, the host and port must use the address and default port of the target server.
jeusadmin
JEUS 6 and script name are the same, but the usage has changed a little bit. Nodename is not used, and the address and port of the server to be connected is used. If the address and port are not specified, then attempt connecting to localhost:9736.
jeusadmin -u <user_name> -p <password> -host 127.0.0.1 -port 9736
As JEUS 7 has changed quite a bit from JEUS 6, client applications written in JEUS 6 may not run in JEUS 7. In this case, the user must newly create client applications, or modify them.
Since the object name format representing MBeans has been changed in JEUS 7, and many MBean APIs have been added/deleted/modified, the MBean monitoring client created in JEUS 6 cannot be used in JEUS 7.
Libraries such as jclient.jar and jclient_jaxb.jar to be used when creating client applications cannot be found in the below path.
JEUS7_HOME/lib/client