WebSphere Extended Deployment Compute Grid provides both implicit and explicit job scheduling requirements, which match against endpoints based on an application name.
An implicit scheduling requirement determines which application(s) a job runs. In Java 2 Platform Enterprise Edition (J2EE) applications, the application name of all J2EE applications installed in the scheduling domain is known through the WebSphere configuration, since all J2EE applications are installed into this environment through WebSphere administrative interfaces.
For grid utility applications, this information cannot be assumed, and by default is unavailable, since grid utility applications are installed outside the control of WebSphere administrative interfaces. For these applications, the grid administrator can optionally enable application-name based endpoint selection for particular nodes by setting the grid.apps node custom property.
if any node published grid.apps then attempt to match job using app names if there is a match then if job has required-capabilities then candidate-nodes= $(apply required-capabilities to the set of nodes that have matching apps) else candidate-nodes= $(nodes that have matching apps) endif else (no match based on grid.apps) if job has required-capabilities then candidate-nodes= $(apply required-capabilities to all nodes) else candidate-nodes= $(all nodes) endif endif else (no nodes publish grid.apps) if job has required-capabilities then candidate-nodes= $(apply required-capabilities to all nodes) else candidate-nodes= $(all nodes) endif endifJ2EE type applications always use application name matching during endpoint selection.
Implicit and explicit matching work together to determine eligible endpoints. For J2EE type jobs, the implicit requirement, application name, is treated simply as an additional required capability; it is logically appended with any explicitly specified requirements.
For grid utility jobs, an application name is a conditional requirement that applies only for grid utility nodes that advertise their installed applications through the grid.apps property. Grid utility jobs for which no application name match exists and that do not specify explicit requirements are eligible for dispatch to any Grid utility node that does not advertise its applications.