SOAP to SOAP scenario testing

Hi Experts,
I have created SOAP to SOAP sceanrio.
I have to test it wheather its working or not.
please tell the full procedure how to test this.
Thanks

Hi,
We can test it through XML spy software, make WSDL format for source and and target structure in ID window Tools-->Define Web Service option.
Open source WSDL format file in spay software and give input meanwhile open receiver structure we can see the result.

Similar Messages

Testing of SOAP to FILE Scenario

Hi all
I have done with SOAP to FILE scenario.
--> while defining web service what we need to give in the URL????
--> How to test this SOAP to FILE scenario to see wheather it is working fine or not, what are the all options
Thanks
Dheeraj

Hi Dheeraj,
Definitely you can test it through the microsoft infopath tool.
steps to follow:
Executing wsdl File Using Microsoft Info Path
1.>Click on the design a from template
2.>Select the Web service icon and click ok
3.>Select the radio button u2018receive and submit datau2019 and click on next.
4.>Enter the path of the generated wsdl which u have saved and click next.
5.>Select the interface and click next
6.>Select the interface and click next.
7.>Double click on parameters.
8.>Double click on the parameter (which you want to send as request). Then click on the query field and click ok.
9.>Click next. And click Finish
10.>Now drag the query fields on the data fields to the left side. And click preview.
Please follow these steps I hope you will be able to test it.
Thanks and regards,
Nutan

SOAP to Proxy scenario communication error

Hi Friends,
 Now i am developing SOAP to Proxy scenario, i am testing WSDL file using SOAP UI software and i am getting an error in SOAP UI tool.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Error Report</title>
