Networks change. Existing functionality is parsed in new ways to support new features. New nodes with new or modified abilities are added. Because of WebLogic Network Gatekeeper's highly modular design, exposing these new features to partners is a straightforward proposition. There are several ways to extend Network Gatekeeper:
Entirely new communication services
New network plug-ins that can work with existing application facing interfaces
New or re-ordered interceptors or policy rules
Integration with the existing network mechanisms with EDR listeners and SMNP MIBs.
The Platform Development Studio
To help operators and systems integrators, WebLogic Network Gatekeeper ships with the Network Gatekeeper Platform Development Studio. The PDS comprises the following features:
Create Subscriber SLAs for subscriber-based policy
Update EDR filters and add JMS-based listeners
Re-order the Interceptor Stack or create new interceptors
Use the Platform Testing Environment, for functional and duration tests, and for unit tests
Example Communication Service, including:
Source code
Wsdls
Build files
Example unit test
Example Subscriber SLA/Profile Provider
The Eclipse Wizard
The developer supplies information to an Eclipse plug-in wizard, which automatically sets up an Extension Project. Included within this project can be a substantial amount of generated code, including:
The entire Access Tier, with the Web Service implementation and any callback modules (EJBs) that are necessary
Note:
The Eclipse Wizard only supports building communication services based on Web Services application-facing interfaces.
Most of the code for the common services code in the Network Tier
A skeleton of the code required for the network plug-in layer of the Network Tier
A complete Javadoc reference
Specialized templates and Ant tasks
The Platform Test Environment, launched using an Ant task at runtime from a flexible set of modules including:
Application Service Clients
Network Simulators
A complete example module including client and simulator
Utilities such as an MBean browser and JMS-based EDR listeners
The PTE supports two modes of running:
Standalone with a Java Swing-based GUI
Console, particularly for use with the Unit Test Framework
The Unit Test Framework, providing:
A base test class, derived from JUnit
Simple to use mechanisms for connecting to the Platform Test Environment
An example unit test bundled with the Communication Service Example
The Profile Provider SPI, which allows operators and integrators to create subscriber-centric policy, associating subscribers to Service Provider and Application Groups based on individualized subscriber preferences and permissions.
