Licensing Guide to OpenInsight (Licensing)
Created at 03 MAR 1998 04:33PM
Revelation Software specializes in tools that enable rapid development and easy deployment of packaged and custom line-of-business applications, providing an environment where applications can be maintained and evolved cost effectively. OpenInsight for Workgroups is a market-leading environment for the design, development, maintenance and deployment of this robust class of business applications.
This guide is offered to assist developers and users in understanding our licensing requirements, and to enlist our customers in helping us ensure that licensing guidelines are properly followed. Our license guidelines ensure that we receive fair value for our innovations and have the resources to provide an ongoing continuum of development capabilities.
General Licensing Guidelines
There are two separate and distinct types of OpenInsight licenses: development and deployment. Each is addressed here separately. Revelation Software s licensing is based on several simple principles which are generally accepted by the software industry. These principles are outlined below.
1. OpenInsight comprises the software, manuals, intellectual property, trade secrets and the product license, which together constitute a complete product. These components cannot be separated from one another.
2. Every user of the software (i.e., developer, reseller, individual application user or corporation) has the responsibility to read, understand and comply with Revelation s software licensing guidelines.
3. As a general practice, software should not be copied for any reason other than backup and safekeeping of the original licensed software.
4. No more than one person has the right to use a single software product license at the same time. Each user must be properly licensed for use, according to the terms and conditions outlined by Revelation Software.
The following section of this document addresses frequently asked questions about licensing for OpenInsight for Workgroups. If you have any questions about this document, or about Revelation Software s licensing requirements, please contact our Customer Care Department at 800-262-4747 or 201-594-1422.
Frequently Asked Licensing Questions
What do I need to purchase in order to develop applications with OpenInsight for Workgroups?
Each individual who is developing, testing, supporting, maintaining or customizing applications with OpenInsight must be individually licensed. Therefore, if a development shop has five people working together or individually, each person must be properly licensed, requiring five licenses. The easiest way to determine if each person is uniquely licensed is by serial number. Each individual must have a copy of OpenInsight with a unique serial number. The development license allows the developer to backup his or her copy and make archive copies of applications developed.
Most development teams usually prefer to work from the one networked copy of OpenInsight. By placing OpenInsight on a network, multiple developers can coordinate their activities, and share and reuse tables and application components. To enable multiple networked users to accessOpenInsight, a Collaborative Development Pack is required for each developer requiring access. A Collaborative Development Pack is included with each development copy of OpenInsight for Workgroups. Applying a Collaborative Development Pack to a network version of OpenInsight, increments by one the number of concurrent users that can access that copy of OpenInsight. For example, if five developers require access toOpenInsight on a network, each of the five developers would apply his or her Collaborative Development Pack to a single copy of OpenInsight on a network.
Revelation also sells TeamWorks, which provides either three or five development users that can develop on the same application on a network.
Can I share my license with my application testers?
No. Each development copy is licensed to an individual developer, regardless of how he or she is using that copy. Each member of your team that uses OpenInsight, regardless of how it is being used, must have a properly licensed copy.
How do I deploy my OpenInsight application(s) to end users?
First, you need to determine what capabilities your end users will require. If end users simply need access to the application, you can deploy the application using a runtime. A runtime provides end users full use of the application; however, it does not allow the users to change or modify the application. In other words, the application is fixed, and cannot be modified. Using a runtime does not enable the end user to have database creation or index creation capabilities. The runtime application license specifically prohibits the distribution of any of the OpenInsight tools with the application. These tools include, but are not limited to:
Revelation Reporter
Form Designer
Table Builder
Popup Builder
Client/Server Workspace
User Interface Workspace Web Publishing
Data Warehousing features
Web Access features
Dictionary modifications
Index creation/rebuild
Table creation
XML Workspace
If the end users require the ability to change, modify or maintain the application, the application can be delivered with development-ready deploymentcapabilities. Development-ready deployment enables users to create, maintain or modify application components, including but not limited to tables, dictionaries, indexes, forms and reports. to get Development Ready capabilities you need to purchase the Works.
How are runtimes licensed?
Single-User Runtime
Each development copy of OpenInsight licenses the developer to distribute his or her application as single-user runtimes. As its name implies, a single-user runtime is deployed on an individual computer for local access. Developers may deliver an unlimited number of runtime copies of their application to individual users without any additional fees. The application can be deployed to an unlimited number of single users, so long as those users are not accessing the application via a network. Installing multiple single-user runtime applications on a network is a violation of Revelation licensing, and could potentially result in corruption of your data.
Multi-User Runtime
Applications to be accessed by end users working on a network must be deployed with Runtime Server Deployment Packs (SDPs). Runtime SDPs allow concurrent users to share and access applications on a local area network (LAN).
The installation of a Runtime SDP performs two functions: it increases the number of concurrent users, and selects the appropriate network driver so that the runtime application can communicate properly with the network. For the convenience of end users, Revelation provides three-user, five-user and Enterprise Runtime SDPs. Enterprise come in three levels; Enterprise A is 250 users, Enterprise B* is 500 users, Enterprise C* is 1000 users. Each of these disks can only be installed on one runtime, located on one server. If you need to deploy the application on multiple servers, additional Runtime SDPs must be purchased. A Runteim SDP disk cannot be used on more than one runtime, and that runtime cannot be distributed on more than one server.
How are development-ready applications licensed?
If end users need access to the application, but also need to change, modify or maintain the application, then the application should be delivered with the Works. This will allow you to deliver development-ready capabilities to your users. If you need development capabilities for multiple users, purchase TeamWorks in the developer increment that you need (Three user or Five user licenses). The Works may only be applied to a single server. If you need to deploy your application on multiple servers, additional copies of the Works must be purchased.
Is it possible to deploy an application on a network without buying Server Deployment Packs (SDPs) or The Works?
When implementing and installing multi-user applications, the proper acquisition and licensing of the appropriate pack is required. The Works,Teamworks and the Runtime SDP are an implementation of our licensing, enabling developers to track and administer adherence to our licensing guidelines. We have left certain flexibility in our software to enable easier implementation and installation. Periodically, developers discover that particular implementations of the tool and application will enable them to avoid the installation and licensing of these packs. However, these should not be construed as permission to violate our licensing guidelines. Attempts to circumvent the installation of, or to engineer around the need for the Works (development capabilities) or Runtime SDPs is a direct violation of our licensing. If there is more than one user participating in the access, update or query of an OpenInsight database file, then the proper acquisition and licensing of a Runtime SDP or the Works is required.
How can I extend my Revelation applications to the Web?
OpenInsight Works version 3.3 introduced the capability to implement OpenInsight as an interactive web application and transaction server with your existing applications. With OpenInsight 3.3 and above, your traditional OpenInsight forms, together with their event and database logic, can be extended to interactive browser-based applications with OpenInsight working interactively with the your HTTP server to deliver HTML browser-based rendering of results. When planning your implementation of these capabilities, please consider that when licensing web-enabled applications, the Web Deployment Pack must be purchased.
How do I deploy web-enabled applications?
In order to enable communication from a web browser to a Revelation application via Internet or intranet, the purchase of the Web Deployment Pack is required. The Web Deployment Pack (WDP) is a module which enables the publication of Revelation data to the World Wide Web. The WDP provides Internet users with access to the application extensions exclusively within the context of a web browser. It has no effect on the licensing of networked concurrent users. All users who require standard network access to the application must be properly licensed using the appropriate Runtime Server Deployment Pack or copies of the Works. The WDP can be installed on only one web server. If additional servers are required, a separate WDP license must be acquired.
What is OpenInsight Works & why do I need it?
OpenInsight Works is an annual subscription service which provides developers with access to all of the innovations and improvements that Revelation delivers. The Works is packed with useful source code examples, sample applications, white papers, technical information and more, in addition to product upgrades, that make your investment in OpenInsight even more valuable. Each Works subscription is licensed to an individual developer. Neither the development tool nor the Works content may be copied for use by another user. Each developer must have his or her own unique serial number and Works subscription.
What can I do to improve application performance?
Revelation provides a suite of network products that deliver superior performance and integrity for deployed OpenInsight-based applications:
The Revelation NLM
The Revelation 2000 Service
The Revelation NLM and 2000 Service are licensed per server. The implementation and use of these products require the presence of properly licensed OpenInsight Server Deployment Packs for the correct number of concurrent users. (For additional information about licensing Server Deployment Packs, please see the previous sections regarding Multi-User Runtimes and Development-Ready Deployment). Server Deployment Packs, the NLM, and the NT Service are each licensed independently.
If you have any questions about OpenInsight for Workgroups licensing, please contact our Customer Care Department at 800-262-4747 or 201-594-1422.