Http Receiver Monitoring

Hi Experts,
I have configured an plain http receiver adapter to send messages to an apache server.
All parameters in communication channel are configured.I am able to see a checked flag in monitor.But the message doesn't reach the target system
Also tried looking at the message display tool : http://<HostName>:<Port>/MessagingSystem/monitor/monitor.jsp
which shows a success :
2010-02-04 12:02:23 Success The message was successfully transmitted to endpoint http://<HostName>:8000/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System.
2010-02-04 12:02:23 Success The message status set to DLVD.
The message display tool shows till my XI Integration engine successful post.How can i determine where the message is failing?

Which log did you check? the sender side adapter or the receiver side? it looks like your message is posted to integration engine.. there it got processed successfully (hence the checkered flag in sxmb_moni). But it might be failing on the receiver http adapter side. Check the communication channel monitoring for that channel in rwb.
VJ

Similar Messages

HTTP Receiver Adapter: Payload in SXI Monitor

Hi
We have a scenario where System A is sending information by HTTP to SAP XI (No Sender HTTP Adapter required). SAP XI is posting an Idoc in R/3 and sending back two fields to same sender.
We have defined 2 Receiver determination, one for Idoc and another for response for the same sender. Further also seprate mapping program, Interface mapping and Message interface has been defined for them (No BPM is required).
When we are running the test,everything goes successful and the incoming messages has two receivers, the Idoc is posted and also a response is send back to the sender system(which becomes receiver now). I can see successful flag for both of them and further the receiving system also is able to receive the response successfully, but I cannot see the response payload in Monitor for HTTP receiver, it shows the incoming payload and transformed Idoc after mapping, but it does not show the response message for HTTP receiver and only shows the incoming payload.
How can I see the outgoing payload for the same (as HTTP Adapter does not exist on AE) and thus RWB - AE monitoring is not possible. Can someone help me out how to check the outgoing payload for HTTP receiver in Monitor.
System A --> SAP XI --> SAP R/3 (IDoc)
I----
> System A (HTTP Receiver)
BR / Swetank

Hi
I am not bothered about Idoc part. The sender is sending supposing 3 fields
a,b,c. The idoc is posted with those two fields.
And a message is again send to Sender system (Which now becomes receiver) with two fields only (a,b) that we have received this field A( order number). This is not transport acknowledgement, but a payload which is send back.
Separate Mappings have been defined for Idoc and HTTP receiver and my query is that I cannot see the outgoing payload in monitor. Even though on verifying with the receiver system, they receive the actual transformed payload.
So I do I see the outgoing payload in Monitor for HTTP receiver in Monitor ?
BR / Swetank

How Do We Monitor HTTP Receiver Communication Channel

Hi Exports,
How do we monitor the HTTP Receiver communication channel. Could you please share your ideas.
I am able to send the message to http to third party system. i want to monitor all messages which it's goes to third party system. Same like if you go to component monitoring we have communication channel monitoring over there we can do monitoring by adapter but when we choose http communication channel there is 0 messages.
Please provide monitoring thing those messages which is goes to third party system.
Advance thanks
Regards
Ramidi S

There isnt any transaction to directly monitor the HTTP adapter. However u may do the following:
1. To test the HTTP adapter you can just test the adapter_plain service in TCODE SICF.
2. TCODE : SMICM and then Shift + F1 and you can see the status of the HTTP server
3. You can go to SM59 to see whether the HTTP connections between XI and R/3 are up and running
Regards,
Prateek

Monitoring of messages sent by HTTP Receiver

Hello,
is there any possibility to monitor HTTP requests sent by the HTTP receiver? I would like to check the header settings of the HTTP request. Thank you.

Hi Florian,
Do you mean Messages sent by HTTP sender?
YOu can monitor messages in SXMB_MONI transaction in the abap stack of the XI system.
Not sure, if you meant anythig else.
Regards,
Ravi

HTTP receiver Adapter configuration

Hi All,
I want to post an XML message using HTTP Receiver Adapter for my BPM scenario (Idoc to HTTP service)
The receiver has Oracle gateway and it expects message in following format.
HTTP Header
   HttpVersion: HTTP/1.1
   Authorization: Digest username=myusername,
                         realm=[email protected],
                         nonce=dcd98b7102dd2f0e8b11d0f600bfb0c093,
                         uri=/dir/index.html,
                         qop=auth,
                         nc=00000001,
                         cnonce=0a4f113b,
                         response=6629fae49393a05397450978507c4ef1,
                         opaque=5ccc069c403ebaf9f0171e9517f40e41
                         Contentlength: 12345
                         Contenttype: text/html
