Problem with SOAP Scenario

Hi,
I am trying a http to soap scenario.
In the receiver soap adapter, I have specified the following:
Target url: http://test.abc.com/
Action: handleLogin()
When I send the request, I get a "time out error" as the response in the http client tool.
However, in sxi_monitor, I get a webpage as the response(A web page is being displayed in the monitor).
What I was expecting is a response message that matches the wsdl.
I have tried using "" and a blank value for the Action field in the soap adapter, but no luck.
Any help would be appreciated.
Thanks,
Smitha.

Hi Shabarish,
Thanks for your response.
I provided the operation name in the soap adapter as specified in the blog, but I am getting a http_adapter exception. (500 internal server error)
Any clues?
Thanks,
Smitha.

Similar Messages

Another problem with SOAP sender

I have another problem with SOAP scenario in a different environment (PI 7.0) from my earlier post.
Scenario:
Soap Sender -> PI -> Soap Receiver
Following steps from GoogleSearch SOAP scenario in the SAP How-to Guide for SAP NetWeaver '04 entitled: "How To... Use the XI 3.0 SOAP Adapter" version 1.00 - March 2006.
I have loaded in the api.google.com/GoogleSearch.wsdl file as an External definition and created the SOAP receiver as described in the How-to guide. It takes a doGoogleSearch as input and sends back a doGoogleSearchResponse (Sync Call).
Note that the GoogleSearch.wsdl contains a complex type ResultElementArray that refers to ResultElement\[\], and a DirectoryCategoryArray that refers to DirectoryCategory\[\]. The ResultElement and DirectoryCategory types are defined in the GoogleSearch.wsdl file.
Problem One:
The generated WSDL for the SOAP sender contains the ResultElementArray and DirectoryCategoryArray types but it DOES NOT contain the required ResultElement and DirectoryCategory types. XML Spy complains that this WSDL is not valid because the type ResultElement\[\] is not defined.
Problem Two:
I generate a SOAP message in XML Spy, provide values for the doGoogleSearch fields, and send. In SXMB_MONI, the SOAP sender payload contains only the <key> value from the doGoogleSearch message body, i.e. <part name="key" type="xsd:string" />
The other doGoogleSearch fields seem to be missing, i.e.
<part name="q" type="xsd:string" />
<part name="start" type="xsd:int" />
<part name="maxResults" type="xsd:int" />
<part name="filter" type="xsd:boolean" />
<part name="restrict" type="xsd:string" />
<part name="safeSearch" type="xsd:boolean" />
<part name="lr" type="xsd:string" />
<part name="ie" type="xsd:string" />
<part name="oe" type="xsd:string" />
Does anyone know why:
(1) PI/XI seems to leave out the ResultElement and DirectoryCategory types from the SOAP sender service WSDL file?
(2) The doGoogleSearch message seen in SXMB_MONI contains only the first <key> field, and not the other fields?
Thanks for any help with this.

I have another problem with SOAP scenario in a different environment (PI 7.0) from my earlier post.
Scenario:
Soap Sender -> PI -> Soap Receiver
Following steps from GoogleSearch SOAP scenario in the SAP How-to Guide for SAP NetWeaver '04 entitled: "How To... Use the XI 3.0 SOAP Adapter" version 1.00 - March 2006.
I have loaded in the api.google.com/GoogleSearch.wsdl file as an External definition and created the SOAP receiver as described in the How-to guide. It takes a doGoogleSearch as input and sends back a doGoogleSearchResponse (Sync Call).
Note that the GoogleSearch.wsdl contains a complex type ResultElementArray that refers to ResultElement\[\], and a DirectoryCategoryArray that refers to DirectoryCategory\[\]. The ResultElement and DirectoryCategory types are defined in the GoogleSearch.wsdl file.
Problem One:
The generated WSDL for the SOAP sender contains the ResultElementArray and DirectoryCategoryArray types but it DOES NOT contain the required ResultElement and DirectoryCategory types. XML Spy complains that this WSDL is not valid because the type ResultElement\[\] is not defined.
Problem Two:
I generate a SOAP message in XML Spy, provide values for the doGoogleSearch fields, and send. In SXMB_MONI, the SOAP sender payload contains only the <key> value from the doGoogleSearch message body, i.e. <part name="key" type="xsd:string" />
The other doGoogleSearch fields seem to be missing, i.e.
<part name="q" type="xsd:string" />
<part name="start" type="xsd:int" />
<part name="maxResults" type="xsd:int" />
<part name="filter" type="xsd:boolean" />
<part name="restrict" type="xsd:string" />
<part name="safeSearch" type="xsd:boolean" />
<part name="lr" type="xsd:string" />
<part name="ie" type="xsd:string" />
<part name="oe" type="xsd:string" />
Does anyone know why:
(1) PI/XI seems to leave out the ResultElement and DirectoryCategory types from the SOAP sender service WSDL file?
(2) The doGoogleSearch message seen in SXMB_MONI contains only the first <key> field, and not the other fields?
Thanks for any help with this.

