![]() ![]() ![]() ![]() ![]() ![]() |
The following section describes configuration and maintenance attributes and operations for SOAP2SOAP communication services. The plug-ins for SOAP2SOAP communication services are created using the Platform Development Studio. The sections also provide a workflow for the configuration:
This section contains a description of the configuration attributes and operations available for SOAP2SOAP-type of plug-in instances.
SOAP2SOAP communication services are developed using the Platform Development Studio.
Based on a set of service WSDLs and callback WSDLs, a SOAP2SOAP communication service acts as a proxy service, and provides the functionality provided by the Network Gatekeeper container services, such as:
SOAP2SOAP plug-in services can be instantiated using the plug-in manager. The plug-in instances process traffic and connects to individual network nodes. The instances are managed independently of each other.
For application-initiated requests, all requests are routed to the network node defined for the plug-in instance.
For network-triggered requests, the network-node should distinguish which application instance the request is targeted to by adding the application instance ID to the URL:
http://<WLNG IP Address>:<port>/<context-root>_nt/<plug-in instance ID>_nt/<application instance ID>
The endpoint at which the application instance has implemented the Web Service is provisioned: see Provisioning Workflow for SOAP2SOAP Communication Services.
The ID is given when the plug-in instance is created, see Managing and Configuring the Plug-in Manager.
|
|
Derived from the package name of the network protocol plug-in, as given when the plug-in was generated, and the name of the interface as defined in the WSDL.
See see Managing and Configuring the Plug-in Manager for information on how to list the interfaces.
|
|
<communication service identifier>_<protocol>_plugin.jar, <communication service identifier>_service.jar and <communication service identifier>_callback.war, packaged in wlng_nt_<communication service>.ear
|
Below is an outline for configuring the plug-in using the Network Gatekeeper Administration Console:
Note: | If the SOAP2SOAP plug-in is the only plug-in for the service enabler, routing based on destination address is not applicable. All requests will be routed to the plug-in instance. If there are other, non-SOAP2SOAP, plug-ins in the service enabler, the routing applies. |
http://<IP Address>:<port>/<context-root>_nt/<plug-in instance ID>/<application instance ID>
default <context-root>
is the communication service ID, as specified when the communication service was generated.
<plug-in instance ID>
is the ID of the plug-in instance. The network node is assumed to specify which application instance the request is targeted to by adding the application instance ID as the suffix in the URL.
Continue with the provisioning of service provider accounts and application accounts.
For each application that uses SOAP2SOAP communication services and supports network-triggered requests, a mapping must be set up between the application instance ID and the URL for the Web service this application instance implements. Use the following operations to manage the callback URLS for the application instances:
Below is a list of attributes and operations for configuration and maintenance:
Specifies whether HTTP Basic Authentication shall be used when authenticating with the network node. Enter:
Specifies the URL to the network node.
Specifies the password to use when connecting to the network node.
Specifies the username to use when connecting to the network node.
Specifies whether Web Services Security Username Token shall be used when authenticating with the network node.
Adds the URL to which network-triggered requests per application instance should be forwarded. The application is assumed to implement the callback web service on this URL.
addApplicationEndPoint(AppinstanceId: String, CallbackUrl: String)
Displays the URL to which network-triggered requests for a given application instance should be forwarded.
getApplicationEndPoint(AppinstanceId: String)
Displays a list of all registered callback URLS.
listApplicationEndPoints()
Removes the URL to which the network-triggered requests for a given application instance are forwarded.
removeApplicationEndPoint(AppinstanceId: String)
![]() ![]() ![]() |