Migrating custom Physical Service Data Objects

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


  1. In your Version 7.0 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, which is 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. Copy the files from your backup location to the following location in your Version 8.0 environment: workspace_dir\WC\xml\config\servicemodulename.
  3. Use the Data Service Layer wizard to generate object-relational metadata and physical data objects that represent the customized schema.
    1. If your development environment uses a Derby database, ensure that there is no existing connection to it. (To drop the connection, stop the WebSphere Commerce Server.)
    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 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 contains the SDOs.
      If you are extending the catalog schema, the values would be as follows:
      • 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 that you added to the schema.
    8. Under each select table, select the columns that you want 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 you must include them in the SDO.
    9. Click Next.
    10. On the Metadata Editing panel, you can choose which columns you want to include in the UserData area of the logical schema by clicking the UserData column. You can then set the values to true or false.
      Note: Ensure that the check box labeled Generate business object mediator configuration file is not checked.
    11. Click Finish.