<style>
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
A:link {color : #0059AA;}
A:visited {color : #999999;}
A:active {color : #999999;}
</style>
</head>
<body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0">
<table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75">
<tr bgcolor="#FFFFFF">
<td align="left" colspan="2" height="48"> 403 Forbidden</td>
</tr>
<tr bgcolor="#3F73A3">
<td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>
<td height="23"><img width=1 height=1 border=0 alt=""></td>
<td align="right" height="23">SAP NetWeaver Application Server </td>
</tr>
<tr bgcolor="#9DCDFD">
<td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td>
</tr>
</table>
 
 Error: You are not authorized to view the requested resource.
 <a href="https://wiki.sdn.sap.com/wiki/x/wIN3Cw">SAP Technology Troubleshooting Guide</a>
<table>
<tr>
<td valign="top"> Details:</td>
<td valign="top"><PRE>No details available.</PRE></td>
</tr>
</table>
</body>
</html>
I have tried with the same WSDL earlier it was working fine, now its not working and throwing the above error.
Kindly suggest me to overcome from this issue.
Regards,
Senthil.

Hi Senthil,
Try with the authentication preemtive. Also, check your URL because that error seems that you are accessing to wrong PI section or your user has not the enough credentials, try with PIAPPLUSER or with the same roles that this user.
Regards.

Soap to proxy scenario Getting exception caught with cause error

Hi Experts,
MY scenario is soap to proxy i am getting below exception message in advanced engine configuration in ICO.
OAP: request message entering the adapter with user J2EE_GUEST
09/10/2014 11: 06: 03 346 XI Information Packaging (Bulk Mode) is not Enabled, Proceeding to the Normal Processing.
09/10/2014 11: 06: 03 346 XISOAP Information: Received an XI message for processing
09/10/2014 11: 06: 03 598 Error SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
09/10/2014 11: 06: 03 598 Information SOAP: completed the processing
OAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
09/10/2014 11: 06: 03 598 Information SOAP: completed the processing
09/10/2014 11: 06: 03 598 Information SOAP: response message to continuing 7477aafa-38da-11e4-beed-00000028af0a
09/10/2014 11: 06: 03 599 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
09/10/2014 11: 06: 03 599 Error SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault: Error in processing the Web Service; Other details in the error log of the Web Service from the provider side (Registration UTC 20,140,910,110,603; 6EDA38E4CE67F1B3B939005056882C3A transaction ID)
payload is contains some special charters in which is in protiguse language
example.
• AWPJ SERV DE TERCERIZ and
dot is the special char
same payload while testing using sproxy tcode dot "•" is converting in " # "symbol and with out error its successfully updating the database in ECC.
while testing using the same payload using soap ui removing the dot symbol from the field its successfully processing and updating the database.
is this interface is failing in PI level ? or ECC i am not getting dump in ecc.
is there any special character conversation in sap pi level.
where this message exactly failing is in PI level or in ECC level?
Help us find the solution.

Hi Ravinder,
When you mark the option Do not use SOAP envelope the adapter will not generate the SOAP envelope therefore you need to set an extra mapping in the Request to wrap the SOAP envelope. For example with XSL:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml"/>
 <xsl:template match="/">
 <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Header/>
 <SOAP:Body>
 <xsl:copy-of select="/"/>
 </SOAP:Body>
 </SOAP:Envelope>
 </xsl:template>
</xsl:stylesheet>
Later in the response you will have the SOAP envelope tags. (You can do a first try without java mapping only to see in the monitoring the response with the junk character).
When you determine the junk character you can try to use and to modify the next java mapping SAP PI - Deciphering apostrophes in XML - Process Integration - SCN Wiki to deal with your problem.
Hope this helps.
Regards.

JCO problem in SOAP to file scenario

Hey guys
i m doin a SOAP to file scenario and getting a JCO error in moni,the status of my queue in SMQ2 is SYSFAIL,when i check the TCP/IP connection in SM59 i find error in two places
AI_DIRECTORY_JCOSERVER and AI_RUNTIME_JCOSERVER .when i test connection for both of them i get the followin error "Error opening and RFC connection".
is this error dues to some server problem of something wrong in my scenario.?
the SOAP adapter in RWB is green.
i tried to unlock and delete the queue in SMQ2 but when i execute my scenario again,it gets SYSFAIL error.
thanx
ahmad

Hi,
If you restart the J2ee engine, it will work.
But The error may because of many reasons
-Might be because of lots of messages are to be processed simultaneously.
-Increasing the number of processes in VisualAdmin (VisualAdmin>JCO RFC Provider>AI_RUNTIME_<SID>) and see if that helps.
-This SAP Note may help u -709140.
Hope this helps,
Regards,
Moorthy

Soap to rfc scenario error

Hi PI Experts,
For the first time i was doing soap to rfc scenario. I have created all the objects in the ID and in the IR and also created a web service from ID an then i have saved the wsdl in my system. I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
so kindly please help me to solve this scenario.
Thanks & Regards,
B.Srinivas Prasad.

I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
Make sure that its in the below format :
From SAP help :
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
and check Sender Soap Channel Status is it activated/not and check Cache Status

Doubt Regarding SOAP to File Scenario

Hi All,
I am trying to create a SOAP to File scenario .These are the following things I have done so far :
IR - 2 datatypes ( 1 for soap message and 1 for file message )
       2 message types for the corresponding messages
      2 Message interfaces, both are asynchronous
      1 message mapping
      1 interface mapping
ID- 2 business systems (1 to send soap, 1 to recieve file )
    2 communiccation channel (soap sender, file receiver )
soap sender adapter parameters - Interface Name - Message interface for soap message
                                                  interface namespace - scenario namespace
Then, i generated a wsdl file to expose the outbound message interface for soap message as a web service, url for message interface : http://host:port.XISOAPAdapter/MessageServlet?:service:channel.
After generating the wsdl file, i imported it in external definition
Could anyone plz. tell me, is this the right approach to creat this scenario ? how can I test this scenario?using altova spy ?

Hi,
The URL you have mentioned to genarate WSDL is not a valid one
http://host:port.XISOAPAdapter/MessageServlet?:service:channel.
Check the below valid URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:service:channel.
You no need to import this to the Eexternal Definition as you already have DT,MT and MI, Any way this dosn't make any difference.
You can use SOAPGUI Tool to test:
->Create New Project -> provide WSDL you have genarated.
->Select Request and provide username and password and click the green button on top(Submit request to end URL).
Using altova spy:
Select SOAP Menu->Create New SOAP Request and provide your WSDL file and
SOAPMenu->Send Request To Server
Then you will get response..
Regards,
Prasanna

Soap to File Scenario with BPM

Hi Guys
I have create my Soap to File Scenario using BPM to split the file on "Transformation step" into 7 files and it must save these files to my FTP Server, when testing on sxmb_moni I don't get any errors but when checking on the FTP server no files are created, and I understand that it should be showing all seven processing on the sxmb_moni, but that is not happening.
I have used the ForEach mode on my Block.
What could I be doing wrong.
Thanks!!
Yonela

go to runtime work bench to see communication channel, especailly the receiver channel.
To see what happened on it

SOAP to IDOC scenario: java.lang.NullPointerException

Our trading partners currently post their xml files directly to our Integration Engine, where they are converted to idocs and posted to ECC. I am now trying to change this scenario to a SOAP to IDoc scenario so that we can process the files through the Adapter Engine using HTTPS. But I am running into an error when trying to post an xml file and I'm wondering what I am missing.
My SOAP communication channel is configured as follows:
Transport protocol: HTTP
Message protocol: SOAP 1.1
Adapter engine: Integration Server
HTTP Security Level: HTTP
Do Not Use Soap Envelope: *Checked*
Default interface and namespace have been specified
QoS: Exactly Once
If I post an xml file to this channel using the RWB test tool, I receive message java.lang.NullPointerException. However, I can find the message via the Message Monitoring in the RWB, with versions for both the AE and IE, each with status Successful. The idoc is created and successfully posted to ECC.
If I post this same file to the same URL using a third-party tool, I get the same error message along with more details (listed below). Futhermore, a message does *not* show up in the RWB and thus does not get converted to an idoc and posted to ECC.
Any ideas??? Thank you.
<?xml version="1.0" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Body>
- <SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
- <detail>
- <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
- <text>
- <![CDATA[
java.lang.NullPointerException
 at com.sap.aii.messaging.net.MIMEInputSource.decodeContentType(MIMEInputSource.java:425)
 at com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:323)
 at com.sap.aii.messaging.net.MIMEServletInputSource.parse(MIMEServletInputSource.java:58)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:381)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
]]>
</text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Here's the message log found in End-to-End monitoring from RWB test post (different from third-party tool message):
java.lang.NullPointerException
 at com.sap.plaf.frog.FrogScrollPaneUI$1.propertyChange(FrogScrollPaneUI.java:113)
 at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
 at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
 at java.awt.Component.firePropertyChange(Unknown Source)
 at javax.swing.JScrollPane.setHorizontalScrollBar(Unknown Source)
 at javax.swing.plaf.basic.BasicComboPopup.createScroller(Unknown Source)
 at javax.swing.plaf.basic.BasicComboPopup.<init>(Unknown Source)
 at com.sap.plaf.frog.FrogComboPopup.<init>(FrogComboPopup.java:21)
 at com.sap.plaf.frog.FrogComboBoxUI.createPopup(FrogComboBoxUI.java:410)
 at com.sap.plaf.frog.FrogComboBoxUI.installUI(FrogComboBoxUI.java:178)
 at javax.swing.JComponent.setUI(Unknown Source)
 at javax.swing.JComboBox.setUI(Unknown Source)
 at javax.swing.JComboBox.updateUI(Unknown Source)
 at javax.swing.JComboBox.init(Unknown Source)
 at javax.swing.JComboBox.<init>(Unknown Source)
 at com.sap.jnet.clib.JNcToolBar$ComboBox.<init>(JNcToolBar.java:64)
 at com.sap.jnet.clib.JNcToolBar.addComboBox(JNcToolBar.java:192)
 at com.sap.jnet.clib.JNcAppWindow.newUI(JNcAppWindow.java:607)
 at com.sap.jnet.clib.JNcAppWindow.newData(JNcAppWindow.java:1097)
 at com.sap.jnet.JNetData.createGraphFromDOM(JNetData.java:512)
 at com.sap.jnet.JNetData.load(JNetData.java:709)
 at com.sap.jnet.JNetApplet.initJNetApplet(JNetApplet.java:524)
 at com.sap.jnet.JNetApplet.access$000(JNetApplet.java:40)
 at com.sap.jnet.JNetApplet$1.run(JNetApplet.java:265)
 at java.awt.event.InvocationEvent.dispatch(Unknown Source)
 at java.awt.EventQueue.dispatchEvent(Unknown Source)
 at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.run(Unknown Source)

SET_PAYLOAD_FAILED error in SOAP to Proxy scenario

Hi PI Experts,
We have an inbound syncronus interface (Non sap system to SAP) using the SOAP to Proxy scenario.
When we test the interface using any soap tool like soapui it is working fine but when the interface is triggered end to end from source system then the below error is getting dispalyed on source system.
500 Internal Server Error
In XI below is the error message -
<?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>XIProxy</SAP:Category>
<SAP:Code area="ABAP">SET_PAYLOAD_FAILED</SAP:Code>
<SAP:P1>IN</SAP:P1>
<SAP:P2>REQUEST</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Internal error when completing the message object (setting the payload, direction: IN message: REQUEST)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any please let me know what is the issue here?
Appreciate your help.
Regards,
Jitender

We had a similar issue with a Synchronous Interface
The interface worked perfectly when sending the request directly to the integration server, but when sending it using SOAP the issue appeared.
It was very tricky to solve it because we had similar interfaces that worked without any issues.
SOLUTION: Create a new Service interface with a new name different from the one failing. And make sure The Message Types are in the same namespace as the service interface.
Why?:
The issue turned out to be in the sender agreement, and name-spacing issues.
Our Outbound Service Interface belonged to one SWCV and ns, We will call it "ns1:SI_A_OUT".
In PI 7.3, and I believe 7.11 also, the you no longer assign a default interface in the to the SOAP communication channel sender agreement pair.
Therefore the SOAP adapter determines the soap method from the payload. If The internal message type in the soap message belong to different namespace, the the java method getMessage() does not find the correct XML node, therefore does not find the payload.
<"ns1:SI_A_OUT">
...<ns2:MT_element>
getMessage( ns1:MT_element)
We are not sure if the issue is the implementation of the SOAP protocol or in the WSDL generation. But this issues seem to create orphan object during runtime, and even if you re-implement the complete interface, the sender agreement seems to be corrupt.
Therefore the only was we could solve this, was to move our MT to the same namespace as the service interface and rename the interface "ns1:SI_A2_OUT"
Hope this helps someone.
Juan Francisco Zurita Duque
NNIT A/S

Public URL for Synchronous SOAP to RFC scenario

Hello Everyone,
I have synchronous SOAP to RFC scenario.
i have created the http URL for testing environment through sender agreement.
However, now the user wants a public URL and that too secured one ... means ( https ) in production.
i tried this blog, but Service registry is not configured in our landscape.
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/23725
is there any other way ..?
Regards,
Ravi

The process of creating the wsdl will remain same. The url in your case will start with HTTPS instead of HTTP. Note that the port at which HTTPS data would be received will be different than HTTP port and thererfore you need to change that as well. You don't have to set any client authentication unless there is a business requirement. You may simply use certificates for SSL.
In some cases, if PI always receives data through web-dipatcher (ask your network team), then the data hostname and port of web-dispatcher should be used.
Regards,
Prateek Raj Srivastava

NO_RECEIVER_CASE_BE error in a SOAP - XI - RFC scenario

Hi gurus:
I'm configuring a SOAP -> XI -> RFC scenario and I'm getting a "NO_RECEIVER_CASE_BE" error when I send a test message using the SOAP adapter.
I have another interfaces using the SOAP adapter of the same XI server and no problems with it. So I think my problem is not into the SOAP adapter.
Thanks to all in advance,
Alejandro Gomez.
Edited by: Alejandro Gómez on May 27, 2008 10:24 AM

Hi:
The entire XML result from MONI is next:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <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>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:TimeSent>2008-05-27T09:10:24Z</SAP:TimeSent><SAP:Sender><SAP:Service>Openlab_Desarrollo</SAP:Service><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</SAP:Interface></SAP:Sender><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</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><SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="AE">af.xi2.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info/></SAP:Hop><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="IS">is.00.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info>3.0</SAP:Info></SAP:Hop></SAP:HopList><SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SAP:Date>20080527</SAP:Date><SAP:Time>101024</SAP:Time><SAP:Host>xidserver</SAP:Host><SAP:SystemId>XI2</SAP:SystemId><SAP:SystemNr>00</SAP:SystemNr><SAP:OS>Windows NT</SAP:OS><SAP:DB>ORACLE</SAP:DB><SAP:Language/><SAP:ProcStatus>023</SAP:ProcStatus><SAP:AdapterStatus>000</SAP:AdapterStatus><SAP:User>XIAFUSER</SAP:User><SAP:TraceLevel>3</SAP:TraceLevel><SAP:Logging>1</SAP:Logging><SAP:LogSeqNbr>001</SAP:LogSeqNbr><SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr><SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal><SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal><SAP:PipelineElementId>5BC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId><SAP:PipelineService>PLSRV_RECEIVER_DETERMINATION</SAP:PipelineService><SAP:QIdInternal/><SAP:CommitActor>X</SAP:CommitActor><SAP:SplitNumber>0</SAP:SplitNumber><SAP:NumberOfRetries>0</SAP:NumberOfRetries><SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries><SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine><SAP:PlsrvExceptionCode/><SAP:EOReferenceRuntime type="TID"/><SAP:EOReferenceInbound type="TID"/><SAP:EOReferenceOutbound type="TID"/><SAP:MessageSizePayload>508</SAP:MessageSizePayload><SAP:MessageSizeTotal>2985</SAP:MessageSizeTotal><SAP:PayloadSizeRequest>508</SAP:PayloadSizeRequest><SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap><SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse><SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap><SAP:Reorganization>INI</SAP:Reorganization><SAP:AdapterInbound>AENGINE</SAP:AdapterInbound><SAP:InterfaceAction>INIT</SAP:InterfaceAction><SAP:RandomNumber>00</SAP:RandomNumber><SAP:AckStatus>000</SAP:AckStatus><SAP:SkipReceiverDetermination/></SAP:RunTime><SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30"><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.616</SAP:Timestamp></SAP:RunTimeItem></SAP:PerformanceHeader><SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:TraceLevel>Fatal</SAP:TraceLevel><SAP:Logging>Off</SAP:Logging></SAP:Diagnostic><SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = xidserver:8000</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.137.73.104</Trace>
<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace>
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB... </Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found </Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK. </Trace>
</Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">XMB entry processing </Trace>
<Trace level="3" type="T">system-ID = XI2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = S</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace>
<Trace level="1" type="T">Message-GUID = BD9B57A12BCC11DDC738001B7899027A</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace>
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline attributes </Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline elements </Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="2" type="T">Persisting original message </Trace>
<Trace level="3" type="T">Message-Version = 000</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION"></Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG = </Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">Start without given receiver </Trace>
<Trace level="1" type="T">No Relation found - accept given Receivers. </Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0 </Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="3" type="T">Persisting message Status = 023</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace></SOAP:Header><SOAP:Body><SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:payload-bd9b57a22bcc11dd95bc001b7899027a#sap.com"><SAP:Name>MainDocument</SAP:Name><SAP:Description>Main XML document</SAP:Description><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest></SOAP:Body></SOAP:Envelope>
Thanks,
Alejandro Gomez.

File to Web service (SOAP) to File scenario with out BPM in PI 7.1

Hi All,
I have scenario File to Web service (SOAP) to File scenario with out BPM.i am getting the below error:
1) Error MP: unexpected exception caught com.sap.aii.af.service.cpa.impl.exception.CPAObjectKeyException: Value of key must not be null: ObjectId
2) Error ROB: error during processing: com.sap.aii.af.lib.mp.processor.ModuleProcessorException: Processing Error
PI server is 7.1 with SP:8
I have configured the scenario like this
1) 2 File channels - Sender & Receiver ,1 RFC channel - Receiver. We need to note that, the additional Module parameters need to be added only for sender File channel
2) Created Sender Agreement
3)Created Receiver Determination
4)Created Interface Determination
5)Created Receiver Agreement
Regards,
Ramesh

