Set up a job manager environment

Network Deployment (Distributed operating systems), v8.0 > Set up the application serving environment > Administer nodes and resources > Administer nodes remotely using the job manager

Set 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 dmgrs, stand-alone application server nodes that are managed by admin 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.
Install the WAS product.
Before you use the job manager, 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 admin agent. Those nodes and admin 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 the environment, you might need profiles for admin agents, the nodes registered to the administrative agents, dmgrs, and the nodes federated with the dmgr.
Job managers can manage v8 and v7 target nodes. A job manager can manage a node at an equal or lesser version number than the job manager. For example, a v8 job manager can manage v8 and 7 nodes. A v7 job manager can manage Version 7 nodes. The fix pack portion of the version number does not matter; for example, a v7.0.0.3 job manager can manage a node at v7.0.0.9, which is v7 with fix pack 9 installed.
Further, a job manager can manage a v8 or v7 dmgr that has a v8, v7, or v6 federated node. A dmgr 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 v6 federated node.

Procedure
Determine the topology for your flexible management environment. Flexible management encompasses admin 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 admin agent on each computer where the stand-alone application servers reside. See topics on the admin agent and Scenarios 5 in the Planning to install WAS topic.
To collectively manage dmgrs 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 WAS topic.
Determine the security roles needed for your flexible management environment.
Depending on the environment, you might need profiles for admin agents, the nodes registered to the admin agents, dmgrs, the nodes federated with the dmgr, 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.
We 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 be authorized to work with an admin agent and its nodes.
For more information, see the job manager security topic.

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 admin 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.

Create profiles for any admin 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 admin agent.
Stand-alone nodes are also called unfederated or base application servers. They are not managed by a dmgr. 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 admin agent enables the administrative agent to manage the nodes. We must register stand-alone application servers with an admin agent before you can register the stand-alone application servers with the job manager.
For details on creating the profiles and registering with an admin agent, see the topic on setting up the administrative agent environment.

Create profiles for any dmgrs and federated nodes that you intend to have in your flexible management environment.
Federated nodes are managed by a dmgr. Federated application servers typically have a profile name such as AppSvr01, however you cannot administer them individually. We must administer federated nodes using the dmgr.
See topics on creating cell profiles, management profiles for dmgrs, or the manageprofiles command.
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 dmgr server, the admin 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, ensure the clocks on all systems that communicate with each other and have WAS installed are synchronized. Otherwise, you might experience errors, such as security tokens no longer being valid.
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 Windows operating system Taskbar.
Click Start > [All] Programs > IBM WebSphere > product_name > Profiles > job_manager_profile_name > Start the management server for job administration .
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.
Register stand-alone application server target nodes with a job manager.
Register stand-alone nodes with a job manager enables the job manager to administer stand-alone application server nodes.
Register dmgrs with the job manager.
Register a dmgr with a job manager enables you to run job manager jobs from a dmgr console and enables the job manager to administer federated nodes of the dmgr and their resources.
Register host computers with the job manager.
A remote host target is not required to have any WAS products installed. There are no software requirements for this host beyond its operating system. Registering a remote host with a job manager enables the job manager to access applications, command files, and other resources on the host computer.
Verify that the targets are registered with the job manager.
We 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 dmgr 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 admin agent bin directory to list stand-alone application server targets or from the dmgr bin directory to list other targets.
To use Jython, 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.
Ensure that the servers in your flexible management environment are running.
In the job manager console or dmgr 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.
Job manager
Create management profiles for job managers
Set up the admin agent environment
Create management profiles with admin agents
Create cell profiles
Create management profiles with dmgrs
Start and stop the admin agent
Start and stop the job manager
Register nodes with the job manager using commands
Administer nodes remotely using the job manager
Submit jobs
New feature: Configure port settings

Related

manageprofiles command
JobManagerNode command group using wsadmin.sh
New feature: New target settings
Commands for the AdminConfig object using wsadmin.sh
System administration for WAS V7: Part 3: Administering a flexible management topology

+
Search Tips | Advanced Search