Synchronous RFC -- SOAP Scenario: problem with SOAP Response/Fault Mapping

Hi,
I've a synchronous RFC --> PI --> SOAP Scenario. The problem is that the message structure of the sending RFC doesn't match the Webservice Structure.
The (SAP standard) RFC has just a Request / Response message structure. Part of the Response Message structure is a exception structure.
The Webservice has a Request / Response message structure and in case of an error I get a SOAP:Fault.
Problem now is that I cannot configure that scenario without usage of BPM as I will have to map SOAP:Response or SOAP:Fault to the RFC Response structure.
Has anybody another idea to do that synchronous scenario (with usage of message mapping) without BPM?
BR
Holger

1)
you maus define 3 mapping.
1)request
2)response
3)Fault
in Interface mapping define at response boths (2-3) mapping. its clear??
2)
otherwise sometjhing is not clear, why do you want fault?? why dont you get only response message. we implement this kind of response:
<response_MT>
<ID> (error ID)
<system> (target system)
<error> (Error Description)
</response>
by this way fault message is not needed. but if you must have it just follow the top of message else, propose second.
Thanks
Rodrigo
Thanks
Rodrigo
Edited by: Rodrigo Pertierra on Feb 25, 2008 11:52 AM

Problem with soap receiver adapter

Hi All
I have Idoc sender and soap receiver in my scenario.
I am calling web service deployed on WAS.
The web service is getting called but the acknowledgement message in xi contains following system error acknowledgement because of which xi changes the status of message to WAIT and starts retrying.
<?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.aii.af.ra.ms.api.MessagingException: java.net.SocketTimeoutException: Read timed out: com.sap.aii.af.ra.ms.api.RecoverableException: java.net.SocketTimeoutException: Read timed out</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please anybody can help to resolve this problem. This scenario has worked without any error previously.
Thanks in advance
Beena

Hi Bhavesh,
It is an Async call where method does not return anything.
I added entries in IDX_NOALE but still it is setting the message status to WAIT and does retry.
Following is the Audit Log in Runtime workbench :
Audit Log for Message: 22b3052d-c519-034e-85db-e65d541d6414
Time Stamp Status Description
2006-12-13 10:25:23 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
2006-12-13 10:25:23 Error Exception caught by adapter framework: Read timed out
2006-12-13 10:25:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
2006-12-13 10:25:24 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:30:24 GMT+05:30 2006.
2006-12-13 10:25:24 Success The message status set to WAIT.
2006-12-13 10:30:25 Success Retrying to deliver message to the application. Retry: 1
2006-12-13 10:30:25 Success The message was successfully retrieved from the receive queue.
2006-12-13 10:30:25 Success The message status set to DLNG.
2006-12-13 10:30:25 Success Delivering to channel: INSPWCCT_PVtoSAP_Ack
2006-12-13 10:30:25 Success SOAP: request message entering the adapter
2006-12-13 10:35:28 Success SOAP: call failed
2006-12-13 10:35:28 Success SOAP: sending a delivery error ack ...
2006-12-13 10:35:28 Success SOAP: sent a delivery error ack
2006-12-13 10:35:28 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
2006-12-13 10:35:28 Error Exception caught by adapter framework: Read timed out
2006-12-13 10:35:28 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
2006-12-13 10:35:28 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:40:28 GMT+05:30 2006.
2006-12-13 10:35:28 Success The message status set to WAIT.
I have tried this scenario earlier. I am sending the same Idoc from R3 which was processed successfully earlier.
Thanks
Beena.

Problem with IDoc scenario - IDocs do not aarive to XI

Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.

Hi Olian ,
just check if u have followed all the following steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name
Regards,
AshwinM

XSLT Problem with soap namespace

