To Configure Initiators in a Running JES Region

Initiators can be defined or modified once the region has been started, using the Enterprise Server for .NET Administration UI's Initiators view, or from the command-line using the seeout or casout utilities. Normally initiators would be defined in the region startup file to ensure that they are immediately available to run jobs once the region starts. However, there may be a need to modify the properties of existing initiators or start new ones after a region has been started, due to a change in workload, for example. This procedure demonstrates how to define initiators in a running JES region from the Enterprise Server for .NET Administration UI's Initiators view:

1. Select the running JES region from the Tree pane under Regions > JES, and click Initiators in the Actions pane.

   The Initiators view is displayed in the Results pane, showing each of the initiators currently configured.

2. An initiator may be enabled or disabled by selecting it in the list and clicking the Enabled check box. If the initiator being disabled is currently running a job, the job is allowed to complete, but no further jobs will be scheduled for execution on it until it is enabled again.
3. To create a new initiator, click the Add Initiator icon in the toolbar.

   The Advanced tab is displayed

4. By selecting SEP node affinity, you can now specify the URI of a machine, or a network load balanced set of machines, on which jobs associated with this initiator are to be run. Enter the name of the machine/node in the Host entry field. The full URI is displayed in the URI entry field. The full URI only needs to be entered if a non-standard URI is being used in the scale-out.
   Reasons to restrict the execution of jobs to a specific machine, or set of machines, include:

   • The licenses for third-party software used by the jobs are only installed on these machines
   • The jobs require machines with more/less processing power than the other machines in the default scale-out
   • The jobs need to be run on machines in specific geographic areas

   Click OK to dismiss the dialog and create the initiator.

5. The newly created initiator now appears in the list of initiators in the Results pane.

Note that any changes made in this view will be lost at the next cold-start of the region unless the corresponding changes are made to the initiator configuration in the region startup file. However, changes made in this view will be retained across subsequent warm-starts of the region.