This chapter describes how the different types of Service Level Agreements (SLAs) are managed and provisioned in Oracle Communications Services Gatekeeper.
It contains the following sections:
Introduction to SLA types
Summary of Tasks Related to SLAs
There are two different kinds of SLAs:
System level SLAs
Custom SLAs
System level SLAs have static XSDs that are already defined in Services Gatekeeper, while custom SLAs provides the possibility to use a custom XSD. Any given service provider group or application group can have only one system SLA associated with it, while they can have many custom SLAs. Create custom SLAs when additional SLA enforcement logic is required that is not provided by default in Services Gatekeeper. You must create the enforcement logic for a Custom SLA. See Services Gatekeeper Extension Developer's Guide for information on how to develop Custom SLAs.
When SLAs are loaded into memory, they are stored in the SLA repository. SLAs can be loaded into the repository in two ways:
The contents of the SLA is provided as a parameter in the operation that loads the SLA.
The SLA is stored in a file and the URL to that file is provided as a parameter in the operation that loads the SLA.
SLAs are retrieved from the SLA repository using the retrieve operations.
The SLA loaded into the SLA repository is the one being enforced. Changes to the file after the SLA is loaded into the repository are not automatically reflected in the active version.
Table 3-1 outlines the different SLA types, the IDs and their scope.
| SLA Type | ID(s) | Description |
|---|---|---|
|
Application Group |
application system:geo_application |
System SLA. Defines how application can use Services Gatekeeper. See "Application Group SLAs" for a summary of related management operations. For information on creating these SLAs, see "Defining Service Provider Group and Application Group SLAs". The SLA type ID:
|
|
Service Provider Group |
service_provider system:geo_service_provider |
System SLA. Defines how service providers can use Services Gatekeeper. See "Service Provider Group Node SLAs" for a summary of related management operations. For information on creating these SLAs, see "Defining Service Provider Group and Application Group SLAs". The SLA type ID:
|
|
Global Node |
global_node |
System SLA. Defines how Services Gatekeeper is allowed to use the underlying telecom network nodes. See "Global Node SLAs" for a summary of related management operations. For information on creating these SLAs, see "Defining Service Provider Group and Application Group SLAs". This SLA type is loaded and enforced locally in the network tier cluster it is loaded. |
|
Service Provider Node |
service_provider_node |
System SLA. Defines how Service Providers are allowed to use the underlying telecom network nodes. See "Service Provider Group Node SLAs". For information on creating these SLAs, see "Defining Service Provider Group and Application Group SLAs". This SLA type is loaded and enforced locally in the network tier cluster it is loaded. |
|
Subscriber |
subscr |
System SLA. Defines classes of application services that can be associated with subscribers in the context of Services Gatekeeper. Using the Platform Development Studio, an operator or integrator may create a subscriber-centric policy mechanism. The specifics of this mechanism are covered in ”Using SLA Policies to Manager Subscribers” in Services Gatekeeper Extension Developer's Guide. This SLA type is loaded and enforced locally in the network tier cluster on which it is loaded. |
|
Custom |
Defined at load time |
Custom SLA. A custom SLA is defined by an XSD, that must be created and loaded. A custom SLA type ID is associated with the XSD, and this type is the one being referenced when loading the custom SLAs. In addition to the SLA, the enforcement logic that operates on the data in the SLA must be created. See ”Creating Custom Runtime SLAs” in Services Gatekeeper Services Gatekeeper Extension Developer's Guide. Just like system SLAs, the custom SLAs are associated with service provider groups and application groups. In addition there is a custom global SLA, that does not take into consideration the originator of the request, but affects all requests. Custom SLAs are loaded and enforced locally in the network tier cluster it is loaded. |
Note:
The prefix system is reserved, and should not be used by custom SLAs. For backward compatibility, there is a set of SLA types without this prefix.The tasks related to the management of SLAs comprise the following:
The management of Service Provider and Application Group system SLAs comprises managing the following:
You use the methods of the ServiceLevelAgreementMBean MBean to manage Service Provider and Application Group system SLAs. For information on the methods and fields of the ServiceLevelAgreementMBean, see the ”All Classes” section of Services Gatekeeper OAM Java API Reference.
Table 3-2 describes the tasks related to managing Service Provider Group system SLAs and the ServiceLevelAgreementMBean MBean methods to use.
Table 3-2 Tasks Related to Managing Service Provider Group System SLAs
| Task | ServiceLevelAgreementMBean Method to Use |
|---|---|
|
Associate Service Provider Group with SLA |
loadServiceProviderGroupSlaByType loadServiceProviderGroupSlaFromUrlByType |
|
View Service Provider Group SLA |
retrieveServiceProviderGroupSlaByType |
Table 3-3 describes the tasks related to managing Application Group system SLAs and the ServiceLevelAgreementMBean MBean methods to use.
The management of Node SLAs comprises managing the following:
You use the methods of the ServiceLevelAgreementMBean MBean to manage Node SLAs. For information on the methods and fields of the ServiceLevelAgreementMBean, see the ”All Classes” section of Services Gatekeeper OAM Java API Reference.
Table 3-4 describes the tasks related to managing Global Node system SLAs and the operations you use to perform those tasks.
Table 3-5 describes the tasks related to Service Provider Group Node SLAs and the operations you use to perform those tasks.
Subscriber SLAs are a feature that can be developed using the Platform Development Studio. Table 3-6 describes the tasks related to managing Subscriber SLAs and the operations you use to perform those tasks.
Custom SLAs are a feature that can be developed using the Platform Development Studio. This section describes the management of Custom SLAs.
You use the methods of the ServiceLevelAgreementMBean MBean to manage custom SLAs. For information on the ServiceLevelAgreementMBean methods and fields, see the ”All Classes” section of Services Gatekeeper OAM Java API Reference.
Table 3-7 describes the tasks related to managing Custom XSDs and the operations you use to perform those tasks.
Table 3-8 describes the tasks related to managing Custom Application Group SLAs and the operations you use to perform those tasks.
Table 3-8 Tasks Related to Managing Custom Application Group SLAs
| Task | Operation to Use |
|---|---|
|
Associate Custom Application Group with SLA |
loadApplicationGroupSlaByType loadApplicationGroupSlaFromUrlByType |
|
View Custom Application Group SLA |
retrieveApplicationGroupSlaByType |
|
Count Custom Application Group SLA |
countApplicationGroupsByType |
|
List Custom Application Group SLA |
listApplicationGroupsByType |
Table 3-9 describes the tasks related to managing Custom Service Provider Group SLAs and the operations you use to perform those tasks.
Table 3-9 Tasks Related to Managing Custom Service Provider Group SLAs
| Task | Operation to Use |
|---|---|
|
Associate Custom Service Provider Group with SLA |
loadServiceProviderGroupSlaByType loadServiceProviderGroupSlaFromUrlByType |
|
View Custom Service Provider Group SLA |
retrieveServiceProviderGroupSlaByType |
|
Count Custom Service Provider Group SLA |
countServiceProviderGroupsByType |
|
List Custom Service Provider Group SLA |
listServiceProviderGroupSlaTypes listServiceProviderGroupsByType |
Table 3-10 describes the tasks related to managing Custom Global SLAs and the operations you use to perform those tasks.