Skip to main content

Systems Management Framework for Distributed Environments

A custom-coded Java framework for administering a distributed WebSphere environment.

Date Posted: September 28, 2006

alphaworks tab navigation

 

What is Systems Management Framework for Distributed Environments?

Systems Management Framework for Distributed Environments is a custom-coded framework for administering a distributed WebSphere® environment. (There are two other ways to administer a distributed environment: using Web Consoles or scripting using WSADMIN.) Because WebSphere exposes its configuration as MBeans that run on an MBean Server (for example, the deployment manager of one's cell), it is possible to connect to this server using the JMX (Java Management Extensions) API, to read or create MBeans of interest, or to change the attributes and store the MBeans on the server again.

This framework provides a single point for executing system management tasks in a distributed environment. It is not limited to WebSphere: It can also be used to administer WebSEAL or other external systems. The framework is easy to use by simply changing the provided XML configuration files, and it is easy to extend by providing a new XML file and writing a single Java™ injector class.

In addition, there are agents that run on the different physical machines in the environment and listen to incoming requests for changes in the configuration. For example, an agent on the WebSEAL host can create a new WebSEAL instance and junctions.

How does it work?

A set of XML files is included for the most common components. Configuration data is stored in these files. There is, for example, a cluster.xml file that can be used and changed in order to set up a WebSphere Application Server cluster. All changes to the WebSphere environment are made on the deployment manager to which it connects using the JMX API.

When the framework is run, an injector class (in this example, a cluster injector) reads the configuration of the XML file, connects to the MBean server, gets the existing cluster object or creates a new one, and makes the changes specified in cluster.xml.

About the technology author(s)

Marco Seifried

Marco Seifried is a Senior IT Specialist working in the Pan-IOT Cross Brand Services Team for the IBM Hursley Laboratories, U.K. He has worked in the WebSphere area for six years and was involved in projects for major clients all around the world. Mr. Seifried works as both an IT architect and IT specialist. His skills and interests include WebSphere Application Server, WebSphere Portal Server, Web Content Management Systems, and J2EE development and performance tuning. He holds several product certifications in WebSphere products. Mr. Seifried is a regular speaker at international conferences and has published several articles on developerWorks.


Jacek Zimorodzki

Jacek Zimorodzki is a consulting IT specialist in the Pan-EMEA cross-brand services team at IBM Hursley Labs. His main areas of interest are J2EE development; WebSphere management and performance tuning; and systems scalability and high availability. During team engagements, he has completed several critical missions in all areas. Mr. Zimorodzki has deep cross-brand skills in such areas as WebSphere, Tivoli, Rational, and Data Management. As a certified IT specialist, he led several development and subscription and support teams.

Remigiusz Galka is an IT Specialist with IBM's CEMAAS WebSphere Services group in Poland. He has extensive experience with WebSphere Portal, WebSphere Application Server, and messaging-oriented infrastructures based on MQ Series and SIBs. Mr. Galka took leading roles in designing and implementing heavily-customized, high-performance systems using those products. He has five years of experience in WebSphere Application Server systems architecture.

Trademarks