2.3.1 Process configuration
The following figure shows the processes that configure Application Server for executing J2EE applications:
|
|
![[Figure]](GRAPHICS/ZU020100.GIF)
- Reference note
-
Note that for building a system, match these processes with the requirements of the system, and then deploy one or multiple processes on each machine within the system.
Each process is described as follows. The numbers in the figure correspond to (1) to (6) in the following description:
- Organization of this subsection
(1) J2EE server
A J2EE server is a process that serves as a J2EE application execution platform. The multiple program modules such as J2EE applications, J2EE containers, J2EE services, and J2EE resources configure the J2EE server. Also, the J2EE containers are divided into EJB containers and Web containers according to the provided functionality. The details about the program modules configuring the J2EE server are described in 2.3.2 Configuration of a J2EE server.
(2) Web server
A Web server is a process that executes the processing related to receiving requests from the Web browser and sending data to the Web browser. You must use the Web server for systems that access the J2EE application running on a J2EE server from the Web browser#. You can also access servlets, JSPs, or static contents included in the J2EE application from the Web browser.
In Application Server, you can use Cosminexus HTTP Server or Microsoft IIS as a Web server. Cosminexus HTTP Server is one of the component software of Application Server. For details about the functionality of Cosminexus HTTP Server, see the uCosminexus Application Server HTTP Server User Guide.
- #
-
If you send and receive requests directly between the NIO HTTP server of the J2EE server and the Web browser without going through a Web server, you do not need to implement the Web server process. For details, see the manual uCosminexus Application Server Web Container Functionality Guide.
(3) CTM
A CTM is a group of processes used for scheduling the requests for Session Bean within the J2EE application. On using CTM, the requests from the client can be distributed and scheduled appropriately. As a result, you can control the load on the server, increase the system availability, and promote the business without delay.
You use multiple processes such as CTM daemons, CTM regulators, and CTM domain managers to implement the CTM functionality. Also, use the CORBA Naming Service as a Naming Service for implementing functions.
For details on the CTM functionality, see 3. Scheduling and Load Balancing of Requests Using CTM in the uCosminexus Application Server Expansion Guide.
- Tip
-
You can use CTM only with the products that contain Cosminexus Component Transaction Monitor in the component software. For details on the available products, see 2.2 Component software in the manual uCosminexus Application Server Overview.
(4) PRF daemon (Performance tracer)
Application Server outputs trace information to a buffer when processing a request. You can also expand the trace target so that applications in addition to Application Server also output trace information to a buffer. A PRF daemon (performance tracer) is an I/O process that outputs the trace information (output to the buffer) to a file.
The trace information file output by the PRF daemon is useful for verifying bottlenecks of the system and determining troubleshoot efficiency.
For details about the PRF daemon functionality, see 7. Performance Analysis by Using Trace Based Performance Analysis in the uCosminexus Application Server Maintenance and Migration Guide.
(5) Administration Agent
Administration Agent is an agent function that starts the logical server on each host and updates the setup file, instead of an administrator. Note that the logical server is a server or a cluster that is managed by Management Server.
(6) Management Server
Management Server is a process that issues instructions to Administration Agent deployed on each host of the management domain and executes operation management of the entire management domain.
(7) Other processes
In addition to the above (1) to (6) processes, the following processes are used depending on their functionality:
-
A user server is any service or process defined by user. The user server can be defined as the logical server (logical user server), and thereby specific services and processes can be managed by Management Server. As a result, you can manage the services and processes in a batch in the Management Server in the same way as with the other logical servers.