Online Model Loading

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

You can invoke the catalog publish workflow in TIBCO Product and Service Catalog directly by using the sample SOAP web service requests available in the $OM_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 Product and Service 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 Product and Service Catalog is deployed and running.

Refer to the TIBCO Product and Service Catalog documentation for more details.

The sample request to invoke TIBCO Product and Service Catalog workflow for publishing product catalogs are available in $OM_HOME/samples/Online_ProductModel_Publish_Request.xml.

TIBCO Product and Service Catalog publishes the models on respective topics as mentioned in the following table:

Model (Catalog) TIBCO Product and Service Catalog JMS Topic
Product tibco.ac.productmodel.topic
Action tibco.ac.actionmodel.topic
Plan Fragment tibco.ac.planfragmentmodel.topic

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

TIBCO Product and Service Catalog Source Topic TIBCO Order Management - Long Running Target Queue
tibco.ac.productmodel.topic tibco.aff.catalog.product.request
tibco.ac.actionmodel.topic tibco.aff.catalog.action.request
tibco.ac.planfragmentmodel. topic tibco.aff.catalog.planfragment.request
Note: A bridge does not have to be created for the Segment Model because it is not required by the core components. Order Capture System loads the segment model differently. See Order Capture System details in TIBCO Order Management - Long Running 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 Order Management - Long Running processes it using Model Processing.