What are the network ports involved with CA Software Change Manager?
Article ID: 54501
Updated On:
Products
Issue/Introduction
Description:
CA Software Change Manager uses a proprietary communication mechanism, Enterprise Communicator (also referred to as PEC), for its internal communication.
Solution:
CA Software Change Manager uses a proprietary communication mechanism, Enterprise Communicator (also referred to as PEC), for its internal communication. This usually is done via TCP/IP protocol. TCP port 5101 is the default port that CA Software Change Manager uses for this communication.
CA Software Change Manager also requires additional TCP ports for operations like Checkout, Checkin, browsing Agent's file system etc. These additional ports are requested from the operating system. By default, such ports are ephemeral ports and so the operating system allocates a random un-assigned port to the CA Software Change Manager component requesting the port.
It is difficult to let network firewalls allow connectivity over such random (ephemeral) ports. So, flexibility is available for you configure a range of ports that CA Software Change Manager can use. Specific information about this is available in the CA Software Change Manager Administrator Guide -> Chapter 3 -> How the CA Software Change Manager communication works.
CA Software Change Manager also requires additional TCP ports for operations like Checkout, Checkin, browsing Agent's file system etc. The default direction of communication between various CA Software Change Manager components is:
HAgent -> HServer
HClient -> HServer
HClient -> HAgent
(Note: the component on the left initiates connection to the component on the right).
The direction of communication indicated above can be changed using a configurable option in the ARG file of the respective components. Specific options are documented in this section: CA Software Change Manager Administrator Guide -> Chapter 2 -> Connection method options for direct connection.
Environment
Component:
Feedback
