Testing a Client Proxy - mustUnderstand=1, is not recognized

Hello,
I developed an Application Service in NWDS and tested it in the WebService Navigator.
It worked fine u2026
Now I want to call this WebService in ABAP. So I created a Client Proxy (SE80) with the corresponding WSDL and set up a logical port (with the same WSDL).
While testing this Client Proxy an error occurred:
SoapFaultCode: 1
Through the transaction se11 I got the following infos:
E SOAP_RUNTIME 20100914152300.8430000 : CL_SOAP_RUNTIME_CLIENT
->EXEC_PROCESSING Ausnahmebehandlung innerhalb der SOAP Laufzeit
E HTTP_TRANSPORT_BINDING 20100914152300.7340000 : CL_SOAP_HTTP
_TPBND_ROOT ->HANDLE_STATUS_CODE Received return code 500 (
Internal Server Error )
E SOAP_RUNTIME 20100914152300.8430000 : CL_SOAP_RUNTIME_CLIENT
->EXEC_PROCESSING SOAP Fault Exception caught: : Header element
[http://schemas.xmlsoap.org/ws/2004/08/addressing]To, marked with
mustUnderstand=1, is not recognized.
Can anybody give me a hint how to solve this problem?
Best regards
Tim

Can you goto Logical port and suppress message Id transfer.
You can find it under tab "Messaging"->"Message Id Protocol" = suppress id transfer and then test.
For troubleshooting please test RFC destination in SM59, you can find name of HTTP destination in "Additional Settings" tab if it is working.
Regards,
Gourav

Similar Messages

Testing the client proxy

Hi,
I generated the client proxy from the WSDL .Created a HTTP destination( Type G ) and also configured the logical port.
I also tested the HTTP connect, it works fine. But when I test the service I get an error saying
Error duing proxy processing (PART UNKNOWN (NULL) )
I'm I missing something ?
Regards,
christina.

Hi Julius,
Here is the WSDL....
http://10.54.154.128:53000/XMII/WSDLGen/Default/Oilandgas/ForTagQuery
Regards,
christina.

Client Proxy - Response Message does not populate table type element

Hi,
I came cross the situation:
Sync Client ABAP Proxy --->PI -
> Web Service Provider
In our response structure, there are some single value (0:1) and table value (0:unbound).
While testing proxy, we can see response message has one value for table type element, however, input structure table is not populated with the value.
Any advice or idea ?
Thanks
Liang

Thanks for your advice.
The proxy is in green status. Anyway, I regenerate it and activate it again.
The problem still exist.
For all single elment value, I do not have problem, it seems the proxy treat the table element as single element.
Regards
Liang

Synch Client Proxy working fine, Asynch not working

Hello,
I have created 2 Client proxies in ECC, 1 Synch,, the other Asynch.
When I run the Synch, it prompts for User/passwd in PI (I guess the default user must be bad maintained), but it works.
When I run the Asynch (I added a COMMIT WORK), I get the following error in the ECC Integration Server monitor :
"- 
- <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="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3 />
And another bunch of messages that I cannot post otherwise it will not show properly
Any ideas??
Thanks,
Marcelo

Hello, let me put here what I found out. I cannot exaplain why PI behaves like this, but it is a fact:
When the ECC's Integration Server is not correctly maintained in SM59 (it means for example that the logon data for PI is wrong), when you send a message Synchronously (which does not require a COMMIT WORK), you have to enter manually user and passwd for the PI system. I do not know why (maybe because of the COMMIT WORK??), if you do the same for an Asynchronous Proxy, the message just stays hanging in the ECC's IS with an error status, it does not prompt for user/passwd.
Living and learning...
Regards
Marcelo

How to find the error when client proxy is not successfully triggered?

Hi all,
I want to consume a .NET service in SAP.
But when I want to test the client proxy the following error occur:
GENERAL_ERROR Error duing proxy processing (PART
UNKNOWN (NULL) )
Transaction ST11:
TRACE SOAP RUNTIME - trace records
E CONTEXT 20090518061404.5255720 : CL_SOAP_CONTEXT ->SET_FAULT
SOAP runtime fault handling
E SOAP_RUNTIME 20090518061404.5256990 : CL_SOAP_RUNTIME_CLIENT
->EXEC_PROCESSING Exception handling in SOAP runtime
E CONTEXT 20090518061404.5255620 : CL_SOAP_CONTEXT ->SET_FAULT set
fault loop detected
E SOAP_RUNTIME 20090518061404.5256920 : CL_SOAP_RUNTIME_CLIENT
.NullPointerException:
Transaction SM21:
SOAP Runtime Protocol: SOAP Fault exception occurred in program CL_SOAP_RUNTIME_ROOT==========CP in include CL_SOAP_RU NTIME_ROOT==========CM004 at position 80
SOAP Runtime Protocol: Exception message: Severe processing error; SOAP fault handling required
How can I find what's wrong????
This error logging is not really helpful to me...
Any ideas?
regards

Hello Mr. Bauer,
Will you please elaborate on your solution to fix this issue?
We are facing this issue too.
Thanks in advance.
Regards,
Victor

** Logical Port in Client Proxy

Hi Friends,
I am doing proxy to web service scenario. My proxy is client proxy. After I created proxy, I checked that. There is no standard method 'EXECUTE_ASYNCHRONUS'. I read the Michal's blog /people/michal.krawczyk2/blog/2009/06/20/pixi-abap-proxies-say-goodbye-to-executeasynchronous-method and understand that this method is not created. The reason is that SAP_BASIS support package level is 15. (Release 700) in our R/3 ECC 6.0 system.
Now, I am not able to test my proxy from SPROXY tcode. It asks Logical Port.
1. Can you tell me, what is logical port ? How do I create this in LPCONFIG tcode ?
2. Once this is done, can I call the class with the method like in older version ?
3. Currently I am getting the information 'No vendor specified' while test proxy withe empty logical port.
Expecting your reply.
Kind regards,
Jegathees P.

Hi Rene,
If a logical port is not configured, the X/PI Runtime will be used instead.
In Jegathees' case, this is probably what happened. If you want to route your message through PI then you need to make sure that you are pointing to your Integration Server (i.e. PI), on ECC use transaction code SXMB_ADM --> Integration Engine Configuration. Role of Business System should be "Application System" and "Corresp. Integration Server" should be your PI server.
You will see when you test your client proxy (using TCode SPROXY) you have the option of choosing XI Runtime - or - Logical port too.
Regards, Trevor

Error while deploying Java Client Proxy

Hi Experts,
I developed a java client proxy.Since i do not have access to visual administrator, i uploaded the ear file to a folder in the XI box and asked the basis folks to deploy it.
On trying to deploy it on to the server they got the following error.
Details:
========
1) Error loading archive
    /usr/sap/XS1/put/R3Ear.ear
    (server side name is: /usr/sap/XS1/put/R3Ear.ear)
    com.sap.sdm.util.sduread.IllFormattedSduFileException: Error during attribute reading: received exception: invalid stored block lengths
