Enterprise Orchestrator integration
Enterprise Orchestrator is an orchestration service that can trigger BaaS services.
Refer to the Enterprise Orchestrator documentation for more information.
Enterprise Orchestrator implementation
When you add the Enterprise Orchestrator handler, a new implementation class called "EnterpriseOrchestratorHandler" is created. This class handles incoming requests using input variables and supports sending responses with output variables.
The input variables can be used to trigger custom logic, such as processing data from API calls. All Enterprise Orchestrator calls are asynchronous. As a result, the Queue handler is required in the services.
The Enterprise Orchestrator handler depends on the Queue handler because all requests are processed asynchronously, and the queue is used to manage this process. All log entries related to these requests will appear in the Queue log.
Configuration
The manifest defines an eoHandler with input and output variables. These variables are displayed in the Enterprise Orchestrator client when defining the orchestration. Use the variable names from the manifest in your implementation to ensure proper configuration.
When working with variables in the implementation, use the same names as configured in the manifest.
Example: Manifest
Example configuration for input and output variables:
```json
"eoHandler": {
"enabled": true,
"inputVariables": [
{
"name": "MyInput",
"dataType": "string"
}
],
"outputVariables": [
{
"name": "MyOutput",
"dataType": "string"
}
]
}
```