MACROMEDIA 38000382 - Macromedia JRun - Mac, Руководство по началу работы

Страница: 21 / 132

JRun architectural model 7
For detailed information on the J2EE platform, see Chapter 3, “Introduction to J2EE”
on page 29 .
JRun architectural model
JRun has a service-based architecture, a modular design that contains pluggable services
(components) in a core server backbone.
The server backbone facilitates communication among all components or services that
plug into it. It provides a core set of services that are shared across all the components and
features of the server. The backbone provides flexibility through its ability to
accommodate various services. Services extend the core server by adding functionality,
independently of each other.
In JRun, the core server backbone is the server kernel. The services are JRun server
features, as the following figure shows:
The JRun architecture is based on Java standards, including the following:
•
Java Management Extensions (JMX)
Specifications for managing Java
environments. JMX defines the architecture and APIs for a scalable system that you
can integrate with existing management systems.
•
Java Naming & Directory Interface (JNDI)
A standard mechanism for Java-based
applications to access application components and server resources across a
distributed computing environment.
•
XML
An open, cross-platform formatting standard used for storing information
about the state of a JRun service.
JRun is built on a JMX service-based architecture, and uses JMX to provide flexible and
dynamic management and administration. JMX is an emerging Java standard for
management and customization.
JRun implements its features and functionality (for example, EJB container, web
container, and logging) as JMX services (called MBeans), plugged into the JRun kernel.
You can manage these services through the JMX-enabled JRun Management Console
(JMC) or other JMX-enabled management tools.