Interbase Licensing Error
Dulce Donten
I had my RadStudio setup all working and have created a very simple mobile app for android that uses IBLite to grab some data. For business reasons I had to leave the project and move on to other things. So I come back to Radstudio thinking I can just pick up where I left off.
I notice there is an update for the product so I apply the changes and then open up my previous project. From there things get very strange. I can build and deploy to android and the project still works. If I deploy to IOS simulator again no problem and everything works fine. As soon as I try to deploy to a device I get the following compiler error:-
Which looks to me like a problem with the licence file. So I try to manually add it to the deployment but still get the error. So I decided to park my project and go back to the IOS IBLite tutorial from the Embarcadero website. I get to the stage where I want to drop an sqlconnection to the form and connect to the database... No joy it comes up with unavailable database which I thought might be a licensing issue or the fact the IB Server was not running. So I double checked the latter and sure enough it is running as a windows service and I can use IBConsole to connect to it.
I have created a 32Bit RAD Server application and I wanted to host it in my local IIS Server. I followed the steps mentioned in here But when I try to call a webservice say :8080/emsserver/EMSServer.dll/version I get the following error :
Is there again another instance of interbase has to be installed ? I had installed the interbase along with the RAD Studio 10.2 set up. The error message also suggests to configure emsserver.ini. What configuration change does it require ?
Procedurally, depending on your hosting environment, you will add your RAD Server deployment license to InterBase via its License Manager on Windows or via the command line on Linux: /opt/interbase/bin/LicenseManagerLauncher -i Console as discussed here. This presumes you have previously installed InterBase centrally to serve Identity and Access Management (IAM) purposes as well as to record resource data analytics by endpoint (built-in features of RAD Server's RESTful web application framework).
By default, the RAD Server Database is defined within the InterBase file "emsserver.ib" which serves to persist the devices, users, groups and data analytics for all connected RAD Server instances. In turn, the connection parameters required by each RAD Server instance are stored under the [Data] section of the associated EMSSERVER.INI configuration file as detailed hereunder:
As exemplified above, the [Data] section within EMSSERVER.INI defines the connection parameters to the central RAD Server Database (powered by InterBase). The connection parameters needed to get started are:
NOTE: Multiple RAD Server instances (i.e., multiple physical installations on separate machines or docker containers as discussed here) can all use the same remote RAD Server Database backend (powered by InterBase) via this InstanceName setting.
UserName and Password represent credentials for the RAD Server instance connecting to the InterBase-powered RAD Server Database (by default, respectively: sysdba and masterkey).
For a list of add-ons and licenses you can obtain for InterBase products, see Chapter 2, Licensing, in the InterBase Operations Guide. You receive all six InterBase user guides in PDF format at the time of purchase.
Check InterBase Community for a variety of information and resources of interest to those who develop and maintain InterBase databases and applications. Embarcadero maintains several active newsgroups for InterBase users. To access them, go to Forums.
InterBase 2020 Update 6 server is certified to work with a compatible InterBase 2020 Update 6 client. Since there are no breaking API changes, earlier versions of InterBase clients may work with the current version of the server also.
The InterBase installer installs InterBase on Windows, Linux. As part of this installation, you have the opportunity to register the product. InterBase must be registered before you can start the server. If the server is started without entering any licensing information an error message with the registration key is logged in interbase.log. This registration code along with your serial number may then be used to register your software on any computer by going to
Installing and registering the product provides a base level of functionality; the exact level of functionality depends on whether you are installing the Desktop Edition, ToGo Edition, or the Server Edition. It is important to note that the Desktop edition is only available for the Windows operating systems.
To add more users, more processors, or strong encryption, you need to purchase additional appropriate licenses from the Embarcadero shop site or from your sales representative. The license key and registration are explained in the "Licensing" chapter of the Operations Guide. You will find this and the other InterBase books in the /doc directory. See Licensing users, processors, and strong encryption below for more details.
The following instructions guide you through the process of installing and registering InterBase using the cross-platform installer. You are encouraged to use this installer when possible. A console (command-line) installer is available for Unix users who have environments that are not compatible with a GUI installer. However, to use the command-line installer on a Unix OS, you must also have a copy of X-Windows installed. See Command-line installation for instructions on how to run the installation from a console window.
The installers are named ib_install.exe and ib64_install.exe on Windows platforms. Using a property file that contains the variables for a specific install can customize the installer. Property files should be placed in the same directory as the installer. Sample property files are available under the extras directory of the InterBase install kit.
Set to No by Default. If you want to take advantage of the InterBase Multi-Instance feature, set MULTI_INSTANCE=Yes. It is important to set the INSTANCE_NAME and SERVER_TCP_PORT variables to something other than the default to not interfere with other version of InterBase running on the system.
The Wise Installer technology based installer of InterBase on Windows is not available starting with InterBase 2017 Update 3 release for the full product installer. You need to migrate your installation to using the InstallAnywhere based installer on Windows for both English and Japanese. The Update/Patch installer continues to use Wise Install technology though.
This completes your InterBase installation and registration. You now need to install any licenses that you have purchased for users, processors, and Internet use. Please see Licensing Users, Processors, and Strong Encryption for information on licensing.
Return to the opening panel if it is still displayed and choose the connectivity drivers that you want to install. Otherwise, run the InterBase installer again and choose the "Install InterBase Connectivity Drivers" button. Choose a driver to install and follow the prompts.
Use the InstallAnywhere-based installer. The InstallAnywhere-based installer requires X Window System libraries to be available. If they are not available, you will get the error "Installer User Interface Mode not Supported".
For more information about InterBase options, please visit the Embarcadero InterBase Portal. The Licensing chapter in the Operations Guide PDF manual covers this topic in more detail. You can purchase licenses to enable additional simultaneous users and additional processors through the Embarcadero web site or through your sales representative.
In a Multi-Instance install the /usr/interbase symbolic link is not automatically created. Set the INTERBASE and LD_LIBRARY_PATH environment variables to use that particular instance of InterBase. This does not apply to "single" instance installations.
For system library path setting on Linux, please ensure that /usr/local/lib/libgds.so is pointing to a proper libgds.so under /lib folder via a symbolic link (ln -s /opt/interbase_ems/lib/libgds.so /usr/local/lib/libgds.so). This will allow applications without a proper LD_LIBRARY_PATH setting to still launch the InterBase client. If you have better control over the application environment, you can customize LD_LIBRARY_PATH setting to include /opt/interbase_ems/lib and not have any need for the symbolic link
After upgrading to Delphi Rio 10.3.3, I have an issue with IBLite licensing on Android devices (haven't checked on iOS). The issue is the following. When a user downloads the app for the first time, it runs perfectly fine. When they update the app (if they have it already installed on their phone), they get the "product INTERBASE is not licensed" exception. In the same way, during development, if I do a "clean install", everything works fine. If I don't I'm getting the same error.
Most probably, there is a file on the existing app that is not being overwritten during the update because it is newer then the file on the updated app. The files needed for IBLite are the following:
I changed my Interbase connection from IBLite to IBTogo. Now, if I run the app without the "-cleaninstall" in the Run parameters, it works fine on the device. If I create a bundle (32 & 64-bit) and upload it to the Google Play Store, I'm getting the same error: "product INTERBASE is not licensed". Have in mind that this is ONLY if the app is already installed and is updating; not when the user is installing it for the first time.
I've been using a small InterBase database for testing and learning purposes while doing some mobile and web development. I work on a Windows 10 machine and have a Windows 2016 Server, both with InterBase 2020 installed. My Windows 10 development machine has Delphi and I use the developer license for InterBase.
I'm also playing around with RAD Server and have gotten a small module working in RAD Server on my development machine. I'm using my one production RAD Server license on my Windows server which requires encrypted databases. I finally found the reference on how to encrypt an InterBase database and want to copy this database over to the server so I can test it out on a simulated real-world environment.
93ddb68554