INTEGRATION_DIRECTORY_HMI - Response Code 200

Hi Experts,
Readiness Check Document for PI 7.1 suggests that HTTP Response code for INTEGRATION_DIRECTORY_HMI should be 500. But when I am testing this on my PI 7.1 EHP1 server, I am getting 200 as HTTP response. Is this normal? If not, please let me know what to do. Thanks in Advance.
Cheers,
Phani Akella.

Hi Phani,
As you have mentioned according to the sap pi 7.1 documentation
http://help.sap.com/saphelp_nwpi71/helpdata/en/8f/770f41218ff023e10000000a155106/content.htm
the test is successful if the response status code is 500 and you find REQID not found in the response body.
in PI 7.1 when i checked ,i am getting 500 status code.
could you please let us the message that you are getting any different error message.If you are getting the same message which used to come when response code is 500.if yes this might be a change in EHP1.
Regards,
Srinivas

Similar Messages

How to check HTTP response code

Hi,
we have the following scenario:
HTTP -> PI -> HTTP
So it's easy to use HTTP or SOAP-adapter here.
But we have to inform the sender of the message immediately about the successfull delivered message.
So we have to check if response code 200 was sent from the receiver of the message and inform the sender about this.
I can't find any possibility how I can check this in PI 7.1 (neither by using HTTP adapter nor by using SOAP-adapter). There is no acknowledgement mechanism (I can't find any).
Does anybody know how we can solve this?
Thanks for your replies.
Regards
Thorsten

If the response has to travel from Receiver to Sender then you have to make use of SYNC mode of processing or use a BPM.
In Async flow the Sender will get a HTTP 200 OK response from the sender adapter of SAP XI/ PI.
Regards,
Abhishek.

HTTP response code 302

When sending an HTTP POST request from a java application, I get a response code 200 but nothing is done. And when I look at the http access log on the server (responses.0.trc), a 302 response code is logged.
Any idea to solve this problem?
Thanks in advance

Hi
See this link for the reason of the error
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
Kind Regards
Mukesh

Response.sendError(200)does not work in Tomcat

Hi,everyone,
I'm using a servlet named as "Router" to receive messages from client. Because the processing time of "Router"is quite long, I want it to send back the "200 OK" response to the client at the beginning of the service() method. My Router.java is like this:
public class Router extends HttpServlet
public void service(HttpServletRequest request, HttpServletResponse response)
throws ServletException
// send a response code "200 OK" to the client
response.sendError(200);
//processing the received message
My program works well in ServletExec server, but in Tomcat, it does not work. In tomcat, the 200 OK can only be sent back after the whole service() process is finished. The "response.sendError(200);" seems does not work at all. Can anyone help me to resolve it?
Thanks a lot!
grass

hi, greatmazinger,
Thank you very much! I changed my code
"reponse.sendError(200);" to:
"reponse.setStatus(200);
response.flushBuffer();"
Then the response was sent back immediately.
Thanks a lot!
Ying

Message failed in PI: Status code 200 But Error During Response Parsing:

Hi
I have integration scenario for sending PO/PO change/Proact from R/3 to SNC, everything was working till yesterday morning and suddenly all messages are failing in SAP PI with below error. We have not done any changes. The strange thing is this is failing in dev as well as in QA.
HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)
I can see some messages in sxmb_moni (we have not configured this) from sender component "Integration_Server_SID" and it's failed with below message
Proxy calls are not permitted on sender or
receiver side on the IS (client)
Thanks,
Nishant

HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received
XML element {http://schemas.xmlsoap.org/soap/envelope/}Envelope missing in SOAP message header (SAP XI Extension)
Same problem answered in this discussion....check if it helps:
Re: BW to File scenario
Regards,
Abhishek.

HTTP Status Code 200 Received But Error During Response Parsing

Hi Experts,
We are testing a simple Proxy(ECC) to File scenario in QA. This interface was working fine in Dev but we are getting the following error here in QA:
<?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="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
We searched other threads but could not get any solution. Please provide suggestions.
Thank You.
Regards,
Anandan

the problem was due to high volume message (247 MB ) ...Java stack was not able to process this huge message ,that is the reason ,it started automatically and as a result , "HTTP Status Code 200 Received But Error During Response Parsing" due to unavailability of AFW during Call adapter step in the pipeline processing...
We have done the following activities in order to solve this problem....
increase the value of icm/HTTP/max_request_size_KB to 512MB
 icm/wp_roll_timeout to maximum
 HTTP TIMEOUT to 1800 sec
 icm/wp_roll_timeout to maximum
 mpi/total_size_MB to maximum
 mpi/buffer_size to maximum
and then increased the maxthreadcount ,maxcontentlength using config tool...
and also increased the java heap size to maximum....
After doing everything ,the file has been successfully processed....
the problem has been resolved...

Ace http response code seeing 500, but server returning 200

we have an http probe configure like below,the real is failing probe, and the ace says it's returning a 500 response code,however when i browse to the server from my laptop, i get a 200, and the correct regex ( going to http://172.19.254.51/operation.aspx) . Is it possible the server could send a different response code to ace?
probe http HTTP
interval 5
passdetect interval 5
receive 3
request method get url /operation.aspx
expect status 200 200
open 2
expect regex "operation"
serverfarm host AMS_AI
probe HTTP
rserver server1
    inservice
rserver server2
    inservice
rserver server3
    inservice
show probe HTTP detail
     real      : server3I[0]
                       172.19.254.51   1925172    24779      1900393    FAILED
   Socket state        : CLOSED
   No. Passed states   : 5646         No. Failed states : 5646
   No. Probes skipped : 0         Last status code : 500
   No. Out of Sockets : 0         No. Internal error: 0
   Last disconnect err : Received invalid status code
   Last probe time     : Wed Feb 23 10:53:21 2011
   Last fail time      : Wed Feb 23 09:21:29 2011
   Last active time    : Wed Feb 23 03:51:41 2011

you will probably have to configure the HTTP header of the probe you send. Maybe the web server
is expecting specific fields (virtual hosts ?)

"UnexpectedHTTP Response - Status Code:200" error with Yahoo mail.

I am getting constant error "UnexpectedHTTP Response - Status Code:200" error with Yahoo mail. Is it some known error?
I have a snapshot of issue but there is now way I could attach that with this query. This happens more often after I login into yahoo and try to delete my mails or delete my spam mails or go to inbox etc...
Thanks,
Santosh Thankachan

EXACT, but the interface monitor shows that as an error.
And that's what I need, a good monitoring, that should not appear as an error

Receiver XI adapter error :HTTP Status Code 200 during Reponse Parsing

Hi Exeprts,
My Scenario is mail to ABAP proxy , I have got the bellow error in moni while testing my secnario .
Please help me reslove this .
<?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="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Regards
Upendra

Hi Mark ,
No error message in attachement . only it daisplay the following information
SAP Library
SAP Library contains the complete documentation for SAP NetWeaver Application Server Java. You can access it by choosing SAP NetWeaver.
 SAP NetWeaver Administrator
A powerful administration, configuration and monitoring tool, which bundles key administrative tasks to keep your SAP NetWeaver system landscape running. SAP NetWeaver Administrator can be used in a central or local scenario. Here you access the local NetWeaver Administrator.
 System Information
System information provides administrators with an overview of the system configuration and its state. It shows all of the system's instances and processes, their current state and important parameters (such as ports) that may be required for support cases, as well as the versions of the components installed.
 Services Registry
The Services Registry is a UDDI based registry that contains definitions of enterprise services and references to their metadata.
 User Management
The user management administration console provides administrators with the functions they need to manage users, groups, roles, and user-related data in the User Management Engine (UME). Users without administrator permissions can use it to change their user profile.
 UDDI Client
The UDDI client provides query and publishing functions for UDDI entities to any UDDI compliant registry.
 Web Services Navigator
Web Services Navigator is a tool that gives you a short overview of a specific Web service based on its WSDL, and enables you to test your Web service by creating and sending a client request to the real end point.
 Web Dynpro
Web Dynpro is a User Interface technology available within the SAP NetWeaver Developer Studio.
Various Web Dynpro tools provide administrators and application developers with performance measurement and application administration capabilities. The Web Dynpro runtime is already deployed.
Regards
Upendra

Error Transmitting the message to endpoint -Received HTTP response code 401

Hello Experts,
I am having a SOAP to Proxy scenario. We are using HTTPS without client Authentication.
Everything is running fine and well set on DEV system. After transporting to Test system, i am getting error as :
Error Transmitting the message to endpoint http://host:port/sap/xi/engine?type=entry using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 401 : Unauthorized.
I get HTTP 200 Ok response in my soap client but the message is not reaching to Integration Engine. It is failing with above error. On CC monitoring for SOAP adapter it shows call completed successfully. But when I use the mesage ID from CC monitoring in Message monitoring i get the error as shown above in Audit log.
I have checked for Roles attached to my user on DEV and Test systems , I have same roles on both systems.
Any inputs to solve this problem will be very helpful to me. Let me know which service users i need to check for this issue?
Thanks in Advance,
XI Queries.

Hi Pinang,
Thanks for input.
1) Check Role -SAP_XI_APPL_SERV_USER is there in XIAPPLUSER or not.
->Done. Its Ok.
2) check tyour port entry is like J2EE port 5<System no> or not.
->Done. Its Ok.
3) If the error in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
->This note refers in case it happens with high load. I am just sending a small request and no one else is using / testing this interface. So no high load.
4) Check password for user XIISUSER
-> Basis team said they checked for all Xi users and they are not locked.
5) Check password for user XIAFUSER
-> Basis team said they checked for all Xi users and they are not locked.
Any other hints will be helpful.
Kind Regards,
Xi Queries.

