Request Response Bean for SOAP Sender Adapter

Hi Friends,
Is it possible to use Request Response Bean Module described (FIle to RFC to File here) for SOAP(sender) and JDBC(receiver) adapter?
I want to configure SOAP to JDBC to JDBC scenario.
http://wiki.sdn.sap.com/wiki/display/HOME/UsingRequestResponseBeanModuleinFILE+Adapter
Scenario:
I will do SOAP adapter call Asynchronously and JDBC receiver adapter will select data from database. This response will go back to SOAP adapter and then SOAP will divert this response to another JDBC adapter. This JDBC adapter will insert data into another database.
I do not want to use ccBPM. Is there any design approach to implement this scenario?
Thanks,
Sandeep Maurya

Hi Sandeep,
SAP says SOAP sender adapter does not support Modules. You can serch Help.sap (for SOAP sender channel) to find the same.
I would suggest to use AXIS adapter (provides all the functionality of SOAP) and supports the Modules as well.
I have used the Module beans that you mentioned in the past... but it is not consistent with its processing.. sometimes it stucks with Message ID issue... I have seen same issue faced some other friends as well .. search on SDN you will find the issue with these modules...
Using BPM would be another option...
Thanks,
Sunil Singh

Similar Messages

Using Request Response Bean Module in FILE Adapter

Hi Experts,
Can we use Request Response Bean Module in FILE Adapter in reverse way. That is can we configure thses adapter modules in Reciever file channel and call a sender file channel in it?
My case is RFC to File synchronous case? How do we do this?
Thanks & Regards,
priyanka

Can we use Request Response Bean Module in FILE Adapter in reverse way. That is can we configure thses adapter
modules in Reciever file channel and call a sender file channel in it?
My case is RFC to File synchronous case? How do we do this?
The above is not possible....Bean works only for Sender channel and not for Receiver.....requirement not possible using even a BPM as FILE does not support SYNC communication in receiver end......max you can do is split the scenario into SYNC-ASYNC bridge.
Regards,
Abhishek.

Reading Header data in a SOAP Envelope for SOAP Sender Adapter

Hello All,
Am using a SOAP sender adapter and want to use the data inside the SOAP Header for some routing purpose(extended receiver determination). Any SOAP message coming into XI will look something like below. But XI will pass the contents of <SOAP-ENV:Body> to Payload and <SOAP-ENV:Header> to the SOAP Header category you can see that in SXMB_MONI.
Is there a way to read the data in my SOAP Header to be later used in my extended receiver determination.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:Q-ENV="/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <SOAP-ENV:Header>
          <Q-ENV:Header>
               <Q-ENV:Sender-Id>1</Q-ENV:Sender-Id>
               <Q-ENV:Receiver-Id></Q-ENV:Receiver-Id>
               <Q-ENV:Correlation-Id></Q-ENV:Correlation-Id>
               <Q-ENV:Message-Id></Q-ENV:Message-Id>
               <Q-ENV:Date-Sent></Q-ENV:Date-Sent>
               <Q-ENV:Document-Type></Q-ENV:Document-Type>
               <Q-ENV:Message-Format></Q-ENV:Message-Format>
          </Q-ENV:Header>
     </SOAP-ENV:Header>
     <SOAP-ENV:Body>
          <Q-ENV:Body>
               <Q-ENV:Content-Type>text/xml</Q-ENV:Content-Type>
               <Q-ENV:Message-Type></Q-ENV:Message-Type>
               <Q-ENV:Encoding>UTF-8</Q-ENV:Encoding>
               <Q-ENV:Message-Body>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Thanks for your replies in advance.
Regards,
Prashanth

Hello,
but they were not getting any response back from XI and the sending system kept resending the message.. may be it was acting like a HTTP post.
The method that is used by the native SOAP Adapter is always HTTP Post. Not sure why you are not getting a response, have you checked the outbound firewall of the sending party or the inbound firewall of XI? To which SOAP URL are you sending to?
Hope this helps,
Mark

