![]() ![]() ![]() ![]() ![]() ![]() |
The following section describes configuration and maintenance attributes and operations for the Plug-in manager. It also provides a workflow for the configuration:
Network protocol plug-ins consist of two parts: the plug-in service and the plug-in instance.The plug-in service is the deployable and updatable unit. It does not itself process any traffic. Plug-in instances are instantiated from a plug-in service. One plug-in service can be the base for many plug-in instances.
Plug-in instances are created using the Plug-in Manager MBean.
The plug-in manager introspects the plug-in north interfaces, methods, and names of any arguments. This is useful when creating up service provider group and application group SLAs.
When an application’s request is processed, it is routed to the network protocol plug-in instance via the plug-in manager. The plug-in manager triggers a chain of service interceptors, where the request is evaluated and a given plug-in instance is selected based on:
Once the decision has been made, the request is forwarded to the selected plug-in.
Routes are configured in the Plug-in manager via OAM operations, and are used by the service interceptors.
Refer to the section in this guide for each communication service for the plug-in service ID and plug-in type under which individual plug-ins are registered.
The following interceptors are use data configured using the plug-in manager:
When a request is triggered from the network, the plug-in manager is also part of the request flow, and is responsible for invoking the chain of service interceptors.
Address ranges are specified using UNIX regular expressions. A few examples are given below:
The address scheme can be included in the expression. If not specified, any scheme will match. Examples
Configuring the plug-in manager can be divided into:
Below is an outline for configuring the plug-in manager:
Below is an outline for creating an instance of a plug-in service:
The administration of routes uses the following operations:
A node ID is assigned to one or more plug-in instance IDs to enforce node SLAs,. The node ID is then referred to in the node SLAs.
Managed object: Container ServicesPluginManager
MBean: com.bea.wlcp.wlng.plugin.PluginManagerMBean
Below is a list of attributes and operations for configuration and maintenance:
Specifies if a network protocol plug-in service is allowed to transition to state ACTIVE if it fails to establish a connection with the underlying network node during deployment or re-deployment. This assures that a new version of the network protocol plug-in service is activated only when it is certain that it can accept traffic.
If enabled, all plug-ins services packaged in the EAR that is being updated must become active before any traffic is routed to the plug-in instances derived from the new version. If any plug-in instance fails to connect to the underlying network, the new version does not become active.
Specifies whether policy based routing should be used.
Note: | Policy based routing must be enabled in order to enforce node SLAs. |
Adds a new plug-in route. A route is identified by the plug-in instance ID and a match pattern.
addRoute(PluginInstanceId: String, AddressExpression: String)
ID of the plug-in instance that is the target of the route. A list of plug-in instance IDs is displayed using the Operation: listPluginInstances.
|
|
The pattern to be used as a matching criteria. See How address ranges are specified when setting up routes.
|
Creates a new instance of a specific plug-in service.
createPluginInstance(PluginServiceId: String, PluginInstanceId: String)
ID of the plug-in service to instantiate. See Operation: listPluginServices for a list of plug-in service IDs.
|
|
All existing instances can be displayed using Operation: listPluginInstances.
|
Destroys an instance of a specific plug-in instance. All routes associated with the instance are kept.
destroyPluginInstance(PluginServiceId: String, PluginInstanceId: String)
Gets information about a specific plug-in instance. The information includes:
getPluginInstanceInfo(PluginInstanceId: String)
Displays which plug-in node ID a plug-in instance is associated with, if any.
getPluginNodeId(PluginInstanceId: String)
Displays information about a plug-in service. The information includes:
getPluginServiceInfo(PluginServiceId: String)
Displays information about a service type. The information includes:
This list is useful when setting up SLAs.
getServiceInfo(Type: String)
ID of the service type. See Operation: listServiceTypes.
|
Displays a list of plug-in instances IDs.
<Plug-in instance ID>#<JEE application name>#<version of JEE application>
The plug-in instance ID is the part of each entry up to the first #.
listPluginInstances()
Displays a list of plug-in service IDs. A plug-in service ID uniquely identifies a plug-in service.
listPluginServices()
Displays a list of all registered routes.
listRoutes()
Displays a list of service types. The service types defines a collection of plug-in services exposing a specific functionality in the network.
listServiceTypes()
Removes a route. The route is identified by the ID of the plug-in instance and the matching pattern.
removeRoute(PluginInstanceId: String, AddressExpression: String)
The pattern used as a matching criteria. See How address ranges are specified when setting up routes.
|
Assigns a node ID to a plug-in instance.
setPluginNodeId(PluginInstanceId :String, nodeId: String)
![]() ![]() ![]() |