The Oracle interface for the Project Portal server is a mandatory add-on, the configuration of which cannot and must not be skipped. Installation may continue if Oracle was installed as described in Oracle database server setup.
Project Portal stores project and document structures and properties into an Oracle database for fast and efficient access. For this, the prerequisites are listed and the Oracle Interface is installed after confirmation.
The installation script needs to know the location and port of the Oracle installation and information about the database and Oracle user account used with Project Portal. Note that the previous two questions are asked only if the environment settings that you are using and default system settings are different.
**This version of Kronodoc has the following pre-requisites
(Please see the Kronodoc Server Setup guide for more information)
- Oracle database on Linux, Solaris or HP-UX (Windows is not supported!)
- Oracle database version 11g (R2 or later)
- Oracle Text feature installed and configured
- Kronodoc projects directory readable by Oracle server Oracle user account
- CTXAPP role granted to krono_role
- Increased krono_data tablespace space requirements
NB: IF ANY OF THESE REQUIREMENTS IS NOT MET, PLEASE BAIL OUT NOW.
**
Do you want to continue [no]? yes
These answers specify the details of the Oracle database connection used by Project Portal. The Oracle database can either be local (on the same host as Project Portal) or remote (accessed through a network with local Oracle 10g client libraries). Oracle needs to be running during the installation and use of Project Portal.
What is the host name of the Oracle database server [default ora.company.com]? ora.company.com What is the SID (non-global) of the Oracle database used [default KRONO]? KRONO What is the port to access the Oracle database [default 1521]? 1521 What is your Oracle account user name [default kronodoc]? krono40 What is your Oracle account password [default krono40]? krono40password Oracle database server version is 11.2.0.3.0 User Kronodoc has krono_role Role krono_role has ctxapp role
Unless you are updating an existing Project Portal database installation, you should initialize the empty database. It will then contain the necessary tables for storing documents, properties and structures. When upgrading, a new empty database MUST NOT be initialized.
Do you want to initialize a new empty database [no]? yes
Oracle requires direct access to the document file attachments stored on the Project Portal server for indexing. No special configuration is required if Oracle is running on the same server host as Project Portal.
Is the database running on this operating system instance? [yes]
no
The Project Portal data storage for workspace data should be configured to be on a partition that has enough space to hold all the user data.
The directory should be independent of any specific Project Portal installation or version to make future version upgrades easier. Also, the directory must exist and be empty.
Which directory do you want to use for storing Kronodoc project data? [/home/kronodoc/projects.1]
NB: THE DIRECTORY SHOULD BE INDEPENDENT OF ANY SPECIFIC KRONODOC INSTALLATION OR VERSION TO MAKE FUTURE VERSION UPGRADES EASIER.
The directory can be empty or contain Kronodoc project data.
If the directory is not empty, it will be linked in the new installation.
/home/kronodoc/projects
Using /home/kronodoc/projects. for storing Kronodoc project data
Moving data from /home/arir/foosetup/Kronodoc/KRONO/projects_blank to /home/arir/foosetup/projects
Workspace data moved. /home/arir/foosetup/Kronodoc/KRONO/projects_blank can now be removed
Note that the current user has to be a member of the following group. The database server Oracle user account (for example, oracle) also needs to be a member of this group.
Which operating system group will you be using for granting access to Kronodoc data for the Oracle database user? [kronodoc] kronodoc Note that the current user kronodoc has to be a member of this group. The database server Oracle user account (e.g. oracle) also needs to be a member of this group. Kronodoc is a member of group kronodoc Kronodoc default group is kronodoc Using group Kronodoc for project data ownership Do you want to automatically change group ownership and permissions for project data dir parent and sub directories? [yes] yes Changing group ownership and permissions for /home/kronodoc/projects Changing group ownership and permissions for /home/kronodoc Changing group ownership and permissions for all files in project data directory tree (/home/kronodoc/projects).
If Oracle is running on a separate server, additional configuration of the access paths must be configured. The data directory must be mounted on the database server, providing Oracle read access to the data files.
The Kronodoc project data directory /home/kronodoc/projects should be mounted on the database server file system.
Mount the file system read-only and only allow access from the Oracle server.
In which path do you want to mount it? [/mnt/oracle/krono/home/kronodoc/projects]
/mnt/oracle/krono/home/kronodoc/projects
Using /mnt/oracle/krono/home/kronodoc/projects as the Kronodoc data directory path on Oracle server
**Please verify that /mnt/oracle/krono/home/kronodoc/projects is accessible by the database user account**
Modifying /home/kronodoc/pp2012/Kronodoc/KRONO/conf/instconfig.pm
The system initially and periodically prepares indexes for full text searches of file text content.
Attempting to re-create existing oracle text indexes (Errors may be ignored) Attempting to delete existing oracle text content indexes (Errors may be ignored) Creating Oracle Text index (this may take a while) Filtering file content from files to DB ((this may take a while) Synchronizing file content indexes Attempting to delete existing oracle text metadata indexes (Errors may be ignored) Creating Oracle Text index for metadata (this may take a while) Synchronizing metadata indexes