3.2.1 Common points to be considered for the system configurations described in this chapter
Note the following common points for each system configuration:
-
This chapter describes the system configuration using Application Server. You can read the terminology used in this chapter for the products that you use, as and when required.
The products that you use and products used in this chapter are described in the following table:
Table 3‒2: Products to be used and products used in this chapter Products to be used
Products described in this chapter
uCosminexus Developer#
Application Server
uCosminexus Service Architect#
uCosminexus Service Platform
- #
-
You must read this as is when you use this product in a test environment.
-
Most of the examples of system configurations show the deployment of one Application Server for each role. However, in the case of actual configuration, Hitachi recommends that you implement a cluster configuration by using the load balancer for scalability and availability. This will help to avoid complete suspension of the service whenever problems occur and server maintenance is required. For details about the configuration where load balancing is implemented, see 3.7 Determining the load balancing method by the load-balancing cluster.
-
This chapter describes examples where Management Server is used for performing operations. When you perform an operation without using Management Server, the following processes are unnecessary so you need not read the description:
-
Management Server
-
Administration Agent
The machine that starts only those processes that are required for operation management is called the Management Server machine. Note that the management sever machine is only required when you use Management Server for performing operations.
-
-
This chapter mainly cites examples of configurations that involve Web server integration when the access point is either a servlet or JSP. Because the following process is unnecessary when accessing the NIO HTTP server of the J2EE server directly without going through a Web server, you can ignore mentions of this process:
-
Web server
-
-
The PRF daemon is a process that outputs a performance analysis trace file. Always deploy the PRF daemon on the Application Server and if required, also deploy the PRF daemon on the EJB client. For details about the deployment of a PRF daemon, see 3.12 Deploying a process for the output of the performance analysis trace file.