Date Created: Wed 04-Feb-2009

Related Document Categories:

Get my WebSphere Application Server course here >> http://www.themiddlewareshop.com/products/


DeRegister a managed node away from the Administrative Agent in WebSphere Application Server 7 (base)


[root@s15299773 bin]# ./deregisterNode.sh -help
Usage: deregisterNode -profilePath <path of profile to be deregistered> [-host
<adminagent host>] [-connType <SOAP | RMI | JSR160RMI | IPC>] [-port
<adminagent JMX port>] [-username <adminagent user name>] [-password
<adminagent password>] [-nodeusername <registered node user name>]
[-nodepassword <registered node password>] [-profileName <adminagent
profile name>] [-trace] [-help]

Example:

Lets say you have a single Linux machine with an Administrative Agent Profile and an Application Server profile. the Application Server profile is registered with the Admin Agent allowing a the Administrative console the ability to manage the application server node.

The application server profile is located @ /home/apps/was7/profiles/AppSrv01 and was registered with the registerNode.sh command and federated into the admin agents profile.

To un-federate the node and allow the Application Server to be stand lone again use the following command.

You have to use the <was_root>/profiles<admin_agent_profile>/bin/deregisterNode.sh -profilePath /home/apps/was7/profiles/AppSrv01 -username <username> password <password> syntax if security is enabled and you have not added the username and passwords to soap.client.props.

Sample log of the de-registration process

[root@s15299773 bin]# ./deregisterNode.sh -profilePath /home/apps/was7/profiles/AppSrv01 -username wasadmin -password ********
ADMU0116I: Tool information is being logged in file
/home/apps/was7/profiles/AdminAgent01/logs/deregisterNode.log
ADMU0128I: Starting tool with the AdminAgent01 profile
ADMU8053I: Successfully connected to AdminAgent Server: localhost:8877
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: server1
ADMU0506I: Server name: server2
ADMU2010I: Stopping all server processes for node s15299773Node01
ADMU0510I: Server server1 is now STOPPED
ADMU0512I: Server server2 cannot be reached. It appears to be stopped.
ADMU8052I: Removing signers exchanged during node registration.
ADMU8051I: Removed signers successfully.
ADMU8009I: Begin deregistration of Application Server with path
/home/apps/was7/profiles/AppSrv01.
ADMU0024I: Deleting the old backup directory.
ADMU8021I: Backing up the original config directory of the profile will be
deregistered.
ADMU8038I: Deregistering the node with an adminagent.
ADMU8045I: Node has been successfully deregistered.
ADMU8043I: The administrative agent is stopping the administrative subsystem
for the deregistered node.
ADMU8016I: The administrative subsystem for deregistered node has been
successfully stopped.
ADMU8044I: The administrative agent is destroying the administrative subsystem
for the deregistered node.
ADMU8017I: The administrative subsystem for deregistered node has been
successfully destroyed.
ADMU8013I: Application Server with path /home/apps/was7/profiles/AppSrv01 has
been successfully deregistered.


The Administrative Console (admin console) shows at login the choice to switch between the admin agent's admin console or the admin console for the server.

https://www.yourdomain.com:9044/ibm/console/





you can see next time you load the admin console URL login the ability to switch to the node is lost.



You will have to restart the application server again ie


./startServer.sh server1
ADMU0116I: Tool information is being logged in file
/home/apps/was7/profiles/AppSrv01/logs/server1/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server server1 open for e-business; process id is 4460

After de-registration the admin server now has it's own console again.

https://www.yourdomain.com:9045/ibm/console/

Notice the admin console is now loading on it's own port again (above example is SSL port) and it has it's own login again just like a stand alone Application Server.



You can now can stop using the administrative agent and remove the profile if it is not going to be used.

Get my WebSphere Application Server course here >> http://www.themiddlewareshop.com/products/


Steve Robinson - IBM Champion 2013

About Me

Steve Robinson has been working in IT for over 20 years and has provided solutions for many large-enterprise corporate companies across the world. Steve specialises in Java and Middleware.

In January 2013, I was awarded the prestigous 'IBM Champion' accolade.


  • Linked In
  • Twitter
  • About Me
  • My Blog
  • Contact Me

Read my books?

IBM WebSphere Application Server 8.0 Administration Guide

IBM WebSphere Application Server 8.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Categories

Other Categories