Installation Tasks
This section lists the installation tasks for Dynamic Service Activator. Refer to the following sections for information about these tasks.
To install Dynamic Service Activator:
- Complete the prerequisite tasks.
- Install one copy of Dynamic Service Activator on a Web application server to support all business partners.
Installation of Dynamic Service Activator includes customization of the bootstrap.properties file, which defines how Dynamic Service Activator connects to the directory that contains the configuration information for this Web application.
Prerequisite Tasks
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 Components Guide, Vol. 2, Chapter 12, 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 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 the section Sample Data for examples of hierarchical organization of methods, scripts, and clients.
Installing Dynamic Service Activator
To install Dynamic Service Activator:
- Create a temporary folder for the application on a host.
mkdir dsa- Copy the dsa.war file from the webapp directory on the application library CD to a temporary directory on your workstation.
cp /cdrom/cdrom0/webapp/dsa.war dsa- Extract the bootstrap.properties file from the dsa.war file.
jar xvf dsa.war WEB-INF/bootstrap.properties- Edit the bootstrap.properties file with any text editor to configure values for properties in the following list.
This file provides information about how Dynamic Service Activator communicates with the directory. The default file shows examples of the settings for the properties.
- Replace the bootstrap. properties file in the dsa.war file.
jar uvf dsa.war WEB-INF/bootstrap.properties- Deploy the dsa.war file by following the procedure appropriate to the Web application server you are using.
Config.java.naming.provider.url
- URL of the primary directory that stores configuration information in URL string format.
- Value—ldap:// <host>:<portNumber>
- <host>—IP address or name of host that supports the Web application
- <portNumber>—Number of the TCP port
Config.java.naming.security.credentials
- Password that the Web application server uses to authenticate and authorize gateway clients.
- Value—Text string
- Default—conf
Config.java.naming.security.principal
- DN that contains the username that the Web application server uses to authenticate and authorize gateway clients.
- Value—DN of object that contains the username
- Default—cn=conf, o=Operators, o=umc
Config.net.juniper.smgt.des.backup_provider_urls
- Redundant directories that store configuration information.
- Value—Space-separated list of URLs in URL string format (see description for the property Config.java.naming.provider.url)
Config.net.juniper.smgt.des.<propertySuffix>
- Set of properties that specify how Dynamic Service Activator interacts with the directory.
- Values—See SDX Components Guide, Vol. 1, Chapter 11, Configuring the Directory Eventing System.
- Defaults—See SDX Components Guide, Vol. 1, Chapter 11, Configuring the Directory Eventing System.
Config.net.juniper.smgt.lib.config.staticConfigDN
- Root of the static configuration properties.
- Value—DN of object that contains the username
- Default—ou=staticConfiguration, ou=configuration, o=Management, o=umc (root of static configuration properties of sample data)
Dsa.namespace