As part of the meta-driven architecture, Adeptia’s SOA framework orchestration engine allows dynamic usability of services at run-time based on business rules. Ability to dynamically discover and incorporate a service within a process run-time is one of the key advantages of using Adeptia Integration Suite.
In this example we will talk about how to dynamically call a service in an orchestration. One of the integration design pattern for an orchestration would be to identify based on the source data what specific service to call that would process that information. Typically developers would hard-code the entire logic inside the one flow and that makes it difficult to manage going forward. Taking a modular design approach helps in separating out the specific logic for data integration into separate services.
Below is an example of the Adeptia Integration process flow where Purchase Orders are verified and based on a Client ID a different service is called to process that PO. Each client may have different processing needs or data transformation rules. Separating out the transactional rules into different sub processes or services helps in managing the clients efficiently and also makes the management of the processes simpler.
Parent process uses context variables to dynamically pass the sub process ID in the Call action. It also uses Set-Child-Context to pass the data stream into that service. Gateway condition checks for any errors in the incoming data file. If the data is correct then the valid path is taken and sub process is called that would execute the PO for that client. Else if there are errors then the Error route is taken and an error handling sub process is called.
Here's a summary of the key design elements used in the flow above:
1. Get PO is an http source. It can be any source type.
2. Copy the source PO data into three streams using the Repeater Service
3. After the source is parsed the data is taken to the "Identify PO" mapping which has a database lookup to check which matching process ID is needed to call. This ID is then used by the put context var to assign the ID to the Call action.
4. Identify PO mapping also has a context variable called Error. If the PO is not valid based on any business rule then this variable is set to true. This variable is then used in the Gateway to check which route to take.
5. Put context variable assigns the process flow ID to the Call action.
6. Context target is used to pass the source data into a variable (key) that is then passed in the Set Child Context action.
Refer to the Set Child Context information available in the forum to see what properties are needed to pass data to a child flow. It has Key, ChildKey and ChildName (which is the name of the Call action) as parameters that need to be set so that the data is passed successfully to the child flow. Purpose of the Child key is to act as a receiving parameter in the sub process which would accept this data stream.
Key variable in the Set-Child-Context is the name of the parameter defined in the Context Target. Suppose it is called 'data'.
ChildKey in the Set-Child-Context is the name of the variable in the Context Source of the sub process that would receive this data. Suppose it is called 'receiver'.
Here's a snapshot of how to call a service in the process flow:
The database lookup which is done in the "Identify PO" mapping step is looking for the matching Client ID in a rules table. This table can have a front-end web form that developers can fill with the service IDs and the matching Client IDs. Example of the web form is shown below:
Above process also has a gateway condition to check if there are errors in the PO. If there are errors then an error handling service is called whose task is to correct and resubmit the errors back into the process. If you need assistance on how to build a similar process template at your local Adeptia instance please contact email@example.com.