After a stand-alone application server is registered with
an administrative agent, you must register the application server
with a job manager to enable the job manager to administer the application
server and its resources.
Before you begin
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.
About this task
To register stand-alone nodes with a job manager, you
can use the administrative agent console or the wsadmin registerWithJobManager command.
Procedure
- Use the administrative agent console to register stand-alone
application server nodes.
- Click .
- On the Configuration tab of the Administrative
agent page, click Nodes.
- On the Nodes page, select the node
to register with the job manager and click Register with
Job Manager.
- 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.
避免困難: 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, connect to the administrative
agent process adminagent and 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.
What to do next
Verify that the application server target is registered
with the job manager.