Show TOC

URLs and NamespacesLocate this document in the navigation structure

Use

When using your own namespaces, there are some particularities to note with regard to the paths in the Internet service tree of the Internet Communication Framework ICF and in the MIME repository.

Note

When creating your own namespaces, refer to the naming conventions. For more information, go to http://help.sap.com, and search for Defining Naming Conventions.

Normally, a Web Dynpro application is created in SE80 either in the SAP namespace with its simple name, for example, myapp, or in a customer namespace with the complex name specification in the form /<name space>/<application name>, for example /test40p/myapp. The path in the ICF is then under both /sap/ and your own namespace, as in the examples below.

Application Name

ICF Path

myapp

/sap/bc/webdynpro/sap/myapp

/test40p/myapp

/sap/bc/webdynpro/test40p/myapp

If the path hierarchy in the SAP namespace (/sap/bc/webdynpro/sap/myapp) or in the customer namespace (/sap/bc/webdynpro/acme/myapp) is too long-winded in the ICF, you can position our own namespace at the highest level directly below the default host (/acme/webdynpro/myapp). To do this, the following prerequisites must be met:

  • In the ICF, the relevant superordinate node for the respective namespace and the webdynpro subnode must be created. For more information, go to http://help.sap.com, and search for Creating and Configuring the ICF Service

  • For the webdynpro subnode, the HTTP request handler CL_WDR_MAIN_TASK must be defined in the handler list.

    For this subnode, the system logon must also be configured. As soon as this has been configured, the system logon is automatically available for all subnodes of webdynpro.

    If applications already exist under the long ICF path, they have to be moved accordingly.

    • For all existing applications under the old path, new application nodes have to be created manually in the ICF under the new path: /acme/webdynpro/myapp1

    • The /sap/bc/webdynpro/acme/ path should then be deleted together with all the subapplications.

  • In addition, the MIME repository must contain the relevant folder for the namespace and a subfolder for webdynpro.

    If there are already images for existing applications in the MIME repository under the corresponding long path, these have to be moved:

Once these prerequisites are met, the ICF path is at the highest level, as shown in the example below.

Application Name

ICF Path

/1wda/myapp

/1wda/webdynpro/myapp

/acme/myapp

/acme/webdynpro/myapp

Preparatory Settings

To ensure that Web Dynpro runs smoothly in a customer namespace, you need to make the following settings:

  1. Call up the Internet Communication Framework using transaction SICF.

  2. Create a new root node for your namespace (for example, /acme) in the service tree directly below the default host.

    Note that you only enter and save the name here.

  3. Below your new root node, create a subnode called webdynpro: The path is then /acme/webdynpro.

    Note that the name of the subnode must be webdynpro (without any spaces).

  4. For the subnode webdynpro, specify CL_WDR_MAIN_TASK as the handler on the Handler List tab.

  5. If you have existing applications that have a node under the long ICF path, create a new node under the new path for each of these old applications and then delete the old path completely.

  6. In the MIME Repository tree, create a new root node for your namespace and underneath it a subnode for webdynpro. The method CREATE_ROOT_FOLDER of class CL_MIME_REPOSITORY_API is provided for this.

    In the MIME Repository, the path is then as follows: /acme/webdynpro

    Move existing images under the long/old path in the MIME Repository to the relevant positions in the new path.

Checking the Settings

  1. Call transaction SE80.

  2. Navigate to your test application.

  3. Check whether the syntax of the URL for the Characteristics of the application has the following notation: http://host.domain.ext:port/1wda/webdynpro/helloworld