uCosminexus Application Server, Operation, Monitoring, and Linkage Guide

[Contents][Glossary][Index][Back][Next]

1.5 Main updates in the functionality of Application Server 09-50

This subsection describes the main updates in the functionality of Application Server 09-50 and the purpose of each change.

The contents described in this section are as follows:

Organization of this section
(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 describes the items that are changed to improve the development productivity.

Table 1-9 Changes made for improving the development productivity

Item Overview of changes Reference manual Reference location
Simplifying the Eclipse setup The Eclipse environment can now be set up by using GUI. Application Development Guide 1.1.5, 2.4
Supporting debug using the user extended performance analysis trace The user extended performance analysis trace configuration file can now be created in the development environment. Application Development Guide 1.1.3, 6.5

(2) Simplifying implementation and setup

The following table describes the items that are changed to simplify implementation and setup.

Table 1-10 Changes made for simplifying implementation and setup

Item Overview of changes Reference manual Reference location
Expansion of the system configuration pattern in a virtual environment The types of tiers (http-tier, j2ee-tier, and ctm-tier) usable in a virtual environment are now increased. Because of this, the following system configuration patterns can now be set up:
  • Pattern that allocates Web servers and J2EE servers to another host
  • Pattern that separates and deploys the front-end (servlet and JSP) and the back-end (EJB)
  • Pattern that uses CTM
Virtual System Setup and Operation Guide 1.1.2

(3) Supporting standard and existing functionality

The following table describes the items that are changed to support standard and existing functionality.

Table 1-11 Changes made for supporting standard and existing functionality

Item Overview of changes Reference manual Reference location
Supporting the JDBC 4.0 specifications HiRDB Type4 JDBC Driver of the JDBC 4.0 specifications and the JDBC driver of SQL Server are now supported by DB Connector. Common Container Functionality Guide 3.6.3
Relaxing the naming conventions for the Portable Global JNDI name. Usable characters have been added in the Portable Global JNDI name. Common Container Functionality Guide 2.4.3
Supporting the Servlet 3.0 specifications Updates of the HTTP Cookie name and the path parameter name of URL of Servlet 3.0 can now be used even with the versions earlier than Servlet 2.5. Web Container Functionality Guide 2.7
Applying the expansion of applications that can be integrated with Bean Validation Bean Validation can now be used and validated even with CDI and user applications. Common Container Functionality Guide Chapter 10
Supporting JavaMail The e-mail send and receive functionality that uses the JavaMail 1.4-compliant API can now be used. Common Container Functionality Guide Chapter 8
Applying the expansion of OSs in which the javacore command can be used The javacore command can now be used to acquire thread dumps of Windows. Command Reference Guide javacore (Acquiring thread dumps/ for Windows)

(4) Maintaining and improving reliability

The following table describes the items that are changed for maintaining and improving reliability.

Table 1-12 Changes made for maintaining and improving reliability

Item Overview of changes Reference manual Reference location
Avoiding exhaustion of the code cache area By confirming the size of the code cache area used in the system, and changing the threshold value before the area becomes exhausted, the area exhaustion can now be avoided. System Design Guide 7.1.2
Maintenance and Migration Guide 5.7.2, 5.7.3
Definition Reference Guide 16.1, 16.2, 16.4
Supporting efficient application of the Explicit Memory Management functionality
Expanding the output range of the class-wise statistical information
The automatic release processing time is now reduced, and the functionality that can control the objects moved to the Explicit heap has been added as the functionality to efficiently apply the Explicit Memory Management functionality.
  • The functionality to control the movement of objects to the Explicit memory block
  • The functionality to specify the Explicit Memory Management functionality exemption class
  • The output of the object release rate information to the Explicit heap information
The reference relationship that is based on the static field can now be output to the extended thread dump that includes the class-wise statistical information.
System Design Guide 7.13.6
Expansion Guide 8.2.2, 8.6.5, 8.10, 8.13.1, 8.13.3
Maintenance and Migration Guide 5.5
Maintenance and Migration Guide 9.6

(5) Maintaining and improving the operational performance

The following table describes the items that are changed for maintaining and improving operational performance.

Table 1-13 Changes made for maintaining and improving operational performance

Item Overview of changes Reference manual Reference location
Supporting the EADs session failover functionality The EADs session failover functionality that implements the session failover functionality by integrating with EADs is now supported. Expansion Guide Chapter 5, Chapter 7
Operating with WAR A WAR application that consists of only WAR files can now be deployed on a J2EE server. Web Container Functionality Guide 2.2.1
Common Container Functionality Guide 13.9
Command Reference Guide cjimportwar (Importing WAR applications)
Starting and stopping with the synchronous execution of the management functionality The option to synchronously execute the starting and stopping of the management functionality (Management Server and Administration Agent) has been added. This manual 2.6.1, 2.6.2, 2.6.3, 2.6.4
Command Reference Guide adminagentctl (Starting and stopping Administration Agent), mngautorun (Set up and unset up of automatic start and automatic restart), mngsvrctl (Starting, stopping, and set up of Management Server)
Forced release of the Explicit memory block in the Explicit Memory Management functionality The release processing of the Explicit memory block can now be executed at any timing using the javagc command. Expansion Guide 8.6.1, 8.9
Command Reference Guide javagc (Forced occurrence of garbage collection)

(6) Other purpose

The following table describes the items that are changed for other purposes.

Table 1-14 Changes made for other purposes

Item Overview of changes Reference manual Reference location
Acquiring the definition information Only the definition files can now be collected by the snapshot (snapshot log acquisition) command. Maintenance and Migration Guide 2.3
Command Reference Guide snapshotlog (Collection of snapshot log)
Log output of the cjenvsetup command The execution information of the Component Container administrator setup (the cjenvsetup command) can now be output to message logs. System Setup and Operation Guide 4.1.4
Maintenance and Migration Guide 4.20
Command Reference Guide cjenvsetup (Component Container administrator setup)
Supporting BIG-IP v11 BIG-IP v11 has been added to the types of usable load balancer. System Setup and Operation Guide 4.7.2
Virtual System Setup and Operation Guide 2.1
The output of the CPU time to the event log of the Explicit Memory Management functionality The CPU time required for the Explicit memory block release processing can now be output to the event logs of the Explicit Memory Management functionality. Maintenance and Migration Guide 5.11.3
Expending the functionality of the user extended performance analysis trace The following functionality have been added in the user extended performance analysis trace:
  • The specification methods for trace have been added to the specification methods of the regular method units, and can now be specified in each package or each class.
  • The range of the usable event ID has been extended.
  • The restriction on the number of lines that can be specified in the user extended performance analysis trace configuration file has been relaxed.
  • The trace acquisition level can now be specified in the user extended performance analysis trace configuration file.
Maintenance and Migration Guide 7.5.2, 7.5.3, 8.28.1
Improving the information analysis when using the asynchronous invocation of Session Beans The root application information of the PRF trace is used so that the requests of the invocation source and invocation destination can now be compared. EJB Container Functionality Guide 2.17.3