Hi there,
I have a problem transforming an XML doc with soap elements, using XSLT (Xalan).
Here's the input:
<?xml version = "1.0" encoding = "ISO-8859-1"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns="http://www.ean.nl">
<testthis>123456</testthis>
</soap:Envelope>and here's the XSL:
<?xml version="1.0"?>
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" exclude-result-prefixes="soap">
<xsl:output method="xml" indent="yes"/>
<xsl:template match="soap:Envelope">
<Orders>
     <H01>
          <xsl:value-of select="testthis"/>
     </H01>
</Orders>
</xsl:template>
</xsl:transform>I expect to get something like:
<?xml version="1.0" encoding="UTF-8"?>
<Orders>
<H01>123456<H01>
<Orders>But instead I get:
<?xml version="1.0" encoding="UTF-8"?>
<Orders>
<H01/>
</Orders>I've tried a lot of things and I'm probably overseeing something stupid, but I'm stuck.
It seems as if anything without soap: namespace cannot be processed by my XSL (when I add it in the input XML and XSL it works).
Any help would be greatly appreciated.
Greetings,
Erik

Yes, I found it!
The following XSL for the same XML doc works!
<?xml version="1.0"?>
<xsl:transform xmlns:ean="http://www.ean.nl" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" exclude-result-prefixes="soap">
<xsl:output method="xml" indent="yes"/>
<xsl:template match="soap:Envelope">
<Orders>
     <H01>
          <xsl:value-of select="ean:testthis"/>
     </H01>
</Orders>
</xsl:template>
</xsl:transform>Thanks, you pointed me in the right direction :-)
Erik

Newline problem with soap

I'm having these weird problems with newlines. I'm sending \n in a message because I have a multi lined message i want parsed. Axis is receiving the message and throwing exceptions. I printed out the line it's parsing and it's giving this error that it can't parse:
'2.5
PID'
The parser is not supposed to parse past the \n but it seems to be trying to. I've tested this without webservices and it works fine, adding webservices into the equation gives me these errors.

Additional info: The problem is the same in the entire environment here (PI DEV, QAS and PRD) and on another PI machine.
So I doubt very much if it's cache related.
Edit: This is the 'application 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>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Edited by: Frederik-Jan Roose on Dec 7, 2009 11:11 AM

Problem with SOAP Servlet

Hi,
I have a SOAP servlet, but It is the fist SOAPServlet as I use.
I think that the vsd that developper of SOAP servlet provide is ok.
But, I do not understand which is the XML that I could provide to it.
It is posible that I have a problem with XML, SCHEMA and SOAP.
Could you help me , I attach the VSD, but I need a tool or a sample file in order to call my SOAP servlet.
<xsd:schema xmlns:xsd="http://schemas.xmlsoap.org/soap/encoding">
    <xsd:complexType name="STD_TRN1_I_PARM_V_TYPE">
      <xsd:sequence>
        <xsd:element name="COD_TX_DI">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00004"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="ID_INTERNO_TERM_TN">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00008"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="ID_EMPL_AUT">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00008"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="NUM_SEC">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00007"/>
                <fractionDigits value="00"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="COD_TX">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00008"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="TR_CONS_SALDOS_VISTA_EVT_Y_TYPE">
      <xsd:sequence>
        <xsd:element name="COD_CENT_UO">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00004"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="NUM_SEC_AC">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00010"/>
                <fractionDigits value="00"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="COD_NRBE_EN">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00004"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="STD_TRN1_O_PARM_V_TYPE">
      <xsd:sequence>
        <xsd:element name="HORA_OPRCN" type="xsd:time"/>
        <xsd:element name="FECHA_OPRCN" type="xsd:date"/>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_DISPO_V_TYPE">
      <xsd:sequence>
        <xsd:element name="STD_DEC_15Y2">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00015"/>
                <fractionDigits value="02"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_SDO_CONTABLE_V_TYPE">
      <xsd:sequence>
        <xsd:element name="IMP_SDO">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00015"/>
                <fractionDigits value="02"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_SDO_RETEN_V_TYPE">
      <xsd:sequence>
        <xsd:element name="IMP_SDO">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00015"/>
                <fractionDigits value="02"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_SDO_AUT_V_TYPE">
      <xsd:sequence>
        <xsd:element name="IMP_SDO">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00015"/>
                <fractionDigits value="02"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_SDO_INCID_V_TYPE">
      <xsd:sequence>
        <xsd:element name="IMP_SDO">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00015"/>
                <fractionDigits value="02"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_BLOQUEOS_V_TYPE">
      <xsd:sequence>
        <xsd:element name="STD_CHAR_01">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00001"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_SDO_CONECT_V_TYPE">
      <xsd:sequence>
        <xsd:element name="IMP_SDO">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00015"/>
                <fractionDigits value="02"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="COD_IDIOMA_V_TYPE">
      <xsd:sequence>
        <xsd:element name="COD_IDIOMA">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00002"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_ANOTACIONES_V_TYPE">
      <xsd:sequence>
        <xsd:element name="STD_CHAR_01">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00001"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="TR_CONS_SALDOS_VISTA_EVT_Z_TYPE">
      <xsd:sequence>
        <xsd:element name="COD_NUMRCO_MONEDA">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00003"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="PSV_DISPO_V" type="PSV_DISPO_V_TYPE"/>
        <xsd:element name="PSV_SDO_CONTABLE_V" type="PSV_SDO_CONTABLE_V_TYPE"/>
        <xsd:element name="PSV_SDO_RETEN_V" type="PSV_SDO_RETEN_V_TYPE"/>
        <xsd:element name="PSV_SDO_AUT_V" type="PSV_SDO_AUT_V_TYPE"/>
        <xsd:element name="PSV_SDO_INCID_V" type="PSV_SDO_INCID_V_TYPE"/>
        <xsd:element name="PSV_BLOQUEOS_V" type="PSV_BLOQUEOS_V_TYPE"/>
        <xsd:element name="PSV_SDO_CONECT_V" type="PSV_SDO_CONECT_V_TYPE"/>
        <xsd:element name="COD_CSB_OF">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00004"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="NOMB_50">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00050"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="COD_INTERNO_UO">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00004"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="COD_IDIOMA_V" type="COD_IDIOMA_V_TYPE"/>
        <xsd:element name="PSV_ANOTACIONES_V" type="PSV_ANOTACIONES_V_TYPE"/>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="STD_TRN1_MSJ_PARM_V_TYPE">
      <xsd:sequence>
        <xsd:element name="TEXT_ARG1">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00018"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="TEXT_CODE" type="xsd:int"/>
      </xsd:sequence>
    </xsd:complexType>
