Tutorials > Content management > Create a content-managed resource

< Previous


Summary of introducing a content managed resource

The following summarizes the steps required to introduce a new resource into a WebSphere Commerce authoring server.


Lessons learned

By completing this tutorial , you learned about the following concepts and tasks:

Unmanaged resource

  1. Create the table into the production ready schema and EJB with access beans.

  2. Access and manage data directly with access beans within runtime programming model.

  3. When all resources are created, invoke the workspace allocation ant task script that allocates the definitions of the tables into the workspace schema.

Managed operational resource

  1. Create the table into the production ready schema and EJB with access beans.

  2. Access and manage data directly with access beans within runtime programming model.

  3. When all resources are created, invoke the workspace allocation ant task script that allocates the definitions of the tables into the workspace schema.
Managed operational resource:

  1. Create the table into the production ready schema and EJB with access bean.

  2. Access and manage data directly with access beans within runtime programming model.

  3. Create the managed operational resource container (if necessary) or add to an existing container. When a new container is to be created, create an object extending from the com.ibm.commerce.context.content.resources.AbstractResourceContainerImpl directly.

  4. Configure the resource container (if a new one was added) by adding a corresponding entry into the wc-resource-containers.xml.

  5. Configure the managed operational resource by adding a corresponding entry into the container containers xml file.

  6. When all resources are created, invoke the workspace allocation ant task script that allocates the definitions of the tables into the workspace schema.

Managed Content Resource

  1. Create the table into the production ready schema and EJB with access bean.

  2. In addition, implement an additional class corresponding to the EJB implementing the com.ibm.commerce.context.content.resources.EntityBeanCreationData interface. The class is a value object that can set and return each and every one of the data properties that is contained within the EJB.

  3. Implement an ejbCreate(EntityBeanCreationData) within the EJB. This method should create an instance of the EJB given all the properties that are set into the Creation Data object.

  4. Create the managed content resource container (if necessary) or add to an existing container. When a new container is to be created, create an object extending from the com.ibm.commerce.context.content.resources.AbstractResourceContainerImpl directly.

  5. Configure the resource container (if a new one was added) by adding a corresponding entry into the wc-resource-containers.xml.

  6. Configure the managed content resource by adding a corresponding entry into the container containers xml file. The access bean, resource manager and key field data are required in the xml.

  7. Create command logic to create, update or delete content using the Resource Manager class and not the AccessBean or EJB.

  8. When all resources are created, invoke the workspace allocation ant task script that allocates the definitions of the tables into the workspace schema.

< Previous


+

Search Tips   |   Advanced Search