Creating the database for a scheduler

Before you begin

Your database system must be installed and available.

It is important to realize that the scheduler uses this database for storing tasks and then executing them. The performance of the scheduler 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 the scheduler database.

Why and when to perform this task

The scheduler requires a database, a Java Database Connectivity (JDBC) provider and a data source.

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 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, see the topic Creating and configuring a JDBC provider and data source. 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.




Searchable topic ID:   tsch_data
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/scheduler/tasks/tsch_data.html

Library | Support | Terms of Use | Feedback