What could be the reason for the error?

Hi
recreate your ear file and try to redeploy it.
it could be a zipping problem
Regards
Vishnu

Web service - Client Proxy - SOAP error

Hi All,
I created a custom web service/port and Client proxy.
While I test the Client proxy with Logical port via SE80, I am getting error message related to SOAP.
Error text:
SOAP:14 Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
Error when processing Web service call
Error when calling SOAP Runtime functions: Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
Am I missing any configuration?
THanks,
Chirag

Hi,
I got the same error with using the configuration tool LPCONFIG after implementing -> with SOAMANAGER everything worked allright directly just create a port with that tool.
Maybe tha will help you also - for your problem.
Regards,
Jeroen Cosijnse

Sqlplus is not recognized

hi,
When I connect to database from client it says sqlplus is not recognized as internal or external command.
The Path is set to correct directory though
Client 10.2.0.3 on Windows 2003
Thanks
Message was edited by:
user604101
Message was edited by:
user604101

oops, I think SQLPLUS is not installed on this server with the client installation. Because I cannot see sqlplus.exe in BIN directory.
This was installed long back.
Can anyone tell me how to install only SQLPLUS into this client?
Thanks
Message was edited by:
user604101

PI 7.1 - Configuring a client proxy - not working.

I am trying to send a Client proxy from ECC to XI.
This is a new PI 7.1 install so I am trying to test a quick and easy client proxy from ECC to XI and cant even get a message sent to XI.
On ECC, I am getting a weird message in SXI_MONITOR
I get a gray colored flag and when I hover over it, give me the following info:
"Message recorded (Commit Missing)".
Has anyone encounter this type of status.
Basically the message never send out to XI. Also, the message does not let me restart or even cancel the message.
Overall, all the config looks good on ECC
SLDCHECK looks good.
In ECC, I configured the Integration engine config as an Application Server and pointed it to RFC destination that points to the XI server.
-steve

