What’s New in EAServer EAServer Version 5.
DOCUMENT ID: DC38032-01-0550-01 LAST REVISED: September 2006 Copyright © 1997-2006 by Sybase, Inc. All rights reserved. This publication pertains to Sybase software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement. To order additional documents, U.S.
Contents CHAPTER 1 CHAPTER 2 New features in EAServer 5.5 ........................................................ Axis 1.2.1 support ............................................................................ unixODBC ........................................................................................ Upgrade to Eclipse 3.1.2 .................................................................. 1 2 3 1 New features in EAServer 5.3 ........................................................
Contents Systems Management ................................................................... The EASDefault Web application ................................................... Jagtool enhancements ................................................................... Web application synchronization enhancement ...................... New flushstaticpage command ............................................... Alternate Solaris Java threading model .........................................
Contents Enhanced Windows service support ....................................... Adaptive Server Enterprise wide table support ....................... Enhanced character set support ............................................. Apache Web server redirector supports EAPI......................... New EJB CMP component properties..................................... EJB session bean passivation................................................. Message service enhancements......................................
Contents Connection caching enhancements ........................................ jagtool enhancements ............................................................. Servlet and Web application interface changes ...................... Maintaining authenticated sessions ........................................ EJB 2.0 component behavior in EAServer 4.0 versus 4.1 ...... CHAPTER 8 vi 66 66 66 67 67 New Features in EAServer 4.0 ...................................................... 69 J2EE 1.3 support.....
CH A PTE R 1 New features in EAServer 5.5 These features are new in EAServer 5.5. Topic Axis 1.2.1 support unixODBC Page 1 2 Upgrade to Eclipse 3.1.2 3 Axis 1.2.1 support EAServer 5.5 now supports Axis 1.2.1 upgrade release. Axis is a Simple Object Access Protocol (SOAP) engine—a framework for constructing SOAP processors such as clients, servers, gateways, and others. The Axis 1.2.1 delivers the following key features: What’s New • Supports SOAP 1.1/1.
unixODBC • Includes WSDL2Java tool for building Java proxies and skeletons from WSDL documents and Java2WSDL tool for building WSDL documents from Java classes • Provides preliminary security extensions, which can integrate with Servlet 2.
CHAPTER 1 New features in EAServer 5.5 Upgrade to Eclipse 3.1.2 EAServer 5.5 upgrades the current Eclipse plug-ins to support Eclipse 3.1.2.
Upgrade to Eclipse 3.1.
CH A PTE R 2 New features in EAServer 5.3 These features are new in EAServer 5.3. Topic Merge of Axis 1.2 Named classloader support Page 5 6 Oracle 10g support jConnect 6.0 support 6 7 JDK 1.5 support Unicode datatype support 7 8 Upgrade to Eclipse 3.0.1 Upgrade to Adaptive Server Anywhere 9.0.2 (ASA 9.0.2) 8 8 Merge of Axis 1.2 EAServer 5.3 now supports Axis 1.2 final release.
Named classloader support You can easily define reusable networks of Handlers to implement common patterns of processing your applications, or to distribute to partners. • Component-oriented deployment • Transport framework • Web Services Description Language(WSDL) Axis has a clean and simple concept for designing transports, and the core of engine is completely transportindependent. Axis supports the WSDL version 1.
CHAPTER 2 New features in EAServer 5.3 jConnect 6.0 support This new feature of EAServer is compiled using JDK 1.4, which includes the JDBC 3.0 standards and all associated interfaces. With jConnect 6.0, you can use Kerberos to authenticate Java applications without sending user names and passwords over a network. jConnect 6.
Unicode datatype support Unicode datatype support EAServer 5.3 now supports Open Client 12.5 Unicode datatype. The primary goal of the Unicode datatype feature is to make it possible to use unichar or univarchar in place of the traditional character datatype char or varchar. This Unicode support handles the Adaptive Server Enterprise (ASE) new features and datatypes in creating a connection cache using the EAServer manager. Upgrade to Eclipse 3.0.1 EAServer 5.
CH A PTE R 3 New features in EAServer 5.2 These features are new in EAServer 5.2. Topic Automatic performance tuning EAServer Manager enhancements Page 9 10 In-memory mirror caching FIPS and TLS support 10 12 Automatic performance tuning The automatic performance tuning feature monitors EAServer response rates and modifies controllable parameters to improve these response rates.
EAServer Manager enhancements EAServer Manager enhancements In EAServer 5.2, EAServer Manager includes new configuration wizards for these entity types: • Log Profile • Log Category • Log Handler • Log Formatter EAServer Manager launches the wizard when you create an entity of the associated type, instead of displaying a properties dialog box with default or empty values. You can also reconfigure existing entities using the wizard.
CHAPTER 3 New features in EAServer 5.2 To use mirror caching feature, the message service must be active. The mirror object cache uses the following message queues to send and receive messages: ❖ • – the object cache queue listens for system messages, such as server shutdown and start-up messages. • – the mirror cache queue enables a remote server to recover lost data.
FIPS and TLS support “Configuring the object cache” in Chapter 4, “EJB CMP Tuning,” in the EAServer Performance and Tuning Guide describes how to enable and configure the object cache. The CtsComponents/ObjectCache component, which previously provided the default implementation of the cache manager, has been replaced by CtsComponents/JavaObjectCache. FIPS and TLS support EAServer 5.2 supports FIPS and TLS security enhancements.
CHAPTER 3 New features in EAServer 5.2 The TLS protocol addresses some of the security concerns of SSL v3. FIPS requires TLS for use with a FIPS cryptographic module. See RFC 2246 at http://www.faqs.org/rfcs/rfc2246.html for a complete description of TLS. See Chapter 9, “Using TLS and FIPS in EAServer,” in the EAServer Security Administration and Programming Guide for complete information.
FIPS and TLS support 14 EAServer
CH A PTE R 4 New features in EAServer 5.1 These features are new in EAServer 5.1. Topic EAServer Manager enhancements Running components externally Page 15 17 IPV6 support Server performance monitoring 18 18 Custom class loader enhancements Systems Management 18 19 The EASDefault Web application Jagtool enhancements 19 20 Alternate Solaris Java threading model Private UDDI registry security enhancements 20 21 EAServer Manager enhancements In EAServer 5.
EAServer Manager enhancements • Connection Cache Configuration • Instance Pool • Managed Connection Factory • Identity • Security Profile EAServer Manager launches the wizard when you create an entity of the associated type, instead of displaying a properties dialog box with default or empty values. You can also reconfigure existing entities using the wizard rather than the properties dialog box.
CHAPTER 4 New features in EAServer 5.1 Web application synchronization enhancement When synchronizing Web applications, you can optionally exclude Java class files that are listed in the Web application’s custom class list. Doing so may save time if these files are already present on the host server or included in the file set of other entities that are being replicated at the same time. For more information, see Chapter 6, “Clusters and Synchronization,” in the EAServer System Administration Guide.
IPV6 support IPV6 support EAServer 5.1 supports the Internet Protocol Version 6 (IPV6) on platforms that provide the underlying network support such as Windows 2003, Windows XP, and Solaris 2.8. Windows 2000 does not support IPV6. IPV6 support also requires JDK 1.4 or a later JDK version. By default, the server supports IPV4 connections only. To start the server with support for IPV6, specify the -IPV6 and -jdk14 command-line options.
CHAPTER 4 New features in EAServer 5.1 Systems Management EAServer 5.1 includes support for the Simple Network Management Protocol (SNMP), which includes an SNMP master agent from J.AgentX. This replaces the functionality provided previously by Java AgentX. The graphical user interface has also been updated. The Web Console plug-in allows you to browse the MBeans and services installed on either your local server or a remote server using a Web browser.
Jagtool enhancements Jagtool enhancements In EAServer 5.1, jagtool includes the following enhancements. For information on jagtool, see Chapter 12, “Using jagtool and jagant,” in the EAServer System Administration Guide. Web application synchronization enhancement When synchronizing Web applications with the sync command, you can optionally exclude Java class files that are listed in the Web application’s custom class list by adding -syncwebappjavaclasses false to the command.
CHAPTER 4 New features in EAServer 5.1 Private UDDI registry security enhancements EAServer 5.1 includes security enhancements for the private UDDI registry, including three new roles and security constraint support. For more information, see “Controlling access to resources” in Chapter 7, “The Private UDDI Server,”in the Web Services Toolkit User’s Guide.
Private UDDI registry security enhancements 22 EAServer
CH A PTE R 5 New features in EAServer 5.0 These features are new in EAServer 5.0.
EAServer Manager enhancements • Online help. The online help for EAServer Manager now includes the EAServer product manuals in addition to the context-sensitive help. To access the help, click Help if enabled in any dialog box, or choose Tools | EAServer Manager Help. • More wizards. Several new wizards are available, as listed under “New wizards” on page 24. • Undeployment support.
CHAPTER 5 New features in EAServer 5.0 These wizards guide you through the tuning of server, component, Web application, servlet/JSP or server settings that affect performance. To run them, highlight the server, component, Web application, or JSP icon, then choose File | Performance Tuning Wizard.
HTTP directory browsing Undeployment of packages, Web applications, and applications When deleting a package, Web application, or application, you can choose whether to delete only the entity’s properties file, or to delete all files that have been generated by the deployment of the entity, including component stubs and skeletons and IDL interface and datatype definitions. By default, EAServer Manager performs a full deletion. In earlier EAServer versions, only properties files were deleted.
CHAPTER 5 New features in EAServer 5.0 The EAServer Transaction Manager enables EAServer to control the scope and duration of transactions across multiple resource managers. It also provides the ability to synchronize transactions and to communicate with other transaction managers using CORBA OTS. For more information about this feature, see Chapter 2, “Understanding Transactions and Component Lifecycles,” in the EAServer Programmer’s Guide.
Enhanced systems management support Table 5-2 describes three possibilities for configuring connection cache properties to duplicate the functionality that was previously available by passing the JCM flags to JCMCache.getConnection. Table 5-2: Configuring connection caches If components previously passed this flag to getConnection JCM_WAIT Configure these connection cache property values Set the value of com.sybase.jaguar.conncache.poolmanager.maxconnections equal to the value of com.sybase.jaguar.
CHAPTER 5 New features in EAServer 5.0 Enhanced Solaris C++ compiler support The Solaris version of EAServer 5.0 supports 4.x and 6.x versions of the Solaris C++ compiler. The binary format of executable files and libraries differs between the two compiler versions, so you must choose one version for all C++ components running in a server. When starting the server, specify the compiler compatibility version with the -compilerversion option. For example, for compatibility with the 6.
Server logging enhancements Server logging enhancements EAServer 5.0 includes a more configurable logging mechanism that allows integration with the JDK 1.4 Java Logging package or the Apache Log4j logging system. A server’s logging properties are defined in a Log Profile, which defines the logging subsystem used as well as other properties, such as output destinations, formats, and the level of severity required before a message is recorded.
CHAPTER 5 New features in EAServer 5.0 Logging APIs Regardless of the logging system you use, you can write messages to the log using all of the methods supported in earlier versions of EAServer, such as: • System.out.println or Jaguar.writeLog from Java code running in the server • ErrorLogging.log from PowerBuilder® NVO components • JagLog from C or C++ components • IJagServer.
Admin role granularity • Jaguar::PerfMonitor is a new performance monitoring interface that provides performance statistics in a per-second, per-minute, and perhour bucket model. • Jaguar::StatProvider and Jaguar::StatProviderController are new interfaces implemented by statistic provider components that collect performance statistics. EAServer 5.0 includes statistics providers for the connection caching and HTTP protocol handler subsystems.
CHAPTER 5 • New features in EAServer 5.0 Creating, updating, or deleting applications, packages, servlets, and Web applications For more information, see Chapter 13, “Security Configuration Tasks,” in the EAServer Security Administration and Programming Guide. Web Services Toolkit Web Services Toolkit (WST) combines the architecture and tools required for creating, managing, and administering Web services contained in EAServer, and has many enhancements to WST version 4.
PowerDynamo Web site conversion utility • The new command rebind allows you to rebind the name servers in a cluster. • The ejbref command has been enhanced to support EJB local references. • The export command has been enhanced to take an emptycachetags argument.
CHAPTER 5 New features in EAServer 5.0 Partial page caching Partial page caching allows you to cache parts of a response. This mechanism is useful when pages contain volatile content, such as calculation results, but otherwise have static content such as headers and footers. Partial page caching is supported by a tag library for use in JSPs, and a public API for use in servlets.
Partial page caching 36 EAServer
CH A PTE R 6 New Features in EAServer Versions 4.2.3, 4.2.2, 4.2.1, and 4.2 Topic New features in version 4.2.3 Server stack size Sharing of JSP class files Suppressing SSL error messages 38 39 Servlet authenticated session enhancement Jagtool enhancements 39 39 Web server redirector enhancements New features in version 4.2.
New features in version 4.2.3 New features in version 4.2.3 EAServer 4.2.3 includes these new features: • Server stack size • Sharing of JSP class files • Suppressing SSL error messages • Servlet authenticated session enhancement • Jagtool enhancements • Web server redirector enhancements Server stack size On Windows, the default per-thread stack size for the server executable has changed to 256K (previously 512K). The smaller setting makes more memory available for other uses.
CHAPTER 6 New Features in EAServer Versions 4.2.3, 4.2.2, 4.2.1, and 4.2 Suppressing SSL error messages EAServer 4.2.3 includes new settings which allow you to suppress client SSL errors from the server log file. In EAServer Manager, the Log SSL Error setting for listener and security profile properties specifies whether EAServer logs SSL errors from client connections to the listener.
New features in version 4.2.3 • server is the server name Retrieving runtime monitoring statistics The new command getmonitorstats retrieves and prints runtime monitoring statistics from the server that you are connected to. For details, see the getmonitorstats reference page in Chapter 12, “Using jagtool and jagant,” in the EAServer System Administration Guide. New jmsmanage_selectors command The new jmsmanage_selectors command allows you to add and remove selectors to and from JMS message queues.
CHAPTER 6 New Features in EAServer Versions 4.2.3, 4.2.2, 4.2.1, and 4.2 New Web application property When using a Web server redirector, you can configure the source for information returned by the HTTPServletRequest methods getScheme, getServerPort, and getServerName. To configure the source, set the Web application property com.sybase.jaguar.webapplication.get-serverinfo-from.
New features in version 4.2.2 • Enhanced character set support • Apache Web server redirector supports EAPI • New EJB CMP component properties • EJB session bean passivation • Message service enhancements Netegrity SiteMinder Integration EAServer 4.2.2 supports integration with Netegrity SiteMinder security software. Netegrity SiteMinder provides single sign-on and centralized management of Web, database, and software resources in enterprise applications.
CHAPTER 6 New Features in EAServer Versions 4.2.3, 4.2.2, 4.2.1, and 4.2 Retrieving additional user session details in a JAAS login module Beginning in version 4.2.2, EAServer allows you to retrieve additional IIOP or HTTP user session information when using the JAAS API to install custom security implementations.For more information, see “Retrieving additional user session details in a JAAS login module” in Chapter 11, “Using the JAAS API,” in the EAServer Security Administration and Programming Guide.
New features in version 4.2.2 Changing the effective user ID for the server process Beginning in version 4.2.2, EAServer on UNIX platforms allows you to configure an effective user name and group for the server to run as. This feature is useful if you start the server while logged in as a UNIX user with administrator privileges: you can start the server with administrator privileges, but the server switches to an account that has fewer privileges before it begins accepting client connections.
CHAPTER 6 New Features in EAServer Versions 4.2.3, 4.2.2, 4.2.1, and 4.2 You can specify the service name when installing a server as a service or manually starting or stopping the service. To specify the service name, use the -servicename argument in addition to the arguments documented in Chapter 3, “Creating and Configuring Servers,” in the EAServer System Administration Guide.
New features in version 4.2.2 New EJB CMP component properties Table 6-1 lists new component properties that you can set on the Advanced tab in the EAServer Manager Component Properties dialog box for EJB entity beans that use Container Managed Persistence (CMP). Actual property names are prefixed with com.sybase.jaguar.component. These properties were added for the 4.1.3 and 4.2.2 releases, as indicated in the table. Table 6-1: New component properties Property Description com.sybase.jaguar.component.
CHAPTER 6 New Features in EAServer Versions 4.2.3, 4.2.2, 4.2.1, and 4.2 Property Description com.sybase.jaguar.component.ts.triggers Specifies that the storage component (CtsComponents/JdbcStorage) should automatically create database triggers to enforce the required timestamp semantics when using table-level timestamps. Enables automatic transaction retry for EJB CMP entity beans that use optimistic concurrency control (OCC). (New in 4.1.3) com.sybase.jaguar.component.tx_retry (New in 4.1.
New features in version 4.2.2 Soft locking EAServer 4.2.2 introduces support for in-server soft locking of database rows used by EJB CMP entity beans that use the isolation level repeatable_read_with_cache. For more information, see “Concurrency control options” in Chapter 4, “EJB CMP Tuning,” in the EAServer Performance and Tuning Guide. Generated entity bean subclasses Beginning in EAServer 4.1.3, you can use the “Generated class” option for EJB 1.1 and 2.0 CMP entity beans.
CHAPTER 6 New Features in EAServer Versions 4.2.3, 4.2.2, 4.2.1, and 4.2 New features in version 4.2.1 EAServer 4.2.1 supports these new features: • Web application form login enhancements • EJB pass-by-reference support • Database set-proxy support for EJB CMP entity beans • SSL connection troubleshooting enhancement Web application form login enhancements EAServer 4.2.
New features in version 4.2 SSL connection troubleshooting enhancement You can set the new security profile property com.sybase.jaguar.security.logpeerIP. If this property is set to true in an SSL listener’s security profile, the client’s IP address is logged when SSL connections cannot be established. The default is false. New features in version 4.2 This section outlines the new features in EAServer 4.2.
CH A PTE R 7 New Features in EAServer Versions 4.1.3, 4.1.2, 4.1.1, and 4.1 Topic New features in version 4.1.3 Performance tuning features HTTPS support for Web server plug-ins Jagtool merge_props command Java connection manager API change New features in version 4.1.2 54 55 55 55 JDK 1.
New features in version 4.1.3 Topic jagtool enhancements Page 66 Servlet and Web application interface changes Maintaining authenticated sessions 66 67 EJB 2.0 component behavior in EAServer 4.0 versus 4.1 67 New features in version 4.1.3 EAServer 4.1.3 introduces the following: • Performance tuning features • HTTPS support for Web server plug-ins • Jagtool merge_props command Performance tuning features New EAServer 4.1.
CHAPTER 7 New Features in EAServer Versions 4.1.3, 4.1.2, 4.1.1, and 4.1 Lightweight EJB container The performance of some inter-component calls in EAServer can be improved by enabling the lightweight container (LWC). The LWC co-exists with the standard container. The LWC provides optimized performance for EJB-to-EJB calls, while ensuring all expected EJB semantics are preserved such as pass by value when using remote interfaces.
New features in version 4.1.3 Entity instance caching with Oracle You can use object caching when running EJB CMP entity beans. This feature works with any database. You can also configure change notification to notify EAServer's cache manager of changes to the underlying table rows. For more information, see see “Entity instance and query caching” in in Chapter 4, “EJB CMP Tuning,” in the EAServer Performance and Tuning Guide. New server properties Table 7-1 lists new server properties.
CHAPTER 7 New Features in EAServer Versions 4.1.3, 4.1.2, 4.1.1, and 4.1 See the EAServer Installation Guide for Web server redirector installation and configuration instructions. Jagtool merge_props command Introduced in EAServer 4.1.3, the merge_props command merges or deletes property values for an entity. For more information, see the reference page in Chapter 12, “Using jagtool and jagant,” in the EAServer System Administration Guide. Java connection manager API change The JCMCache.
New features in version 4.1.2 • Web application character set properties • HTTP session attribute API change JDK 1.4 EAServer 4.1.2 adds support for running with JDK 1.4 as the in-server Java virtual machine. New performance tuning features The following performance-related features are new in EAServer 4.1.
CHAPTER 7 New Features in EAServer Versions 4.1.3, 4.1.2, 4.1.1, and 4.1 Flow control When the server is very busy with many client connections, client request threads may repeatedly conflict with each other for access to low-level system resources. Flow control provides a coarser level of granularity for synchronizing access to system resources by request threads.
New features in version 4.1.2 JavaServer Pages compilation speed To reduce the compilation time for JavaServer Pages (JSPs), you can configure the class path for JSPs separately from the EAServer class path. Doing so can speed up the compilation of the JSPs. This can improve performance if your application requires runtime compilation, and can speed up the development cycle.
CHAPTER 7 New Features in EAServer Versions 4.1.3, 4.1.2, 4.1.1, and 4.1 Client connection timeouts Response timeout properties have been added to the Java CORBA client ORB and EJB initial context. For applications that run in a cluster, these properties allow you to specify a time limit to receive a server response before the connection fails over to try another server in the cluster. Setting this property ensures that failover happens without an unreasonable delay. The property names are: • com.sybase.
New features in version 4.1.2 When this directive is set, the connector appends the value of ConnectorSessionId to the URL that is forwarded to EAServer. EAServer writes the URL to the server’s HTTP request log, which can be helpful for debugging. For example, if you add this directive to the redirector configuration file: Connector.SessionId ConnSID EAServer writes this information to the HTTP request log: 10.22.85.66 - - [28/May/2002:12:11:09 /TestHTTPS/?ConnSID=2696_000000000000 10.22.85.
CHAPTER 7 New Features in EAServer Versions 4.1.3, 4.1.2, 4.1.1, and 4.1 APPLET context parameter for EJB clients Beginning in EAServer 4.1.2, EJB clients that run as applets can set the APPLET parameter for the javax.naming.InitialContext instance used to connect to EAServer. For more information, see Chapter 8, “Creating Enterprise JavaBeans Clients,” in the EAServer Programmer’s Guide. Web application character set properties EAServer 4.1.
New features in version 4.1 Message Bridge for Java enhancements EAServer 4.1.1 includes Message Bridge for Java™, version 2.1.1. Enhancements in this version include: • Improved support for XML Schema • Performance improvements for schema import, code generation, and the graphical user interface. • Additional samples. For more information on these features, see the Message Bridge for Java™ User’s Guide. Java Secure Sockets Extension support EAServer 4.1.
CHAPTER 7 New Features in EAServer Versions 4.1.3, 4.1.2, 4.1.1, and 4.1 • EJB 2.0 container-managed persistence enhancements • Web services support • Message Bridge for Java™ • Deployment enhancements • Web server redirector for Microsoft Internet Information Server • HTTP response caching enhancements • Connection caching enhancements • jagtool enhancements • Servlet and Web application interface changes • Maintaining authenticated sessions • EJB 2.
New features in version 4.1 Web services support 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).
CHAPTER 7 • New Features in EAServer Versions 4.1.3, 4.1.2, 4.1.1, and 4.1 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.
New features in version 4.1 Connection caching enhancements 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. jagtool enhancements 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.
CHAPTER 7 New Features in EAServer Versions 4.1.3, 4.1.2, 4.1.1, and 4.1 Maintaining authenticated sessions 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.
New features in version 4.
CH A PTE R 8 New Features in EAServer 4.0 EAServer 4.0 includes these new features: Feature J2EE 1.3 support Page 69 Performance enhancements EJB 2.0 support 70 71 Message service enhancements Servlet, JSP, and Web application enhancements 73 74 Java XML parser integration J2EE connectors 76 76 J2EE naming enhancements J2EE security enhancements 76 77 Enhanced transaction support HTTP 1.
Performance enhancements • Java API for XML Parsing (JAXP) integration, described in “Java XML parser integration” on page 76. • The J2EE connector architecture, described in “J2EE connectors” on page 76. • J2EE naming enhancements described in “J2EE naming enhancements” on page 76. • J2EE 1.3 security features such as CSIv2 and the Java Authentication and Authorization Service (JAAS) API, described in “J2EE security enhancements” on page 77. • J2EE 1.
CHAPTER 8 New Features in EAServer 4.0 Servlet response caching can be enabled and configured in EAServer Manager. No programming is required. For more information, see Chapter 5, “Web Application Tuning,” in the EAServer Performance and Tuning Guide. Entity component instance and query caching EAServer 4.0 supports instance and query caching for EJB entity beans and components of other types that use the entity design pattern.
EJB 2.0 support For information on JMS and MDB components, see Chapter 31, “Using the Message Service,” in the EAServer Programmer’s Guide. Home interface methods EJB 2.0 allows you to define business methods in the home interface for an entity bean and changes the syntax of create methods. For information on defining home interface methods, see Chapter 7, “Creating Enterprise JavaBeans Components,” in the EAServer Programmer’s Guide.
CHAPTER 8 New Features in EAServer 4.0 EJB 2.0 interoperability EAServer 4.0 implements the interoperability requirements in the EJB 2.0 specification to allow interoperability with other EJB 2.0 servers. EAServer continues to support CORBA-2.2 based interoperability, for interacting with other CORBA-based application servers and to allow interoperability between EJB components hosted by EAServer and EAServer components of other types.
Servlet, JSP, and Web application enhancements Java Message Service API support EAServer 4.0 provides implementations of the JMS API drivers, layered on top of the existing message service API. The JMS specification defines two messaging models: point-to-point for sending messages to specific message consumers, and Publish/Subscribe for publishing messages that are available to all consumers. For more information, see Chapter 31, “Using the Message Service,” in the EAServer Programmer’s Guide.
CHAPTER 8 New Features in EAServer 4.0 JSP 1.2 support EAServer 4.0 supports the JSP 1.2 specification. JSP 1.2 extends JSP 1.1 in a number of ways: • Uses Servlet 2.3 as the foundation for its semantics. • Defines the XML syntax for JSP pages. • Provides for translation-time validation of JSP pages. A new compilation phase has been added that gives custom tag libraries the opportunity to examine an XML view of the parsed page, and throw a translation time exception if problems are detected.
Java XML parser integration Web server redirector plug-in The Web server redirector plug-in allows communication between the Web server and the EAServer HTTP protocol listener. You can integrate a Web server and EAServer by installing the redirector plug-in on the Web server host. Client requests are sent directly to the Web server, which forwards requests to EAServer that need to access EAServer resources. EAServer processes the requests and returns the results back to the Web server.
CHAPTER 8 New Features in EAServer 4.0 • Message-driven beans • JMS resource connection factory references • Resource environment references • J2EE connectors • EJB components hosted on other EJB 2.0 application servers, using interoperable naming URLs For more information, see Chapter 5, “Naming Services,” in the EAServer System Administration Guide. J2EE security enhancements EAServer 4.0 implements J2EE version 1.
HTTP 1.1 support HTTP 1.1 support EAServer 4.0 offers support for HTTP/1.1. EAServer 4.0 supports features listed as must and required for origin server and client in the W3C spec for HTTP/1.1. For more information about HTTP/1.1, see the HTTP/1.1 specification at http://www.w3.org/Protocols/rfc2616/rfc2616.html. Enhanced C++ component support Beginning in EAServer 4.0, you can run C++ components in a separate process from the host server.
CHAPTER 8 New Features in EAServer 4.0 Deployment and code generation performance EAServer 4.0 introduces Java-to-IDL and IDL-to-Java code generation optimizations. These optimizations can increase your productivity when you deploy Java based applications with complicated component class hierarchies and when you generate Java stubs for these applications.
Systems management enhancements Globally available connection caches Connection caches are now available to all servers run from the same EAServer installation. You no longer need to install connection caches into a server to allow access from components on that server. Java class file consolidation EAServer’s runtime Java classes have been consolidated into these JAR files: • $JAGUAR/java/lib/easserver.jar, required in the CLASSPATH for serverside Java code. • $JAGUAR/java/lib/easclient.
CHAPTER 8 New Features in EAServer 4.0 Repository versioning Repository versioning allows you to save implementation and configuration information for your EAServer applications. For more information on this feature, see Chapter 10, “Using Repository Versioning,” in the EAServer System Administration Guide.
Systems management enhancements 82 EAServer
