2.5.2 Determining the processes to be used and preparing the required software

(1) Processes required depending on the system classification

The processes required depending on the system classification are described as follows. These are processes that are required regardless of the functionality used. Application Server provides these processes.

Processes required for a Web front-end system

The processes required for a Web front-end system are as follows:

• Web server^#

• J2EE server

• PRF daemon

The Web server included in Application Server is Cosminexus HTTP Server. A Web browser is used for the client.

#

If you access the NIO HTTP server of the J2EE server directly without going through a Web server, you do not need to implement the Web server process.

Tip

Guidelines for selecting the Web server

In a Web client system, you can process requests from a Web client using any one of the following Web servers:

• Web server with reverse proxy function enabled

  The Web client system processes requests by linking with a Web server that incorporates a proxy module. The requests the Web server receives are sent to the NIO HTTP server of the J2EE server via the proxy module.

• NIO HTTP server

  Processing requests on the HTTP server that functions within the processes of the J2EE server provided as a part of Web container function. You can receive requests from Web clients directly on J2EE servers.

We recommend that you use a Web server with the reverse proxy function enabled on the Application Server. Under the default settings, the Application Server uses a Web server with the reverse proxy function enabled. If you want to build a system with a particular emphasis on performance, consider a configuration that accesses the NIO HTTP server directly.

The following table describes the characteristics of respective Web servers. Use this information as the guideline for selecting Web servers.

Table 2‒5: Guidelines for selecting the Web server

Points for Comparison	Web server with reverse proxy function enabled	NIO HTTP server
Functionality available as a Web server	Good You can use various functionality provided by Cosminexus HTTP Server (Web server based on Apache functionality) or Microsoft IIS.	Basic Only minimum functions are provided with an objective of accessing Web applications configured with servlets, JSPs, or HTML.#1
Simplified build and operation	Good Web server environment settings are necessary for building a system. You need to start and stop the Web server for operations. However, you can build or run the Web server using the commands of the Smart Composer functionality, and hence, the complex operations are not required.	Good Environment settings of Web servers for the setup, startup, and termination of the Web server for operations are not required.
Access performance for static contents such as HTML and JPEG	Good You can enable optimal performance by deploying the static contents on the Web server. Static contents deployed on a Web container are accessed via reverse proxy, and access processing will take longer.	Good You can ensure optimal performance because access takes place without going through a reverse proxy.
Access performance for dynamic contents such as servlets and JSPs	Basic Access processing takes longer because it goes through a reverse proxy.	Good You can ensure optimal performance because access takes place without going through a reverse proxy.
Notes	If you connect to the internet, from the security point of view, Hitachi recommends that you use a configuration securing DMZ and deploy a reverse proxy on the front-end. If you do not deploy a reverse proxy, you can achieve similar results by deploying a Web server that incorporates a reverse proxy in the DMZ#2.	While connecting to the Internet, select the configuration that ensures DMZ with the objective of security, and make sure to set up the deployment of reverse proxy at the front-end.#2

#1

For details about the functions you can use with the NIO HTTP server, see the manual uCosminexus Application Server Web Container Functionality Guide.

#2

For the deployment of a Web server on DMZ, see 3.3 Deployment of reverse proxies in a DMZ in the uCosminexus Application Server Security Management Guide.

Processes required for a back-end system

The processes required for a back-end system are as follows:

• J2EE server

• PRF daemon

The system uses an EJB client for the back-end system client. EJB client refers to Servlets, JSPs, other Enterprise Beans, EJB client applications, or other business systems that invoke the Enterprise Beans.

If you are using an EJB client application as an EJB client, you can build the client machine for Windows by using uCosminexus Client. You can invoke the PRF daemon as and when required, whether you use Application Server or uCosminexus Client software.

Reference note

For the system using CTM, you can use any client such as clients of TPBroker or TPBroker Object Transaction Monitor other than EJB client.

To Page Top

(2) Processes and modules required depending on the functions to be used

This subsection describes the processes and modules that are required depending on the functions to be used. Some of these processes and modules are provided by Application Server and some are provided by software other than Application Server.

Among the processes required for each function to be used, the following table describes the processes those are provided by Application Server. You can invoke these processes on the machine where Application Server is installed.

Table 2‒6: Processes and modules required for each function (provided by Application Server)

Functions	Necessary processes
Use CTM in the integration between the servers/Distribute the load using CTM	CTM daemon
	CTM regulator
	CTM domain manager
	Global CORBA Naming Service
	Smart Agent
Management using the Management Server	Management Server
	Administration Agent
Invoking the CORBA Naming Service in the out-process	CORBA Naming Service

Among the processes and modules required for each function to be used, Table 2-7 and Table 2-8 describe the processes and modules provided by products other than Application Server.

Table 2‒7: Modules required for each function (provided by the products other than Application Server) and software to be provided

Functions	Modules	Provided by	Remarks
Connecting to the database (HiRDB)	HiRDB Type4 JDBC Driver	HiRDB Server Version 10 HiRDB/Run Time Version 10 HiRDB/Developer's Kit Version 10 HiRDB Developer's Suite Version 10 HiRDB Server Version 9 HiRDB Server with Additional Function Version 9 HiRDB/Run Time Version 9 HiRDB/Developer's Kit Version 9 HiRDB Developer's Suite Version 9	This module is required for using the HiRDB Type4 JDBC Driver as a JDBC driver.
Connecting to the database (Oracle)	Oracle JDBC Thin Driver	Oracle JDBC Thin Driver	This module is required for using the Oracle JDBC Thin Driver as a JDBC driver.
Connecting to the database (SQL Server)	SQL Server JDBC Driver	SQL Server JDBC Driver	This module is required for using the SQL Server JDBC Driver as a JDBC driver.
Connecting to the database (XDM/RD E2)	HiRDB Type4 JDBC Driver	HiRDB Server Version 10 HiRDB/Run Time Version 10 HiRDB/Developer's Kit Version 10 HiRDB Developer's Suite Version 10	This module is required for using the HiRDB Type4 JDBC Driver as a JDBC driver.
Connecting to the Message Queue server	TP1/Message Queue - Access	TP1/Message Queue - Access	--
Connecting to the SPP of OpenTP1	uCosminexus TP1 Connector	uCosminexus TP1 Connector	--
	TP1/Client/J	TP1/Client/J	--

Table 2‒8: Processes required for each function (provided by products other than Application Server) and software to be provided

Function	Necessary processes	Software to be provided
Switch the node using cluster software when an error occurs	Windows Server Failover Cluster	Windows Server Failover Cluster
	HA monitor	HA monitor

To Page Top