Definition of SRM Backend URL when calling a shop

[Former Member]

Hi,

we installed the SRM portal and SRM 7.0 Backend on a server with full qualified host name "internal.server.int". The portal and the backend are accessed by the customer (internal network) with URLs "srmportal.company.com" and "srmbackend.company.com". Most stuff works fine, but when calling an external shop, the application /sap/sapsrm/outbound_hdlr is being called with the hostname "internal.server.int" and not with srmbackend.company.com as it should be. Therefore SSO is not working and the user is being asked to logon with password and username. When accessing the portal with the original server ID, everything works fine.

We changed the parameters

gw/alternative_hostnames

icm/host_name_full

to "srmbackend.company.com" but still the application /sap/sapsrm/outbound_hdlr is being called wit the wrong URL.

Now my question is where the information of hostname and port is being taken from to call the application /sap/sapsrm/outbound_hdlr. Is it a profile parameter or customizing or...?

Thanks a lot for your help,

Fabian

[Jnouwen · Accepted solution]

Fabian,

The scenario you describe would normally require a reverse proxy (which could be a web dispatcher).

In the table HTTPURLLOC you than enter the addresses of the reverse proxy.

If you look up that table name in help.sap.com, you will find a load of information.

Succes !

[Former Member · Accepted solution]

Hi,

we changed the two parameters in the Catalog Call Structure:

BYPASS_INB_HANDLER X (Fixed Value)

BYPASS_OUTB_HANDLER X (Fixed Value)

Now it seems to work.

Thanks to all,

Fabian

[Jnouwen]

Did you set up web dispatchers for both ABAP and JAVA stacks ?

Did you add an entry in table HTTPURLLOC to translate into the 'external' address ?

Rgds

[Former Member]

Hi,

no, we don't have web dispatchers in place.

"Did you add an entry in table HTTPURLLOC to translate into the 'external' address?"

How exactly would that work?

Thanks,

Fabian