Setting up a job manager environment

A job manager environment consists of a job manager and the targets that it manages. The job manager targets can be deployment managers, stand-alone application server nodes that are managed by administrative agents, and host computers. Setting up a job manager environment involves creating a job manager profile and any other profiles that are needed for the environment, synchronizing the clocks on all environment computers, and then registering the targets with the job manager.

Before you begin

Install the WebSphere® Application Server product.

About this task

Before you use the job manager, you must create a job manager profile and a profile for each target node that you want managed by the job manager.

Job managers are part of the flexible management environment. Job managers can manage stand-alone application server nodes that are registered to an administrative agent. Those nodes and administrative agents are also part of the flexible management environment.

Ensure that the profiles in the flexible management environment either all have security enabled or all have security disabled. Depending on your environment, you might need profiles for administrative agents, the nodes registered to the administrative agents, deployment managers, and the nodes federated with the deployment manager.

Job managers can manage Version 8 and Version 7 target nodes. A job manager can manage a node at an equal or lesser version number than the job manager. For example, a Version 8 job manager can manage Version 8 and 7 nodes. A Version 7 job manager can manage Version 7 nodes. The fix pack portion of the version number does not matter; for example, a Version 7.0.0.3 job manager can manage a node at Version 7.0.0.9, which is Version 7 with fix pack 9 installed.

Further, a job manager can manage a Version 8 or Version 7 deployment manager that has a Version 8, Version 7, or Version 6 federated node. A deployment manager that is registered with a job manager can manage a mixed version cell. Using the job manager, you can submit jobs that manage any resources in the mixed version cell, including resources on a Version 6 federated node.

