Services: Training Services | Consulting Services
In this case I have a Websphere ND installation that has a DMGR and a one Node.
I ran an upgrade using the Update Installer (See my other articles on this site) and after logging back into a restarted Deployment Manager I saw the following
Looking at the Deployment Manager Node I am able to tell the ports being used, I can then manually issue a node sync to ensure that the node is synchronised and since the deployment manager has been restarted it knows it has an upgrade where as the node agent is out of sync with the DMGR and need to be told to sync.
Select Deployment Manager from the LHS navigation menu
Using the port information, I can use the nodeSync command.
[root@s15418557 bin]# ./syncNode.sh
Usage: syncNode dmgr_host [dmgr_port] [-conntype <type>] [-stopservers]
[-restart] [-quiet] [-nowait] [-logfile <filename>] [-replacelog]
[-trace] [-username <username>] [-password <password>]
[-localusername <localusername>] [-localpassword <localpassword>]
[-profileName <profile>] [-help]
./syncNode.sh <host_name> 8879 -conntype SOAP
Once the node is synchronised I can then restart it
[root@s15418557 bin]# ./startNode.sh
ADMU0116I: Tool information is being logged in file
ADMU0128I: Starting tool with the appsrv01 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 30263
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.
IBM WebSphere Application Server 8.0 Administration Guide
WebSphere Application Server 7.0 Administration Guide
Contact | Articles | Shell Scripts | Java Code | JACL | Jython | WebSphere MQ | WebSphere Message Broker | WebSphere Blog | © Copyright 2006-2013 Robinson (UK) Limited