SOAP adapter works synchronously with EO !??

Hello,
I configured Sender SOAP Adapter with EO. The SOAP adapter follow the message to a BPM.
All of this process work fine with the HTTP Adapter (that I use for test) but when I use the SOAP Adapter I receive a strange error message :
BPE_ADAPTER.SYNCHONOUS_MESSAGE
The process does not support the given synchronous interface or does not support synchronous messages
Does anybody know how to sovle this ?
Thanks
Regards
Chris

I always have the return code 0. This process work with the HTTP Adapter but not with the SOAP Adapter.
The only thing I change was the adapter in the sender agreement.
This is the begeening of the XI Message :

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SOAP:Header>
<SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>1CCC5F0F-F2BB-BC49-BDC3-A6C2F209A645</SAP:MessageId>
<SAP:TimeSent>2006-12-26T11:50:36Z</SAP:TimeSent>
<SAP:Sender>
<SAP:Service>TOFFStaging</SAP:Service>
<SAP:Interface namespace="http://t.be/xi/TOFF/LeadCreation">MIOA0001_Offer</SAP:Interface>
</SAP:Sender>
<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>BP0001_ToffLeadCreation</SAP:Service>
<SAP:Interface namespace="http://t.be/xi/PI/LeadCreation">MIAA0001_Offer</SAP:Interface>
<SAP:Mapping notRequired="M">
<SAP:ObjectId>rrEYQC3BMRyBTROgtt+SaQ==</SAP:ObjectId>
<SAP:SWCV>g2bqoJATEdu/Gvy1rBATzQ==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://t.be/xi/PI/LeadCreation">MIAA0001_Offer</SAP:Interface>
</SAP:Main>
<SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
Regards,
Chris

Similar Messages

In what QOS does the receiver SOAP adapter work BE or EO?

Hi,
In what QOS does the receiver SOAP adapter work BE or EO?
My guess is that it is by default EO, if so how do i make it work like synchronous?
There is no option to set it explicitly.
Thanks]
Shakthi

