QLR Manager can be set up in different ways, depending on your server configuration. The most important item to note is the referencing conventions used to configure QLR Manager and to grant your users access to their data.
The single server setup is rather straight forward. Both the database that the users will access, and the QLR Manager application, are on the same server. When this is the case, the server is referred to as "localhost". This means the following:
|•||Your master QLR Manager ID that you create must have access to the QLR Manager tables, with the requesting server being "localhost"|
|•||Your users' database ID's must have access to their data on "localhost".|
|•||When your users log into QLR manager, they can reference "localhost" as the server.|
One Server Setup
Database & QLR Manager on the same server
If the QLR Manager and the database servers are different, the referencing is not difficult, but it is a little trickier than calling all server references "localhost". The important thing to remember is that when you establish database access (within your database application), it is based on which server a request is coming from, not based on where the data is located.
|•||The master QLR Manager ID that you create must have access to the QLR Manager tables, with the requesting access coming from the server where the QLR Manager application resides.|
|•||Your users' database ID's must have access granted to their data, with the requesting access coming from the server where the QLR Manager application resides.|
|•||When your users log into QLR manager, they reference the server where their data is located, which enables QLR Manager to find it. Note: Be sure to grant your users access to execute their commands as coming from the server where QLR Manager resides.|
Two Server Setup
Database & QLR Manager on different servers
Once the proper access has been established, the install program can be run by invoking a URL that references install.html. This is found in the main directory of the directories you established when you loaded QLR Manager to your web server.
|•||If you have not established the proper file access to the /reports directory, and you have chosen to store your pages as files, the install program will issue a warning message.|
|•||A warning message will also be generated if you have not established proper access to the qlr.ini file.|
Even if you don't grant access to create/update the qlr.ini file, the information needed to populate this file will be displayed on the install status page (see below) and you can manually copy and paste this data into the qlr.ini file.
There are only few steps to the install process:
|1.||If this is the first time you are using the installer, you will be asked to accept the terms of the license agreement. If it is not the first time using the installer (there is an option to Update Settings Only on the second page of the install program), you will be prompted to enter the master QLR Manager User ID and password. Even though the install manager is password protected, it is recommended that you rename install.html once you have finished the installation.|
|2.||Next you will be asked to define the database engine with which QLR Manager will be working.|
|3.||The first installer page gathers information about your operating system and an existing database ID to perform the install. When the first page is displayed, it also verifies that the proper access exists for the qlr.ini file and /reports directory. If it does not, a warning message will appear at the bottom of the first page.|
|4.||The second installer page gathers information about the database that will house the tables that drive QLR Manager. This page also contains some advanced settings options.|
|5.||The final installer page is a status page that will give you the results of your install or Settings Update, along with information to manually update your qlr.ini file.|
QLR Manager uses a small set of tables to manage its information. The database server identifies the server that will contain the database for these tables. This can be either a computer name or an IP address. If the QLR Manager database and the QLR Manager application reside on the same server, "localhost" can be used to describe the database location.
The Application Server identifies the server on which the QLR Manager Web application will reside. This can be either a computer name or an IP address. If the QLR Manager database and the QLR Manager application reside on the same server, "localhost" can be used to describe the application location. There are really only two choices for the server name:
|•||"localhost" if you plan on running QLR Manager and the QLR database on the same server.|
|•||The name or IP address of the server that is running this install program.|
In order to perform the installation, you must specify an ID that exists in your database, which has sufficient authority to execute the install. This ID needs the authority to be able to:
|•||Create new databases.|
|•||Create a new user ID.|
|•||Grant SELECT, UPDATE, INSERT and DELETE authority to the QLR Manager ID that will be created in the install process.|
Note: If this is a new installation, an ID with "Super User" authority is needed to perform the install. If this ID does not have a password, the password can be entered as [none]. The installation requires that a master ID and password be created to run QLR Manager. This ID can be an existing or a newly created ID. It is recommended that this ID always have a password, but if your environment does not allow for the creation of new ID's, and an existing ID must be used that does not have a password, then [none] can be used for the QLR Manager master ID as well.
In order to connect to the database to perform the installation, you must also provide the password for the installation ID. This ID must be able to receive requests from the QLR Manager application server.
For example, if the ID to perform the install is called "Fred", and the QLR Manager application server is called "webapps", then fred should have been created with a database command similar to:
GRANT SELECT, UPDATE, INSERT and DELETE on *.* to fred@'webapps' with GRANT OPTION;
You must decide which database that the QLR Manager files will reside. It is recommended that a separate database be established for the QLR Manager tables, but it is not mandatory to do so.
A Unicode transformation format (UTF) is an algorithmic mapping from every Unicode code point (except surrogate code points) to a unique byte sequence. The ISO/IEC 10646 standard uses the term "UCS transformation format" for UTF; the two terms are merely synonyms for the same concept. UTF-8 is the byte-oriented encoding form of Unicode.
If you are using MySQL 4.1 or later, QLR Manager can be installed specifying that it's data tables be set up as UTF-8 compatible. This will allow you to store queries, layouts, etc. that contain character data from numerous languages.
This option can be set in the Advanced Options setting in Step #2 of the installation.