Maintaining ITS Service Parameters 

Use

The service parameters maintained for the standalone ITS in the ABAP Workbench and then published as service file <service name>.srvc are ignored in the integrated ITS.

You must maintain the parameters in transaction SICF for every service individually.

Procedure

If the service parameters contain logon data (for example, ~client or ~language), you can enter them in change mode on the Service Data tab page in the group Anonymous Logon Data. ~timeout corresponds to the entry Session Timeout, which you can find on the Service Data tab page in the group Service Options. In addition, you must activate on the same tab page the flag GUI Connection in the group Service Options (set to Y) and edit the additionally required service parameters in the Settings dialog.

Parameters for defining the application server to which to connect the ITS, for example ~appServer, ~systemNumber, ~routeString, which are required for the standalone ITS, must no longer be maintained as service parameters. For more information on allowed service parameters, see Parameters for Developers.

Allowed Service Parameters to be Maintained

Parameter Name	Value
~TRANSACTION	it00
~THEME	99

Note that individual parameters are not inherited in the ICF (there is no counterpart for the global.srvc file). For this reason, all parameters must be specified completely in every service.

If you are working with one set of templates for the standalone ITS and the integrated ITS, you must maintain the service parameters twice: once in the ICF for the integrated ITS and once in the ABAP Workbench for the standalone ITS.

Result

You have now maintained the service parameters for your service to be used with the integrated ITS.

In the next step, you must make the changes to the HTML templates.