Migrate > Migrating WebSphere Commerce Developer > Migrating custom assets > ... non-EJB projects > ... store asset project
Migrate custom projects
In WebSphere Commerce Developer v7.0, only custom projects need to be migrated. The migration process involves exporting assets as archive files and then importing the archive files.
The assets to be exported:
- Custom static store assets
- Custom Java code
- Custom JSP files
Procedure
- To export a custom Web project from a WebSphere Commerce Developer v6.0 development environment workspace:
- Open the WebSphere Commerce Developer v6.0 development environment workspace and open the J2EE perspective.
- Select the project containing the customized code. Right-click the mouse button and select Export .
- Select Zip file and click Next .
- In the list of resources under Select the resources to export , deselect Stores, then select all contents under Stores. Ensure the project is selected.
- Ensure the Create only selected directories option is selected
- Click Browse and choose a path to save the exported ZIP file.
- Ensure Compress the contents of the file is checked.
- Click Finish to complete the exporting,
- You need to correct the paths in the compressed ZIP file for the Stores project. The directory path has changed from:
- JavaSource
to
- src
- To export a custom Web project from WebSphere Commerce Developer v5.6.1, or a custom Java project from version 5.6.1 or version 6.0:
- Open the WebSphere Commerce Developer development environment workspace and open the J2EE perspective.
- Select the project containing the customized code. Right-click the mouse button and select Export .
- Select Jar file and click Next .
- In the list of resources under Select the resources to export , ensure the project is selected.
- Ensure Export generated class files and resources and Export java source files and resources are selected.
- Click Browse and choose a path to save the exported JAR file.
- Ensure Compress the contents of the JAR file is checked.
- Click Finish to complete the exporting,
- If you exported custom projects from a WebSphere Application Server v5.1 environment, correct the paths in the compressed JAR or ZIP file. The directory path has changed from:
- Stores/Web Content/storename
to
- Stores/WebContent/storename
- Import a custom project
- Open the WebSphere Commerce Developer v7.0 development environment workspace and open the Java EE perspective.
- Select the corresponding project.
- Right-click the target project and click Import .
- Select the type of source that will be imported and click Next .
- Click Browse to find the file to import.
- If you are asked to overwrite any files, select Yes for each file.
- Click Finish .
Notes:
- The class path for each custom project must be updated to resolve the dependencies on libraries and between projects.
- 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
Next topic:
Migrate JSP files