ATG Commerce includes two fulfiller objects: the HardgoodFulfiller and the ElectronicFulfiller. This section will describe how fulfillers are used in the fulfillment process, how to replace a fulfiller, or add a new fulfiller of your own. Most of the examples in this section refer to the HardGoodFulfiller. For information on the ElectronicFulfiller, see the ElectronicFulfiller Class section.

The fulfiller’s responsibility for an order begins with the receipt of the FulfillOrderFragment message. Prior to this, the OrderFulfiller owns the order. The first method called is:

public void receiveMessage (String pPortName, Message pMessage)
      throws JMSException

This method is inherited from the MessageSink interface. HardgoodFulfiller is actually a subclass of SourceSinkTemplate, which implements the MessageSink. For more information, see the ATG API Reference. All that this method does is get the JMS object message that was sent, check the contained objects type and call the appropriate method. In the case of a FulfillOrderFragment message, the method called is:

public void handleFulfillOrderFragment(String pPortName,
      ObjectMessage pMessage) throws JMSException

This method begins the processing of each shipping group included in the FulfillOrderFragment (pMessage in the signature above).

loading table of contents...