Home > Articles > Programming > Java

Jiro Storage Networks

2.6 Inside the Federated Management Architecture

The first thing to keep in mind with FMA and Jiro is that no single piece of hardware or communication protocol is "the best" for a particular class of device. All the protocols and devices have a place and a need to fill. Direct attach storage is fast for a workstation user but unrealistic when placed in the context of an enterprise network that has hundreds of users accessing the shared data. Parallel SCSI architectures can deliver great bandwidth over a short distance for servers, but they do not address the flexibility that storage networks offer. Storage networks—specifically, SANs—can address limitations in DAS and parallel SCSI architectures but are more costly to implement. Unfortunately, the use of each type of device and software leads to a management challenge.

The realization that a variety of management styles exist in a storage network is the driving factor behind the Federated Management Architecture. FMA is an umbrella management architecture that allows heterogeneous storage resources to coexist without increasing the complexity of management.

To that end, FMA provides programmers with facilities for dynamic discovery and expansion of the software used to manage storage. It also provides a common architecture and services for use in building software components that manage software and hardware in the storage network. The architecture is built so as to provide component reuse at different levels.

Here's an example of how to use an SRM built with the Federated Management Architecture:

  1. Coffee House Inc. owns a switch from switch vendor A, disk arrays from Sun Microsystems, and Sun Solaris and Windows NT servers.

  2. A series of Jiro FederatedBeans components are deployed on the Sun Solaris machine and the Windows NT servers. These components manage resources that are physically attached to the machine, such as any direct attach storage, file systems, or volume managers. Components deployed on these systems also manage devices that have control points accessible to the machine but may not be capable of running a JVM for hosting a FederatedBean of its own. An example of this scenario is a fibre channel switch that has a port with a Web server for out-of-band management. The Jiro FederatedBean that manages the switch actually exists on the Sun Solaris machine. Calls to the bean are forwarded to the switch via the Web interface on the switch.

  3. A second set of Jiro FederatedBeans components deployed on the servers adds policy-based management capabilities to the "pass-through" nature of the beans discussed in point 2.

  4. A storage resource manager dynamically discovers the Jiro FederatedBeans components in the network and provides the status of the storage network and the policies that are running in the network. The user of the SRM can modify the storage network and policy rules from the SRM user interface.

  5. Coffee House Inc. purchases a new disk array and attaches it to the fibre channel switch.

  6. Because this disk array is from a new vendor (a cost decision on the part of Coffee House Inc.), a new Jiro FederatedBean is deployed to both the Windows NT server management domain and the Solaris management domain. The FederatedBean was supplied by the disk array vendor along with deployment instructions. 6 The SRM does not have to be used in this step unless it makes the installation easier than that of the vendor that provided the Jiro FederatedBeans. For example, the SRM may be able to recognize the new device in the network (through one of its own Jiro FederatedBean policy components) and download a Jiro FederatedBean from the vendor's Web site.

  7. A Jiro FederatedBean policy on the Windows NT server and a similar one on the Sun Solaris server recognize the addition of a RAID device via an event from the Jiro FederatedBean managing the switch. The policies negotiate with each other based on predicted storage need. The "winner" then calls the Jiro FederatedBean responsible for the switch to allocate the array (zone) to the Solaris host. After zoning is complete, the policy calls the volume manager FederatedBean and the file system FederatedBean to make the space on the new disk array usable by clients.

In this scenario, the SRM software is merely a client to the many continuously running software components that manage the servers and connected hardware. You can have the SRM software take on many different forms—Web-based, application-based—by adapting the user interface rather than rewriting the software. Because Jiro FederatedBeans are remote objects, you can bring up the SRM from any location in the network for management of all storage resources that have Jiro FederatedBeans representations. You may be able to develop generic FederatedBeans for devices that do not have beans already built for them, depending on how well those devices fit to standards. For example, you would not have to build a FederatedBean for a device that exposes all control points via a standardized WBEM model.

With this scenario in mind, let's look briefly at what Sun's Java, Jini, and Jiro architectures can bring to the table in terms of programming environment, programming model, and architecture and design. This discussion is very high-level because the implementation of this discussion is the topic of the book as a whole.

2.6.1 The Java Programming Language

Simply put, creating management applications for heterogeneous environments would be difficult, if not impossible, without the Java programming language. The following strengths of Java are leveraged in creating a solution in the scenario described in Section 2.6:

  • Platform independence. The Coffee House scenario has two operating systems and processor architectures involved for servers: Windows NT and Sun's Solaris operating system. Because of Java's Virtual Machine, the differences between the platforms are nullified from a programmer's perspective.

  • Network capabilities. Java's distributed object technology, RMI, enables distributed object management by piggybacking onto Java's platform independence. The data streams passed to and from distributed objects on different operating systems and hardware architectures contain data that is formatted according to the JVM specification and not according to the underlying platform architecture.

  • Portable code. Java's remote codebase capabilities allow classes that do not exist in the space of one JVM to be loaded dynamically from a remote Web server. This makes implementation code extremely portable and dynamic; as long as interfaces are known at programming time, new implementations can be deployed during runtime of the system.

Simply put, Java is the most advanced platform-independent object-oriented programming language available. Every year Java becomes faster, more stable, and more feature-rich. Other object infrastructures could handle a heterogeneous distributed management environment, but there are no others that allow code to be moved over as wide of a range of operating systems and hardware architectures as Java. This is a critical point when you're looking at how to create a management environment that truly handles heterogeneous managed resources.

2.6.2 The Jini Platform

Jini combines with the distributed object capabilities of Java to create a truly dynamic service environment. An oversimplified description of Jini is to compare it to Web search engine services. Jini leverages the multicast network capability to discover lookup services (the search engine). After you've found a lookup service, you can construct a query to submit to the lookup service, and the lookup service returns network proxies to the services that fit the query. You can then use the remote service from the client to query data.

Because Java can move code to a client during runtime via the remote codebase, your management program can use a service that is found in a Jini lookup server that you may not have known about when you wrote your program. The disk array added in the Coffee House scenario can be installed, discovered by your client, and managed without the need to restart the management client or any of the servers.

Jini is also a well-behaved system. If a server were to crash, the Jini group would remove services that are no longer available using its landlord/lease mechanism (see section 5.3).

2.6.3 The Federated Management Architecture and Jiro

Even with Java and Jini available, the technology is still applicable to a very broad domain. Java can be used to solve virtually any computing problem, and Jini is a platform to create self-healing groups and federations of devices and services. The Federated Management Architecture defines specific services that are required to be available in a Jini group as well as behaviors of components that exist to manage resources. These services and behaviors are defined specifically to address the needs of the domain of management application programming.

For Coffee House, FMA defines the architecture of the components to represent the managed resources and also defines how those components should be deployed, where they should run in the network, and how they can be found in Jini. A specific example of how FMA ties into the Coffee House scenario can be found in the handling of the addition of a new disk array. Policies exist on both the NT machine and the Solaris machine. Upon entering the network, the disk array delivers an event for which both policy components listen. This event can be consumed by the first policy that receives the event, or the policies could simply observe the event and construct a separate negotiation mechanism. The event chaining and delivery mechanism that enables either behavior is defined by FMA.

Jiro implements the behaviors defined by FMA. The Jiro implementation also adds many helper capabilities and tools to ease creation and adherence to FMA.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020