Progress Sonic ESB Configuration and Management Guide

Chapter 2: ESB Containers
Using Activation Daemons
Using an Activation Daemon is a way to launch new containers as spawned processes of
the container hosting the Activation Daemon. This allows new containers to be launched
by remote administrative clients without the administrator having to log on to that host. A
typical use would be to have the container hosting the Activation Daemon launched as a
Windows service on Windows platforms or a startup process under UNIX.
An Activation Daemon monitors the health of its spawned containers and, depending on
configured rules, restarts those containers upon failure. Normally, one Activation Daemon
is deployed per host. Multiple Activation Daemons can be created per domain.
Containers can be launched by the Activation Daemon:
● At Activation Daemon startup time
● At a configured time
● After a container failure (up to a configurable number of retries)
● On demand from the Sonic Management Console or through the Activation
Daemon’s management API (see the “Using the Runtime API for the Sonic
Management Environment” chapter in the Progress SonicMQ Administrative
Programming Guide)
This section demonstrates how to create and configure an Activation Daemon to start an
ESB Container. As an example, the procedures describe how to create an Activation
Daemon to automatically start the Service5 container when the Activation Daemon’s
container starts. See the “Configuring Framework Components” chapter in the Progress
SonicMQ Configuration and Management Guide for detailed information on using
Activation Daemons. The steps required to create, configure, and test the Activation
Daemon are:
1. “Creating an Activation Daemon” on page 88
2. “Adding an Activation Daemon to a Management Container” on page 88
3. “Adding an ESB Container to an Activation Daemon’s Activation List” on page 90
87 Progress Sonic ESB Configuration and Management Guide 8.5