Tutorials > Management Center > Add new properties to a WebSphere Commerce service using the data service layer

< Previous | Next >

Customize the physical layer to include the new information

In this step we will customize the physical layer by modifying the WebSphere Commerce schema, generating object-relational metadata, and generating physical service data objects (SDOs).

To do so, you will use a tool called the Data Service Layer wizard.

The Data Service Layer Wizard is used to generate object-relational metadata and physical data objects for the schema customization. Physical SDOs are service data objects that represent tables in the WebSphere Commerce schema. Each data object type corresponds to a table definition in the schema, and each data object property corresponds to a table column or a reference to another data object type; these references correspond to the foreign key relationships between the database tables.

For each service module, there is object-relational metadata that contains the information to relate the physical data object to a database table. Custom object-relational metadata is stored in the component configuration extension directories and custom physical SDOs are stored inside the WebSphereCommerceServerExtensionsLogic project.

This wizard performs the following tasks:

1. Creates an extension configuration folder for the Catalog service module if one does not already exist. The directory path is: WC_EAR\xml\config\com.ibm.commerce.catalog-ext.

2. Generates a custom object-relational metadata file that describes the new custom tables and relationships. In this tutorial, the metadata file will describe the two new tables, XWARRANTY and XCAREINSTRUCTION, along with the three new relationships between tables:

   • XWARRANTY and CATENTRY

   • XCAREINSTRUCTION and CATENTRY

   • XCAREINSTRUCTION and CATENTDESC

   This file is located at:WC_EAR\xml\config\com.ibm.commerce.catalog-ext\wc-object-relational-metadata.xml.

3. Generates an SDO Java class and places it in the WebSphereCommerceServerExtensionsLogic project for:

   • Each new custom table (XWARRANTY and XCAREINSTRUCTION).

   • Each modified WebSphere Commerce table (CATENTRY and CATENTDESC were modified by adding new relationships to the custom tables).

   Physical SDOs are service data objects that represent tables in WebSphere Commerce. For each table there is one data object that represents the tables, columns, and relationships.

4. Creates a utility Java class to return the physical SDO root class (and its package) for the service module. This root class ensures that all WebSphere Commerce physical SDOs for the Service Module, and any additional physical SDOs for the customization, are available at runtime.

5. Creates an extension service module configuration file that instructs WebSphere Commerce to use the newly created catalog physical SDO class in WC_EAR\xml\config\com.ibm.commerce.catalog-ext\wc-component.xml.

6. Creates an extension business object mediator configuration file that configures the business object mediator to include data from the XWARRANTY and XCAREINSTRUCTION tables in the user data of a CatalogEntry noun. This file is located at WC_EAR\xml\config\com.ibm.commerce.catalog-ext\wc-business-object-mediator.xml.

Procedure

To begin customizing the physical layer:

1. 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 an Apache Derby 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

   5. Click Next.

   6. Enter the following information:

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

      • Extension class prefix: MyCompany

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

   7. Click Next.

   8. Select the XWARRANTY and XCAREINSTRUCTION tables.

   9. Expand the XWARRANTY and XCAREINSTRUCTION tables and make sure all columns are selected.

   10. Click Next.

   11. Under UserData, ensure the Warterm, Wartype, and Careinstruction database columns are set to True. Set the other columns to False if they are set as True by default.

   12. If you are using the Oracle database in the WebSphere Commerce Developer environment, under the Datatypes column, select INTEGER for the LANGUAGE_ID row.

   13. Click Finish.

2. The following step is necessary only if the WebSphere Commerce Developer environment uses the Oracle database.

   The Oracle NUMBER data type can represent different number types, including integer, float, and double. However, the data service layer requires all columns to be resolved to specific types. When generating object-relational metadata and physical service data objects, the wizard assumes that other columns with a data type of NUMBER default to long. You can specify other data types, such as: BIGINT, SMALLINT, and DECIMAL. If a different data type is required, the object-relational metadata XML file must be changed.

   To update the column attribute:

   1. Open WC_EAR\xml\config\servicemodulepackagename-ext\wc-object-relational-metadata.xml.

   2. Update the type attribute for the LANGUAGE_ID column.

      Find the section that corresponds to the following XML sample:

      <_config:table name="XCAREINSTRUCTION" occColumnName="OPTCOUNTER" propertyName="Xcareinstruction">
         
      <_config:column name="CATENTRY_ID" nullable="false" primaryKey="true" propertyName="catentry_id" type="NUMBER"/>
         
      <_config:column name="LANGUAGE_ID" nullable="false" primaryKey="true" propertyName="language_id" type="NUMBER"/>
         
      <_config:column name="DESCRIPTION" nullable="true" primaryKey="false" propertyName="description" type="VARCHAR2"/>
         
      <_config:column name="OPTCOUNTER" nullable="true" primaryKey="false" propertyName="optcounter" type="SMALLINT"/>
      </_config:table>
      

      Change this LANGUAGE_ID column data type from NUMBER (which would default to Long) to INTEGER, as shown in the following XML sample:

      <_config:table name="XCAREINSTRUCTION" occColumnName="OPTCOUNTER" propertyName="Xcareinstruction">
         
      <_config:column name="CATENTRY_ID" nullable="false" primaryKey="true" propertyName="catentry_id" type="NUMBER"/>
         
      <_config:column name="LANGUAGE_ID" nullable="false" primaryKey="true" propertyName="language_id" type="INTEGER"/>
         
      <_config:column name="DESCRIPTION" nullable="true" primaryKey="false" propertyName="description" type="VARCHAR2"/>
         
      <_config:column name="OPTCOUNTER" nullable="true" primaryKey="false" propertyName="optcounter" type="SMALLINT"/>
      </_config:table>
      

   3. Repeat step 1. The wizard removes the existing SDOs for the table and generate new SDOs with the new data type.

      The custom tables is preselected for you, when you repeat step 1g.

If the code generated by the Data Service Layer produces an error, for example, CatalogEntityPackage can not be resolved, this might be caused by a Rational Application Developer issue.

To potentially resolve the error, select Project > Clean.

There will be compiling errors in the generated classes.

To fix the errors, add Catalog-DataObjects.jar and Catalog-Client.jar to the classpath.

< Previous | Next >

+

Search Tips   |   Advanced Search