With a valid Serena Support login that is tied to a site ID with current Support Maintenance (both are required) go to http://support.serena.com/licensing/Default.aspx Complete the 4 drop-down selections for Site, Product, Serial Number and version. Click the enabled "View Licenses" button below the fields that will take you to the "Manage Licenses" table
HP-UX: http://www.hp.com/products1/unix/java/java2/jpi SUN/Windows/Linux: http://java.sun.com/j2se/1.4.1/download.html NOTE: Some of these sites might require you to establish a log-on id first. Follow the installation instructions listed in these sites and retry invoking the Web Client.
What pieces are needed to see the benefit from the fixes in this release? Below is information from the Release Notes about changes made to the Serena License Manager 2.1.4 including the associated Change Request ID and necessary component, in paranthesis. If the item shows "Server", the Serena License Server needs to be upgraded.
Merant, PVCS, and Collage are registered trademarks of Merant Inc. Dimensions, Professional, Tracker, Version Manager, Builder, Meritage, and Mover are trademarks of Merant, Inc. All other products or company names are used for identification purposes only, and may be trademarks of their respective owners. U.S. Government Rights
3.8 Remote Build Server Consumes Too Many Version Manager Licenses a recommended configuration–-residual local omsubmit processes will prevent the identification of remote build process as being remote. This causes the remote build process to consume a Version Manager license when it should not. To prevent this, kill any residual local build omsubmit processes before running remote builds.
On the client machines they will need to setup a System Environment variable “MERANT_LICENSE_FILE” and set that to also be the Host ID of the License Server machine (ie. @OR-NAML).
