SOAP to SOAP (ECC) Synchronous Scenario

Hi,
I am configuring SOAP to SOAP scenario. Source systems is take an SOAP UI and Destination system as SAP ECC system. I configured as follows in PI 7.11
1. Created Two Data type for Source System( one for Request and Second one is for Response)
2. Imported WSDL which was created in ECC.
3. Two Service Interface( Both are Synchronous)
4. Two Message Mappings( Source Message Type to SOAP Request & SOAP Responce to Sencer system Response message)
5. Operatino Mapping ( Request and Response)
ID
6. Once Business Component for both Sender and Receiver
7. Two SOAP Communicatino Channels ( Target Channel i given Target url and authentication Details)
8. Receiver Determination
9. Interface Determination
10. Sender Agreement
11. Recever Agreement
I am executing the scenarion now i am getting the "http 404 not found error".
My doubt is do we need to do any Configuratin in ECC System? I did not do any configuration in ECC System. If i am accessing that WSDL through IE then i am getting response back. Please lte me know the solution.
Regards,
Dev

Hi Deevan,
Check if the Target URL that you have mentioned is correct.
The target URL should be like this,
http://server:port/sap/xi/adapter_plain?namespace=<xxx>&interface=<xxx>&service=<xxx>&sap-user=<xxx>&sap-password=<xxx>&sap-client=<xxx>&sap-language=<xx> .
Copy ur target url on to the browser and check what happens??
Regards
Deepthi Premnath

Similar Messages

SOAP - XI- PROXY synchronous scenario

Hi Experts,
I have a
SOAP -
XI -
PROXY Synchronous Scenario
I have done the following things ESR and ID
ESR:
1. Created DT and respective MT for Request and Response.
2. Created Service Interfaces with Synchronous mode with respective MT's.
3. Created Two separate MM with respective Request and Response MT's.
4. Created Operation Mapping and call both Request and Response Mappings in it.
Integration Directory (ID):
1. Configured considering Sender SOAP and Receiver ECC Services.
2. Configured CC with required parameters in Sender SOAP CC and Receiver XI CC.
3. Generate wsdl from Sender agreement and save it as a local file.
I am getting error in receiver agreement. Do I need to specify any Module parameters in Module TAB for Sender CC or Receiver CC to synchronous scenario.
Please hep me out.
Thanks

Hi Ram,
I am getting error in receiver agreement. Do I need to specify any Module parameters in Module TAB for Sender CC or Receiver CC to synchronous scenario.
It looks like you did not create a receiver agreement, or if you did, it did not match the interface that is given or configured in Interface Determination. Can you recheck your configuration?
Regards,
Mark

Synchronous Scenario SOAP to Proxy and Proxy to SOAP

Hi Sdn,
I am new to Synchronous Scenario.
Third party will send SOAP message requesting some information from SAP.
SOAP - > PI -> Proxy SAP
they are expecting a response Proxy - > PI -> SOAP.
Could you please let me know how to design teh Synchronous Scenario in PI .
Thanks

> Create DT and respective MT for Request and Response.
> Create Service Interfaces with Synchronous mode with respective MT's.
> Create Two separate MM with respective Request and Response MT's.
> Create Operation Mapping and call both Request and Response Mappings in it.
> Complete the Configuration part considering Sender SOAP and Receiver ECC Services.
> Configure CC with required parameters in Sender SOAP CC and Receiver XI CC.
> Generate wsdl from Sender agreement and save it as a local file.
> Use SOAP UI or any available Tool for testing purpose. Import the generated wsdl, provide input data and execute the test.
> If you are comfortable with expected result, deliver wsdl to the Sender Party.
> For Inbound Proxy, you can refer initial replies.
Hope it helps.!
Regards,
Sunil

FILE to SOAP synchronous scenario - config of SOAP channel

Hi All,
I have a scenario where I want PI to pull some files from 3rd party application.
Adapters to be used: SOAP receiver, FILE adapters.
I am aware of the use of Request/Response beans in File sender channel and the File receiver channel to dump the received files in a particular location.
I need help with the configuration of the SOAP channel.
The files to be pulled will be Encrypted.
Summary:
File sender(RequestResponse & ResponseOneWay Beans) , File receiver( to receive the files), SOAP receiver.
Need help with the config of SOAP.
Kindly let me know your views.
Thanks,
Pratibha.

