on 12-01-2015 4:52 PM
Hello Friends,
I am working on redesigning of a ccBPM to NW BPM. In the ccBPM, we were sending direct messages to a third party(file) and an ECC system(idoc).
But when converting this functionality to NWBPM, I think there is no option that we can send the messages from NW BPM to a third party directly, we have to involve PI.
I mean the only flow allowed is
PI -> NW BPM -> PI -> ECC
but not
PI -> NW BPM -> ECC.
Tried to find out whether we can send the messages to other parties / systems via BPM but didn't find any example nor in SAP documentation. So my assumption is that it is a must that we involve PI in between.
The only thing I can think of a system can work on XI 3.0 protocol via SOAP adapter, then its possible. Can you comment please.
Hello Ravi,
you can directly send messages to ECC via RFC and third party webservices using application communication.
For rest all scenarios you need to have PI.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ravi
I don't recall being able to send a message directly from ccBPM to a target system. For ccBPM design, you still have to design a configuration scenario to route from ccBPM as sender to the target system. This means any message out of ccBPM goes through PI's integration engine before reaching the target system.
The approach with NW BPM is exactly the same. You can to route a message out of NW BPM through a PI iFlow/ICO.
ccBPM and NW BPM are used to design and control the flow of process, messaging to/from backend systems still goes through PI.
Rgds
Eng Swee
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Eng Swee,
Thats what I wanted to say - we could use ccBPM as a sender and send the messages to a receiver. By 'Direct' I meant to say, unlike NW BPM which first sends the message to PI and then PI takes care.
For example - if the result from BPM processing needs to be sent to a third party as a file, in case of ccBPM, we would configure the message from ccBPM to third party by configuring receiver determination / interface determination and receiver agreement, so sender here is ccBPM and target is third party.
But here in NWBPM, we first need to route the message to PI (One ICO) and then PI would another ICO to send the file to third party. I hope you get my point which is - NWBPM is not the direct sender unlike ccBPM
Eng Swee, I have already checked this one and many more over SDN. I didn't find what I am looking for. (NWBPM -> Third party). The link you copied also talks about NWBPM -> PI only.
If you look closely, almost every blog tells about NWBPM -> PI, not NWBPM -> third party.
And hence my query here. As Raghu mentioned (and my understanding as well), we can not send the direct messages to third parties. We have to first send the message to PI from NWBPM and then PI takes care of that message. Its not a one to one transformation when comparing with ccBPM.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.