uCosminexus Application Server, Maintenance and Migration Guide

Summary of amendments

The following table lists changes in the manual 3020-3-Y11-10(E) for uCosminexus Application Server 09-50, uCosminexus Application Server(64) 09-50, uCosminexus Client 09-50, uCosminexus Developer 09-50, uCosminexus Service Architect 09-50, uCosminexus Service Platform 09-50, uCosminexus Service Platform(64) 09-50 and product changes related to the manual:

Changes	Location
The functionality has been added for collecting the definition sending data in the snapshotlog (snapshot log collection) command.	2.3, 2.3.3, 2.3.4, 2.4, 2.4.2, Appendix A
A description has been added for the output destination of the trace based performance analysis file.	2.3.2
A description has been added for the action to be taken when an error occurs using the EADs session failover functionality.	2.5.4
The description has been changed for the action to be taken when JavaVM terminates abnormally.	2.5.7
An example has been added for executing the cjdumpsv command to obtain the J2EE server thread dump when an error occurs in a Web server.	3.3.1(3)
A description has been added for the functionality for obtaining the user dump when the logical server is terminated forcefully in an environment set up with Management Server in Windows.	3.3.17
A description has been added for the execution information of the Component Container Administrator setup command (in UNIX).	4.20
An option (-XX:+JITCompilerContinuation) has been added as an option that can be specified for obtaining the JavaVM log, using the JIT compiler continuation functionality.	3.3.19, 4.10, 5.7.1
A description has been added for the Explicit memory block release ratio information to be output to the extended thread dump.	4.7.3, 5.5
A description has been added for the code cache area information to be output to JavaVM log files.	5.7.2, 5.7.3
A description has been added for the following items output to the event log of the Explicit Memory Management functionality: User CPU time (User: <USERCPU> secs) System CPU time (Sys: <SYSCPU> secs)	5.11.3
The following items has been added as the events triggering the output of the event log of the Explicit Memory Management functionality, and a description has been added for the content that is output: Error in opening the configuration file of the functionality for specifying the classes to be excluded from the Explicit Memory Management functionality Error in the configuration file path of the functionality for specifying the classes to be excluded from the Explicit Memory Management functionality	5.11.1, 5.11.3
The following functionality have been added in the user-extended trace based performance analysis: The trace target specification method can now be specified for packages or classes in addition to the usual trace target specification method for methods. The range of available event IDs is expanded. The restrictions on the number of lines that can be specified in the user-extended trace based performance analysis configuration file are relaxed. The trace collection level can now be specified in the user-extended trace based performance analysis configuration file.	7.5.2, 7.5.3, 7.8, 8.28.1
The trace collection points of the EADs session failover functionality have been added to the trace collection points of the Web container that can be obtained with the trace based performance analysis.	8.9
The trace collection points when JavaMail is sent have been changed and added as follows: The point immediately before the start of the issuing of the \r\n. command has been changed to the point immediately before the start of the issuing of the notification for the end of mail text transmission. The point immediately after the starting of the issue of the STARTTLS command has been added.	8.24.1
The following points have been added to the trace collection points when JavaMail is received: Immediately before the issuing of the CAPA command is started Immediately after a response is received from the CAPA command	8.24.2
The reference relationship output functionality based on the static field has been added to the extended thread dump containing the class-wise statistical information.	9.6
A description has been added for the migration from DABroker Library to a database connection using Oracle JDBC Thin Driver.	11.4
The following files and directories have been added as the targets for snapshot log collection. Note that the text in the parentheses indicates the related targets and classification. Configuration file for the CTM regulators (Component Transaction Monitor) Configuration file for the OTM gateway (Component Transaction Monitor) Directory to output the temporary PRF trace file (Component Container/Manager) Explicit Memory Management functionality exclusion configuration file (Developer's Kit for Java) Explicit Memory Management functionality non-exclusion configuration file (Developer's Kit for Java) Directory to output the EADs client log for the EADs session failover functionality EADs client message log for the EADs session failover functionality (Component Container) EADs client communication trace for the EADs session failover functionality (Component Container) EADs client maintenance log for the EADs session failover functionality (Component Container) EADs client message dump for the EADs session failover functionality (Component Container) Catalog files (Component Container/JAX-WS functionality of this product) Operation log of the cjenvsetup command^# (Component Container/Change CC Administrator command) File configuration information before the cjenvsetup command is executed^# (Component Container/Change CC Administrator command) File configuration information after the cjenvsetup command is executed^# (Component Container/Change CC Administrator command) FTP adapter maintenance log (HCSC server/ FTP adapter) #: Only in UNIX.	Appendix A.1, Appendix A.2, Appendix A.3, Appendix A.5, Appendix A.16
The information for the following files and directories for which the snapshot log was collected has been deleted. Note that the text in the parentheses indicates the related targets and classification. All the Service Coordinator information (Component Container/Service Coordinator) Redirector action definition file for IIS^# (Component Container/Redirector (Web server)) Mapping definition file^# (Component Container/Redirector (Web server)) #: Only in UNIX.	Appendix A.2
The information for the following files and directories for which the snapshot log was collected has been changed. Note that the text in the parentheses indicates the related targets and classification. Process-wise action definition file (Component Container/JAX-WS functionality of this product) web.xml (Component Container/ JAX-WS functionality of this product) cosminexus-jaxws.xml (Component Container/JAX-WS functionality of this product) Handler chain configuration file (Component Container/JAX-WS functionality of this product) WSDL (Component Container/JAX-WS functionality of this product) All the trace (HCSC server/file adapter) FTP adapter protocol trace (HCSC server/FTP adapter) Message log of the operating commands of the FTP adapter (HCSC server/FTP adapter)	Appendix A.2, Appendix A.13, Appendix A.16
Collection targets have been added for the snapshot log related to the information on the following HCSC servers: HCSC server HCSC server (FTP receiving) HCSC server (File operation adapter) HCSC server (FTP inbound adapter) HCSC server (Mail adapter) HCSC server (HTTP adapter)	Appendix A.10, Appendix A.11, Appendix A.17, Appendix A.18, Appendix A.19, Appendix A.20
The description of notes has been moved from Release Notes.	2.3, 2.3.2, 2.6.4, 3.3.5, 3.3.13, 3.3.17, 3.3.18, 4.3.1, 4.4.1, 4.7, 4.9.1, 4.9.4, 5.1, 5.2.5, 5.5, 7.3.3, 7.5.1, 8.23.4, 9.15, 10.3, 10.4.1, 10.4.2, 10.4.3, 10.4.5, 10.6, 10.9, 10.9.2

In addition to the above changes, minor editorial corrections have been made.