<xsd:complexType name="TR_CONS_SALDOS_VISTA_TRN1">
    <xsd:complexType name="TR_CONS_SALDOS_VISTA_TRN1_O_TYPE">
      <xsd:sequence>
        <xsd:element name="RTRN_CD" type="xsd:int"/>
        <xsd:element name="STD_TRN1_O_PARM_V" type="STD_TRN1_O_PARM_V_TYPE"/>
        <xsd:element name="TR_CONS_SALDOS_VISTA_EVT_Z" type="TR_CONS_SALDOS_VISTA_EVT_Z_TYPE"/>
        <xsd:complexType name="STD_TRN1_MSJ_PARM_V_OCCURS">
            <xsd:element name="STD_TRN1_MSJ_PARM_V" type="STD_TRN1_MSJ_PARM_V_TYPE" maxOccurs="000005"/>
        </xsd:complexType>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="TR_CONS_SALDOS_VISTA_TRN1_I_TYPE">
      <xsd:sequence>
        <xsd:element name="STD_TRN1_I_PARM_V" type="STD_TRN1_I_PARM_V_TYPE"/>
        <xsd:element name="TR_CONS_SALDOS_VISTA_EVT_Y" type="TR_CONS_SALDOS_VISTA_EVT_Y_TYPE"/>
      </xsd:sequence>
    </xsd:complexType>
</xsd:complexType>
</xsd:schema>Thanks you

