SRM6.0: Changing Catalog Technical Settings from POST to GET

[Former Member]

SRM Guru's,

I'm trying to change the method used to connect to an external catalog from the default POST to a GET method. I've checked the "USE HTTP GET to Call Web Service" checkbox, however the connection still fails. There are two catalogs and when using httpwatch to look at the data, indeed it is still doing a POST to those external catalogs. Am I missing a something or is that checkbox all that should be required?

thanks,

[lisa_sheil · Accepted solution]

Hi,

This BSP service receives the call structure from LAUNCH_CATALOG method

(by GET or POST depending upon SPRO settings) but then posts it to the

catalog. So if a catalog needs the call structure entries as GET method,

this BSP application can not be used.

So you need to disable the "Back To SRM Application" link.

To do that you need to use Outbound Handler instead of Catalog Wrapper

and then disable it through SPRO setting (Introducing

BYPASS_OUTB_HANDLER = X).

In that case you should not have the "Back To SRM Application" link

displayed, but the catalog will receive the call structure entries as

GET method.

In SRM 6.0 which runs inside portal environment, If a catalog is

configured in SPRO to work with GET, then the portal calculates the

length of the URL (Absolute URL of the catalog + the appended call

structures). If the length exceeds 1024 then automatically the data get

transferred to the catalog as POST instead of GET.

This is a feature of Portal and from SRM we can not change it.

So if the 3rd Party catalog is not working because the Parameters are

passed to them as POST instead of GET, then the correction needs to be

done from the Catalog Solution Provider to support POST, as this is the

more standard way of passsing parameters through Http request.

I hope this helps in regards to this issue.

Kind Regards,

Lisa

[Former Member · Accepted solution]

Yes, I got this already, but awarding full points as this solution should help someone else.