Before You Install Dynamic Service Activator
Before you use Dynamic Service Activator, you must:
- Deploy a working SDX network.
- Configure a NIC that identifies the SAE reference for each subscriber type
See SDX Network Guide: SAE, Juniper Networks Routers, and NIC, Chapter 5, Locating Subscriber Information.
- Create the Java scripts that Dynamic Service Activator invokes (see the SAE CORBA Remote API documentation in the SDX software distribution at SDK/doc/idl/sae/html/index.html or on the Juniper Networks Web site at
http://www.juniper.net/techpubs/software/management/sdx/api-index.html).- Install the sample data from the application library CD.
See Chapter 1, Installing the SDX Applications.
- Determine a hierarchy for the methods and scripts that Dynamic Service Activator activates and the clients who request use of those methods and scripts.
When you configure Dynamic Service Activator, you must create a set of access controls between a gateway client and each method or script the client uses. One approach is to create one object for each relationship between a client and a method or script. However, with this approach, the configuration namespace could become cluttered and difficult to manage.
A more ordered approach is to organize client objects subordinate to method and script objects or vice versa. For example, you can create an object that specifies a method or script. You can then create subordinate objects for each gateway client that can use the method or script, and you can define the names of the gateway clients and other access properties in these subordinate objects.
Alternatively, you can create an object that defines a gateway client. You can then create subordinate objects for each method or script to which the gateway client has access, and you can define the arguments for the method or script and other access properties in the subordinate object.
See Sample Data for Dynamic Service Activator for examples of hierarchical organization of methods, scripts, and clients.