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:
- Run the test dsa dsa-service command.user@host> test dsa dsa-service (invoke-gateway-extension | invoke-script | subscriber-activate-service | subscriber-deactivate-service | subscriber-login | subscriber-logout | subscriber-modify-service | subscriber-read-subscription | subscribers-activate-service | subscribers-deactivate-service | subscribers-login | subscribers-logout | subscribers-modify-service | subscribers-read | subscribers-read-subscriber | subscribers-read-subscription)
For the document literal implementation of Dynamic Service Activator (DSA2), issue the test dsa dsa2-service command.
user@host> test dsa dsa2-service (invoke-gateway-extension | invoke-script | subscriber-activate-service | subscriber-deactivate-service | subscriber-login | subscriber-logout | subscriber-modify-service | subscriber-read-subscription | subscribers-activate-service | subscribers-deactivate-service | subscribers-login | subscribers-logout | subscribers-modify-service | subscribers-read | subscribers-read-subscriber | subscribers-read-subscription)where:
- invoke-gateway-extension—Invokes a servlet that has been created and deployed in the Web Services Gateway Web application server.
- invoke-script—Manages all operations involved with invoking scripts.
- subscriber-activate-service—Activates subscribers’ subscriptions to services.
- subscriber-deactivate-service—Deactivates subscribers’ subscriptions to services.
- subscriber-login—Logs in subscribers.
- subscriber-logout—Logs out subscribers.
- subscriber-modify-service—Modifies subscriptions.
- subscriber-read-subscription—Determines whether a subscriber accesses services through the SRC owner’s network and obtains all of that subscriber’s subscriptions.
- subscribers-activate-service—Activates subscribers’ subscriptions to services for all subscriber sessions.
- subscribers-deactivate-service—Deactivates subscribers’ subscriptions to services for all subscriber sessions.
- subscribers-login—Logs in subscribers.
- subscribers-logout—Logs out subscribers.
- subscribers-modify-service—Modifies subscriptions for all subscriber sessions.
- subscribers-read—Reads attributes for the services, subscribers, and subscriptions of all subscriber sessions.
- subscribers-read-subscriber—Reads attributes for the subscriber session.
- subscribers-read-subscription—Reads attributes for the subscriber’s subscriptions of all subscriber sessions.
- Testing Subscriber Logins and Logouts (SRC CLI)
- Testing Subscriber Access to Subscriptions (SRC CLI)
- Testing Subscription Activations and Deactivations (SRC CLI)
- Testing Subscription Modifications (SRC CLI)
- Testing Script Invocations (SRC CLI)
- Testing Gateway Extension Invocations (SRC CLI)
- Testing Access to Attributes for Subscriber Sessions (SRC CLI)
- Example: Testing Subscriber Access to Subscriptions
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:
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:
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:
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:
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:
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:
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:
Use the following command to test the method that reads attributes for a subscriber session:
Use the following command to test the method that reads attributes for the subscriber’s subscriptions:
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:
- Issue the test dsa dsa-service subscriber-read-subscription command.
- 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×tamp=1216221624715 serviceName: COAService