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

Migrate custom Physical Service Data Objects

Custom Physical Service Data Objects are migrated automatically when you migrate the WebSphere Commerce Server. However, these objects must be migrated in the development environment by running the Data Service Layer Wizard.

Procedure

1. In the v6 installation of WebSphere Commerce Developer, make a backup (to a temporary location or removable media) of all files under WCDE_installdir \xml\config\servicemodulename , where servicemodulename is one of the following subdirectories:

   • A customized WebSphere Commerce service module, identified by the -ext appended to the name. For example, extensions to the catalog service module are stored in the com.ibm.commerce.catalog-ext subdirectory.

   • A custom service module. For example, the com.mycompany.commerce.myservicemodule subdirectory.

2. In the v7 installation of WebSphere Commerce Developer, copy the files from the backup location or removable media to the location in the new environment: workspace_dir \WC\xml\config\servicemodulename .

3. Use the Data Service Layer wizard to generate object-relational metadata and physical data objects representing the customized schema.

   1. If the development environment uses a Cloudscape database, ensure that there is no existing connection to it (for example, ensure that the WebSphere Commerce Server is stopped).

   2. Select File > New > Other > WebSphere Commerce > Data Service Layer .

   3. Click Next .

   4. Select Extend a default WebSphere Commerce service module or Work with a custom service module .

   5. Enter the required information. In Service module , select the name of the module for which you are building SDOs. In Extension class prefix enter a string that is used to prefix all classes that are generated. In Extension Java package name enter the name of the package that will contain the SDOs.

      For example, if we are extending the catalog schema, the values would be...

      • Service module: Select com.ibm.commerce.catalog

      • Extension class prefix: MyCompany

      • Extension Java package name: com.mycompany.commerce.catalog

   6. Click Next.

   7. Select the custom tables you have added to the schema.

   8. Under each table you have selected, select the columns to include in the SDO class. Primary key columns, non-nullable columns, and the optcounter column are automatically selected. Primary key columns are not available, because include them in the SDO.

   9. Click Next .

   10. On the Metadata Editing panel, you can choose what columns to include in the UserData area of the logical schema, by clicking the UserData column to set the value to true or false.

       Verify the checkbox labelled Generate business object mediator configuration file is not checked.

   11. Click Finish.

+

Search Tips   |   Advanced Search