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

In Application Server systems, the system configuration is determined on the basis of the types of processes to be used and their deployment.

A Web front-end system and a back-end system configure Application Server systems. The Web front-end system uses a Web browser as the client. The back-end system uses an EJB client as the client. For details about the system classification, see 3.1.1 Purpose and configuration of the system.

The following subsection first explains the processes and software that would be required based on the classification of the system. Next, it describes the processes, modules, and software that would be required depending on the functions to be used. For details about how to deploy the processes, modules, and software on the system, see 3. Determining the System Configuration (J2EE Application Execution Platform).

Organization of this subsection
(1) Processes required depending on the system classification
(2) Processes and modules required depending on the functions to be used

(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 are using in-process HTTP servers, Web server processing is not required.
Hint
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 integrated with a redirector (Web server integration)
    Integrate with Application Server or a Web server containing a redirector module to process requests. The requests that the Web server receives are sent to the J2EE server through the redirector module.
    You can use Cosminexus HTTP Server or Microsoft IIS.
  • In-process 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.
Hitachi recommends that you use the Web servers integrated with redirector on Application Server. In default settings, the Web server integrated with the redirector is also used. For building systems that emphasize on performance, you specifically determine the usage of in-process HTTP servers.
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 ComparisonWeb server integrated with a redirectorIn-process HTTP server
Functionality available as a Web serverGood
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 operationGood
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 JPEGGood
You can enable optimal performance by deploying the static contents on the Web server.
If you deploy the static contents on the Web container, the access is through the redirector, so the access process takes time.
Good
You can ensure optimal performance because you can access without passing through the redirector.
Access performance for dynamic contents such as servlets and JSPsBasic
The access process through the redirector takes time.
Good
You can ensure optimal performance because you can access without passing through the redirector.
NotesIf 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.
Furthermore, if you do not deploy a reverse proxy, you can get the same advantage by deploying a Web server with an embedded redirector on 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 that you can use with in-process HTTP server, see 5.2.2 Functions that can be used with the in-process HTTP server in the uCosminexus Application Server Web Container Functionality Guide.
#2
For the deployment of a Web server on DMZ, see 3.3 Determining the deployment of reverse proxy on 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.

(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)

FunctionsNecessary processes
Use CTM in the integration between the servers/Distribute the load using CTMCTM daemon
CTM regulator
CTM domain manager
Global CORBA Naming Service
Smart Agent
Management using the Management ServerManagement Server
Administration Agent
Improving availability using the memory session failover functionalitySFO server
Invoking the CORBA Naming Service in the out-processCORBA 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

FunctionsModulesProvided byRemarks
Connecting to the database
(HiRDB)
HiRDB Run Time
  • HiRDB Run Time
This module is required for using the Cosminexus DABroker Library as a JDBC driver.
HiRDB Type4 JDBC Driver
  • 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
  • HiRDB/Parallel Server Version 8
  • HiRDB/Single Server Version 8
  • HiRDB Run Time Version 8
  • HiRDB/Developer's Kit Version 8
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/Parallel Server Version 8
  • HiRDB/Single Server Version 8
  • HiRDB Run Time Version 8
  • HiRDB/Developer's Kit Version 8
This module is required for using the HiRDB Type4 JDBC Driver as a JDBC driver.
Connecting to the EADs serverEJB client
  • uCosminexus Elastic Application Data store Client for Java 02-00
--
Connecting to the Message Queue serverTP1/Message Queue - Access
  • TP1/Message Queue - Access
--
Connecting to the SPP of OpenTP1uCosminexus TP1 Connector
  • uCosminexus TP1 Connector
--
TP1/Client/J
  • TP1/Client/J
--
Legend:
--: Not applicable.
Note:
The modules are included in the J2EE server processes for the operation.

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

FunctionNecessary processesSoftware to be provided
Switch the node using cluster software when an error occursWindows Server Failover ClusterWindows Server Failover Cluster
HA monitorHA monitor