Creating scheduler databases

The scheduler uses the scheduler database for storing and running tasks. To create a scheduler database, your database system must be installed and available.

Before you begin

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 reduce the cost of administering scheduler databases.

About this task

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

Procedure

  1. Create the database according to the description for your database system:
    • Creating Apache Derby databases for schedulers.
    • Creating a DB2® database for schedulers.
    • [z/OS]Creating a DB2 database for z/OS® for schedulers.
    • [IBM i]Creating a DB2 for iSeries database for schedulers.
    • Creating an Informix® database for schedulers.
    • Creating a Microsoft SQL Server database for schedulers.
    • Creating an Oracle database for schedulers.
    • Creating a Sybase database for schedulers.
  2. If the database is not on the same machine as your IBM® 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, refer to the Creating and configuring a JDBC provider and data source topic. The JDBC driver can be either one-phase or two-phase commit depending on whether other transactions take place using other data sources, for example, while using the scheduler. The data source can represent multiple versions of the product.

Results

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