Proxy to File - CLIENT_RECEIVE_FAILED - error code: 200, error text:

I have configured a Proxy to JDBC scenario from a new ECC dev system and it works great. I recently tried migrating the changes to the new ECC qas environment and I get the following error message. Can anyone help, I must have missed some configuration somewhere?
<?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="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>200</SAP:P1>
<SAP:P2>Error Parsing Response. No XI Response Received.</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><html> <head> <title>SAP J2EE Engine Start Page</title> </head> <frameset framespacing="0" border="0" rows="90,*" frameborder="0"> <frame name="banner" scrolling="no" noresize target="contents" src="top.html" marginwidth="0" marginheight="0"> <frame name="main" src="main.html" marginwidth="10" marginheight="30" scrolling="auto"> <noframes> <body> This page uses frames, but your browser doesn't support them. </body> </noframes> </frameset> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while receiving by HTTP (error code: 200, error text: Error Parsing Response. No XI Response Received.)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>

Hi!
I think what michal told is correct there is a connectivity issue but please make sure regarding mapping also why it is unable to receive the response...
Actually ERROR 200 code means::
Description: The request has succeeded. The information returned with the response is dependent on the method used in the request GET an entity corresponding to the requested resource is sent in the response; HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body; POST an entity describing or containing the result of the action; TRACE an entity containing the request message as received by the end server.
Possible Tips:
Have a look into SAP Note: 871959..
I know this is not an exact answet but this ill give u some idea..
Regards::
Amar Srinivas Eli

Reset the HTTP response code in OSB for proxy service

Hi,
I created a HTTP proxy service in ALSB with any XML message option. There are some business scnearios for which i need to send a custom error message in the HTTP body. I am replacing the $body variable with the error message and sending reply with success.As i am using reply with success it sends a HTTP response status code as 200 Ok.
However based on different error conditions i want to send appropraite http response code. How can this be achieved?

I would like to share the solution so that it would be useful to all the users of the forum.
There is a http:http-response-code element in the $inbound variable which is optional element. You need to insert this element to the $inbound using the insert action. Here is the extract of the code:
Insert [<http:http-response-code>401</http:http-response-code>] [ as last child of ] [./con:transport/con:response] in [inbound]
Please note namespace con belongs to "http://www.bea.com/wli/sb/context".
Edited by: [email protected] on Aug 12, 2009 10:47 PM

Receiver proxy error - CLIENT_RECEIVE_FAILED error code 200

