In order to install QLR Manager, you will need to know the Oracle database reference name found in the TNSNAMES.ORA file that you will define to contain the schema which will run QLR Manager. It may also be necessary that your PHP application server be running an Oracle client (such as an instance of SQL Plus) in order for QLR Manager to resolve the reference name into it's network address.
Prior to running the install program, we recommend you read the General Installation help information.
Once the QLR Manger files have been copied onto your application server, the install program can be run by invoking a URL that references install.html. Install.html is found in the main directory of the directories you established when you loaded QLR Manager to your application 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 a 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 schema 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.|
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 a new schema.|
|•||Grant create session, create table, create trigger, and create sequence to the QLR Manager ID that will be created during the install process.|
In order to connect to the database to perform the installation, you must also provide the password for the installation ID.
You must decide on the schema where QLR Manager tables will reside. It is recommended that a separate schema be established for the QLR Manager tables, but it is not mandatory to do so.
When creating a new schema, the tablespaces for permanent and temporary data storage must be defined. You can either create new tablespaces, or use existing tablespace.
Note: It is highly recommended you create a new Permanent tablespace for the schema that will house the QLR Manager tables.
This is especially true if you have decided to use the database to store the page content created by the QLR Manager, as peak load usage may exceed tablespace limits for existing permanent tablespace configurations. This should not be a problem for your temporary tablespace, so using an existing temporary tablespace should not present a problem.
The datapath displayed for where the tablespaces will reside on disk is determined by examining the datapath for your SYSTEM tablespace. The filename created for newly created tablespaces is the datapath + the new schema name + '01.dbf'.