IBM WebSphere - Synchronize a node (syncNode)

 IBM WebSphere - Synchronize a node (syncNode)



Before we get into synchronization, let's talk about nodes and the master configuration. The master configuration is a collection of XML files that contain all sorts of information about a cell, such as the security settings and the applications in the cell. A node contains one or more WebSphere application servers. When a managed nodes is federated into the dmgr, the node needs to be synchronized with the master configuration so that the node is using the dmgr configuration.

The synchronization is always from Dmgr to Nodes and it never happens vise versa. If you made any changes from the node side it will be cleared during next synchronization process.





Let's consider a common example. You make some change in the WebSphere admin console, and you are presented wit the Save option. Selecting save updates the master configuration.






This will cause the node to be out of sync with the master configuration.




To know if a node is synchronized, in the WebSphere admin console, select System administration > Nodes. In this example, AppSrv01Node01 is out of sync.





In this example, the node is synchronized








Be aware that if the dmgr cannot communicate with the node, a question mark icon will be displayed. When there is a lack of communication between the dmgr and the node, synchronization is not possible. In this situation, you first will want to resolve the communication issue between the dmgr and the node




Manual Synch Node


However, you most certainly can manually synchronize the node with the master configuration. To manually synchronize, at System administration > Nodes, check each node that is out of sync, and select Synchronize. Or, you can use the syncNode.sh (Linux) or syncNode.bat (Windows) commands (more on this in a moment).

We can manually synchronize a node with the Deployment Manager through the command
syncNode command. The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.


Go to the respective profile bin /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin folder and run:

  • Stop the Nodeagent as first step

./stopNode.sh -user <username> -password <password>
  • Run the below command to synch Node manually with DMGR

./synchNode.sh <DMGR HostName > <SOAP Connector Port> -user <username> -password <password>


 Automatic synchronization 



Typically, there is no need to get involved and manually synchronize the node with the master configuration. By default, at System administration > Nodes > nodeagent > File synchronization service, Automatic synchronization is enable, so that the synchronization will happen automagically, once every 1 minute.






There are two types of synchronizations.

  •  Synchronization:  In this node synchronization operation is performed using the normal synchronization optimization algorithm. This operation is fast but might not fix problems from manual file edits that occur on the node .So it is still possible for the node and cell configuration to be out of synchronization after this operation is performed.

  • Full synchronization:  In this it clears all synchronization optimization settings and performs configuration synchronization a new ,so there will be no mismatch between Node and Cell configuration after this operation is performed. This operation can take longer time than the synchronization operation.

Comments

Post a Comment

Popular posts from this blog

Daily usage Linux Commands for Any Middleware Administration

Daily usage Linux Commands for Any Middleware Administration Processes related: ------------------ $ ps -ef | grep <process_name> ----- will show the process ID of the proces $ ps -eaf --> to see the Process ID's $ telnet <hostname> <Port_Number> --> It is used to check whether port(server) is listening or not $ scp    -r     file_Name     username@hostname:path  ----- If you want to copy a file from one linux server to another sever $ kill -9 PID ----- Killing an unwanted process $ kill -3 PID ----- Used to take thredDump of the process $ ssh username@servername --> Command used to login to server $ nslookup <host_name> --> Query the nameserver for the IP address of the given HOST optionally using a specified DNS server (To identify the server ip_address by using nslookup command ) $ crontab Minute Hour DayOfMonth Month DayOfWeek (eg: 30 08 10 06 * /home/was/full-backup) ----- Used to scheduled a job on Li...
Read more

Backup and Restore of WebSphere Application Server configuration

                      Backup & Restore of IBM WebSphere Application Server Configuration Backup configuration in  WebSphere One of the major activity that we can perform in Websphere as a pre-requisites when ever we intended to perform any major configuration changes like Fix Pack upgrade ,Interim Fix upgrade, JDK upgrade etc. For any mission critical application, taking frequent backups is essential for recovering from severe errors. In the case of WebSphere Application Server, setting up of the application server environment is a demanding task and it is not an easy to repeat the setup if something bad happens. So, its wise to take backups whenever we make the first setup or when we do configuration changes. Depending upon our diskspace availability two types of backups is possible . 1) Full Backup A full backup can be performed by running the ./backupConfig command from the<WAS-ROOT>/bin di...
Read more