If you use the reload functionality, the regeneration of applications (creation of EAR files) is no longer required and you only need to replace the class files directly. Therefore, the process of switching between applications becomes easier.

You can execute the reload functionality only for those J2EE applications that are in exploded archive format and are in running state or in stopped state due to reload failure.

The two ways of implementing the reload functionality are as follows:

• Reload functionality based on auto-detection of updates by the J2EE server
• Reload functionality based on command execution

This section describes the reload functionality based on command execution.

The procedures for switching between J2EE applications using the reload functionality are described below:

1. Compile the Java program to be updated.
2. Execute the reload command.

Execute the following reload command to switch the J2EE applications that are in exploded archive format:

Execution format

cjreloadapp [server-name] -name Application-name [-t timeout-period-until-forced-reloading-starts]

Example of execution

cjreloadapp MyServer -name App1
 

For details on the cjreloadapp command, see cjreloadapp (Reloading applications) in the uCosminexus Application Server Command Reference Guide.

For details on the reload functionality and the reload functionality based on update detection, see 13.8 Detecting updates and reload of J2EE applications in the uCosminexus Application Server Common Container Functionality Guide.

Note:

• By default, the reload functionality is disabled. To use the reload functionality, specify the property setup file (usrconf.properties) key as follows:

• Setting the scope for reload functionality
  ejbserver.deploy.context.reload_scope=app
  
• Setting the update detection interval
  ejbserver.deploy.context.check_interval=1
  

For details on reload settings and update detection of J2EE applications, see 13.8.12 Settings for detecting updates and reload of J2EE applications in the uCosminexus Application Server Common Container Functionality Guide.

• For J2EE applications including resource adapters, the RAR files are saved in the archive format. Even if one RAR file existing under an application directory is changed, the reload functionality will not be executed.
• When the reload functionality is used for applications that contain cosminexus.xml, the definition information of cosminexus.xml will not be reloaded.