Show TOC

Setting Up the ICF Service for the ITS Service (IAC)Locate this document in the navigation structure

Prerequisites

There is an ITS service in the ABAP Workbench, which you want to execute with the integrated ITS.

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.

Example

If the handler lies directy on the webgui service, the URL http://<host>:<port>/sap/bc/gui/sap/its/webguiInformation published on non-SAP siteis split by the integrated ITS into ~urlwgate=/sap/bc/gui/sap/its and ~service=webgui. This allows for an almost complete compatibility between standalone ITS and integrated ITS.

Procedure

To make your ITS service known for the ICF, perform the following steps:

  1. Creating ICF Service Names

  2. Creating ICF/ITS Handlers

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`.

Example

Services in the Same Hierarchy Level

The following ITS services are registered in the ICF:

/sap/bc/gui/sap/bbp/bbpstart

/sap/bc/gui/sap/bbp/bbpgo

Service bbpstart can start service bbpgo by coding in HTMLBusiness as in the standalone ITS: `~urlwgate`/bbpgo/!.

Example

Services in Different Hierarchy Levels

The following ITS services are registered in the ICF:

/sap/bc/gui/sap/its/start/bbpstart

/sap/bc/gui/sap/its/bbp/bbpgo

Service bbpstart can address service bbpgo only by specifying relative path names: `~urlwgate`../bbp/bbpgo/!, where the two periods are used to address the ITS directory and then bbp is used to address bbpgo. These entries are not compatible with the standalone ITS.

Note

Store the services in a flat hierarchy under the ITS root node /sap/bc/gui/sap/its.

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).

Activating ICF Services

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

Result

You have now created the ICF service for the ITS service to be used by the integrated ITS.

In the next step, you must Maintain Service Parameters.