SAE CORBA Remote API

@

Introduction

The SAE CORBA remote API provides way to use external applications to access the service activation engine (SAE) throught a CORBA interface.

The SAE CORBA remote interface comprises an interface module manager and the following interface modules:

• SAE access interface module—Provides remote access to the SAE Core API (saeaccess.idl)
• Java script interface module—Allows you to control the SAE with a Java script (saescript.idl)
• Python script interface module—Allows you to control the SAE with a Python script (saescript.idl)
• Event notification interface module—Allows you to integrate the SAE with external IP address managers (event.idl)

Note:

Do not modify the IDL files.

The following figure shows the SAE CORBA remote interface on the SAE.

Interface Module Manager

The remote interface publishes one object reference (sae.ServiceActivationEngine) that acts as the interface module manager. External applications communicate through CORBA with the interface module manager to retrieve a particular interface module. That interface module runs in the same Java virtual machine (JVM) as the SAE and has full access to the SAE core API.

The SAE creates one object of type ServiceActivationEngine and exports a CORBA reference for this object to the file:

/opt/UMC/sae/var/run/sae.ior

When you develop applications using the SAE CORBA remote API, you must include the CORBA reference for the SAE in one of the following formats:

• The absolute path to the IOR file
• A corbaloc URL in the form corbaloc::<host>:8801/SAE where <host> is the name or IP address of the SAE host.

Before You Use the CORBA Remote API

You should be familiar with the SAE core API before you use the CORBA remote API. You can locate documentation for the SAE core API on the SDX software CD in the folder /sdk/doc/sae/index.html or on the Juniper Networks Web site at www.juniper.net/techpubs/software/management/sdx/api-index.html.

You will notice that some of the class names are the same, but that the methods vary. The CORBA remote API bundles a number of methods together so that one remote API call can be made rather than numerous calls from the SAE core API.

Security Considerations

The CORBA remote API does not support any security restrictions. The remote interface and the SAE should be installed in a network to which only authorized clients have access.

More Information About Using the Interface Modules

For information about each interface module, see:

• Using the SAE Access Interface Module
• Using the Java Script Interface Module
• Using the Python Script Interface Module
• Creating a Customized Interface Module
• Using the Event Notification API

---