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:
Follow these steps to migrate an existing deployed EJB JAR to the new deployment plan model.
To migrate an existing EJB to 3.5:
For EJB JARs that do rely on externally stored classes, you must:
For information on Class-path entries and the Rebuild command, see the chapter on the JAR Designer in the online Tools Guide.
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.
The behavior of these options depends on the state (enabled/disabled) of the XXXDeployed.JAR. The following table describes the behavior.