SOAP to SOAP

Hi experts...
Need some help in implementing SOAP to SOAP test interface... read some document on SOAP client, dint really get anything from that.
I would appreciate if anyone could guide me in this.
What to put in SOAP client and what steps i need to follow...
Pranav

Hi,
This might help you to get more picture on SOAP
Check these
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Regards
Agasthuri Doss

Similar Messages

I am trying SOAP to SOAP scenario an i am getting the following error

HTTP operation 'POST' could not be performed on URL
'/XISOAPAdapter/MessageServlet?channel=:BS:CC'due to an error :The connection with the server was terminated abnormally.
Can some one help me out , really urgent

Hi,
You could give more data.
I assume that you have SOAP<>XI<>SOAP and the problem its in the communication SOAP-->XI
Can you give us the exception that you obtain in SXB_MONI?
The error can be the error signed by Matias or another internal error in the service.
Regards.

** SOAP to SOAP call - HTTP 404 not found - invalid content type

Hi friends,
We have one scenario SOAP to SOAP call. It is synchronous interface. We are calling the WSDL.
For some of the messages (not all), we are getting the error in SXMB_MONI
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found
In the sender & receiver SOAP communication channel also, same error : SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found
Friends, this error is not coming for all messages. For some of the messages it is coming. For example,
10:50 - Message Processed Successfully
10:54 - Message Processed Successfully
10:59 - Error
11:05 - Message Processed Successfully
By looking threads and blogs, I implemented MessagesTransformBean in the receiver CC and added the parameter Transform.ContentType as 'text/xml;charset=utf-8'.
After implementing this also, error is coming for some of the messages.
Can you kindly clarify friends, what could be the problem?
Kind regards,
Jegathees P.

I'm in agreement with Stefan...
If the problem is intermittent then the system is overloaded at certain times. You would probably need to do some JVM analysis to see the resource usage & look at increasing the memory.
Regards, Trevor

SOAP - XI - SOAP Error

Hi,
I am working on a scenario where a SOAP Client ( XMLSPY) sends a request to XI and XI forwards it to a web service and returns the result back to Soap Client. I am using SOAP Adapter at outbound and inbound.
I have done the following steps:
1. imported the WSDL for the web service.
2. created MI based on the WSDL.
3. Configured the agreements and determinations.
4. Generated WSDL based on the configuration objects in ID.
5. Called my WSDL in XMLSPY client.
6. I am asked to login to the XI system.
7. I get an error message back in XMLSPY:
<?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>DeliveryException</code>
                         <text><![CDATA[
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: QName is 'xmlns', but URI is not 'http://www.w3.org/2000/xmlns/' in the qualified name, 'xmlns'
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:457)
     at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:125)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:512)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:141)
          ]]></text>
                    </s:SystemError>
               </detail>
          </SOAP:Fault>
     </SOAP:Body>
</SOAP:Envelope>
The message monitoring shows:
2006-04-03 11:37:37 Success SOAP: request message entering the adapter
2006-04-03 11:37:40 Success The message was successfully received by the messaging system. Profile: XI URL: http://diamond:50500/MessagingSystem/receive/AFW/XI
2006-04-03 11:37:40 Success Using connection AFW. Trying to put the message into the request queue.
2006-04-03 11:37:40 Success Message successfully put into the queue.
2006-04-03 11:37:40 Success The message was successfully retrieved from the request queue.
2006-04-03 11:37:40 Success The message status set to DLNG.
2006-04-03 11:37:40 Success Delivering to channel: SOAP_RECEIVER_ADAPTER
2006-04-03 11:37:40 Success SOAP: request message entering the adapter
2006-04-03 11:37:42 Error SOAP: error occured: org.w3c.dom.DOMException: QName is 'xmlns', but URI is not 'http://www.w3.org/2000/xmlns/' in the qualified name, 'xmlns'
2006-04-03 11:37:42 Error Exception caught by adapter framework: QName is 'xmlns', but URI is not 'http://www.w3.org/2000/xmlns/' in the qualified name, 'xmlns'
and it also shows:
Time Stamp Status Description
2006-04-03 11:37:37 Success SOAP: request message entering the adapter
2006-04-03 11:37:40 Success The message was successfully received by the messaging system. Profile: XI URL: http://diamond:50500/MessagingSystem/receive/AFW/XI
2006-04-03 11:37:40 Success Using connection AFW. Trying to put the message into the request queue.
2006-04-03 11:37:40 Success Message successfully put into the queue.
2006-04-03 11:37:40 Success The message was successfully retrieved from the request queue.
2006-04-03 11:37:40 Success The message status set to DLNG.
2006-04-03 11:37:40 Success Delivering to channel: SOAP_RECEIVER_ADAPTER
2006-04-03 11:37:40 Success SOAP: request message entering the adapter
2006-04-03 11:37:42 Error SOAP: error occured: org.w3c.dom.DOMException: QName is 'xmlns', but URI is not 'http://www.w3.org/2000/xmlns/' in the qualified name, 'xmlns'
2006-04-03 11:37:42 Error Exception caught by adapter framework: QName is 'xmlns', but URI is not 'http://www.w3.org/2000/xmlns/' in the qualified name, 'xmlns'
The message I am sending to the XI is :
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Body>
          <m:VerifyAddress xmlns:m="http://www.webservicex.net">
               <m:City>Plano</m:City>
               <m:State>TX</m:State>
               <m:Zip>75024</m:Zip>
          </m:VerifyAddress>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
