How to change the Timekeeper node in a TIBCO Data Virtualization Active Clustered environment?

How to change the Timekeeper node in a TIBCO Data Virtualization Active Clustered environment?

book

Article ID: KB0075264

calendar_today

Updated On:

Products Versions
TIBCO Data Virtualization All supported versions

Description

If there is any issue with the network or the any cluster specific issues, the TDV Timekeeper node 'may' have changed to a different node. This article explains how to set the Timekeeper node in TIBCO Data Virtualization Active Clustered environment.

Environment

All supported Operating Systems

Resolution

In TIBCO Data Virtualization, the node which creates the Active Cluster is by default the Timekeeper. To set a different TDV node from the Active Cluster as a Timekeeper, the Regroup cluster activity can be performed. Below are several ways to Regroup the Cluster.

#1) To regroup using TDV Web Manager:

1. Launch TDV Web Manager from the node that needs to be set as the Timekeeper.  
2. From the CONFIGURATION tab, choose Cluster. The members of the Active Cluster are displayed along with their status.
3. Click the 'Re-group Cluster' button. Web Manager displays a Confirmation dialog before proceeding.
Note:  Active Cluster resets all cluster connections for this node, rejoins the cluster, and re-synchronizes its metadata with the cluster. If there are metadata conflicts, this node will be removed from the cluster. Plan to perform this activity during a TDV Server downtime. 

Screenshot for reference:

User-added image
 

#2) Regroup with the cluster_util Script

1. From the TDV Server machine, open a command prompt window or UNIX terminal.
2. Navigate to the [TDVServer_Installation_Dir]/bin directory.
3. Run the cluster_util script using .bat for Windows or .sh for UNIX.
For example: ./cluster_util.sh –regroup -user -password -server [-port ] 
Note: Specify the appropriate information for a TDV server in the cluster that needs to be set as Timekeeper (Information in square brackets is optional). If the port is not mentioned the TDV Server that runs the script becomes the timekeeper if it is not already the timekeeper.
Example (TDV Server on UNIX): ./cluster_util.sh –regroup –user admin –password admin –server localhost –port 9400

Screenshot for reference (TDV Server on Windows)

User-added image
 

#3) Regroup using the API

The cluster regroup API can be run as a web service or from the command line. This API issues a regroup command to all nodes that are reachable and recycles their connections while setting the timekeeper to the node where the command was issued. This does not require a cluster reboot.

From TDV Studio, navigate to the Composite Data Services >services > webservices > system > admin > server > operations > repairCluster.
When using the API for regrouping, specify REGROUP as the option and the remaining details of the TDV node that needs to be set as the timekeeper. Additional information about the API can be found under the INFO tab.
Example:

<server:repairCluster xmlns:server="http://www.compositesw.com/services/system/admin/server">
  <server:option>REGROUP</server:option>
  <server:remoteHostName>localhost</server:remoteHostName>
  <server:remotePort>9800</server:remotePort>
  <server:remoteDomainName>composite</server:remoteDomainName>
  <server:remoteUserName>admin</server:remoteUserName>
  <server:remotePassword>password</server:remotePassword>
</server:repairCluster>

Screenshots for reference:

User-added image  User-added image

Issue/Introduction

How to change the Timekeeper node in a TIBCO Data Virtualization Active Clustered environment?