Online Model Loading

Online model loading requires the invoking of the catalog publish workflow in TIBCO Fulfillment Catalog using the exposed SOAP service.

You can invoke the catalog publish workflow in TIBCO Fulfillment Catalog directly by using the sample SOAP web service requests available in the $AF_HOME/samples directory. The request can be sent using any standard SOAP client tools such as SOAPUI. Specify the correct enterprise name, user name, and password in the request. Also specify the correct MASTERCATALOGNAME key and a PRODUCTID to publish the specific catalog.

Invoke the request against the running instance of TIBCO Fulfillment Catalog on the URL which typically looks like http://<HOST>:<PORT>/eml/services/router/MasterCatalogRecordAction where HOST and PORT are the machine name and port number where TIBCO Fulfillment Catalog is deployed and running.

Refer to the TIBCO Fulfillment Catalog documentation for more details.

The sample request to invoke TIBCO Fulfillment Catalog workflow for publishing product catalogs is available in $AF_HOME/samples/Online_ProductModel_Publish_Request.xml.

TIBCO Fulfillment Catalog publishes the models on respective topics as mentioned in the following table:

Model (Catalog) TIBCO Fulfillment Catalog JMS Topic
Product tibco.ac.productmodel.topic
Action tibco.ac.actionmodel.topic
Discount tibco.ac.discountmodel.topic
Price tibco.ac.pricemodel.topic
Plan Fragment tibco.ac.planfragmentmodel.topic

To make these models available to TIBCO Fulfillment Order Management, the following JMS bridges must be created between the TIBCO Fufillment Catalog topics and the corresponding TIBCO Fulfillment Order Management queues as mentioned in the following table:

TIBCO Fulfillment Catalog Source Topic TIBCO Fulfillment Order Management Target Queue
tibco.ac.productmodel.topic tibco.aff.catalog.product.request
tibco.ac.actionmodel.topic tibco.aff.catalog.action.request
tibco.ac.discountmodel.topic tibco.aff.catalog.discount.request
tibco.ac.pricemodel.topic tibco.aff.catalog.price.request
tibco.ac.planfragmentmodel. topic tibco.aff.catalog.planfragment.request
Note: A bridge does not need to be created for the Segment Model because it is not required by the core components. OCS loads the segment model in a different way. See OCS deatils in TIBCO Fulfillment Order Management User's Guide for more details.

This software has separate listeners on each queue mentioned in the earlier table. On receiving the JMS message, corresponding to a particular model, TIBCO Fulfillment Order Management processes it using Model Processing.