[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


SRC Programming Interfaces

You can use the APIs provided with the SAE to extend SRC capabilities. The SAE provides the following APIs:

Other components within the SRC software may provide programming interfaces. These interfaces are described in the documentation for the associated component.

The SRC software also includes plug-ins, such as plug-ins for accounting and authentication, admission control, customized accounting and authentication, and prepaid access.

CORBA Plug-In SPI

The CORBA-plug-in SPI is an interface that allows you to implement external plug-ins to integrate SAE with OSS software written in a wide variety of languages and distributed across a variety of hardware and operating system platforms. The SPI lets you link the rest of a service provider's OSS with the SRC software so that the OSS is notified of events in the life cycle of SAE sessions. For example, plug-ins can notify the OSS when a subscriber attempts to log in, and the OSS can evaluate general data and resource allocation to make authorization decisions.

CORBA Remote API

The CORBA remote API provides remote access to the SAE. It comprises an interface module manager and the following interface modules:

Most functions that are available through the SAE core API are also available through the CORBA remote API.

NIC Access API

The NIC access interface module (nicAccess.idl) is a simplified CORBA interface used to perform NIC resolutions. Use the NIC access module to develop applications not written in Java.

SAE Core API

The SAE core API is used to control the behavior of the SRC software, including subscribers, services, and subscriptions, as well as the SAE itself. For example, it can be used to provide subscriber credentials information (username and password) or to request subscription activation or deactivation for a subscriber.

Script Services

Script services are SAE services that provide an interface to call scripts that supply custom services. You can use script services to create custom service implementations, such as:

You can use script services to provision policies on a number of systems across a network, including networks that do not contain a JUNOSe router or JUNOS routing platform.


[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]