SOAP comm channel with SSLException error

Hi,
I have set up a SOAP to web service but I'm encountering this error :
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Peer sent alert: Alert Fatal: illegal parameter: iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: illegal parameter
SOAP: call failed: iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: illegal parameter
Has anyone also encountered this before? Is it because the target URL of the web service is using HTTPS?
Thanks!

Hi,
Reconfigure the Web service client logical port and enable HTTP protocol instead of HTTPS.
Please go through this link : http://wiki.sdn.sap.com/wiki/display/JSTSG/(WSR)Problems-P16.
Regards,
Ranjani.

Similar Messages

Receiver SOAP Comm Channel Settings with TServerLocation

Hello All,
We are working on using Dynamic Configuration of Receiver SOAP. We are using the following scenario
*Can anyone please guide us on Receiver SOAP Comm Channel settings*
1) Value to be used in Target URL
Which parameters need to be checked ?
Currently we are getting the following error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.util.URI$MalformedURIException: no scheme</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Truly apprecaite your help
Thanks.
Kiran

Hello
Can anyone guide me on the settings in receiver Comm Channel which uses dynamic configuration in TServerLocation ?
Thanks.
Kiran

SOAP adapter engine with system error, problem with fault message.

HI,
I have IDOC -> PI -> SOAP scenario.
Idoc to PI is async. I have no problem in receiving the idoc in PI. The message mapping is carried out and sent to the adapter engine. I can also see the technical routing payload. It is sucessful at XML monitoring in SXMB_MONI.
The error is at PI -> SOAP.
I have wsdl provided by the receiver webservice. Which I have imported.
And created a service interface against this wsdl. I tried changing it to both sync and async.
I have also provided fault message.
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap
action = processDocument. Also provided user id and password.
I have a
Sender Agreement
Receiver determination
Interface determination
Receiver Agreement
I check in RWB adapter engine, this message goes to system error. The error log is as shown at the bottom.
When I see the message content, the SOap document shows me the details about IDOC, Instead I feel it should match
with the wsdl, where they have specified the corresponding interface name and address location etc.Please correct me.
How does the receiver know which service interface is it? The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same? I see that the soap document in the adapter engine has the
Service interface name which I created in the ER. Where in the document the Reciever interface name is sent?
Where can I see the generated soap document for the receiver?
Is there some setting/configuration required in PI for this to work?
I tried using the tcpgw to see the error. If I dont provide the service interface name in the communication channel
then I get the following error in the TCPGW. "The service cannot be found for the endpoint reference"
When I provide the service interface name in the communication channel I get a valid fault message.
Similarly
When I use SOAPUI, I can see the fault exception being return. The adapter engine doesnot show an equivalent message
instead it goes into system error as shown at the bottom. I guess this is expected, if so what is the work around? (I found this weblog /people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it, do I need to implement this? Or use ALEAUD?
The fault message what I see in SOAPUI has the below format.
<soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">
         <faultcode>axis2ns1:Server</faultcode>
         <faultstring>nested exception is: psdi.util.MXApplicationException: BMXAA7136E - Validation failed when the
                            database default values were set. See the associated message for more information.
           BMXAA4190E - Country NZ is not in the value list.</faultstring>
         <detail>
            <Exception>org.apache.axis2.AxisFault: nested exception is: psdi.util.MXApplicationException: BMXAA7136E
                      - Validation failed when the database default values were set. See the associated message for more information.
     BMXAA4190E - Country NZ is not in the value list.
            /Exception>
         </detail>
</soapenv:Fault>
And the fault message in my ER service interface is stanadard datatype ExchangeFaultData, which is different from
the above. Is this the problem? Can I change the data type here to be the same as above?
Audit log in the RWB adapter engine.
Time Stamp Type Description
30.09.2011 15:10:57 Information MP: processing local module Localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
30.09.2011 15:10:57 Information SOAP: request message entering the adapter with user J2EE_GUEST
30.09.2011 15:10:57 Information SOAP: completed the processing
30.09.2011 15:10:57 Information SOAP: sending a delivery error ack ...
30.09.2011 15:10:57 Information SOAP: sent a delivery error ack
30.09.2011 15:10:57 Error MP: exception caught with cause
com.sap.engine.interfaces.messaging.api.exception.MessagingException
30.09.2011 15:10:57 Error Adapter Framework caught exception: null
30.09.2011 15:10:57 Error Delivering the message to the application using connection
SOAP_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException.
30.09.2011 15:10:57 Information The message status was set to WAIT.
30.09.2011 15:10:57 Information The asynchronous message was successfully scheduled to be delivered at Fri Sep 30
15:15:57 NZDT 2011.

I tried changing it to both sync and async.
I have also provided fault message.
dont feel that you need to do above steps.
I have a
Sender Agreement
ideally you dont need a sender agreement (and a channel) for IDOC --> PI flow.
When I see the message content, the SOap document shows me the details about IDOC
this is fine...you may see fields as seen in EDI_DC40 of the IDOC...
How does the receiver know which service interface is it?
receiver need not know about the SI created in PI.
The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same?
you should the WSDL (external definition) as the Request Message in your service interface.
Is there some setting/configuration required in PI for this to work?
nothing specific...AFAIK
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap action
can you open the URL from Internet explorer...from your machine or from the machine which is in the same network as your PI server?
Things to check:
WSDL structure in PI and in target system is exactly the same.
does the target system require mesage in SOAP format (SOAP envelope - SOAP Header + SOAP body)?
target system is up and running?

Exception handling in receiver sync SOAP comm channel

Hi experts,
We are developing following synchronous scenario: sRFC to SOAP.
In this, XI sends some data to an application and the application sends back the response. No problem so far.
However, this application can throw exceptions that we want to send back to SAP, these exceptions are not part of a message and we can only see them AS AN ERROR IN SXI_MONITOR in the receiver SOAP header, in the error tab, they look like:
"com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault:
Questions:
Is there any way to get these exceptions from the application and send them back to SAP as if they were the SOAP.response message??
What if we select Keep headers in the receiver SOAP channel?
do we need to create a fault message type and assign it in ID?
Any ideas?
Best regards,
David

check for the possibility of raising an alert which has SXMS_TO_ADAPTER_ERRTXT as the Container variable....so if there is an error this alert variable will get populated and you will receive an alert....applicable only for adapter engine alert...
for more information: http://help.sap.com/saphelp_nw70/helpdata/EN/d0/d4b54020c6792ae10000000a155106/frameset.htm
Regards,
Abhishek.

External SOAP-Call ends with general error "PART UNKNOWN (NULL)"

Hi,
we generated a consumer proxy using the following WSDL file:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="https://soap.global-esign.com/axis/services/GlobalEsignSoapExt" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="https://soap.global-esign.com/axis/services/GlobalEsignSoapExt" xmlns:intf="https://soap.global-esign.com/axis/services/GlobalEsignSoapExt" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="https://soap.global-esign.com/xsd" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

   <wsdl:message name="CreatePdfSignatureRequest">
      <wsdl:part name="in0" type="xsd:string"/>
      <wsdl:part name="in1" type="xsd:string"/>
      <wsdl:part name="in2" type="xsd:base64Binary"/>
      <wsdl:part name="in3" type="xsd:string"/>
      <wsdl:part name="in4" type="xsd:boolean"/>
      <wsdl:part name="in5" type="xsd:string"/>
      <wsdl:part name="in6" type="xsd:string"/>
   </wsdl:message>
   <wsdl:message name="CreatePdfSignatureResponse">
      <wsdl:part name="CreatePdfSignatureReturn" type="xsd:base64Binary"/>
   </wsdl:message>
   <wsdl:portType name="GlobalEsignSoapExt">
      <wsdl:operation name="CreatePdfSignature" parameterOrder="in0 in1 in2 in3 in4 in5 in6">
         <wsdl:input message="impl:CreatePdfSignatureRequest" name="CreatePdfSignatureRequest"/>
         <wsdl:output message="impl:CreatePdfSignatureResponse" name="CreatePdfSignatureResponse"/>
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name="GlobalEsignSoapExtSoapBinding" type="impl:GlobalEsignSoapExt">
      <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
      <wsdl:operation name="CreatePdfSignature">
         <wsdlsoap:operation soapAction=""/>
         <wsdl:input name="CreatePdfSignatureRequest">
            <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://GlobalEsign.tsi.de" use="encoded"/>
         </wsdl:input>
         <wsdl:output name="CreatePdfSignatureResponse">
            <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="https://soap.global-esign.com/axis/services/GlobalEsignSoapExt" use="encoded"/>
         </wsdl:output>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name="GlobalEsignSoapExtService">
      <wsdl:port binding="impl:GlobalEsignSoapExtSoapBinding" name="GlobalEsignSoapExt">
         <wsdlsoap:address location="https://soap.global-esign.com/axis/services/GlobalEsignSoapExt"/>
      </wsdl:port>
   </wsdl:service>
</wsdl:definitions>
The coding of the test program is:
*& Report Z_SOAP_PDF_SIGNATUR
REPORT z_soap_pdf_signatur.
*------ Type pools
type-pools: sai.
*------ Class definitions and references
DATA: lo_zpdf_sign    TYPE REF TO zpdfco_global_esign_soap_ext,
      lo_system_fault TYPE REF TO cx_ai_system_fault,
      lo_appl_fault   type ref to cx_ai_application_fault.
*------ data
DATA: output TYPE zpdfcreate_pdf_signature_respo,
      input TYPE zpdfcreate_pdf_signature.
DATA: wa_controller TYPE prxctrl.
DATA: pdfout(255) TYPE c VALUE
'C:/TEMP/pp-20080229-93ES-40010-0013439840-1690000005.pdf',
       pdfsign(255) TYPE c VALUE
'C:/TEMP/pp-20080229-93ES-40010-0013439840-1690000005-sign.pdf',
        wa_objcont TYPE soli,
        objcont LIKE soli OCCURS 0.
DATA: xlines TYPE string,
      buffer TYPE xstring,
      x_msg TYPE c LENGTH 100.
TRY.
    CREATE OBJECT lo_zpdf_sign
      EXPORTING
        logical_port_name = 't_systems'.
CATCH cx_ai_system_fault .
ENDTRY.
* read unsigned pdf
OPEN DATASET pdfout FOR INPUT MESSAGE x_msg
                    IN BINARY MODE.
TRY.
    READ DATASET pdfout INTO xlines.
CATCH cx_sy_file_open_mode.
    EXIT.
ENDTRY.
CLOSE DATASET pdfout.
* convert string
CALL FUNCTION 'SCMS_STRING_TO_XSTRING'
EXPORTING
    text           = xlines
*   MIMETYPE       = ' '
*    encoding       = 'UTF-8'
IMPORTING
    buffer         = buffer
EXCEPTIONS
    failed         = 1
    OTHERS         = 2 .
TRY.
    input-in0 = 'user'.
    input-in1 = 'password'.
    input-in2 = buffer.
    input-in3 = 'affilinet'.
    CALL METHOD lo_zpdf_sign->create_pdf_signature
      EXPORTING
        input = input
      IMPORTING
        output = output.
CATCH cx_ai_system_fault INTO lo_system_fault.
    DATA: lv_message TYPE string.
    DATA: lv_message_long TYPE string.
    CALL METHOD lo_system_fault->if_message~get_text
      RECEIVING
        result = lv_message.
    CALL METHOD lo_system_fault->if_message~get_longtext
      RECEIVING
        result = lv_message_long.
    WRITE lv_message.
    WRITE lv_message_long.
CATCH cx_ai_application_fault into lo_appl_fault.
    DATA: lv_messaap TYPE string.
    DATA: lv_messaap_long TYPE string.
    CALL METHOD lo_appl_fault->if_message~get_text
      RECEIVING
        result = lv_messaap.
    CALL METHOD lo_appl_fault->if_message~get_longtext
      RECEIVING
        result = lv_messaap_long.
    WRITE lv_messaap.
    WRITE lv_messaap_long.
ENDTRY.
LOOP AT output-controller INTO wa_controller.
WRITE:/ wa_controller-field.
WRITE:/ wa_controller-value.
ENDLOOP.
* store signed pdf
OPEN DATASET pdfsign FOR output MESSAGE x_msg
                    IN BINARY MODE.
transfer output-CREATE_PDF_SIGNATURE_RETURN
         to pdfsign.
Processing the soap call in the test programm ends in a system exception (cx_ai_system_fault) with the message:
"General Error Es ist ein Fehler bei der Proxy-Verarbeitung aufgetreten ( PART UNKNOWN (NULL)    )"
It seems as if there is no response or a response in a wrong format given by the webservice.
We had a look at the ICF-Trace.
The request seems to be a proper soap-call.
But the response is not in XML-format and therefore could not be completely displayed.
it says:
Ungültig auf der obersten Ebene im Dokument. Fehler beim Bearbeiten der Ressource 'file:///C:/Dokumente und Einstellungen/S...
HTTP/1.1 200 OK
^
Could anybody help ?
Kind regards
Heinz

Hello Mathias,
in our case the problem was, that the WDSL used parameters, which were not correcty interpreted by the SAP-Routine that creates the proxy.
We changed the WDSL using only paramters covert by SAP.
Here ist the WSDL that worked fine:
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions targetNamespace="https://soap.global-esign.com/axis/services/GlobalEsignSoapExt" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="https://soap.global-esign.com/axis/services/GlobalEsignSoapExt" xmlns:tsi="http://GlobalEsign.tsi.de">
- <wsdl:documentation>
<sidl:sidl xmlns:sidl="http://www.sap.com/2007/03/sidl" />
</wsdl:documentation>
- <wsdl:types>
- <xsd:schema elementFormDefault="qualified" targetNamespace="https://soap.global-esign.com/axis/services/GlobalEsignSoapExt" xmlns="https://soap.global-esign.com/axis/services/GlobalEsignSoapExt">
- <xsd:complexType name="CreatePdfSignature">
- <xsd:sequence>
<xsd:element name="in0" type="xsd:string" />
<xsd:element name="in1" type="xsd:string" />
<xsd:element name="in2" type="xsd:base64Binary" />
<xsd:element name="in3" type="xsd:string" />
<xsd:element name="in4" type="xsd:boolean" />
<xsd:element name="in5" type="xsd:string" />
<xsd:element name="in6" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
- <xsd:schema targetNamespace="http://GlobalEsign.tsi.de" xmlns="http://GlobalEsign.tsi.de">
<xsd:import namespace="https://soap.global-esign.com/axis/services/GlobalEsignSoapExt" />
<xsd:element name="CreatePdfSignature" type="tns:CreatePdfSignature" />
- <xsd:element name="CreatePdfSignatureResponse">
- <xsd:complexType>
- <xsd:sequence>
<xsd:element name="CreatePdfSignatureReturn" type="xsd:base64Binary" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
- <wsdl:message name="CreatePdfSignature">
<wsdl:part name="CreatePdfSignature" element="tsi:CreatePdfSignature" />
</wsdl:message>
- <wsdl:message name="CreatePdfSignatureResponse">
<wsdl:part name="CreatePdfSignatureResponse" element="tsi:CreatePdfSignatureResponse" />
</wsdl:message>
- <wsdl:portType name="GlobalEsignSoapExt">
- <wsdl:operation name="CreatePdfSignature">
<wsdl:input message="tns:CreatePdfSignature" />
<wsdl:output message="tns:CreatePdfSignatureResponse" />
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
<wsdl:part name="in1" type="xsd:string"/>   was changed to <xsd:element name="in0" type="xsd:string" /> .
Please let me know, whether you succeeded.
Kind regards
Heinz Schäfe

SOAP receiver channel with https url

Hi All,
We are working on SAP PO 7.4. We have RFC to SOAP scenario. To connect with external target system we are using https url.
We don't have any sign, encrypt requirement, do we still need to maintain certificates in Key Store as we are using https?
Thanks
Shivi

No.you don't have to select that option.
But you have to install the certificates.
Below one can help you.
How to Enable SSL certificate at the receiver SOAP Adapter

How to configure HTTP receiver comm channel with dynamic URL parameters?

I need to perform HTTP Post using PI. URL contains some parameters. I need to set these parameters with different values in run time.
Please help to do this.
Thanks
Ranji

Check the section Adapter Specific Message Attributes from this help section:
http://help.sap.com/saphelp_nw70/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
The parameters can be set in the Message Mappinga nd then using the appropriate options in communication they can be included in the message header....for more info search with keywords "Dynamic Configuration" and you will get to know how the procedure works.
Regards,
Abhishek.

Error in SOAP Receiver channel

Hi,
We are working on IDOC to SOAP Scenario (Connecting to third party).
We have configured the SOAP Receiver channel with the Target URL and teh corresponding SOAP Action.
But the SOAP Receiver channel gives the error while processing and sends back the following error message in log :
"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/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Value cannot be null. Parameter name: s."
Payload seems to look fine in XI and SAP.
Any help on this ?
Thanks and regards,
Vikas

Hi Vikas,
Copy the payload from SXMB_MONI after mapping and check with SOAPGUI or Altova, if it working fine then your payload is good. You can use the WSDL to ganarate and send independent soap request from these tools.
Besides this IDOC is Asyc, you need to use RequestResponseBean and ResponseOneWayBean to get the response from SOAP. Check the following and try to simulate it.
https://wiki.sdn.sap.com/wiki/display/XI/File-RFC-File%28Without+BPM%29
Server was unable to process request. ---> Value cannot be null. Parameter name: s."
The error specifies that the request has null value, check the parameter specified in the error message and make sure that is not null while you are sending the request.
Regards,
Prasanna

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á

Connection problem in SOAP Sender Channel

Dear All,
I have created two SOAP Sender channel with the following specification:
Transport Protocol - HTTP
Message Protocol - SOAP 1.1
HTTP Security Level - HTTP
But while sending a message from a Java client, I am getting the following error :
The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Basic realm="XISOAPApps"'.
Please suggest if you find any way out.
Thanks and Regards,
Rana Brata De

Hi Rana
Looks like you have used authentication scheme as 'anonymous'. But you have chosen the option 'HTTP' in soap adapter.
So you have to pass the user id and password during the call.
Sample Code:
ICalcCTCWebService calcCTCWebService = calcCTCWebServiceImplServiceLocator.getCalcCTCWebServiceImplPort();
Stub stub = (Stub)calcCTCWebService;
stub._setProperty(Stub.USERNAME_PROPERTY, "abc");
stub._setProperty(Stub.PASSWORD_PROPERTY, "xyz");
You can also test the WSDL from SOAP UI and provide user name and password in the header section in SOAP UI and see if the message goes to PI or not.
You can also try the below option in the sender soap adapter and see if it works or not.

HTTP Error 501 with SOAP Sender channel

Hello,
i've am simple Question:
I want to call the following SAP XI SOAP Sender channel "MySoapSenderChannel":
XI-Parameters:
namespace: <myInterfaceNamespace>
Interface: <myAsynchInterface>
QoS: Exactly Once in Order
Queue: MY_QUEUE
We do not care about the Response - so the processing is asynchron.
Thus my interface mapping maps to asynch interfaces. The desitnation
is an ABAP Proxy. The configuration has been done and tested.
Here my question:
according the documentation, the URL has the following syntax:
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel.
In our case:
http://<myHost>:8002/XISOAPAdapter/MessageServlet?channel=:MyService:MySoapSenderChannel.
But when i generate a WSDL for the interface out of the Configuration, the address is:
<soap:address location="http://<myHost>:8002/sap/xi/engine?type=entry&version=3.0&Sender.Service=MyService&Interface=...
and so forth.
But was is the difference between these 2 possibilities?
Why do i get HTTP Error 501 when i use the URL from the documentation (the first one)?
Thanx in advance
Gunnar

Gunnar,
I will suggest you to go through it once to check all your connection.
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Regards,
Sarvesh

Error in receiver comm channel

Hi All,
   I am working on scenario file to file with out IR.just picking up the file from sap app server and placing in target ftp server.
My sender comm channel is picking the file fine but when in receiver comm channel i am getiing error as
"Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Unknown payload format 0 in message"
"Attempt to process file failed with Unknown payload format 0 in message"
i have checked in content of the file it contains no special character. are any security is being maintained.
please advise on this.
Thanks,
Bhaskar

Hi Jude,
I have checked in sender comm channel in message display tool under message content i am getting error as below.
messagecontent
message part [soap document]
500   Internal Server Error
SAP J2EE Engine/6.40
Application error occurred during request processing.
Details:   Error [javax.servlet.ServletException: null], with root cause [java.lang.NullPointerException: null].
Exception id: [00145E474044003F000018AD00003E0D000471A1CBF6A02A]
what would be the error and how can i find it.
Is this basis related issue?
Thanks,
Bhaskar

Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

Hi all,
We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
We are running PI 7.4.
Any help is appreciated.
Thanks,
Pushpa

Hi,
Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
1. Test a fresh message from local SOAP UI tool.
2. Pick 3rd party WSDL file and Import in SOAP UI tool.
3. Put some dummy data for mandatory fields
4. Trigger it msg and ckh if you get successful / response msg.
5. Check if firewall is open and that URL is not blocked.
Hope it helps
Regards,
Azhar

Mapping Error - Dump source message to file adapter comm channel

Hi
Does anyone know of a way to dump the source message to a file adapter comm channel if - and only if - the message fails during mapping. For example, we receive a message from a trading partner that lacks an element that is mandatory during the mapping. When the mapping fails, the source message is sent - as is - to a file adapter comm channel.
I don't need anything more than the source message i.e. no need for any errors etc... to be included.
The kicker.. I would like to do this without using BPM if at all possible.
Any ideas greatly appreciated. Thx, Duncan

Hey Ram,
Go to Integration Directory and open the Receiver Determination for your scenario.
Check the configured receiver services. They are in a table-like area in the middle of the screen.
In this table of configured receiver services for that particular Sender Service/Interface, you should have the system that normally receives that message (your ERP or any other application system) and the service that contains the receiver file comm channel that will receive the message in case of error.
Check help.sap.com for help on condition editor on receiver determinations.
Now, the issue. You can only check whether a field exists, you can't check whether it doesn't exist (There's only a "EXIST" operator, and no negative operator). Thus, you can only do the following: always send messages to File, but you can avoid messages that dont have field from being sent to App System. Yeah, that sucks...
But don't fear, young padawan! There is a possible workaround. =D
In your message mapping, do the following for that particular field:
If field exists (check with Exist and IF standard functions) just bypass the field. Else, map the field with an impossible value (like string "$CREATED$"). Then, in your receiver determination, you will do the following conditions:
for App System: If field =/= $CREATED$
for File Receiver: If field = $CREATED$
Now, if the field doesnt exist, it will have value $CREATED$, thus the message will be sent to File and not to App System. If the field exists, the message will be sent to App and not to File.
Try that out.
Regards,
Henrique.

SOAP Receiver Channel error

Dear PI and SOAP experts:
I have been having trouble getting a SOAP Receiver channel working for a webservice. I get the following error in the SOAP receiver channel:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: content-type of the request should be text/xml
I also forced the content-type as text/xml;charset=utf-8 from PI by using the MessageTransformBean as a module in the SOAP Receiver channel, but still getting the same response.
When I called the same w/s using XMLSpy and SOAPUI, it works fine and I get a positive response. So there is no problem with the webservice.
I also tried calling a different webservice from PI and that works fine too. So there is no problem with outbound communication with PI and the SOAP receiver channel either.
But whenever I send the request from PI to the first webservice it gives me the above error.
Thank you.
Param.

Hi Param,
Also, please do have a look at the following link which could be of help to you.
https://wiki.sdn.sap.com/wiki/display/XI/SOAPMessagesin+XI
Best Regards

SOAP comm channel with SSLException error

Similar Messages

Maybe you are looking for