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

This section 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 operation performance
(6) Other purposes

(1) Improving development productivity

The following table describes the items that were changed to improve development productivity.

Table 1-6 Changes made for improving the development productivity

ItemOverview of changesReference manualReference
Simplifying the Eclipse setupThe Eclipse environment can now be set up by using a GUI.Application Development Guide1.1.5, 2.4
Supporting debug by using the user expanded performance analysis traceThe user expanded performance analysis trace setup file can now be created in the development environment.Application Development Guide1.1.3, 6.5

(2) Simplifying implementation and setup

The following table describes the items that were changed to simplify implementation and setup:

Table 1-7 Changes made for simplifying implementation and setup

ItemOverview of changesReference manualReference
Expanding the system configuration patterns in the virtual environmentThe types of tiers (http-tier, j2ee-tier and ctm-tier) that can be used in the virtual environment have increased. The following system configuration patterns can now be configured in accordance with this:
  • A pattern of configuring the Web server and J2EE server on separate hosts
  • A pattern of configuring by separating the front end (servlet, JSP) and backend (EJB)
  • A pattern of using CTM
Virtual System Setup and Operation Guide1.1.2

(3) Supporting standard and existing functionality

The following table describes the items that were changed to support standard and existing functionality:

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

ItemOverview of changesReference manualReference
Supporting the JDBC 4.0 specificationsDB Connector now supports the HiRDB Type4 JDBC Driver with JDBC 4.0 specifications and the JDBC Driver of SQL Server.Common Container Functionality Guide3.6.3
Simplifying the naming conventions in the Portable Global JNDI nameThe characters that can be used in the Portable Global JNDI name have been added.Common Container Functionality Guide2.4.3
Supporting the Servlet 3.0 specificationsYou can now use the changed HTTP Cookie name and the URL path parameter name of Servlet 3.0 even in versions earlier than Servlet 2.5.This manual2.7
Extending the applicability of the applications that can be integrated with Bean ValidationThe CDI or user applications can also be verified now by using Bean Validation.Common Container Functionality GuideChapter 10
Supporting JavaMailThe mail send and receive function that uses JavaMail 1.4 compliant APIs can now be used.Common Container Functionality GuideChapter 8
Expanding the applicability of OSs on which the javacore command can be usedThe thread dump of Windows can now be acquired by using the javacore command.Command Reference Guidejavacore (acquiring the thread dump/when using Windows)

(4) Maintaining and improving reliability

The following table describes the items that were changed for maintaining and improving reliability:

Table 1-9 Changes for maintaining and improving reliability

ItemOverview of changesReference manualReference
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 Guide7.1.2
Maintenance and Migration Guide5.7.2, 5.7.3
Server Definition Reference Guide16.1, 16.2, 16.4
Supporting the effective application of the Explicit management functionalityA functionality that can control the objects to be moved to the Explicit heap is now added as the functionality for effective application of the explicit management function by curtailing the auto-release processing time.
  • Functionality for controlling the moving of objects to the Explicit memory block
  • Functionality for specifying the application exclusion class for the explicit management functionality
  • Output of the object release rate information to the Explicit heap information
System Design Guide7.13.6
Expansion Guide8.2.2, 8.6.5, 8.10, 8.13.1, 8.13.3
Maintenance and Migration Guide5.5
Expanding the output range of the class wise statistical informationThe reference relation based on the static field can now be output in the expanded thread dump that includes the class wise statistical information.Maintenance and Migration Guide9.6

(5) Maintaining and improving operation performance

The following table describes the items that were changed for maintaining and improving operation performance:

Table 1-10 Changes for maintaining and improving operation performance

ItemOverview of changesReference manualReference
Supporting the EADs session failover functionalityThe EADs session failover functionality that implements the session failover functionality by integrating with EADs is now supported.Expansion GuideChapter 5, Chapter 7
Operations by WARThe WAR applications that are configured only by the WAR files can now be deployed on the J2EE server.This manual2.2.1
Common Container Functionality Guide13.9
Command Reference Guidecjimportwar (importing WAR applications)
Starting and stopping by the concurrent execution of the management functionalityThe startup and stopping of the management functionality (Management Server and Administration Agent) has been added to the option for concurrent execution.Operation, Monitoring, and Linkage Guide2.6.1, 2.6.2, 2.6.3, 2.6.4
Command Reference Guideadminagentctl (starting and stopping Administration Agent), mngautorun (setting/cancelling the setting of automatic start and automatic restart), mngsvrctl (starting, stopping and setting up Management Server)
Forcibly releasing the Explicit memory block in the Explicit management functionalityThe Explicit memory block can now be released at any time, by using the javagc command.Expansion Guide8.6.1, 8.9
Command Reference Guidejavagc (forcibly generating the garbage collection)

(6) Other purposes

The following table describes the items that were changed for other purposes:

Table 1-11 Changes due to other purposes

ItemOverview of changesReference manualReference
Acquiring the definition information
Performing the log output of the cjenvsetup command
Only the definition files can now be collected by using the snapshot (collecting the snapshot log) command.
The execution information of the Component Container administrator setup (cjenvsetup command) can now be output in the message log.
Maintenance and Migration Guide2.3
Command Reference Guidesnapshotlog (collecting the snapshot log)
uCosminexus BPM/ESB Service Platform System Setup and Operation Guide4.1.4
Maintenance and Migration Guide4.20
Command Reference Guidecjenvsetup (setting up the Component Container administrator)
Supporting BIG-IP v11BIG-IP v11 has been added to the available types of the load balancers.uCosminexus BPM/ESB Service Platform System Setup and Operation Guide4.7.2
Virtual System Setup and Operation Guide2.1
Performing the output of the CPU time to the event log of the Explicit management functionalityThe CPU time required for releasing the Explicit memory block can now be output to the event log of the Explicit management functionality.Maintenance and Migration Guide5.11.3
Expanding the functionality of the user expanded performance analysis traceThe following functionality have now been added to the user expanded performance analysis trace:
  • The specification method to be traced can now be added to the specification method in the method unit and can be specified in the package unit or class unit.
  • The range of the available event IDs has been expanded.
  • Released the restrictions on the number of lines that can be specified in the user expanded performance analysis trace setup file.
  • The trace acquisition level can now be specified in the user expanded performance analysis trace setting file.
Maintenance and Migration Guide7.5.2, 7.5.3, 8.28.1
Improving the information analysis used at the time of asynchronous calling of Session BeanThe requests at the calling source and the requests at the calling destination can now be compared by using the root application information of the PRF trace.EJB Container Functionality Guide2.17.3