URL of a Web Dynpro Application 
The URL of a Web Dynpro application is automatically generated by the system. You find the URL of your application in the Web Dynpro Explorer on the Properties tab.
The URL of a Web Dynpro application has the following structure (default configuration), whereby the following formats are possible:
● SAP namespace
<schema>://<host>.<domain>.<extension>:<port>/sap/bc/webdynpro/<namespace>/<application name>
● Customer namespace
○ <schema>://<host>.<domain>.<extension>:<port>/abc/klm/xyz/<namespace>/webdynpro/<application name>
○ <schema>://<host>.<domain>.<extension>:<port>/namespace>/webdynpro/<application name>
<schema> stands for the URL schema (also known as protocol), which usually is the protocol http or https (if configured). Host is the name of the application server that should execute the application. Domain with the extension comprises several hosts under a common name and can either be an individual host or a network (see also Fully Qualified Domain and Host Names (FQDN/FQHN)). The port number can be omitted if the standard port 80 (http) or 443 (https) is used.
The namespace can be the standard namespace /SAP/ or customer namespaces (see below).
The application name is the name of the Web application as defined in the Web Dynpro explorer by the Web Dynpro component.
See also:
Calling a Web Dynpro
Application Using Parameters
Applications in the SAP Namespace
Web Dynpro
applications are stored in the ICF Internet service tree under the path
/sap/bc/webdynpro/<namespace>/<application
name> (see also
Creating and
Configuring an ICF Service). If only the component name is specified, the
standard namespace /SAP/ is used.
SAP applications are always delivered in the /SAP/namespace. If
you create your Web application in a separate namespace, it must be used in
the URL (see also Setting Up a Namespace
for Development). Components are specified in the format /<namespace>/<application
name>, for
example, /TEST40P/MYFIRSTAPP.
Examples
Application |
URL |
Application1a Application1b |
http://us4049.wdf.sap.corp:1080/sap/bc/webdynpro/sap/myFirstApp/ http://us4049.wdf.sap.corp:1080/sap/bc/webdynpro/sap/mySecondApp/ |
Application2a Application2b |
http://us4049.wdf.sap.corp:1080/sap/bc/webdynpro/test40p/myFirstApp/ http://us4049.wdf.sap.corp:1080/sap/bc/webdynpro/test40p/mySecondApp/ |
In these two examples the Web Dynpro application mySecondApp belongs to the component myFirstApp.
Pictures
Note that images are always loaded using the application URL (see below).
Examples
Application |
URL |
Application1a Application1b |
http://us4049.wdf.sap.corp:1080/sap/bc/webdynpro/sap/myFirstApp/allinone.bmp http://us4049.wdf.sap.corp:1080/sap/bc/webdynpro/sap/mySecondApp/allinone.bmp |
Applikation2a Applikation2b |
http://us4049.wdf.sap.corp:1080/sap/bc/webdynpro/test40p/myFirstApp/allinone.bmp http://us4049.wdf.sap.corp:1080/sap/bc/webdynpro/test40p/mySecondApp/allinone.bmp |
For mySecondApp/img.gif the incoming request must be changed so that it points to myFirstApp/img.gif, before the MIME handler is called.
If no further actions are performed, Web Dynpro applications are normally placed under /sap/bc/webdynpro. Understandably, many customers prefer to place their applications under a different URL namespace to /sap/bc.
Applications in the Customer Namespace
Normally
customers create their own branches in the ICF Internet service tree and place
their applications there. For example, company XYZcorp has a registered
namespace and has created the following entry in the ICF:
/xyzcorp/webdynpro/.
The Web Dynpro handler is stored in this ICF node. Then the customer can
create an application under this ICF path.
For a new
Web Dynpro component /XYZCORP/MYFIRSTAPP you would
find the following path in the ICF service tree:
.../xyzcorp/webdynpro
If this path exists, the application is stored under this ICF tree, and also
in the MIME Repository.
Examples
Application |
URL |
Application3a Application3b |
http://us4049.wdf.sap.corp:1080/1wda/webdynpro/myFirstApp/ http://us4049.wdf.sap.corp:1080/1wda/webdynpro/mySecondApp |
Keep in mind that namespaces are not allowed to begin at the root node of the
HTTP service tree. Instead they begin with the signature <namenspace>/webdynpro, that can be anywhere in the ICF tree.
For example, SCM has created the “Internet Communication Hub”
project in the namespace /ICH/. In this case the URL format would look like:
/sap/scm/ich/webdynpro/myFirstApp
See also:
FQDN
The fully qualified domain name (FQDN) must be specified in the URL of Web Dynpro applications. For more information see Fully Qualified Domain Names (FQDN).
Loading Images
Usually
images are loaded via the URL of the application in question. For Web Dynpro
ABAP images are stored in the MIME Repository.
For each component there is usually a corresponding identical Web Dynpro
application, for example, component abc is assigned to application abc. For
example, if URL .../sap/abc is assigned
to the application, the associated images are loaded as .../sap/abc/img.gif.
Component abc may be assigned to a second application xyz. In so this application has the URL .../sap/xyz, and any associated images should also be loaded using .../sap/xyz/img.gif. The image however is stored under .../sap/abc/img.gif. Instead of using relative paths, images should be loaded via the application URL, and not via the component name. This has the following advantages:
● Customer view
All the components of an application should also be stored in the relevant directory under this application. For customers using, for example, the application SalesOrder, it is easiest to store everything under SalesOrder/*.
● Load Balancing
When load balancers is used customers normally configure them so that they use URL paths to reach specific computers, and reject all requests that point to other paths. Here it is important that all images are loaded via the URL under which the application is also running.
For
information about the various URL formats that can be resolved by Web Dynpro
ABAP, see Handling Web
Icons.
URL with “/” Attached
When relative URLS are used to load images keep in mind how URLs behave in the browser. For example, if an image img.gif (or ./img.gif) is to be loaded with a URL of the format .../sap/app, the browser removes the last segment and generates a new URL with the format .../sap/img.gif. The app segment therefore no longer exists. The only way to get the browser to generate correct URLs is to attach a “/” character at the end of the URL. For example, if an application is started with .../sap/app, change the URL in .../sap/app/, either using a redirect command, or implicitly at the time when the frameset is loaded.
Special Cases
External URLs
Customers often define external URLs in the HTTP service tree of the ICF. A corresponding URL could look like:
Example
Application |
URL |
Application 1a |
http://us4049.wdf.sap.corp:1080/superApp/ |
Note that internal links function the same in the ICF tree.
Since relative URLs are used for images, theses are always loaded correctly. As soon as an application has been started, the internal name in the ICF tree must be used for the application so that it is clear what is going on behind it (pointer in the ICF tree).
Homepages
If a Web Dynpro application for a homepage is running directly under the root URL, the URL looks like:
Example
Application |
URL |
Special case 1a |
http://us4049.wdf.sap.corp:1080/ |