Set FQDN in Logon Group

[Former Member]

Hi Gurus,

In SMLG - Maintain Logon Groups, is there possible to set fully qualified domain name (FQDN) instead of IP address to Logon Group?

This is because if I only set the Public IP for this Logon Group, internal user in LAN is not able to use this Logon Group to access R3.

Anyone has any idea? Please help.

Thanks,

HauChee

[Former Member]

You are assigning logon group to instance name rite ? I dont think IP address is mandatory ...

Thanks

Prince Jose

[Former Member]

Hi Prince Jose,

Thanks for fast response. Yes, i did assigned a logon group to 2 instances.

I have to put Public IP (e.g. 210.19.18.XX) for these 2 instances, so that external users from internet can access R3 via this logon group.

In this case, internal users from LAN are not able to access R3 using this logon group because LAN users cannot access Public IP from LAN (e.g. 192.168.XX.XX).

From my understanding, this can be resolved by using FQDN instead of IP address. So, i am looking for the way to set FQDN to instance attribute.

Do you have any idea?

Thanks,

HauChee

[Former Member]

Hi Chee,

If you set IP and host name in etc/host file, you can use the host name instead of IP address.

Regards,

Hari.

[Former Member]

Hi Hari,

Thanks for your suggestion. But it is not working for my case.

In SMLG, I can only set the IP address for instance attribute. Is there any way to set FQDN instead of IP address in SMLG? I cant find any possible fields to fill in FQDN value in SMLG.

Please help.

Thanks,

HauChee

[Former Member]

Hi,

Why don't you create 2 logon groups ?

One for the intranet users and one for the internet users ?

Then you'll be able to set the internet translated IP address in the logon group for external users.

Regards,

Olivier

[Former Member]

Hi Olivier,

Actually, my users will only use SAP Portal to single sign on to R3 system. I have created a system connector with load balancing (logon group) in Portal to connect to R3 system. Wingui is used to access R3 system in Portal using this system connector with load balancing.

This is working perfectly, when user using his/her laptop to access R3 system via Portal from internet/WAN.

When user back to the office and attachs his/her laptop to office LAN (same network as the R3 servers), SSO in Portal will fail as Wingui is trying to access Public IP in LAN.

So, I am thinking of if this Public IP can be replaced by FQDN, then this issue will gone. However, I have no idea how to set FQDN for instance attribute in logon group.

Any idea? Please help. Thanks.

Regards,

HauChee

[Former Member]

Hi Hau,

(Sorry if Hau is not your first name !)

It is not possible to enter a FDQN as the help is :

IP address

(Numeric) IP address of the application server. This should be specified only if the application host belonging to the instance has to be addressed from the frontend side using a different IP address than that used for communication within the application host. This could be the case if, for example, the communication from application host to application host uses a different network than that used for the communication from the frontend to application host

I think you need the 2 different saplogon groups AND you need to find a way from the portal to check if the laptop is connected internally or externally. The portal would then choose the right saplogon group :

Also, I don't really understand the need : I think it would be much nicer for your users to use directly sapgui when connected internally than webgui.

webgui, IMHO is just an acceptable way to work when not in house.

Regards,

Olivier