Create the component facade

Create a component facade consists of running the Design Pattern Toolkit and then customizing the template code that is generated. The EJB service module is created with shell commands that return empty BODs.

To create a component facade:

  1. Install the Design Pattern Toolkit and the ComponentProjects design pattern.

  2. Create a WebSphere Commerce service module.

  3. Open the MyServiceModule-Server project.

  4. Implement the shell commands in the com. mycompany.commerce. myservicemodule.facade.server.commands package. For example, implement Verb MyNounCmdImpl.java. This is the simplest approach to implementing a component facade -- use the shell command to parse your XML and execute any existing WebSphere Commerce or custom commands containing business logic you wish to reuse.

  5. (Optional) Alternatively, use the
    Message mapper to flatten the XML messages into name-value pairs appropriate to your WebSphere Commerce commands. If you do so, you will use the command registry table to select the correct command implementation, based on the inbound XPath expression in the BOD. For an example of how the member subsystem maps XML messages to command name-value pairs, see the
    Member component message mapper.

  6. Register your new commands. When you do so, if you are using the message mapper, associate the XPath search expression key with your new custom fetch command implementation with an SQL statement. For example
    insert into cmdreg (STOREENT_ID, INTERFACENAME, CLASSNAME,TARGET)
    VALUES 
    (0,'com.ibm.commerce.catalog.facade.server.commands.FetchCatalogEntryCmd+/CatalogEntry[Price[StandardPrice[Price[(Price<=
    and Price[@currency=]) 
    and (Price>= and Price[@currency=])]]]]',
    'com.mycompany.commerce.customization.catalog.FetchCatalogEntryByPriceRangeTaskCmdImpl',
    'Local');
    

    that the interface name contains the name of the command concatenated with the XPath.

    For implementations that do not use the Message mapper, including WebSphere Commerce member subsystem customization, update the CMDREG entry for the existing default fetch command. Also, no XPath details are included in the SQL update.

Related concepts

WebSphere Commerce services
WebSphere Commerce service module
Component facade interfaces

Related tasks

Deploying the component facade


Related Reference


Member component message mapper configuration