Creating application schedulers databases

Before you begin

Your database system must be installed and available.

It is important to know that the scheduler uses this database for storing and running tasks. The performance of schedulers is ultimately limited by the performance of the database. If you need more tasks per second, you can run the scheduler daemons on larger systems or you can use clusters for the session beans used by the tasks. Eventually, however, the task database becomes saturated and you then need a larger or better-tuned database system.

Multiple applications can share a scheduler database. This sharing can lower the cost of administering scheduler databases.

The scheduler requires a database, a JDBC provider, and a data source.

Why and when to perform this task

To create a database for the application scheduler, follow these steps
Draft comment:
Step one and step 3 have xrefs to be put in.
.

Steps for this task

  1. Create the database according to the description for your database system:
  2. If the database is not on the same machine as your WebSphere Application Server, verify that you can access the database from your application server machine.
  3. Configure your JDBC provider and data source. For details, see the topic Creating and configuring a JDBC provider and data source.

Result

The database is created and ready for you to create scheduler tables.

What to do next


Copyright IBM Corp. 2003, 2005 |