on 08-24-2010 5:23 AM
Hi,
My requirement is to have asynchronous communication from my sender to PI. Now I initially planned to use SOAP sender adapter, but in this case the WSDL that we generate does not contain reliable messaging specifications.
1. I need to have reliable messaging between sender to PI, can I achive this through SOAP or I need to go for WS adapter.
2. Also if achievebale through SOAP let me know how I can have this parameter in WSDL???
3. Would appriciate for any blog links for WS with reliable messaging, I cannot see reliable messaging under my WS sender adapter
Regards,
Siddhesh S.Tawate
PS: I am working on SAP PI 7.11
Hi Siddhesh,
Refer the below link:
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hareenkumar,
WS-RM standard is supported over the WS adapter, not SOAP adapter.
It even says so in the document you linked yourself.
Implementation in SAP NetWeaver PI 7.1
The SOAP adapter as of today supports already asynchronous messaging, however with proprietary means
since there was no standard available before, now the WS-RM protocol is supported via an own entry in the
integration engine (implemented in ABAP) and not the adapter engine.
Best regards,
Henrique.
Hi,
In case of WS sender and receiver adapter, the reliable messaging parameters are missing. I am working on SAP PI 7.11.
Is there any settings to be done through NWA or any services to be activated.
Under SICF the SOAP_APPL_Management and WS related services have been activated. I have also executed the WS_Setup report program.
Regards,
Siddhesh S.Tawate
Hi,
We had a similar issue where the message triggered by SOAP UI with WS-RM ticked as 'True' used to work and the one sent from SAP PI used to fail.
I had used the SOAP channel for Synchronous connectivity.
How this was achieved with SOAP Adapter is, I had used a XSLT mapping ahead of Message Mapping and ticking 'Do Not Use SOAP envelope' in SOAP channel.
The XSLT mapping was to for the additional tags like <wsrm:Sequence> , <wsrm:Identifier> , <wsa:MessageID>, <wsa:Action> which were getting additionallly created.
The SOAP structure was created and the SOAP body was taken from SAP PI message (with <xsl:copy-of select="/*" /> ).
This worked
Regards,
Rohan
This is one of the guides for WS adapter reliable messaging. You may search SDN and will surely find many such articles.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.