Edit 10-9-2015 (b), See full draft document.

(5) Licensing

Ongoing licensing work:

• Generation and delivery of license files to RiverWare users. Tasks include tracking of expiring licenses, contacting users to get information; generating license files; updating the license data records; providing instructions for RiverWare download, install, and floating license server manager configuration setup; and problem solving for users.
• Maintenance of licenses for internal development environment.
• Periodic reporting of sponsor and other user licenses, including temporary licenses for users attending in-house and on-site classes.

Upgrade from Reprise License Manager RLM 10.0 to RLM 11.3 (for RiverWare 6.7)

A new version of the Reprise license software (RLM 11.3) is now used by RiverWare. This is an upgrade from RLM 10.0. We started preparing for this upgrade in January 2014, just before RLM 11.0 was released. The first RiverWare version to use this new version (actually, RLM 11.3) is RiverWare 6.7 (released on 8-7-2015). This new RLM version resolved some problems we had been having with roaming licenses. Completed tasks in FY 2015 include:

• Built the RLM Developer Kit (initially with 11.2, and subsequently with 11.3) on both of our release build machines: scuba (32-bit Windows) and spurwink (64-bit Windows).
• Built RiverWare with these new libraries to test new licensing functionality in preparation for upgrading license software in RiverWare 6.7.
• Some exploration was done to see what could be done to support RLM 11 license server on Solaris (which had still been the license server platform used by TVA). Ultimately, TVA moved to a Windows platform for their RiverWare license server, so Solaris support became moot.
• Added new RLM version to the RiverWare build environment. Both 32-bit and 64-bit tar files were made of the relevant libraries and dlls. These were added to the win-config.pl script that is used to update the tools directory of development machines.
• The RiverWare code base was modified to compile with the new version of Reprise and these changes were committed to both the RiverWare 6.7 and the master development branches of the RiverWare code. The 32-bit and 64-bit overnight builds machines were updated for the changes and instructions were sent to all developers regarding the updates.
• Tested the platform-independent settings file between the Windows 64-bit and 32-bit machines.
• Updated the "network license server program" download zip files on the RiverWare download website to contain the new RLM 11.3 license server program files.
• Updated document RLM for RiverWare Configuration and Build Guide. All version numbers and file locations refer to the new release 11.3.
• Updating the online License Server Configuration Guide. The platform-independent ISV server file was added to the release after version 11 is checked into the development area.
• Wrote instructions specific to TVA to test the platform-independent settings file.
• Tested and verified the procedure for upgrading RLM to a new version in RiverWare for floating license users. Compared the old RLM version to the new RLM version in RiverWare to identify the changes and differences in the new RLM version.
• Contributed to the preparation of RiverWare 6.7 release notes with respect to use of the new RLM version.
• A new section, "Upgrade RLM to a New Version," was added to the online document, "License Server Configuration Guide."

Reprise RLM Failover Server License

The failover license is a backup license for floating license users which provides the capability for a different license server to take over the license service when the primary license server has gone down. Work to support this feature included:

• General testing of the failover server license.
• Created failover license template file.
• Created failover license setup instruction guide.
• Worked with Grant County to help them with setting up their failover license server.

Reprise RLM License Generation Tool (rlmgen)

This tool is for internal use only. The purpose is to automate the generation of simple license keys for users. It generates only the license key; it does not generate the standard license information normally included in a license file. This tool is currently configured to generate license keys for the following license types:

1. Floating 1-year
2. Floating CPLEXfromCADSWES
3. Floating CPLEXfromIBM
4. Node-locked CPLEXfromCADSWES
5. Node-locked CPLEXfromIBM
6. Node-locked Evaluation
7. Node-locked Full 1-year
8. Node-locked Sponsor
9. Node-locked Viewer
10. Roaming host=ANY
11. VM-enabled
    

Completed tasks related to the RLM License Generation Tool (rlmgen) in FY 2015 include:

