B.1 JP1/IM processes (Windows)
The following shows the process names displayed in the Processes page of the Windows Task Manager.
- Organization of this subsection
(1) JP1/IM - Manager
The table below describes the JP1/IM - Manager processes. The numbers in parentheses are the number of processes that can be executed concurrently.
|
Parent process |
Functionality |
Child process |
Functionality |
|---|---|---|---|
|
jco_spmd.exe (1) |
JP1/IM - Manager process management |
jcamain.exe (1) |
Automatic Action Service (displayed process name: jcamain) |
|
evtcon.exe (1) |
Event console service (displayed process name: evtcon) |
||
|
evflow.exe (1) |
Event base service (displayed process name: evflow) |
||
|
jcsmain.exe (1) |
Central Scope service#1 (displayed process name: jcsmain) |
||
|
evgen.exe (2)#2 |
Correlation event generation service#3 (displayed process name: evgen) |
||
|
jcfmain.exe(1) |
IM Configuration Management service#4 (displayed process name: jcfmain) |
||
|
jddmain.exe(1) |
Intelligent Integrated Management Base service#5 (displayed process name: jddmain) |
||
|
imbase.exe(1) |
Servicing JP1/IM agent management base (imbase)#5 (displayed process name: imbase) |
||
|
imbaseproxy.exe(1) |
Servicing JP1/IM agent management base (imbaseproxy)#5 (displayed process name: imbaseproxy) |
||
|
jco_service.exe(1) |
Windows service control in JP1/IM - Manager |
-- |
-- |
|
jcfmain.exe(1) |
IM Configuration Management in JP1/IM - Manager |
-- |
IM Configuration Management service |
|
jcfallogtrap.exe(0 to 157)#6 |
Log collection process |
||
|
pdservice.exe |
IM database |
-- |
Windows service control |
|
pdprcd.exe |
Process server process |
||
|
pdprcd.exe(1) |
IM database |
-- |
Process server process |
|
pdrsvre.exe(3) |
Post-processing process. Performs recovery processing when a process terminates abnormally. |
||
|
pdmlgd.exe(1) |
Message log server process. Controls message output. |
||
|
pdrdmd.exe(1) |
System manager process. Controls unit starting and stopping and manages connected users. |
||
|
pdstsd.exe(1) |
Status server process. Controls I/O operations to unit status files. |
||
|
pdscdd.exe(1) |
Scheduler process. Distributes transactions among single server processes. |
||
|
pdtrnd.exe(1) |
Transaction server process. Controls transactions. |
||
|
pdtrnrvd.exe(1 to 128)#7 |
Transaction recovery process. Controls transaction determination and recovery. |
||
|
pdlogd.exe(1) |
Log server process. Controls acquisition of system logs and log-related processes. |
||
|
pd_buf_dfw.exe(1) |
Deferred write process. Controls background writing to disks where the database is kept. |
||
|
pd_buf_awt.exe(2) |
Parallel write process for the deferred write process |
||
|
pdlogswd.exe(1) |
Log swapper process. Allocates and de-allocates system log-related files, manages I/O operations for system log-related files, and acquires syncpoint dumps. |
||
|
pdsds.exe(10 to 96)#8 |
Single server process. Performs SQL processing. |
||
|
pdsha.exe (1) |
IM database |
-- |
Service for embedded HiRDB in a cluster environment |
|
pg_ctl.exe(1) |
Intelligent Integrated Management Database servicing (PostgreSQL) |
-- |
Windows servicing controls |
|
postgres.exe(16 to 100) |
Intelligent Integrated Management Database servicing |
||
|
promsrv.exe(1) |
Trend Data Management Service (Promscale) |
-- |
Windows servicing controls |
|
promscale.exe(1) |
Trend Data Management Service |
- Legend:
-
--: None
#1: The process is started only when Central Scope is used. The process is not started by default.
#2: Maximum 2; normally 1. Breakdown as follows:
-
Main processes of the event generation service
-
Temporary process issued when the event service is connected. The process is generated when the event generation service starts and when an event acquisition filter is updated.
#3: Functionality for correlation event issue (inactive by default). The correlation event generation service is used in systems that do not use the integrated monitoring database.
#4: The process is started when IM Configuration Management is used. The process is not started by default.
#5: The process is started when the Intelligent Integrated Management Base is used. The process is not started by default.
#6: When the parent process starts, no child process is started. The number of child processes increases with the number of remotely monitored files. The maximum number of concurrent child processes is 157.
#7: Only one process runs when the system starts, but this number increases temporarily with each abnormal termination of the pdsds.exe process.
#8: 10 instances of this process run at startup, and this number increases with the number of access requests to the IM database. The maximum number of concurrent processes is 96.
When JP1/IM - Manager is used in a cluster system, the above processes are executed on each physical host and logical host. The number of processes that can be executed concurrently is the number of processes in the table multiplied by the number of physical and logical hosts on which the processes are running.
Processes in the above table whose parent process is jco_spmd.exe are controlled by the process management. You can check their status using the jco_spmd_status command.
An example of the display when the processes are running normally is shown below.
c:\>jco_spmd_status
KAVB3690-I Processing to report the status of JP1_CONS has started.
Display the running processes
Process name Process ID
evflow 3672
jcamain 4088
evtcon 4236
jcsmain 4668
evgen 5624
KAVB3691-I All the processes have started.
jcsmain is listed only when the Central Scope functionality is enabled, evgen is listed only when correlation event generation is enabled, and jcfmain is listed only when the IM Configuration Management functionality is enabled.
(2) JP1/IM - View
The table below describes JP1/IM - View processes. The numbers in parentheses are the number of processes that can be executed concurrently.
|
Parent process |
Functionality |
Child process |
Functionality |
|---|---|---|---|
|
jcoview.exe (3) |
JP1/IM - View process management |
jcoview_evt.exe (3) |
Sends thread dump output events |
|
java.exe (3) |
JP1/IM - View window control |
||
|
jcfview.exe (3) |
IM Configuration Management - View process management |
jcfview_evt.exe (3) |
Sends thread dump output events |
|
java.exe (3) |
IM Configuration Management - View window control |
#: Add when the JP1/IM - View (JP1/IM - Rule Operation linkage function) is active.
- Important
-
-
In case of operating in Japanese if the program jcoview.exe is executed from a command prompt where the code page is set to a value other than 932, the characters displayed on the screen might be garbled.
-
In case of operating in Chinese if the program jcoview.exe is executed from a command prompt where the code page is set to a value other than 936, the characters displayed on the screen might be garbled.
-
(3) JP1/IM - Agent
JP1/IM-Agent process is as follows: The numbers in parentheses () in the table indicate the number of processes to be executed simultaneously. When operating in a cluster system, execute the following processes for each physical host and logical host.
|
Parent process name |
Function |
Child process name |
Function |
|---|---|---|---|
|
jpc_imagent_service.exe(1) |
Start JP1/IM agent control base (imagent) as a Windows service I will |
imagent.exe |
-- |
|
imagent.exe(1) |
Servicing JP1/IM agent control base (imagent) |
-- |
-- |
|
jpc_imagentproxy_service.exe(1) |
Start JP1/IM agent control base (imagentproxy) as a Windows service I will |
imagentproxy.exe |
-- |
|
imagentproxy.exe(1) |
Servicing JP1/IM agent control base (imagentproxy) |
-- |
-- |
|
jpc_imagentaction_service.exe(1) |
Start JP1/IM agent control base (imagentaction) as a Windows service I will |
imagentaction.exe |
-- |
|
imagentaction.exe(1) |
Servicing JP1/IM agent control base (imagentaction) |
-- |
-- |
|
jpc_prometheus_server_service.exe(1) |
Start Prometheus server as a Windows service I will |
prometheus.exe |
-- |
|
prometheus.exe(1) |
Prometheus server |
-- |
-- |
|
jpc_alertmanager_service.exe(1) |
Atart Alertmanager as a Windows service I will |
alertmanager.exe |
-- |
|
alertmanager.exe(1) |
Alertmanager |
-- |
-- |
|
jpc_windows_exporter_service.exe(1) |
Start Windows exporter as a Windows service I will |
windows_exporter.exe |
-- |
|
windows_exporter.exe(1) |
Windows exporter |
-- |
-- |
|
jpc_blackbox_exporter_service.exe(1) |
Start Blackbox exporter as a Windows service I will |
blackbox_exporter.exe |
-- |
|
blackbox_exporter.exe(1) |
Blackbox exporter |
-- |
-- |
|
jpc_ya_cloudwatch_exporter_service.exe(1) |
Start Yet another cloudwatch exporter as a Windows service I will |
ya_cloudwatch_exporter.exe |
-- |
|
ya_cloudwatch_exporter.exe(1) |
Yet another cloudwatch exporter |
-- |
-- |
|
jpc_fluentd_service.exe(1) |
Start Fluentd as a Windows service I will |
ruby.exe |
-- |
|
ruby.exe(1) |
Fluentd |
ruby.exe |
-- |
|
ruby.exe(1 to 129) |
Monitor and notify logs according to the log monitoring definition |
-- |
-- |
|
jpc_promitor_scraper_service.exe(1) |
Start Promitor Scraper as a Windows service I will |
promitor_scraper.exe |
-- |
|
promitor_scraper.exe(1) |
Promitor Scraper |
-- |
-- |
|
jpc_promitor_resource_discoery_service.exe(1) |
Start Promitor Resource Discovery as a Windows service I will |
promitor_resource_discovery.exe |
-- |
|
promitor_resource_discovery.exe(1) |
Promitor Resource Discovery |
-- |
-- |
|
jpc_script_exporter_service.exe(1) |
Start Script exporter as a Windows service I will |
script_exporter.exe |
-- |
|
script_exporter.exe(1) |
Script exporter |
-- |
-- |
Legend
-:None