To Configure Initiators in a JES Region Startup File

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:
  1. Open the startup file of the JES region you are configuring, with the Region Startup File editor. See To Edit a JES Regions Configuration.
  2. In the Results pane, expand the Region node and select the Initiators node. See 1 in the diagram below. A window is displayed, showing the initiators already configured for the region.

  3. 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. See 2 in the diagram below.

  4. To define a new initiator, right-click the Initiators node and select Add... from the context menu. See 3 in the diagram below.

    The Add New JES Initiator dialog is displayed.
  5. 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. See 4 in the diagram below.

    The Advanced tab is displayed.
  6. 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.
  7. The new initiator is now listed under the Initiators node. See 5 in the diagram below. To modify the properties of the initiator just created, select it and change the properties in the displayed Properties window.
  8. Once all changes have been made, choose File > Save, or click the Save icon in the toolbar to save the file. See 6 in the diagram below.

You must cold-start the region for the changes to take effect.

Parent topic: JES Region Configuration
Related tasks
To Edit a Region Startup File Associated with a JES Region
To Create a JES Region Startup File
To Edit a Region Startup File Associated with a JES Region
To Configure Initiators in a Running JES Region
Related reference
casout: administer a batch job or JES region
seeout: administer an Enterprise Server for .NET JES region