Setting up a job manager environment

A job manager environment consists of a job manager and the nodes that it manages. The job manager nodes can be deployment managers and stand-alone application server nodes that are managed by administrative agents. 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 node profiles 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 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.

Procedure

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

    Determine which machines, nodes, and node 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 nodes and resources on those nodes. If the environment includes stand-alone application server 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.

    [AIX Solaris HP-UX Linux Windows] 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, and the job manager server first. After you stop the servers, change the system clock, and then restart the servers. 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.

    [z/OS] 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
    • [Windows] Use the Windows® operating system Taskbar.

      Click Start > [All] Programs > IBM WebSphere > product_name > Profiles > job_manager_profile_name > Start the management server for job administration .

    • [z/OS] 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 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. 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, if security is not enabled, specify 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.
      1. Open a command window on the bin directory of the administrative agent profile.
      2. 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
      3. 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, specify 9960, the default unsecure port number. 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 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.

    • Use the deployment manager administrative console to register deployment managers.
      1. Click Deployment manager > System administration > Job managers > Register with Job Manager.
      2. On the Register with Job Manager page, specify the deployment manager 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, if security is not enabled, specify 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 deployment managers. The command is in the ManagedNodeAgent command group.
      1. Open a command window on the bin directory of the deployment manager profile.
      2. Run the wsadmin command to start the wsadmin tool and, optionally, use the Jython language:
        wsadmin -lang jython
      3. Run the registerWithJobManager command to make the deployment manager a managed 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 disabled, specify 9960, the default unsecure port number. 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.

        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 nodes with the job manager using scripting.

  10. Verify that the nodes are registered with the job manager.

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

    • In the job manager console, click Jobs > Nodes. The Nodes page lists nodes that are registered with the job manager.
    • Run the AdminConfig list command to see a list of managed nodes. Run the following wsadmin scripting commands from the administrative agent bin directory to list stand-alone application server nodes or from the deployment manager bin directory to list a deployment manager node.
      • 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 nodes are registered with the job manager, enter quit to exit the wsadmin scripting tool.

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

    In the job manager console, click Jobs > Node resources > server_name. On the Node 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 and conditions for information centers | Feedback

Last updatedLast updated: Jun 11, 2013 8:40:09 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=tagt_jsetup_fm
File name: tagt_jsetup_fm.html