CWS/CMS Application Support

Installing Specified CWS/CMS-A Guide for Technical Staff 11/14/2018

Installing *Specified CWS/CMS Releases – A Guide for Technical Staff

* If this guide applies it is referenced in the applicable release bulletin.

This document is not intended for the typical end user. Rather, it is directed at technical staff, particularly in those sites that prefer to pre-install the CWS/CMS application on end users’ workstations over the weekend. Also, whereas the typical end user would install and then just start using the application, these sites often want to verify installation, which is why this document includes “Testing the New Code Installation” on page 2.

Installation of the new code can be expected to take 5 to 10 minutes. Factors that can affect overall installation time include the speed of the workstation, the speed of the connection to the server, and server/network traffic from other workstations — especially from other workstations running the installer.

In some larger sites, the existing LAN configuration tends to reduce the effect of network traffic, so the bottleneck is often server traffic. To reduce traffic on any single server, multiple software distribution servers have been set up in these sites. This allows an even greater number of concurrent workstation installations.

Note:Since attempts to install over a dialed-in connection would take several hours, it is not tested or supported. The install of new code delivery must occur via the office network. These instructions apply equally to laptops as well as desktops, as long as the workstations are connected to the office network.

Here is what a user can expect to see when the new code delivery goes live. The installation takes place in 3 phases:

  1. Network logon
  2. The Installer
  3. A second network logon
First Network Logon

During network logon, the CWS File Transfer program (CWSFT) downloads a very small set of updated program files.

The Installer

Installation continues when the user starts the CWS/CMS application normally. Users will see a message box that reads “The CWS\CMS Application has detected a newer version of the code on the code server! Would you like to install the most current version of the CWS\CMS Application at this time?” Users whose workstations are network-connected should respond by clicking on the Yes button. Users with dialed-in laptops should respond by clicking on the No button, then connect the laptop to the office network before trying again.

At this point, the workstation briefly displays a panel entitled “Setup” before displaying the main installer panel entitled “CWSCMS Setup.” The screen shows various progress bars during the installation of the new code delivery.

When the installer is finished, it displays another panel entitled “Setup Complete.” The panel contains a pre-selected radio button labeled “Yes, I want to restart my computer now.” Users should leave the radio button selected as-is, and then click on the Finish button. The workstation now restarts.

Note: This workstation restart must occur before the CWS/CMS application will be useable.

Second Network Logon

Following the restart, users need to log onto the network again. The network login script completes some local customization of CWS/CMS settings.

The workstation is now ready to run the CWS/CMS new code.

In Case of Outage

If the CWS/CMS installer aborts due to a power outage or server/network failure outage, it will retry automatically after the outage has been resolved. Take these steps on each workstation that may be affected:

  • If Windows ScanDisk starts, allow it to complete.
  • Start the CWS/CMS application normally.

The Control Panel will determine whether installation was completed. If necessary, it will restart the installation. Otherwise, it will display the Control Panel’s logon dialog as usual. If you are merely verifying installation, you can just cancel out of the logon dialog.

Testing the New Code Installation

Although the following list is not meant to be all-inclusive, it is a suggestion of ways to touch the various parts of the application for purposes of verifying installation. The list is not meant to imply that all of these parts of the application were actually affected by the new code delivery.

  • Retrieve case/referral.
  • Make changes.
  • Print document. (Court template recommended.)
  • Save to database.
  • Retrieve same case/referral.
  • Navigate between Client Services/Caseload and Resource Management applications.
  • Open cases through the Caseload application.
  • Make changes to assignment unit in Resource Management application.
  • Merge county-created placement homes in Resource Management application.
  • Create a referral; add a new assignment. Create a contact in the Contact notebook using that new assignment.
  • From the bulletin, select a new SCR of interest and attempt to verify it.

If you believe you have found a problem, follow normal procedure to report it.

18040v1Page 1 of 2