Change or add EJB JAR files

 

EJB JAR files can be changed without having to cycle the appserver. See Hot Deployment for information on the location of metadata.

 

Change the ejb-jar.xml file of an EJB JAR file

  1. Change the ejb-jar.xml file.

  2. Cycle the application. Automatic reloading does not detect the change.

Hot deployment: Not applicable
Dynamic reloading: Yes
Restart the application: Yes

 

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

  1. Change the file that you want to update.

  2. Cycle the application. Automatic reloading does not detect the change.

Hot deployment: Not applicable
Dynamic reloading: Yes
Restart the application: Yes

 

Change the Table.ddl file for an EJB JAR file

  1. Change the table.ddl file.

  2. Rerun the DDL file on the user database server. Changing the Table.ddl file does not affect the application server and is a change to the database table schema for the EJB JAR files.

Hot deployment: Not applicable
Dynamic reloading: Not applicable
Restart the application: No

 

Change 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. Cycle the application.

Hot deployment: Not applicable
Dynamic reloading: Yes
Restart the application: Yes

 

Update 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. Update the application.

    If automatic reloading is enabled, you do not need to take further action. Automatic reloading detects the change.
    If automatic reloading is not enabled, use the administrative console or wsadmin to stop and restart the application of which the EJB file is a member. If the updated module is used by modules in other applications, restart those applications as well.

Hot deployment: Not applicable
Dynamic reloading: Yes
Restart the application: If automatic reloading is not enabled

 

Update 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. Update the application.

    If automatic reloading is enabled, you do not need to take further action. Automatic reloading detects the change.
    If automatic reloading is not enabled, use the administrative console or wsadmin to stop and restart the application of which the EJB file is a member.

Hot deployment: Not applicable
Dynamic reloading: Yes
Restart the application: If automatic reloading is not enabled

 

Add a new EJB file to an existing EJB JAR file

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

  2. Update the application.

    If automatic reloading is enabled, you do not need to take further action. Automatic reloading detects the change.
    If automatic reloading is not enabled, use the administrative console or wsadmin to stop and restart the application.

Hot deployment: Yes
Dynamic reloading: Yes
Restart the application: If automatic reloading is not enabled