Latest License Management System for ROGUEWAVE ILOG Visualization Products

Article ID: 2434
Last updated: 09 Dec, 2014
Article ID: 2434
Last updated: 09 Dec, 2014
Revision: 1
Views: 1358
Posted: 23 Jul, 2010
by Dean J.
Updated: 09 Dec, 2014
by Lenormand P.

Question

What is the latest License Management System for Roguewave ILOG Visualization Products and what do I need to do in my application?

Answer

1- All ROGUEWAVE ILOG Visualization products except C++ products

Have you removed license keys for both development and deployment?

Yes. Starting from the June 2010 release, all new versions of the Java, and Flex-based products no longer require any sort of license key, for both development and deployment. These products include:

· ROGUEWAVE ILOG ELIXIR
· ROGUEWAVE ILOG ELIXIR ENTERPRISE
· ROGUEWAVE ILOG JVIEWS CHARTS
· ROGUEWAVE ILOG JVIEWS DIAGRAMMER
· ROGUEWAVE ILOG JVIEWS ENTERPRISE
· ROGUEWAVE ILOG JVIEWS GANTT
· ROGUEWAVE ILOG JVIEWS GLE
· ROGUEWAVE ILOG JVIEWS MAPS
· ROGUEWAVE ILOG JVIEWS MAPS FOR DEFENSE
· ROGUEWAVE ILOG JVIEWS TGO

You can now use these products for development and for deployment without any key. You still have to control the use of the product to ensure that you do not exceed your contractual limits (entitlement).

If I am not upgrading to the latest version of the product and want to develop or deploy with a previous release, how do I get license keys?

ROGUEWAVE continues to deliver license keys for supported versions older than this release. Contact the support to get the license keys.

How can we manage the current installations of our Visualization products to ensure we do not exceed our entitlement?

Each ROGUEWAVE ILOG Visualization product delivers ROGUEWAVE License Metric Tool (ILMT) signatures that you can use to manage your inventory of licenses. 

See http://www.ROGUEWAVE.com/software/tivoli/products/license-metric-tool/ to understand how you can leverage these signatures with ILMT.

Each product installs a readme file that explains these signatures.

For development licenses: 
· During the installation, each product installs an ILMT signature to retrieve the Developer Edition license.

For deployment licenses: 
· Because ROGUEWAVE ILOG Visualization programs are typically embedded in the customer's application, ROGUEWAVE cannot automatically add inventory signatures for the deployment licenses.
Each product delivers an archive file that contains signature files for each metric (type of license) available for deployment.
Customers can use these signature files and install them with their application.

2- Product specificities

All JViews products: JViews Charts, JViews Diagrammer, JViews Enterprise, JViews Gantt, JViews Graph Layout for Eclipse, JViews Maps, JViews Maps for Defense, and JViews Telecom Graphic Objects[]

With the latest release of JViews products, do I have to make changes in my Java code now that there are no longer any keys?

Yes. In Java code applications, you must invoke the method IlvProductUtil.DeploymentLicenseRequired 

In thin-client applications, you must instantiate a servlet context listener of a type like DeploymentLicenseRequired_for_IBM_ILOG_JViews_Enterprise_Deployment 

See the section "Deployment licenses" in the product documentation for details.

3- JViews Enterprise

I understand that I can purchase ROGUEWAVE ILOG JViews Enterprise (a package that includes development licenses for JViews Diagrammer, JViews Maps, JViews Charts, and JViews Gantt), and then deploy only a subset of the displays (for example, JViews Diagrammer). How can I make sure that I am only deploying with JViews Diagrammer?

The boundaries between the various JViews Enterprise components (Diagrammer, Maps, Charts, Gantt) are complex. ROGUEWAVE has added an API that helps developers ensure they stay within the set of APIs for which they want a deployment entitlement. When coding with JViews Enterprise, developers must "declare" (through an API) which module or modules of JViews Enterprise they want to use. Any subsequent API call outside of these declared modules will throw an exception.

The set of modules that have been "declared" in this way can be viewed through monitoring tools such as jconsole. 

See the section "Deployment licenses" in the product documentation for details.

This article was:   Helpful | Not helpful
Report an issue
Article ID: 2434
Last updated: 09 Dec, 2014
Revision: 1
Views: 1358
Posted: 23 Jul, 2010 by Dean J.
Updated: 09 Dec, 2014 by Lenormand P.
Also listed in


Others in this category