Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Developing
The topics in the Developing section describe tasks performed by an application developer.
Persistent object model
WebSphere Commerce deals with a large amount of persistent data. There are numerous tables defined in the current database schema. Even with this extensive schema, however, you might need to extend or customize the database schema for your particular business needs.
WebSphere Commerce enterprise beans
The persistence layer within the WebSphere Commerce architecture is implemented according to the EJB component architecture. The EJB architecture defines two types of enterprise beans: entity beans and session beans. Entity beans are further divided into container-managed persistence (CMP) beans and bean-managed persistence (BMP) beans.
Extending the WebSphere Commerce object model
Application requirements may lead you to extend the existing WebSphere Commerce object model. The WebSphere Commerce object model can be extended in two ways.
Extending the WebSphere Commerce object model with entity beans
One situation that merits an extension to the existing WebSphere Commerce object model is addition of attributes to your application.
Modifying the schema name
The next step is to modify the schema name so that your bean will be portable to other databases. The special value to allow a bean to be portable in this manner is NULLID.

Modifying the schema name

The next step is to modify the schema name so that your bean will be portable to other databases. The special value to allow a bean to be portable in this manner is NULLID.

Before you begin

You have mapped the fields in the enterprise bean to the columns in the database table.

About this task

To modify the schema name:

Procedure

In the Project Explorer view expand Databases > WebSphereCommerceServerExtensionsData.
Right-click the schema node (for example, db2user) and select Rename.
Set the value to NULLID.
Proceed to creating the access bean.