HTTP Body
   TRANSPORT_PROTOCOL=OXTA
   TRANSPORT_PROTOCOL_VERSION=1.0
   REQUEST_TYPE=SEND
   MESSAGE_ID=A1234567890ZZ0987654321
   MESSAGE_TYPE=XML
   MESSAGE_STANDARD=OAG
   TRANSACTION_TYPE=PO
   TRANSACTION_SUBTYPE=PROCESS
   DOCUMENT_NUMBER=12345
   PARTYID=9999
   PARTY_SITE_ID=8888
   PROTOCOL_TYPE=HTTPSOXTA
   PROTOCOL_ADDRESS=HTTPS://www.me.com/servlets/oracle.ecx.oxta.
   transportAgentServer
   USERNAME=myusername
   PASSWORD=myloginpassword
   ATTRIBUTE1=
   ATTRIBUTE2=
   ATTRIBUTE3=
   ATTRIBUTE4=
   ATTRIBUTE5=
   PAYLOAD=<xml ... ...>
I think this is not a typical HTTP URL type of format, is it?
And I am not sure how I can build the message. Where do I put the parameters like TRANSPORT_PROTOCOL, TRANSPORT_PROTOCOL_VERSION, REQUEST_TYPE etc in the HTTP adapter?
Also is there any place where I can see the final actual XI message that is sent to HTTP service?
Any help will be really appreciated.
Thanks and regards,
Rahul.

Hi Rajeev,
The receiver system should have the details about the content type it expects. I got that from the team who monitors our receiver system.
The HTTP Body of HTTP adapter is made up of PrologPayloadEpilog.
So I added the paramter list that receiver system expects as part of the Prolog. Refer to the HTTP body that I have posted in my earlier message. Out of that till ".....Payload=" is added to Prolog and XI then appends actual payload to it.
To be precise -
TRANSPORT_PROTOCOL=OXTA&TRANSPORT_PROTOCOL_VERSION=1.0&MESSAGE_TYPE=XML&MESSAGE_STANDARD=UNIVERSAL&TRANSACTION_TYPE=XXXE&TRANSACTION_SUBTYPE=ORDER_I&DOCUMENT_NUMBER=PO12345&PARTY_SITE_ID=ESAP_ORDER_I&USERNAME=***&PASSWORD=**&PAYLOAD=
So in the end it worked out well.
Cheers,
Rahul.

HTTPS communication using HTTP receiver adapter URL address as Address Type

Hi All,
If some one who has tried HTTPS communication using HTTP receiver adapter using URL address as Address type can you please guide me what are the steps need to be done.
Note : Address type is a parameter in HTTP adapter setup .
Regards,
Reddy

Hi,
Check this,
Configurations in Integration Directory
The plain HTTP adapter gives the receiver system the following specifications:
 Specifications for addressing using a URL address:
Target host, service number, and path prefix including query string:
http://<hostname:port>/<path>?<query-string>
You can identify the target host (HTTP port) of a SAP Web Application Server using
the
ICM monitor
Host and port of the HTTP proxy (optional if there is a firewall between the plain
HTTP adapter and the receiver system)
Authentication data for the receiver system.
See also: transaction Display and Maintain RFC Destinations (SM59).
 Specifications for addressing using an HTTP destination:
HTTP destination
 Parameters from the communication channel for technical routing
Content type (the entry text/XML is expected as default)
Specifies the format that the message contents (the payload) should have.
Optional header fields for the receiver-specific protocol
Attributes for the query string
1. Sender party
2. Sender service
3. Receiver Interface
4. Message ID
5. Quality of service
6. Queue ID
All attributes are selected except for the queue ID. If you do not want a value to be
transferred to the receiver, deselect it. The queue ID is only required if the quality of
service is EOIO.
Specifications for payload manipulation
XML code (default UFT-8)
Specifies the character set.
URL escaping
Presents the XML in a URL-enabled format. Special characters that could be
interpreted as control characters are replaced with escape characters (masked).
Prolog
Enhances the payload for particular servers (optional, see below).
Epilog
Enhances the payload for particular servers (optional, see below).
Enhancing the Payload
Regards
Seshagiri

Schedule HTTP receiver adapter

Hi!
I want to schedule http receiver adapter to run at specified times, instead of triggering a whole end-to-end process. Possible?
I have searched all over, but nothing. Is there any background job in PI that I can schedule?
Thanks!

