Administer nodes using the administrative agent

 

+

Search Tips   |   Advanced Search

New feature: The administrative agent provides a single interface to administer multiple unfederated appserver nodes, reducing the overhead of running admin services on every appserver.

We can...

• Set an administrative agent
• Change unfederated appserver nodes registered to the administrative agent
• Change job manager configurations for a registered node.

The job manager asynchronously submits jobs for a node registered to the administrative agent and job manager.

Before you use the administrative agent...

• Install WAS ND V7.0.
• Create a management profile for the administrative agent.

• Start the administrative agent...

  startServer <adminagent_name>

• Use registerNode to register at least one appserver node with the administrative agent.

If we plan to change the system clock...

1. Stop...
   • appservers
   • node agent servers
   • dmgr server
   • administrative agent server
   • job manager server

2. Change the system clock

3. Restart the servers

Ensure clocks on all systems that communicate with each other and have WAS installed are synchronized. Otherwise, we might get errors, such as security tokens no longer being valid.

 

Procedure

• View and change properties for the administrative agent.

  System Administration | Administrative agent

  View the administrative agent properties on the Configuration tab and the Runtime tab.

  Select Start components as needed on the Configuration tab to allow administrative agent components to start dynamically as needed for applications.

• View and change properties for a node registered to the administrative agent.

  1. Go to...

     System Administration | Administrative agent | Nodes

     • We can view the nodes registered to the administrative agent.

     • Click Register with Job manager to register an appserver node with a job manager.

     • Click Unregister from a Job Manager to unregister an appserver node from a job manager.

  2. Go to...

     System Administration | Administrative agent | Nodes | mynode

     • Select Poll jobs from job manager to have the administrative agent retrieve jobs from the job manager for this node.

     • To change other properties for the node, click the links under Additional Properties.

• View and change job manager configurations for a registered node.

  1. Go to...

     System Administration | Administrative agent | Nodes | node_name | Job managers

     ...to view the job managers to which the node is registered.

  2. Go to...

     System Administration | Administrative agent | Nodes | node_name | Job managers | job_manager_UUID

     ...to change job manager-related properties for the registered node.

     • Change the polling interval by entering an integer value.

       The administrative agent uses the polling interval to check for jobs from the job manager for this registered node.

     • Optionally change the Web address of the job manager that the administrative agent polls for this registered node.

 

What to do next

We can continue to administer registered nodes from the administrative agent.

Register more nodes with the administrative agent using registerNode.

Deregister nodes from the administrative agent using deregisterNode.

Register and unregister nodes with a job manager.

 

Gotcha

When attempting to unregister an appserver profile that is in ADMIN_AGENT_HOME/bin, a null pointer exception can result if the profile is corrupted or unusable.

If we receive the null pointer exception, the process to unregister the appserver from the administrative agent has failed. You receive error messages...

ADMU0116I ADMU0128I ADMU0211I ADMU0113E ADMU1211I

To resolve the issue...

1. Unregister the appserver node with the deregisterNode command.

2. If the unregistering process fails...

   • Run...

     cd ADMIN_AGENT_HOME/bin
     ./wsadmin
     $AdminConfig list ManagedNode

   • Find the node name in the list of the profile that we are removing, and copy into the following set command...

     set mn isthmusNode09(cells/mymachineCell01/managednodes/mymachineNode01|managednode.xml#ManagedNode_121)
     $AdminConfig remove $mn
     $AdminConfig save
     quit

3. Restart the administrative agent.

   cd ADMIN_AGENT_HOME/bin
   stopServer adminagent
   startServer adminagent

   The profile should be removed from the administrative agent.

4. Delete the corrupted appserver profile using manageprofiles.

Administrative agent settings
Nodes collection for the administrative agent
Register or unregister with job manager settings
Job managers collection

 

Related concepts

Administrative agent

 

Related tasks

Administer nodes using the job manager
Create a management profile with an administrative agent
manageprofiles

 

Related

startServer
registerNode
Administrative console buttons
deregisterNode
stopServer