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.
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).
SPUFI scripts are provided in WAS_install_root/longRunning.
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.