Testing Dynamic Service Activator

The SDX application library includes two gateway client that you can use to test Dynamic Service Activator.

NOTE: Juniper Networks Customer Service does not provide support for these gateway clients.

Web Application Gateway Client

The SDX application library includes a Web application gateway client that you can use to test Dynamic Service Activator's ability to invoke methods and scripts.

Installing the Gateway Client

To install the gateway client:

1. Access the Web application, soapClient.war, in the folder unsupported on the application library CD.
2. Install the Web application on a host.

For information about installing Web applications, see Chapter 1, Installing the SDX Applications. You do not need to configure any properties for this Web application.

Starting the Gateway Client

To start the Web client, access the following URL with a Web browser:

http://<host>:<portNumber>/soapClient/

• <host>—IP address or name of host that supports the Web application
• <portNumber>—Number of the TCP port

The Home Web page appears.

Connecting to the Gateway

To connect to the gateway, click on Configuration and follow the instructions on the screen.

Running Methods and Scripts

To run a method or script:

1. Click Methods.

The list of methods appears in the navigation menu.

2. Click on the method you want to run.

Follow the instructions on the screen to enter the required information for the method.

For example, if you want to view a list of the clients subscriptions, proceed as follows:

1. Click Subscriber_readSubscription in the navigation pane.
2. Enter the required information in the screen. The Client ID and password must match the data you configured.
3. Click Read subscription.

The Subscriber_readSubscription Method Web page displays the subscriber's subscriptions.

Gateway Client for PCs

The SDX application library includes a gateway client that you can use to test Dynamic Service Activator's ability to invoke scripts on the SAE.

Requirements

You can use this gateway client on a PC running the following software:

• Microsoft Windows 98 or a later version of Windows that supports Microsoft .NET Framework

For information about compatibility between Windows and .NET Framework, see:

http://msdn.microsoft.com

• .NET Framework version 1.1 or higher

Installing the Gateway Client

To install the gateway client:

1. Access the folder unsupported on the application library CD and copy the folder b2bTestClient to a PC.
2. Access the folder b2bTestClient on the PC, and open the file setup.exe.

If you see the following dialog box, you must install .NET Framework.

To install .NET Framework:

1. Click Yes in the dialog box.

The appropriate page on the Microsoft Web site appears.

1. Follow the instructions on the Web site to download and install .NET Framework version 1.1 or higher.
2. Repeat Step 2.

3. Follow the instructions on the screen to install the gateway client.

Starting the Gateway Client

To start the gateway client, select Start > Programs >
ScriptInvoker SOAP Client. The ScriptInvoker SOAP Client window appears.

Customizing the Default Settings

Customizing the default settings is optional. You can choose either to overwrite the default settings in the ScriptInvoker SOAP Client window each time you use the gateway client or to customize the default settings. If you choose the latter option, you can avoid modifying information each time you use the client.

To customize the default settings:

1. Access the folder on the PC in which you installed the gateway client.
2. Open the file ScriptInvokerClient.exe.config with a text editor.
3. In the file, find the line that reads <appSettings>.

The code for the settings appears below this line. Each setting has a line with the following format:

<add key="<settingName>" value="<settingValue>"

4. Edit the line for each setting.

ScriptInvoker URL

• Specifies URL of Dynamic Service Activator.
• Value—URL
• Default—http://127.0.0.1:8080/b2b/services/ScriptInvoker
• Guidelines—Be sure to edit the default setting of this property. The default setting points to an old application. See the following example for the correct application.
• Example—<add key="ScriptInvoker URL.Text" value="http://10.227.7.100:8080/dsa/services/DynamicServiceActivation" />
• Property name—ScriptInvoker URL.Text

Client ID

• Specifies user name that Dynamic Service Activator uses to authenticate this client.
• Value—Text string that matches user name
• Default—Anonymous
• Example—<add key="Client ID.Text" value="anonymous" />
• Property name—Client ID.Text

Client Password

• Specifies password that Dynamic Service Activator uses to authenticate this client.
• Value—Text string that matches password
• Default—Secret
• Example—<add key="Client Password.Text" value="secret" />
• Property name—Client Password.Text

SAE Script Name

• Specifies name of script that Dynamic Service Activator starts.
• Value—Text string that matches name of script
• Default—Echo
• Example—<add key="SAE Script Name.Text" value="Echo" />
• Property name—SAE Script Name.Text

SAE Script Arguments

• Specifies arguments that the script requires.
• Default—10.227.1.122,VideoGold,true
• Example—<add key="SAE Script Arguments.Text" value="10.227.1.122,VideoGold,true" />
• Property name—SAE Script Arguments.Text

Using the Gateway SOAP Client

To use the gateway client:

1. Start > Programs > ScriptInvoker SOAP Client.

The ScriptInvoker SOAP Client window appears.

2. If necessary, modify the default settings in the window.
3. Click Send SOAP Request.

Dynamic Service Activator runs the specified script and returns a message that states whether the operation was successful in the message box. If the operation was unsuccessful, you will see an error message that explains why the operation failed.

To clear the message box in the ScriptInvoker SOAP Client window, click Clear Output.

To view the SOAP messages, you must install and use a SOAP sniffer. The message box does not display the actual SOAP messages transmitted to and received from Dynamic Service Activator.

Sample Scripts

You can find a sample script called Echo in the file:

• /opt/UMC/sae/var/javaScripts/Echo.java—For JUNOS routing platforms
• /opt/UMC/ssp/var/javaScripts/Echo.java—For JUNOSe routers