Configure your flexible management environment by registering
application servers that are registered with administrative agents,
or by registering deployment managers as nodes on the job manager.
After you register nodes with the job manager, you can submit and
manage jobs.
Before you begin
You must configure a flexible management environment, consisting
of a job manager, and optionally an administrative agent for the application
server node to register. Start the job manager and the administrative
agent processes before registering nodes or deployment managers with
the job manager.
Attention: The identity under which
the administrative agent server is running must have at least the
monitor role for the profile of the managed application server node.
Otherwise, when you attempt to register the node with the job manager,
registration fails with the ADMN0022E message.
Ensure that
the administrative agent or deployment manager version number is not
higher than the version number of any job manager with which the administrative
agent or deployment manager is registered. 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.
A job manager can manage a Version
8 or Version 7 deployment manager that has a 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.
About this task
您可以管理多個從含有管理代理程式的管理設定檔執行客戶應用程式的應用程式伺服器。
管理代理程式提供單一管理主控台來管理應用程式伺服器。
您可以在多個部署管理程式之間協調管理動作,以非同步方式管理多個未聯合應用程式伺服器,以及提交工作來從含有工作管理程式的管理設定檔啟動伺服器。
如果要開始利用工作管理程式來執行工作,請將您的應用程式伺服器和部署管理程式節點登錄為工作管理程式的受管理節點。
Use the following
steps to register profiles that contain administrative agents as nodes
on the job manager.
Procedure
- Register the application server with the administrative
agent if it is not yet registered.
Run the registerNode command
from the bin directory for the administrative
agent server to register a node with the administrative agent. When
you run the command, the stand-alone node is converted into a node
that the administrative agent manages. The administrative agent and
the node being registered must be on the same system. You can only
run the command on an unfederated node. If the command is run on a
federated node, the command exits with an error.
If the administrative
console or the management Enterprise JavaBeans (EJB)
applications of the application server being registered are enabled,
the node registration process disables them.
Use the registerNode command
utility to register the application server profile with the administrative
agent, as the following command demonstrates:
bin>registerNode -profilePath /AppServer/profiles/AppSrv01 -host localhost -conntype SOAP -port 8878
- Launch the wsadmin tool.
Navigate to the profile_root/profiles/myAdminAgent/bin directory
and use the following command to connect the wsadmin tool to the administrative
agent process:
wsadmin -profileName myAdminAgent -lang jython
- Register the node as a node on the job manager.
If
the node to register contains an administrative agent, use the
registerWithJobManager command
and the following parameters to register a node as a node on the job
manager.
Table 1. registerWithJobManager
parameter descriptions. Run registerWithJobManager to
register a node with a job manager.Parameter |
Description |
Data type |
-managedNodeName |
Specifies the name of the node that is registered
with the administrative agent. If the node is a deployment manager
profile, specify the node name of the deployment manager. (Required) |
String |
-host |
Optionally specifies the hostname of the job
manager. |
String |
-port |
Optionally specifies the administrative port
number to use. The default secure port number is 9943.
The default unsecure port number is 9960. |
|
-user |
Optionally specifies the connector login user
name. |
String |
-password |
Optionally specifies the password for the connector
login user name. |
String |
-alias |
Optionally specifies an alias for the node.
The job manager uses this name instead of the value of the managedNodeName
parameter to register the node. Use this parameter if the new node
has the same name of a node that is registered with the job manager. |
String |
-startPolling |
Optionally specifies whether to start polling
after registering the node. Specify false to disable
polling. The default value is true. |
Boolean |
-autoAcceptSigner |
Optionally specifies whether to automatically
accept the signer provided by the server. Specify false to
disable this option. The default value is true. |
Boolean |
The following sample command registers
the
AppSvr01 application server profile with the
job manager:
AdminTask.registerWithJobManager('[-host jobMgrHost -managedNodeName AppSvr01]')
The following sample command registers the
DMGR01 deployment
manager profile with the job manager:
AdminTask.registerWithJobManager('[-host jobMgrHost -managedNodeName DMGR01]')
- Optional: Repeat the registerWithJobManager command
to register additional profiles as nodes on the job manager.
Results
The node of interest is registered with the job manager
when the system successfully runs the registerWithJobManager command.
What to do next
Submit, monitor, and manage jobs for the nodes that are
registered with the job manager.