SM59, Type G connection; PathPrefix problem; 255 characters exceeded

[Former Member]

Hi All,

I have created an ABAP/RFC Destination in sm59, Type G to connect to an external server.

The server to which i am posting is a 322 character URL.

/invoke/cpq_Std_Xcbl.flow/acceptXcblPoRequest?postBack=http://<ServerName>:60000/sap/xi/adapter_plain?namespace=http%3A//abcd.org/xi/pktest&interface=MI_OUT_PurchaseOrderResponse_xCBL2x&service=PKSELLSID&party=PKWEBSITE1&agency=&scheme=&QOS=EO&sap-user=xiappluser&sap-password=XXXXXXXX&sap-client=100&sap-language=EN

So i am not able to mention the complete URL in "PathPrefix". Its accepting only 256characters.

/invoke/cpq_Std_Xcbl.flow/acceptXcblPoRequest?postBack=http://<ServerName>:60000/sap/xi/adapter_plain?namespace=http%3A//abc.org/xi/pktest&interface=MI_OUT_PurchaseOrderResponse_xCBL2x&service=PKSELLSID&party=PKWEBSITE1&agency=&scheme=&QOS=EO&sap-user=x

How can i mention the complete URL in path prefix..?

Regards,

Siva Maranani

[Former Member · Accepted solution]

Hi,

Are you using a HTTP Receiver adapter to post this ?

If yes, you can make use of the Prolog & Epilog to achieve this.

in the RFC destination, in path prefix, enter "/invoke/cpq_Std_Xcbl.flow/acceptXcblPoRequest" ...

in the comm. channel to be used enter "postBack=http://<ServerName>:60000/sap/xi/adapter_plain?namespace=http%3A//abcd.org/xi/pktest&interface=MI_OUT_PurchaseOrderResponse_xCBL2x&service=PKSELLSID&party=PKWEBSITE1&agency=&scheme=&QOS=EO&sap-user=xiappluser&sap-password=XXXXXXXX&sap-client=100&sap-language=EN" in the PROLOG field.

the http body is made like <prolog-data>payload<epilog-data>...These values will be available to the target application via the http body and not the query string..what i mean is if the application is doing something similar to a request.getParameter(), then it would work....

check out the HTTP adapter help also to see details on prolog & epilog...(see the section "enhancing the payload")

http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/frameset.htm

Thanks & Regards,

Renjith

[Former Member]

Hi,

i tried ur suggestions.

But as HTTPS is being used to communicate with external system, and HTTPS was not enabled on JAVA Stack, it was throwing Client Attribute error.

I think if HTTS was enabled on Java Stack, this would have worked.

Anyhow thanks for your timely help.

I also solved my problem. I removed the unnecessary parameters like agency, schema and shortened the Interface names to least possible length(1 or 2 chars for each). It had then come to 220 char length.

Cheers,

Siva Maranani