Not logged in | Login
ESB Console Details
ESB console allow multi level integration point for plug-ins. Integration points are hooks that ESB console provides to manage and monitoring each component in runtimes. These hooks are provided at various places and at multiple levels. For easy of use these integration points are categorized into 4
The plug-ins can be any of the following types
All the core modules of ESB console are developed as internal plug-ins. Currently it requires few additional steps in order to develop and configure the internal plug-in compared to external plug-in. Before going in detail of internal plug-ins, letâs quickly see how the external plug-ins can be developed and use the integration points to plug n play in ESB console
Communication: ESB Console communicates with the external plug-ins by passing the context values as parameters to the plug-in module entry point URL. The external plug-ins can read the context values by querying the parameters form the URL
Module Entry Point URL?name=sun-bpel-engine&entityType=service-engine&connectionKey=localhost_4848_true_admin&host=localhost&port=848&targetName=domain&packagedIn=null&deployedOn=null
Name: Component name Entity Type: Type of the component connectionKey: Server connection key, This key used to get the server connection info from the connection service of console. host: Runtime Server Name port: Runtime admin port targetName: instance name/ cluster name/ domain if it is parent packagedIn: Service assembly where the service unit is packaged in and null if the component is not service unit deployedOn: Component where the service unit is deployed on and null if the component is not service unit
void init(Component component) â Initialize your plug-in module __Note__: Call initialize (<your module root widget>) at the end of init. Pluggable getNewInstance() â return new instance of your plug-in module void onLoad() â this is called when the user access the integration point to play the plug-in module on the console
Register your internal plug-in module in the console internal plug-ins registry as follows
registeredWidgets.put("uri://<Entry Name, this should be unique from other core registry entries. > ", new YourInternalPluginModule());
Note: This requires rebuild and deployment of ESB console. Currently we are working on the dynamic linking of internal module, so this approach might change as we proceed on the dynamic linking. Keep tuned to ESB console development mailing list.
Communication: Incase of internal plug-ins the context values as part of component object to the init method. The all context parameter mentioned for the external plug-ins are part of the component object.
When you have you plug-in module ready the nest step is to configure your plug-in.
Plug-ins are configured in an XML configuration file. All the core plug-ins of the console are configured in an internal configuration file called defaultnodes.xml. These configurations can be done in an XML file manually or by using the ESB consoleâs rich plug-ins configuration editor. The configuration editor not only simplifies configuration tasks but also allows applying configurations to the console on the fly. A simple configuration file looks as follows.
<esb-console-plugin name='BPEL Plugin' targetComponentName='sun-bpel-engine' version='1.0' xmlns='http://java.sun.com/xml/ns/esb/console/PluginData'> <pluginType customPluginType='Management' entityType='service-engine' uiIntegrationType='tree-node'> <parentId entityType='ServiceEngines'> Service Engines </parentId> <displayName> sun-bpel-engine </displayName> <urlEntryPoint isRelativeToContextRoot='false'> <Your module entry point URL goes here> </urlEntryPoint> <imageUrl> <Your module image icon URL goes here> </imageUrl> </pluginType> </esb-console-plugin>
One plug-in configuration file define configurations for one target component i.e. one configuration file for each target component. The root node of the configuration file defines the context of the plug-in types defined in the file.
<esb-console-plugin name='BPEL Plugin' targetComponentName='sun-bpel-engine' version='1.0' xmlns='http://java.sun.com/xml/ns/esb/console/PluginData'>
name: Logical name to the configuration file.
targetComponentName: Component name, to which the configurations to be applied
version: Version of the configuration file
Define pluginType entry for each plug-in. The attributes of the pluginType represents the appropriate integration point on the console i.e. in the above example
entityType represents the type of the component to which you want to plug your module to.
uiIntegrationType represents the place holder of the integration point on console.
parentId is applicable for only plug-ins with uiIntegrationType=âtree-nodeâ, which means that this plug-in is a node of the component tree on the console explorer. In which case the parent ID is required and represents the parent node on the tree under which you want to display your plug-in.
displayName is the name of the plug-in and is the name of the integration point to display on the console.
urlEntryPoint represents the plug-in location. In case of external plug-in this contains fully qualified URL of the plug-in module and in case of internal it contains the URI:// followed by full class name. The attribute isRelativeToContextRoot is used in case of external plug-in configuration, if it is true that mean the URL is relative and the plug-in module is deployed on the same server as ESB console and false means the URL is a fully qualified URL and the module is remote to ESB console.
imageURL is the display icon/image of the plug-in on the console. It can be either local (relative URL) or remote (fully qualified URL).
For more plug-in samples go to http://wiki.open-esb.java.net/Wiki.jsp?page=ESBConsolePluginType
After you configure your plug-ins the next step is load your plug-in configurations to the console.
Plug-in configurations are loaded using any of the following
Plug-in Manager: Plug-in manager allows you to
Access plug-in manager from the welcome (Common tasks) screen
Use the plug-in manager to manage plug-ins
Deploy plug-in utility (Under development): This utility allows you to
Plug-in Editor (Under development): Plug-in Editor is rich configuration editor.
Command line tool (Under development): Use command line tool to