|Oracle® Communications Services Gatekeeper Concepts Guide
Part Number E16613-02
This chapter describes Operation, Administration, and Maintenance (OAM) functionality for Oracle Communications Services Gatekeeper.
Services Gatekeeper is controlled through the Services Gatekeeper Administration Console, a specialized extension of the general WebLogic Server Administration Console. The console is a Web-based tool and can be run in any environment that supports appropriate Web browsers. For general information on the administration console, see Oracle Fusion Middleware Introduction to Oracle WebLogic Server at:
For some tasks, you can also use scripts that run in the WebLogic Scripting Tool. For details, see "Oracle WebLogic Scripting Tool" in Oracle Fusion Middleware Concepts Guide at:
In addition, all or selected parts of the management application can be integrated with external OSS using JMX/JMS. Additionally, alarms can be distributed using SNMP traps.
Finally, the application service provider management tool functionality can be integrated with PRM and CRM systems using the Services Gatekeeper Partner Relationship Management Interfaces.
Administrative users can be divided into user groups with access to different aspects of the administrative functionality. Within user groups, individual users can have differing levels of access. See System Administrator's Guide for more information.
As stated earlier, the Services Gatekeeper Administration Console is a Web browser-based, graphical user interface that you use to manage a WebLogic Server domain.
A standard production installation for Services Gatekeeper consists of at least one WebLogic Server domain. One instance of WebLogic Server in each domain is configured as an Administration Server.
The Administration Server hosts the Administration Console and provides a central point for managing a Services Gatekeeper domain. All other server instances in the domain are called Managed Servers. In Services Gatekeeper, they are divided into Access Tiers and Network Tiers. In a domain that contains only a single WebLogic Server instance, such as a development environment, that server functions as the Administration Server and both Managed Servers, that is, the Access Tier and the Network Tier.
Use the Administration Console to:
Configure, start, and stop Services Gatekeeper instances
Configure Services Gatekeeper clusters
Configure Services Gatekeeper services, such as database connectivity (JDBC) and messaging (JMS)
Monitor server and application performance
View server and domain log files
View application deployment descriptors
Edit selected run-time application deployment descriptor elements
Upgrade communication services
Configure security parameters and roles
Use the Services Gatekeeper-specific section (accessed through the Domain Structure tree on the left side of the Administration Console) to:
Configure Services Gatekeeper communication services
Manage administrative users and groups
Provision Application Service Providers, Applications, Application Instances, and related SLAs.
Monitor alarms, CDRs, and EDRs
Create multiple plug-in instances, set up plug-in routing, and so on.
Tasks performed outside the Console
Extend Services Gatekeeper's functionality
Back up and restore the system
Upgrade the system
See Communication Service Guide for information about configuring and managing communication services.
See System Administrator's Guide for information about configuring and managing other aspects of Services Gatekeeper.
All or selected parts of the management application can also be integrated with external OSS through secured JMX/JMS interfaces. For more information on working with JMX, see Developing Manageable Applications With JMX for Oracle WebLogic Server at:
http://download.oracle.com/docs/cd/E15523_01/web.1111/e13729/designapp.htm and Oracle Fusion Middleware Configuring and Using the Diagnostics Framework for Oracle WebLogic Server at:
http://download.oracle.com/docs/cd/E15523_01/web.1111/e13714/title.htm. Alarm supervision systems can set up external JMS listeners to receive user definable types of event-based data, including standard alarms. SNMP traps are sent to any registered SNMP managers.