The [JDENET_KERNEL_DEF1] section actually refers to an internal kernel that JDE Engineering (development) uses for debugging purposes. You do not need to autostart this kernel. The actual JDENET is controlled by the parameter maxNetProcesses that is found in section [JDENET].
The JDESNET process (on Windows) or the parent JDENET_N (on all other platforms) process is the one that gets started when you start JDE services. It has the capability to launch the required kernels and when request messages come in from clients.
Based on the message identifier the JDESNET/JDENET_N will decide which kernel will handle this message and if this kernel is not available it will start one automatically.
The only kernels that is usually set to autostart is the Scheduler kernel (this is one kernel that has to be set to autostart due to design complications), Call Object kernel (these are set to autostart only for performance purposes. These are not mandatory), Management Kernel (for Server Manager Runtime Metrics) and Metadata kernel (for EntepriseOne 8.12 and above releases only).
No comments:
Post a Comment