Defining integration properties

You can set up communication between JDA and Sterling Order Management System Software by defining the integration properties.

About this task

To set up communication between JDA and Sterling Order Management System Software, you must define properties in the customer_overrides.properties file by building the EAR. When you build the EAR, all the setup files automatically run.

The following sample customer_overrides.properties file shows all properties and their values.

This procedure assumes that you want to define queue variables for services that are related to all integration functions. For information about how to set up a Connection Factory for WebSphere MQ, see the MQ V7.5 IBM® Documentation. You can create Connection Factories by using the JMS administration tool.

Note: After the creation of a resource pool, the deliveryMethod or the CapacityUOM can not be changed.
The following code is a sample from the customer_overrides.properties file:
yfs.ibmjda.integration.providerurl=corbaloc::
    <SC_host_where_MQ_QFC_and_JNDI_names_are_defined>:<WAS_bootstrap_port>
yfs.ibmjda.integration.providerurl=t3://localhost:7001
yfs.ibmjda.integration.apis.export.qcf=AgentQCF
yfs.ibmjda.integration.apis.import.qcf=AgentQCF
yfs.ibmjda.integration.apis.internal.qcf=AgentQCF
    
yfs.ibmjda.integration.apis.import.queue=DefaultAgentQueue

yfs.ibmjda.integration.apis.releaseOrder.event.queue=DefaultAgentQueue
yfs.ibmjda.integration.apis.closeOrder.event.queue=DefaultAgentQueue
yfs.ibmjda.integration.apis.scheduleOrder.event.queue=DefaultAgentQueue
yfs.ibmjda.integration.apis.releaseOrderTO.event.queue=DefaultAgentQueue
yfs.ibmjda.integration.apis.createShipmentTO_Int.queue=DefaultAgentQueue
yfs.ibmjda.integration.apis.receiveOrderTO_Int.queue=DefaultAgentQueue
yfs.ibmjda.integration.apis.UpdtandCnfShipmentTO_Int.queue=DefaultAgentQueue

yfs.ibmjda.value.mapping.file=/INSTALL/<INSTALL_DIR>/properties/IBMJDAValueMaps.xml
The following table describes the default values for each of these integration properties:
Property Description
yfs.ibmjda.integration.providerurl Provider URL for integration. Use the corbaloc::<SC_host_where_MQ_QCF_and_JNDI_names_
are_defined>:<WA_bootstrap_port> format for the URL.
yfs.ibmjda.integration.apis.export.qcf Queue Connection Factory for outbound messages.
yfs.ibmjda.integration.apis.import.qcf Queue Connection Factory for inbound messages.
yfs.ibmjda.integration.apis.internal.qcf Queue Connection Factory for internal Sterling Order Management System Software usage.
yfs.ibmjda.integration.apis.import.queue Queue to which messages from JDA to Sterling Order Management System Software are written.
yfs.ibmjda.integration.apis.releaseOrder.event.queue Queue that is used to post order details to the JDA shipping warehouse management system.
yfs.ibmjda.integration.apis.closeOrder.event.queue Queue that is used to post the closed sales order details to JDA Demand.
yfs.ibmjda.integration.apis.scheduleOrder.event.queue Queue that is used to post return order details for JDA.
yfs.ibmjda.integration.apis.releaseOrderTO.event.queue Queue to which the transfer order release messages from Sterling Order Management System Software are written to JDA.
yfs.ibmjda.integration.apis.createShipmentTO_Int.queue Internal queue that is used for transfer order create shipment.
yfs.ibmjda.integration.apis.receiveOrderTO_Int.queue Internal queue that is used to receive a transfer order.
yfs.ibmjda.integration.apis.UpdtandCnfShipmentTO
_Int.queue		 Internal queue that is used for the transfer order update and confirm shipment.
yfs.ibmjda.value.mapping.file The absolute path to IBMJDAValueMaps.xml must be specified. If the path is not specified, the application searches in the <INSTALL_DIR>/properties folder.
Important: The path to IBMJDAValueMaps.xml must be accessible from the application server.
For more information about the IBMJDAValueMaps.xml file, see Defining and deploying the IBMJDAValueMaps.xml file.
yfs.ibmjda.integration.apis.WfmrIntegration.
serviceSlotGroupId		 This property is used to send the Service Slot Group ID of Service Slots and Service Slot Groups from JDA to Sterling Order Management System Software.
Note: Once a Service Slot Group ID is configured, it cannot be changed.

Procedure

  1. Define properties in the sample <INSTALL_DIR>/properties/customer_overrides.properties file.
  2. To specify different properties for each process you are running, add -DVendorFile to the start script and set it to <path to your custom servers.properties file>. You must have different servers.properties and customer_overrides.properties files for each process that you are running. In the servers.properties, change the entry for customer_overrides.properties to point to your new customer_overrides.properties file. Do the following based on the -DVendorFile filepath:
    • If the value is a full path, the customer_overrides.properties file is outside of the EAR.
      1. Restart the application server.
    • If the value is a relative path, the customer_overrides.properties file is inside of the EAR.
      1. Create the resources.jar file by running:
        • UNIX <INSTALL_DIR>/bin/deployer.sh -t resourcejar
        • Windows <INSTALL_DIR>/bin/deployer.cmd -t resourcejar
      2. Re-create the EAR file, which is nothing but the EAR package. For more information about creating and deploying the EAR file, see Building and deploying the EAR on the server.