Siva,
In receiving adapter you can't set the status. The receiving QOS is set in the pipeline by using the Sender Comm.channel QOS.
So for example in SOAP to SOAP scenario, if you set the Sender comm.channel as BE, then through out the Pipeline till it reaches the Receiver Comm.channel the QOS will be considered as BE only( Even though you didn't explicitly said to the Receiver comm.channel).
Hope it helps!
raj.

Lightning to 30-pin Adapter works great with iPad Keyboard Dock

In case anyone was wondering, the Lightnng to 30-pin Adapter works great with the original iPad Keyboard Dock and an iPhone 5. In fact it is better than the 4S was, as that tended to pop out. The Lightning adapter stays in place, and there is plenty of support in the back plastic to keep the iPhone in place, with any tiny stress happening at the Dock connector end: the Lightning connector itself seems very solid indeed. All the keys work, and charging is fine.
(In answer to the implicit question: my employer blocks email at work on its systems, and it's convenient to have the keyboard hold the phone in place, and also charge it, which is the problem with the Bluetooth keyboard.)

Might be a question better asked of the manufacturer of the iHome device.

Issue with Receiver SOAP adapter for synchronous scenario

Hello All,
We are facing a strange issue with the SOAP adapter in the interface we have setup. This is the 1st time we are using SOAP adapter in our system (PI 7.11 SP7). We are making a synchronous HTTP call to the web service exposed by another system in our landscape. The payload is send with SOAP envelope and there are no credentials to be maintained in PI settings.
The issue is that we are always getting timeout exception in PI audit logs after sending the request (3 minutes - standard timeout value, no additional config for this). But target system has confirmed that they are sending the response back. We tested from our server OS level and have received the response back in the same screen (to verify there is no firewall/port issue in between the systems). But when tried from RWB, it is always giving the timeout exception and we are not able to see any other log.
We have tried checking in the NWA logs as well after increasing the logging level to ALL for com.sap.aii.adapter.soap. But surprisingly, we didn't get any logs at all for the outgoing SOAP call or incoming response and hence we are unable to trace the issue.
We have setup another synchronous inbound SOAP interface (PI exposing the webservice) and it is working fine. We are also able to trace the logs in both audit log and NWA logs.
Is there anywhere else we can check for the logs? Audit logs is showing timeout error and we are not able to see anything in NWA logs.
Does the target system need to maintain PI credentials in the header when they send the synchronous response back?
Are there any specific settings which should be checked to enable the sync communication? (this should not be the case since the inbound interface is working fine)
Please help.
Thanks
Justin

Hi Amit,
Thanks for the reply.
Yes we had tested successfully via SOAP UI as well (forgot to mention that). We are getting back the expected response in SOAP UI without using any credentials. We got the same response when we tested it through OS commands from PI server.
The WS is hosted by the target system and they haven't maintained any credentials at their end. So when PI is trying to access, we don't need to provide any credentials. My question is, whether the target system should keep any credentials to send the synchronous response back to PI (java stack). We have tried that as well but since there aren't any logs, we are unable to verify whether the credentials are coming correctly.
The service interfaces are correct and PI configuration are OK. I will try the XPI inspector for logs as you have suggested.
Thanks
Justin

How to make call to Sender Soap Adapter using HTTPS with Client Aut

Hello everyone, I have spent some time trying to get this to work. We downloaded a trail certificate from SAP and installed it on our machine and I created a webservice that works great. I tested the HTTPS without client authentification and it works great, as soon as I change it to use with Client Authentification I can't get it to go through. I am using Soap Sonar to test the certificates. To get the certificate I called the url with firefox then saved the certificate in my trust store, from there I import it to soap sonar as a signed certificate, but I am getting the error <Exception>Object contains only the public half of a key pair. A private key must also be provided.</Exception> I assume I am doing something way wrong, is there a way to get the certificate with both public and private key pair, or a way to test this that I can't seem to find in documentation or blogs?
I def award points
Cheers
Devlin

Hi
I think This link is useful to u
http://www.sapag.co.in/SAP-XI-SOAP-Adapter-FAQ'S.html
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
Thanks
Santosh

SOAP adapter and WS with rpc/encoded

Hi All,
Does anyone know if and how the SAP XI 3.0 SOAP Adapter supports WebServices which expects XML messages in rpc/encoded.
Cheers,
FRank

Hi Frank,
I have the same issue and I got a reply from OSS:
This problem is caused by the diversification of the WSDL binding
styles.
A Web service is described by a WSDL document. A WSDL binding
describes how the service is bound to a messaging protocol, particularly
the SOAP messaging protocol. A WSDL SOAP binding can be either an RPC
style binding or a document style binding. A SOAP binding can also have
an encoded use or a literal use. This gives us four style/use models:
- RPC/encoded
- RPC/literal
- document/encoded(It will probably disappear from future versions of
WSDL.)
- document/literal
RPC styled web services have serious interoperability problems. This
is the reason that the rpc style is not in the basic profile
specification of the web interoperability and also it has been
deprecated in the current soap specification. For these reason, the
integration directory does not currently support the RPC style! I would
suggest you to use other document style web service provider if possible
. It's the best way to solve this problem. But if you persist in using
this RPC web service provider, we still have a workaround solution:
you need to convert your RPC wsdl to a document styled wsdl and import
it to the directory and if necessary, you need to add some mapping to
solve some RPC interoperability problems.
In your case,
1. The WSDL file you used is RPC style.
2. The XI SOAP adapter doesn't support the RPC style. It only sends the
document/literal SOAP message which can't be understand by your web
service provider.
One of the significant differences between the SOAP message of RPC
style and that of the document style: the operation name is contained in
the RPC style SOAP message but not in the document's.
However, you can't solve this problem by simply specify a method
name. What you should do is convert your RPC wsdl to a document styled
wsdl. RPC turns out to be a subset of document/literal. This
means for any given RPC WSDL, you can create a completely
equivalent document/literal WSDL that would describe the same wire
messages. Here are the steps for doing this (mostly schema element
declarations).
Solution:
For each RPC operation:
1. For each part in the input and output messages of that operation,
declare a type with the contents described in step 2.
2. Declare an element with the name of the part, the type referenced by
type=". The element form must be unqualified.
3. Declare a global element with the operation name and the namespace
from soap:body/@namespace in the binding. Make the type of this element
the one defined in step 1 for the input message.
4. Declare a global element with the operation name and the word
Response appended to it and the namespace from soap:body/@namespace in
the binding. Make the type of this element the one defined in step 1 for
the output message.
5. Change the input message to contain one part and reference the
element you declared in step 3.
6. Change the output message to contain one part and reference the
element you declared in step 4.
7. Change the style to document in the binding.
After that, import the new WSDL file to the integration directory. You
will find the "method name" appears in the document style SOAP message.
But actually it's the name of the input element which is the same as
the name of the operation. It's just a little trick.
Cheers Stefan

Why doesn't a genuine Apple 30 pin to Lightning adapter work with an iPhone 6 Plus?

Hello all - I was wondering if anyone else out there was having an issue with their Apple 30 pin to Lightning adapter not working with their new iPhone 6 Plus? The adapter worked fine with my iPhone 5, but since I got my new phone, I keep getting the message that says that "this accessory may not be compatible..." Did Apple change something with their Lightning ports? Should I purchase a new 30 pin to Lightning adapter? This is annoying! I have used it in my car (Kia) for over a year with an iPhone 5 and it worked flawlessly.

Howdy nanster23,
If you have as yet been unable to use this 30pin to lightning bolt adapter, I would like to recommend the troubleshooting in the following article to help you get that squared away:
If you need help with iPhone, iPad, or iPod touch accessories
These sections in particular since you have already done a couple of them:
Disconnect and inspect the accessory, then restart your device
Disconnect the accessory and turn it off, if possible.
Inspect the connection between the accessory and device and make sure that no debris or other damage is present.
Restart your iOS device by turning it off, then back on. When the Home screen appears, reconnect the accessory.
Restore iPhone, iPad, or iPod touch
Restore your iOS device. You should rarely need to use this step with an accessory issue. If the issue only affects a third-party accessory, contact the manufacturer before restoring the device.
Thank you for using Apple Support Communities.
Cheers,
Sterling

SOAP Adapter - Using Fault Message

Hi all,
I have developed a Synchronous Integration Scenario which receives a SOAP request to the SOAP adapter, calls an ABAP proxy in SAP ECC to post some information and return a response or a fault to the sender.
This all works fine, I am using a fault message in the ABAP proxy to record errors and return them to the SOAP adapter using the fault mapping. Again this all works fine. However when an application error is identified and a fault message returned to thre SOAP adapter, I had expected that the error details in the fault message to be packaged up in a standard SOAP fault and returned to the sender. Instead the fault message details are sent as the payload in the SOAP body of the response.
Can anyone provide information on if it is possible to return the fault message as a standard SOAP fault instead of in the SOAP body of the response.
Thanks
Gary

Dont think this is possible in standard.
As an alternate, maybe you can select option Do not use SOAP Enevlope int he sender SOAP Adapter and thereby the entire SOAP Message will enter the mapping and you would need to use a XSL or Java mapping to strip the SOAP Envlope in the mapping for the request and like wise in the response mapping you would need to add the SOAP Enevlope to the response.
For the fault message mapping you need not add the SOAP Envelope.
Not a standard solution, but can be tried if the requirement is really worth it. Otherwise I think the Fault Message will continue to be sent as the payload in the the SOAP Enevlope as this is how the SOAP adapter works.
Regards
Bhavesh

Receiver SOAP Adapter (HTTP AXIS)

Hi Experts,
I need to use receiver soap adapter to communicate with a WebService, actually it is a AXIS service i can see when i give the soap url in web browser.
my question is for axis service, does it mean i have to use HTTP AXIS in the receiver channel to request the response for web service server? Can i use HTTP only without AXIS?
when i use SoapUI to test the webservice, it works fine. But when i use receiver soap adapter with HTTP (without AXIS), it is responding with the belwo error.
<sap:Error ...>
<sap:Category>Application</sap:Category>
<sap:Code area="UNKNOWN">APPLICATION_ERROR</sap:Code>
<sap:AdditionalText>Application Fault</sap:AdditionalText>
<sap:ApplicationFaultMessage namespace="http://sap.com/xi/XI/System/Axis/sample">host name</sap:ApplicationFaultMessage>
<sap:Stack/>
</sap:Error>
Experts, please help on this, the major question is HTTP AXIS is required when target web service is an AXIS service?
Thanks in advance.
Regards,

>>my question is for axis service, does it mean i have to use HTTP AXIS in the receiver channel to request the response for web service server? Can i use HTTP only without AXIS?
You are going to consume webservice. You can use standard SOAP adapter itself to consume the webservice that is built with axis framework.
Do you have some specific user authentication procedures like SAP Assertion Tickets, username token etc and some specific encapsulation formats (MIME, DIME, MTOM),WS Reliable Messaging and so then you need SOAP Axis adapter. If you need to consume webservice with standard transport protocol (HTTP or HTTPS) and client authentication etc , our standard SOAP adapter is more than enough.
Refer this link what axis soap adapter supports

SOAP adapter using HTTPS

We need to using SSL over HTTP for our web service defined in PI, basically using HTTPS in our SOAP adatper. I did a lot of research on this, seems like it's not an easy job to enable SSL. However I am only interested in making it work from an application developer point of view, enabling SSL, generating/installing certificate is a job for basis people.
So I created an sender CC with SOAP adapter with HTTPS with client authentication. (BTW, what is HTTPS without client authentication, does it mean HTTPs with server authentication where the server certificate is to be installed at the client side?), to my understanding, the client certificate should be installed in NWA (We have PI 7.1, not 7.0 -) and somewhere in ID (like sender agreement) we need to specify which client certificate should be used to authenticate the client who calls our service. However nowhere in ID I can specify which client certificate should be used for the defined sender CC. So how would it work in runtime? When my web service is called, which client certificate does PI use to authenticate the client?
It'd very much appreciated if you could give more information about how HTTPS for SOAP adapter works? I've done lot of research on this, but still confused.
Thanks

Hi,
for transport level security you should assign the HTTPS connection created in SM59 to the SOAP communication channel.
The HTTPS connection should use the certificates imported in t-code STRUST.
1. You have to dounload the SAP cryoptographic librariers.
2. Set the specific paramerts in RZ10
3. Maintain the enviornmental variables & you need to keep the logon tickets too in some specific directory.
4. Import the client & server certificates into STRUST.
You can find some documents on ABAP ssl configuration from the SDN library .... I don't have a link now
Regards
Sunil.

Error in Adapter engine of receiver soap adapter

Hi All,
There is one production issue i am currently facing in receiver SOAP adapter while interacting with third party web service(Asynchronous call).
Below is the description i am getting in audit logs.
Success SOAP: completed the processing
Error SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Success SOAP: sending a delivery error ack ...
Success SOAP: sent a delivery error ack
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired.
Error The message status set to NDLV.
Moreover this is a production issue and interface was running fine till last friday.
Has someone ever faced this issue ?
Please provide your valuable inputs on this.
Thanks
Anku

Hi,
Search in sdn with your error message string,you will find ton of links.
HTTP401 error occurs for many reasons.
still no solution let us know..
Regards,
Raj

Error in using XI-SOAP adapter, but no error with SAP-BC

Hi,
I am working on RFC->XI->Webmethod (.asp) scenatio.
I am using SOAP adapter.
Whin I am not using "Do not use SOAP Envelop".
I am getting "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML" Error in SXMB_MONI.
But when I am using "Do not use SOAP Envelop" then I am not getting any error. in SXMB_MONI status showing Successfully Processed. But the responce i am getting is "You are not authorized to view this page // HTTP 401.1 - Unauthorized: Logon Failed"
But same web-service is working fine while connected with SAP-BC.
Please Help why scenario is working with BC, but not with XI.
Thanks & Regards

Hi Bhavesh,
Thanks for reply.
I am getting all success in message monitoring, but still web-services sying they are not getting any message.
I am attaching all 4 logs for one synchronous communication of message monitoring.
I am not able to understand where message going and why XI showing success every where.
********1st(Sent Messages)
Success SOAP: response message leaving the adapter
Success Application attempting to send an XI message asynchronously using connection AFW.
Success Trying to put the message into the send queue.
Success The response message for message cf4fd921-4a74-11db-9312-001279933263(INBOUND) was successfully transmitted to the calling application.
Success The message status set to DLVD.
Success The application sent the message asynchronously using connection AFW. Returning to application.
********2nd (Sent Messages)
Success RFC adapter received sRFC for Z_PA_SAP_TO_Webservice from D02/230. Attempting to send message synchronously
Success Application attempting to send an XI message synchronously using connection AFW.
Success Trying to put the message into the call queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the call queue.
Success The message status set to DLNG.
Success The message was successfully transmitted to endpoint http://XYZ.com:8000/sap/xi/engine?type=entry using connection AFW.
Success The application sent the message synchronously using connection AFW. Returning to application.
Success The message status set to DLVD
**********3rd (Received Messages)
Success Using connection AFW. Trying to put the message into the receive queue.
Success The XI response message for message d0372be1-4a74-11db-91d7-001279933263(INBOUND) was successfully returned to the calling application.
Success The message status set to DLVD.
**********4th (Received Messages)
Success The message was successfully received by the messaging system. Profile: XI URL: http://XYZ.com:50000/MessagingSystem/receive/AFW/XI
Success Using connection AFW. Trying to put the message into the request queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the request queue.
Success The message status set to DLNG.
Success Delivering to channel: IF_O_502_WebserviceBusService_SOAP_In_02
Success SOAP: request message entering the adapter
Success SOAP: completed the processing
Success SOAP: response message received d0372be1-4a74-11db-91d7-001279933263
Success The message status set to DLVD.
Success The message was successfully delivered to the application using connection AFW.

Messages failing in the SOAP adapter with the errror

HI
I am getting the below error in the SOAP adapter monitoring . can any body tell what does "No route to host: Connect" mean .
could some one help us on resolving this .
Error Exception caught by adapter framework: No route to host: connect
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: No route to host: connect: java.net.NoRouteToHostException: No route to host: connect. Setting message to status failed.
Error The message status set to FAIL.
Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: No route to host: connect: java.net.NoRouteToHostException: No route to host: connect.
thanks and regards
sandeep

Hi!
First please confirm whether you are working on XI or PI 7.1 ?
because in XI you need to generate WSDL manaually via Tools>Define Web service-Giving Input..and in XI you need to test the SOAP scenario from external tool like Altova xml spy tool kit or else SOAP client tool.
In PI 7.1::
You can publish directly the web service in the SERVICE REGISTRY from sender agreement onwards.
once it is published you can check the status on your interface in service registry as CONFIGURED..Okay
Here you can test directly in service registry...
According to your error check ocne agan even though you gone through all the steps..
1. Check whether the SOAP service is active or not in SICF>SAP>bc>XI>Service-->SOAP.
2. sicne after generating wSDL u can get one url right that URL itself acts as a gateway to enter the source data into XI..
lets give to the source team to try with XI super uID adn PWD as authentification.
3. Also please STOP ur communication Channel and start once again.
4. Please check whether the WEB Service is configured correctly or not.
Regards::
Amar Srinivas Eli

Problem with SOAP Adapter receiver not receiving the proper string

Hi friends
I have a very simple scenario as follows using SOAP Syncronous Call
SENDING SCENARIO
================
ExternalClient --> SOAP ADAPTER --> XI -> RFC ADAPTER --> ZBAPI
RECEIVING SCENARIO
==================
ZBAPI --> RFC ADAPTER --> XI --> SOAP ADAPTER --> ExternalClient
Here External Client is sending a search ID and ZBAPI searches for that record and send the FirstName and LastName.
I am using external Definitions in XSD format as follows.
INPUT XSD is
=========================================
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://cincom.com/xi/socrates/customerSearch" targetNamespace="http://cincom.com/xi/socrates/customerSearch">
 <xsd:element name="ZBAPI_GET_NAME">
 <xsd:complexType>
 <xsd:all>
 <xsd:element name="ID" type="xsd:integer" minOccurs="0" />
 </xsd:all>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>
===========================================
Reciving XSD file has
==============================================
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:socrates.cincom.com" targetNamespace="urn:socrates.cincom.com">
 <xsd:element name="ZBAPI_GET_NAME_RESPONSE">
 <xsd:complexType>
 <xsd:all>
 <xsd:element name="ADDRESSDATA" minOccurs="0">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="FNAME" minOccurs="0">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="20" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="LNAME" minOccurs="0">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="20" />
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 </xsd:all>
 </xsd:complexType>
 </xsd:element>
</xsd:schema>
=========================================================
I HAVE TESTED THE ZBAPI AND IT WORKS WELL ON ITS OWN. ALSO I HAVE TESTED THAT THE MESSAGE SENT FROM OUTSIDE CLIENT IS REACHING BAPI. HOWEVER WHEN I GOTO 'SXMB_MONI' AND CHECK THE
XML STRING THAT THE RECIEVER IS GETTING, I SEE JUST THE FOLLOWING TWO LINES
===================================
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:ZBAPI_GET_NAME_RESPONSE xmlns:ns1="urn:socrates.cincom.com" />
======================================
IF YOU NEED ANY FURTHER INFO, PLEASE LET ME KNOW.
HOPE SOME ONE CAN GUIDE ME WITH THIS PROBLEM.
THANKS IN ADVANCE
RAM

Ram
Can you pls. confirm whether the mapping of your XSD fields & BAPI fields are in same sequence. I mean hierarchy is same or not.
Just to verify, as you said you are using Sync scenario that means you are using ONE Sender Soap & ONE Reciever RFC adapter.
Regards
Lalit

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

SOAP adapter works synchronously with EO !??

Similar Messages

Maybe you are looking for