Hello gurus,
I'm in trouble with my design for scenarios using SAP, PI, nonSAP systems. There are 6 systems that are all customly developed for business needs and they all run on J2EE application systems. These systems needs to be integrated to SAP using PI with SOAP adapter and ABAP proxies.
The problem exists for EO and EOIO scenarios.
None of these systems has any messaging infrastructure. For inbound interfaces, I cannot monitor application level errors that might happen while processing in these java systems. I do not want to return SOAP fault to PI, but should be able to log, monitor and raise notifications for relevant application system support teams. This by itself requires custom java applications to be developed.
Moreoever, when they send messages to PI, if PI is down, the messages will just run into HTTP timeouts. Again, I need to be able to record them in database before sending and should be able to restart those messages later when PI is up.
Also, the toughest part, I have EOIO interfaces. That means, apart from monitoring and restarting, I need a queueing mechanism so that I can make sure these systems process EOIO messages in correct order for inbound & outbound messages.
As SAP systems already have a PI runtime, we don't have any problems on that side. But, it seems like we have to develop similar logic customly for Java systems.
So all these custom developments puts a lot of extra effort to our project. Which way can we follow to at least lessen it? Any already developed solutions, workarounds?
Thank you for your inputs.
Regards,
Gökhan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.