Endpoint WebSphere variables

Use WebSphere® variables to modify the endpoint configuration. You can do such things as enable jobs to run under user credentials and configure the schema name of the grid endpoint database.

RUN_JOBS_UNDER_USER_CREDENTIAL

Define this WebSphere variable so that jobs can run under user credentials.

Table 1. RUN_JOBS_UNDER_USER_CREDENTIAL. The table includes the scope, valid values, and default for the WebSphere variable.
Scope Valid values Default
Cell, endpoint node, or endpoint server level
  • true

    Jobs are run under user credentials

  • false

    Jobs are run under server credentials

false

GRID_ENDPOINT_HEART_BEAT_INTERVAL

Define this WebSphere variable to configure the amount of time between heartbeat transmissions from the grid endpoint to the job scheduler.

Table 2. GRID_ENDPOINT_HEART_BEAT_INTERVAL. The table includes the scope, valid values, and default for the WebSphere variable.
Scope Valid values Default
Cell, endpoint node, or endpoint server level Time in milliseconds 30 seconds

GRID_ENDPOINT_DATABASE_SCHEMA

Define this WebSphere variable to override the default database schema name for a grid endpoint. Set this variable if the grid endpoint database is different than the job scheduler database and uses a schema name other than the default of LRSSCHEMA.

Table 3. GRID_ENDPOINT_DATABASE_SCHEMA. The table includes the scope, valid values, and default for the WebSphere variable.
Scope Valid values Default
Cell, endpoint node, or endpoint server level Grid endpoint database name LRSSCHEMA

GRID_ENDPOINT_DATASOURCE

Define this WebSphere variable to configure the grid endpoint data source Java Naming and Directory Interface (JNDI) name.

Table 4. GRID_ENDPOINT_DATASOURCE. The table includes the scope, valid values, and default for the WebSphere variable.
Scope Valid values Default
Cell, endpoint node, or endpoint server level Grid endpoint data source JNDI name jdbc/pgc

GRID_MEMORY_OVERLOAD_PROTECTION

Define this WebSphere variable to enable memory-overload protection for the endpoint servers. Memory-overload protection delays the running of a job in the endpoint server if insufficient Java heap memory is available to run the job. The job is delayed until other currently running jobs complete and free up enough memory.

The endpoint server determines the amount of available memory by querying the Java virtual machine (JVM) and assessing the memory requirements of all active jobs currently running within the server.

You can specify the memory requirement for a job by defining the memory attribute of the job element in the xJCL. If you do not specify the memory attribute, then the value of the GRID_MEMORY_OVERLOAD_PROTECTION WebSphere variable is used as the default. If you define the GRID_MEMORY_OVERLOAD_PROTECTION WebSphere variable as ?, then the endpoint server estimates the average job memory requirement by assessing the current active job count and the amount of memory currently in use.

If you do not define the GRID_MEMORY_OVERLOAD_PROTECTION WebSphere variable, then memory-overload protection is disabled.

Table 5. GRID_MEMORY_OVERLOAD_PROTECTION. The table includes the scope, valid values, and default for the WebSphere variable.
Scope Valid values Default
Cell, endpoint node, or endpoint server level
  • An integer value with a unit of KB (kilobytes), MB (megabytes), or GB (gigabytes). For example, specify 100MB or 25KB.
  • A value of ?. The endpoint server estimates the memory requirement for any job that does not define the memory attribute in the xJCL. The estimate is computed by assessing the current active job count and the amount of memory currently in use.
None
Reference topic    

Terms and conditions for information centers | Feedback

Last updated: April 18, 2014 05:01 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-iseries&topic=rgrid_endpointwv
File name: rgrid_endpointwv.html