Installing CA Enterprise Log Manager - CA Technologies

Initial CA Enterprise Log Manager Server ConfigurationsPort Component Description17002 ODBC/JDBC Default TCP port used for communications between ODBC orJDBC driver and the CA Enterprise Log Manager event logstore.17003 Agent TCP port used for communications by the Qpid message bus forr12.1 agents.57000 Dispatcher SMEListener57001 Dispatcher EventListenerTCP port used for the Dispatcher service on the agent localhostto listen for self monitoring events between agent processes.TCP port used for the Dispatcher service is SSL enabled (usingETPKI) to listen for events from client connectors.random SAPI UDP ports used for event collection assigned by the portmapper; you can also configure the SAPI router and collector touse any fixed port value above 1024.List of Related ProcessesThe following table represents a list of the processes that run as part of a CAEnterprise Log Manager implementation. The list does not include systemprocesses related to the underlying operating system.Process Name Default Port Descriptioncaelmagent 6789, 17001 This is the CA Enterprise Log Manager agentprocess.caelmconnectorcaelmdispatcherDependent uponwhat it listens for, orto what it connects.This is the CA Enterprise Log Manager connectorprocess. There will be a separate connectorprocess running for each connector that isconfigured on an agent.This CA Enterprise Log Manager processhandles event submission and statusinformation between the connector and agent.caelmwatchdog None CA Enterprise Log Manager watchdog processthat monitors other processes to ensurecontinuity of operations.caelm-eemsessionsponsorCA EEM main process that manages allcommunications to CA EEM for local sponsorsrunning under safetynet on the CA EnterpriseLog Manager server.This process may run under safetynet.caelm-logdepot 17001 The CA Enterprise Log Manager event log storeprocess that handles event storage, archive fileChapter 3: Installing CA Enterprise Log Manager 79