Improving performance and security by using DBB daemons

DBB provides two build daemons to improve build performance when the DBB User Build tool is used in IBM Developer for z/OS Enterprise Edition (IDzEE) or VSCode. These daemons start and maintain live Java Virtual Machines (JVMs) between builds to avoid the initial startup cost of launching a JVM.

The following two build daemons are available:

• The shared daemon.
  In DBB 2.0.2 and later, the shared daemon launches a pool of JVMs to be shared by a team of developers. It also provides advanced and configurable queueing to control the number of JVMs that run at the same time.

Note: The current documentation of the shared daemon is valid only for DBB 2.0.2 and later. If you are using DBB 2.0.1 or earlier, refer to the DBB 2.0.1 PDF or the DBB 2.0.0 PDF for the shared daemon documentation.

• The personal daemon.
  Each developer gets a dedicated long-running JVM just for their own use. The personal daemon is simple to use and requires minimal configuration. However, it might tax limited resources on a development LPAR.

Note: Starting from version 2.0.2, the personal daemon is deprecated and will be removed in a future release. You should use the shared daemon, which has been enhanced with additional security mechanisms.

For information about installing and configuring the build daemons, see Process definition file, Configuring the shared and personal daemons, and Security definitions for the shared daemon.

Each version of the daemon has the following components:

• The daemon itself, which manages and maintains processes.

• The daemon client, from which you can issue build commands.

It takes you two mandatory and one optional step to use the daemon:

Image of how to use the daemon and its workflow