D.5 Main functional changes in version 09-50

Organization of this subsection

(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 operational performance
(6) Other purpose

(1) Improving development productivity

The following table lists the items for which changes were made to improve development productivity.

Table D‒10: Changes made for improving development productivity
Item	Overview of changes	Reference manual	Reference location
Simplification of Eclipse setup	An Eclipse environment can now be set up from the GUI.	Application Development Guide	1.1.5, 2.4
Aid for debugging with user-extended performance analysis traces	A user-extended performance analysis trace configuration file can now be created in the development environment.	Application Development Guide	1.1.3, 6.4

To Page Top

(2) Simplifying implementation and setup

The following table lists the items that are changed to simplify implementation and setup:

Table D‒11: Changes made for simplifying implementation and setup
Item	Overview of changes	Reference manual	Reference location
Addition of system configurations in a virtualization environment	Additional tier types (`http-tier`, `j2ee-tier`, and `ctm-tier`) can now be used in a virtualization environment. As a result, systems can now be built in the following configurations: Configuration in which a web server and J2EE server are deployed on different hosts Configuration in which the front-end (servlet and JSP) and back-end (EJB) are separately deployed Configuration that uses CTM	Virtual System Setup and Operation Guide	1.1.2

To Page Top

(3) Supporting standard and existing functionality

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

Table D‒12: Changes made for supporting standard and existing functionality
Item	Overview of changes	Reference manual	Reference location
Support for the JDBC 4.0 specifications	DB Connector now supports HiRDB Type4 JDBC Driver compliant with JDBC 4.0 and the JDBC driver for SQL Server.	Common Container Functionality Guide	3.6.3
Relaxation of the naming rules for Portable Global JNDI names	Characters that can be used in Portable Global JNDI names were added.	Common Container Functionality Guide	2.4.3
Support for the Servlet 3.0 specifications	HTTP Cookie names and URL path parameter names can now be changed in Servlet 2.5 or earlier as they can be changed in Servlet 3.0.	Web Container Functionality Guide	2.7
Expansion of applications that can link with Bean Validation	Bean Validation can now be used with the CDI or a user application to perform validation.	Common Container Functionality Guide	Chapter 9
JavaMail support	An email sending and receiving function that uses an API compliant with JavaMail 1.4 can now be used.	Common Container Functionality Guide	Chapter 7
OSs supported by the `javacore` command	The `javacore` command can now be used to obtain thread dumps in Windows.	Command Reference Guide	javacore (Acquiring the thread dump/in Windows)

To Page Top

(4) Maintaining and improving reliability

The following table lists the items that are changed for maintaining and improving reliability:

Table D‒13: Changes made for maintaining and improving the reliability
Item	Overview of changes	Reference manual	Reference location
Prevention of depletion of the code cache area	Depletion of the code cache area can now be prevented by checking the size of the area used by the system and changing the threshold value before depletion occurs.	Maintenance and Migration Guide	5.7.2, 5.7.3
Prevention of depletion of the code cache area		Definition Reference Guide	14.1, 14.2, 14.4
Efficient use of the Explicit Memory Management functionality	The following functions were added that can control the objects that move to the Explicit heap so that the time required for automatic release is reduced to efficiently apply the Explicit Memory Management functionality. Function that controls object movement to Explicit memory blocks Function that specifies classes to which the Explicit Memory Management functionality is not applied	Expansion Guide	7.2.2, 7.6.5, 7.10, 7.13.1, 7.13.3
		Maintenance and Migration Guide	5.5
Expansion of the output range of class-wise statistical information	An extended thread dump containing class-wise statistical information can now include reference relationships based on static fields.	Maintenance and Migration Guide	9.6

To Page Top

(5) Maintaining and improving the operational performance

The following table lists the items that are changed for maintaining and improving operational performance:

Table D‒14: Changes made for maintaining and improving operational performance
Item	Overview of changes	Reference manual	Reference location
Support for the EADs session failover functionality	The EADs session failover functionality, which enables session failover in collaboration with EADs, is supported.	Expansion Guide	Chapter 5
Operations using WAR files	A WAR application that consists of only WAR files can now be deployed on the J2EE server.	Web Container Functionality Guide	2.2.1
		Common Container Functionality Guide	15.9
		Command Reference Guide	cjimportwar (Import a WAR application)
Synchronous start and stop of the management functionality	An option that synchronously starts and stops the management functionality (Management Server and Administration Agent) was added.	This manual	2.6.1, 2.6.2, 2.6.3, 2.6.4
Synchronous start and stop of the management functionality		Command Reference Guide	adminagentctl (start or stop Administration Agent), mngautorun (Set up/canceling the set up of autostart and autorestart), and mngsvrctl (start, stop, or setup Management Server)
Forced release of Explicit memory blocks by the Explicit Memory Management functionality	The `javagc` command can now be used to release Explicit memory blocks at any time.	Expansion Guide	7.6.1, 7.9
		Command Reference Guide	javagc (forcibly perform GC)

To Page Top

(6) Other purpose

The following table lists the items that are changed for other purpose:

Table D‒15: Changes made for other purposes
Item	Overview of changes	Reference manual	Reference location
Acquisition of definition information	The `snapshotlog` command (collect snapshot logs) can now be used to collect definition files only.	Maintenance and Migration Guide	2.3
Acquisition of definition information		Command Reference Guide	snapshotlog (collect snapshot logs)
Output of log data for the `cjenvsetup` command	The information about setup operations (using the `cjenvsetup` command) performed by the Component Container administrator is now output to the message log.	System Setup and Operation Guide	4.1.4
		Maintenance and Migration Guide	4.20
		Command Reference Guide	cjenvsetup (set up Component Container Administrator)
BIG-IP v11 support	BIG-IP v11 was added as a type of load balancer that can be used.	System Setup and Operation Guide	4.7.2
BIG-IP v11 support		Virtual System Setup and Operation Guide	2.1
Output of the CPU time to the event log for the Explicit Memory Management functionality	The CPU time required to release Explicit memory blocks is now output to the event log for the Explicit Memory Management functionality.	Maintenance and Migration Guide	5.11.3
Extension of the user-extended performance analysis trace functionality	The following changes were made to the user-extended performance analysis trace functionality: Although the trace target could be specified by only method, it can now also be specified by package or class. The range of applicable event IDs was expanded. The maximum number of lines that can be contained in the user-extended performance analysis trace configuration file was increased. The user-extended performance analysis trace configuration file can now be used to specify the trace collection level.	Maintenance and Migration Guide	7.5.2, 7.5.3, 8.23.1
Improvement of information analysis in cases where asynchronous Session Bean invocations are used	The requests of invocation source and destination can now be matched by using the root application information of the PRF trace.	EJB Container Functionality Guide	2.17.3

To Page Top