Procedure

  1. Determine the topology for your flexible management environment. Flexible management encompasses administrative agents and job managers.

    Determine which machines, targets, and target resources such as servers and applications to be in the flexible management environment.

    To manage stand-alone application servers, use an administrative agent on each computer where the stand-alone application servers reside. For more information, see topics on the administrative agent and Scenarios 5 in the Planning to install WebSphere Application Server topic.

    To collectively manage deployment managers and stand-alone application servers on the same or different computers, use a job manager. The stand-alone application servers must be registered with an administrative agent before you can manage them using a job manager. For more information, see Scenarios 5 and 10 in the Planning to install WebSphere Application Server topic.

  2. Determine the security roles needed for your flexible management environment.

    Depending on your environment, you might need profiles for administrative agents, the nodes registered to the administrative agents, deployment managers, the nodes federated with the deployment manager, and job managers. Profiles in the flexible management environment must either all have security enabled or all have security disabled. When you create the profiles, you can specify security options, user names, and passwords.

    You must have security roles that authorize you to work with a job manager and to manage registered targets and resources on those targets. If the environment includes stand-alone application server target nodes, then you must be authorized to work with an administrative agent and its nodes.

    For more information, see the job manager security topic.

  3. Create a management profile for the job manager.

    You can use the Profile Management Tool or the manageprofiles command.

    For example, in the Profile Management Tool, select the Management environment and click Next, select the Job manager server type, and select options that create the profile. By default, a job manager has its own administrative console, administrative security is enabled, and the console port is 9960. To disable administrative security, to specify a security certificate, or to change the default ports, use the advanced profile creation option when creating the job manager profile.

    By default, the first administrative agent profile in a product installation is named JobMgr01 and its server name is jobmgr.

    For more information, see the topic on creating management profiles for job managers.

    For manageprofiles examples, see the topic on the manageprofiles command. For -templatePath, specify the management template. For -serverType, specify JOB_MANAGER.

  4. Create profiles for any administrative agents and stand-alone application server nodes that you intend to have in your flexible management environment. Then, register the stand-alone application server nodes with the administrative agent.

    Stand-alone nodes are also called unfederated or base application servers. They are not managed by a deployment manager. Stand-alone application servers typically have a profile name such as AppSvr01. An administrative agent must be on the same computer as its stand-alone nodes. Registering the stand-alone nodes with the administrative agent enables the administrative agent to manage the nodes.

    Avoid trouble Avoid trouble: You must register stand-alone application servers with an administrative agent before you can register the stand-alone application servers with the job manager.gotcha

    For details on creating the profiles and registering with an administrative agent, see the topic on setting up the administrative agent environment.

  5. Create profiles for any deployment managers and federated nodes that you intend to have in your flexible management environment.

    Federated nodes are managed by a deployment manager. Federated application servers typically have a profile name such as AppSvr01, however you cannot administer them individually. You must administer federated nodes using the deployment manager.

    See topics on creating cell profiles, management profiles for deployment managers, or the manageprofiles command.

  6. Synchronize the clocks on all involved systems.

    If you plan to change the system clock, stop all the application servers, the node agent servers, the deployment manager server, the administrative agent server, the job manager server, and the location service daemon first. After you stop the servers and location service daemon, change the system clock, and then restart the servers and location service daemon. If you change the system clock on one system, you must ensure the clocks on all systems that communicate with each other and have WebSphere Application Server installed are synchronized. Otherwise, you might experience errors, such as security tokens no longer being valid.

  7. Start the job manager server.
    • Run the startServer command.

      For example, suppose the JobMgr01 profile has the server name jobmgr. Run the following command from the bin directory of the JobMgr01 profile:

      startServer jobmgr
    • Use the START command to start the job manager:
      START job_manager_proc_name,JOBNAME=server_short_name,
            ENV=cell_short_name.node_short_name.server_short_name

    If the job manager starts successfully, the message open for e-business displays and is written to the job manager startServer.log file:

    Server launched.  Waiting for initialization status.
    Server jobmgr open for e-business; process id is 1932.

    For more information, see the topic on starting and stopping the job manager.

  8. Register stand-alone application server target nodes with a job manager.

    Registering stand-alone nodes with a job manager enables the job manager to administer stand-alone application server nodes.

    Avoid trouble Avoid trouble: Before you can register the stand-alone application server nodes with the job manager, the stand-alone application servers must be registered with an administrative agent. Ensure that the administrative agent version number (excluding fix pack level) is not higher than any job manager with which you are registering the administrative agent. For details on registering stand-alone application servers with an administrative agent, see the topic on setting up the administrative agent environment.gotcha

    To register stand-alone nodes with a job manager, you can use the administrative agent console or the wsadmin registerWithJobManager command.

    • Use the administrative agent console to register stand-alone application server nodes.
      1. Click System administration > Administrative agent.
      2. On the Configuration tab of the Administrative agent page, click Nodes.
      3. On the Nodes page, select the node to register with the job manager and click Register with Job Manager.
      4. On the Register with Job Manager page, specify a node name, specify a job manager administrative console port number, optionally specify other parameters such as the job manager user name and password, and click OK.
        Avoid trouble Avoid trouble: For Port, specify the job manager administrative console port. If security is not enabled, specify the unsecure job manager administrative console port; the default is 9960 for an unsecure job manager administrative console port. If no port number is specified, the default secure port number 9943 is used.gotcha
    • Use the wsadmin registerWithJobManager command to register stand-alone application server nodes. The command is in the ManagedNodeAgent command group.
      • Open a command window on the bin directory of the administrative agent profile.
      • Run a wsadmin command to start the wsadmin tool, connect the wsadmin tool to the administrative agent process, for example adminagent, and optionally use the Jython language:
        wsadmin -profileName adminagent -lang jython
      • Run the registerWithJobManager command to make a stand-alone application server a managed node of the job manager:
        AdminTask.registerWithJobManager('[-host jobmgr_host -port jobmgr_console_port -managedNodeName application_server_node_name]')

        jobmgr_host is the host name of the job manager. The default value is localhost.

        jobmgr_console_port specifies the job manager administrative console port number. If security is disabled, the default unsecure port number is 9960. If security is enabled, optionally specify the secure port number. The default secure port number is 9943. If no port number is specified, 9943 is used.

        application_server_node_name is the host name of the stand-alone application server, for example, myHostNode01.

        Alternatively, you can run the registerWithJobManager command in interactive mode:

        AdminTask.registerWithJobManager('-interactive')

        If the command is successful, wsadmin displays the unique ID (UUID) of the job manager. For example:

        'JobMgr01-JOB_MANAGER-74cdda0c-68f6-4970-a959-6f6800b9f22d'

    For more information, see the topic on registering target nodes with the job manager using scripting.

  9. Register deployment managers with the job manager.

    To register deployment managers, you can use the deployment manager console or the wsadmin registerWithJobManager command.

    Avoid trouble Avoid trouble: A deployment manager version number must not be higher than the version number of any job manager with which you are registering the deployment manager.gotcha
    • Use the deployment manager administrative console to register deployment managers.
      1. Click System administration > Deployment manager > Job managers > Register with Job Manager.
      2. On the Register with Job Manager page, specify the deployment manager node name, optionally specify other parameters such as the job manager user name and password, and click OK.

        For Port, specify the job manager administrative console port number. If security is not enabled, specify the unsecure job manager administrative console port; the default is 9960. If no port number is specified, the default secure port number 9943 is used.

    • Use the wsadmin registerWithJobManager command to register deployment managers. The command is in the ManagedNodeAgent command group.
      • Open a command window on the bin directory of the deployment manager profile.
      • Run the wsadmin command to start the wsadmin tool and, optionally, use the Jython language:
        wsadmin -lang jython
      • Run the registerWithJobManager command to make the deployment manager a managed target node of the job manager:
        AdminTask.registerWithJobManager('[-host jobmgr_host -port jobmgr_console_port -managedNodeName deployment_manager_node_name]')

        jobmgr_host is the host name of the job manager. The default value is localhost.

        jobmgr_console_port specifies the job manager administrative console port number. If security is not enabled, specify the unsecure job manager administrative console port; the default is 9960. If no port number is specified, the default secure port number 9943 is used.

        deployment_manager_node_name is the host name of the deployment manager, for example, CellManager01.

        Alternatively, you can run the registerWithJobManager command in interactive mode:
        AdminTask.registerWithJobManager('-interactive')
        If the command is successful, wsadmin displays the unique ID (UUID) of the job manager. For example:
        'JobMgr01-JOB_MANAGER-74cdda0c-68f6-4970-a959-6f6800b9f22d'

    For more information, see the topic on registering targets with the job manager using scripting.

  10. Register host computers with the job manager.

    A remote host target is not required to have any WebSphere Application Server products installed. There are no software requirements for this host beyond its operating system. To register remote hosts, you can use the Targets page of an administrative console or the wsadmin registerHost command.

    • Use the Targets page of the job manager console or the deployment manager console to register hosts.
      1. Click Jobs > Targets > New Host .
      2. On the New target page, complete the following steps:
        1. Specify the host computer name in one of the following formats:
          • Fully qualified domain name servers (DNS) host name string, such as xmachine.manhattan.ibm.com
          • Default short DNS host name string, such as xmachine
          • Numeric IP address, such as 127.1.255.3
          The host can be the same computer on which the product is installed or a different computer.
        2. Specify the administrative user name for the host.
        3. Specify the password or private key file for the administrative user so that the job manager can access and run jobs on the host. If the host does not require a password, you can specify a null String value of "".
        4. Specify other parameters as needed.
          Best practice Best practice: Select Save security information and you will not need to enter the user name and password for every job manager action on the host.bprac
        5. Click OK.
    • Use the wsadmin registerHost command to register hosts. The command is in the JobManagerNode command group.
      • Open a command window on the bin directory of the job manager profile.
      • Run the wsadmin command to start the wsadmin tool and, optionally, use the Jython language:
        wsadmin -lang jython
      • Run the registerHost command to make the host computer a target of the job manager:
        AdminTask.registerHost('[-host host_computer -hostProps [ [osType operating_system][username administrative_user]
         [privateKeyFile key_file_path] [passphrase passphrase][saveSecurity true] ]')

        host is the computer name of the host that you want to register with the job manager. You must specify a host value.

        hostProps specifies properties of the host.
        Table 1. registerHost -hostProps defined properties. You can specify one or more defined properties for the registerHost command, or specify undefined properties for the command.
        Property name Property description
        osType The operating system type. Specify osType to enable the command to complete faster. This optional property determines the means for connecting with the host. Valid values are:
        • os390
        username A user with authority to log in to the host. This property is required.
        password The password for the given username. A value for password or privateKeyFile must be specified. If the host does not require a password, you can specify a null String value of "".
        privateKeyFile The path to the private keyfile. If you do not specify a value for password, then you must specify a value for privateKeyFile.
        passphrase A passphrase for the privateKeyFile, if needed.
        saveSecurity Specifies whether to store security properties (username, password, privateKeyFile, passphrase) with the host and used as default values for job submissions. If this property is given a value of true, then the security properties are stored with the host and used for subsequent job submissions to this host.
        Alternatively, you can run the registerHost command in interactive mode:
        AdminTask.registerHost('-interactive')
        If the command is successful, wsadmin displays the unique ID (UUID) of the host.

    For more information, see topics on the New target settings or the JobManagerNode command group.

  11. Verify that the targets are registered with the job manager.

    You can use an administrative console or wsadmin scripting commands to see a list of targets that are registered with the job manager.

    • In the job manager console or deployment manager console, click Jobs > Targets. The Targets page lists targets that are registered with the job manager.
    • Run the AdminConfig list command to see a list of managed targets. Run the following wsadmin scripting commands from the administrative agent bin directory to list stand-alone application server targets or from the deployment manager bin directory to list other targets.
      • To use the Jython scripting language, enter the following two commands in succession:
        wsadmin -lang jython
        
        print AdminConfig.list('JobManagerRegistration')
      • To use the Jacl scripting language, enter the following two commands in succession:
        wsadmin
        
        $AdminConfig list JobManagerRegistration

      After you verify that the targets are registered with the job manager, enter quit to exit the wsadmin scripting tool.

  12. Ensure that the servers in your flexible management environment are running.

    In the job manager console or deployment manager console, click Jobs > Target resources > server_name . On the Target resource page, a server status of Started shows that the server is running.

Results

The flexible management environment is set up and the job manager is configured.

What to do next

Submit jobs using the job manager.




In this information ...


Related concepts

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 3:08:41 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-zos&topic=tagt_jsetup_fm
File name: tagt_jsetup_fm.html