System Administrator’s Guide

Managing and Configuring SOAP2SOAP Communication Services

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:

SOAP2SOAP Communication Services

This section contains a description of the configuration attributes and operations available for SOAP2SOAP-type of plug-in instances.

About SOAP2SOAP Communication Services

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.

Properties for SOAP2SOAP Plug-ins

Property	Description
Managed object in Administration Console	<domain name>WLNG<server name>Communication Services<plug-in instance ID>
MBean	Domain=com.bea.wlcp.wlng Name=wlngt InstanceName is same as plug-in instance ID Type=com.bea.wlcp.wlng.httpproxy.management.HTTPProxyMBean
Network protocol plug-in service ID	Defined when generating the SOAP2SOAP plug-in using the Platform Development Studio.
Network protocol plug-in instance ID	The ID is given when the plug-in instance is created, see Managing and Configuring the Plug-in Manager.
Supported Address Scheme	Given when the plug-in was generated using the Platform Development Studio.
North interfaces	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. For application-initiated request: <package name>.plugin.<Interface name>Plugin For network-triggered requests: <package name>.callback.<Interface name>Callback See see Managing and Configuring the Plug-in Manager for information on how to list the interfaces.
Service type	Given when the plug-in was generated using the Platform Development Studio.
Exposes to the service communication layer a Java representation of:	Depends on the WSDLs used.
Interfaces with the network nodes using:	The same protocol as exposed by the application-facing interfaces.
Deployment artifacts	<communication service identifier>_<protocol>_plugin.jar, <communication service identifier>_service.jar and <communication service identifier>_callback.war, packaged in wlng_nt_<communication service>.ear <communication service identifier>_callback.jar and <communication service identifier>.war, packaged in wlng_at_<communication service identifier>.ear <communication service identifier> and <protocol> was given in the Eclipse wizard when the communication service was generated.>

Configuration Workflow for SOAP2SOAP Plug-ins

Below is an outline for configuring the plug-in using the Network Gatekeeper Administration Console:

Continue with the provisioning of service provider accounts and application accounts.

Provisioning Workflow for SOAP2SOAP Communication Services

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:

Reference: Attributes and Operations for SOAP2SOAP Plug-ins

Below is a list of attributes and operations for configuration and maintenance:

Attribute: HttpBasicAuthentication

Scope: Cluster

Unit: n/a

Format: Boolean

Specifies whether HTTP Basic Authentication shall be used when authenticating with the network node. Enter:

Attribute: NetworkEndpoint

Scope: Cluster

Unit: n/a

Format: String

Specifies the URL to the network node.

Attribute: Password

Scope: Cluster

Unit: n/a

Format: String

Specifies the password to use when connecting to the network node.

Attribute: UserName

Scope: Cluster

Unit: n/a

Format: String

Specifies the username to use when connecting to the network node.

Attribute: UserNameTokenAuthentication

Scope: Cluster

Unit: n/a

Format: Boolean

Specifies whether Web Services Security Username Token shall be used when authenticating with the network node.

Operation: addApplicationEndPoint

Scope: Cluster

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.

Signature:

addApplicationEndPoint(AppinstanceId: String, CallbackUrl: String)

Operation: getApplicationEndPoint

Scope: Cluster

Displays the URL to which network-triggered requests for a given application instance should be forwarded.

Signature:

getApplicationEndPoint(AppinstanceId: String)

Operation: listApplicationEndPoints

Scope: Cluster

Displays a list of all registered callback URLS.

Signature:

listApplicationEndPoints()

Operation: removeApplicationEndPoint

Scope: Cluster

Removes the URL to which the network-triggered requests for a given application instance are forwarded.

Signature:

removeApplicationEndPoint(AppinstanceId: String)