Creating a WebSphere Commerce service module

1. Right-click on the WebSphereCommerceServerExtensionsLogic project and select New > Other > XML > XML and click Next.

   

2. Click Next.
3. Select Create XML file from an XML schema file and click Next.

   

4. Select Select file from Workspace, select WC > xml > config > xsd > wc-component-pattern.xsd and click Next.

   

5. Click Finish.

<_pattern:commerceComponent xmlns:_pattern="http://www.ibm.com/xmlns/prod/commerce/foundation/pattern" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xsi:schemaLocation="http://www.ibm.com/xmlns/prod/commerce/foundation/pattern 
    ../../WC/xml/config/xsd/wc-component-patten.xsd "
    name="MyServiceModuleName" packagenameprefix="com.mycompany.commerce" company="MyCompany"
    namespace="http://www.mycompany.com/xmlns/prod/commerce/9/MyServiceModuleName" nlsprefix="myco" type="SOI/BOD">
  <_pattern:noun name="MyBusinessObject" get="true" process="true" change="true" sync="false" /> 
</_pattern:commerceComponent> 

Where My Company is your company name.

name=" MyServiceModule"

The name of your new service module

packagenameprefix="com. mycompany.commerce"

Used to prefix the generated starter store code

Note: Do not include the component name in this prefix. That is, this prefix should only represent the prefix for your organization.

namespace=http://www.mycompany.com/xmlns/prod/commerce/myservicemodule

The namespace to associate with your component. This namespace should represent your organization.

nlsprefix="mycompany"

The xml schema prefix to associate with the name space. To avoid collision with the WebSphere Commerce prefix, avoid using an underscore (_) as the first character of the namespace prefix.

type="SOI/BOD"

Specify the type of service module. If you specify SOI, the pattern will create a service module that provides service-oriented integration into your existing controller commands, access beans, and EJBs.

If you specify BOD, the pattern will create a service-oriented architecture service module that will use commands developed using the BOD command framework. These BOD commands will act upon Structured Data Objects (SDOs) and use the Business Object Mediator to persist and retrieve these SDOs.

• name=" MyBusinessObject" where MyBusinessObject is the name of your new noun.

  Nouns define the name of each data element in the logical model, and assign that name to a data type. The data type can be a primitive XML schema type such as boolean, or a complex type. A complex type is a construct of data elements such as CurrencyType which contains price (represented by a double type) and currency (represented as a string). A noun can contain one or more noun parts (sometimes referred to as noun elements). A Noun part is a complex XML type within a noun that can be acted upon independently. Noun parts represent parts of a logical noun. Separating a noun into parts simplifies coding by reducing the scope of commands and mediators. Instead of handling the entire noun, code is limited to only processing the noun part. When a request arrives, it is broken into its different parts and the appropriate command for each part is run. For example, the CatalogEntry noun contains a list of descriptions. A catalogEntry description is considered a noun part and is processed using the ChangeCatalogEntryDescriptionCmdImpl and ChangeCatalogEntryDescriptionMediator.

• get="true"
• process="true"
• change="true"
• sync = "false"

Note: You can create multiple <noun> elements in one service module, although in this example we just create one. Do not choose Get, Process, Change, or Sync as the name of your noun (they are reserved for use as verbs).