Hi,
Scenario: JDBC to Proxy.
I am getting an error on the receiver side - below is the error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>200</SAP:P1>
<SAP:P2>Error Parsing Response. No XI Response Received.</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>--SAP_4732F0E6BA080C67E1000000A859B621_END content-type:text/xml content-length:4118 content-id:<[email protected]> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <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>asynchronous</SAP:ProcessingMode><SAP:MessageId>FA074580-8DE5-11DC-9B3E-00144F2B5900</SAP:MessageId><SAP:TimeSent>2007-11-08T10:33:00Z</SAP:TimeSent><SAP:Sender><SAP:Service>BS_ESS</SAP:Service></SAP:Sender><SAP:Receiver><SAP:Party agency="" scheme=""/><SAP:Service>CD103</SAP:Service></SAP:Receiver><SAP:Interface namespace="http://www.Coj.co.za/EssToSapIsu/Ess">MI_EssToSapIsu_EssMiForSapIsu</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>ExactlyOnce</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="2007-11-08T10:33:00Z" wasRead="false"><SAP:Engine type="AE">af.cxd.jssxid0</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter><SAP:MessageId>FA074580-8DE5-11DC-9B3E-00144F2B5900</SAP:MessageId><SAP:Info/></SAP:Hop><SAP:Hop timeStamp="2007-11-08T10:33:00Z" wasRead="false"><SAP:Engine type="IS">is.00.jssxid0</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter><SAP:MessageId>FA074580-8DE5-11DC-9B3E-00144F2B5900</SAP:MessageId><SAP:Info>3.0</SAP:Info></SAP:Hop></SAP:HopList> <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:TraceLevel>Information</SAP:TraceLevel><SAP:Logging>Off</SAP:Logging></SAP:Diagnostic> <SAP:MessageHeader xmlns:SAP="http://sap.com/exchange/MessageFormat" version="1.0" SOAP:mustUnderstand="1"><SAP:From><SAP:Name></SAP:Name><SAP:Interface namespace=""></SAP:Interface></SAP:From><SAP:MessageId>00000000-0000-0000-0000-000000000000</SAP:MessageId><SAP:QualityOfService></SAP:QualityOfService><SAP:TimeSent></SAP:TimeSent><SAP:Direction>Request</SAP:Direction><SAP:Document></SAP:Document></SAP:MessageHeader> <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat"><SAP:Context></SAP:Context><SAP:Code p1="" p2="" p3="" p4="">CALLER.MSG_GUID_NOT_QUALIFIED</SAP:Code><SAP:Text language="EN">Attribute message GUID not specified</SAP:Text></SAP:ErrorHeader> <SAP:HopList xmlns:SAP="http://sap.com/exchange/MessageFormat" Version="1.0"><SAP:Hop SystemName="CD103" Type="SENDER" TimeStamp="2007-11-08T11:00:57Z" WasRead="0"><SAP:MessageInbound><SAP:Type>AENGINE</SAP:Type></SAP:MessageInbound><SAP:MessageOutbound><SAP:Type></SAP:Type></SAP:MessageOutbound></SAP:Hop></SAP:HopList> <SAP:InternalAttributesHeader xmlns:SAP="http://sap.com/exchange/MessageFormat"><SAP:AdapterInbound>AENGINE</SAP:AdapterInbound></SAP:InternalAttributesHeader> </SOAP:Header> <SOAP:Body xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <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:[email protected]"><SAP:Name>MainDocument</SAP:Name><SAP:Description/><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest> <SAP:Manifest xmlns:SAP="http://sap.com/exchange/MessageFormat" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0"> <SAP:Payload xlink:href="cid:[email protected]"> <SAP:Document>TraceDocument</SAP:Document> </SAP:Payload> </SAP:Manifest> </SOAP:Body> </SOAP:Envelope> --SAP_4732F0E6BA080C67E1000000A859B621_END content-type:application/xml content-length:417 content-id:[email protected] <?xml version="1.0" encoding="UTF-8"?> <ns0:MT_EssToSapIsu_EssMtForSapIsu xmlns:ns0="http://www.Coj.co.za/EssToSapIsu/Ess"><TABLE1><BSTKD>A0707120330</BSTKD><BSTDK>12-07-2007 </BSTDK><ZE01>15:33</ZE01><ZE04>JANICE</ZE04><ZE05>DS3</ZE05><ZE06>RIVERLEA</ZE06><ZE02>,957 A KOMANI,RIVERLEA</ZE02><MATNR>A</MATNR><ZE03></ZE03><AUGRU>Medical - General</AUGRU></TABLE1></ns0:MT_EssToSapIsu_EssMtForSapIsu> --SAP_4732F0E6BA080C67E1000000A859B621_END content-type:text/plain content-length:1717 content-id:[email protected] <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat"><Trace level="1" type="B">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace> <Trace level="1" type="E">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</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="1" type="T">system-ID = CD1</Trace> <Trace level="1" type="T">client = 103</Trace> <Trace level="1" type="T">language = E</Trace> <Trace level="1" type="T">user = MOLAIM</Trace> <Trace level="1" type="Timestamp">2007-11-08T11:00:57Z </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">**************************************************** </Trace> <Trace level="1" type="B">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace> <Trace level="1" type="T">Message-GUID = 00000000000000000000000000000000</Trace> <Trace level="1" type="E">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace> <Trace level="1" type="System_Error">Exit XMB because of system error!</Trace> <Trace level="1" type="System_Error">System-Error: CALLER.MSG_GUID_NOT_QUALIFIED</Trace> <Trace level="1" type="System_Error">Attribute message GUID not specified </Trace> <Trace level="1" type="E">CL_XMS_MAIN-ENTER_XMS</Trace> <Trace level="1" type="E">CL_XMS_HTTP_HANDLER-HANDLE_REQUEST</Trace> </SAP:TraceHeader> SAP_4732F0E6BA080C67E1000000A859B621_END</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while receiving by HTTP (error code: 200, error text: Error Parsing Response. No XI Response Received.)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Thanks,
Leanne

