Develop > Business logic layer > Work with the data service layer
Extend the WebSphere Commerce schema using the data service layer
You 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.
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.
See WebSphere Commerce database schema for information about what changes and extensions to the schema are supported and recommended.
- Accept object-relational metadata and Physical Service Data Objects to reflect schema changes using the Data Service Layer Wizard
The WebSphere Commerce Data Service Layer Wizard generates the physical SDO Java classes for the customizations, along with the required object-relational metadata and configuration for business object mediators. These steps are required if you add a new table, and also for any new service modules you develop. XML assets that are generated are stored in the service module configuration extension directories and custom physical SDO Java classes are stored inside the WebSphereCommerceServerExtensionsLogic project.
- Configure the Business Object Mediator
You can use XML configuration data to configure the Business Object Mediator. This XML can also be generated by the Data Service Layer wizard.
- Add query templates to include custom information
This file describes how to add query templates to include information you have added to the schema.
- Extend the provided 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, you can override the properties of the expression builder.
Related concepts