Chapter 6: New Features in EAServer Versions 4.1.3, 4.1.2, 4.1.1, and 4.1
EAServer 4.1 introduces these features:
EAServer 4.1 adds support for ejbSelect methods and queries defined in EJB query language (EJB-QL), as required by the EJB 2.0 specification. ejbSelect methods allow you to run queries internal to your implementation. In your implementation, these methods must be declared private and abstract, and EAServer provides the runtime implementation. EJB-QL is the new standard language to define the database queries required to run finder methods and ejbSelect methods. At runtime, EAServer translates EJB-QL to SQL that is appropriate for the database type used by the component.
For more information on EAServer CMP support, see:
“CMP enhancements” describes CMP enhancements added to EAServer 4.0.
Chapter 27, “Creating Entity Components,” in the EAServer Programmer’s Guide describes how to configure container managed persistence for EJB entity beans.
In EAServer 4.1, you can optionally install the Web Services Toolkit, which provides support for industry-standard Web services protocols such as Simple Object Access Protocol (SOAP), Web Services Description Language (WSDL), and Uniform Description, Discovery, and Integration (UDDI). SOAP provides a standard protocol for component invocations over HTTP connections, for example, you can expose a purchasing component to be called by business partners as a Web service. WSDL describes the service and can be used in client applications. You can also publish business and service information to a UDDI registry site on the Web and make your web service available to other users. SOAP provides a platform and language neutral means of accessing these services. With SOAP, WSDL, and UDDI, collaboration between business partners is made easier because interfaces between applications become standardized across disparate platforms.
The Web Services toolkit provides a Web application to run SOAP services, and graphical user interfaces to configure the SOAP services, create WSDL documents, and register services in UDDI registries.
For more information on these features, see the Web Services Toolkit User’s Guide.
EAServer 4.1 includes Message Bridge for Java, a powerful, easy-to-use tool you can use to build applications that generate and consume documents and messages. Message Bridge generates Java classes that simplify the parsing and construction of XML documents. For more information, see the Message Bridge for Java™ User’s Guide.
EAServer 4.1 has new features to simplify the deployment of applications to EAServer:
When using Jaguar JAR format archives to deploy between EAServer installations, you can include merge files. A merge file allows you to modify or delete settings for entities that already exist. For example, you can create a merge file to install a package into the Jaguar server, without affecting the list of packages that are already installed.
When using J2EE standard archive formats such as an EJB-JAR file, an application EAR file, or a Web application WAR file, you can define an EAServer supplemental deployment descriptor to configure properties that are required by EAServer but are not supported by the standard deployment descriptor format. EAServer creates a supplemental descriptor for any archive that you export from EAServer Manager.
For more information on these features, see Chapter 9, “Importing and Exporting Application Components,” in the EAServer System Administration Guide.
EAServer 4.1 adds support for integration with Web sites hosted by Microsoft Internet Information Server (IIS) on Windows platforms. You can host static content on IIS, and use the EAServer Redirector Plug-in for IIS to redirect servlet and JSP requests to EAServer. In addition to IIS, plug-ins for several other Web servers are available. For more information, see the EAServer Installation Guide for Windows.
EAServer 4.1 adds support for caching of static content, and enhances the servlet response caching abilities introduced in EAServer 4.0.
Static page caching can increase performance by caching static files in memory. You can configure which files are cached and for how long on a per-server basis. For more information, see Chapter 5, “Web Application Tuning,” in the EAServer Performance and Tuning Guide.
In EAServer 4.1, the entire response from JSPs that use forward or include commands is cached. Previously, you needed to configure caching separately for the forwarded or included page. In version 4.1, you can enable the Cache Entire Tree option for a Web component so that the response from all forwards and includes is cached together with content generated by the Web component itself. For more information on servlet response caching, see see Chapter 5, “Web Application Tuning,” in the EAServer Performance and Tuning Guide.
EAServer 4.1 adds connection cache support for Oracle OCI 9 connections to Oracle databases, and Sybase Open Client™ Client-Library™ connections to highly-available Adaptive Server Enterprise databases.
The administration automation tools, jagtool and jagant, have been enhanced with several new commands for EAServer 4.1, including:
Several new commands to configure Java Message Service entities.
The compilejsp command to compile JavaServer Pages.
The configure command to execute XML configuration files.
The exportconfig command to create XML configuration files.
For more information, see Chapter 12, “Using jagtool and jagant,” in the EAServer System Administration Guide.
The servlet filter interface required by EAServer 4.1 has changed from version 4.0. The setFilterConfig method is no longer supported (as of version 4.1); it has been replaced by the init and destroy methods.
For Web application lifecycle event listeners, the interfaces javax.servlet.ServletContextAttributeListener and javax.servlet.http.HttpSessionAttributeListener are both new for EAServer version 4.1. The corresponding interfaces from EAServer version 4.0, where “Attributes” was plural, are not supported in EAServer 4.1.
For more information on servlet filters and Web application lifecycle event listeners, see Chapter 23, “Using Filters and Event Listeners,” in the EAServer Programmer’s Guide.
EAServer 4.1 adds methods that allow a client to maintain an authenticated session across multiple transport sessions. In versions earlier than EAServer 4.1, if a client created a second component instance on the same server, or created a component instance on another server in the same cluster, the client was reauthenticated. A server can now authenticate and verify a client’s credentials once, and, on subsequent authentication requests, the client provides a reference to the initial authentication.
To use the single authentication mechanism, you must use a custom authentication component that implements the CtsSecurity::AuthService interface.
CtsSecurity::SessionInfo::setName is a method that can be called only when your custom authentication component is running. When this method is called from the custom authentication component, the server sets the reference to the authenticated security credentials. When the client needs to be authenticated again, the custom authentication component returns the original principal name by calling CtsSecurity::AuthService::getCallerPrincipal(string alternate_name). For more information, see Chapter 10, “Creating and Using Custom Security Components,” in the Security Administration and Programming Guide.
The effect of the com.sybase.jaguar.server.ejb.role.default property on EJB 2.0 components in EAServer 4.0 differs from EAServer version 4.1:
The com.sybase.jaguar.server.ejb.role.default property is a server-wide property. To assign roles to all methods of an EJB 2.0 component in EAServer 4.0, you can assign individual roles to all methods of the component, or set the com.sybase.jaguar.server.ejb.role.default property to everybody.
In EAServer 4.1, com.sybase.jaguar.server.ejb.role.default has been removed. To assign a role to any one method of an EJB 2.0 component, assign roles to all methods of the component. Otherwise, the server displays an error message when trying to execute the method that does not have a role assigned to it.
If none of the methods of an EJB 2.0 component have roles assigned to them, authorization checks are not enforced and authorization is not performed. No error message is sent to the server log.
|Copyright © 2005. Sybase Inc. All rights reserved.|