Service policies use a hierarchical naming scheme to describe
the policy name. The notion of hierarchy in the name is only to provide
additional meaning to the policy names to make them easier to read.
The actual hierarchical capabilities are provided by the Service Policy Manager runtime
component.
The naming convention does not affect a policy's position
in the Service Policy Manager inheritance hierarchy. Each name can have multiple parts, where each part is separated by a period
(.) delimiter.
The following categories are defined:
- Category: message (message processing service policies)
- message.capacity
- Policies for capacity measurements
- message.intercept
- Policies for message intercept
- message.sla
- Policies for SLA measurements
- message.statistics
- Policies for network statistics
- message.privacy
- Policies for privacy
- Category: requester (requester policies)
- requester.operation
- Policies to apply to requester use of operations
- requester.trace
- Policies related to tracing requests by requester
- Category: service (service policies)
- service.config
- Policies related to service configuration
- service.custom
- Policies defined for Web service implementations
- service.standard
- Policies defined by Web services specifications
- Category: customer (values that are customer unique and
are not recorded in the service usage record, but are made available
to plug-in points)
- Category: usage (values that are to be passed through to
the service usage record)
A Service Policy Manager installation
includes a default requester hierarchy and a default service hierarchy.
They are enumerated in the following sections.
Requester hierarchy
For the requester hierarchy,
the following interface definitions are initialized by default.
A
group named ALL, containing all of these definitions, is also initialized.
Requester: unauthenticated
Group:
authenticated- Requester: anonymous.invalid
- Requester: notification
Service hierarchy
For the service hierarchy,
the following interface definitions are initialized by default. Use
these definitions to help you register the Web service implementations.
A
group named ALL, containing all of these definitions, is also initialized.
Group:
WAP
Push- Service: http://www.ibm.com/wsdl/wappush/send/v1_0/interface
Group:
Parlay X- Group: Third Party Call
- Service: http://www.csapi.org/wsdl/parlayx/third_party_call/v2_3/interface
- Group: Call Notification
- Service: http://www.csapi.org/wsdl/parlayx/call_notification/v2_2/interface
- Service: http://www.csapi.org/wsdl/parlayx/call_notification/notification_manager/v2_3/interface
- Service: http://www.csapi.org/wsdl/parlayx/call_direction/v2_2/interface
- Service: http://www.csapi.org/wsdl/parlayx/call_direction/notification_manager/v2_3/interface
- Group: SMS
- Service: http://www.csapi.org/wsdl/parlayx/sms/notification_manager/v2_3/interface
- Service: http://www.csapi.org/wsdl/parlayx/sms/send/v2_2/interface
- Service: http://www.csapi.org/wsdl/parlayx/sms/receive/v2_2/interface
- Service: http://www.csapi.org/wsdl/parlayx/sms/notification/v2_2/interface
- Group: MMS
- Service: http://www.csapi.org/wsdl/parlayx/multimedia_messaging/notification_manager/v2_5/interface
- Service: http://www.csapi.org/wsdl/parlayx/multimedia_messaging/send/v2_4/interface
- Service: http://www.csapi.org/wsdl/parlayx/multimedia_messaging/receive/v2_4/interface
- Service: http://www.csapi.org/wsdl/parlayx/multimedia_messaging/notification/v2_4/interface
- Group: Payment
- Service: http://www.csapi.org/wsdl/parlayx/payment/amount_charging/v2_1/interface
- Service: http://www.csapi.org/wsdl/parlayx/payment/reserve_amount_charging/v2_1/interface
- Service: http://www.csapi.org/wsdl/parlayx/payment/reserve_volume_charging/v2_2/interface
- Group: Account Management
- Service: http://www.csapi.org/wsdl/parlayx/account_management/v2_2/interface
- Group: Terminal Status
- Service: http://www.csapi.org/wsdl/parlayx/terminal_status/notification_manager/v2_2/interface
- Service: http://www.csapi.org/wsdl/parlayx/terminal_status/v2_2/interface
- Service: http://www.csapi.org/wsdl/parlayx/terminal_status/notification/v2_2/interface
- Group: Terminal Location
- Service: http://www.csapi.org/wsdl/parlayx/terminal_location/notification_manager/v2_3/interface
- Service: http://www.csapi.org/wsdl/parlayx/terminal_location/v2_2/interface
- Service: http://www.csapi.org/wsdl/parlayx/terminal_location/notification/v2_2/interface
- Group: Call Handling
- Service: http://www.csapi.org/wsdl/parlayx/call_handling/v2_3/interface
- Group: Audio Call
- Service: http://www.csapi.org/wsdl/parlayx/audio_call/v2_1/interface
- Group: Multimedia Conference
- Service: http://www.csapi.org/wsdl/parlayx/multimedia_messaging/notification_manager/v2_5/interface
- Service: http://www.csapi.org/wsdl/parlayx/multimedia_messaging/send/v2_4/interface
- Service: http://www.csapi.org/wsdl/parlayx/multimedia_messaging/receive/v2_4/interface
- Service: http://www.csapi.org/wsdl/parlayx/multimedia_messaging/notification/v2_4/interface
- Group: Address List Management
- Service: http://www.csapi.org/wsdl/parlayx/group_mgmt/v2_1/interface
- Service: http://www.csapi.org/wsdl/parlayx/group/v2_1/interface
- Service: http://www.csapi.org/wsdl/parlayx/group_member/v2_1/interface
- Group: Presence
- Service: http://www.csapi.org/wsdl/parlayx/presence/supplier/v2_3/interface
- Service: http://www.csapi.org/wsdl/parlayx/presence/consumer/v2_3/interface
- Service: http://www.csapi.org/wsdl/parlayx/presence/notification/v2_3/interface
Note: Registration of a Web service implementation
is performed when installing a Web service implementation through
the First Steps script auto
configuration facility.