Hi,
Not sure and never tried but I guess it is multithread in case of sync requests (over http) otherwise XI wont be able to handle parallel multiple request from various senders (i.e. Flight booking, banking request) etc.
Regards,
Gourav

Similar Messages

SOAP Adapter Sender PI7.1: 400 Bad HTTP request

Hello,
I have a problem with a SOAP adapter sender communication channel.
I'm trying to migrate a scenario from XI 3.0 to PI7.1 SP6 (PI_BASIS 2006_1_710 SAPKIPYN06).
I can send messages successfully to the old system using the URL
    http://host:port/XISOAPAdapter/MessageServlet?channel=:BC_Name:CC_SOAP_Sender
On PI7.1 I get
    400 Bad HTTP request
    Error: -21
    Version: 7010
    Component: HTTP_PLG
    Module: http_plgrt_mt.c
    Line: 5226
    Error Tag:
    Detail: illegal request version
I have created a Sender Agreement, generated the wsdl from that and tried the URL in there.
Surprisingly it has the old format, namely
    http://host:port/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_Name&receiverParty=&receiverService=&interface=myInterface&interfaceNamespace=urn:my.Interface:ns
although the 7.1 documentation describes the ?channel=party:service:channel style only.
Anyway, the result remains the same.
I tried some other approaches like escaping the colons in the URL without success.
The user has the role SAP_XI_DEVELOPER_J2EE assigned.
Any idea what's wrong here?
Thanks in advance
Rainer

>>In RWB the channel appears as "started but inactive".
Yeah,it will be like that because you are posting messages directly to Integration server."Propose URL" does that.You are bypassing the adapter engine when you use the URL generated by "Propose URL" button.
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
The above blog gives the reason for this,if you want to bypass the adapter engine,then generate the URL as given in the above blog
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
This blog explains how to post message to adapter engine,here you need to change the URL,don't click on "Propose URL" button.You can monitor SOAP adapter in RWB only if you generate the URL as given in second blog
The URL which is working for you in XI 3.0 is posting messages to adapter engine,so generate the URL in PI 7.1 in the same way,by following the second blog i have mentioned.
Thanks
Aamir

Soap adapter communication channel problem

Hi...
While doing Webservices to file scenario, in component monitoring, the soap adapter communication channel is showing as (in small traiangle inyellow color) channel started but inactive

Hi leelaratnam,
Please check that you have only 1 communication channel active and running.
This happens when more than 1 CC is pointing or waiting for the same incoming data.
Also perform a dummy activate (i.e. write somthing in description and activate) in your message mapping and communication channel objects in case you are using PI 7.0
Thanks,
Varun

SOAP Adapter sender/receiver commnunication channel?

Hello everybody,
I wonder how to configure the commnunication channel for the SOAP-Adapter. If XI triggers a webService (acts like a WebService client) then XI expects a response from the WebService. The first step seems to me as a receive-step. Then I wonder how XI gets the response?
Thanks a lot
Mario

hi,
>>>The first step seems to me as a receive-step.
why? it's a send step
if you want to do it in a sync way then
XI does not loose connection and it waits
for the response
if you want to understand little bit more
sync calls have a look at this weblog:
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
the rfc call is done in a sync way
the same can be done with SOAP
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

Sender Soap Adapter communication channel error

Dear Experts,
When i see Sender soap adapter status in Communication channel monitoring.I am getting the status as:
"Processing Errors in the Last 50 Minutes"
Thanx in advance

Aamir,
My other interface is working fine by giving the following url:
http://kpmgvm015:8001/XISOAPAdapter/MessageServlet?channel=:KPMG_AU_ALL:RetrieveOpportunityRecord_SOAP_Sender
I am not using the propsed url.
Moreover when i try to give this url in the browser . It is asking of user id and password.
I am giving user as : PIAPPLUSER.It gives message servelet is ok.
In my communication channel monitoring the corresponsing communication channel:
RetrieveclientRecord_SOAP_Sender is in Red - Processing Errors In the Last 40 Minutes
Error meesage in Webclient:
java.security.AccessControlException: PIAPPLUSER has no permission for accessing binding com.sap.aii.af.service.cpa.Binding@d046043a

