6.6.0.15: Deployment Tool

InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.0: About user assistance >
6.6.0.15: Deployment Tool

Main topics

Other topics

Migrating CMP beans from Version 3.5

To preserve the existing (older) table/schema rules when migrating CMP entity beans from WebSphere Application Server Version 3.5 to Version 4.0, use the -35 option of the deployment tool. The deployment tool is used to generate code for deployment on Version 4.0. Its -35 option will generate table mappings based on the 3.5 rules. Combine the -35 option with the -dbschema EJB option to map to the 3.5 generated schema that was used.

To migrate manually, the EJB JAR requiring migration must be invoked through the deployment tool command line, using the arguments:

-35 -dbschema EJB

Without these options, the database table will follow a new set of rules that is more aligned with the defaults for VisualAge for Java.

The .java and .class file time stamps must differ

If an error occurs when you are generating code for deployment, ensure that the time stamps of the .class files and corresponding .java files in your EJB JAR file do not match. If the .class and .java files have the same time stamp, one solution is to perform an operation on the .java files (such as "touch" on a UNIX system) to cause their time stamps to change without changing the file content.

Go to previous article: XML-SOAP Admin tool Go to next article: Generating EJB deployment code from the command line

 

 
Go to previous article: XML-SOAP Admin tool Go to next article: Generating EJB deployment code from the command line