Hi,
1) Queues are clean
2) I have checked the RFC Destination for the HTTP connection. It brings back a 500 empty response which is good.
I did a check on the Integration Engine Config and it brings back a yellow status that "Corresponding Integration Server not Maintined"
I wasnt sure if this was an info message that really wasnt an error.....any thoughts?

Need some help regarding Client Proxy generation and test via SOAMANAGER

Hello,
we are integrating a 3rd party Java client via webservices.
For that matter I generated a client proxy (consumer proxy) in se80 using the existing WSDL.
This worked fine.
The I wanted to create a logical port.
Since this is only possible in SOAMANAGER I tried it there.
Trying to do this automatically by the given WSDL file didn't work. The system dumps.
So, I tried the manual approach by entering the server name and path in the 'Transport settings' tab.
Now I wanted to test this.
Unfortunately the test function in se80 (Proxy->Test) doesn't show a positive result.
I always get an error
SOAP:1.023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response:
ICM_HTTP_CONNECTION_FAILED")
So, I am kind of stuck here.
Do you guys have any idea what's wrong (approach, settings, bugs)?.
I tested the webservices with a test application (soapUI), and they work fine.
So it seems to be a problem in the proxy framework or a network problem?
I really appreciate any kind of help.
Thanks,
Michael

i created the port in soamanager.Do i need to create in lpconfig also?
yes i have loaded the certificate in strust.
i am getting the response also from the web service. as Security requirements are not satisfied because the security header is not present in the incoming message.
i need to pass the user name and password while using the method.wsse security.wld u have any clue?

How to use Http test Client for Java Client Proxy Scenario

Hi,
I build a scenario using Java Client Proxy where JSP as my FrontHand.
Can I know that whether i can use Http Test Client in place of JSP for sending data and getting response back. If yes than how can i implement this ?
Regards,
Abhi

Hi,
with Http Test Client you post your messages
directly to the Integration Engine (not using adapter framework)
so you can use Http Test Client to simulate any message
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

I want to test sender ABAP proxy in AAE by SOAP client

To PI Specialists
Now I plan to test sender ABAP proxy in AAE by SOAP client system.
(we use aae so we set sender abap proxy by sender soap adapter.)
ABAP creating team and PI creating team are in other site.We cant contact easily.
I want to separate ABAP Unit test and PI Unit test, plan to use soap client for test driver.
(we use SOAPUI. )
the url is http://<host>:<port>/XISOAPAdapter/MessageServlet?channel=party:service:channel
I noticed that sender soap adapter is started, but the messeage protocol is invalid.
we use messege of wsdl. it must be XI3.0 protocol.
Please tell me XI3.0 protocol.
Naoki

