Customize the HTTP RECEIVER URL

Hi all,
With AS2, all inbound messages are received at the following URL /b2b/httpReceiver.
Is it possible to customize this URL ?
Thanks in advance.
Sebastien

Hi Sebastien,
All the inbound http msgs can be received via following two URLs.
/b2b/httpReceiver
/b2b/transportServlet
If you have a specific use case, please raise an SR or talk to our PM KrishnaPrem ([email protected])

Similar Messages

HTTP Receiver URL

Hi,
I am doing a HTTP to HTTP scenario. my requirement is to send a value randomly from HTTP sender CC to the Receiver HTTP CC URL. let me more precise, i want to send a parameter to the target URL
for example the target URL http://localhost:8001/echo.jsp?echo=x, i want to send a value x=10 from the Sender HTTP CC.
Can some help me how can i achieve it.
Thanks
Shaik

Azias,
Select ASMA.Check URL Parameters indicator and give the URL values.
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
Read this it might be helpful.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/66dadc6e-0a01-0010-9ea9-bb6d8ca48cc8
Best regards,
raj.

In HTTP receiver, how to make a dynamic query string in URL

Hi,
I have a scenario where after a map we get an XML output as shown below
<FUNLOC>000010038</FUNLOC>
<SECONDARY_KEY>0000010038</SECONDARY_KEY>
<SOURCE>SAP customer</SOURCE>
<NAME>NAME NAME12 NAME13</NAME>.
Now what i need that my HTTP receiver URL should add these tags as
FUNLOC=000010038&SECONDARY_KEY=0000010038&SOURCE=SAP customer&NAME=NAME NAME12 NAME13.
Can any one help me out in step by step process to archive this.
This will be a great help from you.
Thanks in advance,
Smita

Hi Smita,
Check these threads You can find the solution there.
https://forums.sdn.sap.com/click.jspa?searchID=5694804&messageID=3189288
https://forums.sdn.sap.com/click.jspa?searchID=5694804&messageID=3717577
Regards,
Sreenivas

HTTP Receiver Adapter : Dynamic URL

Hi,
I have a scenario where I wish to build a dynamic URL for the HTTP Receiver Adapter. The URL will contain a customer number which is present in the mapping.
The help seems to suggest that this is possible :
<i>If you want to use an HTTP destination or URL set by the mapping, set the URL or HTTP Destination indicator. (The indicator displayed depends on the Addressing Type you selected above). If you set the indicator, the URL or HTTP destination set dynamically is called by HTTP.
If the message header does not contain the URL or the HTTP destination, and you have set the Fail If Adapter-Specific Message Attributes Missing indicator, the XI message is set to status System Error. If you do not set the indicator, the URL or HTTP destination defined statically in the communication channel is used.</i>
However, it is not very clear where the URL needs to be set dynamically.
Does anyone know how to achieve this ?
Cheers
Colin.

hello to all,
We have a unique issue with one of our customers that is limited to 100 character URL. The current url is http://mycompany.com/sap/xi/adapter_plain?namespace=urn%3Agoodyear%2Ecom%3AAIT%3AInventoryCheck&interface=AITInventoryCheck_Abs&service=HTTP_AIT_InvChk&QOS=BE&sap-client=010&sap-language=EN
Is there a way to have a URL like
http://mycompany.com/sap/xi/adapter_plain?namespace=urn%3Agoodyear%2Ecom%3AAIT%3AInventoryCheck
and then somewhere in the process add... &interface=AITInventoryCheck_Abs&service=HTTP_AIT_InvChk&QOS=BE&sap-client=010&sap-language=EN
So the data comes to an F5 through the DMZ to the SAP webdispatcher then to the SAP XI system.
Any ideas if this is possible or how you could start with a shorter URL?
Thanks,
Dede

Error while creating the HTTP client with destination GB_DPSRetrieve

