4.8.2 Notes on setting Easy Setup definition file (when using other functionality)

This subsection describes the notes on setting a system for using the following functions of Application Server in Easy Setup definition file by using the Smart Composer functionality.

Scheduling functionality using CTM
NIO HTTP server functionality (when not using Web server integration)

Organization of this subsection

(1) When using CTM based Scheduling functionality in the system for executing J2EE applications
(2) When using NIO HTTP server functionality (when not using Web server integration)
(3) Notes common for each functionality

(1) When using CTM based Scheduling functionality in the system for executing J2EE applications

If the system uses CTM, you must define a client that sends requests to CTM. Besides Web front system that is set up by using the Smart Composer functionality or the management portal, you can use EJB client, or a unique user-defined Web system, as a client.

You must define the integrated naming scheduler server and Application Server with the Easy Setup definition file when you use the integrated naming scheduler server (host to which the global CORBA Naming Service is allocated) to set up a system with the integrated naming scheduler server model. Define the integrated naming scheduler server and Application Server respectively on different Web systems. Also, if you want to use a Web front system set up by using the Smart Composer functionality, as a system for sending the requests to CTM; you must define a Web system different from the Web system used in the scheduling functionality.

You must define the following items in Easy Setup definition file for each Web system.

(a) Web system for Application Server (CTM)

This Web system defines Application Server.

Defining the properties of the Web system

Define Web system for setting up Application Server.
Defining the load balancer

You cannot define the load balancer. If you define the load balancer, an error occurs.
Defining the physical tiers

Define ctm-tier as the type of the physical tier.

You can allocate multiple servers with Application Server. For allocating multiple J2EE servers, set the number of J2EE servers to be allocated to a single host in the definition of the physical tier. Note that you cannot change the number of J2EE servers to be allocated to a single host while changing the configuration of the Web system.

Besides setting the configuration of CTM domain manager, CTM, Smart Agent, and the Performance Tracer, you can also set a configuration common to all the J2EE servers in ctm-tier. When you allocate multiple servers, you can specify common configuration for J2EE servers having the same number (server-no tag).

If there are multiple applicable configuration definitions for each J2EE server, and you set the same parameters in each definition, the definitions are applied in the following priority order
1. Service unit definition (defining a specific J2EE server)
2. Physical tier definition (common definition for J2EE servers having the same number)
3. Physical tier definition (common definition for all the J2EE servers)
Set the same value as that of the integrated naming scheduler server for the following parameters to define the relationship with the integrated naming scheduler server.
- CTM domain name (ctmdomname of the logical CTM Domain Manager) to which CTM Domain Manager belongs
- Port number to be used in CTM domain manager (cdm.port of the logical CTM Domain Manager)
- Port number to be used in Smart Agent (smartagent.port of the logical Smart Agent)
Defining a service unit

Define a service unit for allocating the processes related to CTM, and the J2EE server.

Besides setting the configuration of CTM domain manager, CTM, Smart Agent, and Performance Tracer, you can set the configuration of a specific J2EE server for each service unit. When allocating multiple J2EE servers, specify J2EE servers within a service unit by using a number (server-no tag).

You must set a unique value for CTM identifiers (ctmid) to identify CTM within a management domain. You can opt not to set a CTM identifier (ctmid).
Defining a host

Define Application Server for allocating the processes related to CTM, and the J2EE server.

(b) Web system for integrated naming scheduler server

This Web system is required when you set up a system with the integrated naming scheduler server model. This Web system defines the integrated naming scheduler server (computer to which the global CORBA Naming Service is allocated).

Defining the properties of Web system

Define the Web system for setting up the integrated naming scheduler server.
Defining the load balancer

You cannot define the load balancer. If you define the load balancer, an error occurs.
Defining the physical tiers

Define ctm-tier as the type of the physical tier.

Set the number of J2EE servers to 0 in the ctm-tier, because no J2EE server is allocated in an integrated naming scheduler server.

You can configure CTM domain manager, CTM, Smart Agent, and Performance Tracer with ctm-tier.
Defining a service unit

Define a service unit for allocating the processes related to CTM.
Defining a host

Define the integrated naming scheduler server.

To Page Top

(2) When using NIO HTTP server functionality (when not using Web server integration)

You must define the following items in Easy Setup definition file. Note that you cannot use the load balancer in the j2ee-tier. Therefore, delete the load balancer definition. If you want to use the load balancer, use the management portal to set up the system.

Defining the physical tiers

Define j2ee-tier as the type of the physical tier. Also define the setting that enables the NIO HTTP server functionality in j2ee-tier.
Defining a service unit

Define a service unit in which to deploy the J2EE server. Define the port number to be used by the NIO HTTP server.

To Page Top

(3) Notes common for each functionality

You can allocate multiple service units to a single host when using any of the functionalities. You however cannot allocate multiple service units of the same CTM domain to the same host. Following are the notes on allocating multiple service units to a single host:

