Defining JMS queue variables in the properties file

You can use this information to define JMS queue variables for communication services.

About this task

To set up communication between an Order server and the Promising server in IBM® Sterling Order Management, you must define the JMS queue variables for these services in the Sterling Order Management customer_overrides.properties file and run the setupfiles script before deployment. This sample customer_overrides.properties file shows all of the properties, followed by a table that describes the services associated with these properties.

The following is a sample customer_overrides.properties file:

yfs.prms.integration.icf=com.ibm.websphere.naming.WsnInitialContextFactory
yfs.prms.integration.apis.sendexternalsupplyupdates.event.queue=SupplyUpdateQueue
yfs.prms.integration.supply.providerurl=corbaloc:iiop:wesb_server:2809
yfs.prms.integration.apis.supply.qcf=SupplyUpdateQCF
yfs.prms.integration.apis.sendexternaldemandupdates.event.queue=DemandUpdateQueue
yfs.prms.integration.demand.providerurl=corbaloc:iiop:wesb_server:2809
yfs.prms.integration.apis.demand.qcf=DemandUpdateQCF

Note: All of the properties in this sample file must be present in the customer_overrides.properties file.

The following table displays the drop-down options for the initial context factory type, yfs.prms.integration.icf:

Initial context factory type	Value
WebSphere MQ	com.ibm.websphere.naming.WsnInitialContextFactory
WebLogic	weblogic.jndi.WLInitialContextFactory
JBoss	org.jnp.interfaces.NamingContextFactory
TIBCO	com.tibco.tibjms.naming.TibjmsInitialContextFactory
File	com.sun.jndi.fscontext.RefFSContextFactory

Following are the Sterling Order Management properties, along with their associated services.

Property	Description	Services associated with property
yfs.prms.integration.apis.sendexternalsupplyupdates.event.queue	Queue name for supply updates for Promising server integration	SendExternalSupplyUpdates
		ProcessExternalSupplyUpdates
yfs.prms.integration.supply.providerurl	Value of the provider URL for the supply updates queue for Promising server integration	SendExternalSupplyUpdates
yfs.prms.integration.supply.providerurl		ProcessExternalSupplyUpdates
yfs.prms.integration.apis.supply.qcf	Value of connection factory for the supply updates queue for Promising server integration	SendExternalSupplyUpdates
yfs.prms.integration.apis.supply.qcf		ProcessExternalSupplyUpdates
yfs.prms.integration.apis.sendexternaldemandupdates.event.queue	Queue name for demand updates for Promising server integration	SendExternalDemandUpdates
		ReceiveExternalDemandUpdates
yfs.prms.integration.demand.providerurl	Value of provider URL for the demand updates queue for Promising server integration	SendExternalDemandUpdates
yfs.prms.integration.demand.providerurl		ReceiveExternalDemandUpdates
yfs.prms.integration.apis.demand.qcf	Value of connection factory for the demand updates queue for Promising server integration	SendExternalDemandUpdates
yfs.prms.integration.apis.demand.qcf		ReceiveExternalDemandUpdates
yfs.prms.integration.icf	Initial context factory for Promising server integration	SendExternalSupplyUpdates
		ProcessExternalSupplyUpdates
		SendExternalDemandUpdates
		ReceiveExternalDemandUpdates

Perform the following procedure on both the Order server and the Promising server.

Procedure

UNIX: Open the INSTALL_DIR/properties/customer_overrides.properties file.
Windows: Open the INSTALL_DIR\properties\customer_overrides.properties file.
Note: If customer_overrides.properties does not exist, create this file.

Define the properties as shown in the sample customer_overrides.properties file above.
UNIX: Run the INSTALL_DIR/bin/setupfiles.sh script.
Windows: Run the INSTALL_DIR\bin\setupfiles.cmd script.
Create and deploy the EAR.