Running Methods and Scripts for Dynamic Service Activator Services (SRC CLI)

To run a method or script for the Dynamic Service Activator Web service interface:

Testing Subscriber Logins and Logouts (SRC CLI)

These methods support only subscribers who are identified by their IP addresses. These methods do not support subscribers who are identified by the names they use to log in or by their DNs.

Use the following commands to test the methods that log in and log out subscribers:

test dsa dsa-service subscriber-login <subscriber-uri subscriber-uri> <subscriber-id subscriber-id> <subscriber-password subscriber-password> <client-id client-id> <client-password client-password> <host host> <port port>
test dsa dsa-service subscriber-logout <subscriber-uri subscriber-uri> <client-id client-id> <client-password client-password> <host host> <port port>
test dsa dsa-service subscribers-login <subscriber-uri subscriber-uri> <subscriber-id subscriber-id> <subscriber-password subscriber-password> <rollback rollback> <client-id client-id> <client-password client-password> <host host> <port port>
test dsa dsa-service subscribers-logout <subscriber-uri subscriber-uri> <client-id client-id> <client-password client-password> <host host> <port port>

For the document literal implementation of Dynamic Service Activator (DSA2), issue the test dsa dsa2-service commands.

Testing Subscriber Access to Subscriptions (SRC CLI)

Use the following commands to test the method that determines whether a subscriber accesses services through the SRC owner’s network and obtains all of that subscriber’s subscriptions:

test dsa dsa-service subscriber-read-subscription <subscriber-uri subscriber-uri> <attributes attributes> <filter filter> <client-id client-id> <client-password client-password> <host host> <port port>
test dsa dsa-service subscribers-read-subscription <subscriber-uri subscriber-uri> <attributes attributes> <filter filter> <client-id client-id> <client-password client-password> <host host> <port port>

For the document literal implementation of Dynamic Service Activator (DSA2), issue the test dsa dsa2-service commands.

Testing Subscription Activations and Deactivations (SRC CLI)

Use the following commands to test the methods that activate and deactivate subscribers’ subscriptions to services:

test dsa dsa-service subscriber-activate-service <subscriber-uri subscriber-uri> service-name service-name <service-session service-session> <accounting-tag accounting-tag> <downstream-bandwidth downstream-bandwidth> <upstream-bandwidth upstream-bandwidth> <session-timeout session-timeout> <subscription-user subscription-user> <subscription-password subscription-password> <substitutions substitutions> <client-id client-id> <client-password client-password> <host host> <port port>
test dsa dsa-service subscriber-deactivate-service <subscriber-uri subscriber-uri> service-name service-name <service-session service-session> <client-id client-id> <client-password client-password> <host host> <port port>
test dsa dsa-service subscribers-activate-service <subscriber-uri subscriber-uri> service-name service-name <service-session service-session> <accounting-tag accounting-tag> <downstream-bandwidth downstream-bandwidth> <upstream-bandwidth upstream-bandwidth> <session-timeout session-timeout> <subscription-user subscription-user> <subscription-password subscription-password> <substitutions substitutions> <client-id client-id> <client-password client-password> <host host> <port port>
test dsa dsa-service subscribers-deactivate-service <subscriber-uri subscriber-uri> service-name service-name <service-session service-session> <client-id client-id> <client-password client-password> <host host> <port port>

For the document literal implementation of Dynamic Service Activator (DSA2), issue the test dsa dsa2-service commands.

Testing Subscription Modifications (SRC CLI)

Use the following commands to test the method that modifies subscribers’ subscriptions to services:

test dsa dsa-service subscriber-modify-service <subscriber-uri subscriber-uri> service-name service-name <service-session service-session> <accounting-tag accounting-tag> <downstream-bandwidth downstream-bandwidth> <upstream-bandwidth upstream-bandwidth> <session-timeout session-timeout> <subscription-user subscription-user> <subscription-password subscription-password> <substitutions substitutions> <client-id client-id> <client-password client-password> <host host> <port port>
test dsa dsa-service subscribers-modify-service <subscriber-uri subscriber-uri> service-name service-name <service-session service-session> <accounting-tag accounting-tag> <downstream-bandwidth downstream-bandwidth> <upstream-bandwidth upstream-bandwidth> <session-timeout session-timeout> <subscription-user subscription-user> <subscription-password subscription-password> <substitutions substitutions> <client-id client-id> <client-password client-password> <host host> <port port>

For the document literal implementation of Dynamic Service Activator (DSA2), issue the test dsa dsa2-service commands.

Testing Script Invocations (SRC CLI)

Use the following command to test the method that manages all operations involved with invoking scripts:

test dsa dsa-service invoke-script sae-script-name sae-script-name sae-script-arguments sae-script-arguments <client-id client-id> <client-password client-password> <host host> <port port>

This method retrieves requests to invoke scripts from the gateway client, authenticates the gateway client, verifies the arguments supplied by the gateway client, communicates with other SRC components, and returns values to the gateway client.

For the document literal implementation of Dynamic Service Activator (DSA2), issue the test dsa dsa2-service invoke-script command.

Testing Gateway Extension Invocations (SRC CLI)

Use the following command to test the method that invokes a servlet that has been created and deployed in the Web Services Gateway Web application server:

test dsa dsa-service invoke-gateway-extension gateway-extension-name gateway-extension-name gateway-extension-arguments gateway-extension-arguments <client-id client-id> <client-password client-password> <host host> <port port>

The servlet can be a standalone application, or it can be part of a WAR or EAR file. When deployed, servlets invoked with this method should be accessible only from the local host.

For the document literal implementation of Dynamic Service Activator (DSA2), issue the test dsa dsa2-service invoke-gateway-extension command.

Testing Access to Attributes for Subscriber Sessions (SRC CLI)

Use the following command to test the method that reads attributes for the services, subscribers, and subscriptions of all subscriber sessions:

test dsa dsa-service subscribers-read <subscriber-uri subscriber-uri> <subscription-attributes subscription-attributes> <subscription-filter subscription-filter> <service-attributes service-attributes> <service-filter service-filter> <subscriber-attributes subscriber-attributes> <client-id client-id> <client-password client-password> <host host> <port port>

Use the following command to test the method that reads attributes for a subscriber session:

test dsa dsa-service subscribers-read-subscriber <subscriber-uri subscriber-uri> <subscriber-attributes subscriber-attributes> <client-id client-id> <client-password client-password>

Use the following command to test the method that reads attributes for the subscriber’s subscriptions:

test dsa dsa-service subscribers-read-subscription <subscriber-uri subscriber-uri> <attributes attributes> <filter filter> <client-id client-id> <client-password client-password> <host host> <port port>

For the document literal implementation of Dynamic Service Activator (DSA2), issue the test dsa dsa2-service commands.

Example: Testing Subscriber Access to Subscriptions

To view a list of the Dynamic Service Activator client’s subscriptions:

  1. Issue the test dsa dsa-service subscriber-read-subscription command.
  2. Enter the required information (such as client ID, client password, and subscriber address). The entered data must match the data you configured.

    For example, this information is provided for Fred:

    user@host> test dsa dsa-service subscriber-read-subscription client-id Fred client-password secret subscriber-address 10.19.1.6 subscriber-type ip attributes "serviceName"
    The Subscriber_readSubscription method was successfully performed for 
    subURI: ip:ipAddress=10.19.1.6&timestamp=1216221624715 
    serviceName: COAService

Related Documentation