04-01-2010, 08:16 PM
JIRO
Jiro(pronounced gyro as in gyroscope) is a Sun product that provides the infrastructure and plumbing for building distributed applications. Distributed services such as event handling, logging, transaction management, security, as well as basic communication services for distributed objects are included.It is written in Java and uses the Jini¿ name and lookup services. It is a product implementation of the Federated Management Architecture, which is a three tier architecture consisting of clients, mangement services and managed resources. This technology provides a middle layer of components and services that facilitate connectivity between managed resources and management applications. These resources can be anywhere on the corporate network, connected with any combination of routers and hubs, and use any standard management protocol such as Simple Network Management Protocol (SNMP).The code is platform-independent, enabled with a Java Virtual Machine.The Jiro management layer supplies basic management functions such as fault notification, scheduling, distributed logging, and transaction rollback.
A product based on Jiro technology is an implementation
based on the Federated Management Architecture (FMA) Specification, which describes extensions to the Java? language environment. FMA
Specification defines a component model called the FederatedBeans model.The success of the initiative
surrounding the Jiro technology will be availability of a wide variety of FederatedBeans
components from different suppliers. The FMA platform supports automated
communication between networked Java Virtual Machines, thus promoting applications
that are federations of the constituent components.
The Jiro Technology Solution
The need for the Jiro technology because of a storage sector dominated by point
products that are not compatible with each other.of information that are difficult to
integrate, complex to manage, or that actually prohibit cross-platform information
management are the problems of the present storage landscape.Its history began when it was decided to develop a Java
language extension designed to make it easier for the developer to create new storage
management applications, enable faster design cycles, lower development costs, and offer
a wider market potential.This project also intended to remove the need to conform to multiple
APIâ„¢s and interface specifications.
The High Level Architecture
-the representation of the resources to be managed,
-the interaction with the wishes of the user
-the computational logic that is needed in order to translate the wishes of the users into
the desired actions
The three tiers of the system are
1) Client/Presentation:
It may be as simple as an administrator sitting infront of his console but It is necessary to be able to initiate actions from CLIâ„¢s, scripts, periodic
schedulers, and components of the management system itself.
2)Logic:
contain the actual programs that are the applications implementing
the logic needed to perform management decisions and management functions.The applications commonly contain a number of modules, architectural subapplications,The FMA specifically defines such a
component model, i.e., FederatedBeans.
that deal with various aspects of the overall tasks to be performed
3)Resource/Information:
contains both the physical hardware
used to create the storage resources: the disks, tapes, disk subsystems, automated
libraries, channel interconnects, storage area networks etc.
Full seminar report pdf:
[attachment=1031]