Configuring Administrative Service Providers

Use

If the usual security options of SAP NetWeaver are not sufficient, SAP can flag a specific Web service as administrative. The ICF node that this Web service uses during runtime is then created under a special administrative virtual host. If you need to mark your own Web service as administrative, you can proceed as described in the section Task at Design Time.

Prerequisites

You have configured an administrative host in your ABAP system. For more information, see SAP Notes 1748112 Information published on SAP site (with attachment) and 1778777 Information published on SAP site.

Procedure

Task at Design Time

SAP flags administrative Web service providers as administrative. This means that you usually do not have any tasks at design time. If you want to flag your own Web service as administrative, proceed as follows:

  1. In transaction SM30, open the table VEPADMINFLAG.

  2. Add the service definition that you want to mark as administrative to the table.

  3. Save your settings.

  4. Transport the changes manually using TABU entries within a standard ABAP transport.

Tasks at Configuration Time

A Web service that is marked as administrative uses the admin host.

  1. In SOA Manager (transaction code SOAMANAGER), go to the Service Administration tab.

  2. Choose Web Service Configuration.

  3. Search for the service definition and choose Apply Selection.

    On the Details tab, you see whether the service definition is marked as administrative under Governance and Administration Relevance.

  4. On the Configuration tab, open a binding or create a new one.

  5. On the Transport Settings tab of the binding, the admin virtual host is specified. If you do not want the Web service to use the admin host, you have to select False under Assigned to Admin Virtual Host.

Health Checks

The health check Admin Service in SOA Manager checks the following:

  • Whether configurations for service definitions that are administrative use the admin host. If this is not the case, it is reported as a warning.

  • Whether there are configurations that use the admin host, but no admin host has been configured in the ICF framework. In this case, the configuration is inconsistent. This is reported as an error in the health check.

  1. In SOA Manager (transaction code SOAMANAGER), go to the Tools tab.

  2. Choose Health Check.

  3. Choose Run to execute the health check.

  4. Select the system on which you want to execute the health check.

  5. Choose Options, ensure that the Admin Service Check is included, and choose OK.

  6. When the health check is finished, the results are displayed. You can also display the results of previous health checks in SOA Manager.

More Information

Managing Administration-Relevant ICF Services