Hi All,
It is an interface R/3 -->XI --> HTTP ( proxy to HTTP ).
Please find the error log below and throw some light why the HTTP adapter is getting error -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <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>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>DC98499F-7E42-74F1-A41F-0017A4107EE6</SAP:MessageId>
<SAP:RefToMessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:RefToMessageId>
<SAP:TimeSent>2007-11-21T15:51:30Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">GovernmentGateway</SAP:Party>
<SAP:Service>GGMailbox</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>SAP_DEV_ERP2005</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFI_DPSretrieve</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</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>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
<SAP:P1>GB_DPSRetrieve</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while creating the HTTP client with destination GB_DPSRetrieve</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
- <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-21T15:51:30Z" wasRead="false">
<SAP:Engine type="BS">SAP_DEV_ERP2005</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS">is.00.lbsth-tb1ci</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20071121</SAP:Date>
<SAP:Time>155130</SAP:Time>
<SAP:Host>lbsth-tb1ci</SAP:Host>
<SAP:SystemId>XIS</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>023</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>PISUPER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
<SAP:QIdInternal />
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID" />
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>0</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>2918</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>0</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
<SAP:InterfaceAction>INIT</SAP:InterfaceAction>
<SAP:RandomNumber>15</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Receiver_Agreement_GUID>24422A5646443F8E9D975D57A3EE8162</SAP:Receiver_Agreement_GUID>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.5</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.656</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <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:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">SystemError message generated. Guid: DC98499F7E4274F1A41F0017A4107EE6</Trace>
<Trace level="1" type="T">Error during execution of message : DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
<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" />
</SOAP:Body>
</SOAP:Envelope>
Regards,
Kishore

Hi,
In the HTTP Receiver what is the Addressing Type used ? (URL Address or HTTP Destination).
If its URL Addressing Type, check if right Authentication Type is used with valid values and for HTTP Addressing Type check this HTTP Client Create Error, it could be helpful.
Also check if the Target system can be reached from the XI server to validate the configuration parameters.
Regards,
S.Santhosh Kumar

HTTP RECEIVER QUERY

hello everyone,
I have to develop a synchronous scenario, SOAP Sender to HTTP Receiver.
Soap sender will be passing suppose 2 fields Name and Employeeid and the Http receiver will be replying back the
response with entire employee details (name, id, address, dateofbirth, etc).
Http receiver has to be accessed via a URL like
https://abc.com/test/servlet/ServletInterface?command=getdetails&emp_name=<Name>&emp_id=<Employeeid>
This is an https request, henc an RFC destination needs to be configured in XI and SSL has to be activated but how will i add the parameters Name and Employeeid to the URL mentioned in the RFC destination.
i went through many blogs on SDN, but i could not figure out how to append the URL mentioned in the Http Destination. Is it possible to do dynamic configuration with SSL enabled.
i tried passing URL https://abc.com/test/servlet/ServletInterface?command=getdetails in the HttpDestination and also configured a mapping for dynamic configuration but with no success.
please let me know if i am on the right track. if not please suggest.
thanks in advance.
Edited by: praveen kalwa on Feb 22, 2008 1:33 PM

Hi,
XI supports only PUT method of http request. While adding parameters to the addr string is considered as a GET method.
Refer following blog in this regard.
/people/amol.joshi2/blog/2006/06/28/must-fire-a-http-get-from-xi---try-this
-Kavita

Advanced HTTP Receiver Configuration

Hi Experts,
In my Business Scenario I am using the HTTP Receiver Adapter with "Additional Query String Attributes" for adding up the "MessageID" in the HTTP Header(I am not sure whether it will be added there).. and the adapter sends the HTTP data to a URL, where there is a JSP program which takes out the Message ID and stores the data with ID as key in a dataBase.
My Quesiton is - Is their any chance to override the MessageID in the HTTP Header?
And also please refer some documents where can I find the detailed information on "HeaderFields" section in Receiver HTTP adapter... and also how can I see the HTTP Header data which is generated by XI system...
Thanx in advance..

