Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Scheduler service > Manage schedulers
Create the database for schedulers
Each scheduler requires a database in which to store its persistent information. Schedulers use this database for storing tasks and then running them. The choice of database and location should be determined by the application developer and server administrator.
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 refer to the "WebSphere Enterprise Scheduler planning and administration guide" technical paper.
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. However, do not configure schedulers with non-unique table prefixes such that two separate servers share the same database table. A lease occurs between a specific database table and a scheduler running on a server. This lease allows one server at a time to own the lease to a specific database table. This process exists to ensure that one server runs schedule events, such as EJB timers, in a cluster environment. If the server with this lease is unavailable, another server in the cluster obtains the lease. Complete the following steps to create scheduler databases.
Procedure
- Create a database.
To create the database for a scheduler or to determine if an existing database is adequate for a scheduler, review the Create scheduler databases topic.
- Create the scheduler tables. There are three methods for creating the tables for a scheduler:
- Create tables for schedulers . Use the administrative console to add, delete and verify database tables through your Web browser. This method is ideal for developers and simple scheduler topologies.
- 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.
- Create tables for schedulers using DDL files. Manually edit the DDL files using your favorite text editor, and verify that mapping between the table names and the scheduler resources and data sources is correct.
Related
Create scheduler databases
Scheduler table management functions
Scheduler table definition
Create scheduler tables
Create scheduler tables using scripting and Java Management Extensions
Create scheduler tables using DDL files
Use wsadmin scripting with Java Management Extensions (JMX)
Create scheduler tables using scripting and Java Management Extensions
Use the administrative console
WebSphere Enterprise Scheduler planning and administration guide