A.5 Major functional changes in 09-50
- Organization of this subsection
(1) Improving development productivity
The following table outlines the changes made to improve development productivity.
Item |
Overview of changes |
Reference manual |
Relevant information |
---|---|---|---|
Simplifying setup of Eclipse |
The GUI can now be used to set up an Eclipse environment. |
Application Development Guide |
1.1.5, 2.4 |
Support for debugging using user extended performance analysis traces |
User extended performance analysis trace configuration files can now be created in the development environment. |
Application Development Guide |
1.1.3, 6.4 |
(2) Implementing standard and existing functionality
The following table outlines the changes made to enable implementation of standard and existing functionality.
Item |
Overview of changes |
Reference manual |
Relevant information |
---|---|---|---|
Support for JDBC 4.0 |
DB Connector now supports HiRDB Type4 JDBC Driver and SQL Server JDBC drivers that comply with the JDBC 4.0 specifications. |
Common Container Functionality Guide |
3.6.3 |
Easing of portable global JNDI naming rules |
Characters permitted for portable global JNDI names have been added. |
Common Container Functionality Guide |
2.4.3 |
Support for Servlet 3.0 |
Servlet 2.5 and earlier versions can now rename HTTP cookies and URL path parameters from Servlet 3.0. |
Web Container Functionality Guide |
2.7 |
Addition of applications that can link with Bean Validation |
CDI and user applications can now use Bean Validation. |
Common Container Functionality Guide |
Chapter 9 |
Support for JavaMail |
Email sending and receiving functionality that uses JavaMail 1.4-compliant API functions is now supported. |
Common Container Functionality Guide |
Chapter 7 |
Addition of OSs that are supported by the javacore command |
The javacore command can now be used to obtain Windows thread dumps. |
Command Reference Guide |
javacore (obtains thread dumps (Windows) ) |
(3) Maintaining and enhancing reliability
The following table outlines the changes made to maintain and enhance reliability.
Item |
Overview of changes |
Reference manual |
Relevant information |
---|---|---|---|
Avoiding a shortage of space in code cache areas |
A shortage of space in code cache areas can now be avoided by checking the size of a code cache area being used by the system and then changing the threshold values before a shortage of space occurs in the area. |
System Design Guide |
7.2.6 |
Maintenance and Migration Guide |
5.7.2, 5.7.3 |
||
Definition Reference Guide |
14.1, 14.2, 14.4 |
||
Support for efficient application of the Explicit Memory Management functionality |
Functions for controlling objects that are moved to the Explicit heap have been added to reduce the automatic release processing time and apply the Explicit Memory Management functionality efficiently:
|
System Design Guide |
7.14.6 |
Expansion Guide |
7.2.2, 7.6.5, 7.10, 7.13.1, 7.13.3 |
||
Maintenance and Migration Guide |
5.5 |
||
Extension of output range for statistical information by class |
Referential relationships based on the static field can now be output to extended thread dumps that contain statistical information by class. |
Maintenance and Migration Guide |
9.6 |
(4) Maintaining and enhancing availability
The following table outlines the changes made to maintain and enhance availability.
Item |
Overview of changes |
Reference manual |
Relevant information |
---|---|---|---|
Support for the EADs session failover functionality |
Functionality that links with EADs and achieves session failover is now supported. |
Expansion Guide |
Chapter 5 |
Operations by using WAR |
WAR applications that consist of only WAR files can now be deployed on J2EE servers. |
Web Container Functionality Guide |
2.2.1 |
Common Container Functionality Guide |
15.9 |
||
Command Reference Guide |
cjimportwar (imports WAR applications) |
||
Synchronously starting and stopping the operation management functionality |
An option for synchronously starting and stopping the operation management functionality (Management Server and Administration Agent) has been added. |
Operation, Monitoring, and Linkage Guide |
2.6.1, 2.6.2, 2.6.3, 2.6.4 |
Command Reference Guide |
adminagentctl (starts and stops Administration Agent), mngautorun (configures and cancels the configuration of automatic start and automatic restart), mngsvrctl (starts, stops, and sets up Management Server) |
||
Forced release of Explicit memory blocks by using the Explicit Memory Management functionality |
The javagc command can now be used to release the Explicit memory blocks at any time. |
Expansion Guide |
7.6.1, 7.9 |
Command Reference Guide |
javagc (forced execution of garbage collection) |
(5) Other purposes
The following table outlines the changes made for other purposes.
Item |
Overview of changes |
Reference manual |
Relevant information |
---|---|---|---|
Acquiring definition information |
The snapshot (snapshot log collection) command can now be used to collect only definition files. |
Maintenance and Migration Guide |
2.3 |
Command Reference Guide |
snapshotlog (collects snapshot logs) |
||
Output of logs by the cjenvsetup command |
Information about the execution of Component Container Administrator setup (cjenvsetup command) is now output to the message logs. |
System Setup and Operation Guide |
4.1.4 |
Maintenance and Migration Guide |
4.20 |
||
Command Reference Guide |
cjenvsetup (Component Container Administrator setup) |
||
Support for BIG-IP v11 |
BIG-IP v11, a type of load balancer, is now supported. |
System Setup and Operation Guide |
4.7.2 |
Output of CPU time to the event logs of the Explicit Memory Management functionality |
The CPU time required for releasing Explicit memory blocks is now output to the event logs of the Explicit Memory Management functionality. |
Maintenance and Migration Guide |
5.11.3 |
Functional enhancement of user extended performance analysis traces |
The following functions associated with user extended performance analysis traces have been added:
|
Maintenance and Migration Guide |
7.5.2, 7.5.3, 8.23.1 |
Improvement of information analysis when asynchronous Session Bean calls are used |
The source and target requests can now be matched by using the root application information in PRF traces. |
EJB Container Functionality Guide |
2.17.3 |