Configure WebSphere grid endpoints
Tasks
- Install a batch application on a server or cluster using the administrative console, wsadmin commands, or another supported method for deploying applications.
- If the application is the first batch application installed on the server or cluster, restart the server or cluster.
The WebSphere grid endpoints are automatically set up. By installing the application on the deployment target, the common batch container is automatically deployed on the server or cluster selected using the default Apache Derby data source jdbc/pgc. The default file-based Derby data source can be used only when using the batch function on a stand-alone application server. If we have a WAS Network Deployment environment, we must use a network database.
If we use the default Derby data source, no further action is required. If we use a different data source to make the data source available to the WebSphere grid endpoints.
- On the administrative console, click Environment > WebSphere variables.
- Select the Cell scope from the list.
- Edit the GRID_ENDPOINT_DATASOURCE variable to point to the JNDI lookup name of the job scheduler data source.
- Save the configuration.
- Restart all endpoints.
Subtopics
- Endpoint WebSphere variables
Use WebSphere variables to modify the endpoint configuration. We can do such things as enable jobs to run under user credentials and configure the schema name of the grid endpoint database.
Configure the job scheduler Create the job scheduler and grid endpoint database Install the batch application