I.1 Estimating the required number of file descriptors

Organization of this subsection

(1) Formula for calculating the number of file descriptors
(2) Values used in the formula for calculating the number of file descriptors

(1) Formula for calculating the number of file descriptors

Use the following formula to estimate the maximum number of file descriptors that will be used in a system that uses the HCSC server:

Maximum number of file descriptors = (A + A' + B + C) × 1.25

The following explains the variables in the preceding formula:

A: Number of file descriptors used on the HCSC server (J2EE server)

Calculate A by using the following formula:: Number of file descriptors on the J2EE server^# + 39
#: To estimate the number of file descriptors used on the J2EE server, use the formula in (2) Number of file descriptors in 5.2.1 Estimating the resources used by J2EE server in the Application Server System Design Guide. Hereinafter, this formula is referred to as the J2EE Server's Formula. Note that the calculation using this formula requires the information shown in the following section: The Values used in J2EE Server's Formula in the formula for variable A column of the table in (2) Values used in the formula for calculating the number of file descriptors.

A': (Number of file descriptors that are used for each of the specified settings of the HCSC server (J2EE server))

A' is calculated from the following formula:

a + b + c

The details of the a, b, and c variables are as follows:

a: Number of types of log data output on the HCSC server (message trace, request trace, and activity trace) x 2

b: Number of JAR files used when custom functions are used

c: Number of CSV files used when the change value function

B: (Number of file descriptors that each HCSC component uses for only startup)

To obtain the value to be assigned to B, first, see the table in (2) Values used in the formula for calculating the number of file descriptors. In this table, you can see calculation formulas in the Formula for variable B column. The total of the results of the formulas for the relevant HCSC components is the value to be assigned to B.

The value of B is equal to the total of I and L in the J2EE Server's Formula. Use this value when estimating the number of file descriptors that will be used on the J2EE server or the HCSC server.

C: (Number of file descriptors that each HCSC component uses for requesting)

To obtain the value to be assigned to C, first, see the table in (2) Values used in the formula for calculating the number of file descriptors. In this table, you can see calculation formulas in the Formula for variable C column. The total of the results of the formulas for the relevant HCSC components is the value to be assigned to C.

To Page Top

(2) Values used in the formula for calculating the number of file descriptors

The value of each variable in the calculation formula in (1) varies depending on the HCSC components to be used. The following table provides the information required to determine the value of each variable in the formula.

Table I‒1: Number of file descriptors used by each HCSC component
HCSC component		Values used in J2EE Server's Formula in the formula for variable A	Formula for variable B	Formula for variable C
Business process		--	4 + (3 x number of business processes)	If the service emulation function is not used: 0 If the service emulation function is used: Total maximum number of emulation-target service adapters that can concurrently run x 3
Standard reception	SOAP	`C` in the J2EE Server's Formula: Assign the total of the values specified for the following properties in the HCSC server runtime definition file: `request-soap.instance.maximum` property `request-soap1_2.instance.maximum` property	3	0
Standard reception	EJB	`B` in the J2EE Server's Formula: Assign the value specified for the `request-ejb.instance.maximum` property in the HCSC server runtime definition file.	1	0
User-defined reception	SOAP reception	`C` in the J2EE Server's Formula: Assign the value specified for the `user-defined-reception-soap.threads.maximum` property in the user-defined reception runtime definition file.	1 x number of receptions	Total of the results of the following calculation for all receptions: Number of attached files x maximum number of concurrent threads Maximum number of concurrent threads: Value specified for the `user-defined-reception-soap.threads.maximum` property in the user-defined reception runtime definition file
	TP1/RPC reception	`H` in the J2EE Server's Formula: For `total-of-values-specified-in-<pooled-instance><maximum>-of-each-MDB-(services)-Message-driven-Bean-attribute-file` in the formula, assign the total of the values specified for the `urecp-tp1rpc.pooled-instance.maximum` properties in the TP1/RPC reception definition file.	6 x number of receptions	0
	FTP reception	--	3 x number of receptions	Total of the values specified for the `urecp-ftp.pooled-instance.maximum` properties for all receptions in the FTP reception definition file
	HTTP reception	`C` in the J2EE Server's Formula: Assign the value specified for the `urecp-http.pooled-instance.maximum` property in the HTTP reception definition file	4 x number of receptions	Total of the values resulting from the following calculation for all receptions: (Number of receive files + number of send files) x maximum number of instances Maximum number of instances: Value specified for the `urecp-http.pooled-instance.maximum` property in the HTTP reception definition file
	Message Queue reception	--	4 x number of receptions	0 If calculation of the number of file descriptors for the MQ resource adapter requires the number of pool instances of each service, assign the value specified for the `pooled-instance.maximum` property in the Message Queue reception definition file.
	File event reception	--	8 x number of receptions	Total of the values resulting from the following calculation for all receptions: For monitoring the update completion notification file: 2 (= update completion notification file + lock control) x maximum number of threads For monitoring the files to be obtained: 2 (= file to be obtained + lock control) x maximum number of threads Maximum number of threads: Value specified for the `urecp-fileevent.thread-pool.maximum` property in the file-event-reception definition file
	Custom reception (excluding user-defined ones)	--	2 x number of receptions	0
Service adapter	SOAP adapter	--	3 x number of adapters	Total of the values resulting from the following calculation for all adapters: (Number of attached files + 1) x maximum number of instances for each adapter
	Session Bean adapter	--	4 x number of adapters	Total of the maximum number of instances for each adapter
	DB adapter	--	6 x number of adapters	0
	TP1 adapter	--	10 x number of adapters + value specified for `<con_pool_num>` in the TP1 adapter communication-configuration definition file x 2	Total of the maximum number of instances for all adapters
	File adapter	--	6 x number of adapters	Total of the maximum number of instances for all adapters
	Message Queue adapter	--	10 x number of adapters	The smallest of the following values: Total of the maximum number of instances for all adapters Value specified for the `//hitachi-connector-property/resourceadapter/property[./property-name='` `MaxTPoolSize']` `../property-value` property in the HITACHI Application Integrated Property File for the MQ resource adapter Value specified for the `//hitachi-connector-property/resourceadapter/config-property[./config-property-name='maxConnections']` `../config-property-value` property in the HITACHI Application Integrated Property File for the MQ resource adapter
	FTP adapter	--	13 x number of adapters	3 x total of the maximum number of instances for all adapters
	File operations adapter	--	8 x number of adapters	2 x total of the maximum number of instances for all adapters
	Mail adapter	--	10 x number of adapters	If the attached files and the text files to be inserted into the body are used: (Number of attached files + number of text files) x total of the maximum number of instances for all adapters In the other cases: 0
	HTTP adapter	--	If OAuth 2.0 is not used: 9 x number of adapters If OAuth 2.0 is used: 10 x number of adapters	Total of the results of the following calculation for all adapters: (Number of sent attached files + number of received attached files + 1) x maximum number of instances for each adapter If OAuth 2.0 is used, also add the number of private key files to this total value.
	Command adapter (excluding user-defined ones)	--	13 x number of adapters	0
	SFTP adapter	--	If either password authentication or public key authentication is set 12 x number of adapters If both password authentication and public key authentication are set 13 x number of adapters	If host authentication is performed 3 x total of the maximum number of instances for all adapters If public key authentication is performed 2 x total of the maximum number of instances for all adapters + number of private key files
	Custom adapter (excluding user-defined ones)	--	2 x number of adapters	0
Resource adapter	FTP inbound adapter	--	26	2 x maximum number of concurrent connections Maximum number of concurrent connections: Value specified for `server_maxLogins` in the attribute file for the FTP inbound adapter
Resource adapter	TP1 inbound adapter	Use `H` in the J2EE Server's Formula for estimation.

Legend:: --: Not applicable

To Page Top