Multi-Tenancy Configuration

To use the multi-tenancy feature for Order Management Server, configure the appropriate properties as necessary.

Note: When there are multiple tenants in TIBCO Order Management - Long Running, then you must specify the TENANTID in the TDS requests so that the order management system knows which tenant the request is related to.

Database details for the admin schema are provided in ConfigValues_OMS.xml under the category "Data Source Configuration" and the database details for the default tenant are provided in ConfigValues_OMS.xml under the category "Data Source Configuration Default Tenant".

You can use the following property under the category "Orchestrator Configuration" to determine messages sent to the process component is sent to a new JMS destination or not: 
<ConfValue description="Flag to enable or disable using the tenant specific destination for process component" isHotDeployable="true" name="Tenant specific destination for process component destinations" propname="com.tibco.fom.orch.tenantSpecificDestination" readonly="false" sinceVersion="3.1" visibility="Basic">
	<ConfBool default="false" value="false"/>
</ConfValue>

If this property is set to true, the messages are sent to a JMS destination prefixed with the tenant ID to the existing destination as follows:

<TENANTID>.tibco.aff.orchestrator.planItem.execute.request

Along with the existing property com.tibco.fom.orch.overridePlanfragmentDestination, the new flag com.tibco.fom.orch.tenantSpecificDestination works in the following manner:
  • If com.tibco.fom.orch.overridePlanfragmentDestination is set to true and com.tibco.fom.orch.tenantSpecificDestination is set to false, the messages are sent to the configured destination for the respective process component.
  • If com.tibco.fom.orch.overridePlanfragmentDestination is set to false and if com.tibco.fom.orch.tenantSpecificDestination is true, then
    • if the owner is defined for this process component, the JMS destination is tibco.aff.orchestrator.planItem.<planFragment-owner>.execute.request.
    • if the owner is not defined for this process component, the JMS destination is <TENANTID>.tibco.aff.orchestrator.planItem.execute.request.
  • If com.tibco.fom.orch.overridePlanfragmentDestination is set to false and if com.tibco.fom.orch.tenantSpecificDestination is false, then
    • if the owner is defined for this process component, the JMS destination is tibco.aff.orchestrator.planItem.<planFragment-owner>.execute.request.
    • if the owner is not defined for this process component, the JMS destination is tibco.aff.orchestrator.planItem.execute.request.
Note: By default, both properties are set to false.