The Graphical BPEL Monitor described in my previous blog entry "Graphical
BPEL Monitoring and Usage Statistics" can be integrated into the
Open ESB "Enterprise
Service Bus Console" in a number of simple steps. This quick blog
entry will take you through the integration process and hopefully show
the power of the ESB Console framework.
Before we can integrate the Graphical BPEL Monitor you will need to download the latest ESB Console. This can be done as either a pre-built war or, if you are registered, you can download the source and build a war based on the latest source. I will assume that you have downloaded and built the ESB Console as per the instructions on the ESB Console Wiki and hence you have generated the esb-console-1.0-SNAPSHOT.war file in the target directory. I renamed mine to esb-console.war to allow Glassfish to generate the name I wanted for the context root.
So now we have generated the esb-console.war you need to deploy this in the Glassfish instance running the BPEL2SVGMonitorWebApplication.
Once the esb-console.war has been deployed we will need to modify its defaultnode.xml file. This can be found in the glassfish\domains\domain1\applications\j2ee-modules\esb-console\data directory. The following changes need to be made :
ESB Console Integration
Now we have modified the ESB Console we can navigate to the sun-bpel-engine tree node and select it.You will notice that a new Tab "Instance Monitor" has appeared. If we select this the Graphical BPEL monitor will be displayed within the main ESB Console as below. As you can see this was a fairly quick and painless integration process.


ESB Console
Before we can integrate the Graphical BPEL Monitor you will need to download the latest ESB Console. This can be done as either a pre-built war or, if you are registered, you can download the source and build a war based on the latest source. I will assume that you have downloaded and built the ESB Console as per the instructions on the ESB Console Wiki and hence you have generated the esb-console-1.0-SNAPSHOT.war file in the target directory. I renamed mine to esb-console.war to allow Glassfish to generate the name I wanted for the context root.
So now we have generated the esb-console.war you need to deploy this in the Glassfish instance running the BPEL2SVGMonitorWebApplication.
Configuring the Console
Once the esb-console.war has been deployed we will need to modify its defaultnode.xml file. This can be found in the glassfish\domains\domain1\applications\j2ee-modules\esb-console\data directory. The following changes need to be made :
- Add a new Instance Monitor definition that defines the
BPEL2SVGMonitorWebApplication
<!-- Instance Monitor -->
<pluginType customPluginType='Instance Monitor' entityType='SERVICE_ENGINE' uiIntegrationType='tab'>
<imageUrl>/tree/sa.png</imageUrl>
<urlEntryPoint isRelativeToContextRoot='true'>/BPEL2SVGMonitorWebApplication</urlEntryPoint>
</pluginType>
<!-- **************** -->
<!-- Tab Plugins ends -->
<!-- **************** -->
- Edit the Service Engine Tabset definition and add the new
"Instance Monitor" Plugin type.
<!-- Service Engine Tabset -->
<tabsetType name='Service Engine Tabset' tabs='Status, Runtime Configuration, Descriptor, Log Settings, Statistics, Endpoints, Instance Monitor, Help' />
ESB Console Integration
Now we have modified the ESB Console we can navigate to the sun-bpel-engine tree node and select it.You will notice that a new Tab "Instance Monitor" has appeared. If we select this the Graphical BPEL monitor will be displayed within the main ESB Console as below. As you can see this was a fairly quick and painless integration process.










Very nice post. Thanks.
Posted by petro on March 02, 2009 at 01:43 AM GMT #