uCosminexus Application Server provides a development and execution environment for applications that support Web services and that comply with the Java EE 6 standards (such as Servlet 3.0, EJB 3.1, and JAX-WS 2.2), the SOAP*1 and WSDL*2 specifications. This improves application-development productivity.
A Web application server environment can be set up by using an intuitive wizard. The user can set up an environment by simply selecting a configuration pattern and connection-target database, thus significantly reducing the initial system-installation cost. Oracle and Hitachi HiRDB are supported as connection-target databases.
When used with Job Management Partner 1/Automatic Job Management System 3 (a job management product), uCosminexus Application Server allows routine jobs such as starting and stopping of servers and applications to be scheduled for automatic execution.
Note: This function is supported only in Japanese editions.
When used with Job Management Partner 1/Integrated Management (an integrated management product), uCosminexus Application Server provides consolidated management of the operation status and events of servers and applications. If a failure is detected, the user can call the Cosminexus operation-management portal window from the Job Management Partner 1/Integrated Management monitoring window, and take corrective action with ease.
Resident Java VM processes provide a high-performance batch-application execution environment to support batch processing. When usedwith Job Management Partner 1/Automatic Job Management System 3 (a job management product), uCosminexus Application Server enables automatic job execution. A job scheduling function that controls the number of concurrently-running batch applications is also provided.
A unique ID is assigned to each request, and trace data is acquired at each processing point on the server. Requests can be traced by their IDs, allowing simplified performance tuning and log analysis in the case of failure. In addition, the database*3 connection ID is also output, allowing you to understand the flow of processing from the Web server to the database. Since a fast method that does not affect online performance is used, log data can be constantly output while the system is running.
You can also acquire trace data at processing points in an application and framework, without modifying the application or framework, by simply specifying a definition file. Therefore, identification of bottlenecks and locations of failures in applications and frameworks, which was difficult in previous versions, is now possible. You can set trace points by using the GUI while referencing the application source code.
Memory leaks—situations in which memory cannot be released—are difficult to investigate because they are hard to reproduce in a test environment. To determine why the memory was not released, check the ranking of classes by memory usage to identify the class that might have caused the memory leak, and then check the reference relationships of that class. In this way, if a memory leak occurs, you can determine the memory usage without restarting the server. This offers quick resolution for memory leak problems that are hard to reproduce in a test environment.