(a) Notes on logical server settings

If you allocate multiple service units to a single host, multiple logical servers of the same type exist within the same host. Therefore, while creating Easy Setup definition file, do not specify a duplicate value for the following items in the configuration of each logical server.

Table 4‒41: Items to be set without duplicating the values for each logical server
Logical server type	Item	param-name specification value
Web server	http port number	`Listen`
J2EE server	Port number of NIO HTTP server	`webserver.connector.nio_http.port`^#1
	Port number of ajp13	`webserver.connector.ajp13.port`^#2
	Port number of in-process naming service	`inprocess.ns.port`
	Port number of in-process HTTP server	`webserver.connector.inprocess_http.port`^#2
	Fixed port number of JTA recovery	`ejbserver.distributedtx.recovery.port`
	Port number of RMI registry	`ejbserver.rmi.naming.port`
	Port number of the management server	`ejbserver.http.port`
	Request-reception port number when acquiring operation information	`ejbserver.rmi.remote.listener.port`
Performance Tracer	PRF identifier	`PRFID`
Smart agent	Port number monitored by the smart agent	`smartagent.port`
CTM domain manager	CTM domain name to which the CTM domain manager belongs	`ctmdomname`
	CTM execution environment directory	`ctmspool`
	Port number used by CTM domain manager to exchange CTM domain configuration information	`cdm.port`
CTM	CTM identifier	`ctmid`^#3
	Port number used by CTM	`ctm.port`
	Port number of the naming service corresponding to CTM	`ctm.ns.port`

#1: This item is used in recommended mode. If recommended mode is not used, this item is ignored on the Management Server.
#2: This item is used in V9 compatibility mode. If V9 compatibility mode is not used, this item is ignored on the Management Server.
#3: You can opt not to set ctmid. If you do not set ctmid, Management Server automatically sets a value that is unique across the hosts.

Reference note: You can set the same value to the same type of the logical server in each service unit, when you do not want to concurrently run multiple service units on a single host.

The definition configuration of setting items differs depending on the Web system to which the service unit allocated to the host belongs.

When allocating service units of the same Web system to the same host:

Specify in the configuration tag within the logical server definition (define-server tag) of each service unit.
When allocating service units of different Web systems to the same host:

Specify in the configuration tag within the physical tier definition (tier tag) of each Web system.

(b) Notes on the port numbers of Web server

When you allocate multiple service units to a service machine, there are following limitations for changing the port numbers of the Web server. Note that these limitations are equally applicable when multiple service units exist on the same Web system or on different Web systems.

When same port number is set for Web servers of multiple service units

You can set the same port number for Web servers of each service unit, when you do not want to concurrently run multiple service units on a single server machine.

Use any of the following procedures to do the changes:
- Concurrently change the port numbers of Web servers of all the service units.
- Change the port numbers of the Web servers of some service units first, and then of other service units.
  
  Important note
  
  If you change the port numbers of Web servers of some service units, the port numbers of other service units get deleted, and you can no more use those Web servers. Be sure to change the port numbers of Web servers of other service units later.

When different port numbers are set for the Web servers of multiple service units

In the following example, the port number of the Web server of service unit 1 (unit1) is 80, while that of service unit 2 (unit2) is 81. The following table describes how to change the settings of a port number and also the possibility of doing the changes:

Table 4‒42: How to change a port number, and the possibility of doing the changes
Method to change the port number	Settings to be done in the Configuration Change definition file used for changing the parameters of the logical server	Changed port number of the Web server		Change possibility (Y/N)
Method to change the port number		unit1	unit2	Change possibility (Y/N)
Changing the port number of the Web server of each service unit to the same number	Set port number `81` in the Web server of service unit 1.	`81`	`81`	Y
	Set port number `80` in the Web server of service unit 2.	`80`	`80`	Y
Replacing the port number of the Web server of each service unit	Set port number `81` in the Web server of service unit 1 and `80` in the Web server of service unit 2.	`81`	`80`	N
Changing the port number of the Web server of one service unit to the port number of the other service unit, and changing the Web server of the other service unit to the unused port number (example: 82)	Set port number `81` in the Web server of service unit 1 and `82` in the Web server of service unit 2.	`81`	`82`	N
	Set port number `82` in the Web server of service unit 1 and `80` in the Web server of service unit 2.	`82`	`80`	N
Change the port number of the Web server of a service unit to an unused port number (example: 82)	Set port number `82` in the Web server of service unit 1.	`82`	`81`	Y
	Set port number `82` in the Web server of service unit 2.	`80`	`82`	Y

Legend:

Y: Change is possible

N: Change is not possible

Reference note: You cannot change the preset port number with a single operation. You must execute a set of operations such as setting an unused port number once and then switching to the preset number, and changing the port number in multiple steps.

To Page Top