Progress Sonic ESB Configuration and Management Guide
Progress Sonic ESB Configuration and Management Guide
Progress Sonic ESB Configuration and Management Guide
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Using Activation Daemons<br />
See the following sections for examples that describe how to specify primary <strong>and</strong> alternate<br />
servers for different JDBC drivers:<br />
● “Specifying Alternate Servers for the <strong>Progress</strong> OpenEdge Driver” on page 145<br />
● “Specifying Alternate Servers for the DB2 Driver” on page 161<br />
● “Specifying Alternate Servers for the Informix Driver” on page 172<br />
● “Specifying Alternate Servers for the Oracle Driver” on page 187<br />
● “Specifying Alternate Servers for the Microsoft SQL Server Driver” on page 200<br />
● “Specifying Alternate Servers for the Sybase Driver” on page 213<br />
Using Activation Daemons<br />
Using an Activation Daemon is a way to launch new containers as spawned processes of<br />
the container hosting the Activation Daemon. This allows new containers to be launched<br />
by remote administrative clients without the administrator having to log on to that host. A<br />
typical use would be to have the container hosting the Activation Daemon launched as a<br />
Windows service on Windows platforms or a startup process under UNIX.<br />
An Activation Daemon monitors the health of its spawned containers <strong>and</strong>, depending on<br />
configured rules, restarts those containers upon failure. Normally one Activation Daemon<br />
is deployed per host. Multiple Activation Daemons can be created per domain. Containers<br />
can be launched by the Activation Daemon:<br />
● At Activation Daemon startup time<br />
● At a configured time<br />
● After a container failure (up to a configurable number of retries)<br />
● On dem<strong>and</strong> from the <strong>Sonic</strong> <strong>Management</strong> Console or via the Activation Daemon’s<br />
management API<br />
You can create <strong>and</strong> configure an Activation Daemon to start an <strong>ESB</strong> Container hosting a<br />
Database Service. The steps required to create, configure, <strong>and</strong> test the Activation Daemon<br />
are:<br />
1. Create an Activation Daemon<br />
2. Add the Activation Daemon to a management container<br />
3. Add a container to an Activation Daemon’s activation list<br />
“Using Activation Daemons” on page 87 provides information about how to complete the<br />
steps to create <strong>and</strong> configure an Activation Daemon to start an <strong>ESB</strong> Container hosting a<br />
service.<br />
<strong>Progress</strong> <strong>Sonic</strong> <strong>ESB</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Management</strong> <strong>Guide</strong> 8.5 136
Change language