Are u trying a synch scenario? Ur server proxy must be receiving the data properly. If it is a sync scenario then u should check the response mapping again in sxmb_moni.
Regards,
Prateek

SAP consume external web service - HTTP Code 200 : OK

Hi
We are integrating UPS Shipping Ground Web service with SAP system and we have the settings in place on our side and did a blank request test today and we are getting a " HTTP Code 200 : OK " error instead of a response.
The SAP SOAManager shows the below detail for the error:
A SOAP Runtime Core Exception occurred in method get_http_headers of class CL_SOAP_HTTP_TPBND_ROOT at position id 3 with internal error id 1007 and error text SRT: Unsupported xstream found: ("HTTP Code 200 : OK") (fault location is 1 ).
One thing we noted but not sure about it is that the response content type is showing text/plain while the request shows content type accept text/xml in SOAManager trace functionality. (screen shot )
I see several discussion on this but could not figure out what needs to be changed in SE80 consumer proxy or the SOAManager port level. Please advice.
Regards,
Prabaharan G

hi Prabaharan! thanx for answer!
i do integration with document scanning/recognitioning system (ABBYY FlexiCapture). It interact as SOAP services over MS IIS server in local network.
what i`ve done:
- drop everething at first.
- create proxy in se80 using wsdl file. created ok.
- create logical port in soamanager using "Create WSDL based configuration". created ok.
- go to sm59. there are some connections but nothing like my connection. i have check all sections, not only type G(HTTP).
AND HERE HAPPEN GREAT THING!
Test "ping" fail but my test code start to work!
All I have change is "url access path". So i think that was my problem. (I was confused by ping fail early and have trying to change all settings)
you bring me luck - thank you very much!

Problem in SXI Cache refresh:Response Code 503

Hi all,
The SXI cache contents are not getting refreshed automatically on making changes in the Directory or Repository. Also, I am unable to refresh the cache contents manually in transaction SXI_CACHE.
I get the following error on refreshing: Response Code 503: Service Unavailable.
The RFC Destination INTEGRATION_DIRECTORY_HMI has correct entry in the URL(Path Prefix) and Test Connection from SM59 is working fine.
How do I make this work?
Regards,
Puloma Chaudhuri.

Hi all,
The exact nature of the error on refreshing in SXI_CACHE is:
CacheRefreshRepositoryCommunicationException: Attempt to access application REPOSITORY using Http Method Invocation (HMI) failed. Detailed information: Invoking ROA method "ReadObjects" via HMI ... FAILED due to following exception: Message: Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://server:50000/rep/remoteobjectaccess/int?container=ejb" with user "XIDIRUSER". Response code is 503, response message is "Service Unavailable"
Does that narrow it down?
Regards,
Puloma Chaudhuri.

INTEGRATION_DIRECTORY_HMI - Response Code 200

Similar Messages

Maybe you are looking for