Currently as part of an integration initiative we are design the following integration Flow:
1) We have one single requester Application; We design the related ABCS requester
2) We Use on single EBS. We are using the Synch operation of the EBS
3) We have 2 Provider ABCS
Our business requirement is as follows:
if a single message is fired from the requester application through the requester ABCS, it has to be published to both of the provider applications through the provider ABCS components. In fact one single requester ABCS instance will be created, one single EBS instance and 2 Provider ABCS instance have to created
Can you please suggest how we can design the EBS service in such way that 2 Provider ABCS instances will be created from on single EBS instance
Have you had a chance to look at the chapter ' Working with AIA Design Patterns' in the IDG?
I don't know the exact details of your usecase from your post, but I would suggest you to go through some of the design patterns described in detail in the above chapter- 'Guaranteed delivey pattern' in particular.
Let us know if that suits your requirements.
Thanks for your reply. I have gone through the AIA Design Pattern. It is helpful I think. A small doubt please:
Does a mediator can initiate 2 service calls a the same time. If yes can you please share some insights
The answer to your question is Yes, a single mediator can invoke two service calls at same time as well.
First, define your service references in the composite.xml
Once you have done that, you can add any number of routing rules for each operation defined in the mediator. In your case, you will need to add two static routing rules within the same operation in the Mediator file. You can also select whether the calls will be sequential or parallel by selecting correct value in the dropdown inside the routing rule. Each routing rule will invoke one service reference in your case.