Change or adding EJB Jar files

We can change enterprise bean (EJB) Jar files on application servers without having to stop the server and start it again.

 

Overview

There are several changes that one can make to EJB Jar files without stopping the server and starting it again. We can use the update wizard of the administrative console to make the changes without having to stop and restart the server. This article describes how to make the following changes by manipulating an EJB file on the server where the application is deployed:

  • Changing the ejb-jar.xml file of an EJB Jar file

  • Changing the ibm-ejb-jar-ext.xmi or ibm-ejb-jar-bnd.xmi file of an EJB Jar file

  • Changing the Table.ddl file for an EJB Jar file

  • Changing the Map.mapxmi or Schema.dbxmi file for an EJB Jar file

  • Updating the implementation class for an EJB file or a dependent class of the implementation class for an EJB file

  • Updating the Home/Remote interface class for an EJB file

  • Adding a new EJB file to an existing EJB Jar file

Changing the ejb-jar.xml file of an EJB Jar file

Restart the application. Automatic reloading will not detect the change. Use the administrative console to restart the application. Or run the wasadmin stopApplication and startApplication commands.

Hot deployment Not applicable
Dynamic reloading Yes

Change the ibm-ejb-jar-ext.xmi or ibm-ejb-jar-bnd.xmi file of an EJB Jar file

Restart the application. Automatic reloading will not detect the change. Use the administrative console to restart the application. Or run the wasadmin stopApplication and startApplication commands.

Hot deployment Not applicable
Dynamic reloading Yes

Changing the Table.ddl file for an EJB Jar file

Rerun the DDL file on the user database server. Changing the Table.ddl file has no effect on the application server and is a change to the database table schema for the EJB files.

Hot deployment Not applicable
Dynamic reloading Not applicable

Changing the Map.mapxmi or Schema.dbxmi file for an EJB Jar file

  1. Change the Map.mapxmi or Schema.dbxmi file for an EJB Jar file.

  2. Regenerate the deployed code artifacts for the EJB file.

  3. Apply the new EJB Jar file to the server.

  4. Restart the application. Use the administrative console to restart the application. Or run the wasadmin stopApplication and startApplication commands.

Hot deployment Not applicable
Dynamic reloading Yes

Updating the implementation class for an EJB file or a dependent class of the implementation class for an EJB file

  1. Update the class file in the application_root/module_name.jar file.

  2. If automatic reloading is enabled, you do not need to take further action. Automatic reloading will detect the change.

    If automatic reloading is not enabled, restart the application of which the EJB file is a member. If the updated module is used by other modules in other applications, restart those applications as well. Use the administrative console to restart the application. Or run the wasadmin stopApplication and startApplication commands.

Hot deployment Not applicable
Dynamic reloading Yes

Updating the Home/Remote interface class for an EJB file

  1. Update the interface class of the EJB file.

  2. Regenerate the deployed code artifacts for the EJB file.

  3. Apply the new EJB Jar file to the server.

  4. If automatic reloading is enabled, you do not need to take further action. Automatic reloading will detect the change.

    If automatic reloading is not enabled, restart the application of which the EJB file is a member. Use the administrative console to restart the application. Or run the wasadmin stopApplication and startApplication commands.

Hot deployment Not applicable
Dynamic reloading Yes

Adding a new EJB file to an existing EJB Jar file

  1. Apply the new or updated Jar file to the application_root location.

  2. If automatic reloading is enabled, you do not need to take further action. Automatic reloading will detect the change.

    If automatic reloading is not enabled, restart the application. Use the administrative console to restart the application. Or run the wasadmin stopApplication and startApplication commands.

Hot deployment Yes
Dynamic reloading Yes

 

Related Tasks


Hot deployment and dynamic reloading