Need Information on FQDN

[Former Member]

Hi Experts,

I need some basic details on FQDN used by WDABAP.

please explain in basic terms.

Thanks in advance.

Gokul.N

[Former Member]

Hi Gokul,

Check this

Fully Qualified Domain Names (FQDN)

In Web Dynpro ABAP it is imperative that a client browser with a fully qualified domain name (FQDN) has access to the AS-ABAP. For this reason the full URL must be assigned to a Web Dynpro ABAP application when it is called. The URL must not be shortened (for instance, no domain specification).

The domain used must also satisfy the requirements of the cookie specification (see http://wp.netscape.com/newsref/std/cookie_spec.html).

To check the FQDN, in the Web Dynpro explorer in the ABAP development environment (SE80), choose the relevant Web Dynpro application from the navigation tree for your Web Dynpro component/interface, and check the URL in the administration data. Check whether the path details in field URL also contain the full domain and host name.

Note that neither IP addresses nor underscore characters are allowed in host names (see below).

More information: SAP Note 654982.

Purpose

FQDNs are necessary for the following reasons:

● One domain is required with which cookies can be set domain-wide, for instance, SSO2 cookies.

● Domain relaxation code is required for cross-frame JavaScript.

This is particularly important for Portal Integration (see below).

● In an HTTPS environment, client and server names must correspond to each other for certificates and for the SSL protocol.

Note that the domain in which the AS ABAP is run is not necessarily the FQDN used to access the AS ABAP from the browser. A typical example is an AS ABAP that runs both in the Intranet and in the Internet. In a case like thi,s the FQDN is determined by the position of the browser relative to the AS ABAP and not by the AS ABAP itself.

Configuration of Fully Qualified Domain Names

If the host name simply specifies the host and port but not the domain (including the extension), the shortened URL of a Web application looks like:

<schema>://<host name>:<port>/sap/...

Example:

http://pwdf0487:1080/sap/bc/webdynpro/sap/wdr_test_events

Whereas the full URL should look like:

<schema>://<host name>.<domain> <extension>:<port>/sap/...

Example:

http://pwdf0487.wdf.sap-ag.de:1080/sap/bc/webdynpro/sap/wdr_test_events

IP Addresses Not Supported

URLs that contain IP addresses are not supported.

<schema>://<IP address>:<port>/sap/...

Example:

http://10.21.81.0:1080/sap/bc/webdynpro/sap/xyz

The following notation is required:

<schema>://<host name>.<domain> <extension>:<port>/sap/...

Example:

http://hs0059i.wdf.sap.corp:1080/sap/bc/webdynpro/sap/xyz

To map IP addresses correctly, the following is required:

&#9679; A minimal form of DNS at the customer location with the name of the AS-ABAP and a mapping to an IP address.

&#9679; Alternatively, a pseudo AS-ABAP name can be used, and the HTTP proxy configured at the firewall in such a way that this URL is sent to the correct IP address.

&#9679; For smaller installations you can use the following quick solution:

Update the hosts file on each workstation. Insert the line 10.17.73.210 hostname.domain.ext into file \WINNT\system32\drivers\etc\hosts.

No Support for '_' in Host Names

The browser does not accept cookies if a host name contains the underscore character '_'.

Since Microsoft Internet Explorer 6.0 and MS Internet Explorer 5.5 including security patch MS01-055 cannot accept any domain names with underscore characters, session cookies cannot be saved. This will result in terminations when navigating within a Web application.

Example:

The development system is called dev_sys, and the quality security system, qsys. This means the fully qualified domain name is:

qsys.company.co.xx

The following notation is not accepted:

dev_sys.company.co.xx

qsys.my_company.co.xx

For this reason, host and domain names must never contain the underscore character, '_'.

Domain Restrictions in Accordance with the Cookie Specification

The portal must be started with a domain that complies with the domain specification of the Internet standard cookie specification. Otherwise the portal cannot create the MYSAPSSO2 cookie.

So that the browser can decide which servers a cookie can be sent to, the URL must contain the domain specification, since the decision is based on this information. In accordance with the Netscape cookie specification (available under http://wp.netscape.com/newsref/std/cookie_spec.html), cookies can be set for one domain only, and a domain must contain two or three dots (.) due to security restrictions. Each of the seven top level domains (.COM,.EDU,.NET,.ORG,.GOV,.MIL,.INT) must contain at least one further domain component (usually the name of the company or organization), amounting to two dots. Each domain with a different ending (this includes the top level domains for countries, such as UK, DE, FR, and so on) must consist of two further domain components, that is, these domains must contain at least three dots. For more information see the cookie specification.

Examples of valid domains:

&#9679; <host>.sap.com

Top level domain -> two domain components

&#9679; <host>.portal.sap.de

No top level domain -> three domain components

Some browsers (for instance, Microsoft Internet Explorer) are less strict and permit domains that violate the cookie specification rules listed above.

The Internet Explorer would allow the following domain:

<host>.sap.de

This is not a top level domain, yet it only has two domain components.

Same is available at

http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm

Regards

Sarath