Before you begin
Each scheduler requires a database in which to store its persistent information. The choice of database and location should be determined by the application developer and server administrator.
Schedulers use this database for storing tasks and then running them. 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 schedulers. Eventually, however, the scheduler database becomes saturated, and a larger or better-tuned database system is needed. For detailed information on scheduler topologies see the technical paper, "WebSphere Enterprise Scheduler planning and administration guide".
Multiple schedulers can share a database when you specify unique table prefix values in each 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 scheduler databases.Steps for this task
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.