There is some URI conflict in both the adapters. They expect some URI format which it is not getting. I dont understand where the problem is.
Can anyone help?
Thanks,
Shubha.

Hi,
I think namespace in the URL is conflicting somewhere.
Just check with this blog-
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Hope this helps,
Regards,
Moorthy

Response from PI in SOAP to SOAP Scenario

Hi,
My scenario is Soap to SOAP sending purchase orders. they want acknowledgement from PI whether PI received the message or not in the form of SOAP response.
sender system not expecting the response after the message processing in receiver system, they are expecting the response when PI receives message from them.
As any way they receive HTTP200 OK acknowledgement is it necessary that to send the SOAP response from PI by developing BPM?
Is it a good way of doing it?
Is any other way of doing it?
Your suggestions will be helpful to me.
Thank you.
Santhi.

Hi Santhi,
Please refer to SAP Note 856597 - SOAP Adapter FAQ Question number 2
2. Sender Asynchronous Calls
o Q: What are the correct sender options for asynchronous calls?
When the client sends a SOAP message and checks if the response is
an HTTP 200 response message with an empty soap envelope or an HTTP
202 response message with no content, the quality of service with
AtLeastOnce can be realized. In this case, the client must resend
the message until such a successful response is returned. When the
message successfully accepted by the adapter, an HTTP 200 response
with an empty SOAP envelope or an HTTP 202 response message with no
content is returned.
You don't have to do anything. When an async message is sent, PI will either reply with a 200 with an empty SOAP Envelope or an HTTP 202 with no content . That will serve as your acknowledgement.
Regards,
Mark

SOAP to SOAP BPM scenario

Hi Experts,
Could you please tell me, how to do SOAP to SOAP scenario using BPM?
SOAP -> XI -> BPM ( Inside BPM two more SOAP Adapter call) -> SOAP.
1. Pass the request thro' SOAP to BPM
2. Call first SOAP Adpter.
3. Response of the first SOAP will be the input for the next SOAP adapter
4. Call second SOAP adapter.
5. Return the SOAP response
Regards
Sara
Message was edited by:
        Sara D

