Java ES consists of a collection of product components and shared components that work together to support distributed applications across a network. During installation the Java ES installer presents selectable components, many of which have selectable subcomponents. These components and subcomponents are listed in this appendix.
This appendix provides brief descriptions of Java ES components and is intended as an overview. For detailed information about specific components, see the component documentation sets available at http://docs.sun.com/app/docs/prod/entsys.5. A wide range of Java ES information and resources is also available at http://www.sun.com/bigadmin/hubs/javaes/.
The Java ES components listed in this appendix are grouped by category and described in the following sections:
Java ES system service components provide the infrastructure services needed to support distributed enterprise applications. These services, as described in Why You Need Java ES, include portal services, identity and security services, web and application services, and availability services. Java ES system service components are described in the following sections:
Sun Java System Access Manager (Access Manager) integrates authentication and authorization services, policy agents, and identity federation to provide a comprehensive solution for protecting network resources. Access Manager prevents unauthorized access to web service applications and web content, providing an infrastructure for organizations to manage the digital identities of customers, employees, and partners who use their web-based services and non-web applications. Because these resources might be distributed across a range of internal and external computing networks, the attributes, policies, and entitlements are defined and applied to each identity to manage access to these technologies.
Access Manager includes the following subcomponents:
Access Manager Core Services. Provides the means for creating and managing user identities and for defining and evaluating policies that provide access to Java ES resources based on user identities.
Access Manager Administration Console. Consolidates identity services and policy management and provides a single graphical interface for users to create and manage user accounts, service attributes, and access rules in the Directory Server.
Common Domain Services for Federation Management. Enables users to use a single identity to access applications offered by multiple affiliated service providers.
Access Manager SDK. Provides a remote interface to Access Manager. This subcomponent must be installed on any computer hosting a Java ES component that accesses Access Manager remotely.
Access Manager Distributed Authentication User Interface. Provides a user interface that enables a policy agent or an application that is deployed in an unsecured area to communicate with the Access Manager Authentication Service that is installed in a secured area of the deployment.
Access Manager Client SDK. Enables users to implement stand-alone applications that can access an Access Manager server to use services such as authentication, single sign-on, authorization, auditing, logging, and Security Assertion Markup Language (SAML).
Access Manager Session Failover Client. Required to configure Access Manager session failover.
Sun Java System Application Server (Application Server) provides a J2EE compatible platform for developing and delivering server-side Java applications and web services. Key features include scalable transaction management, container-managed persistence runtime, web services performance, clustering, high availability session state, security, and integration capabilities.
Application Server includes the following subcomponents:
Domain Administration Server. Provides server-side administration functions, such as managing and configuring Application Server and deploying J2EE components and applications.
Application Server Node Agent. A lightweight process that runs on every machine that hosts server instances and performs a number of administrative tasks, including stopping, starting, and restarting server instances.
Command Line Administration Tool. Provides command-line administration clients that enable you to manage and configure Application Server installations and hosted applications. The tool also assists with deploying applications.
Load Balancing Plug-in. Used to evenly distribute the workload among multiple Application Server instances (either stand-alone or clustered), thereby increasing the overall throughput of the system. Also used to enable requests to fail over from one server instance to another.
Sample Applications. Installed with the full installation of Application Server.
Sun Java System Directory Server (Directory Server) is an LDAP-based directory server that provides a centralized directory service for your intranet, network, and extranet information. Directory Server integrates with existing systems and acts as a centralized repository for the consolidation of employee, customer, supplier, and partner information. You can extend Directory Server to manage user profiles and preferences and extranet user authentication.
Directory Server includes the following subcomponents:
Directory Server 6 Core Server. Provides the scalable, secure, and flexible means to store and manage identity data.
Directory Service Control Center. Provides a browser-based administration interface to configure directory and directory proxy services.
Directory Server Command-Line Utility. Enables you to perform administration tasks from the command line.
Directory Proxy Server 6 Core Server. Enhances security by offering virtual directory capabilities and increasing directory service availability and scalability.
Java DB provides a lightweight database for Java application development. Java DB is Sun's supported distribution of the open source Apache Derby 100% Java technology database. Java ES 5 is the first release to include Java DB as a product component. Java DB was first released as a shared component named Derby Database and was included Java ES 2005Q4.
Java DB includes the following subcomponents:
Java DB Client
Java DB Server
Sun Java System Message Queue (Message Queue) is a standards-based solution to the problem of inter-application communication and reliable message delivery. Message Queue is an enterprise messaging system that implements the Java Message Service (JMS) open standard.
In addition to being a JMS provider, Message Queue has features that exceed the minimum requirements of the JMS specification. With Message Queue software, processes running on different platforms and operating systems can connect to a common Message Queue service to send and receive information. Application developers can focus on the business logic of their applications rather than on the low-level details of how their applications communicate across a network.
The Java ES installer provides Message Queue as a single installable component.
Sun Java System Portal Server (Portal Server) is an identity-enabled portal server solution. Portal Server combines portal services such as personalization, aggregation, security, integration, and search.
The Java ES installer provides Portal Server as a single installable component.
Sun Java System Service Registry (Service Registry) is a repository that serves as both a web services (UDDI) registry and an enterprise business XML (ebXML) registry for supporting web service-oriented architecture (SOA) applications. The UDDI registry is used to register and discover web services, and the ebXML registry is used to store and manage the information artifacts needed to support business process integration. These artifacts include metadata such as XML schema, business process rules, web service access controls, version controls, classifications schemes, and so forth.
Service Registry includes the following subcomponents:
Service Registry Client Support
Service Registry Deployment Support
Sun Java System Web Server (Web Server) is a multiprocess, multithreaded, secure web server built on industry standards. Web Server provides high performance, reliability, scalability, and manageability for medium to large enterprises.
Web Server includes the following subcomponents:
Web Server CLI
Web Server Core
Web Server Samples
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.
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 Sun N1 Service Provisioning
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.
Shared components provide local services and technology support upon which Java ES system service components and service quality components depend. These components are local libraries that can be shared by any Java ES component running on a particular host computer. The Java ES installer automatically installs any shared components required to support other Java ES components installed on a host computer.
ACL (Apache Common Logging) 1.0.4
ANT (Jakarta ANT Java/XML-based build tool) 1.6.5
BDB (Berkeley Database) 4.2.52
Common Agent Container 1.1 (Sun Cluster only)
Common Agent Container 2.0
ICU 3 (International Components for Unicode) 3.2
J2SE (Java 2 Platform, Standard Edition) 5.0 Update 6 (version 5.0 Update 3 is supported for HP-UX)
JAF (JavaBeansTM Activation Framework) 1.0.3
JATO (Java Studio Web Application Framework) 2.1.5
JavaMailTM API 1.3.2
JAXB (Java Architecture for XML Binding) 2.0.3
JAXP (Java API for XML Processing) 1.3.1
JAXR (Java API for XML Registries) 1.0.8
JAXRPC (Java API for XML-based Remote Procedure Call) 1.1.3_01
JAXWS (Java API for Web Services) 2.0
JDMK (Java Dynamic Management Kit) 5.1.2
JSS (Java Security Services) 4.2.4
JSS3 (Network Security Services for Java) 3.1.11
JSTL (JavaServer PagesTM Standard Tag Library) 1.0.6
KTSE (KT Search Engine) 1.3.4
LDAP C SDK 6.0
LDAP Java SDK 4.19
MA Core (Mobile Access Core) 6.3.1
NSPR (Netscape Portable Runtime) 4.6.4
NSS (Network Security Services) 3.11.4
NSSU (Network Security Service Utilities) 3.11
SAAJ (SOAP with Attachments API for Java) 1.3
SASL (Simple Authentication and Security Layer) 2.19
Sun Explorer Data Collector (Solaris OS only) 4.3.1
Sun Java System Monitoring Framework 2.0 (supports the Monitoring Console 1.0)
Sun Java Web Console 3.0.2
WSCL (Web Services Common Library) 2.0
XWSS (XML Web Services Security) 2.0