Hi,
Let me put it in detail steps:
In forward flow we will be sending an IDoc. It will be processed and later an Acknowledgement file will be generated.
Now, we want to PULL this Ack file. If the other party had to push the Ack file, the scenario would have been simple.
But, we want to poll for this file and then pull it.
So, we would have something like this:
1. FILE SENDER sends a sample file.
2. We will be applying the beans in file sender to make it a synchronous scenario. So, the Ack file will be received at the location mentioned in the corresponding FILE RECEIVER adapter.
3. We have a SOAP RECEIVER which should send the ACK file in response.
I have configured the same scenario where the RECEIVER was HTTP adapter. The 3rd party had provided us the URL and ENT-APRF value. When I used to send the sample file via FILE SENDER to this HTTP receiver, I was able to retrieve the ACK file via the FILE RECEIVER.
Now, I wish to configure the same using RECEIVER SOAP adapter.
I need to know about the config at SOAP end i.e. how and where the ACK file will be available at the SOAP end for the FILE sender to pull the file.
Ack files will be encrypted..
Any views/suggestions will be of great help.
Thanks,
Pratibha.

SOAP to RFC scenario (SFDC - ECC synch)

Working on a SFDC to ECC synch scenario using SOAP to RFC interface. I generated the WSDL for SFDC team and tested on soapUI, I am able to see the successful request/response structure in sxmb_moni.
However, when the SFDC team is sending the request in real time from SFDC, the request is successful in SFDC but not reaching PI and hence there is no response. The error I see in sxmb_moni for this is
<SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">PROXY_NOT_ALLOWED_ON_IS</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Proxy calls are not permitted on sender or receiver side on the IS (client)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Are there any additional setting need to be done.
Please guide on this issue . Thanks
Edited by: jbagga on Nov 14, 2011 7:42 AM

SFDC sending request to PI. SFDC Request is not hitting PI, neither traceable in MONI or RWB.
SFDC request is not hitting PI . The ForeFront has allowed the SFDC IP range to target PI using reverse proxy rules. But SFDC and Forefront both get the "HTTP 500 internal server error"
The question is , I am helpless until the request is monitored anywhere in MONI or RWB_communication channel
Also SFDC receives some fault message error along with HTTP 500 i.e. Header Missing in Soap Message Header. In this case, also if its PI related error there should be at least some track of request hitting PI in MONI or RWB. also tried creating a WSDL with PI username and password in the WSDL under Header tags, still the same situation
ALL Ports are open by BASIS team.
Can someone point out any helpful solution. URGENT !! Thanks a ton in advance.
EVERYTHING , THE ENTIRE REQUEST/RESPONSE STRUCTURE WORKS PERFECT WITH SOAPUI.

Help SOAP to RFC Scenario using BPM (Synchronous communication)

Hi,
I am doing a scenario from SOAP to RFC scenario(Synchronous communication). Here I am creating a PM Notification in the SAP system through a webservice.
I am using three BAPI'S here,
1. BAPI_ALM_NOTIF_CREATE
2. BAPI_ALM_NOTIF_SAVE
3. BAPI_TRANSACTION_COMMIT
I am successful in calling the first BAPI from the Web Service. For this I have not used BPM. But to commit the transaction(PM notification in this case), I have to execute the other two BAPI's as well. I have to pass the output of first BAPI to the second BAPI and then execute the 2nd BAPI. And finally have to execute the 3rd BAPI. FYI, 3rd BAPI is not dependent on any output. It has to be executed independently after execution of the first two BAPI's.
How can I execute this scenario? Do I have to use BPM? If yes please let me know the steps in detail. I have not done any BPM scenario till now. So please answer me in detail.
Thanks in Advance,
Vijay
p.s. reward points are must