• Set up the RLM License Generation (rlmgen) tool for generating basic RiverWare Viewer Node-locked, RiverWare Node-locked, and RiverWare Floating license key.
• Created product definition for RiverWare license products. This includes full and Viewer licenses, Node-locked and floating licenses, CPLEX licenses, roaming license, and VM-enabled license.
• Testing the license definitions and the license creating procedure. Verifying all different types of licenses created.
• The first licenses, generated by the rlmgen tool, for commercial users and sponsor users, were sent out in May 2015. (Also, with use of the related tool, rlmsign, in June).
• Added a new product definition "Nodelock-Evaluation" which is defaulted to a 60-day license.
• Completed the instruction file "RiverWare License Key Creation Guide (rlmgen)"

Reprise Activation Pro License Center

Reprise Activation Pro allows automated generation of license keys from a web server. CADSWES has explored the possibility of using this tool to generate RiverWare Viewer licenses from our website. Internal support for this capability has been provisionally developed (excluding the web portion). Actual deployment of this capability is still under consideration. Completed tasks in FY 2015 include:

• Set up the product definition for RiverWare Viewer licenses and their activation keys.
• Also set up the analogous node-locked license for comparison.
• Also set up the product definition database for all types of RiverWare licenses. Ten (10) product definitions have been set up. Worked with Reprise support regarding how to set up some customized product definitions, especially for the floating licenses (because we allow users to customize the configuration of their multi licenses).
• Tested the license activation procedure. Testing includes setting up the product definitions, creating license activation keys, activating the license key, and verifying the activated licenses can start RiverWare.
• Drafted the online document, "Obtaining a RiverWare Viewer License Key".

At the end of FY 2015 (Sept), work is continuing on implementing the Reprise Activation Pro License online page and user instructions. The current procedure is very tedious and has too many steps. We are working on simplifying the procedure for users. This has not yet been deployed for actual use.

Significant Licensing User Support Tasks
Note: many of these problems were resolved with the new RLM 11.3 licensing library in RiverWare 6.7 (released on 8-7-2015).

• Three related floating license issues (all reported in October 2014):
  • Grant County's floating license error: client machine cannot start RiverWare. Client machine received "Communications error with license server (-17)" error while license server has started and RiverWare can be checked out on the license server machine.
  • CAP's floating license error: client machine cannot start RiverWare. The license server will be shut down when a client machine tries to start RiverWare. Client machine received "Communications error with license server (-17)" error. License server diagnostics output file received error "Shutdown request by signal@local."
  • Hydro Consulting's roaming license error: roaming license cannot be checked out on the license server machine, but client machines can check out roaming licenses with no problem.
     
• Client machine broadcasting for floating license issue. This issue was reported to Reprise. Client machines would find the floating CPLEX license started on a license server machine and check out the CPLEX license to the client machines, even though the client machines already has its own node-locked license. The client machine would not check out the floating RiverWare license, only the CPLEX license.
• A tool rlmclient.exe built in our developer's kit has been posted on our download site. Users are asked to download this program and execute it on the server or client machine that is experiencing the error to provide further debug information.
• Created an email template file which has the detailed step-by-step instructions on how to generate a full set of diagnostic output files. This list is specifically provided to users who are having floating license problem so they can generate debug log files for us to look into the error.
• Worked on solving the roaming license error on the 32-bit client machine. After the roamed license has been returned to the license pool and the RLM_ROAM variable has been set correctly, RiverWare would not start even with a valid node-locked license. We discovered that restarting the client machine clear up the tangled roaming data left on the client machine. Based on the testing result, the online Roaming License User Guide was updated.

Other Licensing Support Work

• Repaired Maximizer displaying format.
• Updated document "RiverWare License File Creation Guide." Verified that version and location for all license program files are up to date. This procedure document is for internal use only.
• Issued new license files with CPLEX key for all 14 CADSWES training computers.
• Worked on the issue regarding the hacked RLM’s DLL file (rlm#.dll) included in each RiverWare release. Communicated with Reprise support to get their inputs of how to solve and prevent this problem.

---