HTTP Receiver without charset in SP18

Hi,
I have a scenario, in which I am sending data to external server using HTTPS Receiver.
In configuration I have following values :
1) Content Type: multipart/mixed; boundary=BOUNDARY
2) XML Code ( charset) : UTF-8
With these settings XI message is going to external server.But external server is not processing the message correctly because it <i>expects XI message <b>without</b> "charset"</i> (XML Code configuration in XI)
In HTTP receiver configuration XML Code(charset) configuration is mandatory. I tried to put other charset values. But as external server expects messages without charset, it is not working.
BTW, this same communication channel was working OK when we had SP14. we recently had our system upgraded to SP19 and it stopped working. On researching found charset is the problem. I sent same payload to the external server using another HTTP client without charset and it is working ok.
Is there any way we can configure HTTPS Receiver ( in SP18 ),so that we can send payload to extenal server without charset (XML Code) value.
Any input/pointers will be greatly appreciated.
-Venu

Hi Venu,
Install note 1038911 in your system.
The note is not translated to english yet, but it should work anyway.
Regards
Stefan

Similar Messages

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

Is there any way to create a HTTP_AAE Receiver without a path in NW PO 7.31

Hi ,
Does anyone know how to create a HTTP_AAE Receiver without a path??
We are in a phase of migrating Interfaces from PI 7.1 to PO 7.31(Java Only).
For one of the Interface in PI 7.1 there is a RFC Destination for vendor communication through HTTPS connectivity :
TargetHost: IP Address
Post: value
Path Prefix: Blank
During migration requirment is to keep the Path field BLANK of the Communication Channel,however since PO has mandatory path field a "/" is been provided, because of which data post fails.
PI: https://IP:9443
PO: https://IP:9443/ (Since Path Prefix is mandatory)
As per my understanding The data is supposted to be posted directly to the IP (https://IP:9443) however it is getting posted to (https://IP:9443/) where the service is not available. For Reference attached relevant screenshots.
Is there any way to create a HTTP_AAE Receiver without a path. Need ardent support and suggestions
regarding this.
Regards
Riju

Hi,
For Service auto- PO from PR, you need to activate Automatic Purchase order creation for Service requisitions in ML91 t.code.
Note:
For material :automatic PO creation from PR, follow the steps.
1) Material Master purchasing view tick automatic PO check box
2) Vendor Master purchasing view tick automatic PO check box.
3) Maintain Source list for Vendor & Material.(ME01)
4) Maintain Purchase Info Record.(ME11)
5) Create a Purchase Requisition.(ME51)
6) Use T.Code: ME59 & execute for PR for vendor, you will be able to create automatic PO.
During creation of PR , select check box of Source Determination in the 1st screen of ME51
Ensure that Purchase Info Record should be there.
If you have more than one vendor then fixes only one vendor in source list.
Regards,
Biju K

How can I use my iPhone as a radio receiver without using internet?

How can I use my iPhone as a radio receiver without using internet?

Apple!!!! Please listen to your customers!!!!
http://finance.yahoo.com/news/Smartphone-Fans-Want-FM-iw-1184795842.html?x=0&.v= 1
Give us or make us pay for FM app already!!!!!
http://www.tomsguide.com/us/Apple-iPhone-iPod-FM-Receiver,news-4855.html

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

How to set HTTP header field "cookie" with http receiver adapter?

Hi,
I am using http receiver adapter (not axis) in a scenario. I could not set a parameter with key cookie in http header. Is there some kind of restriction to set it? I am able to set others like connection and create custom fields using ASMA and dynamic key configuration via UDF on mapping.
Could you please comment on, is cookie http parameter special or noneditable by PI's http adapter? I am looking for a solution without editing any abap code...
Regards,

I believe it is possible since axis adapter provides very same functionality. Let me summarize my scenario may be it helps:
I am trying to call series of webservice lets say in a BPM. First service (login service) will provide me with a session id (in http header with key Set-Cookie) then I will call another service which has that session id in its http header with key cookie then I am going to logout. So I am testing the second part now, but it doest let me send cookie http header parameter.
I hope I clarified a bit more my problem.
Regards,

Https for SOAP and HTTP Receiver adapters in PI 7.1

