You can create a database for the planejador de tarefa and grid
endpoint if you do not use the default Apache Derby database. The planejador de tarefa stores
job information in a relational database while the grid endpoint uses
the database to track the progress of a batch job.
Before you begin
When you install the produto, one Derby Java™ Database Connectivity (JDBC)
provider is created. The Derby JDBC provider contains two data sources.
One is the default Derby data source, JNDI name jdbc/lrsched, that
points to the default Derby planejador de tarefa database.
The other, JNDI name jdbc/pgc, is the batch execution environment
data source. If you decide to use the default data source you do not
need to create the planejador de tarefa database.
The default Derby database for the planejador de tarefa is created
when the planejador de tarefa host
(deployment target) is selected through the administrative console.
The default Derby database for the endpoint is created when a batch
application is first installed on a node. Embedded Derby databases
cannot be shared by multiple processes and are unsuitable for environments
where the planejador de tarefa must
move from one node to another. For example, the job scheduler must
move from one node to another in high availability scenarios.
Evitar Problemas: You may create multiple
base profiles, but when operating in a WebSphere Application Server
non-network deployment environment, such as the WebSphere Application
Server Base product, profiles/instances should not share a relational
database when more than a single instance will be active at one given
time. The instances cannot communicate and inconsistent deletion of
job data from tables is the usual result. Such a use of multiple
base profiles is not supported.
gotcha
About this task
The produto supports Derby, DB2®, and Oracle databases. You can
use the following steps to configure the job scheduler and grid endpoint
database if you decide to use a database other than the Derby database.
When you create the database manually, the planejador de tarefa and grid
endpoint can use the same database.
Procedure
- Select the correct file based on the type of database that
you are going to use.
The produto provides DDL
files except for DB2 on the z/OS® operating system. Use the
DDL files to define the planejador de tarefa database
in the app_install_root/util/Batch directory.
The DDL files for creating the planejador de tarefa database
are named CreateLRSCHEDTablesXxx.ddl where Xxx indicates
the type of database manager that the scripts are intended for. These
same DDL files are used for the grid endpoint.
The produto provides a
SPUFI script for DB2 in the <WAS_install_root>/util/Batch directory.
The SPUFI script is SPFLRS.
- See the documentation of your database vendor for details
on customizing scripts and using the database tools to run it.
What to do next
After creating the database, complete the following steps.
- Define the XA JDBC provider for the database through the administrative
console.
Consult the JDBC provider documentation for more information
about defining a new JDBC provider.
- Create the data source using the JDBC provider through the administrative
console.
Define the data source at the cell level. Doing so guarantees
that the database is available for each application server that hosts
the planejador de tarefa.
- Verify that the database has been created by testing the connection
on the data source that you created in the previous step.
- Configure the job scheduler by selecting the JNDI name of the
newly created data source in the job scheduler panel.
- Specify the JNDI name of the data source that you created in a
previous step as the value of the GRID_ENDPOINT_DATASOURCE variable.