This subsection describes the TCP/UDP port used in a system for executing batch applications for each process. The following table describes the TCP/UDP port used in a system for executing batch applications:

Table 4-1 TCP/UDP port used in a system for executing batch applications

No.#1	Process	Explanation
(1)	Batch server	Request-receiving port of the EJB container.
(2)		Communication port for management.
(3)		Port for receiving requests from the Web server (redirector).
(5)		Request-receiving port of the Naming Service invoked with in-process.
(7)		Request receiving port of the RMI registry.
(9)		Port for receiving requests when acquiring the operation information.
(13)	Smart Agent#2	Port environment variable for Smart Agent communication. Smart Agent is required for the two-way communication through UDP.
(25)	CTM regulator#2	Fiducial value of the port where the CTM regulator receives requests from the EJB client. Only fiducial value + number of processes are used. Required when CTM is used.
(26)	CTM daemon#2	Port where CTM daemon receives requests from the EJB client. Required when CTM is used.
(27)		Port for communicating CTM daemons with other daemons and J2EE servers. Required when CTM is used.
(28)	CTM domain manager#2	Port for communicating the CTM domain manager with other CTM domain managers. Required for TCP and UDP communication (broadcast) when CTM is used.

Note

When you are instructed to use Smart Agent, some ports other than those described in the above table are used to communicate with the Smart Agent. For details on the Smart Agent, see the manual Borland(R) Enterprise Server VisiBroker(R) Programmers Reference.

#1

Corresponds to the numbers in Table 3-4 TCP/UDP port number used by Application Server of 3.16 TCP/UDP port numbers used by Application Server processes.

#2

This process is required for using the scheduling functionality of batch applications.

In the following cases, make sure that the used ports are not duplicated:

• When concurrently using the J2EE server and batch server on the same machine
• When concurrently using multiple batch servers on the same machine

For details about the TCP/UDP ports used in each process, see 3.16 TCP/UDP port numbers used by Application Server process.

Note

Notes on the standby port for a server (In UNIX)

In UNIX, when all the following conditions are satisfied, a connection might be successfully established with the TCP port that is not in a standby mode:

• An attempt is made to establish a connection with a port that is not in a standby status
• The host itself is the connection target, and the port is in the range of the temporary port numbers (range of port numbers that are dynamically allocated by the OS)

When this event occurs, the assumed process communication cannot be executed and a timeout occurs. To avoid this event, specify a value outside the range of the temporary port numbers as the standby port of the server. You can check the range of the temporary port numbers in the following files:

In AIX

Minimum value (32768): no -o tcp_ephemeral_low

Maximum value (65535): no -o tcp_ephemeral_high

In Linux

/proc/sys/net/ipv4/ip_local_port_range

For details on how to set up the standby port of a server, see the documentation for the OSs.