Was this page helpful to you?
Do you have any additional feedback?
Creating and Configuring an ICF Service
You need to inset the handler into an ICF service so that the HTTP request handler is called up in the browser when a URL is entered. You can use transaction SICF to create, configure and insert the right handler.
Setting up the ICF Service Hierarchy
The services delivered by SAP are stored in the ICF service hierarchy under the virtual host default_host and the service node sap. In turn, the sap node is divided into the subtrees option, public, bc (basis functionality) and xi (Exchange Infrastructure), under which the relevant services are found.
The special services stored under the default_host/sap/option node are for SAP-internal use only. No services can be changed or created in this subtree.
The services defined below the default_host/sap/option node do not require user authentication in the SAP system.. They are used for general test purposes and global services. All actions in these services are carried out under a standard system user. You are not able to create your own services in this subtree either.
An HTTP request handler has been created.
To create and configure an ICF service, you normally need to perform the following steps:
· Create the service
· Define the logon procedure
· Define the service options
· Define the security requirements
· Set up error pages
· Inserting an HTTP request handler
· Activate/deactivate the service
You have the option of creating your own services under your own virtual host.
In Web server systems, virtual hosts allow a computer to be accessible via various combinations of host names and ports (the host names being aliases). You can use virtual hosts to interpret the behaviour of a server in different ways, for example to define various folders in the file system as root nodes.
If you want to use internal or external aliases, read the following detailed information about assigning aliases when implementing handlers:
The following content is not part of SAP product documentation. For more information, see the following disclaimer .