Option Adapter Engine of SOAP Adapter Sender

Hi, I have a question, I am creating a Communication Channel Type Sender Adapter Soap and note that the combo box Adapter Engine only appears Adapter Engine Central option and watch some examples of internet show Integration Server option and the section Default XI Parameters. It has to do with the version I'm using? or need to configure anything?. The version I have installed is the PI version 7.1.
Thanks for the support.

Hi, if the adapter XI shows the Integration Server. So in version 7.1 is no longer displayed in the Integration Server in the option Adapter Engine?. The problem is that I am leading this link http://www.****************/Tutorials/XI/SYNCASYNC/Page2.htm see image http://www.****************/Tutorials/XI/SYNCASYNC/Page2.76.jpg and not put in the Adapter Engine and XI Default Parameter. Thanks for the help.

Sender SOAP Adapter with HTTPs call

Hello,
Our scenarion is .. we will have a sender SOAP adater .. but it needs to be called using HTTPs(SSL).
Now considering we have the certificate generated and installed ..and that integration server is HTTPs enabled....What URL should the sending system call..?
For normal HTTP call the inbound address for inbound Adapter is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
For the case of HTTPs just changing the htttp to https and the port number in in the calling system will suffice? Or is there other configurations that needs to be done??
Thanks and Regards,
Himadri

Hi Himadri,
Firstly as suggested by others you can call using https and give the https port in the soap adapter servler URL. Secondly you need to do the following configurations:
1) If its PI 7.0/3.0, deploy the latest version of the SAP Java cryptography toolkit.
2) Configure SAP PI as the server for HTTPS calls. In short
      Using the SSL Provider service:
                            a.      Select whether the J2EE Engine should:
                               ■      Request (but not require) that the user presents a client certificate for authentication.
                               ■      Require that client certificates are to be used for authentication.
                            b.      Import the CAu2019s root certificate into the Trusted Certification Authorities list. (Choose Add.) using the following For all the steps, link is mentioned below for XI 3.0, you can find similar ones for PI 7.0
http://help.sap.com/saphelp_nw04/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/content.htm
3) If you want to enable client authentication then you would need to add the client certificate in the TrustedCA keystore view of the SAP J2EE engine.
4) In the SOAP Adapter sender channel, configure Inbound Security level as HTTPS or HTTPs with client authentication based on your scenario.
Best Regards,
Pratik

Enabling HTTPS with Client Authentication for Sender SOAP Adapter on PI7.1

Hello All,
We are currently building up a HTTPS message exchange with an external client.
Our PI 7.1 recieved over HTTPS messages on an already configured Sender SOAP Adapter.
The HTTPS (SSL) connectivity works fine and was completely configured on the ABAP Stack at Trust Manager (TC=STRUSTSSO2)
Login to Message Servlet "com.sap.aii.adapter.soap.web.MessageServlet is required and works fine with user ID and password.
Now we have to configure the addtional Client Authentication.
At SOAP Adapter (Sender Communication Channel) under "HTTP Security Level"you are able to configure "HTTPS with Client Authentication".
But what are the next steps to get this scenario successfully in place?
Many thanks in advance!
Jochen

Hi Colleagues,
following Steps still have to be done:
- Mapping public key to technical user at Java Stack
As preparation you have to activate value "ume.logon.allow.cert" with true under "com.sap.security.core.ume.service" under Config Tool. At NWA under Identity Management at for repecively technical user the public key certificate
- Be sure CA root certivicate at Database under STRUSTSSO2
- Import intermediate Certificate under Certificate List at Trast Manager for the Respecive Server Note
- use Login Module "client_cert" which you have to configure under NWA\Configuration Management\Authentication for Components "sap.com/com.sap.aii.adapter.soap.app*XISOAPAdapter".
Many thanks to all for support!
Regards,
Jochen

"Channel started but inactive" in RWB Monitor for SOAP sender channel

