Override Planfragment Destination

You can use the following property under the category 'Orchestrator Functional Configuration' to determine messages sent to the process component is sent to a new JMS destination or not:

{
          "propName": "tenantSpecificDestination",
          "propDescription": "Flag to enable or disable using the tenant specific destination for process component",
          "propValue": "false",
          "valueType": "string",
          "isTenantProperty": "true"
        }

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 overridePlanfragmentDestination, the new flag tenantSpecificDestination works in the following manner:

  • If overridePlanfragmentDestination is set to true and tenantSpecificDestination is set to false, the messages are sent to the configured destination for the respective process component.
  • If overridePlanfragmentDestination is set to false and if 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 overridePlanfragmentDestination is set to false and if 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.