Deprecated featureExtend the WebSphere Commerce schema using the data service layer
We can extend the existing schema to support customization. These extensions include changing the physical database schema, generating the object-relational metadata and physical SDOs, and using query templates to retrieve the new information.
About this task
These tasks enable you to add new data to a service provided by WebSphere Commerce. They do not, however, apply to creating a new, custom service.
(Developer) Building metadata and data objects to reflect Data Service Layer schema changes
The WebSphere Commerce Data Service Layer Wizard generates the physical service data objects (SDO) Java classes for a customization. This Wizard also generates the required object-relational metadata and configuration for business object mediators. If we create a database table or develop new service modules, we must build the required object-relational metadata and physical SDOs with the Data Service Layer Wizard to reflect your schema changes.- Configure the Business Object Mediator
We can use XML configuration data to configure the Business Object Mediator. This XML can also be generated by the Data Service Layer wizard.- Extending a business object mediator
Occasionally the default business objects provided with WebSphere Commerce are insufficient to describe the types of data used in certain businesses, making it is necessary to extend or create new business objects. If you have created custom business objects, then you will need to create a custom business object mediator in order to override existing component services to understand them.- Adding query templates to include custom information
This file describes how to add query templates to include information you have added to the schema.- Extending the get-data-config.xml file
You should extend the get-data-config.xml file when the configuration file has been provided for you. By extending the configuration, we can override the properties of the expression builder.