Hi Yuvaraj
Is their any chance to override the MessageID in the HTTP Header?
You can using the Header fields. Add values here
how can I see the HTTP Header data which is generated by XI system..
You can go to SMICM change the trace level to 3 and you can see messages going out of PI.
Thanks
Gaurav

HTTP receiver adapter: dynamic configuration

I was told that if I have a URL and some parameters, I can use a sync HTTP receiver adapter to call a site.
I know this can be done using some kind of dynamic configuration, but I am not familiar with this adapter.
The most important question here is that I need to know if this can be done throw PI, so my question is:
Is there a parameter limit in the HTTP adapter? If so, what is the quantity of parameters that I can give to the adapter?

for the ASMA parameters you can use for the HTTP receiver adapter check
Configuring the Receiver Plain HTTP Adapter - http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/frameset.htm

HTTP Receiver To HTTP Sender

Hello,
i have the following scenario:
System A --> [XI1 -> http-receiver] -
> [ http-sender --> XI2]
So i send an IDoc from A to my XI1 and then i want to send it with the http-receiver to
the http-sender of an other XI2.
In my http-receiver i want to use a rfc-connection.
The adress of the http sender is something like:
http://xisystem:8000/sap/xi/adapter_plain?interface=INVOIC.INVOIC01&service=BS_HTTP_SENDER...
My question is how can i configure the parameters like 'service' from the sender in the http-receiver.
Thanks and regards
Patrick

Hi Patrick,
as URL parameter of the http-address, you have it there: sercice=BS_HTTP_SENDER. You need as well parameter interface, namespace and QOS=EO. The rfc destination will give you a warning for that - ignore it.
Regards,
Udo

HTTP Receiver Configuration

Hi Experts,
In my Business Scenario I am using the HTTP Receiver Adapter with "Additional Query String Attributes" for adding up the "MessageID" in the HTTP Header(I am not sure whether it will be added there).. and the adapter sends the HTTP data to a URL, where there is a JSP program which takes out the Message ID and stores the data with ID as key in a dataBase.
My Quesiton is - Is their any chance to override the MessageID in the HTTP Header?
And also please refer some documents where can I find the detailed information on "HeaderFields" section in Receiver HTTP adapter... and also how can I see the HTTP Header data which is generated by XI system...
Thanx in advance..

hi
u can see the Header data in SXMB_MONI transaction.
select the IDOC and u can see the complete IDOC information with payloads ,header information,error information for both Inbound and outbound.

Changing HTTP-Parameters for HTTP Receiver Channel

Dear all,
we have a partner we send files to using the simple HTTP adapter.
We have different types of messages (interfaces) we send to the partner.
Our partner expects the message type as a parameter of the URL. Such as http://xxx:000/xxx?msgtype=outbound
In turn, the "outbound" could also be "inbound" - depending on the message type.
I want to avoid using to services with two adapters.
Thus, my question to you: Do you have an idea how I could manipulate the parameter's value?
Thanks in advance,
Helge

Hi Helge,
if you have Sp14 and above you can try setting the url
dynamically in the mapping using Adapter-Specific Message Attributes in the http receiver channel:
http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
this way it should be no problem to change it
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

HTTP sender url parameters

Hi all,
Can we configure the HTTP sender URL with multiple interfaces ?
I mean as far as i know the URL can have only one interface name and namespace.
In our landscape we have 4 sender interfaces which gets input from a single URL through HTTP POST
I need to extract the individual Interfaces from the URL and route the messages accordingly
Any help in this is highly appreciated
Thanks
Keerthi

Hi,
I don't this it is very much achievable in PI. What ever you send from from the http url (using interface name and namespace), it comes to IE. So as said by the former reply, you have to receive the message from the http post, and later you can split it using and send to corresponding receivers.
OR
if you dont want to do that..then create four different scenarios..sender will be the common message and target will bhe the required message (from the four). and accordingly you can configure them in ID. so in ESR there will be four different Operation Mapping and in ID there will be four different configuration.
All solution depends on your business requrement Hope it may help you.
Regards,
Farooq