Message Interface
1. MI_SEND_SOAP_OUT           - (Out,Asyn : MT_BPM_SOAPRequest)
2. MI_SEND_SOAP_IN          - (In, Asyn : MT_BPM_SOAPResponse)
3. MI_BPM_Req_ABS_OUT          - (Abs,Asyn : MT_BPM_Receiver_SOAPRequest)
4. MI_BPM_Req_ABS_IN          - (Abs,Asyn : MT_BPM_Receiver_SOAPResponse)
5. MI_WS1_Service_ABS          - (Abs, Synch : OutMessage : MT_BPM_WS1_Request InMessage:MT_BPM_WS1_Response)
6. MI_WS2_Service_ABS          - (Abs, Synch : OutMessage : MT_BPM_WS2_Request InMessage:MT_BPM_WS2_Response)
Message Mapping
1. MM_BPM_SOAPRequest_To_BPM_RecSOAPRequest ( Source: MT_BPM_SOAPRequest Target :MT_BPM_Receiver_SOAPRequest)
2. MM_BPM_RecSOAPRequest_To_BPM_WS1Request ( Source: MT_BPM_Receiver_SOAPRequest Target :MT_BPM_WS1_Request)
3. MM_BPM_WS1Response_To_BPM_WS2Request     ( Source: MT_BPM_WS1_Response Target :MT_BPM_WS2_Request)
4. MM_BPM_WS2Response_To_BPM_RecSOAPResponse( Source: MT_BPM_WS2_Response Target :MT_BPM_Receiver_SOAPResponse)
5. MM_BPM_RecSOAPResponse_To_BPM_SOAPResponse( Source: MT_BPM_Receiver_SOAPRespons Target :MT_BPM_SOAPResponse)
Could you please tell me, whether the above objects are correct for this scenario?
Regards
Sara
Regards
Sara
Message was edited by:
        Sara D
Message was edited by:
        Sara D

File to SOAP and SOAP to File (Synchronous)

Hi,
Can anybody advice me how to do the File to SOAP and SOAP to File with Synchronous call.
Thanks,
Naidu.

Hi,
Use this blog
RFC -> XI -> WebService - A Complete Walkthrough (Part 1)
and create an inbound synchronous interface for soap receiver structure. provide request and response structure in it.
Thanks!

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.

SOAP Runtime: SOAP Runtime exception: 1023 occurred in method IF_SOAP_TRANS

Hi ,
we currently have the SAP discovery system setup, i have notice that when i check the system log via sm21 , i recieve hundreds of the following error messages:
SOAP Runtime: SOAP Runtime exception: 1023 occurred in method IF_SOAP_TRANSPORT_BINDING~receive of class CL_SOAP11_HTTP_TPBND at position 1
SOAP Runtime: Exception message: SRT: Processing error in Internet Communication Framework: ("ICF Error when receivin g the response: ICM_HTTP_CONNECTION_FAILED")
Please advise where to check on resolving this error as some services donot work because of this,All services start up fine , i have also checked /nsicf and some RFC ,but have not found any thing specific.
Kind Regards
A.

Hi,
I know this question was asked a long time ago but you should check out the following note and fix to un-release the "osp" background jobs running under SM37.
Note 1113842 - Discovery System V3 Central Note

Access to SOAP Header/SOAP Envelope in OSB

We have a need where we need to copy the SOAP header request to SOAP header response. Is there a way to access SOAP Header/SOAP Env in OSB ?
Thanks,
Pavan
Edited by: user10413378 on Mar 6, 2010 7:14 AM

There is $header variable with headers:
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageflow.html#wp1093911
You can pass all headers through using "Get All Headers" option in Proxy settings and Transport Headers - Pass all Headers in your flow:
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageflow.html#wp1125345

Apache Axis Soap Envelope soap:Header

<?xml version="1.0" encoding="utf-8"?>
<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/">
<soap:Header>
<DataHeader xmlns="http://mySite/">
<HeaderUsername>string</HeaderUsername>
<HeaderPassword>string</HeaderPassword>
</DataExportHeader>
</soap:Header>
<soap:Body>
<ReturnDataList xmlns="http://mySite/">
<functionName>getAll</functionName>
</ReturnDataList>
</soap:Body>
</soap:Envelope>
I am using Apache Axis, how can i embed DataHeader{HeaderUsername, HeaderPassword} in my request? Thanks,

I can generate the code from .wsdl by using JAP+RPC, but there is not Header class in the code. Any help?

SOAP to SOAP scenario - XIServer:UNAUTHORIZED

Hello,
I created a scenario synchronous SOAP<>PI<>SOAP, but when I consume the WS (using soapui) this show me the next error:

<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>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:UNAUTHORIZED:
     at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:663)
     at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:447)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
     at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:428)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
     at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:462)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:270)
     at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