Hi Vijay,
Yes, You will indeed need a BPM in this case...
Based on my understanding of the Scenario u have explained, here are the steps that would be needed.
1. Receive With the Sync-Async Bridge open.
2. Transformation Step (Between the source Request and The BAPI_ALM_NOTIF_CREATE Request)
3. Send Synchronous
4. Fork
5. In one Branch of the fork - Transformation (Between the BAPI_ALM_NOTIF_CREATE Response and API_ALM_NOTIF_SAVE Request)
6. In the other branch of the fork - Transformation (Between a Dummy Source and the BAPI_TRANSACTION_COMMIT Request)
7. Send Synchronous (to make the 2nd BAPI Call)
6. Transformation ( BAPI_ALM_NOTIF_SAVE Response and the source Response)
7. Send Asynchronous (to make the 3rd BAPI call)
8. Send the Source Response and close the Sync-Async Bridge.
There might be alternative ways also of doing it...
Also a better design would be to take care of the 2nd and the 3rd BAPI call within the code of the 1st RFC Function Module.
Regards,
Abhy Thomas

SOAP to Proxy synchronous scenario

Hi,
Hope you are all doing well.
I have a SOAP to Proxy synchronous scenario. As part of this scenario, the data structure of the response sent by SAP is different from the response sent back to the SOAP requester. Hence I have used request message mapping between the SOAP request sent by requester and the one passed on to SAP and response message mapping between the response sent by SAP and the one passed on to the requester. Both the message mappings are incorporated in a single Interface mapping.
The problem is that the interface is behaving like a asynchronous one, i.e., request is passing over to SAP but though the proxy is giving a response back, the same is not coming over to XI.
It would be really helpful if you can let me know what might have gone wrong.
regards
Debansu

Hi,
you should have that:
1. Two Message Mapping:
1.1. a Message Mapping for request    (called MM_request)    , from MT_SOAP_request     to   MT_Proxy_request.
1.2. a Message Mapping for response (called MM_response) , from MT_Proxy_response   to   MT_SOAP_response.
2. One Operation Mapping (in PI 7.1) or Interface Mapping (in PI 7.0) from SI_SOAP to SI_ Proxy with:
2.1 in the tab "request", so from MT_SOAP_request     to   MT_Proxy_request    , give your Message Mapping "MM_request".
2.2 in tab "response"   , so from MT_Proxy_response   to   MT_SOAP_response, give your Message Mapping "MM_response".
3. In you Directory, you define a flow like that:
from SI_SOAP to SI_ Proxy by using your Operation Mapping.
If I missed nothing, that's all.
MT = Message Type
MM = Message Mapping
SI =Service Interface in PI 7.1 or Message Interface in PI 7.0.
regards.
Mickael
Edited by: Mickael Huchet on Oct 19, 2011 4:07 PM

IDoc to soap synchronous scenario with BPM

Hi,
I am working on IDoc to soap synchronous scenario using BPM. Here i am facing lot of soap exceptions in my production system. I handled the exceptions. The data getting excuted for the first time, the same data(just changed the description)is giving exceptions for the second time. Please let me know why the exceptions are getting, and different type of exceptions and solutions for the same.(Blog also is fine)
Thanks & Regards,
Pragathi.

The data getting excuted for the first time, the same data(just changed the description)is giving exceptions for the second
time.
Ideally you should not get an exception for the same data....can you tell is the description and where are you getting the exception...is it a part of the SOAP message or some object?
An exception might have occured because the description would be something unacceptable by the target application.
and different type of exceptions and solutions for the same
there would be many blogs....your thread would be spammed...better make a search on SDN with exception text that you are getting.
Regards,
Abhishek.

IDOC to SOAP synchronous scenario

Hi All,
We have an IDOC to SOAP synchronous scenario in which IDOCs are sent to SOAP by calling a service and then SOAP sends a response back to XI . The response is not sent to SAP- R3. Please suggest on this
Thanks

Hello Rajesh,
Thanks for your good justification.
Here I have also replicated same kind of scenario and having same kind of issue.
One thing just wanted to confirm - Even though SOAP adapter expects HTTP 200 response back from webservice, still SOAP channel is getting into red with following , and as we have Alert configured ...Alert mail also receiving as part of Error only. So How can we avoid that response ? Is there have any parameter to handle or suppress the response back?
Thanks!
Goutam

ERROR During call of SOAP with a SOAP- RFC- SOAP Synchronous scenario