Hi Marianne,
I never yet tested with a HTTP Receiver adapter but yes it think it's possible (just try): I think you can use the standard scheduler of PI called "Availibilty-time Planning".
RWB > Component Monitoring > Display ALL > Adapter Engine > Communication Channel Monitoring > Availibilty-time Planning.
or directly this URL: http://<host>:<port50000>/mdt/channelschedulingservlet
Define your scheduling by precising dates / frequency / days and option "For Duration = 0 hour" to avoid a polling. Then add your CC receiver to this scheduling.
Maybe you need to put also the option "Manually" for the Control Data of your CC under :
RWB > Component Monitoring > Display ALL > Adapter Engine > Communication Channel Monitoring
Regards.
Mickael
P.S: the time I open my PI and check, Ravi suggest you the same idea...
Edited by: Mickael Huchet on Apr 23, 2009 1:47 PM

Plain HTTP debugging / Monitoring

Hi,
I am developing an asynchronous scenario where I am sending XML Data using plain HTTP receiver communication channel using POST. Can anybody tell me How to monitor HTTP channels it is part of Integration Engine? Where can I see all the messages went through it? Whether it is delivered to Target system from XI or not etc? If any trouble then How do i know that?
Any help will be appreciated.
Thanks.
-Adrean.

hi,
check out this page for ICF (IE ) trace and how to turn it on
http://help.sap.com/saphelp_webas620/helpdata/en/2d/64d041e74911d6b2e400508b6b8a93/content.htm
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>

Https health monitor not working on ACE.

Hello Guys,
Hope you are all doing well, i need some help in setting up my https health monitor for real servers.
I am configuring it on ACE appliance 4710 but the probe appears failing.
The VIP is listening on port 443 and 8080, the cert is not uploaded to ACE but eventually it will be on ACE so SSL will terminate on ACE but not at the minute.
The user don't want to enable port 80 on server so will need https health probe configuring. Following is my config for https health probe but it is failing.
probe https SSDSD-ServerAvailability-443
interval 5
passdetect interval 5
ssl version all
request method head url //ssdsd/servlet/SDLogin
expect status 200 200
As per my knowledge https is also an http probe but encrypted. Please see the detailed output below and let me know if i am missing anything.
probe       : SSDSD-ServerAvailability-443
type        : HTTPS
state       : ACTIVE
description :
   port      : 443          address   : 0.0.0.0
   addr type : -            interval : 5       pass intvl : 5
   pass count: 3            fail count: 3       recv timeout: 10
   SSL version      : All
   SSL cipher       : RSA_ANY
   http method      : HEAD
   http url         : //ssdsd/servlet/SDLogin
   conn termination : GRACEFUL
   expect offset    : 0         , open timeout     : 1
   regex cache-len : 0
   expect regex     : -
   send data        : -
                ------------------ probe results ------------------
   associations     ip-address         port porttype probes failed passed health
   ------------ ----------------------+----+--------+------+------+------+------
   serverfarm : SSDSD_SF
     real      : SSDSD-AL2[0]
                        192.168.225.26 443 VIP     48611 1834   46777 FAILED
   Socket state        : CLOSED
   No. Passed states   : 1         No. Failed states : 2
   No. Probes skipped : 1         Last status code : 302
   No. Out of Sockets : 0         No. Internal error: 0
   Last disconnect err : Received invalid status code
   Last probe time     : Mon Nov 11 04:05:10 2013
   Last fail time      : Mon Nov 11 02:10:00 2013
   Last active time    : Fri Nov 8 09:09:31 2013
                        192.168.225.26 8080 VIP     48613 48613 0      FAILED
   Socket state        : CLOSED
   No. Passed states   : 0         No. Failed states : 1
   No. Probes skipped : 0         Last status code : 0
   No. Out of Sockets : 0         No. Internal error: 0
   Last disconnect err : Connection reset by server
   Last probe time     : Mon Nov 11 04:05:14 2013
   Last fail time      : Fri Nov 8 08:34:10 2013
   Last active time    : Never
     real      : SSDSD-AL3[0]
                        192.168.225.27 443 VIP     48612 1817   46795 FAILED
   Socket state        : CLOSED
   No. Passed states   : 1         No. Failed states : 2
   No. Probes skipped : 0         Last status code : 302
   No. Out of Sockets : 0         No. Internal error: 0
   Last disconnect err : Received invalid status code
   Last probe time     : Mon Nov 11 04:05:10 2013
   Last fail time      : Mon Nov 11 02:10:00 2013
   Last active time    : Fri Nov 8 09:09:31 2013
                        192.168.225.27 8080 VIP     48613 48613 0      FAILED
   Socket state        : CLOSED
   No. Passed states   : 0         No. Failed states : 1
   No. Probes skipped : 0         Last status code : 0
   No. Out of Sockets : 0         No. Internal error: 0
   Last disconnect err : Connection reset by server
   Last probe time     : Mon Nov 11 04:05:12 2013
   Last fail time      : Fri Nov 8 08:34:08 2013
   Last active time    : Never