I get the url from directory (sender component):
http://server:port/XISOAPAdapter/MessageServlet?senderParty=&senderService=BS_DEMOWS_100&receiverParty=&receiverService=&interface=SI_SendSMS&interfaceNamespace=http://namespace.com/WS/SendSMS
Into de SXI_MONITOR I can see errror:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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">UNAUTHORIZED</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Authorization error while sending by HTTP (error code: 401 , error text: Unauthorized)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
And in the /MessagingSystem/monitor the log is:
2011-11-16 11:42:46.56 Success SOAP: request message entering the adapter processing with user XSICONSULTOR
2011-11-16 11:42:46.561 Success Application attempting to send an XI message synchronously using connection SOAP_http://sap.com/xi/XI/System
2011-11-16 11:42:46.562 Success Trying to put the message into call queue
2011-11-16 11:42:46.563 Success Message successfully put into the queue
2011-11-16 11:42:46.564 Success Message retrieved from call queue
2011-11-16 11:42:46.564 Success Message status set to DLNG
2011-11-16 11:42:47.101 Error Received XI System Error. ErrorCode: UNAUTHORIZED ErrorText: null ErrorStack: Authorization error while sending by HTTP (error code: 401 , error text: Unauthorized)
2011-11-16 11:42:47.101 Error Transmitting the message using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:UNAUTHORIZED:
2011-11-16 11:42:47.102 Error Message status set to FAIL
2011-11-16 11:42:47.102 Error Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:UNAUTHORIZED:
2011-11-16 11:42:47.103 Error SOAP: call failed: com.sap.aii.af.lib.mp.module.ModuleException: senderChannel 2e4c634fdd973c1c9c0323846834136d: Catching exception calling messaging system
2011-11-16 11:42:47.103 Error SOAP: call failed com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:UNAUTHORIZED:
The XSICONSULTOR user has the next roles:
SAP_ALM_ADMINISTRATOR
SAP_ALM_CUSTOMIZER
SAP_SLD_ADMINISTRATOR
SAP_SLD_CONFIGURATOR
SAP_SLD_DEVELOPER
SAP_SLD_GUEST
SAP_SLD_ORGANIZER
SAP_XI_ADMINISTRATOR_ABAP
SAP_XI_ADMINISTRATOR_J2EE
SAP_XI_APPL_SERV_USER
SAP_XI_BPE_ADMINISTRATOR_ABAP
SAP_XI_BPE_CONFIGURATOR_ABAP
SAP_XI_BPE_MONITOR_ABAP
SAP_XI_CONFIGURATOR_ABAP
SAP_XI_CONFIGURATOR_J2EE
SAP_XI_CONTENT_ORGANIZER_ABAP
SAP_XI_CONTENT_ORGANIZER_J2EE
SAP_XI_DEMOAPP
SAP_XI_DEVELOPER_ABAP
SAP_XI_DEVELOPER_J2EE
SAP_XI_DISPLAY_USER_ABAP
SAP_XI_DISPLAY_USER_J2EE
SAP_XI_IS_SERV_USER
SAP_XI_MONITOR_ABAP
SAP_XI_MONITOR_J2EE
Z_PFUSER
And the profiles:
SAP_ALL
SAP_NEW
I don't know what happen, may be is a problem of configuration of PI but I don't understand what.
I hope that somebody have any idea and if you required more information I don't have problem.
Thank you in advance.
Greetings.
P.D.
I'm sorry the editor doesn't respet the tags.
--erva
Edited by: Esteban Vera on Nov 16, 2011 6:56 PM

Hi Esteban,
Increase the parameters in the Config Tool in the com.sap.security.core.ume.service service as below:
ume.ldap.connection_pool.max_size (default: 10) - change to 100
ume.ldap.connection_pool.max_wait_time (default: 60000) - change to 100000
(note 948654)
Also ensure you have maintained the correct password, which MUST be the same, for all the service users
on XI. You may check all the places it should be maintained, such as Exchange Profile, SU01, SLDAPICUST, etc..
Check the note below:
#999962 - PI 7.10: Change passwords of PI service users
And ensure that the user has the correct role as per link below:
http://help.sap.com/saphelp_nwpi71/helpdata/en/9f/d12940cbf2195de10000000a1550b0/frameset.htm
Kind regards,
Caio

