Configuration Tasks

This section lists the configuration tasks for Dynamic Service Activator. Refer to the following sections for more information about these tasks.

1. Configure security for gateway clients.
2. Access the configuration files.
3. Configure the general properties.
4. Configure access to methods and scripts.
5. (Optional) Delete methods and scripts that you no longer require.
6. Configure the NIC proxy.
7. Configure logging properties.

Configuring Security for Gateway Clients

As described in the section Dynamic Service Activator Operation, Dynamic Service Activator interacts with the Web application server to determine whether a gateway client has access to a method or script. To configure security for gateway clients:

1. Configure the name and credentials, such as a password, that the Web application server uses to authenticate the gateway client.

You must use the same name for the gateway client when you define the scripts and methods to which the gateway client has access (see Configuring Access to Methods and Scripts).

2. Assign gateway clients to the defined security role for Dynamic Service Activator.

The default role is DSAAuthorizedClient; if you want to change the default setting, you can edit the file dsa\WEB-INF\web.xml file, which you can extract from the dsa.war file. For information about extracting files from a WAR file, see the previous section, Installing Dynamic Service Activator.

For information about these tasks, see the documentation for your Web Application server, and the information about security at http://java.sun.com/j2ee/1.4/docs/tutorial/doc/index.html.

Accessing the Configuration Files

Use SDX Configuration Editor to configure general properties for Dynamic Service Activator. For information about using SDX Configuration Editor, see SDX Software Basics Guide, Chapter 15, Using SDX Configuration Editor.

To access the new Dynamic Service Activator:

1. Start SDX Configuration Editor.
2. Import the sample data from the directory.
3. Open the WebApplication/DynamicServiceActivation.xml file and the WebApplication.xml file.

Configuring General Properties

The general properties for Dynamic Service Activator are settings that determine the global behavior of the application, rather than the relationship between an individual gateway client and the application.

To configure general properties for Dynamic Service Activator:

1. In the DynamicServiceActivation.xml file, click the Dynamic Service Activation tab.

The Dynamic Service Activation pane appears.

2. Complete the properties.

Logging subsytem configuration namespace

• Specifies the namespace that defines the properties for the logging operations.
• Value—Path, relative to the root namespace, that defines the object for the namespace
• Default—/WebApplication

Nic Proxy configuration namespace

• Specifies the namespace that defines the properties for the NIC proxy operations.
• Value—Path, relative to the root namespace, that defines the object for the namespace
• Default—/WebApplication/DynamicServiceActivation/nicProxy

Disable Access Control Mechanism

• Specifies the setting that determines the type of access that gateway clients have to methods and scripts.
• Value—True | False

• True—Gateway clients have unrestricted access to all methods and scripts
• False—Gateway clients have access only to methods and scripts that you specify in the configuration

• Default—False

Configuring Access to Methods and Scripts

Before configuring access to methods and scripts, you should determine how you want to organize the methods, scripts, and clients (see Prerequisite Tasks.)

NOTE: Generally, to keep the organization simple, you should make all method and script objects subordinate to client objects, or vice versa.

Configuring access to methods and scripts involves adding methods, scripts, and clients to the directory, and configuring access properties between each client and each method or script.

To configure access to methods and scripts:

1. In the DynamicServiceActivation.xml file, add a method, script, or client.

• Click the Methods/Scripts tab to create a method or script.
• Click the Clients tab to create a client.

The Methods/Scripts or Clients pane appears.

2. Follow the standard procedure to create a new object with SDX Configuration Editor.
3. Depending on the object you created, proceed as follows:

• If you created a method or script object, scroll down the Methods/Scripts pane to the field List of clients who may invoke this method or script, and follow the standard procedure to create new client objects with SDX Configuration Editor.
• If you created a client object, scroll down the Clients pane to the field List of methods that this client may invoke, and follow the standard procedure to create new method objects with SDX Configuration Editor.

4. Specify the following properties for each combination of method or script and client in the Methods/Scripts and Clients panes.

