Creating the job scheduler database

The job scheduler stores job information in a relational database. The first step in setting up the job scheduler is to create this database if the default Derby database is not used.

Before you begin

During the WebSphere Extended Deployment Compute Grid installation, one Derby JDBC provider is created. The Derby JDBC provider contains two datasources. One is the default Derby datasource, JNDI name jdbc/lrsched, that points to the default Derby job scheduler database. The other, JNDI name jdbc/lree, is the grid execution environment datasource. You do not need to create the job scheduler database if you decide to use the default datasource. Thejob scheduler datasource JNDI name is specified in the WebSphere administrative console under the job scheduler panel. If you decide to use a different database for the job scheduler, you must manually create the database and assign a database datasource JNDI name in the job scheduler panel. The default Derby database for thejob scheduler is created when the job scheduler host (deployment target) is selected through the administrative console. The default Derby database for the endpoint is created when a grid application is first installed on a node. Note that embedded Derby databases cannot be shared by multiple processes and are unsuitable for environments where thejob scheduler needs to move from one node to another. For example, high availability scenarios. job scheduler.

About this task

WebSphere Extended Deployment provides DDL files to define the job scheduler database in <WAS_install_root>/longRunning directory. The DDL files for creating the job scheduler database are named CreateLRSCHEDTablesXxx.ddl and CreateLRSCHEDTablespaceXxx.ddl where Xxx indicates the type of database manager that the scripts are intended for. WebSphere Extended Deployment supports Derby, DB2, Oracle, and Informix. Not all database managers have corresponding tablespace DDL files.

The following steps can be used to configure the job scheduler database using the WebSphere embedded Derby database. Note that embedded Derby databases cannot be shared by multiple processes and are unsuitable for environments where the job scheduler needs to move from one node to another (for example, high availability scenarios).

[For z/OS operating system] SPUFI scripts are provided in WAS_install_root/longRunning.

Procedure

Refer to your database vendor's documentation for details on customizing DDL scripts and using the database tools to execute it.

What to do next

After creating the database, define its JDBC provider and datasource in the administrative console. To guarantee that the database is available for each application server that hosts the job scheduler, the definition of the data source at the cell level is recommended. Consult the JDBC provider documentation for more information on defining a new JDBC provider. The next step is Configuring the job scheduler.