Soap to Soap scenario(need suggestions)

Hi All,
I have a scenario to be developed. Its a soap to soap scenario. We need to send a request with target site name and list name in the URL.
As there are 4 different sites each has different list with different columns. We need to retrieve these data in a single structure and send it back to the source system( as response). Now I am stuck in the response structure creation. Anybody has any idea? Please suggest.

Hello,
I would suggest you to check below blog and using this create ur target URL (or action) dynamically to retrieve data from different sites.
Dynamically providing URL and action values to receiver SOAP communication channel
Now for the response, i would suggest you to use JM. So, in java code parse (whatever) response which is coming from WS, send the same to ur sender system - By this way u don't have to worry abt creating response structures in PI for each site.
Hope i understood ur question correctly and if not then do correct me.
Thanks
Amit Srivastava

SOAP to SOAP scenario

Hi Experts,
Could you please tell me, how to do SOAP to SOAP scenario?
Mainly need info for Receiver SOAP Adapter...
Any document for the same?
Regards
Sara

Hi,
Receiver SOAP Adapter
The receiver SOAP adapter connects XI with an external Web service. To call the Web
service, you need to define a message interface that represents the structure of the
request and response of the Web service. You can create this message interface easily
with the help of a WSDL file that represents the Web service. If this is not possible, you must create the message interface based on data types.
- Uploading the WSDL
Since the WSDL describes the message interface, you upload the WSDL into the
Integration Repository. Go to your Software Component Version and open the required
Namespace. Create an External Definition.
In the external definition object, choose Category wsdl and click Import external
definitions.After importing the WSDL file, you can view the included messages on the Messages tab page:
The namespaces of the messages are part of the WSDL description and can
differ from the namespace of the external definition object.
Now you can create a message interface corresponding to the message types from the external definition. You need the message interface for routing the message to the Web service.
In the message interface object, select the message types of the external definition
object by using the input help.
After assigning the output and input message, save and activate your work. Now you can use the message interface for routing and mapping.
Creating a Message Interface Without WSDL
For some scenarios it is not possible to provide a WSDL file. In this case you need to create a message interface according to the message structure of the server. The best way to achieve this is by using an example SOAP message for the request and the response message.
Since the SOAP adapter creates the SOAP envelope you have to extract the SOAP
body. Usually, Web services ignore declarative attributes (xsi:type), therefore you can delete them. The namespace declaration of the root tag must be applied. The XI
message payload should be the following message.
Create a data type, message type, and message interface according to this structure. In the message type, apply the correct name and namespace of the message.
Creating a SOAP Receiver Channel
To call the Web service, you create a communication channel with type SOAP and
direction receiver in the Integration Directory. The obligatory parameters in the
configuration are Target URL and SOAP action. You get the values you have to enter
here from the WSDL file.
You find the target URL at the tag soap:address and the SOAP action at the tag
soap:operation.
If more than one message type is described in the WSDL, several SOAP actions
might also be defined. Check for the correct operation name. If no SOAP action is
defined in the WSDL, you can leave the parameter in the receiver channel empty.
For the receiver SOAP adapter you need at least the following parameters.
If the Web service is outside your system landscape and you need to address a proxy server, select the Configure Proxy checkbox and fill in the corresponding fields.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

SOAP to SOAP / HTTP 200 error

Hi
I have the following scenario   SOAP to SOAP and am getting a HTTP 200 error.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200
I have configured a sender SOAP channel with default values (Nothing is checked).   My receiver channel is configured in a similar manner. The SOAP action is specified. I have tested the receiver webservice in WSNavigator and successfully can get it to call.   The webservice was created from a function module that has used the create webservice functionality, and then endpoints created in SOAMANAGER.
There are no mappings in this scenario.
When I right click on the sender agreement and get the WSDL, I take that URL and place it into the WSNAVIGATOR tool. I supply the same values that I did when I called the service directly.   When I execute, the error above appears in SXMB_MONI.
Ideas?

Here is the error. There is no principle propagation and the user is setup in the BI system.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Edited by: Mike Marowski on Feb 18, 2010 12:12 AM

SOAP to SOAP

Similar Messages

Maybe you are looking for