Service Extension

The following sections describe how to extend WebLogic Network Gatekeeper functionality:

About service extension

Service extension is about extending BEA WebLogic Network Gatekeeper's functionality to provide new Java and Web Services APIs and to support new network services and protocols.

This can be done by installing new SESPA modules, ESPA service capability modules and SCS or network plug-ins in BEA WebLogic Network Gatekeeper SLEEs. Also external protocol adapters can be connected to the Plug-in manager. For more information about system extension alternatives, see Product Description - BEA WebLogic Network Gatekeeper.

Installing a SESPA module

The following is an outline of an installation procedure to be used when adding a new SESPA service to BEA WebLogic Network Gatekeeper. SESPA services are are SLEE services, so the SLEE's standard procedure for SLEE service installation is followed.

A complete procedure, including SESPA service configuration (if any), has to be provided in the new SESPA service's documentation.

Installation can be made in run-time.

Install and start the SESPA service through the SLEE deployment service.

Configure the SESPA service through the service's own OAM methods.

Deploy the servlet in the Tomcat servlet engine and the web service in the Axis SOAP engine. See the new SESPA service's documentation.

Add the SESPA service to an existing resource sharing context or create a new resource sharing context for the SESPA service. If the SESPA service is not manually added to a resource sharing context, the "default" resource sharing context will be used for the SESPA service.

Activate the SESPA service through the SLEE deployment service.

Installing an ESPA service capability module

The following is an outline of an installation procedure to be used when adding a new ESPA service capability to BEA WebLogic Network Gatekeeper. ESPA service capabilities are are SLEE services, so the SLEE's standard procedure for SLEE service installation is followed.

A complete procedure, including ESPA service capability configuration (if any), has to be provided in the new ESPA service capability's documentation.

Installation can be made in run-time.

Install and start the ESPA service capability through the SLEE deployment service.

Configure the ESPA service capability through the service's own OAM methods.

Add the ESPA service capability to an existing resource sharing context or create a new resource sharing context for the ESPA service capability. If the ESPA service capability is not manually added to a resource sharing context, the "default" resource sharing context will be used for the ESPA service capability.

Activate the ESPA service capability through the SLEE deployment service.

Update the SLAs for the affected service provider and application groups, see Service Provider and Application Administration.

Installing a network plug-in

The following is an outline of an installation procedure to be used when adding a new network plug-in to BEA WebLogic Network Gatekeeper. Network plug-ins are SLEE services, so the SLEE's standard procedure for SLEE service installation is followed.

A complete procedure, including plug-in configuration, has to be provided in the new plug-in's documentation.

Installation can be made in run-time.

Install and start the plug-in through the SLEE deployment service.

Configure the plug-in through the plug-in's own OAM methods.

If the plug-in type is not one of the registered plug-in types, add the new plug-in type through the Plug-in manager service.

Set up the routing through the Plug-in manager, see Routing Administration.

Add the plug-in service to an existing resource sharing context or create a new resource sharing context for the plug-in service. If the plug-in service is not manually added to a resource sharing context, the "default" resource sharing context will be used for the plug-in service.

Activate the plug-in service through the SLEE deployment service.

Connecting an external protocol adapter to the plug-in manager

The following is an outline of how to connect an external protocol adapter directly to the plug-in manager. A prerequisite on the external protocol adapter is that it implements the plug-in manager's plug-in interfaces.

The connection can be made in run-time.

If the protocol adaptor type is not one of the registered plug-in types, add the new plug-in type through the Plug-in manager service in the Network Gatekeeper Management Tool.

Install and configure the protocol adaptor according to the protocol adaptor's documentation.

This is dependent on how the protocol adaptor is implemented. If not handled automatically by the protocol adaptor, the protocol adaptor has to be registered manually through the through the plug-in manager service in the Network Gatekeeper Management Tool.

Set up the routing through the Plug-in manager, see Routing Administration.