Hi,
I have a SOAP servlet, but It is the fist SOAPServlet as I use.
I think that the vsd that developper of SOAP servlet provide is ok.
But, I do not understand which is the XML that I could provide to it.
It is posible that I have a problem with XML, SCHEMA and SOAP.
Could you help me , I attach the VSD, but I need a tool or a sample file in order to call my SOAP servlet.
<xsd:schema xmlns:xsd="http://schemas.xmlsoap.org/soap/encoding">
    <xsd:complexType name="STD_TRN1_I_PARM_V_TYPE">
      <xsd:sequence>
        <xsd:element name="COD_TX_DI">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00004"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="ID_INTERNO_TERM_TN">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00008"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="ID_EMPL_AUT">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00008"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="NUM_SEC">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00007"/>
                <fractionDigits value="00"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="COD_TX">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00008"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="TR_CONS_SALDOS_VISTA_EVT_Y_TYPE">
      <xsd:sequence>
        <xsd:element name="COD_CENT_UO">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00004"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="NUM_SEC_AC">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00010"/>
                <fractionDigits value="00"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="COD_NRBE_EN">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00004"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="STD_TRN1_O_PARM_V_TYPE">
      <xsd:sequence>
        <xsd:element name="HORA_OPRCN" type="xsd:time"/>
        <xsd:element name="FECHA_OPRCN" type="xsd:date"/>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_DISPO_V_TYPE">
      <xsd:sequence>
        <xsd:element name="STD_DEC_15Y2">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00015"/>
                <fractionDigits value="02"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_SDO_CONTABLE_V_TYPE">
      <xsd:sequence>
        <xsd:element name="IMP_SDO">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00015"/>
                <fractionDigits value="02"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_SDO_RETEN_V_TYPE">
      <xsd:sequence>
        <xsd:element name="IMP_SDO">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00015"/>
                <fractionDigits value="02"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_SDO_AUT_V_TYPE">
      <xsd:sequence>
        <xsd:element name="IMP_SDO">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00015"/>
                <fractionDigits value="02"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_SDO_INCID_V_TYPE">
      <xsd:sequence>
        <xsd:element name="IMP_SDO">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00015"/>
                <fractionDigits value="02"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_BLOQUEOS_V_TYPE">
      <xsd:sequence>
        <xsd:element name="STD_CHAR_01">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00001"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_SDO_CONECT_V_TYPE">
      <xsd:sequence>
        <xsd:element name="IMP_SDO">
            <xsd:simpleType base="xsd:decimal">
                <totalDigits value="00015"/>
                <fractionDigits value="02"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="COD_IDIOMA_V_TYPE">
      <xsd:sequence>
        <xsd:element name="COD_IDIOMA">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00002"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="PSV_ANOTACIONES_V_TYPE">
      <xsd:sequence>
        <xsd:element name="STD_CHAR_01">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00001"/>
            </xsd:simpleType>
        </xsd:element>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="TR_CONS_SALDOS_VISTA_EVT_Z_TYPE">
      <xsd:sequence>
        <xsd:element name="COD_NUMRCO_MONEDA">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00003"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="PSV_DISPO_V" type="PSV_DISPO_V_TYPE"/>
        <xsd:element name="PSV_SDO_CONTABLE_V" type="PSV_SDO_CONTABLE_V_TYPE"/>
        <xsd:element name="PSV_SDO_RETEN_V" type="PSV_SDO_RETEN_V_TYPE"/>
        <xsd:element name="PSV_SDO_AUT_V" type="PSV_SDO_AUT_V_TYPE"/>
        <xsd:element name="PSV_SDO_INCID_V" type="PSV_SDO_INCID_V_TYPE"/>
        <xsd:element name="PSV_BLOQUEOS_V" type="PSV_BLOQUEOS_V_TYPE"/>
        <xsd:element name="PSV_SDO_CONECT_V" type="PSV_SDO_CONECT_V_TYPE"/>
        <xsd:element name="COD_CSB_OF">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00004"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="NOMB_50">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00050"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="COD_INTERNO_UO">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00004"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="COD_IDIOMA_V" type="COD_IDIOMA_V_TYPE"/>
        <xsd:element name="PSV_ANOTACIONES_V" type="PSV_ANOTACIONES_V_TYPE"/>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="STD_TRN1_MSJ_PARM_V_TYPE">
      <xsd:sequence>
        <xsd:element name="TEXT_ARG1">
            <xsd:simpleType base="xsd:string">
                <maxLength value="00018"/>
            </xsd:simpleType>
        </xsd:element>
        <xsd:element name="TEXT_CODE" type="xsd:int"/>
      </xsd:sequence>
    </xsd:complexType>
