IBM®
Skip to main content
    Country/region [select]      Terms of use
 
 
    
     Home      Products      Services & solutions      Support & downloads      My account     
 
developerworks > My developerWorks >  Dashboard > WebSphere eXtreme Scale V6.1 User Guide > ... > Monitoring applications > Management gateway process overview
developerWorks
Log In   View a printable version of the current page.
Overview Connect Spaces Forums Wikis
Management gateway process overview
Added by joshuad, last edited by bsandman on Jan 26, 2009  (view change)
Labels: 

Getting Started Examples Reference API documentation

See the WebSphere eXtreme Scale Wiki for links to eXtreme Scale Version 7.0 documentation.
If you log in with your developerWorks ID, you can leave comments and feedback for the development team.

ObjectGrid provides a system management infrastructure with which you can monitor and administer static ObjectGrid topology deployment environments. The system management architecture is a three-tiered approach: a user client connects to the management gateway server, which makes an ObjectGrid client connection to an ObjectGrid cluster. The management gateway is not needed for dynamic ObjectGrid deployment topologies.

Figure 1. System management diagram

The management gateway client tier contains any program that uses Java Management Extensions (JMX) to connect to the management gateway server. Any third-party JMX console as well as a client program that uses MX4J application programming interfaces (APIs) are included. The ObjectGrid client tier consists of the management gateway server. The management gateway acts as a server for the management gateway client tier and as a client to a functioning ObjectGrid cluster in the server tier. Also, an ObjectGrid client program can call the same APIs that the management gateway server calls if the user does not want to use JMX. Finally, the server tier consists of an ObjectGrid cluster.

The management gateway contains a set of managed beans (MBeans) and uses JMX to administer and monitor the ObjectGrid environment and is implemented by the MX4J open source project. MX4J is shipped with ObjectGrid.

The ObjectGrid JMX and MBean administration model was created to take advantage of the various JMX consoles that are available for administering JMX environments. You can put together dashboards using the JMX console of your choice. Consoles can be attached to the MBeans running on the management gateway Java virtual machine (JVM) and dashboards can be assembled using these MBeans. Consoles offer graphical histories or charts of numerical and string values.

Two options are provided for running system management commands.

  • Call any command through the client-server infrastructure that is currently in place with the ObjectGridAdministrator interface.
  • Use JMX to call these same commands, with the ObjectGrid MBeans acting as a wrapper to the ObjectGridAdministrator interface.

Additional information

Wiki Disclaimer and License
© Copyright IBM Corporation 2007,2009. All Rights Reserved.
Docs Starting a management gateway process (WebSphere eXtreme Scale V6.1 User Guide)


 
    About IBM Privacy Contact