Dear XI specialists,
I have configured a communication scenario involving SOAP Adapter (sender) usage, but I'm facing the issue when testing the scenario. The problem is that none of messages are coming into the SOAP Adapter (checked via TCode SXI_MONITOR in XI) when using 3rd party SOAP-clients (XML Spy, soapUI) based on WSDL-file generated and exported from XI.
I checked the sender communication channel for SOAP Adapter - it is activated in Integration Builder's Directory. SOAP Adapter itself is also started.
I checked Runtime Workbench monitors and in the Communication Channels Monitor of the Components Monitor received the warning saying "Channel started but inactive" for my configured channel as well as for other channels working on SOAP Adapter.
Activities which were performed (in the order in which they were performed and results tested):
1. the configuration channel restart;
2. the communication channel re-activation and further re-start;
3. SOAP Adapter restart;
4. XI system's Java instance restart.
All mentioned activities didn't give any positive effect in part of this issue resolution.
On the other hand, if I use test message functionality of the Runtime Workbench (Component Monitor), then messages are seen in SXI_MONITOR and expected response messages are also returned to XI from integrated business system.
Would you please advise what can be checked else here and where the root of the problem may be detected?
All your answers and feedback will be greatly appreciated and awarded accordingly.
Many thanks in advance and my regards,
Vadim

