Special Case: Combination with the Logon Application

A URL configuration table often has to be used during the logon procedure.This is particularly important if a Web dispatcher is used that has configured various ports, and when the Logon Application must switch to HTTPS to guarantee the secure transfer of passwords.

The logon application runs in two different clients, one runs in client 000 as user SAPSYS until the logon has been successfully completed, and the other runs in the designated client with the logged on user. During the first part of the logon the logon application finds Table HTTPURLLOC in client 000. Therefore, it is essential that all entries are duplicated in client 000 when the logon application is in use.

Starting from the second scenario table HTTPURLLOC looks like:

HTTPURLLOC

MANDT

SORT_KEY

PROTOCOL

APPL

HOST

PORT

000

010

HTTP

*

WWW.SAP.COM

80

000

011

HTTPS

*

WWW.SAP.COM

443

100

010

HTTP

*

WWW.SAP.COM

80

100

011

HTTPS

*

WWW.SAP.COM

443

If more than one client is active on the same computer with different Web dispatchers, all entries of the various clients must still be duplicated in client 000.In this case the host header filters the entries to be used.