{"id":6351,"date":"2016-10-12T16:33:13","date_gmt":"2016-10-12T08:33:13","guid":{"rendered":"http:\/\/rmohan.com\/?p=6351"},"modified":"2016-10-12T18:30:21","modified_gmt":"2016-10-12T10:30:21","slug":"synchronization-simplified","status":"publish","type":"post","link":"https:\/\/mohan.sg\/?p=6351","title":{"rendered":"Synchronization Simplified"},"content":{"rendered":"

Synchronization Simplified<\/h3>\n
<\/div>\n
\n
\n

Synchronization Simplified<\/u><\/em><\/strong><\/p>\n

Synchronization is a process of updating the nodes with master configuration repository changes.The network deployment scenario of WebSphere application server contains multiple nodes managed by a Dmgr and Dmgr holds the master repository of configurations. Any updates or changes through Dmr will be saved in the master configuration and the nodes will be aware of these changes only after the synchronization.<\/p>\n

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.<\/p>\n

A Simple example<\/u><\/em><\/strong><\/p>\n

Consider below scenario.<\/p>\n

OS —–\u00a0 Linux
\nHostA —– Dmgr
\nHostB ——Node1 — AppSrv01<\/p>\n

Suggest to stop the Nodeagent process in Node1
\nAutosync should be disabled (figure1)<\/p>\n

<\/div>\n
\n\n\n\n\n
\n
Figure 1<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 As part of the tuning process you wants to\u00a0set the JVM heap size of\u00a0Node1\/AppSrv01 to Min 256\/ Max 512. Let us look at the Dmgr\u00a0(Figure 2)<\/em>\u00a0and Node1 (Figure 3)<\/em> configurations before setting the values.<\/div>\n
<\/div>\n
\n

Both these configuration files does not have an entry for jvm heap size (Linux OS) as there is no value set for it currently<\/p>\n\n\n\n\n
\"jvm_master_config_after_jvmset\"<\/a><\/td>\n<\/tr>\n
Figure 2<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
\n\n\n\n\n
\n
Figure 3<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
<\/div>\n

Now let us set the heap size min value to 256 and max to 512 as below (Figure 4)<\/em><\/p>\n\n\n\n\n
\"jvm_value_set\"<\/a><\/td>\n<\/tr>\n
Figure 4<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Make sure that you are not<\/strong> selecting\u00a0 “synchronize changes with nodes” option (Figure 5) <\/em>and then save the changes to master repository<\/p>\n\n\n\n\n
\"sync_disable\"<\/a><\/td>\n<\/tr>\n
Figure 5<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Now let us examine the master configuration repository (Dmgr) for the chnages we made. There you can see the newly created heap size entries (Figure 6)<\/em><\/p>\n\n\n\n\n
\"jvm_master_config_after_jvmset\"<\/a><\/td>\n<\/tr>\n
Figure 6<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

As we disabled synchronization the jvm configuration file of Node1 will not be having that entry (Figure 7)<\/em><\/p>\n\n\n\n\n
\"jvm_node_after_jvmset_before_sysnc\"<\/a><\/td>\n<\/tr>\n
Figure 7<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Now synchronize the master configuration repository changes with nodes by either a syncNode.sh\/bat or by starting the nodes and then synching it from console, This updates the\u00a0JVM configuration file of Node1 with the latest updates of master configuration (Figure 8).<\/em><\/p>\n\n\n\n\n
\"jvm_node_after_jvmset_after_sysnc\"<\/a><\/td>\n<\/tr>\n
Figure 8<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Another simple and practical test for better understanding of synchronization<\/u><\/strong><\/p>\n

Test #1
\n<\/em><\/strong>Go under the config directory of dmgr (master repository) and create a file
\nPerform a full synchronization<\/p>\n

Navigate to the config directory of node, It will be having the file which you created in master configuration.<\/p>\n

The reason for this is during the full sync process it found a file in the master repository and which is not there in the nodes so full sync process transfer this file to nodes<\/p>\n

Test #2
\n<\/em><\/strong>Go under the node config directory, create a file.
\nPerform a full synchrinization from dmgr
\nNavigate to the config directory of the node and check for the file which you created, the file will not be there.<\/p>\n

The reason for this is, During the full\u00a0synchronization process it found a file in the node repository (which you created) and which is not there in the master repository so full sync process removes the file from node to make the configuration in sync with master repository.
\nTypes of Synchronization<\/u><\/strong><\/p>\n

There are two types of Synchronization<\/p>\n

1.) Partial Synchronization : Here only the configuraion file(s) which has changed at the Dmgr level will be Synchronized with nodes.
\n2.) Full Synchronization: This will Synchronize the entire master repository with the nodes.<\/p>\n

Possible ways of Synchronization<\/u><\/strong><\/p>\n

1. syncNode.sh \/syncNode.bat command from the nodes.
\n2. from the admin console or wsadmin
\n3. When node agent starts
\n4. During federationn process.(addNode.sh)
\n5. Auto\/scheduled sync.<\/p>\n

syncNode.sh \/syncNode.bat command from the nodes.<\/u><\/strong><\/p>\n

Usage: syncNode dmgr_host [dmgr_port] [-conntype ] [-stopservers]
\n[-restart] [-quiet] [-nowait] [-logfile ] [-replacelog]
\n[-trace] [-username ] [-password ]
\n[-localusername ] [-localpassword ]
\n[-profileName ] [-help]<\/p>\n

Normally use it as: syncNode.sh -username -password<\/p>\n

Note:-<\/strong> The node agent should be down to execute syncNode and this is always a full synchronization.<\/p>\n

From the admin console or wsadmin<\/u><\/strong><\/p>\n

This can be either a partial synchronization or full synchronization, It depends on the option selected.<\/p>\n

When node agent starts<\/u><\/strong><\/p>\n

If this option is enabled node agent will synchronize with master repository during the startup process. The very first synchronization after startup will be a Full Synchronization and the consicutive synchronization will be Partial Synchronization.<\/p>\n

During federationn process<\/u><\/strong><\/p>\n

This is always a full synchronization<\/p>\n

Auto\/scheduled sync<\/u><\/strong><\/p>\n

This is normally a partial synchronization but the very first synchronization after the node agent start will be a full synchronization.<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Synchronization Simplified <\/p>\n

Synchronization Simplified<\/p>\n

Synchronization is a process of updating the nodes with master configuration repository changes.The network deployment scenario of WebSphere application server contains multiple nodes managed by a Dmgr and Dmgr holds the master repository of configurations. Any updates or changes through Dmr will be saved in the master configuration and the nodes […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25],"tags":[],"_links":{"self":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/6351"}],"collection":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=6351"}],"version-history":[{"count":3,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/6351\/revisions"}],"predecessor-version":[{"id":6362,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/6351\/revisions\/6362"}],"wp:attachment":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6351"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=6351"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=6351"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}