Only HTTPS requests are working for SOAP Sender and HTTP not working

wHi Experts,
We have enabled our HTTPS port ( SSL ) in NWA -- >> Security -- >> SSL and Key stores. So understanding is HTTPS port is now enabled on top of HTTP. So PI should be able to cater requests at both ports.
Now, we have developed a synchronous SOAP to RFC scenario and downloaded WSDL file. This file has both links -
a. http:<host>:<port>
b. https:<host>:<port>
We intend to make a PI system where both ports can work. Now questions.
1. When we test web service exposed from PI using SOAPUI tool, only HTTPS works fine and gets the response back. If we try HTTP URL, an error is encountered - HTTTPS scheme is required.
2. Is this whole understanding that both ports ( HTTP, HTTPS ) should be able to operate simultaneously correct ? Or this is not at all possible ?
3. In SOAP Sender, we tried selecting all 3 options - 1. HTTP 2. HTTPS without client authentication 3. HTTPS with client authentication.
None of the options have any effect on testing, Each time, only HTTPS request works and HTTP doesn't.
Can anyone please provide some hints for troubleshooting ?
Thanks..
regards,
Rajagopal.

The error "HTTPS scheme is required" is normally returned when the HTTP Security Level on the SOAP adapter is not set to "HTTP". I can see you have mentioned you have tried all these, maybe a cache refresh has gone wrong? Could try recreating the channel with just HTTP specified as security level and this should allow HTTP or HTTPS
I assume you are using a different port number for your HTTP and HTTPS requests from SOAP UI. Normally the HTTPS port is the same as the HTTP port number but the final zero changed to a 1 i.e. https://<host>:50001 instead of http://<host>:50000.
You should be able to confirm both HTTP and HTTPS work OK by loading some of the system webpages in a browser over HTTP and over HTTPS i.e. http://<host>:<port>/nwa and https://<host>:<port>/nwa
Chris

Sender adapter request response bean not working for calling a webservice

Hi All,
In PI 7.31, My scenario : SOAP sender Asynch-> PI -> HTTP Receiver Sync ->take response to call another webservice (SOAP)
I have configured request response bean and response one way bean in the sender adapter to make this work.
Attached the screenshot of the module config in the sender soap adapter. The final response from HTTP has to be used to call another webservice (not sender webservice)
This giving an error "couldn't retrieve binding values for sender to receiver etc etc ----------"
Has anyone configured response one way bean to call a webservice to submit? If so, please share the configuration details. And let me know if I am doing anything wrong
thx
mike

Hi Michael,
I think the adapter type is for the receiver channel looking at the documentation SAP Library - SAP Exchange Infrastructure
Have you checked your receiver channel doesn't belong to a party?
I havent tried this bridge with the http_aae but looks to be problematic according with Michal comment here http://scn.sap.com/community/pi-and-soa-middleware/blog/2014/01/28/generic-pi-async-sync-bridge-configuration-for-any-adapters#comment-454463
Regards.

Hi all, Please suggest a case where there is a requirement for new SOAP sender adapter module. I wanted to develop a module but in my current project i am unable to find any such requirement.

Hi all, Please suggest a case where there is a requirement for new SOAP sender adapter module. I wanted to develop a module but in my current project i am unable to find any such requirement. So please give me inputs for the same..
Thank you,
Vinay Kumar A

You can try converting a synchrnous soap call to asynchronous using a custom module
Here your module will send a response back to the sender system and make an asynchronous call forward

Adapter Module for SOAP Sender

Hi,
Any alternative way to create adapter module for soap sender?
Regards,
Farooq

But I just trying to know weather it will work for simple soap or not.
Unfortunately it wont work for the normal SOAP protocol.
Let me try my luck.
If you are successful, then I would waiting for a blog
Regards,
Abhishek.

Anonymous authentication requests via SOAP Sender adapter?

