Setting Up the ICF Service for the ITS Service (IAC)

Basics — The Generic ICF/ITS Handler

In transaction SICF, you find an ITS service for the SAP GUI for HTML. It is stored in the ICF under the virtual host default_host with URL/sap/bc/gui/sap/its/. The service is called webgui.

When you display the webgui service (entry Display Service in the context menu of the service), you find the ITS-specific handler CL_HTTP_EXT_ITS in the properties under the Handler List tab page. This handler is the generic ICF/ITS handler that must be specified for all ITS services. It must be specified exactly on the last node of the ICF tree, that is, directly on the service name. The position of the handler determines the splitting of the URL into path and service name and thus determines the content of the parameters ~urlwgate and ~service at runtime.

Creating ICF Service Names

You can select the service name and the storage location for your ITS service freely, as long as you register the generic ITS service as described above directly on the service. If, at runtime, you want to start other ITS services out of the currently started service, then you must use relative addressing in HTMLBusiness when storing the services in different hierarchy levels of the ICF tree. However, this is not compatible with the standalone ITS. If all called ITS services are located under the same root node in the ICF, you can call these services without any problems. After splitting the URL into path (~urlwgate) and service name (~service), you can address all services of the same hierarchy level using the HTMLBusiness parameter `~urlwgate`.

The procedure in transaction SICF is described in Creating ICF Services.

Creating ICF/ITS Handlers

Register the ITS-specific handler CL_HTTP_EXT_ITS for the newly created ICF service in the handler list (under the Handler List tab page in transaction SICF).

Activate ICF Service

Before you can execute the service for the first time, you must activate it (see also Activating/Deactivating SICF Services).