1.4 Main functionality changes in Application Server 09-50

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

The contents described in this section are as follows:

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

(1) Improving development productivity

The following table describes the items that are changed to improve development productivity.

Table 1-15 Changes made for improving development productivity

ItemOverview of changesReference manualReference section
Simplification of Eclipse setupGUI can now be used to set up the Eclipse environment.Application Development Guide1.1.5, 2.4
Supporting debug using the user-extended trace-based performance analysisThe user-extended trace-based performance analysis setup file can now be created in the development environment.Application Development Guide1.1.3, 6.5

(2) Simplifying installation and setup

The following table describes the items that are changed to simplify installation and setup.

Table 1-16 Changes made for simplifying installation and setup

ItemOverview of changesReference manualReference section
Expanding the system configuration patterns in the virtual environmentMore tier types are now available in the virtual environment (http-tier, j2ee-tier, and ctm-tier). Accordingly, the following system configuration patterns can now be set up:
  • Pattern of allocating the Web server and J2EE server on different hosts
  • Pattern of allocating the front end (servlets or JSPs) and back end (EJBs) separately
  • Pattern of using the CTM
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-17 Changes made for supporting standard and existing functionality

ItemOverview of changesReference manualReference section
Supporting the JDBC 4.0 specificationsHiRDB Type4 JDBC Driver and SQL Server JDBC driver complying with the JDBC 4.0 specifications are now supported with DB Connector.This manual3.6.3
Relaxation of the naming rules for the Portable Global JNDI namesCharacters that can be used in the Portable Global JNDI names are added.This manual2.4.3
Supporting the Servlet 3.0 specificationsThe changes in the HTTP Cookie name, and URL path parameter name in Servlet 3.0 can now also be used in Servlet 2.5 or earlier.Web Container Functionality Guide2.7
Extended use of applications that can be integrated with Bean ValidationBean Validation can now be used for validation in the CDI and user applications as well.This manualChapter 10
Supporting JavaMailThe mail sending and receiving functionality using JavaMail 1.4-compliant APIs is now available.This manualChapter 8
Extended use of the OS that can use the javacore commandThe javacore command can now be used to obtain the Windows thread dump.Command Reference Guidejavacore (Obtaining the thread dump/in Windows)

(4) Maintaining and improving reliability

The following table describes the items that are changed for maintaining and improving reliability.

Table 1-18 Changes made for maintaining and improving reliability

ItemOverview of changesReference manualReference section
Avoiding the depletion of the code cache areaThe size of the code cache area used in the system can now be checked, and the threshold value can be changed to avoid the depletion of area before the area is depleted.System Design Guide7.1.2
Maintenance and Migration Guide5.7.2, 5.7.3
Definition Reference Guide16.1, 16.2, 16.4
Supporting the efficient application of the Explicit Memory Management functionality
Expanding the range of the class-wise statistical information that is output
The functionality that can control the objects transferred to the Explicit heap is added as the functionality for reducing the automatic release processing time and applying the Explicit Memory Management functionality efficiently.
  • Functionality for controlling the transfer of objects to the Explicit memory block
  • Functionality for specifying the classes to be excluded from the Explicit Memory Management functionality
  • Output of the object release rate information in the Explicit heap information
The static field-based reference relationships can now be output to the extended thread dump containing 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 operability

The following table describes the items that are changed with the purpose of maintaining and improving operability.

Table 1-19 Changes made for maintaining and improving operability

ItemOverview of changesReference manualReference section
Supporting the EADs session failover functionalityThe EADs session failover functionality that implements the session failover functionality by integrating with the EADs is now supported.Expansion GuideChapter 5, Chapter 7
Operations using the WAR filesThe WAR applications configured only with WAR files can now be deployed on J2EE servers.Web Container Functionality Guide2.2.1
This manual13.9
Command Reference Guidecjimportwar (Importing WAR applications)
Starting and stopping the management functionality using synchronous executionA synchronous execution option is added for starting and stopping the 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 (Starting and stopping Administration Agent), mngautorun (Setting up and cancelling the settings for auto-start and auto-restart), mngsvrctl (Starting, stopping, and setting up Management Server)
Releasing the Explicit memory block forcefully with the Explicit Memory Management functionalityThe release processing of the Explicit memory block can now be executed at any time with the javagc command.Expansion Guide8.6.1, 8.9
Command Reference Guidejavagc (Forced garbage collection)

(6) Other purposes

The following table describes the items that are changed for other purposes.

Table 1-20 Changes made for other purposes

ItemOverview of changesReference manualReference section
Obtaining definition information
Output of the cjenvsetup command log
The snapshot (collecting the snapshot log) command can now be used to collect only definition files.
The execution information for the Component Container Administrator setup (the cjenvsetup command) is now output to the message log.
Maintenance and Migration Guide2.3
Command Reference Guidesnapshotlog (Collecting the snapshot log)
System Setup and Operation Guide4.1.4
Maintenance and Migration Guide4.20
Command Reference Guidecjenvsetup (Setting up Component Container Administrator)
Supporting BIG-IP v11BIG-IP v11 is now added to the available load balancer types.System Setup and Operation Guide4.7.2
Virtual System Setup and Operation Guide2.1
Output of the CPU time to the event log of the Explicit Memory Management functionalityThe CPU time taken for the Explicit memory block release processing is now output to the event log of the Explicit Memory Management functionality.Maintenance and Migration Guide5.11.3
Extending the functionality of the user-extended trace-based performance analysisThe following functionality is added in the user-extended trace-based performance analysis:
  • The trace target specification method can now be specified for packages or classes in addition to the usual trace target specification method for methods.
  • The range of available event IDs is expanded.
  • The restrictions on the number of lines that can be specified in the user-extended trace-based performance analysis setup file are relaxed.
  • The trace collection level can now be specified in the user-extended trace based performance analysis setup file.
Maintenance and Migration Guide7.5.2, 7.5.3, 8.28.1
Improving the analysis of information when asynchronous Session Bean invocation is usedThe root application information of the PRF trace can now be used to compare the invocation source and the invocation destination requests.EJB Container Functionality Guide2.17.3