This content has been marked as final. Show 2 replies
1) You're using the ODSI ws client to call an sb protocol proxy service. That doesn't work. The ODSI ws client only knows how to call ODSI webservices (or webservices that look like ODSI web services).
2) You would make your life a lot easier if you simple combined whatever you need done in your multiple calls to ODSI into a single data service. But you don't need to.
3) In your picture, it's not clear if the multiple calls to ODSI are done within the same proxy-service call, or if multiple client calls are required. If they are in the same proxy-service call, then all you need is your proxy-service to manage the transaction (an OSB person should be able to tell you how to get that - perhaps it is the default). If your proxy-service is managing the transaction, then it doesn't matter how that proxy-service is being called. But if it requires multiple client calls, then the client has to manage the transaction.
For testing the case of a transaction across multiple ODSI calls within an OSB pipeline, we used a JMS proxy-service. There may be other types of proxy-services that are transactional - check the OSB doc.