SAP Service Activation Letter : Activate and Maintain Services – SAP
Describes the actions available within the Activate and Maintain Services activity in the IMG.
Use
The transaction for activating and maintaining services is used to maintain all registered services on the SAP Gateway server (hub system), to register and activate services, to delete services, and to simplify the usage in general.
The service maintenance offers the following advantages:
Fast overview of all registered services on the SAP Gateway hub system as well as backend systems
Detailed display of a service, such as ICF nodes and system alias assignment
Easy generation and activation of new services
The service maintenance is part of the Implementation Guide (IMG) in your SAP Gateway system. In the SAP Reference IMG (transaction SPRO) navigate to .
The main screen is divided into an upper and a lower part in which the upper part shows all registered services ( Service Catalog) and the lower part shows the details of the selected service from the Service Catalog. The details are split into ICF Nodes and System Aliases.
In the Activate and Maintain Services screen you can access some basic SAP Gateway functions directly:
You can quickly access the SAP Gateway Client by choosing
Goto SAP GW Client . The SAP Gateway Client provides general testing functions for your OData services.You can quickly access the metadata cache by choosing
Goto Cleanup of Model Cache .
Service Catalog
The service catalog lists all services of the current system. You can easily find services from a backend system that have not yet been registered by choosing Add Service in the menu bar
The list of services that will be added is shown as soon as a system alias is provided. The list can be further limited by entering additional search criteria as filter values
You can select a service from the list under Add Service via the hotspot of column Technical Service Name, Service Description, or External Service Name.
Details about the selected service are displayed. In this detailed view you always enter a valid package name or, for local objects which should not be transported, you choose Local Object which will automatically assign package $TMP to the service.
In section ICF Node the option Set current client as default client in ICF Node is pre-selected as well as the ICF node to be used. ICF node creation is disabled if the service already has an ICF node. This is because different versions are using the same ICF node / ICF service. If ICF services for both modes (standard as well as compatibility) exist, then both radio buttons would be greyed out. If only one ICF service exists, then only one ICF button will be greyed out. For example, if an ICF node for the compatibility mode already exists, then this option is greyed out and None is set. In this case, you could activate the standard mode.
Service versioning
Service versioning helps an administrator to generate a service with an additional version. In addition, detailed information of each service can be displayed to get a first idea on the different versions. Thus an administrator can easily handle different versions of a service that are provided by the backend system(s).
Apart from activating single services, you can also activate several services at once. This mass activation can be useful for large amounts of services that have to be available quickly. Of course you need several services to start with. To carry out mass activation, proceed as follows:
- Choose Add Service.
- Enter the relevant system alias. You can use a filter, if needed.
- In the list, select those services that you want to activate and choose Add Selected Services.
- Enter a prefix for your service and model names, for example Z and enter a valid package and choose Enter.
A list of all the services that were created is displayed, together with a status indicator (green for successful execution). Now you can close this screen.
The list of selected backend services no longer contains those services that you have activated.
Be the first to comment