<xsd:complexType name="TR_CONS_SALDOS_VISTA_TRN1">
    <xsd:complexType name="TR_CONS_SALDOS_VISTA_TRN1_O_TYPE">
      <xsd:sequence>
        <xsd:element name="RTRN_CD" type="xsd:int"/>
        <xsd:element name="STD_TRN1_O_PARM_V" type="STD_TRN1_O_PARM_V_TYPE"/>
        <xsd:element name="TR_CONS_SALDOS_VISTA_EVT_Z" type="TR_CONS_SALDOS_VISTA_EVT_Z_TYPE"/>
        <xsd:complexType name="STD_TRN1_MSJ_PARM_V_OCCURS">
            <xsd:element name="STD_TRN1_MSJ_PARM_V" type="STD_TRN1_MSJ_PARM_V_TYPE" maxOccurs="000005"/>
        </xsd:complexType>
      </xsd:sequence>
    </xsd:complexType>
    <xsd:complexType name="TR_CONS_SALDOS_VISTA_TRN1_I_TYPE">
      <xsd:sequence>
        <xsd:element name="STD_TRN1_I_PARM_V" type="STD_TRN1_I_PARM_V_TYPE"/>
        <xsd:element name="TR_CONS_SALDOS_VISTA_EVT_Y" type="TR_CONS_SALDOS_VISTA_EVT_Y_TYPE"/>
      </xsd:sequence>
    </xsd:complexType>
</xsd:complexType>
</xsd:schema>Thanks you

Problem with SOAP receiver

Hello,
Our PI system is 7.4 . We have a lot of interface with related to proxy to soap.When they are used very intensively, errors occur in soap receiver .
Types are error:
503 server not avalibale,
401 unauthorized ,
invalid content type for SOAP:TEXT/HTML such as...
When system is restarted, mostly it is worked but after while again errors occur and a lot of message is waiting in queue.
what can we do for it?
Thanks in advance,
Nurhan

Hi Claudia,
It is dual stack installation. While calling soap receiver adapter, error occur. In sxmb_moni display error as follows:
After restart, we have new error:
It is abap proxy to soap scenario. It's synchronous communication.
Thanks,
Nurhan

