Multi-Tenancy Configuration

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

Database details for the admin schema is provided in ConfigValues_OrchService.xml under the category "Admin Data Source Configuration".

You can use the following property under the category "Orchestrator Engine 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] Tenant specific destination for process component destinations" propname="tnt##tenantSpecificDestination" readonly="false" sinceVersion="5.0" visibility="Basic">
				<ConfString default="false" value="[{TENANT:'TIBCO',VALUE='false',TYPE:'ConfBool'}]"/>
			</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 tnt##overridePlanfragmentDestination, the new flag tnt##tenantSpecificDestination works in the following manner:
  • If tnt##overridePlanfragmentDestination is set to true and tnt##tenantSpecificDestination is set to false, the messages are sent to the configured destination for the respective process component.
  • If tnt##overridePlanfragmentDestination is set to false and if tnt##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 tnt##overridePlanfragmentDestination is set to false and if tnt##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.