Jiro technology

1. Submitted by:
HEENA MADAN
12/CS06

2. • Introduce by SunMicroSystem
• Managing Distributed Resource.
• Platform independent
• Web based GUI’S and Management
App

3.  Jiro is a Management Framework
infrastructure based on a distributed runtime
environment.
 It was standardized as JSR 9 by the Java
Community Process.

4. • Integrated and Automated Management
Software.
• A standard extension to the Java platform, is
specified by the Federated Management
Architecture (FMA).
• Jiro goes further than just platform
independence, however, and introduces Jini-
connection technology for distributed
management across a network.

5.  Jiro divides a management environment into
domains.
 Each domain only a shared management
server (a Java Virtual Machine running Jiro
services) that represents the domain as a
whole.

6. MANAGEMENT CONSOLE
STATIC
MANAGEMENT
SERVICES
DYNAMIC
MANAGEMENT
SERVICES
JIRO TECHNOLOGY
CIM
DEVICES
SNMP
DEVICES
OTHER DEVICES
Distributed
Management
logic
layer

7. • The requirements for this middle tier were
determined by an analysis of distributed
management and the resources that need to
be monitored and controlled.
• There may be several resources processing
the data as it moves from the application to
its eventual destination -- a disk drive, for
example
• Separating the control path from the data
path

8.  Jiro introduces a middle tier of management
between the client/GUI and other Java-based
agent technologies such as JMX and JDMK.
 This middle tier is where the automation of
management take place.

9. • Partition the Management environment
• private management servers can host management
services that are specific to their hosts
• The servers (including the shared server) can be
replicated to achieve higher availability.
• These servers form an intra domain federation for
the management domain. The shared management
servers can also communicate with each other.

10. STATIC
SERVICES
DYNAMIC
SERVICES
SERVICES

11. • known as FederatedBeans base services -- are a
guaranteed part of the environment in a
management domain. The base services include
transaction, controller, logging, events, and
scheduling.
• They are available for use by the clients and
services belonging to a management domain, and
do not depend on the dynamic services model.
• There is only one of each type of service available in
each management domain.

12. • These base services are located with the ServiceFinder
convenience class, as shown below:
 public final class ServiceFinder
 {
 private ServiceFinder() {}
 public static TransactionManager
 getTransactionService()
 throws ServiceNotFoundException;
 public static ControllerService
 getControllerService()
 throws ServiceNotFoundException;
 public static LogService
 getLogService()
 throws ServiceNotFoundException;
 public static EventService
 getEventService()
 throws ServiceNotFoundException;
 public static SchedulingService
 getSchedulingService()
 throws ServiceNotFoundException;
 ...}

13. • The Transaction service is a Jini transaction manager serving
a particular management domain.
• The Controller service provides for the reservation of
ownership within the management domain.
• Management software can use the Log service to log
decisions and state changes, as well as to maintain audit trails.
• The Event service provides a set of topics to which
management services can post and listen. This allows
management services to react to both changing conditions in
the environment and decisions that other management
services have made.
• The Scheduling service allows a management service to
perform periodic or scheduled operations, such as polling.

14. • The FederatedBeans dynamic services model
extends Java's Remote Method Invocation (RMI)
to support the higher level of abstraction
appropriate for management application.
• Additional management capabilities (security,
transaction, controller) that can be added to any
Jiro-based component
• Transactional persistence
• Remote class method (procedural) invocations
• Remote object instantiation

15. •The first set of Jiro components that need to be developed for
these situations are called Management Facades.
•The resource vendor typically develops the Management
Facades for its products that enable the products to be
managed by Jiro -based software.
•FederatedBeans components will typically use a standard
protocol, such as SNMP, to talk to the resource (in the case of
a device or system) or native library (in the case of software).
•We'll create two FederatedBeans components for this
example. The first component maintains a pool of spare disks
that can be used for multiple applications and hosts in the
storage network.

16. •The second FederatedBeans component will monitor file
system utilization and try to predict when the file system
will run out of space.
•It accesses usage information from the filesystem's
Management Facade and tracks its usage over time.
After predicting an out-of-space condition based on the
history of past usage, it then calls the Storage Pool Bean
to get a disk from its pool.
•When the Storage Pool Bean gets the request for the
disk, it calls the switch's Management Facade to change
the zone of the newly allocated disk to that of the host

17. • Jiro makes possible software that can
increase availability and help reduce the
cost and complexity of management.
• The new paradigm for management
software is multiple-vendor creation and
reuse of these FederatedBeans
components.