The long-running scheduler stores job information in a relational database. The first step in setting up the long-running scheduler is to create this database.
WebSphere Extended Deployment provides DDL files to define thelong-running scheduler database in <WAS_install_root>/longRunning. The DDL files for creating the long-running 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 Cloudscape, DB2, Oracle, and Informix. Not all database managers have corresponding tablespace DDL files. Refer to your database vendor's documentation for details on customizing DDL scripts and using the database tools to execute it.
The following steps can be used to configure the long-running scheduler database using the WebSphere embedded Cloudscape database. Note that embedded Cloudscape databases cannot be shared by multiple processes and are unsuitable for environments where the long-running scheduler needs to move from one node to another (for example, high availability scenarios).
For DB2 on z/OS, SPUFI scripts are provided in WAS_install_root/longRunning.
For DB2 Version 7, the long-running scheduler SPUFI is SPFLRSV7. The long-running execution environment SPUFI is SPFLREV7.
For DB2 Version 8, the long-running scheduler SPUFI
is SPFLRS, the long-running execution environment SPUFI
is SPFLREE, and the Postings Sample SPUFI is SPFPOST.
For
both DB2 Versions 7 and 8, the Postings Sample SPUFI is SPFPOST. There are
two versions of long-running scheduler and long-running execution environment SPUFIs for DB2 on z/OS because
of restrictions on the size of the character data columns which comprise the
primary key in DB2 Version 7 for z/OS.
To migrate the long-running scheduler from WebSphere Extended Deployment 6.0 to 6.0.1, do the following: