In the integrated ITS we have new procedures for activating services and their templates. This article describes these steps as a quick start tutorial.
Service data in the integrated ITS
All of this service data are maintained as an Internet Service in the transaction SE80. With the standalone ITS the so called IACOR (Internet Application Component Object Receiver) was used for publishing such a service to the ITS. After having published the data the service can be used. This has changed with the integrated ITS.
Though Internet Services are created in the transaction SE80, they must be defined using the transaction SICF too. Service parameters must be defined in SICF for being effective in the integrated ITS.
Though service parameters can be maintained within the SE80, they must be configured in the ICF service description. There is no possibility for publishing the parameters to an ICF service. However, it is not a big task to create and configure an ICF service.
ICF services are created, configured, and maintained using the transaction SICF. A good starting point is to study some of the ITS services that SAP delivers with the WebAS. Those examples are /sap/bc/gui/its/webgui and /sap/bc/gui/its/test/it/it00.
ICF services have to be activated before they can be used. This task can also be done with transaction SICF.
Business HTML Templates and MIME data
Publishing the templates and the MIME data is an easy task in the transaction SE80. Choose the Internet Service to be published, make sure that your workbench settings for the ITS is 'integrated ITS' - older versions of the dialog offer a site called 'INTERNAL'. Use 'Menu'=>'Utilities'=>'Settings' for maintaining the publishing target. The figures below show the dialog for a WebAS 640 and a newer release resp.. Mark the service in the tree and use the context menu for publishing the whole service. That's all.
Screenshot of 6.40:
Screenshot of 7.00 and higher:
Testing the service
The service can be tested in the transaction SICF. Just use the context menu and choose 'test service'. A browser window with the correct URL will appear. As an alternative the function module SITSP_GET_URL can be used for retrieving the URL.