Migrate > Migrating WebSphere Commerce Developer > Migrating custom assets > ... non-EJB projects

Migrating command and data bean projects

Migrating command and data bean projects involves several steps. The project must be exported from the old development environment, and imported into WebSphere Commerce Developer, v7.

Custom extension logic code from the WebSphereCommerceServerExtensionsLogic project must be exported from WebSphere Commerce Developer v5.6.1 or 6.0 as a jar file named WebSphereCommerceServerExtensionsLogic.jar, and imported as compressed file under WebSphere Commerce Developer v7.0 within Java EE perspective > Other Projects > WebSphereCommerceServerExtensionsLogic > src .

Other custom projects must be exported and imported following the instructions in step 3.

Procedure

1. Export the Java project from the old development environment as a JAR file using Rational Application Developer.

   1. Open the WebSphere Commerce Developer development environment workspace and open the J2EE perspective.

   2. Select the project containing the customized code. Right-click the mouse button and select Export .

   3. Select Jar file and click Next .

   4. In the list of resources under Select the resources to export , ensure the project is selected.

   5. Ensure Export generated class files and resources and Export java source files and resources are selected.

   6. Click Browse and choose a path to save the exported JAR file.

   7. Ensure Compress the contents of the JAR file is checked.

   8. Click Finish to complete the exporting,

2. Import the Java project using (RAD) Rational Application Developer functions within WebSphere Commerce Developer, version 7.0.

   1. Open the WebSphere Commerce Developer v7.0 development environment workspace and open the Java EE perspective.

   2. Select Java EE perspective > Other Projects > WebSphereCommerceServerExtensionsLogic > src

   3. Right-click the target project and click Import .

   4. Select the type of source that will be imported and click Next .

   5. Click Browse to find the file to import.

   6. If you are asked to overwrite any files, select Yes for each file.

   7. Click Finish .

      Notes:

      1. The class path for each custom project must be updated to resolve the dependencies on libraries and between projects.

      2. Do not import any of the meta data, or the migration will not work. Meta data includes the following files:

         • .compatibility

         • .j2ee

         • .runtime

         • .project

         • .classpath

         • .websettings

         • META-INF/

           • MANIFEST.MF

         • WebContent/WEB-INF

           • base.tld

           • flow.tld

           • struts-bean.tld

           • struts-html.tld

           • struts-logic.tld

           • struts-nested.tld

           • struts-template.tld

           • struts-tiles.tld

           • ibm-web-bnd.xml

           • ibm-web-ext.xml

           • WCEP.tld

           • web.xml

           • struts-config-catalog-services.xml

           • struts-config-contract-services.xml

           • struts-config-GiftCenter.xml

           • struts-config-management-center.xml

           • struts-config-marketing-services.xml

           • struts-config-member-services.xml

           • struts-config-order-services.xml

           • struts-config.xml

           • struts-wc-webservices.xml

         • WebContent/META-INF/

           • MANIFEST.MF

         • WebContent/WEB-INF/lib

           • wcbase.jar

3. If the project to import doesn't exist in the v7.0 developer workspace, then follow these steps to import entire command or databean projects from previous versions of WebSphere Commerce Developer:

   1. Open the old WebSphere Commerce Developer vdevelopment environment workspace and open the J2EE perspective.

   2. Select the project containing the customized code. Right-click the mouse button and select Export .

   3. Select Zip file and click Next .

   4. In the list of resources under Select the resources to export , ensure the project is selected.

   5. Ensure the Create only selected directories and Compress the contents of the file options are selected

   6. Click Browse and choose a path to save the exported ZIP file.

   7. Click Finish to complete the exporting.

   8. Open the WebSphere Commerce Developer v7.0 development environment workspace and open the Java EE perspective.

   9. Select File > Import > Existing Projects into Workspace .

   10. Click Browse to find the file you exported.

   11. Click Finish .

   12. A Workspace Migration Wizard is shown. Follow the instructions in the wizard to complete the migration.

4. Correct any compilation errors and rebuild the project.

+

Search Tips   |   Advanced Search