Is it possible to debug "CL_HTTP_PLAIN_OUTBOUND" FROM HTTP RECEIVER ADAPTER

Hi All,
In my PI interface the data from R/3 ( using abap proxy ) is getting posted on a external server using HTTP receiver adapter .
I assume that it triggers this class when you run the HTTP receiver adapter -CL_HTTP_PLAIN_OUTBOUND
Please let me know how can i enable debugging for triggering this class.
Please let me know the steps to debug this class by triggereing from SAP PI system ( when we run the interface on PI system )
Regards,
Reddy

Hi ,
i am not sure about this,i wolukd prefer developing JAVA Proxy or File Adapter . try this code it read the data from website, try in you stand alone application,it is able to read or not.
you will face two problems,you have to convert CSC file to XML it is not possible in HTTP Adapter,
import java.lang.*;
import java.util.*;
import java.net.*;
import java.io.*;
class URL2AC
        public static void main(String args[]) {
       try {
          URL url = new URL("http://www.XXXXXXX.com/raj.txt");
          URLConnection uc = url.openConnection();
          BufferedReader in = new BufferedReader(new InputStreamReader(uc.getInputStream()));
          while (in.readLine()!=null)
               System.out.println(in.readLine());
       catch(Exception e) {
          e.printStackTrace();
Regards,
Raj

RFC TO HTTP receiver scenario.Adding file name to HTTP receiver

Hi All,
Scenario is ZBAPI ->XI-> HTTP conncetivity to EXternal Partners .
ZBAPI sends the Partner data informtaion to XI . I need to create a Partnerdata xml in XI and pass it to HTTP Connectivity (Certificates ) to External Partners
Connectivity is working but I need to add the time stamp to the Partner data xml in the HTTP Receiver .
I dont get the time stamp in ZBAPI
I checked many blogs to create UDF of getfilename, dynamic configuration , but here there is no FTP sender channel .
Can someone help me in giving ideas as hope to assign the time stamp in runtime to HTTPS Receiver Channel .
Thank you ,
Best Regards,
Vara

Hi Vara,
In your question you actually mentioned three different communication methods (HTTP, HTTPS and FTP), but only one of them can really work with files and it is the FTP adapter. Moreover, what you need is the Receiver FTP Communication Channel, not the Sender one (as you need to deliver your message to an external system, not to collect it from there). What you need to do is find your Receiver Communication Channel, go to Advanced tab and mark "Use Adapter-Specific Message Attributes", as well as the File Name (that appears once you mark the first one). Then, in your message mapping, you just put the current timestamp to the respective dynamic configuration parameter. Find an example of how to make the whole change [here|http://www.****************/Tips/XI/ASMA/Index.htm].
However, if I misunderstood you and you need to use the current timestamp in the message body instead of the file name, it will be even simpler. In this case, just go to your Message Mapping and in the target field, put the "currentDate" function from the "Date" group, then double click on it, click the "extended view" button and put your expected date and time format.
Hope this helps,
Grzegorz

HTTP-Receiver: Code page conversion error from UTF-8 to ISO-8859-1

Hello experts,
In one of our interfaces we are using the payload manipulation of the HTTP receiver channel to change the payload code page from UTF-8 to ISO-8859-1. And from time to time we are facing the following error:
u201CCode page conversion error UTF-8 from system code page to code page ISO-8859-1u201D
Iu2019m quite sure that this error occurs because of non-ISO-8859-1 characters in the processed message. And here comes my question:
Is it possible to change the error behaviour of the code page converter, so that the error will be ignored?
Perhaps the converter could replace the disruptive character with e.g. u201C#u201D?
Thank you in advance.
Best regards,
Thomas

Hello.
I'm not 100% sure if this will help, but it's a good Reading material on the subject (:
[How to Work with Character Encodings in Process Integration (NW7.0)|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42]
The part of the XSLT / Java mapping might come in handy in your situation.
you can check for problematic chars in the code.
Good luck,
Imanuel Rahamim.

Customize the HTTP RECEIVER URL

Similar Messages

Maybe you are looking for