Configuring order orchestration properties

The yfs.properties_orch.ext.in file contains the order orchestration properties and is located in the <OMS_Runtime>/properties directory.

You can configure these properties, which are described in the following table in one of the following ways based on whether the property has database support allowed or not:
  • By adding or overriding them in the customer_overrides.properties file.
    Note: You must add "yfs" as prefix when you override these properties in the customer_overrides.properties file.
  • By adding or overriding them in the properties database using Property Management user interface. Learn more...
    Note: Only those properties which have database support can be added to the properties database using this UI.

Order orchestration property value and description

Property Database Support Description
orch.service.providerurl N Provider URL used by integration servers configured in the order orchestration services.
orch.service.internal.qcf Y JMS ConnectionFactory name used by integration servers configured in the order orchestration services.
orch.service.order.create.event.queue Y Queue name used by order orchestration validation service ProcessOrderValidation.
orch.service.trigger.order.decomp.queue Y Queue name used by order orchestration decomposition service TriggerDecomp.
orch.service.trigger.buildplan.queue Y Queue name used by order orchestration execution service TriggerBuildPlan.
orch.service.evaluate.dependency.queue Y Queue name used by the order orchestration service EvaluateOrderDependency.
orch.rulesEngine.validation.URL N URL for invoking business rules engine for the order orchestration validation service.
orch.rulesEngine.decomp.URL N URL for invoking business rules engine for the order orchestration decomposition service.
orch.rulesEngine.buildPlan.URL N URL for invoking business rules engine for the order orchestration execution service.
orch.rulesEngine.validation.RequestParameters N Request parameters for invoking business rules engine for order orchestration validation service. The value of this property must be in the format "name1=value1&name2=value2.....&namex=valuex".
orch.rulesEngine.decomp.RequestParameters N Request parameters for invoking business rules engine for order orchestration decomposition service. The value of this property must be in the format "name1=value1&name2=value2.....&namex=valuex".
orch.rulesEngine.buildPlan.RequestParameters N Request parameters for invoking business rules engine for order orchestration execution service. The value of this property must be in the format "name1=value1&name2=value2.....&namex=valuex".
orch.service.validation.flowname.invokerules Y The service flow name that needs to be invoked when application call the rules engine for validation. By default, the value is set to the application-provided sample validation rules implementation.

For example:

orch.service.validation.flowname.invokerules=InvokeValidationRulesSample

orch.service.validation.flowname.mapping Y The service flow name that needs to be invoked for mapping order data to the rules engine input for validation. By default, the value is set to the application-provided sample validation rules implementation.

For example:

orch.service.validation.flowname.mapping=PrepareMappingForValidationSample

orch.service.decomp.flowname.invokerules Y The service flow name that needs to be invoked when application call the rules engine for decomposition. By default, the value is set to the application-provided sample validation rules implementation.

For example:

orch.service.decomp.flowname.invokerules=InvokeDecompRules
orch.service.decomp.flowname.mapping Y The service flow name that needs to be invoked for mapping order data to the rules engine input for decomposition. By default, the value is set to the application-provided sample validation rules implementation.

For example:

orch.service.decomp.flowname.mapping=PrepareMappingForDecomp
orch.service.buildPlan.flowname.invokerules Y The service flow name that needs to be invoked when application call the rules engine for execution. By default, the value is set to the application-provided sample validation rules implementation.

For example:

orch.service.buildPlan.flowname.invokerules=InvokeBuildPlanRules

orch.service.buildPlan.flowname.mapping Y he service flow name that needs to be invoked for mapping order data to the rules engine input for execution. By default, the value is set to the application-provided sample validation rules implementation.

For example:

orch.service.buildPlan.flowname.mapping=PrepareMappingForBuildPlan

What to do next:
  • Update the Sterling Order Management System Service runtime sandbox by building and deploying configuration and properties extensions. Learn more...