Each application scheduler requires a databaseto store its persistent
information. The choice of database and location should be determined by the
application developer and server administrator.
Before you begin
Application schedulers use a database for storing tasks and then running
them. Application scheduler performance is ultimately limited by database
performance. If you need more tasks per second, you can run the scheduler
daemons on larger systems, use clusters for the session beans used by the
tasks or partition the tasks by using multiple application schedulers. Eventually,
however, the application scheduler database becomes saturated, and a larger
or better-tuned database system is needed. For detailed information on application
scheduler topologies see the technical paper,
WebSphere Enterprise application scheduler planning and administration
guide.
Draft comment:
Check for accuracy, etc.
Multiple
application schedulers can share a database when you specify unique table
prefix values in each application scheduler configuration. This sharing can
lower the cost of administering scheduler databases.