Hi,
We need HTTPS Transport protocol is required to send the message to receiver systems.
Currently we are using below procedures for https:
1) HTTP with SSL (= HTTPS) without client authentication
2) HTTP with SSL (= HTTPS) with client authentication
But client donu2019t want this procedure.
Here my question is How to enable the https Transport protocol in SOAP and HTTP Receiver adapters.

>>Here my question is How to enable the https Transport protocol in SOAP and HTTP Receiver adapters.
What I see is your client wants PI to send communication via HTTPS transport protocol. That means you have to apply for trusted certificate and import that certificate root node in Netweaver keystore.
Then change the transport protocol from http to https in soap and http receiver communication channel and communicate to client via certificate authentication.
Plenty of documents available in sdn about https certificate authentication. Please go through those links.
check this thread.. might be helpful
Client Certificate for PI authentication when Web Dispatcher terminates SSL

SOAP Receiver Success / HTTP Receiver Error

Hello,
we have to connect to a http server (HTTP with user authentication). I have tried both a HTTP receiver channel as well as a SOAP receiver channel (option "Do Not Use SOAP Envelope").
Connection using the SOAP receiver works without problem. If we switch to plain HTTP receiver (same connection details) we get the following error:
"HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED".
What could the reason for this? Probably related to the ABAP Stack?
Edited by: Florian Guppenberger on Jan 26, 2010 3:12 PM

Hi,
>>>What could the reason for this? Probably related to the ABAP Stack?
check the log on ABAP for RFC dest from SM59
there you might see some more info
BTW
does PI/XI have access to this http sever ? (no firewalls etc?)
Regards,
Michal Krawczyk

HTTPS Receiver CC - Prerequisites

Hello,
what are the prerequisites for configuring an HTTPS receiver communication channel? Do I necessarily need to import the server certificate beforehand or would "TEST CONNECTION" in SM59 work without an imported certificate?
Background is, that I get the error "ICM_HTTP_CONNECTION_FAILED". However I can ping the server using telnet, so there should not be a firewall issue. I thought that the "TEST CONNECTION" functionality in SM59 does the same - only pinging a server without using certificates. Is this not correct?
Are there any other things I have to consider? Could it also be that the cryptographic library is not installed? How can I check whether it is installed?
Thank you for your advice!

Hello,
thank you for your helpful answer. Now I have found the problem. in SM59 "HTTP Connections to External Server" I have set "Status of Secure Protocol" to Active and now it worked.
However I would prefer to configure the destination directly in the communication channel by using adressing type "URL". In that case however it still does not work. Is there anything else I have to set directly in the communication chanel so I can get the connection working?

HTTP receiver adaptor

Hi all,
   I am using HTTP receiver adaptor to connect to an external system.Here I have to pass an Idoc from SAP to one folder in the target host where the application is installed.
     My question is without using FTP adaptor(only with HTTP) can i send this Idoc to The folder in the target?
If yes , What should i give the "path" field in Receiver HTTP adapter? I tried giving the folder name, but it was throwign an error 400.
     I created connection G in XI.I put some xml file (KK.xml) as path there and tested the connection it was working fine. Could you please help me out with this?
Thanks
Kiran

Hi Kiran,
You are talking about saving a file in the target director using HTTP Receiver adapter... As per my knowledge it is not possible in a straight fwd. The target should be a web application (obviously) which should recieve the data/xml that HTTP adapter is sending and then should save it in the respective directory. XI HTTP adapter will not do that job for sure. When you use HTTP adapter in XI its job is to deliver the message to the given URL thats it. If XI need to save it as a file then its thru File NFS/FTP.
FYI :
HTTP - Hyper Text Transfer Protocol
This can carry only texts but not a file
FTP - File Transfer Protocol
This is used for transfering files.
If HTTP is mandatory in your scenarion, then then a wep programming to be done at the target end (ASP/ASP.NET/JSP/Servlets/etc..)
Thanks,
Prakash

Http == SOAP without envelope

Any comments on the assumption that SOAP is nothing but an enhancement of the HTTP protocol with an envelope? In other words what payload you can send using http receiver adapter, you can achieve the same using SOAP envelope without envelope with header?

Hi James,
These threads show you all the differences...
Difference between SOAP and Http Sender
HTPP Adatpter Vs Soap Adapter ????
confusion using HTTP Adapter and SOAP Adapter
Hope this solves ur query
cheers
Prashanth
P.S Please mark helpful answers

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

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.

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 without charset in SP18

Similar Messages

Maybe you are looking for