![]() ![]() ![]() ![]() ![]() ![]() |
The following section describes how to generate deploy and configure SOAP2SOAP Communication Services. These Communication Services can be created using the Platform Development Studio or directly from the Administration Console:
SOAP2SOAP communication services are generated using the Platform Development Studio or directly from the Oracle Communications Services Gatekeeper Administration console.
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 Oracle Communications Services 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://<IP Address of AT server>:<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.
If the number of HTTP requests that time-out during a certain time-period exceeds the maximum allowed, the plug-in instance is taken out of operation for a configurable time-period. The HTTP time-out behavior is valid for request between the plug-in instance and the network node. The purpose of this feature is to prevent network nodes that are malfunctioning from incoming request.
SOAP2SOAP Communication Services can be generated and deployed using the Administration console:
See Generated Artifacts for the Communication Service for a description of the generated artifacts.
To generate a SOAP2SOAP Communication Service from the Administration console, open the SOAP-SOAP Generation page by selecting OCSGSOAP-SOAP from the Domain Structure group and enter configuration properties for the Communication Service according to Table 33-1.
SOAP2SOAP Communication Services can also be generated using the Eclipse wizard provided with the Platform Development Studio. See section Using the Eclipse Wizard in Platform Development Studio - Developer’s Guide.
On successful generation of the Communication Service, the deployment screen is displayed, see Deploy a Communication Service.
When a SOAP2SOAP Communication Service has been generated using the Administration Console, see Generate a Communication Service the deployment screen is displayed.
When deploying directly from the Administrating console, fill in the entry fields described in Table 33-2 and click the button Deploy SOAP2SOAP. In this case, the Communication Service is deployed to the same domain as where it was generated.
The generated Communication Service can also be deployed using WebLogic tools, see Generated Artifacts for the Communication Service.
Once the Communication Service is deployed, create one or more plug-in instances, see Managing and Configuring SOAP2SOAP Communication Services.
When generating a SOAP2SOAP Communication Service the following directory structure is created in the directory $DOAMIN_HOME/soap2soap
on the Administration Server.
| +- <Communication service name>_<version>/
| | | +- build.properties
| | +- build.xml
| | +- common.xml
| | +- <Communication service name>/
| | | | +- common/
| | | | | +- resources/
| | | | | | +- enabler/
| | | | | | +- facade/
| | | | | | +- handlerconfig.xml
| | | | +- dist/
| | | | | +- com.bea.wlcp.wlng.soap2soap.<service type>.store_<version>.jar
| | | | | +- wlng_at_<Communication service name>.ear
| | | | | +- wlng_nt_<Communication service name>.ear
| | | | +- plugins/
| | | | | +- soap/
| | | | | +- tmp/
All Java source files, build files, configuration files, and deployable artefacts are created under the directory $DOMAIN_HOME/soap2soap. The source files are there mainly for reference, and the only files that are necessary to deploy the Communication Service are:
wlng_at_<Communication service name>.ear should be deployed in the Access Tier server.
wlng_nt_<Communication service name>.ear should be deployed in the Network Tier server.
The generated Communication Service can be deployed as a part of the generation process, as described above or using standard WebLogic Server tools.
For information on how to deploy the files using WebLogic Server tools, see Deploy and Undeploy Communication Services and plug-ins.
This section contains a description of the configuration attributes and operations available for SOAP2SOAP-type of plug-in instances.
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
<communication service identifier>_callback.jar and <communication service identifier>.war, packaged in wlng_at_<communication service identifier>.ear
|
Below is an outline for configuring the plug-in using the Oracle Communications Services 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 a time period during which a number of HTTP time-outs are counted.
Specifies the number of HTTP time-outs allowed during a time-period. The time-period is specified in Attribute: HttpTimeoutPeriod.
If the number of time-outs are exceed, the plug-in instance transfers to state disconnected, which means that it does not accept new requests. It stays disconnected during the time-period defined in Attribute: ReactivateTime.
Specifies the HTTP time-out value. If this value is exceeded, the request is considered to be lost and the counter that tracks the number of requests that encountered HTTP time-outs is increased.
Specifies the URL to the network node.
Specifies the password to use when connecting to the network node.
Specifies the time a plug-in instance is kept in state disconnected when the number of HTTP time-outs have exceeded the maximum number, specified in Attribute: HttpTimeoutThreshold, over a time-period, specified in Attribute: HttpTimeoutPeriod.
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)
![]() ![]() ![]() |