Administrative interface for WSRP Open Source Project

Here is a note on the administrative structure that is planned for the Enterprise class WSRP Open Source Project (OSP) on java.net. The intent is to provide flexibility in system composition such that the WSRP component could be used without much modification to adapt to new environments.

The administrative interface is provided in terms of Mbeans. These Mbeans that can be deployed on any/existing Mbean server that enables management of the WSRP component.  The user interface (UI)  for these Mbeans (clients) are provided as portlets. Since the user interface is provided as portlets, these portlets can be deployed on to any standard portlet container.

The above componentization provides flexibility in terms of recomposing  and integrating the WSRP project into any environment or existing system that suites a variety of needs. For e.g. it allows the Mbeans to be deployed on an existing Mbean server that manages a larger set of services which is integrated with WSRP.

To be more specific the WSRP OSP project would provide the following MBeans for managing the WSRP Producer and Consumer separately. These Mbeans could be reused when deploying or recomposing the system other than the default bundled configuration/deployment.
  1. WSRP Producer Mbeans
    • WSRPProducerManagerMBean
    • WSRPProducerMBean
  2. WSRP Consumer
    • ConsumerMbean
    • ConfiguredProducerMBean
    • RemotePortletManagerMBean
Apart from providing the above Mbeans.  The WSRP OSP project as such will provide a default sample Mbean server that demonstrates the deployment and management of these Mbeans on to a Mbean server which runs as a separate process.

The user interface for above Mbeans is provided in terms of portlets namely
  1. WSRP Producer Admin  Portlet and
  2. WSRP Consumer Admin  Portlet.
The administrative portlets could be deployed on to any standard Portlet Container that  provides an environment for executing these portlets. Again providing the UI in terms as portlets also provides the flexibility to reuse and recompose the system to suite various needs.

The portlet administrative interface is a demonstration on the usage of public WSRP OSP Mbeans that are exported by the system. Its be possible to write a CLI (command line interface) that uses these same Mbeans also opens up the possibility of integrating the WSRP OSP with existing systems where an unified admin console of CLI would be required.

The default deployment architecture of the WSRP OSP project is as follows.
  1. The system provides a default Mbean server where the WSRP OSP Mbeans are deployed, this runs as an independent process.
  2. The WSRP Producer and the Consumer are deployed over a web container along with the Portlet Container. This is where the WSRP environment exists.
  3. The WSRP OSP admin portlets are deployed over any standard portlet container that provides the UI for the above deployed Mbeans.
The pictorial representation is as shown below :



<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"> </script> <script type="text/javascript"> _uacct = "UA-898027-1"; urchinTracker(); </script>
Comments:

Hi Rajesh, Good blog on WSRP. Keep it up. I have added your blog to http://www.portletsfactory.com, a blogs aggregator on portal technologoy. -- Punit Pandey http://portlets.blogspot.com

Posted by Punit Pandey on November 03, 2006 at 07:34 PM IST #

Post a Comment:
Comments are closed for this entry.
About

trajesh

Search

Categories
Archives
« July 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  
       
Today