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).
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.
Table 2-5 Guidelines for selecting the Web server
Points for Comparison | Web server integrated with a redirector | In-process 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. 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 JSPs | Basic The access process through the redirector takes time. | Good You can ensure optimal performance because you can access without passing through the redirector. |
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. 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 |
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 | |
Improving availability using the memory session failover functionality | SFO server |
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 Run Time |
| This module is required for using the Cosminexus DABroker Library as a JDBC driver. |
HiRDB Type4 JDBC Driver |
| This module is required for using the HiRDB Type4 JDBC Driver as a JDBC driver. | |
Connecting to the database (Oracle) | 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 |
| 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 |
| This module is required for using the HiRDB Type4 JDBC Driver as a JDBC driver. |
Connecting to the EADs server | EJB client |
| -- |
Connecting to the Message Queue server | TP1/Message Queue - Access |
| -- |
Connecting to the SPP of OpenTP1 | uCosminexus TP1 Connector |
| -- |
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 |