Hi,
Can someone please tell me whether it is possible to call the SOAP Sender adapter anonymously?
We can set user credentials for the receiver system adapter but looking at the options in the SOAP Sender communication channel I can't see how it is possible to send messages though SAP PI without a user who has authorisations to process messages.
Any advice greatly appreciated.
Thanks,
Alan

can't see how it is possible to send messages though SAP PI without a user who has authorisations to process messages.
The source system needs to use a user-id to send message to XI/ PI via SOAP.
If you do not want to use any authorization there is a way to switch off the authentication for the entire SOAP adapter (i.e. for all the SOAP scenarios)....not advisable.
This method was actually described in a discussion ages back
Regards,
Abhishek.

Use of variable header XHeaderName1 in SOAP sender adapter

Hi all,
I have a doubt regarding the use of adapter-specific attributes in SOAP sender adapter. In specific:
the SOAP client should be able to pass a variable with the SOAP request (XHeaderName1 header variable) and this should be available in mapping (Dynamic configuration)
I've already checked the [help page|http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm] but it seems I'm doing something wrong.
I tried with those settings in SOAP adapter configuration:
Keep headers checked
XHeaderName1 = Test
I try to call the SOAP adapters in the following 2 ways, but none works (the value is not available in message mapping with Dynamic configuration)
1. Pass "Test" value xxxx in SOAP Header as a tag
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Header>
          *<Test>xxxx</Test>*
     </SOAP-ENV:Header>
     <SOAP-ENV:Body>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
2. Pass "Test" value xxxx in SOAP URL
http://host:50000/XISOAPAdapter/MessageServlet?channel=p:s:c&version=3.0&Sender.Service=...&Interface=...&Test=xxxx
Could anyone give me a hint about how to pass those values in the SOAP call and eventually the correct config. of SOAP sender ?
Thanks a lot,
Manuel

Hi Manuel,
Could you give a bit more detail on how you handled the SOAP message yourself.
I have a similar issue. I am consuming a non SAP Web Service which requires a non-standard token element to be passed back. I have created a an RFC sender to SOAP reciever scenario which works fine for the inital logon and returns the token it expects in the follow up messages.
At present I'm at a loss so your help would be much appreciated. We have got round the immediate issue by creating and sending the SOAP message directly from SAP WAS.
Could we use the XI Adapter and ABAP proxy in a similar way?
Thanks,
Tim J.

Error while posting messages to SOAP sender adapter SP 13

Hi Friends,
I have configured a SOAP sender adapter in XI 3.0 and is using the URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
Message Servlet is in Status ERROR
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal not instantiated
ModuleProcessorRemote not instantiated
But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
<?xml version="1.0" ?>
<http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_EBTR_WEBSERVICE:CC_EBTR_WEBSERVICE_SOAP> <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
<name>CC_WEBSERVICE_SOAP</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>BS_WEBSERVICE</service>
</s:ChannelInfo
I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy we are getting a 500 internal server error.
Am not sure what causes the error ? I saw two notes in SDN related to SOAP - J2EE SP13. We are in SP13. Is this the issue ? Wanted to know your opinion before applying the notes.
Thanks & Regards,
Mathew

ABAP & Java stack was on different SP levels.

Using SOAP Sender adapter in PI 7.1

Hi Guys,
I've created a sync scenario with SOAP sender adapter, but I have troubles with calling it.
I use following URL: http://<host>:50000/XISOAPAdapter/MessageServlet?channel=:BS_Bus_Sys:CC_SOAP_Test as I did in XI 3.0, but I'm getting error HTTP 400 Bad Request. I'm using the request generated from the IR Configuration.
Has something changed in 7.1 for this type of scenario?
Thanks guys,
Olian

