Jetro CockpIT™ Version 3.0 Knowledge Base

:: Quick search Users Cannot Access the CockpIT Logon Page Login Button Does Not Work Single User Cannot Access CockpIT Login Fails for All Users CockpIT Administrator Cannot Access the Site Jetro Client Failed to Download, Operate, or Install Users Cannot Launch Programs Now but Could Before Application Launching and Closing Takes a Long Time User Does Not Get a Newly Defined Application Specific Application Sometimes Works and Sometimes Doesn't White Screen Appears Instead of an Application Terminal Server Asks for Username and Password Terminal Server Fails to Communicate with CockpIT "No server available" Error Message Newly Defined Users or Groups Can Not Be Added to a Security Policy "Maximum concurrent users reached" Error Message "Failed to check in, wrong login parameters" Error Message Jetro Client Failed to Login Automatically When Restarting Computer Configuring CockpIT for the NAT Environment Removing CockpIT Plug-in Files Changing the Domain to Which CockpIT is connected to Determining the size of the Directory Service Optimizing CockpIT Synchronization with Directory Service Creating a Server Failure Alert Script Creating a Load Balancing File Changing a Server's Load Balancing File Backing-up CockpIT Data, Files, and Site Icons Restoring the CockpIT Administrated Server Farm JdsWebClient.dll or MstsCax.dll Can Not Be Found Failed to Trigger Application

JKB000336 Enabling CockpIT Server Redundancy System (SRS™) Introduction: Jetro CockpIT includes an active-passive clustering solution. This means that one server, the active server, communicates with terminal servers and clients and a second server, the passive server, maintains a duplicate copy of all of the records and changes that take place on the CockpIT Server. If the active server fails, the passive server will automatically become available to serve enterprise clients. Jetro SRS technology currently supports only one active server and one passive server. Users will not be logged out of the applications they are using if the active CockpIT Server fails. They will not be able to log into new applications until they or an administrator changes the address to which users CockpIT Client software is directed. There are four steps to enable SRS in a CockpIT Server Farm: 1. Installing CockpIT Server in two servers (one will be designated the active server and one the passive server) 2. Sharing the CockpIT Server folder between the active and passive servers 3. Configuring terminal servers to send load balancing information to both CockpIT Servers 4. Configuring the passive server to synchronize with the active server This document explains steps 2 to 4 of this process. For information about installing CockpIT Servers, please consult the Installation Guide. Step 1: Installing CockpIT Server For instructions about installing CockpIT Server, please see the Installation Guide. Step 2: Configuring File Sharing Between the Active and Passive CockpIT Server The following instructions explain how to configure the active CockpIT Server to share the CockpIT Server file with the passive CockpIT Server. These instructions should be carried out on the active CockpIT Server. 1. After installing CockpIT Server on this server, right click on the Start menu and explore the C drive. 2. Go to Program files – Jetro Platforms. 3. Right-click on the CockpIT Server file and click on Sharing 4. Select "Share this folder" 5. Click on the Permissions button. 6. In the Permissions for CockpIT Server screen un-select the check box in the Allow column for Change. The check box for full control will also disappear. Note: It is recommended to share this file only with the passive CockpIT server. 7. Click OK in the Permissions and file sharing windows. Step 3: Configuring terminal servers to send load balancing information to active and passive servers The following steps should be performed on every terminal server where a TS Agent has been installed. This includes the active and passive CockpiT Servers themselves. 1. Run regedit (Start – run – regedit) 2. Go to the following folder: HKEY_LOCAL_MACHINE – SOFTWARE – Jetro – Jhgate – Performance Monitor 3. Double click on "DispatchURL". Add the URL of the wgate.dll file on the passive CockpIT Server as follows: http://active/cockpit /bin/wgate.dll;http://passive/cockpit/bin/wgate.dll Notice that URLs are separated by a ";" without a space. See figure below: Click OK when complete. 4. Double click on "RemoteHost". Add the name of the passive CockpIT Server. See figure below: Click OK when done. Step 4: Configuring the passive server to synchronize with the active server 1. After installing CockpIT Server and TS Agent on this server, run regedit (Start – run – regedit). 2. Go to the following folder: HKEY_LOCAL_MACHINE – SOFTWARE – Jetro –JDSClusterManager 3. Right-click in a blank space on the Registry Editor screen and choose New and DWORD Value 4. Name the new DWORD Value "ReplicationPeriod". 5. Right-click on ReplicationPeriod and choose modify. 6. Choose Decimal in the Base sub-table. 7. In "value data", specify a number in seconds. This value will determine how frequently the passive CockpIT Server will communicate with the active CockpIT Server to determine what changes, if any, have been made on the active CockpIT Server. Click OK when done. 8. Right-click again on a blank space in the Registry Editor screen and choose New. This time create a new string value. 9. Name the new string value "SourcePath". 10. Right-click on SourcePath, choose modify, and enter the network path for the shared CockpIT Server folder on the active CockpIT Server e.g. \\active\CockpIT Server. See figure below: Click OK when done. 11. Right-click again on a blank space in the Registry Editor screen and choose New. Create a new string value and name it "SourceURL". 12. Right-click on SourceURL, choose modify and enter the http or https* path to the wgate.dll file on the active CockpIT Server e.g. http://active/cockpit/wgate.dll. See figure below: Click OK when done. 13. Close regedit. 14. Open Services. (Start – programs – administrator tools – services) 15. Restart the following services: 1. JDSClusterManager 2. JDS   Final Steps 1. Verify the all terminal servers are sending load status information to both CockpIT Servers. 2. Verify that all terminal servers are sending load status to both CockpIT Servers. 3. Check that the passive CockpIT Server is replicating data from the active CockpIT Server. (Publish a new application, wait for the replication interval to pass and confirm that the application appears on the passive CockpIT Server). 4. Disconnect the active CockpIT Server and confirm that the passive user site is now available. Note: while the active server is on line, no one can log on into the passive user site. SRS is now enabled. The passive CockpIT Server will now maintain a complete copy of all of the changes that take place in the active CockpIT Server. If the active CockpIT Server fails, the passive CockpIT Server can take its place until the active CockpIT Server is brought back online. Directing Users to the Passive CockpIT Server If the active CockpIT Server fails, there are two ways to direct users to the passive server. Change DNS Alias– If users are pre-configured to connect the CockpIT server through a DNS alias record, update the DNS alias record with the IP address of the passive CockpIT Server. If the OS of the active server is working you will need to disconnect it from the network or change its IP address. If you do not disconnect the active server or change its IP address the local DNS cache may cause users to continue to be directed to the active server. E-mail users a new link - Send users links to the passive server and direct them to connect to this server instead of the active server. Alternatively, send a registry update directing users to the passive server. Server address information is stored on the following registry key of every workstation with Jetro CockpIT Full Client software: HKEY_CURRENT_USER\Software\Jetro Platforms\Cockpit\JDsClient. In the server parameter, add the name or IP address of the passive CockpIT Server. Re-activating the Active Server Only one server can allow user logins at a time. When the passive CockpIT Server recognizes that the active server is working, it will stop all user logins to the users site. Remember to update users or change the DNS alias record when re-activating the active server. Back to top