Java ES service quality components enhance the quality of services provided by system service components or distributed application components. Some are availability components that are used to provide for near-continuous system uptime, some are access components that are used to support secure end-user access to system services, and others are system management components that are used to enhance the serviceability of Java ES solutions.
The components that support Java ES services components are grouped into the following categories and described in this section:
Availability components provide for near-continuous uptime for system service components and application components. The following Java ES availability components are described in this section:
Sun Java System High Availability Session Store (HADB) provides a data store that can be used to make application data available even in the case of failure. This capability is especially important for restoring state information associated with a client session. Without this capability, failure during a session requires that all operations be repeated when the session is reestablished.
The following Java ES components provide services that store session state information: Application Server, Access Manager, and Message Queue. However, Application Server is the only component that can use HADB services to maintain session state during failure.
The Java ES installer provides HADB as a single installable component. However, a server and a client subcomponent are both required to provide HADB services.
Sun Cluster components are supported on the Solaris platform only.
Sun Cluster software provides high availability and scalability services for Java ES and for applications based on the Java ES infrastructure.
A cluster is a set of loosely coupled computers (cluster nodes) that collectively provide a single client view of services, system resources, and data. Internally, the cluster uses redundant computers, interconnects, data storage, and network interfaces to provide high availability to cluster-based services and data. Sun Cluster software continuously monitors the health of member nodes and other cluster resources and uses the internal redundancy to provide near-continuous access to these resources even when failure occurs.
The Java ES installer provides the Sun Cluster Core subcomponent and the Sun Cluster Agents as separately installable components. The following Sun Cluster agents are included in Java Enterprise System.
HA in the following list stands for high availability.
HA Application Server
HA Message Queue
HA Directory Server
HA Messaging Server
HA Application Server EE (HADB)
HA/Scalable Web Server
HA Instant Messaging
HA Calendar Server
HA Apache Tomcat
HA Apache
HA DHCP
HA DNS
HA MySQL
HA Sun N1 Service Provisioning
HA NFS
HA Oracle
HA Samba
HA Sun N1 Grid Engine
HA Solaris Containers
The list of agents is not the same on SPARC and x86. For detailed information about Sun Cluster Agents, see Sun Cluster documentation at http://docs.sun.com/app/docs/prod/entsys.5.
Sun Cluster Geographic Edition is a layered extension of Sun Cluster software. This extension protects applications from unexpected disruptions by using multiple clusters that are geographically separated and a redundant infrastructure that replicates data between these clusters. Java ES 5 is the first release to include Sun Cluster Geographic Edition as a Java ES product component.
Sun Cluster Geographic Edition includes the following subcomponents:
Sun Cluster Geographic Edition Core
Sun StorEdge Availability Suite
Hitachi Truecopy Data Replication Support (SPARC only)
EMC SRDF Data Replication
Sun Cluster Geographic Edition is not supported on Solaris x86.
Access components provide front-end access to system services, often from Internet locations outside an enterprise firewall. The following Java ES access components are described in this section:
Sun Java System Portal Server Secure Remote Access (Portal Server Secure Remote Access) extends Portal Server by offering browser-based secure remote access to Portal Server content and services from any remote browser, eliminating the need for client software. Integration with Portal Server ensures that users receive secure access to the content and services that they have permission to access.
Portal Server Secure Remote Access includes the following subcomponents:
Portal Server Secure Remote Access Core. Provides core functionality.
Gateway. Provides the interface and security barrier between remote user sessions originating from the Internet and a corporate intranet. Gateway presents content securely from internal web servers and application servers through a single interface to a remote user and controls communication between the Portal Server and the various Gateway instances.
Netlet Proxy. Enables users to securely run common TCP/IP services over the Internet and other non-secure networks. Netlet allows you to run applications such as telnet, SMTP, HTTP, and fixed-port applications. Netlet enables remote access and operation of file systems and directories and ensures secure communication between the Netlet applet on the client browser, the Gateway, and the application servers.
Rewriter Proxy. Enables secure HTTP traffic between the Gateway and intranet computers. Rewriter provides secure access to corporate intranet web pages from outside of the intranet by transforming web links and creating rule sets for handling intranet web pages.
Sun Java System Web Proxy Server (Web Proxy Server) provides caching, filtering, and distribution of web content. Web Proxy Server is often used inside enterprise firewalls to reduce the number of requests to remote content servers, and outside firewalls to provide a secure gateway for incoming Internet requests.
The Java ES installer provides Web Proxy Server as a single installable component.
The Sun Java System Monitoring Console 1.0 (Monitoring Console) includes a master agent that connects to all node agents in a Java ES deployment. The Monitoring Console is supported by the Sun Java System Monitoring Framework 2.0 (Monitoring Framework), a shared component that provides the instrumentation and node agent needed by every monitored component to expose its attributes for observation. Each product component exposes the objects that represent its observable attributes, and a node agent aggregates a view of multiple components on one host. For detailed information about monitoring, see the Sun Java Enterprise System 5 Monitoring Guide.