D.3 Main functionality changes in 09-70
- Organization of this subsection
(1) Supporting standard and existing functionality
he following table describes the items that are changed to support the standard and existing functionality.
Item |
Overview of changes |
Reference manual |
Reference |
---|---|---|---|
Addition of JSP compilation versions to the management portal |
Compilation methods compliant with JDK 1.7 specifications and those compliant with JDK 7 specifications are now supported as compilation methods for servlets generated from JSP files on the J2EE server. |
Management Portal User Guide |
10.8.4 |
Definition Reference Guide |
4.11.2 |
||
Support for Metaspace by JDK 8 |
The option for the Permanent area used to start JavaVM is changed to the option for the Metaspace area. |
System Setup and Operation Guide |
Appendix A.2 |
Management Portal User Guide |
10.8.7 |
||
Definition Reference Guide |
5.2.1, 5.2.2, Appendix A.2 |
||
Support for SHA-2 for user authentication by integrated user management |
SHA-224, SHA-256, SHA-384, and SHA-512 were added as the hash algorithms for user authentication by integrated user management. |
Security Management Guide |
5.3.1, 5.3.9, 5.10.7, 12.4.3, 12.5.3, 13.2, 14.2.2 |
Addition of automatic start, automatic restart, and automatic stop procedures in Red Hat Enterprise Linux Server 7 |
The procedures for automatically starting, restarting, and stopping Management Server and Administration Agent in Red Hat Enterprise Linux Server 7 were added. |
Operation, Monitoring, and Linkage Guide |
2.6.3, 2.6.4, 2.6.5 |
Command Reference Guide |
7.2 |
(2) Maintaining and improving operability
The following table describes the items that are changed with the purpose of maintaining and improving operability.
Item |
Overview of changes |
Reference manual |
Reference |
---|---|---|---|
Support for upgrading to V9.7 |
The procedure for changing the option for the Permanent area used to start JavaVM during a version upgrade to the option for the Metaspace area was added. |
This manual |
10.3.1, 10.3.2, 10.3.4 |
Operations using WAR files |
The WAR applications configured only with WAR files can now be deployed on the J2EE servers. |
Web Container Functionality Guide |
2.2.1 |
Common Container Functionality Guide |
15.9 |
||
Command Reference Guide |
cjimportwar (Import a WAR application) |
||
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) |
(3) Other purposes
The following table describes the items that are changed for other purposes.
Item |
Overview of changes |
Reference manual |
Reference |
---|---|---|---|
Snapshot log data to be collected |
JavaVM event log data and Management Server thread dump were added as snapshot log data to be collected. |
This manual |
|
Output of the cjenvsetup command log data |
Information about the execution of Component Container Administrator setup (cjenvsetup command) 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) |
||
Output of the CPU time to the event log of the Explicit Memory Management functionality |
The CPU time taken to perform processing to release the Explicit memory block is now output to the event log of the Explicit Memory Management functionality. |
This manual |
|
Enhancement of the user-extended trace based performance analysis |
The following functions were added to the user-extended trace based performance analysis:
|
This manual |
|
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 |