PHH104-N3-ACE-1/N3#
I am confused with the last status code which shows 302 any help from your side will be a life line for me.
Regards,
Amjad Hashim.

Hi Amjad,
I see the last disconnect err: "Received invalid status code" which means that ACE is not getting what is expected (code 200) for it to mark the server as passed.
Also, i see you have configured url "request method head url //ssdsd/servlet/SDLogin", why are you using two slashes "//", can you try with only one?
Also, if you configure probe on TCP PORT 443 does it pass? I see last disconnect err: connection reset by server as well and that could be due to the fact that service was there on server. Looks unlikely since above probes failed due to wrong status code which means that SSL handshake happened.
You can take a pcap on server as well as ACE to see what is going on. You might need to use private key to decrypt the captures if the failure is after SSL handshake has completed to see what status code server is sending. You can also use TCP 443 based probe as workaround till you can arrange pcaps and figure out what is wrong.
Regards,
Kanwal

PI 7.11 - Sync HTTP receiver adapter with response XML file

Hi
We have a File to HTTP scenario in which we need a sync HTTP interface. We send a file to the HTTP address and receive a XML acknowledge. As I read in this forum: sync HTTP interfaces are not possible with the "standard" HTTP adapter. So I found an entry which recommended to use the SOAP adapter instead.
I configured it:
- Do Not Use SOAP envelope
- modules: RequestResponseBeans, CallSapAdapter, ResponseOneWayBean
If i use this scenario, i get following error in the RWB - Message Display Tool:
Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException: while trying to invoke the method com.sap.engine.interfaces.messaging.api.Message.getMessageId() of an object loaded from local variable 'message1'.
I testet this scenario using CURL and it worked properly. Should this kind of scenario work with the SOAP adapter or do I need to buy/develop an own adapter? Is in NW7.3 possible to configure sync HTTP scenarios?
Thanks in advance
Michael

