Registering deployment managers with job managers (deprecated)

Before a job manager can administer federated nodes of a deployment manager and their resources, you must register the deployment manager with the job manager. Registering a deployment manager with a job manager also enables you to run job manager jobs from a deployment manager console.

Before you begin

Deprecated feature: The job manager is deprecated.

Ensure that the deployment manager version number must not be higher than the version number of any job manager with which you are registering the deployment manager.

• 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 a user name and password, and click OK.

     The value that you specify for Port depends upon whether you want to run jobs on the deployment manager from Jobs menu choices in the deployment manager console or a separate job manager console. The default is 9943, the default port for a job manager secure administrative console. Unless you want to use the Jobs choices in a separate secure job manager console, you must specify a different port number.

     • To use the Jobs choices in the deployment manager console, specify a secure or unsecure port number for the deployment manager console.

       For example, specify the port number that is currently shown in the URL for your browser, which is displaying the deployment manager administrative console. If the URL is http://myhost:9065/ibm/console/, then specify 9065.

     • To use the Jobs choices in a job manager console, specify a secure or unsecure port number for the job manager console.

       For example, if the URL for the job manager console is http://myhost:9961/ibm/console/, then specify 9961.

• 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 target node of the job manager.

     AdminTask.registerWithJobManager('[-host jobmgr_host -port console_port -managedNodeName deployment_manager_node_name]')

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

     console_port specifies the deployment manager administrative console port number or the job manager administrative console port number. The value that you specify for console_port depends upon whether you want to run jobs on deployment manager nodes from the job manager function available in a deployment manager or from a separate job manager.

     deployment_manager_node_name is the host name of the deployment manager. The host name typically is the node name.

     For example, to run jobs on deployment manager nodes from the job manager function available in a deployment manager, where the deployment manager console port is 9065 and the deployment manager node name is MyHostCellManager02, specify the following command:

     AdminTask.registerWithJobManager('[-host localhost -port 9065 -managedNodeName MyHostCellManager02]')

     To run jobs on deployment manager nodes from a job manager console, where the job manager console port is 9961 and the deployment manager node name is MyHostCellManager02, specify the following command:

     AdminTask.registerWithJobManager('[-host localhost -port 9961 -managedNodeName MyHostCellManager02]')

     For this example, the job manager profile is in the same installation as the deployment manager profile. Thus, the host value can be localhost.

     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.