This is possible to do in SOAPUI. I am testing this scenario using AAE, but I am also using SOAP UI Pro. The procedure is pretty basic. Instead of sending your payload in as part of the body, you have to send it in as an attachment. You will also need to set the header correctly. Here is a sample message from my SOAP UI tests that may help. The only thing you need to do differently is load the attachment, name it, and make sure that the name of the attachment is reflected in the SAP:Payload attribute. Also, I am using a Groovy script to create a GUID.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
<soapenv:Header>
<SAP:Main versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92FFF13F5C59777FE1ABE00000A1551F7" 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">
   <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
   <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
   <SAP:MessageId>${Create GUID#result}</SAP:MessageId>
   <SAP:TimeSent>${=new java.text.SimpleDateFormat("yyyy'-'MM'-'dd'T'HH':'mm':'ss'Z'").format(new Date())}</SAP:TimeSent>
   <SAP:Sender>
    <SAP:Service>SVCNM</SAP:Service>
   </SAP:Sender>
   <SAP:Interface namespace="Interface_Namehttp://namespace.com">Interface_Name</SAP:Interface>
</SAP:Main>
<SAP:ReliableMessaging SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
<SAP:System SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SAP:Record namespace="http://www.sap.com/webas/712/soap/features/runtime/metering/" name="CallingType">SA</SAP:Record>
</SAP:System>
<SAP:Diagnostic SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SAP:TraceLevel>Information</SAP:TraceLevel>
   <SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
<SAP:HopList SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SAP:Hop timeStamp="${=new java.text.SimpleDateFormat("yyyy'-'MM'-'dd'T'HH':'mm':'ss'Z'").format(new Date())}" wasRead="false">
    <SAP:Engine type="BS">SVCNM</SAP:Engine>
    <SAP:Adapter namespace="XIhttp://sap.com/xi/XI/System">XI</SAP:Adapter>
    <SAP:MessageId>${Create GUID#result}</SAP:MessageId>
    <SAP:Info>3.0</SAP:Info>
   </SAP:Hop>
</SAP:HopList>
</soapenv:Header>
<soapenv:Body>
<SAP:Manifest wsu:Id="wsuid-main-92FFF13F5C59777FE1ABE00000A1551F7" 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">
   <SAP:Payload xlink:href="cid:TestPayload.xml">
    <SAP:Name>MainDocument</SAP:Name>
    <SAP:Description/>
    <SAP:Type>Application</SAP:Type>
   </SAP:Payload>
</SAP:Manifest>
</soapenv:Body>
</soapenv:Envelope>
Here is a picture of my SOAP UI project in case it help the understanding.

Client Proxy: XML message not well-formed unexpected symbol 'target

Hi,
I'm trying to get a client proxy to work based on several blogs (1387,1672)
The error I'm getting now is:
<SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="XML message not well-formed in node (7 ,49 )unexpected symbol: 'target'" p2="" p3="" p4="">PARSING.GENERAL</SAP:Code>
<SAP:Text language="EN">Parsing error: XML message not well-formed in node (7 ,49 )unexpected symbol: 'target'</SAP:Text>
</SAP:ErrorHeader>
The proxy has been generated successfully
in SXMB_ADM R/3 role is application system and uses dest://rfc_dest
The rfc destination does not accept ?type=entry but apparently also does not need it. When I test the connection it gives a statuscode 200 (not 500)
SLDCHECK works fine.
Not sure where to look for this error?
Any ideas?
Thanks
Tom

Hello Smitha,
I forgot to mention that the message is still in R/3, it has not arrived in XI yet, so the error is visible in SXMB_MONI in R/3.
Also it is just a dummy message, It only contains one node and that is called differently:
<?xml version="1.0" encoding="utf-8" ?>
- <ns1:IF021_HTTP_MSG xmlns:ns1="http://oce.com/xi/eu1/R3CCSEU/IF021_Ordrsp_TD_to_Ordrsp_CCS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<IF021_DT>GetOrdRsp</IF021_DT>
</ns1:IF021_HTTP_MSG>
Any mappings only take place in XI itself, and even there I have no node called target.
Regards
Tom

Client proxy message not reaching to XI system

Hi
I have done one scenario from CRM to FILE. When i am executing the client proxy through my zprogram its executing without any errors. I have checked in SXMB_MONI of CRD system i can see the messages but they are not with successful flag or not with error flag. But in XI system (SXMB_MONI) i didnt find any messages. Could you please tell me what's the problem is?
Regards
Sowmya

Sowmya,
As you are not getting any message in SXMB_MONI, there can be following possibilities:
1. There can be some problem in proxy configuration on your CRM system. Please check with your BASIS team that steps give in this blog are properly followed:
How do you activate ABAP Proxies?
2. Make sure that in
SXMB_ADM --->integration engine config -
>change specific attributes....
The RUNTIME parameter is defined LOGGING and TRACE_LEVEL and the value is 1.
3. Make sure the queues are registered in Tx: SMQR.
Further, I do not think that COMMIT statement or anything like that is missing as in that case you should have got a message in SXMB_MONI with a green flag stating that "Commit statement is missing".

Testing a Client Proxy - mustUnderstand=1, is not recognized

Similar Messages

Maybe you are looking for