uCosminexus Application Server, EJB Container Functionality Guide
The following table describes the items that are changed for improving the development productivity:
Table B-21 Changes for improving the development productivity
Item | Overview of change | Reference manual | Reference location |
---|---|---|---|
Simplifying migration from another Application Server product | The following functionality can be used for the smooth migration from another Application Server product:
|
Web Container Functionality Guide | 2.3, 2.7.5 |
Providing cosminexus.xml | By describing the attributes unique to Application Server in cosminexus.xml, a J2EE application can be started without setting up the property, once the J2EE application is imported to the J2EE server. | Common Container Functionality Guide | 11.3 |
The following table describes the items that are changed to support standard functionality:
Table B-22 Changes made for supporting standard functionality
Item | Overview of change | Reference manual | Reference location |
---|---|---|---|
Supporting Servlet 2.5 | Servlet 2.5 is supported. | Web Container Functionality Guide | 2.2, 2.5.4, 2.6, Chapter 6 |
Supporting JSP 2.1 | JSP 2.1 is supported. | Web Container Functionality Guide | 2.3.1, 2.3.3, 2.5, 2.6, Chapter 6 |
JSP debug | JSP debugging can be performed in the development environment by using MyEclipse.# | Web Container Functionality Guide | 2.4 |
Saving the tag library in library JAR and mapping TLD | When the tag library is saved in library JAR, the TLD files in library JAR can be searched by the Web container when the Web application is running, and then TLD files can be mapped automatically. | Web Container Functionality Guide | 2.3.4 |
Omitting application.xml | application.xml can be omitted in the J2EE application. | Common Container Functionality Guide | 11.4 |
Combined use of annotation and DD | Annotations can be used together with DD, and the contents specified in the annotation can be updated in the DD. | Common Container Functionality Guide | 12.5 |
Compliance of annotations with the Java EE 5 standard (default interceptor) | The default interceptor can be saved in the library JAR. Furthermore, DI can be performed from the default interceptor. | Common Container Functionality Guide | 11.4 |
Reference resolution of @Resource | Reference resolution of a resource can be performed with @Resource. | Common Container Functionality Guide | 12.4 |
Supporting JPA | JPA specifications are supported. | Common Container Functionality Guide | Chapter 5 and 6 |
The following table describes the items that are changed for maintaining and improving reliability:
Table B-23 Changes made for maintaining and improving operation performance
Item | Overview of change | Reference manual | Reference location |
---|---|---|---|
Persistence of session information | The session information of an HTTP session can be saved in the database, and can be inherited. | Expansion Guide | Chapter 5 and 6 |
Preventing a full garbage collection | The occurrence of a full garbage collection can be prevented by allocating the object that causes the full garbage collection outside the Java heap. | Expansion Guide | Chapter 8 |
Client performance monitor | The time consumed in client processing can be checked and analyzed. | -- | -- |
The following table describes the items that are changed for maintaining and improving operation performance:
Table B-24 Changes made for maintaining and improving operation performance
Item | Overview of change | Reference manual | Reference location |
---|---|---|---|
Improving the operability of applications in Operations Management Portal | About application and resource operations, the server management command and Operations management portal can now perform mutual operations. | Management Portal User Guide | 1.1.3 |
The following table describes the items changed for some other purposes:
Table B-25 Changes for some other purposes
Item | Overview of change | Reference manual | Reference location |
---|---|---|---|
Deleting disabled HTTP cookie | Disabled HTTP cookie can be deleted. | Web Container Functionality Guide | 2.7.4 |
Detecting a naming service failure | When a failure occurs in the naming service, the EJB client can now detect the error faster. | Common Container Functionality Guide | 2.9 |
Connection failure detection timeout | The timeout period for a connection failure detection timeout can be specified. | Common Container Functionality Guide | 3.15.1 |
Supporting Oracle11g | Oracle11g can be used as a database. | Common Container Functionality Guide | Chapter 3 |
Scheduling batch processing | The execution of batch applications can be scheduled with CTM. | Expansion Guide | Chapter 4 |
Batch processing log | Changes have been made in such a way so that the size and number of log files of batch execution commands, retry frequency, and retry interval (when a failure occurs in the log exclusion processing) can be specified. | Definition Reference Guide | 3.6 |
Snapshot log | The collection details of the snapshot log have been changed. | Maintenance and Migration Guide | Appendix A.1, Appendix A.2 |
Publication of the protected area of method cancellation | The contents of the protected area list to which method cancellation is not applicable are published. | Operation, Monitoring, and Linkage Guide | Appendix C |
Functionality for selecting garbage collection before statistics output | Whether or not to execute a garbage collection can be selected before the statistical information for each class is output. | Maintenance and Migration Guide | 9.7 |
Functionality for the output of age distribution information of the Survivor area | The age distribution information of the Java objects of Survivor area can be output to the JavaVM log file. | Maintenance and Migration Guide | 9.11 |
Functionality for eliminating the finalize stagnation | The stagnation of the finalize processing of JavaVM can be eliminated by monitoring the status of the processing. | -- | -- |
Changing the maximum heap size of the server management commands | The maximum heap size used by server management commands has been changed. | Definition Reference Guide | 5.2, 5.3 |
Support when a display name that is not recommended is specified | A message will now be output when a display name that is not recommended in J2EE application is specified | Messages | KDJE42374-W |
All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.