Managing Accounts and SLAs

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Creating and Maintaining Service Provider and Application Accounts

An essential part of managing WebLogic Network Gatekeeper is dealing with service provider partners. Network Gatekeeper provides a partner administration model to help operators handle the needs and demands of their partners in a flexible and powerful way:

See Figure 2-1 for an illustration of the relationship among the different account types.

Figure 2-1 Service provider and application model with SLAs

Service provider and application model with SLAs

The separation of accounts and groups provides a flexible way of defining service level agreements. Groups allow the Network Gatekeeper administrator to offer tiers of service at both the service provider (via service provider group SLAs) and application (via application group SLAs) level.

For example, a Network Gatekeeper administrator might use SLAs to create three different categories of service providers:

Each of these would have different privileges when it comes to maximum throughput and QoS parameters. When a new service provider is provisioned, the service provider is associated with an appropriate group based on, for example, the amount of network traffic the service provider is projected to generate. If the outcome is not what was predicted, the service provider account can be reassigned to another service provider group with a different QoS parameter defined in the service provider level SLA.

Note: IDs of service provider groups, application groups, application instances, service provider accounts must be unique. The combination of service provider account and application account for an application instance must be unique.

The service provider and application account and group registrations are performed either through the WebLogic Network Gatekeeper Administration Console or through external management systems integrated with WebLogic Network Gatekeeper using the Network Gatekeeper Partner Relationship Management Interfaces or via MBeans. This guide describes many of the tasks associated with establishing and maintaining these accounts and groups using the Administration Console.

Note: Service provider accounts, application accounts, and application instances have states that can be changed using OAM, so they can be temporarily be taken out of service. See States of Accounts.

 


Typical workflow

  1. Define the set of service classes, expressed as SLAs, at both the service provider group level and the application group level, see Defining Service Provider Group and Application Group SLAs.
  2. Define the set of node service classes, expressed as SLAs, at both the service provider node level and global node level, see Defining Global Node and Service Provider Group Node SLAs.
  3. Create service provider and application groups that correspond to these SLAs, see Managing Groups.
  4. Associate the service provider group SLAs and application group SLAs with the groups, see Managing SLAs.
  5. Load the global node SLA and service provider group node SLAs, see Managing SLAs.
  6. Create a service provider account and associate it with the appropriate service provider group. See Managing Service Provider and Application Accounts.
  7. Create an application account and associate it with the appropriate application group. See Managing Service Provider and Application Accounts.
  8. Create an application instance, see Managing Application Instances.
  9. Depending on which communication service is being used, provision communication service specific data using the operation and management for relevant communication service.
  10. Distribute the credentials to be used by the application to the service provider.
Note: It is also possible to create unique SLAs and groups for an individual application. Accounts can be associated with other groups in runtime, so the class of service can be adjusted over time.

  Back to Top       Previous  Next