1.4 Main updates in the functionality of Application Server 09-50

This section describes the main updates in the functionality of Application Server 09-50 and the purpose of each update.

The following contents are described in this section:

Organization of this section
(1) Improving development productivity
(2) Simplifying implementation and setup
(3) Supporting standard and existing functionality
(4) Maintaining and improving reliability
(5) Maintaining and improving the operation performance
(6) Other purposes

(1) Improving development productivity

The following table describes the items that have been changed for improving development productivity.

Table 1-4 Changes made for improving development productivity

ItemOverview of changesReference manualReference location
Simplifying Eclipse setupEnabled the setup of the Eclipse environment by using GUI.Application Development Guide1.1.5, 2.4
Debugging support using the user extended performance analysis traceEnabled the creation of the user extended performance analysis trace configuration file in a development environment.Application Development Guide1.1.3, 6.5

(2) Simplifying implementation and setup

The following table describes the items that have been changed to simplify implementation and setup:

Table 1-5 Changes made for simplifying implementation and setup

ItemOverview of changesReference manualReference location
Expanding the system configuration pattern in a virtual environmentThe types of tier (http-tier, j2ee-tier and ctm-tier) that can be used in a virtual environment have increased. This enables the set up of the following system configuration patterns:
  • A pattern in which the Web server and J2EE server are placed on separate hosts
  • A pattern in which the front-end (Servlet, JSP) and back-end (EJB) are deployed separately
  • A pattern in which CTM is used
Virtual System Setup and Operation Guide1.1.2

(3) Supporting standard and existing functionality

The following table describes the items that are changed to support standard and existing functionality:

Table 1-6 Changes made for supporting the standard and existing functionality

ItemOverview of changesReference manualReference location
Supporting the JDBC 4.0 specificationsDB Connector now supports the HiRDB Type4 JDBC Driver with JDBC 4.0 specifications and the JDBC Driver of SQL Server.Common Container Functionality Guide3.6.3
Modifying naming conventions in the Portable Global JNDI namesAdded characters that can be used in the Portable Global JNDI names.Common Container Functionality Guide2.4.3
Supporting the Servlet 3.0 specificationsUpdates of the HTTP Cookie name of Servlet 3.0 and the path parameter name of URL can now be used even in versions earlier than Servlet 2.5Web Container Functionality Guide2.7
Expanding the applicability of an application which can be integrated with Bean ValidationEnabled validation using Bean Validation with CDI and user applications.Common Container Functionality GuideChapter 10
Supporting JavaMailEnabled the use of the mail sending and receiving functionality that uses APIs, and is compliant with JavaMail 1.4.Common Container Functionality GuideChapter 8
Expanding the applicability of OSs on which you can use the javacore commandEnabled acquisition of a thread dump of Windows by using the javacore commandCommand Reference Guidejavacore (acquiring thread dump / in Windows)

(4) Maintaining and improving reliability

The following table describes the items that have been changed for maintaining and improving reliability:

Table 1-7 Changes made for maintaining and improving reliability

ItemOverview of changesReference manualReference location
Preventing exhaustion of the code cache areaEnabled prevention of area exhaustion by checking the size of the code cache area used in the system and changing the threshold value before the area is exhausted.System Design Guide7.1.2
Maintenance and Migration Guide5.7.2, 5.7.3
Definition Reference Guide16.1, 16.2, 16.4
Supporting an effective application of the explicit heap functionality
Expanding the output range of the class-wise statistical information
Added functionality that can control the objects to be moved to the Explicit heap as functionality to shorten the automatic release processing time and efficiently apply the explicit heap functionality.
  • Functionality that controls the object movement to the Explicit memory blocks
  • Functionality for specifying classes for which application of the explicit heap functionality is to be excluded
  • Output of the object release rate information to the Explicit heap information
Enabled the output of reference relations based on the static field to the extended thread dump, that includes the class-wise statistical information.
System Design Guide7.13.6
Expansion Guide8.2.2, 8.6.5, 8.10, 8.13.1, 8.13.3
Maintenance and Migration Guide5.5
Maintenance and Migration Guide9.6

(5) Maintaining and improving the operation performance

The following table describes the items that have been changed for maintaining and improving operation performance:

Table 1-8 Changes made for maintaining and improving operation performance

ItemOverview of changesReference manualReference location
Supporting the EADs session failover functionalitySupported the EADs session failover functionality, which implements the session failover functionality by integrating with EADs.Expansion GuideChapter 5, Chapter 7
Operation using WAREnabled deploying of the WAR application that consists of only the WAR files, on the J2EE server.Web Container Functionality Guide2.2.1
Common Container Functionality Guide13.9
Command Reference Guidecjimportwar (Importing WAR application)
Starting and stopping by synchronous execution of the operation management functionalityAdded an option that executes the synchronous starting and stopping of the operation management functionality (Management Server and Administration Agent).Operation, Monitoring, and Linkage Guide2.6.1, 2.6.2, 2.6.3, 2.6.4
Command Reference Guideadminagentctl (start or stop Administration Agent), mngautorun (set up/canceling the set up of autostart and autorestart), mngsvrctl (start, stop, or set up Management Server)
Forcefully releasing the Explicit memory blocks in the explicit management heap functionalityEnabled the execution of the process of releasing the Explicit memory blocks with the javagc command at any timing.Expansion Guide8.6.1, 8.9
Command Reference Guidejavagc (Force generation of garbage collection)

(6) Other purposes

The following table describes the items that have been changed for other purposes:

Table 1-9 Changes made for other purposes

ItemOverview of changesReference manualReference location
Acquiring the definition informationEnabled collection of only the definition file with the snapshot (snapshot log collection) command.Maintenance and Migration Guide2.3
Command Reference Guidesnapshotlog (collecting snapshot log)
Log output of the cjenvsetup commandEnabled output of the execution information of the setup (cjenvsetup command) of Component Container Administrator to the message log.System Setup and Operation Guide4.1.4
Maintenance and Migration Guide4.20
Command Reference Guidecjenvsetup (setup of Component Container Administrator)
Supporting BIG-IP v11Added BIG-IP v11 to the types of the available load balancersSystem Setup and Operation Guide4.7.2
Virtual System Setup and Operation Guide2.1
Performing the output of the CPU time to the event log of the explicit heap functionalityEnabled the output of the CPU time taken for the Explicit memory block release processing, to the event log of the explicit heap functionality.Maintenance and Migration Guide5.11.3
Extending the user extended performance analysis trace functionalityAdded the following functionality to the user extended performance analysis trace:
  • Enabled the specification of the trace target in a package unit or class unit in addition to the usual method unit.
  • Extended the range of the available event IDs.
  • Released the restriction on the number of rows that can be specified in the user extended performance analysis trace configuration file.
  • Enabled the specification of the trace acquisition level in the user extended performance analysis trace configuration file.
Maintenance and Migration Guide7.5.2, 7.5.3, 8.28.1
Improving the information analysis when using an asynchronous invocation of Session BeanEnabled the comparison of the requests of the invocation source and invocation destination by using the root application information of the PRF trace.This manual2.17.3