Hi! Olian,
I think u r going in a wrong way. The above given URL is wrong and incomplete one.
The above url comes only after generating the WSDL. You ill gives that URL to ur source team to post their data at which this URL itselfs acts as an Gateway to enter into SAP XI/PI.
The generated WSDL contains URL like this>>
"http:// Host:Port/XISOAPAdapter/MessageServlet?senderParty=&senderService=Business Service&receiverParty=&receiverService=&interface=SenderInterfaceI&interfaceNamespace=http://XXXXXXXX" />
Also follow the below procedure for generating the WSDL.
Except generating WSDL remaining all development steps are same as creating File to Proxy Scenario.
CREATING THE WEBSERVICE IN XI :
1) In Integration Directory, go to Tools tab --> Define Web Services.
2) Now one Wizard window will opens and follow the below steps:
Here donu2019t go for the u2018 Proposed URLu2019, instead specify the URL as::
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>
If there is party then ::
http://host:port/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>.
3) Specify the Source Messageu2019s Message Interface.and remaining other input parameters.
4) Specify the Sender Business Serviceu2019s details:
5) Here, Cross check the details displayed and then click on u2018Finishu2019 button to create the Web Service
document(WSDL)
6) Now Save the WSDL code to the local system. At the bottom u ill get URL based on the above input
URl:
Note: Here in XI there is no XML Testing tool or SOAP client tool to test SOAP messages. That is why most of the people prefer either ALTOVA XML SPY Tool or SOAP CLIENT TOOL or INFO PATH.
If your working on PI 7.1 means::
1) Simply after creating Sender Agreement go to options above to that sender agreement instead of tools menu... and there you can observe 2 options at the bottom side.
a) PUBLISH in SR
b) Generate WSDL.
2) Once after activating your ID componenets just Press or go for option Publish in SR. Then automatically it will generate WSDL and publish that WSDL in the SERVICE REGISTRY. which is latest concept in PI 7.1.
3) Now by entering authentification details you can able to enter into service registry.
There are 4 tabs::
a) Service definitions
b) Publish
c) classifications
d) Manage.
Go for Service definitions::
4) Enter your sender SOAP interface and press GO or enter.
5) Select your interface and then at the bottom u can observe again 4 tabs:
a) General b) End Points c) classifications d) System Details.
6) In the general you can able to see your WSDL URL by again entering Authentification details.
7) Now Click End Points>Test Button>Enter Authentification details-->Seelct your Interface
Note:: Now you can test your scenario in this WEB SERVICE NAVIGATOR.
8) There you can enter you can pass your Input data parameters in your SOAP interface and execute or test your scenario here itself without any using of external tool like Altova XML or SOAP client tool.
I hope the above information will give you a detailed information in generating and testing webservice right.
Regards::
Amar Srinivas Eli

ASMA in SOAP Sender adapter.

Hi All,
Using ASMA under SOAP sender adapter I am trying to get the username of the user . I am referring below links for the same:
/people/michal.krawczyk2/blog/2009/05/26/pixi-pseudo-principal-propagation (referring this only for getting username)
getting user name from sopa header
But while testing through XML SPY , i am getting error :
Com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during parsing of SOAP header.
Please help??.
Thanks
Amit

Hi.
I have created WSDL file using below URL:
http://ISVSAPPIDEV:50100/XISOAPAdapter/MessageServlet?channel=:BS:CC_SOAP_Sender
Actually its a synchronous SOAP -PI - RFC scenario. When i am pinging the PI through XML spy(ASMA AND Transport Binding is UNCHECKED in soap sender channel) i am getting the response back from RFC, but when i am pinging after chking the ASMA and Transport Binding in SOAP sender adapter i am getting this error(the message is itself not reaching the PI):
Com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during parsing of SOAP header.
Thanks
Amit

Soap sender adapter show invalid content type

Hi dear mates,
I have a SOAP-JMS scenario working succesfully on 7.3.1. But in 30 min after ICM restart (usin SMICM) something wrong happend because all Soap sender adapter fails showing that error.
<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage due to invalid content type for SOAP: TEXT/HTML
If I restart manually ICM still working fine until next 30 min more or less.
I have added MP transform bean to ensure that I am sending UTF-8 propertly. But it doens't work.
Does anybody know a clue why occurs this strange behavior?
Thanks in advance and regards.
José Antonio.