WLS 7.0 sp2 - Servlet Problems with SOAP messages

          I'm using Weblogic 7.0 SP2 and trying to create a Servlet to receive SOAP wrapped
          XML messages. I'm getting the following error. Is this a problem with WLS7.0sp2's
          support of JAXM? The System.out.println's indicate I have successfully received
          the incoming SOAP request and then successfully formatted the SOAP response, but
          upon returning saving the response it appears to blow up. Does anyone have any
          suggestions?
          I need to do the following in a servlet:
          - receive an incoming SOAP request with an embedded XML message
          - perform some processing
          - return a SOAP response with an embedded XML message
          Should I be using JAXM? Or can I do this same task easily with JAX-RPC?
          <Feb 24, 2004 4:10:42 PM AST> <Error> <HTTP> <101017> <[ServletContext(id=260434
          7,name=isd.war,context-path=)] Root cause of ServletException
          java.lang.Error: NYI
          at weblogic.webservice.core.soap.SOAPMessageImpl.saveRequired(SOAPMessag
          eImpl.java:360)
          at javax.xml.messaging.JAXMServlet.doPost(Unknown Source)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
          (ServletStubImpl.java:1058)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          pl.java:401)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          pl.java:306)
          at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
          n.run(WebAppServletContext.java:5445)
          at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
          eManager.java:780)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
          rvletContext.java:3105)
          at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
          pl.java:2588)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          >
          I've stripped the code down so that all it does is verifies the incoming SOAP/XML
          request and creates a hard-coded response... be gentle... I'm a novice at this
          import javax.xml.soap.*;
          import javax.servlet.*;
          import javax.servlet.http.*;
          // import javax.xml.transform.*;
          import java.util.*;
          import java.io.*;
          public class RegisterServlet extends HttpServlet
          static MessageFactory fac = null;
          static
          try
          fac = MessageFactory.newInstance();
          catch (Exception ex)
          ex.printStackTrace();
          public void init(ServletConfig servletConfig) throws ServletException
          super.init(servletConfig);
          public void doPost(HttpServletRequest req, HttpServletResponse resp) throws ServletException,
          IOException
          try
          System.out.println("** Note: doPost() Entering req = " + req);
          // Get all the headers from the HTTP request
          MimeHeaders headers = getHeaders(req);
          // Get the body of the HTTP request
          InputStream is = req.getInputStream();
          // Now internalize the contents of a HTTP request
          // and create a SOAPMessage
          SOAPMessage msg = fac.createMessage(headers, is);
          System.out.println("** Note: doPost() Step A");
          SOAPMessage reply = null;
          reply = onMessage(msg);
          System.out.println("** Note: doPost() Step B reply = " + reply);
          if (reply != null)
          * Need to call saveChanges because we're
          * going to use the MimeHeaders to set HTTP
          * response information. These MimeHeaders
          * are generated as part of the save.
          if (reply.saveRequired())
          System.out.println("** Note: doPost() Step C reply.saveRequired()");
          reply.saveChanges();
          resp.setStatus(HttpServletResponse.SC_OK);
          putHeaders(reply.getMimeHeaders(), resp);
          // Write out the message on the response stream
          OutputStream os = resp.getOutputStream();
          System.out.println("** Note: doPost() Step D os = " + os);
          reply.writeTo(os);
          os.flush();
          else
          resp.setStatus(HttpServletResponse.SC_NO_CONTENT);
          catch (Exception ex)
          throw new ServletException("** Error: SAAJ POST failed: " + ex.getMessage());
          static MimeHeaders getHeaders(HttpServletRequest req)
          Enumeration enum = req.getHeaderNames();
          MimeHeaders headers = new MimeHeaders();
          while (enum.hasMoreElements())
          String headerName = (String)enum.nextElement();
          String headerValue = req.getHeader(headerName);
          StringTokenizer values =
          new StringTokenizer(headerValue, ",");
          while (values.hasMoreTokens())
          headers.addHeader(headerName,
          values.nextToken().trim());
          return headers;
          static void putHeaders(MimeHeaders headers, HttpServletResponse res)
          Iterator it = headers.getAllHeaders();
          while (it.hasNext())
          MimeHeader header = (MimeHeader)it.next();
          String[] values = headers.getHeader(header.getName());
          if (values.length == 1)
          res.setHeader(header.getName(),
          header.getValue());
          else
          StringBuffer concat = new StringBuffer();
          int i = 0;
          while (i < values.length)
          if (i != 0)
          concat.append(',');
          concat.append(values[i++]);
          res.setHeader(header.getName(), concat.toString());
          // This is the application code for handling the message.
          public SOAPMessage onMessage(SOAPMessage message)
          SOAPMessage replymsg = null;
          try
          System.out.println("** Note: OnMessage() Entering msg = " + message);
          //Extract the ComputerPart element from request message and add to reply SOAP
          message.
          SOAPEnvelope reqse = message.getSOAPPart().getEnvelope();
          SOAPBody reqsb = reqse.getBody();
          //System.out.println("** Note: OnMessage() Step B");
          System.out.println("** Note: OnMessage () Step A Soap Request Message Body = "
          + reqsb);
          //Create a reply mesage from the msgFactory of JAXMServlet
          System.out.println("** Note: OnMessage () Step B");
          replymsg = fac.createMessage();
          SOAPPart sp = replymsg.getSOAPPart();
          SOAPEnvelope se = sp.getEnvelope();
          SOAPBody sb = se.getBody();
          System.out.println("** Note: OnMessage () Step C Soap Reply Before Message Body
          = " + sb);
          se.getBody().addBodyElement(se.createName("RegisterResponse")).addChildElement(se.createName("ErrorCode")).addTextNode("000");
          System.out.println("** Note: OnMessage () Step D Soap Reply After Message Body
          = " + sb);
          replymsg.saveChanges();
          System.out.println("** Note: OnMessage() Exiting replymsg = " + (replymsg));
          catch (Exception ex)
          ex.printStackTrace();
          return replymsg;


Michael,
I got the same error on WLS8.1/Win2K professional and apache FOP (old version).
After digging into the WLS code and FOP(old version). i found the conflict happens
on
the "org.xml.sax.parser" system property. In WLS code, they hard coded like the
following when startup weblogic server:
System.setProperty("org.xml.sax.parser", "weblogic.xml.jaxp.RegistryParser");
But the FOP code try to use the "org.xml.sax.parser" system property to find the
sax parser then conlict happens.
Here is the response from BEA support :
"I consulted with our developers regarding the question of whether we can change
the hard-coded value for the java system property: org.xml.sax.parser by using
a configuration parameter and I found that unfortunately there is no specific
setting to change the value. As you had mentioned in your note the org.xml.sax.parser
system property can be changed programmatically in your application code."
I solve my problem by using newer apache FOP (it never use the system property:org.xml.sax.parser
any more) and XML Registy for WLS8.1.
Good luck.
David Liu
Point2 Technologies Inc.
"p_michael" <[email protected]> wrote:
>
Help.
When we migrated from WLS 6.1 to WLS 7.0 SP2 when encountered a problem
with XML
parsing that did not previously exist.
We get the error "weblogic.xml.jaxp.RegistryParser is not a SAX driver".
What does this mean? And, what should we do about it.
p_michael

Problems with planning scenarios

Dear all
I've a huge problem with the scheduling of a project. I hope I can explain it properly.
I've created a project with some networks in it. The planning scenario is free scheduling and strict bottom up. I'm using the backward scheduling.
Some of the networks, which are connected with the "Main" Network now are not scheduled properly. For example I have an acitivity in the "Main" network which is connected with a FS relationship to an activity (this activity has set up a constraint earliest possible) of another network. When I'm carrying out the scheduling this activity is planned much later than the activity in the Main network. In some other similar networks the scheduling is carried out regurarly.
Now, when I'm changing the planning scenario to bottom up, canceling the start date in the network of concern and making a new scheduling of the whole project, the activity is placed in the right period. When I'm changing back the planning scenario and rescheduling the project once more, the activity is again postponed, even further in the future than before.
is somebody out there who is able to help me?
many thanks

Hello
is nobody out there who could help?
Best

Problem with SOAP to JDBC scenario. Please help!

Hi Experts,
I have configured a simple SOAP to JDBC scenario where the input data from webservice call is sent to JDBC for inserting into MSSQL database.
The problem is that even though I have setup the QOS in SOAP channel as EO but still in SXMB_MONI I can see the message getting processed as Synchrous but getting interface mapping not found error. But the data is getting inserted in the database.
Why is this not getting processed asynchrously? Please advice me if I am missing anything?
Thanks
Gopal

Hello Gopal,
Hope these lonks are useful to you:
SOAP to JDBC : EXCEPTION_DURING_EXECUTE
Re: need help on SOAP-JDBC-RFC Scenario
SOAP to JDBC/RFC - RFC/JDBC to SOAP XI Scenario
Thanks,
Satya Kumar

Problem with SOAP receiver adapter? Please help!

Hi experts
   I have the following scenario:
   SAP R/3 -ABAP Proxy>XI--->SOAP --webservice
   As you can see, I am sending data from R/3 system to XI via ABAP proxy. XI then sends data or calls a webservice via SOAP adapter.
When I test this scenario I am getting a error in the sxmb_moni that is,
"com.sap.aii.af.ra.ms.api.DeliveryException: TEXT/HTML; HTTP 504 Gateway Time-out"
I have checked the webservice url and it is working fine.
Can somebody tell me why am I getting this error message? How do I resolve this?
Thanks
Gopal

Hi,
Can you please check the settings in Soap Adapter with Module Adapter setting with ModuleTranformBean parameters? There may be some problem. use HTTP Adapter and the message type 'HttpPostIn' to send as HTTP Post.
Also
There is the note 450226 gives an overview over error codes
Probably below solution may help you.........
As an administrator on your portal go to:
System Configuration > Service Configuration >applications
Under: com.sap.portal.ivs.httpservice > Services > Proxy
If any proxy settings are configured you may end up with the problem, so you need to set the "nonProxyHosts" to include the trex host.
regards
Aashish Sinha
PS : reward points if helpful

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

Problems with Soap Adapter

Hi!
I need to implement the following scenario:
In SAP an user exit calls an RFC which uses a TCP/IP Connection (SM59) to the XI and sends data over this connection to it. The XI connects via a SOAP adapter my server program and sends the data in a soap stream to this server.
This works sometimes ok and sometimes not.
The status for those messages in the XI is "scheduled for outbound processing" with a little black arrow pointing to the right.
The error message in the Runtime Workbench for such a job is:
SOAP: request message entering the adapter
SOAP: call failed
SOAP: sending a delivery error ack ...
SOAP: sent a delivery error ack
How can I find out what the problem is?
Thanks,
Konrad

Hi,
When a message is scheduled for outbound processing, it is normally sent automatically.
does it always sit at this status or does it change after a while ?
If it is an issue with the connectivity from the Integration Server to the Adapter Framework you would get a different error message.
If it is an issue with connectivity from the SOAP adapter to your target, you would also get a different error - it is likely to be shown as an outright failure. Plus the error shown in the message is likely to be
"com.sap.aii.af.ra.ms.api.DeliveryException: java.net.ConnectException: Connection refused"
Hope this helps.
i think you need to get Basis involved to see why messages are not getting sent from the rfc queues automatically all the time.
Cheers
Colin.

Problem with SOAP Scenario

Similar Messages

Maybe you are looking for