D.5 Main functionality changes in 09-50

Simplification of Eclipse setup

The GUI can now be used to set up the Eclipse environment.

Application Development Guide

1.1.5, 2.4

Support for debugging by using the user-extended trace based performance analysis

The user-extended trace based performance analysis configuration file can now be created in the development environment.

Application Development Guide

1.1.3, 6.4

Expansion of the system configuration patterns in a virtual environment

The number of tier types that can be used in a virtual environment (http-tier, j2ee-tier, and ctm-tier) increased. This makes it possible to set up the following system configuration patterns:

• Pattern that allocates the Web server and the J2EE server to different hosts

• Pattern that separately allocates the front end (servlets or JSPs) and the back end (EJBs)

• Pattern that uses the CTM

Virtual System Setup and Operation Guide

1.1.2

Support for the JDBC 4.0 specifications

DB Connector now supports HiRDB Type4 JDBC Driver and SQL Server JDBC drivers complying with the JDBC 4.0 specifications.

Common Container Functionality Guide

3.6.3

Relaxation of the naming rules for the Portable Global JNDI names

Characters that can be used for Portable Global JNDI names were added.

Common Container Functionality Guide

2.4.3

Support for the Servlet 3.0 specifications

The names of HTTP cookies and URL path parameters for Servlet 3.0 can now be changed in Servlet 2.5 or earlier.

Web Container Functionality Guide

2.7

Extended use of applications that can be integrated with Bean Validation

Bean Validation can now be used for validation in the CDI and user applications as well.

Common Container Functionality Guide

Chapter 9

Support for JavaMail

The email sending and receiving functionality that uses APIs compliant with JavaMail 1.4 can now be used.

Common Container Functionality Guide

Chapter 7

Expanded scope of OSs that can use the javacore command

The javacore command can now be used to obtain the Windows thread dump.

Command Reference Guide

javacore (Acquiring the thread dump/in Windows)

Avoidance of the depletion of the code cache area

The size of the code cache area used in the system can now be checked, and before the area is depleted, the threshold value can be changed to avoid the depletion of the area.

System Design Guide

7.2.6

This manual

5.7.2, 5.7.3

Definition Reference Guide

14.1, 14.2, 14.4

Support for the efficient application of the Explicit Memory Management functionality

Functionality that can control the objects transferred to the explicit heap was added as functionality for reducing the automatic release processing time and for efficiently applying the Explicit Memory Management functionality.

• Functionality that controls the transfer of objects to the Explicit memory block

• Functionality that specifies the classes to be excluded from those for which the Explicit Memory Management functionality is applied

• Output of the information about the object release rate to the explicit heap information

System Design Guide

7.14.6

Expansion Guide

7.2.2, 7.6.5, 7.10, 7.13.1, 7.13.3

This manual

5.5

Expansion of the output range of statistical information for each class

The static field-based reference relationship can now be output to the extended thread dump that includes statistical information for each class.

This manual

9.6

Support for the EADs session failover functionality

The EADs session failover functionality that implements the session failover functionality by integrating with the EADs is now supported.

Expansion Guide

Chapter 5

Operations by using WAR files

A WAR application configured by using only WAR files can now be deployed to a J2EE server.

Web Container Functionality Guide

2.2.1

Common Container Functionality Guide

15.9

Command Reference Guide

cjimportwar (Import a WAR application)

Start or stop of the management functionality by using synchronous execution

A synchronous execution option for starting or stopping the management functionality (Management Server and Administration Agent) was added.

Operation, Monitoring, and Linkage Guide

2.6.1, 2.6.2, 2.6.3, 2.6.4

Command Reference Guide

adminagentctl (start or stop Administration Agent), mngautorun (Set up/canceling the set up of autostart and autorestart), mngsvrctl (start, stop, or setup Management Server)

Forced release of the Explicit memory block of the Explicit Memory Management functionality

The processing to release the Explicit memory block can now be executed by using the javagc command at any timing.

Expansion Guide

7.6.1, 7.9

Command Reference Guide

javagc (forced execution of garbage collection)

Acquisition of definition information

The snapshotlog (collect snapshot logs) command can now be used to collect only the definition files.

This manual

2.3

Command Reference Guide

snapshotlog (collect snapshot logs)

Output of the cjenvsetup command log data

Information about the execution of Component Container Administrator setup (cjenvsetup command) is not output to the message log.

System Setup and Operation Guide

4.1.4

This manual

4.20

Command Reference Guide

cjenvsetup (set up Component Container Administrator)

Support for BIG-IP v11

BIG-IP v11 was added to the available load balancer types.

System Setup and Operation Guide

4.7.2

Virtual System Setup and Operation Guide

2.1

Output of the CPU time to the event log of the Explicit Memory Management functionality

The CPU time taken to perform the processing to release the Explicit memory block is now output to the event log of the Explicit Memory Management functionality.

This manual

5.11.3

Enhancement of the user-extended trace based performance analysis

The following functions were added to the user-extended trace based performance analysis:

• Trace targets can now be specified in units of packages or classes in addition to being specified in units of methods, which is the usual specification method.

• The range of available event IDs was expanded.

• The restrictions on the number of lines that can be specified in the user-extended trace based performance analysis configuration file were relaxed.

• The trace collection level can now be specified in the user-extended trace based performance analysis configuration file.

This manual

7.5.2, 7.5.3, 8.23.1

Improvement of the analysis of information when the asynchronous Session Bean invocation is used

The root application information of the PRF trace can now be used to compare the requests of the invocation source and the invocation destination.

EJB Container Functionality Guide

2.17.3