Understanding Restricting Write Access to Service Definitions

When you restrict write access to a service, sensitive fields of the service definition and of associated service operations appear in read-only mode. The following table lists the components and pages that contain fields and data that are related to services and describes the impact that restricting access to services has to each of them.

Restricted Component or Page Restriction Comments

Service

All fields are read-only.

NA

Service Operation

All fields are read-only, with the following exceptions:

  • User Password Required.

  • Non-Repudiation.

  • Runtime Schema Validation.

When a service is restricted, you cannot regenerate routings.

Handlers

All fields are read-only except:

  • The Status drop-down list box.

  • The Add a Row button (+) that is used to add new handlers.

When a service is restricted, you can still activate or inactivate handlers.

Routings

All fields are read-only except:

  • The Inactivate Selecting Routings and Activate Selected Routings buttons.

  • The Add button.

When a service is restricted, you can:

  • Activate and deactivate routings of service operations that are associated with the service.

  • Add new routings to service operations that are associated with the service.

You cannot delete or rename a restricted service. In addition, you cannot change, rename or delete any service operation that is defined as part of a restricted service.