A.3 Major functional changes in 09-70

JSP compilation methods in the management portal

The compilation methods compliant with JDK 1.7 specifications and with JDK 7 specifications were additionally supported for servlets generated from JSP files on the J2EE server.

Definition Reference Guide

4.11.2

Metaspace support in JDK 8

The options for the Permanent area used for Java VM startup were changed to the options for the Metaspace area.

System Setup and Operation Guide

A.2

Definition Reference Guide

5.2.1, 5.2.2, 8.2.3

SHA-2 support for user authentication in the integrated user management

The following hash algorithms for user authentication in the integrated user management were additionally supported: SHA-224, SHA-256, SHA-384, SHA-512

This manual

5.3.1, 5.3.9, 5.10.7, 11.4.3, 12.4.3, 12.5.3, 13.2, 14.2.2

Automatic start, restart, and stop in Red Hat Enterprise Linux Server 7

Automatic start, restart, and stop were supported by Management Server and Administration Agent that operate on Red Hat Enterprise Linux Server 7.

Maintenance and Migration Guide

2.6.3, 2.6.4, 2.6.5

Command Reference Guide

7.2

Upgrade to version 9.7

A procedure for changing the options for the Permanent area used for Java VM startup to the options for the Metaspace area was added.

Maintenance and Migration Guide

10.3.1, 10.3.2, 10.3.4

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 (imports WAR applications)

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.

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), 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 (forced execution of garbage collection)

Collection-target data for the snapshot log

Java VM event log data and Management Server thread dumps were added to the collection targets for the snapshot log.

Maintenance and Migration Guide

A.2

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)

Support for BIG-IP v11

BIG-IP v11 was added as a type of load balancer that can be used.

System Setup and Operation Guide

4.7.2

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