Migrating 3.0 EJB JARs to 3.5

In SilverStream 3.5, the deployed JAR (XXXDeployed.JAR) is replaced by two objects: a deployment plan (which includes the information about the deployment) and a deployed object (which includes the implementation classes).

Your existing deployed JARs will run as is. However, you will not be able to open them to edit the deployment information. Any changes to deployment information must be made to the deployment plan using the Deployment Plan Designer. Any new EJB deployments must also be done using the Deployment Plan Designer. The following table describes the components that the Deployment Plan Designer creates when you use it to deploy an EJB:

Component

Description

XXXDeployed

The deployed object (formerly the XXXDeployed.jar). This object is created when you deploy EJBs.

XXXRemote.jar

The remote JAR to be used by the EJB's clients. This object is created when you deploy EJBs.

XXXDeplPlan

The deployment settings for this deployed object

This is the file that you edit if you need to modify the deployment settings for any future deployments.

Component	Description
XXXDeployed	The deployed object (formerly the XXXDeployed.jar). This object is created when you deploy EJBs.
XXXRemote.jar	The remote JAR to be used by the EJB's clients. This object is created when you deploy EJBs.
XXXDeplPlan	The deployment settings for this deployed object This is the file that you edit if you need to modify the deployment settings for any future deployments.

Follow these steps to migrate an existing deployed EJB JAR to the new deployment plan model.

To migrate an existing EJB to 3.5:

Determine if the EJB JAR relies on classes residing in a different JAR file.

For EJB JARs that do rely on externally stored classes, you must:
- Open the EJB JAR and add a Class-path entry to an existing or new Manifest file.
- Choose the XXXDeployed.jar file, right-click and choose Rebuild. (The Rebuild command ensures that the XXXDeployed.jar file includes the updated manifest file.)
  
  For information on Class-path entries and the Rebuild command, see the chapter on the JAR Designer in the online Tools Guide.
Choose the XXXDeployed.jar file, right-click and choose Convert to EJB Deployment Plan.

SilverStream launches the Deployment Plan Designer which allows you to create or modify an XML-based file that includes the deployment information needed by SilverStream.

NOTE When migrating, you are not required to modify this file. SilverStream creates the deployment plan from the deployment information that exists in the XXXDeployed.JAR. It simply stores the information in a different format. This means that the JNDI names in the XXXDeployed.JAR and the JNDI names in the deployment plan will be identical. When you attempt to save and deploy the new deployment plan you will encounter errors if the original XXXDeployed.JAR file is still enabled. See the table below for more information on how the state of the XXXDeployed.JAR might affect your ability to complete the migration.
If your EJB's rely on classes/files that reside in external JARs, you must add these JARS to the "Uses Jars" list of the current deployment plan by choosing the File>Jars menu option.

Choose Save or Save and Deploy.

The behavior of these options depends on the state (enabled/disabled) of the XXXDeployed.JAR. The following table describes the behavior.

XXXDeployed.jar Condition

Save

Save and Deploy

Disabled

Saves the deployment plan

Saves the deployment plan and constructs the deployment objects necessary for the EJBs in the EJB JAR

Enabled with different JNDI names

Saves the deployment plan

Saves the deployment plan and constructs the deployment objects necessary for the EJBs in the EJB JAR

Enabled with same JNDI names

SilverStream prompts you as follows:

"ERROR: the following JNDI names are the same as in the original deployed jar:

JNDINameX, JNDINameX2 JNDINameX3

Do you want to disable the original deployed jar?

If you select Yes, SilverStream disables the XXXDeployed.jar and saves the deployment plan.

If you select No, you must change all the listed JNDI names before you can save.

SilverStream prompts you as follows:

"ERROR: the following JNDI names are the same as in the original deployed jar:

JNDINameX, JNDINameX2 JNDINameX3

Do you want to disable the original deployed jar?

If you select Yes, SilverStream disables the XXXDeployed.jar, saves the deployment plan, and constructs the deployment objects necessary for the EJBs in the EJB JAR.

If you select No, you must change all the listed JNDI names before you can successfully save and deploy.

XXXDeployed.jar Condition	Save	Save and Deploy
Disabled	Saves the deployment plan	Saves the deployment plan and constructs the deployment objects necessary for the EJBs in the EJB JAR
Enabled with different JNDI names	Saves the deployment plan	Saves the deployment plan and constructs the deployment objects necessary for the EJBs in the EJB JAR
Enabled with same JNDI names	SilverStream prompts you as follows: `"ERROR: the following JNDI names are the same as in the original deployed jar:` `JNDINameX, JNDINameX2 JNDINameX3` `Do you want to disable the original deployed jar?` If you select Yes, SilverStream disables the XXXDeployed.jar and saves the deployment plan. If you select No, you must change all the listed JNDI names before you can save.	SilverStream prompts you as follows: `"ERROR: the following JNDI names are the same as in the original deployed jar:` `JNDINameX, JNDINameX2 JNDINameX3` `Do you want to disable the original deployed jar?` If you select Yes, SilverStream disables the XXXDeployed.jar, saves the deployment plan, and constructs the deployment objects necessary for the EJBs in the EJB JAR. If you select No, you must change all the listed JNDI names before you can successfully save and deploy.