uCosminexus Application Server, Operation, Monitoring, and Linkage Guide
The following table lists the items that are changed for improving the development productivity:
Table D-21 Changesmade for improving the development productivity
Item | Overview of changes | Reference manual | Section |
---|---|---|---|
Easy migration from other Application Server products | The use of the following functionality was enabled for smooth migration from other Application Server products:
|
Web Container Functionality Guide | 2.3, 2.7.5 |
Provision of cosminexus.xml | By specifying the Cosminexus Application Server independent property in cosminexus.xml, J2EE applications can be started without specifying the property settings after being imported into the J2EE server. | Common Container Functionality Guide | 11.3 |
The following table lists the items that are changed to support the standard functionality:
Table D-22 Changesmade for supporting standard functionality
Item | Overview of changes | Reference manual | Section |
---|---|---|---|
Support for Servlet 2.5 | Servlet 2.5 is supported. | Web Container Functionality Guide | 2.2, 2.5.4, 2.6, Chapter 6 |
Support for 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 debugging | JSP debugging can now be performed in the development environment using MyEclipse. # | Web Container Functionality Guide | 2.4 |
Storing tag library in the library JAR and TLD mapping | If the tag library is stored in the library JAR, the following processing occurs: When the Web application starts, the TLD file in the library JAR is searched by the Web container and can be automatically mapped. |
Web Container Functionality Guide | 2.3.4 |
Omitting application.xml | application.xml can now be omitted in J2EE applications. | Common Container Functionality Guide | 11.4 |
Combined use of annotation and DD | Annotation and DD can now be used together and the contents specified in annotation can be updated in DD. | Common Container Functionality Guide | 12.5 |
Conforming annotation to Java EE 5 standards (default interceptor) | The default interceptor can now be stored in the library JAR. Also, DI can be performed from the default interceptor. | Common Container Functionality Guide | 11.4 |
Resolving the @Resource references | The resource references can now be resolved with @Resource. | Common Container Functionality Guide | 12.4 |
Support for JPA | JPA specifications are supported. | Common Container Functionality Guide | Chapter 5, Chapter 6 |
The following table lists the items that are changed for maintaining and improving reliability:
Table D-23 Changesmade for maintaining and improving the reliability
Item | Overview of changes | Reference manual | Section |
---|---|---|---|
Persistence of session information | The session information of the HTTP session can now be saved and inherited in the database. | Expansion Guide | Chapter 5, Chapter 6 |
Control of full garbage collection | By deploying the object that causes full garbage collection outside the Java heap, the occurrence of full garbage collection can now be controlled. | Expansion Guide | Chapter 8 |
Client performance monitor | The time required for client processing can now be checked or analyzed. | -- | -- |
The following table lists the items that are changed for maintaining and improving operational performance:
Table D-24 Changesmade for maintaining and improving operational performance
Item | Overview of changes | Reference manual | Section |
---|---|---|---|
Improving the operational performance of applications on the management portal | The server management commands and management portal can now be interoperated for the application and resource operations. | Management Portal User Guide | 1.1.3 |
The following table lists the items that are changed for other purpose:
Table D-25 Changes made for other purposes
Item | Overview of changes | Reference manual | Section |
---|---|---|---|
Deleting invalid HTTP Cookie | Invalid HTTP Cookies can now be deleted. | Web Container Functionality Guide | 2.7.4 |
Detecting Naming Service failure | When a naming service failure occurs, the EJB client can now detect the error faster. | Common Container Functionality Guide | 2.9 |
Timeout in detecting connection failure | A timeout value can now be specified for the connection failure detection timeout. | Common Container Functionality Guide | 3.15.1 |
Support for Oracle11g | Oracle11g can now be used as the database. | Common Container Functionality Guide | Chapter 3 |
Scheduling of batch processing | The execution of batch applications can now be scheduled using CTM. | Expansion Guide | Chapter 4 |
Batch processing log | Changes have been made so that the size and number of log files of batch execution commands, and the 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 collected contents of the snapshot log are changed. | Maintenance and Migration Guide | Appendix A.1, Appendix A.2 |
Releasing the protected area of method cancellation | The contents of the protected area list that are not the target for method cancellation were released. | This manual | Appendix C |
Select garbage collection before statistics functionality | You can now select whether to execute garbage collection before the class-wise statistical information is output. | Maintenance and Migration Guide | 9.7 |
Age distribution information output functionality for survivor area | The age distribution information of the Java objects in the Survivor area can now be output in the JavaVM log file. | Maintenance and Migration Guide | 9.11 |
Finalize retention cancellation functionality | The JavaVM finalize processing status can now be monitored and processing retention can be cancelled. | -- | -- |
Changing the maximum heap size of the server management command | The maximum heap size used by the server management command has changed. | Definition Reference Guide | 5.2, 5.3 |
Support when non-recommended display name has specified. | When an unrecommended display name has specified for a J2EE application, a message will now be displayed. | Messages | KDJE42374-W |
All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.