Oracle® Communications Service Broker Processing Domain Configuration Guide Release 6.0 Part Number E23525-02 |
|
|
View PDF |
This chapter describes how you can deploy, activate, and deactivate Oracle Communications Service Broker's supplementary modules in your deployment.
You can manage supplementary modules, including adding, activating, deactivating, and removing supplementary module instances, using the SM Configuration screen.
To access the SM Configuration page:
In the domain navigation pane, expand OCSB.
Expand Processing Tier.
Expand Supplementary Modules.
A list of currently deployed Supplementary Modules is displayed.
From the module list, select the module instance that you want to configure.
The SM configuration pane displays information about each module instance in the fields described in Table 36-1.
Table 36-1 Configuration Page Fields
Field | Description |
---|---|
Instance Name |
Displays a name of the module instance |
Module Type |
Displays a type of the module instance. Possible values:
|
Version |
Displays a version of the module instance |
State |
Displays a state of the module instance. Possible values:
|
The SM Configuration screen enables you to perform the following actions:
Add a new supplementary module instance.
Activate a supplementary module instance.
Deactivate a supplementary module instance.
Remove a supplementary module instance.
Note:
After adding a new supplementary module, you must click the Commit button. You will be able to configure the module only after clicking Commit.Service Broker provides a set of MBeans that expose attributes and operations for configuring supplementary modules through JMX. Figure 36-1 shows the hierarchy of the supplementary modules management MBeans.
The following sections provide reference information for the supplementary modules management configuration MBeans.
DeploymentsMBean is a container for instances of DeploymentMBean. Each instance of DeploymentMBean represents an individual supplementary module.
Created automatically
None
void addDeployment(string ModuleName, string Version, string Name)
Adds a new instance of a supplementary module. Table 36-2 explains the parameters with which you need to invoke the operation.
Table 36-2 Parameters Required to Create a Deployment
Parameter | Description |
---|---|
ModuleName |
Specifies a type of the module instance and a protocol that the module instance uses. Possible values:
|
Version |
Specifies a version of the module instance |
InstanceName |
Specifies a unique name for the new supplementary module instance. |
void removeDeployment(string ModuleName, string Version, string ModuleInstanceName)
Removes an instance of a supplementary module. For more information on the parameters required for this operation, see Table 36-2.
void activateDeployment(string ModuleName, string Version, string ModuleInstanceName)
Activate an instance of a supplementary module. For more information on the parameters required for this operation, see Table 36-2.
void deactivateDeployment(string ModuleName, string Version, string ModuleInstanceName)
Deactivates an instance of a supplementary module. For more information on the parameters required for this operation, see Table 36-2.
Each instance of DeploymentMBean represents an individual supplementary module and defines configuration parameters for this module.
Deployments.addDeployment()
DeploymentStatus
Family
Name
Version
For more information on these attributes, see Table 36-1.
void activate()
Activates the instance of a supplementary module
void deactivate()
Deactivates the instance of a supplementary module