Integration with Orchestrator
The integration between AOPD and Orchestrator is configured in the file $AF_HOME/roles/configurator/standalone/config/ConfigValues_OMS.xml, in the category called Orchestrator-AOPD Integration Configuration. This configuration can be accessed and modified using the Web Configurator.
| Parameter Name | Description |
|---|---|
| OPDRequest from Orchestrator receiver queue | Name of the OPDRequest from Orchestrator receiver queue (default: tibco.aff.orchestrator.provider.order.opd.request) |
| OPDRequest from Orchestrator receiver count | Number of the OPDRequest from Orchestrator receiver (default: 3) |
| ExecutionPlanNewRequest to AOPD sender queue | Name of the ExecutionPlanNewRequest to AOPD sender queue (default: tibco.aff.ocv.events.plan.new.request) |
| ExecutionPlanAmendRequest to AOPD sender queue | Name of the ExecutionPlanAmendRequest to AOPD sender queue (default: tibco.aff.ocv.events.plan.amend.request) |
| ExecutionPlanNewResponse from AOPD receiver queue | Name of the ExecutionPlanNewResponse from AOPD receiver queue (default: tibco.aff.ocv.events.newplan.reply) |
| ExecutionPlanNewResponse from AOPD receiver count | Number of the ExecutionPlanNewResponse from AOPD receiver (default: 3) |
| ExecutionPlanAmendResponse from AOPD receiver queue | Name of the ExecutionPlanAmendResponse from AOPD receiver queue (default: tibco.aff.ocv.events.amendplan.reply) |
| ExecutionPlanAmendResponse from AOPD receiver count | Number of the ExecutionPlanAmendResponse from AOPD receiver (default: 3) |
| OPDResponse to Orchestrator sender queue | Name of the OPDResponse to Orchestrator sender queue (default: tibco.aff.orchestrator.provider.order.opd.reply) |
Copyright © Cloud Software Group, Inc. All rights reserved.