Creating the grid endpoint database

The grid endpoint uses a separate database to track the progress of a Compute Grid job. Storing this information in a database gives the grid endpoint a transactional datastore that it can use to recover from failures. A particular instance of the grid endpoint can have its own dedicated database, or share a database with other instances of the grid endpoint.

About this task

WebSphere Extended Deployment provides Data Definition Language (DDL) files in the <install_root>/longRunning directory that you can use to define the Compute Grid endpoints database. The DDL files for creating the grid endpoint database are CreateLREETablesXxx.ddl and CreateLREETablespaceXxx.ddl where Xxx indicates the type of database manager. WebSphere Extended Deployment supports Derby, DB2, Oracle, and Informix. Not all database managers have corresponding table space DDL files. Refer to your database vendor documentation for details on customizing DDL scripts and using the database tools.

For DB2 Version 7, the job scheduler SPUFI is SPFLRSV7. The job scheduler runtime environment SPUFI is SPFLREV7.

To use D1LREESM as the schema name for the Compute Grid endpoints application, complete the following steps:
  1. In the SPFLREV7 file, replace the default schema name LREESCHM with D1LREESM.
  2. [For z/OS operating system] Create the new database schema on your DB2 for z/OS database based on the modified SPFLREV7 in step 1.
  3. Use the SPUFI to install the Compute Grid endpoints application as before. Do the same action for the PostingSample application.

To configure the grid endpoint database in a WebSphere Derby database, complete the following steps. Do not use Derby databases in high availability scenarios. These instructions assume that you use the embedded Derby database. Because the embedded Derby database can only be accessed by a single Java Virtual Machine (JVM), each grid endpoint requires its own database. Repeat these steps on each machine that hosts the grid endpoint .

[For z/OS operating system] To use DB2 as a grid endpoint database, the custom property currentSQLID of the datasource must be set to an appropriate value.

To use DB2 9.x on a distributed system as a grid endpoint database, the custom property currentSchema of the datasource must be set to an appropriate value. If you use the CreateLREETablesDB2.dd file to create the grid endpoint database, set the value of currentSchema, which is case-sensitive, to LREESCHEMA.

All the GEE back end databases, except Derby and DB2V82, are built with a NULLID schema name so that you can have multiple GEE databases on the same database server (e.g for development, test, QA and pre-production) or use a schema name that fits a naming standard without having to update the existing DDLs/SPUFIs.

What to do next

Compute Grid will automatically create the LREE derby database.Define the database to WebSphere Extended Deployment. To have multiple grid endpoints share a single database, define the database at the cell level. Define the data source for databases used by a single grid endpoint at the node level.
  1. In the administrative console, select Resources > JDBC Providers.
  2. To define the data source at the cell level, clear the node, server, and cluster fields. To define the data source at the node level, click Browse Nodes, select the appropriate node and click OK.
  3. Click Apply.
  4. Select the JDBC provider that corresponds to the database system with which you create the grid endpoint database. If the JDBC provider for your database vendor is not in the list, define a new JDBC provider. Consult the JDBC provider documentation for more information. If you create the job database using Derby, select Derby JDBC Provider (XA) from the list.
  5. Select Data sources, and click New.
  6. Use the following values:
    • Name: Type LREE, or another name of your choice. If you define per-node data sources, then each node must have a unique name.
    • JNDI name: Type jdbc/lree, or another JNDI name of your choice for the data source. If you define per-node data sources, then each node must have a unique JNDI name.
    • Additional parameters: This value is required by the JDBC provider you select. The Derby data source does not require additional parameters.
  7. Click OK.
  8. If you use a Derby database, click the name of the data source in the table and scroll to the end of the page. Type <db_dir>/LREE database in the Database name field, and click OK.
  9. Save your changes.