• For each client, specify the name of the gateway client.
• For each method, specify the name of the method or script, and a value of zero for the argument that Dynamic Service Activator uses to locate the SAE. For each script, specify the name of the script, and the zero-based index of the argument that Dynamic Service Activator uses to locate the SAE.

Each method or script receives a set of arguments in the gateway client's SOAP request. For example, the second argument has the index 1 and could be a subscriber's IP address. Dynamic Service Activator would pass the argument to the NIC to locate the SAE server managing that subscriber.

• (Optional) For a method, script, or client, specify the regular expressions that the arguments in the SOAP request must match for the gateway client to obtain access to the method or script (see Configuring Access Constraints).

5. Save the file.

Client ID

• Specifies the name of the gateway client.
• Value—Text string that exactly matches the name the Web application server uses to authenticate the gateway client (see Configuring Security for Gateway Clients).
• Guidelines—If you disable the access control mechanism (see Configuring General Properties), and you configure the Web application server to authenticate clients with any username and password (see Configuring Security for Gateway Clients), Dynamic Service Activator sends the text string "anonymous client" as the first argument to the SAE's Java scripts interface module

Method or script name

• Specifies the name of the method or script to activate on the SAE.
• Value—Text string that exactly matches the name of the method or script

SAE locator index

• Specifies the zero-based index of the argument that Dynamic Service Activator should use to locate the SAE server on which to activate the method or script.
• Value—Integer in the range 0-4294967295

Constraints for arguments

• See the section Configuring Access Constraints.

Configuring Access Constraints

Access constraints are regular expressions that the arguments for the method or script in the SOAP request must match. If the arguments for the method or script in a particular SOAP request do not match these regular expressions, then Dynamic Service Activator rejects the request. Access constraints are optional.

You use the fields labelled Constraints for arguments to specify the regular expressions. These fields comprise an entry box, a display table, and a set of action buttons.

To add optional access constraints:

1. Click in the entry box.
2. Enter the access condition in the format

<property>=<regularExpression>

• <property>—Zero-based index of the argument
• <regularExpression>—Regular expression

For information about the regular expression syntax, see http://java.sun.com/j2se/1.4.1/docs/api/java/util/regex/Pattern.html.

3. Click Add.

To modify optional access conditions:

1. Select the access condition you want to delete in the table.

The access condition appears in the entry box.

2. Modify the text in the entry box.
3. Click Modify.

The modified condition appears in the display table.

To delete optional access conditions:

1. Select the access condition you want to delete in the display table.
2. Click Delete.

Deleting Methods, Scripts, and Clients

You can delete methods, scripts, and clients in both the Methods and Clients panes of the DynamicServiceActivation.xml file. At the start of each list of methods, scripts, or clients in these tabs is a menu called Delete an Instance.

To delete a method or client from a list:

1. Select that method or client from the menu to the left of the field called Delete an Instance.
2. Click Delete an Instance.

The Confirmation dialog box appears.

3. Click OK.

SDX Configuration Editor deletes the method or client.

Configuring the NIC Proxy

To configure the NIC proxy, click on the NicProxy tab in the Dynamic Service Activator Web service pane. For information about configuring NIC proxies, see SDX Components Guide, Vol. 2, Chapter 12, Configuring and Starting the NIC.

Configuring the Logging Properties

To configure logging properties:

1. With SDX Configuration Editor, access the WebApplication.xml file.

The Logging pane appears.

2. Configure the logging properties.

You can see default settings for logging in this file. For information about configuring logging, see SDX Components Guide, Vol. 1, Chapter 12, Configuring Logging.

3. Save the file.

Exporting Configuration Objects

Saving configuration changes in SDX Configuration Editor saves them only in the local configuration object. When you have configured the gateway applications, you must export the modified objects to the directory for the changes to take effect.

To export configuration changes back to the directory:

1. Select the project in the navigator pane, and hold down the right mouse button.
2. Select SDX System Configuration > Export to LDAP Directory.