Thanks Vladimir,
This is exactly the behavior. And yesterday we have to increase the memory because it has 32gb shared in two PI instances, 16gb(DEV) and 16gb(TEST). And the memory was always full.
Recently I found the trouble. Doing SLDCHECK have this trouble also. SLDCHECK error-Check and maintain the SLD content for the current client
So, I re-register once again the system in rz70 and review related Bussiness System. And BS pipeline URL was wrong :S because it hasn't be wrote with path /sap/xi/engine?type=entry.
After restart SLD I do sldcheck and it looks perfect.
Thanks to all.
I hope this stupid error do not disturb any other consultants.
Best Regards.
Jose.

Another SOAP Sender adapter "com.sap.aii.af.mp.module.ModuleException" erro

I am working on a synchronous scenario SOAP <-> XI <-> RFC.
This worked fine, when I run it without SOAP adapter, direct via XI Pipeline.
Now I want to use the SOAP sender adapter, but get the error as described below this post.
As this is a real new XI installation, some patches or updates might be required to make it work. Or some adapter modules ?
Any suggestions on how to solve this problem will be rewarded.
What worries me a bit is the line " " in the error description.
Extra info: I use SoapSonar as a test webservice client. The error is the message as received in te test client.
<?xml version="1.0"?>

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
    <SOAP:Fault>
      <faultcode>SOAP:Server</faultcode>
      <faultstring>Server Error</faultstring>
      <detail>
        <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
          <context>XIAdapter</context>
          <code>ModuleUnknownException</code>
          <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/xi/645_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#9 $)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:427)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
          ]]></text>
        </s:SystemError>
      </detail>
    </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Hi Chandravadhana,
The colon should be there :
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
The inbound address for SOAP messages is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
Regards
Suraj

SOAP Sender Adapter gets error '(401) Unauthorized.'

Hi all,
we are using XI 3.0 and have a scenario with a SOAP Sender Adapter, which is using "HTTPS with Client Authentication". I have configured everything I have found on the forum at Visual Admin and Integration Directory:
Set the UME property ume.logon.allow_cert to TRUE in 'Service-->UME Provider'
Imported client certificate and root CA certificate to 'Service-->Keystore'
Created user with role role SAP_XI_APPL_SERV_USER
Assigned this user to the client certificate in 'Security Provider-->UserManagement'
Added the user to xi_adapter_soap_message and xi_adapter_soap_help in 'Security Provider'
Added the root CA in 'SSL Provider>Dispatcher>Client Authentication' and marked 'Request client certificate.
Added the user to BusinessSystem at tab 'Assigned Users'
Added the user to Sender Agreement at tab 'Assigned Users'.
Our business partner got a certificate of our server and the according PrivateKey is added to 'SSL Provider>Dispatcher>Server Identity'
Unfortunately, our server certificate is not verified by an root CA!!
When the business partner now browse the URL 'https://url:port/XISOAPAdapter/MessageServlet?channel=:BS_3RD_PARTNER:SOAP_SENDER&nosoap=true' on his system, he will get a 'Message Servlet is in Status OK'.
But when he tries to process the URL directly in his messaging system, he gets an error '(401) Unauthorized.'
Any hints what could be the problem between browing the URL in InternetExplorer and sending from the messaging system?
Does it really mean that authorization was successful, when getting 'Message Servlet is in Status OK' in the Browser?
How can I assign an user when not using ClientAuthentication?
I would be very thankful for every help...
Grtz, Juergen

Hi Satish,
could the user or password also be wrong, even if you get 'Message Servlet is in Status OK' when browsing the URL in the Internet Explorer? I would have seen this as a sign, that the user authentication works basically...
Is there a special place to store the password in the Visual Admin, or will the password be used, which is available in the SU01 ?
Grtz,
Juergen

Request Response Bean for SOAP Sender Adapter

Similar Messages

Maybe you are looking for