Dear all,
Thank you for your input! Unfortunately, the problem still exists after testings and checkings which you suggested.
TO Seshagiri:
I checked message monitor and found only several messages for the required sender/receiver services pair in the used namespace - all of them were successfully processed (these are messages which I sent by means of RWB Component Monitor's test message functionality).
TO Sarvesh:
Yes, sender agreement is configured properly. I configured it when configuring communication scenario in the Configuration Wizard and then manually re-checked its definition. Moreover, when performing Test Configuration in ID, I received positive results.
TO Nallam Guna:
I cleared Data Cache in Integration Builder, but this didn't help.
TO Gujjeti:
I'm on SAP NetWeaver 2004s PI 7.0. Service Pack level for PI is 13.
TO Durga:
Thank you for provided links! I have already had a look at them - but proposed solutions doesn't seem to be working in my situation.
Thank you all once again for your prompt answers! I really appreciate your attempts in helping me!
I would appreciate if you could share any further ideas on this issue.
My best regards,
Vadim

Defalt VI Parameters in SOAP Sender Channel Config

Hi all,
I have configured soap sender channel with Default XI Parameters as * for both Interface name space and Interface name.
SOAP adapter sends the message with * as the interface namespace and interface and fails with the error "No receiver could be determined".
Why is SOAP adapter is using the default XI parameters from the channel instead of the parameters passed with the SOAP message.
I could make this work specifying the Default XI parameters with correct name space and interface, but my problem is I have 2 different interfaces from the same service and cannel, I don't want to create a separate channel for each of the interfaces.
Please help.

Hi Pratat,
you have to set the
Use Query String to true and the adapter will take the service/interface data from the query string instead of the Default XI Parameters
Regards,
Nicolá

How to build in user authorisation in sender soap adapter

HI ,
how can i built the user authorisation in sender soap adapter. either in a url or somewhere on the server .
if anyone has an idea do let me knwo
Thanks
Nikhil

Nikhil,
<b>sender soap adapter</b> is used for ex in the case, u need some data from the DB say of a vendor. U give the name of the vendor in the site, suppose u get the contact address of the vendor from the DB.
Sender soap adapter sends the soap request from the client to XI and from XI the request is passed to DB.
With XI, WSDL file is generated and SOAP request is generated for the WSDL file. When the WSDL is deployed on the client application, the authorization is handled.
For receiver SOAP adapter, it is the otherway round u r getting the data from the DB first and so the authorizations are held in XI.
-Naveen.

Error in the SOAP Receiver communication channel

Hi ,
My scenario is RFC - to -SOAP (synchronous ) i have specified the TARGET URL inthe SOAP receiver comminication chanel.. but while testing the interface by providing the test data from R/3 .. I'm not getting any Respose.. ..
If I check in the SXMB_MONI in i'm getting the following message .. but the URL whicjh i provided that is fine.. but my doubt is through XI may be it's not able to connect the Target System... .. so, please suggest me...
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: www.webservicex.net</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
regards
Jain

By default, the SOAP adapter sends the SOAP message with the content type text/xml.
When you check "Do not use SOAP envelope", the default contnet type is application/xml.
You can change the content type like this: Go to the SOAP receiver communication channel module tab. Add the module "localejbs/AF_Modules/MessageTransformBean" before the standard module. Add the parameter name Transform.ContentType and value text/xml.
Check out this
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
One way of testing ur scenario
/people/michal.krawczyk2/blog/2005/08/25/xi-sending-a-message-without-the-use-of-an-adapter-not-possible
Also have a look here
SAP Note 856597
reward points if solution found helpfull
regards
chandrakanth

How to setup SOAP Adapter in order to include BinarySecurityToken element

Hi,
I am building an integration scenario where I need to configure a SOAP receiver that will include the BinarySecurityToken element (as described in http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf). The value of the element must be the hash value of the canonicalisation on the XML using SHA-1 hash algorithm and encode it in Base64. Is there a way to configure the SOAP adapter receiver channel to perform such a task? I have see the security settings in the channel and the setting in the receiver agreement but I am not sure how to produce the value as above. Any help is appreciated.
Regards,
S.Socratous

Kiran look into this
As per my knowledge any RFC - enabled function can be exposed as a webservice which can be consumed by any application written in any language directly..
an XI message interface can also be exposed as a Webservice.
RFC is function-oriented webservice.
XI interface is integration webservice
Check the following blogs for webserivces
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
/people/sap.user72/blog/2005/11/22/xi-faqs-provided-by-sap-updated
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
Webservice Development
Consuming webservice
/thread/122211 [original link is broken]
Regards
Sreeram.G.Reddy

SOAP Adapter without SOAP envelope sets contenttype to application/xml

Hi,
I wrote a adaptermodul for the SOAP adapter to create a SOAP:HEADER.
I disable the SOAP envelope in the communication channel.
Now I get a error from the WebService Provider because the SOAP Adapter sends with Content-Type application/xml and not text/xml. I set the content-type in the adapter module but it seens to not work.
How can I correct this ?
Regards,
Gerald

Hi
Simple answer is NO, it is not possible (without party/channel/ service etc to process the request)
but it is worth a try to check if the URL encoding works.. though I have not tried..
for example sending the hex value of the "?" - %3F%
URL is a generic topic, you can search that to get more information
(ex : http://www.blooberry.com/indexdot/html/topics/urlencoding.htm)
Regards
Vishnu

File Sender channel stopped polling on FTP site

Dear all,
We have many file to Idoc interfaces running in production and all are they good.
Yesterday we faced one issue, one of the interface's sender communication channel stopped polling and didn't picked the files from FTP.
There was no error on communication channel monitoring and it is green.
We stopped & started the channel then started picking the files. But this is not usual behavior of file adapter.
We found one SAP Note 1083488, according to this note, we are in the latest SP level( PI 7.0 SP 14). So not required to apply this patch my case.
What should i do to not to face next time
Regards

Hi Bhavana,
Check the below Q & A.....
>> Q: After configuring a large amount of File Adapter sender channels, the J2EE Engine becomes very slow and some services start to block. How can I solve this issue?
A: Up to and including XI 3.0 SP13 each File Adapter sender channel permanently consumes a J2EE application thread. To solve this issue, increase the number of configured J2EE application threads using the SAP J2EE Engine Config Tool ("cluster-data" -> "Global server configuration" -> "managers" -> "ApplicationThreadManager" -> "MaxThreadCount").
Starting with XI 3.0 SP14 / PI 7.0 application threads are allocated on demand by the File Adapter and returned to the thread pool after it has finished the polling sequence, so thread shortage situations will typically occur much more rarely than with earlier SPs.
Also as said by Other SDN'ers check the locks.
Thanks,

SOAP Adapter - Sender Channel (Multithread)

Similar Messages

Maybe you are looking for