Appendix F.4 Main functionality changes in 08-50

Organization of this subsection
(1) Simplifying installation and setup
(2) Supporting standard and existing functionality
(3) Maintaining and improving reliability
(4) Maintaining and improving operability
(5) Other purposes

(1) Simplifying installation and setup

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

Table F-16 Changes made for simplifying installation and setup

ItemOverview of changesReference manualReference location
Changing the mandatory tags for specifying web.xml in the Web Service providerThe specification of the listener tag, servlet tag, and servlet-mapping tag was changed from mandatory to optional in web.xml in the Web Service provider.Definition Reference Guide2.4
Using the network resources of the logical serverThe functionality for accessing the network resources and network drive existing on another host from the J2EE applications was added.Operation, Monitoring, and Linkage Guide1.2.3, 5.2, 5.7
Simplifying the execution procedure of the sample programThe procedure of executing the sample program was simplified by providing a part of the sample program in the EAR format.First Step Guide3.5
System Setup and Operation GuideAppendix M
Improving the operations in the management portal windowThe default update interval of the window was changed from "Do not update" to "3 seconds".Management Portal User Guide7.4.1
Improving the Setup Wizard completion windowThe Easy Setup definition file and HITACHI Connector Property file used for setup are now displayed on the window displayed when the Setup Wizard finishes operations.System Setup and Operation Guide2.2.6
Setting up the virtual environmentThe procedure of setting up Application Server on the virtual server, implemented by using a hypervisor, has been added. #Virtual System Setup and Operation GuideChapter 3, Chapter 5
#
To set up in the 08-50 mode, see Appendix D Settings to Use the Virtual Server Manager in the 08-50 Mode in the uCosminexus Application Server Virtual System Setup and Operation Guide.

(2) Supporting standard and existing functionality

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

Table F-17 Changes made for supporting standard and existing functionality

ItemOverview of changesReference manualReference location
Supporting invocation from OpenTP1The Message-driven Beans running on Application Server can now be invoked from OpenTP1.This manualChapter 4
Supporting JMSThe Cosminexus JMS Provider functionality conforming to the JMS 1.1 specifications can now be used.This manualChapter 7
Supporting Java SE 6The Java SE 6 functionality can now be used.Maintenance and Migration Guide5.5, 5.8.1
Supporting the use of genericsGenerics can now be used with EJB.EJB Container Functionality Guide4.2.19

(3) Maintaining and improving reliability

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

Table F-18 Changes made for maintaining and improving reliability

ItemOverview of changesReference manualReference location
Improving the usability of the Explicit Memory Management functionalityThe Explicit Memory Management functionality can now be used easily by using the automatic allocation configuration file.System Design Guide7.1.1, 7.6.3, 7.10.5, 7.11.1
Expansion GuideChapter 8
Controlling the database session failover functionality for URIsWhen using the database session failover functionality, you can now specify the requests that will be outside the scope of the functionality for URIs.Expansion Guide5.6.1
Monitoring errors in the virtual environmentIn a virtual system, the virtual server is now monitored and the occurrence of errors can be detected.Virtual System Setup and Operation GuideAppendix D

(4) Maintaining and improving operability

The following table describes the items that are changed with the purpose of maintaining and improving operability.

Table F-19 Changes with the purpose of maintaining and improving operability

ItemOverview of changesReference manualReference location
Omitting the management user accountThe login ID and password of the user can now be omitted in the management portal, Management Server commands, or Smart Composer functionality commands.System Setup and Operation Guide4.1.15
Management Portal User Guide2.2, 7.1.1, 7.1.2, 7.1.3, 8.1, 8.2.1, Appendix F.2
Command Reference Guide1.4, mngsvrctl (Starting/ stopping/ setting up Management Server), mngsvrutil (Management Server management commands), 8.3, cmx_admin_passwd (Setting up the management user account of Management Server)
Virtual environment operationsThe procedure of executing batch start, batch stop, scale in, and scale out for multiple virtual servers has been added in the virtual system. #Virtual System Setup and Operation GuideChapter 4, Chapter 6
#
To operate in the 08-50 mode, see Appendix D Settings to Use the Virtual Server Manager in the 08-50 Mode in the uCosminexus Application Server Virtual System Setup and Operation Guide.

(5) Other purposes

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

Table F-20 Changes due to other purposes

ItemOverview of changesReference manualReference location
Unused objects statistical functionality in the Tenured areaOnly the unused objects can now be identified in the Tenured area.Maintenance and Migration Guide9.8
Base object list output functionality for Tenured augmentation factorsThe information of the objects that form the base of unused objects, identified by using the unused objects statistical functionality in the Tenured area, can now be output.9.9
Class-wise statistical information analysis functionalityThe class-wise statistical information can now be output in the CSV format.9.10
Cluster node switching based on the detection of the exceeding of the auto-restart frequency of the logical serverNode switching can now be executed when the logical server is in an abnormally stopped state (state in which the auto-restart count is exceeded, or state in which an error is detected when the auto-restart count is set to 0) in a cluster configuration wherein Management Server is to be monitored for node switching.Operation, Monitoring, and Linkage Guide18.4.3, 18.5.3, 20.2.2, 20.3.3, 20.3.4
Node switching system for the host unit management modelNode switching can now be executed for the host unit management model in the system operations integrated with the cluster software.Chapter 20
Supporting ACOS (AX2000, BS320)ACOS (AX2000, BS320) was added to the types of load balancers that are available.System Setup and Operation Guide4.7.2, 4.7.3, 4.7.5, 4.7.6, Appendix K, Appendix K.2
Definition Reference Guide4.5, 4.6.2, 4.6.4, 4.6.5, 4.6.6, 4.10.1
Transaction attributes that can be specified in the Stateful Session Bean (SessionSynchronization) for CMT-managed transactions, have been addedSupports, NotSupported, and Never can now be specified as the transaction attributes in the Stateful Session Bean (SessionSynchronization), for CMT-managed transactions.EJB Container Functionality Guide2.7.3
Forcefully terminating Administration Agent when OutOfMemoryError occursAdministration Agent is now forcefully terminated when OutOfMemoryError occurs in JavaVM.Maintenance and Migration Guide2.5.8
Asynchronous parallel processing of threadsAsynchronous timer processing and asynchronous thread processing can now be implemented by using TimerManager and WorkManager.Expansion GuideChapter 10