Hi,
Thanks for your reply!!
My Scenario is File to SOAP to File.
Configred modules in Sender channal below:
Prcessing sequence:
Number       Module Name                                        Module Key
1..........       AF_Modules/RequestResponseBean.......1
2..........       CallSapAdapter..........................................2
3..........       AF_Modules/ResponseOnewayBean.......3
Module Configuration:
Module Key                                       Parameter Name                                       ParameterValue
1                                                        passThrough                                            true
3                                                        receiverChannel                                       receiverChannel name
3                                                        receiverService                                        receiverService name
please tell any more confiration requered.
Regards,
Ramesh

SOAP TO JDBC scenario: calling stored procedure which will return the value

Hi
I have Soap To Jdbc scenario in which I am going to call the Stored Procedure at target side which will be executed and it is going to return the result set .
Result contains following values.
return code as ( 0 Or 1) and also specific exception message if its return code as 1.
Could you suggest me the way by which I can handled this return code and send it back to the Sap PI system then the same thing is directed the to SMTP server for sending mail to consern person.
Regards
Kumar

The OUT parameters of stored procedure will be returned as response. Where exactly are you facing the proble? Here is a complete walkthourgh
/people/luis.melgar/blog/2008/05/13/synchronous-soap-to-jdbc--end-to-end-walkthrough
In your case, you don't want response at sender. Instead you want to mail it. For this you may use BPM to design your scenario with following steps
Receive (to receive data from sender)
Send Sync (to stored procedure and get response)
Send Async (to mail receiver)
Regards,
Prateek

Error in SOAP to file scenario

Hey guys
i m doing a SOAP to File scenario and getting the following error.
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
any idea where should i look ?
thanx
ahmad

Hey
i m still getting a red flag in MONI,the error is
<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
i checked my mapping by copyin payload from MONI,its working fine.
thanx
ahmad

SOAP to SOAP scenario testing

Similar Messages

Maybe you are looking for