Initiators may be defined in the region startup file to ensure that they are immediately available once the region has been
started. If initiators are not defined in the region startup file, they can be defined once the region has been started using
the
Enterprise Server for .NET Administration UI's
Initiators view, or from the command-line using the
casout utility. This procedure demonstrates how to define initiators in a JES region startup file using the
Enterprise Server for .NET Administration UI:
- Open the startup file of the JES region you are configuring, with the Region Startup File editor.
A window is displayed, showing the initiators already configured for the region.
- The properties of an existing initiator can be modified by expanding the
Initiators node, selecting the initiator to be modified and changing the properties in the displayed
Properties window.
- To define a new initiator, right-click the
Initiators node and select
Add... from the context menu.
The
Add New JES Initiator dialog is displayed.
- Enter the name of the new initiator, the job classes associated with the initiator and a description of the initiator in the
Initiator name,
Classes and
Description entry fields respectively. Select
Enabled if you want the initiator to be enabled to run jobs when the region starts. If not selected, the initiator will be unavailable
to run jobs until it is enabled using the
seeout command-line utility or from the
Initiators view of the
Enterprise Server for .NET Administration UI.
If you do not require jobs associated with this initiator to be run on a specific machine, or a network load-balanced set
of machines, click
OK to dismiss the dialog and move to step 7. Otherwise click the
Advanced tab.
The
Advanced tab is displayed.
- 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.
- The new initiator is now listed under the
Initiators node. To modify the properties of the initiator just created, select it and change the properties in the displayed
Properties window.
- Once all changes have been made, choose
, or click the
Save icon in the toolbar to save the file.
You must cold-start the region for the changes to take effect.