Question & Answer
How can the active OSLC configuration settings be refreshed on all servers in a load balanced ClearQuest environment?
In a load balanced ClearQuest environment that uses OSLC, configuration changes must be shared across all ClearQuest servers. However, when a configuration change is made, the change is initially visible only to the specific ClearQuest server that processed the change. For the load balanced environment to function as intended, the configuration change must be propagated to all ClearQuest Web servers in the environment. This update can be accomplished by logging into each ClearQuest server to refresh the settings.
You have the option to log into each server manually, or run an automated script that logs into each server. The following example provides a basic template for a Perl script that logs in and out. This script can be run after updating the configuration on any ClearQuest Web server in a load-balanced environment.
@servers = ('https://<lb.server.1>:9443' , 'https://<lb.server.2>:9443');
$get_request = HTTP::Request->new(GET => $_.'/cqweb/oslc/repo/8.0.0/db/SAMPL'.'/refreshRepoConfig');
$get_response = $user_agent->request($get_request);
$delete_request = HTTP::Request->new(DELETE => $_.'/cqweb/oslc/session');
$delete_response = $user_agent->request($delete_request);
Was this topic helpful?
16 June 2018