8.3.4 Communicating within a local host
JP1/IM and JP1/Base use ports to communicate even when the communication takes place within a local host (between the processes on that host).
The following table lists the ports used for communication within a local host.
|
Service |
Port number |
Description |
|---|---|---|
|
jp1imevtapi |
20099/tcp |
Used to acquire JP1 events from JP1/Base and to register JP1 events in JP1/Base. |
|
jp1imevtcon |
20115/tcp |
Used by JP1/IM - Manager internal processing. |
|
jp1imfcs |
20701/tcp |
Used by JP1/IM - Manager internal processing. |
|
jp1imcmda |
20238/tcp |
Used to execute automated actions. |
|
jp1imegs |
20383/tcp |
Used by JP1/IM - Manager (event generation service) internal processing. |
|
jp1imcss |
20305/tcp |
Used by JP1/IM - Manager (Central Scope service) internal processing. |
|
JP1/IM-Manager DB Server |
20700/tcp# |
Used by JP1/IM - Manager (IM database) internal processing. |
|
jp1imcf |
20702/tcp |
Used by JP1/IM - Manager (IM Configuration Management service) internal processing. |
|
jddmain |
20703/tcp |
Used by JP1/IM - Manager (Intelligent Integrated Management Base) internal processing. |
- #
-
You do not have to write the port number for the JP1/IM2-Manager DB Server in the services file. The port number increases with each logical host configured in the system. The port number for the IM database is set in the setup information file. For details, see Setup information file (jimdbsetupinfo.conf) in Chapter 2. Definition Files and Cluster setup information file (jimdbclustersetupinfo.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.