Hello Experts,
I've recently created a SOAP->RFC->SOAP synchronous scenario but every time I'm invoking the SOAP via XMLSpy then i will hang and send a timeout error. Also a log in XI was generated as shown below.
I hope you could help me on this one.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          28.09.2010 09:31:23
Short text
     SQL error in the database when accessing a table.
What happened?
     The database system detected a deadlock and avoided it by rolling back
     your transaction.
What can you do?
     If possible (and necessary), repeat the last database transaction in the
      hope that locking the object will not result in another deadlock.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
      in
     procedure "DELETE_LUW_PACKET" "(FORM)", nor was it propagated by a RAISING
      clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     The database system recognized that your last operation on the database
     would have led to a deadlock.
     Therefore, your transaction was rolled back
     to avoid this.
     ORACLE always terminates any transaction that would result in deadlock.
     The other transactions involved in this potential deadlock
     are not affected by the termination.
Regards,
Alfred

Normally such an error comes when the DB of SAP PI is full.
Contact your BASIS or ADMIN team and ask them to free the DB space.
Regards,
Abhishek.

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

Principal Propagation SOAP - XI - RFC Scenario

Hi,
I am developing a synchronous scenario whereby a SOAP request posted by a non SAP system should be forwarded to an ECC system using RFC. Challenge I am facing is that I want to use the user, which was used for basic user authentification to post to XI, dynamically in the RFC call. I have been reading about Principal Propagation using assertion tickets, however only SOAP receiver adapter is spoken about. I am trying to configure this using SOAP Sender adapter.
As far as my understanding goes the sending system should be able to create these assertion tickets ?
Has anyone developed a similar interface ?
Scenario is: Non SAP SOAP Sending system = Client, Adapter engine = Server & Client, Integration Server = Server & client and Receiving ABAP system (ECC6.0) is Server.
Any help would be appreciated and awarded if helpfull.
Kind Regards, Jelmer Keuken
Ps. XI is version 7.0 SP18, Alreay read the Blogs of Alexander Bundschuh
Edited by: J. Keuken on Sep 9, 2009 4:04 PM

Hi,
This scenario is definately possible to implement with principal propagation.
1. Enable the PP on Integration server
2. Here you need not have to do anything on SOAP sender side to create the assertion ticket..
The assertion ticket is required on SAP side which will act as Web AS ABAP Server.
refer the settings --http://help.sap.com/saphelp_nw04/helpdata/en/61/42897de269cf44b35f9395978cc9cb/frameset.htm
3. And then follow further steps as it mentioned the blogs...
Thanks
Swarup

SOAP with IDOC scenario

Hi Experts,
Could you help me with the following scenario using XI:
The sender is a webservice client which sends a SOAP request with the order number (over HTTPS). The order number needs to be pased to SAP ECC to return the order details as a SOAP response synchronously. The order details are actually stored in very complex custom idocs in SAP ECC.
Plz let me know how to configure this scenario.
Thanks,
Shobhit

Steps in BPM:
1) Receive Step: (Receive New Order from WebServer)
Message: sales_order1 (Give the appropriate message type)
Start Process: Click on the check box
Mode: Asynchronous
Activate correlation:
Order_number:
2) Send Step: (Send order to SAP R/3)
Mode: Asynchronous
Create New transaction: Do not Click on the check box
Message: sales_order1 (Give the appropriate message type)
Acknowledgement: none
received from : Send Contect
3) Receive Step: (receive purchase Order from R/3)
Message: Purchase_order1
use correlations: Order_number
4) Send Step: (Send order response to WebService)
Mode: Asynchronous
Create New transaction: Do not Click on the check box
Message: Purchase_order1 (Give the appropriate message type)
Acknowledgement: none
received from : Send Contect
These are basic steps, depends on your requirement(Error Handling or response time limitations) the design may change.
The ID Configuration is same...
Receiver determination:
1) Service_is_Sender_WS - Sender_Interface_Sales_Ord (Party is optional)
2) Service_is_IP - Interface_is_request_abs
3) Service_is_IP - Interface_is_response_abs
4) Service_is_SAP - Interface_is_IDoc_PURCH_Ord
Same as Interface determination....

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

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)

SOAP to SOAP (ECC) Synchronous Scenario

Similar Messages

Maybe you are looking for