Creating the database for application schedulers

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.

Why and when to perform this task

Complete the following steps to create application scheduler databases.

Steps for this task

  1. Create a database. To create the database for a scheduler or to determine if an existing database is adequate for a scheduler, review the topic, "Create scheduler databases".
  2. Create the scheduler tables. There are three methods for creating the tables for a scheduler:
    1. Create tables for schedulers using the administrative console. Use the administrative console to add, delete and verify database tables through a Web browser. This method is ideal for developers and simple scheduler topologies.
    2. Create tables for schedulers using JMX or scripting. Use JMX to add, delete and verify database tables programmatically with Java or scripting. This method is ideal for automating scheduler configurations for simple scheduler topologies.
    3. Create tables for schedulers using DDL files. Manually edit the DDL files through a text editor, and verify that mapping between the table names and the scheduler resources and data sources is correct.

What to do next


Copyright IBM Corp. 2003, 2005 |