[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


API for Dynamic Service Activator

This section contains information that developers need to create gateway clients and that administrators need to manage gateway clients and their interactions with the gateway.

NOTE: The SDX application library includes a gateway client that you can use to test Dynamic Service Activator. However, SDX developers must create their own gateway clients for testing the other gateway Web applications and for implementing the gateway applications in a network.


Public SOAP Interfaces of Web Applications

When you have installed Dynamic Service Activator, you can access a Web Services Description Language (WSDL) file for the application. The WSDL file defines the SOAP properties that you or your customers can use to develop a gateway client. The URL for Dynamic Service Activator is:

http://<host>:<portNumber>/dsa/services/DynamicServiceActivation ?wsdl

Methods for the Dynamic Service Activator SOAP Interface

This section describes the methods associated with Dynamic Service Activator, and provides information additional to that in the WSDL file.

invokeGwExtension

When deployed, servlets created with InvokeGwExtension should be accessible only from the local host.

invokeScript

Subscriber_readSubscription

Subscriber_readSubscription_retAttrSeq

Subscriber_activateService

For information about these attributes, see Subscription Attributes.

Subscriber_deactivateService

Subscriber_modifyService

For information about these attributes, see Subscription Attributes.

Subscriber_login

Subscriber_logout

Format of the Subscriber's URI

Many of Dynamic Service Activator's methods require the argument subURI, the subscriber's uniform resource identifier (URI). This argument comprises two portions: the type of subscriber (subscriber-type) and a list of the subscriber's attributes (subscriber-comp). The syntax for the subURI argument is:

<subscriber-type>:<subscriber-comp> [& <subscriber-comp>]*

The <subscriber-type> variable is the name of the Subscriber Type instance that is defined in the directory during the Dynamic Service Activator configuration (see Configuring Subscriber Types for Dynamic Service Activator). For example, the sample data provides these Subscriber Type instances for the <subscriber-type> value:

The <subscriber-comp> variable has the format <type>=<value>.

; | / | ? | : | @ | & | = | + | $ | ,

For example, you can use the following subscriber's URI to look up a subscriber by IP address as specified by the sample data:

ip:ipAddress=192.168.1.10

The sample data defines a subscriber type named ip, whose sidType is SIT_ADDRESS and nicProxyNamespace is /nicProxies/ip. As a result, ip is the value of the <subscriber-type> variable. Because the sidType is SIT_ADDRESS, ipAddress is mandatory for the <type> component, and the subscriber's IP address is the <value> component of the <subscriber-comp> variable.

Subscription Attributes

Some methods take attributes for subscriptions, as described below.

sessionTimeout

downstreamBandwidth

upstreamBandwidth

sessionTag

subscriptionUsername

subscriptionPassword

substitutions

SOAP Fault Codes for Dynamic Service Activator

When Dynamic Service Activator receives a SOAP request that it cannot handle, it returns a SOAP fault message to the gateway client. This message contains a text string that specifies a SOAP fault code and a text string that provides additional information about the fault.

Dynamic Service Activator returns the following SOAP fault codes. If the SOAP fault code has the format client.<variables>, you must correct the gateway client. However, if the SOAP fault code has the format server.<variables>, record the error code and notify the gateway administrator.

Client.InvalidArguments

Client.InvalidSubscriberFormat

Server.AccessDenied

Server.AccessControlMisconfiguration

Server.Misconfiguration

Server.SAEUnreachable

Server.SAE.UnkownSAEUser

Server.SAE.UserNotUniqueToSAE

Server.SAE.UnknownService

Server.SAE.UnknownSubscription

Server.SAE.ServiceAuthenticationError

Server.SAE.UnknownServiceSession

Server.SAE.LoginError

Server.SAE.Exception

Server.SAE.Overload

Server.SAE.ScriptProcessorError

Server.SAE.ScriptExecutionError


[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]