Hi
actually i use a simple HTTP receiver CC with the setting "XI Payload in HTTP Body" to send a XML datafile to a webpage (java servlet). This part works fine by now. But, this servlet would also send back a status information to the state of the received datafile, which I like to catch.
e.g. HTTP response from the servlet (catched using CURL):
HTTP/1.0 403 Forbidden
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548)/Tomcat-5.5
Set-Cookie: JSESSIONID=OALHMomjR9TVgIATi8SrPQ**.ajp13_ls_1; Path=/ls
Content-Type: text/xml
Date: Tue, 06 Mar 2012 16:19:56 GMT
X-Cache: MISS from proxy.xxxx.com
Via: 1.0 proxy.xxxx.com:xxxx (http_scan/4.0.2.6.19)
Proxy-Connection: close
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><!DOCTYPE transportordersfromls [ <!ELEMENT transportordersfromls (userid, clntid, msgid, (transportorderfromls+ | error))> <!ATTLIST transportordersfromls vers CDATA #REQUIRED> <!ELEMENT userid (#PCDATA)> <!ELEMENT clntid (#PCDATA)> <!ELEMENT msgid (#PCDATA)> <!ELEMENT transportorderfromls (refid, status)> <!ELEMENT refid (#PCDATA)> <!ELEMENT status (ok | error+)> <!ELEMENT ok EMPTY> <!ELEMENT error EMPTY> <!ATTLIST error reason (XMLError | SystemNotAvailable | ApplicationError | OTHER) #REQUIRED message CDATA #REQUIRED> ]>
<transportordersfromls vers="1.0">
    <userid/>
    <clntid>XXXXX</clntid>
    <msgid>0</msgid>
    <error reason="OTHER" message="Access denied"/>
</transportordersfromls>
Michael

Assign a dynamic value to a field in HTTP receiver header without IR part

hi experts,
I am doing a scenario in which i am to add a header field in http receiver, whose value will vary for each transaction. and the value will be same as sender file name.
But this all I am to do without doing Repository part.(i.e. No message interface and no mapping)
Is it possible? If yes help me out.
"Useful effort will be appreciated"....
Thanks

Hi Jaideep,
Hpoe the below link will help you.
Dynamic Configuration of Some Communication Channel Parameters using Message Mapping
Regards,
Leela

Not able to see 'Adapter specific' indicator in http receiver comm. channel

I am not seeing the Adapter Specific Message attributes indicator in http receiver adapter where one can set a dynamic URL. Anybody any idea? Thanks.

I have a fixed URL except that it should be formed with https instead of http. I guess the default http is used as there is no where in the communication channel to select https. I am able to invoke the https url through browser but through http receiver adapter, I get error 'http client code 110 reason'. I see in other blogs that this is due to https not enabled in the J2EE engine. But for outbound why should that matter? As long as the target URL is set to accept https, I should be able to sent the message as long as the URL gets formulated starting with https. If it was SOAP adapter, the entire URL can be entered so no issue, but with http adapter is there a way to specify entire URL including the https:// ? Thanks.

HTTP Receiver Adapter - delete ?xml version="1.0" encoding="UTF-8"?

Hi,
Is it possible to delete the part below when sending an HTTP request through HTTP receiver adapter without any java/abap/xslt mapping?
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_SELL xmlns:ns0="http://test.com/Sell">
Thanks
Arman

Hi,
<?xml version="1.0" encoding="UTF-8"?>
Specifies that the given message is xml
<ns0:MT_SELL xmlns:ns0="http://test.com/Sell">
Specifies its a MessageType of the payload, without this that message is not identifies and is not processed. Its manditory to have these. Other wise error will raise.
Regards,
Prasanna

Manipulate the URL in HTTP receiver adapter possible?

hello together,
i have an HTTP receiver adapter. To the parameters which i can tick in XI as default (sender party, sender service, ....) i want to add some parameters too.
who can i do that? i have read the weblog from william li. i tried to change the parameter link the comments at the end of the blog (see kurt rasmussen) but nothing happend..... the parameters are not available....
can somebody help me?
thanks a lot
alex

hello michal,
yes, i did. i took the information from http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm and tried to put some special information to URL. nothing to see.
is it mandatory to use a mapping to fill the URL parameter fields, isn't it??
i am using a port sniffer to see the URL and the fields (parameters) in it.
thanks a lot.
alex

HTTP Receiver interface returns with error code 110

Hi All,
We are posting the document from XI to a external server as HTTPS request.
We are able to sucessfully post the request to external server using HTTP destination as address type but not able to post sucessfully with URL as address type.
Here goes the details -
We are able to post the HTTPS request successfully on the external server using the HTTP destination as address type in HTTP receiver adapter setup.
When we setup address type as HTTP destination , we need to provide the following details -
IN SM59 , Connection type G
Target Host : host name ( with out "https://" as prefix)
Service No : 443
Path prefix : query string
SSL : Active
Certificate : Select the certifacte from the client certificate list.
We can post the request to external server using URL as address type in HTTP receiver adapter setup.
When we setup address type as URL , we need to provide the following details -
Address type : URL Address
Target Host : host name ( with out "https://" as prefix)
Service Number : 443 ( HTTPS port setup on XI)
Path : query string.
When we post the same request as we did with HTTP destination as Address type , we are getting a HTTP response code as failure HTTP response code 110
Please find the details about the return code -
If a cache returns a stale response, either because of a max-stale directive on a request, or because the cache is configured to override the expiration time of a response, the cache MUST attach a Warning header to the stale response, using Warning 110 (Response is stale).
110 Response is stale
MUST be included whenever the returned response is stale.
Please find the error message from SXMB_MONI
<?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>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 110 reason</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Please let me know if some one has faced this issue.
Regards,
Reddy
Edited by: Nanda kishore Reddy Narapu Reddy on Mar 11, 2008 12:35 PM

Hi All,
Is some one can confirm that - We can use HTTPS with Address type as URL address in HTTP receiver adapter setup.
I can confirm that using HTTP destination as Address type in HTTP receiver adapter setup we can attain HTTPS communication with external server.
If some one who has tried HTTPS communication using HTTP receiver adapter using URL address as Address type can guide me what are the steps need to be done.
Address type is a parameter in HTTP adapter setup .
Regards,
Reddy

Http Receiver Monitoring

Similar Messages

Maybe you are looking for