We begin with a number of definitions, and follow through to the conclusion of the installation.

Transcription

1 Owl-Hosted Server Version 0.9x HOW TO Set up Owl using cpanel Introduction Much of the documentation for the installation of Owl Intranet Knowledgebase assumes a knowledge of servers, and that the installation is on one's own server. However, many prospective users have neither a server to host the software, nor the skill to manage one, yet wish to enjoy the benefits of the Owl Knowledgebase product. Suitable hosts can be found by a web search using the term 'Owl Knowledgebase Hosting'. It is recommended to find a provider that is open to the installation of scripts from outside their normal list (fantastico, Plesk), as there are fewer impediments to the installation of Owl. Some providers will install Owl for a fee; a very few others will install it at no cost. Even fewer providers that have installed Plesk Power Pak 8.0 offer an automated install of Owl, though it may be an older version than is currently available from Sourceforge.net. However, an installation of Owl is relatively straightforward, even for those unfamiliar with the process. This document is by no means exhaustive, it describes one method of installing the product on a hosted server. This tutorial takes the user through an understandable path to install Owl. It is not the most expedient, and a number of extra steps are included to help the uninitiated follow the process of installing the Owl Intranet Knowledgebase, so that they can update or change the product themselves. We begin with a number of definitions, and follow through to the conclusion of the installation. You should also download a copy of the Owl Installation Manual at Comments, suggestions and improvements for this document may be forwarded to:

2 Terms used in this document cpanel Intranet knowledgebase local computer repository owl_db_filedir[x] owl_db_name[x] owl_db_user owl_db_pass root username yourdomain.name yourroot the interface on *nix based computers that allows you limited manipulation of the remote system. the name given to your installation of Owl and the subdirectory in which Owl resides. Often is also the name used for your first repository. the fully operational product. the one you are sitting in front of. ONE file set. Many repositories can be managed from one instance of Owl. the directory(s) you create in / to hold your repository(s). Each must hold a sub-directory with the name Documents. This would be /Intranet in our example (actually /home/username/intranet). the SQL database associated with the repository named owl_db_filedir[x]. This would be Intranet in our example. the name of the user of the database (i.e. the Knowledgebase). password of above user. the top level directory on the remote computer. Usually designated / the name your ISP has assigned for you to access their system. It will have a password associated with it. You will need these two pieces of information to access cpanel. the Domain name you have registered, and your ISP has set up on their host for you. the highest directory you can reach in your hosted space using FTP or cpanel File Manager. This is a virtual directory, usually designated / (note the quotes). It is really something like /home/username/ and you can determine the actual path in a number of ways which are discussed later.

3 This document assumes you are familiar with your chosen FTP program. Notes for Installer: Record your chosen names here for future reference ISP: Domain: Login: Password: (username) yourroot: /home/username owl_db_filedir[x]:/intranet[0] /Second[1] /Third[2] /Fourth[3] owl_db_name[x]: Intranet[0] Second [1] Third[2] Fourth[3] owl_db_user: owl owl_db_pass: owlpass Tools: Browser FTP program that you are familiar with using installed on local computer File Editor (Wordpad (Win) or FileEdit (linux)) Access to cpanel on ISP host computer The file phpinfo.php Installation: 1. Create the following file (phpinfo.php) in your text editor, save it, and upload it using FTP to the public_html folder on your ISP host. <?php phpinfo();?> Run it by typing: in the location bar on your browser. If you receive an error message, you will need to discuss your needs with your ISP and see if you can obtain appropriate permissions for your script. If the script is successful, you will see a lot of information from your ISP. Confirm the following: PHP is greater than 4; and also the real path to yourroot, your assigned (virtual) home folder. It should be /home/username/, but could be different.

4 2. Using your browser, download the most recent version of Owl from to your local computer. If your Host is running linux, then the owl-0.xx.tar.gz is the best choice. 2.1 Using FTP, upload the Owl compressed file to the /public_html directory on the Host computer. Also, in yourroot, create a directory (owl_db_filedir[0]) named Intranet and place a subdirectory within it named Documents. Repeat this step, using a fresh directory name, for each repository you wish to have on your host. Note: this can also be done in cpanel. 3. Using your browser, login to cpanel ( (Login & Password needed) Open File Manager Note: MySQL Databases Note: Error Log Move to the directory /public_html by clicking on the folder icon Extract Owl-XX-XX.tar.gz by clicking on the filename and choosing extract file contents from the list on the upper right of the screen. Close the window or tab that opens to show the extracted files.

5 Return to /public_html, and find the folder that contains all the extracted files (not the tar file). Should be owl- 0.XX. Click on the foldername and choose rename this folder from the selection list at the upper right of the window. Rename this directory Intranet. You will notice that the real path to <yourroot> is displayed at the upper right of the screen during this process. You may need to change permissions on these folders. My ISP seems happy with 755. To accomplish this, you click on the foldername and choose Change Permissions from the selections at the upper right of the window. Make selections as shown and save your changes. You may have to repeat this step with each of the subdirectories within the Intranet directory. Exit File manager by clicking on the X at the top right of the left-hand panel on the screen. 4. Return to your FTP program, and download the following files to a known location on your local computer: /Intranet/config/owl.php /Intranet/DOCS/sql/mysql-tables.sql

6 5. At cpanel, choose mysql You will need to create a database for each repository, one database user, and permissions for that user within each database. 5.1 Create a database <username>_intranet. Repeat with a new database name for each repository. 5.2 Create a user <username>_owl, with a password owlpass 5. Give <username>_ owl all permissions to database <username>_intranet. The database must have at least CREATE, INSERT, SELECT, DELETE, & UPDATE permissions on the databases. Repeat with this user for each database. Note: the remote system will automatically pre-pend your database name and database user name with the <username>_ portion of the names. Now we have to shape the database(s). 5.4 Choose phpmyadmin at bottom of page Choose a database from the selection box on the left of the screen Select your database name from the list on the left Click on IMPORT.

7 5.4.4 Press 'Browse'; a selection window will open to your local computer. Browse to the folder on your local computer where you placed the file mysql-tables.sql, select that file and click 'open'. The selection window will close, returning you to myphpadmin Click on 'GO'. The tables will be loaded into your database Repeat for each database. Exit phpmyadmin. 6. Open owl.php on your local computer. If using Windows, Wordpad is the better editor to use, as it preserves carriage returns better than notepad. Make the following changes to owl.php: 6.1 $default->owl_root_url = "/Intranet"; 6.2 $default->owl_use_fs = true; 6.3 $default->owl_lang = "English"; Insert your choice instead of English You may have to upload other language files to the /locale directory 6.4 $default->owl_db_id[0] = "0"; $default->owl_db_user[0] = "<username>_owl"; $default->owl_db_pass[0] = "owlpass"; $default->owl_db_host[0] = "localhost"; $default->owl_db_name[0] = "<username>_intranet"; $default->owl_db_display_name[0] = "Intranet"; $default->owl_db_ldapserver[0] = "your.ldap.server.address"; $default->owl_db_ldapdomain[0] = ""; //$default->owl_db_filedir[0] = "/var/www/html/owl-0.90"; $default->owl_db_filedir[0] = "/home/<username>/intranet"; $default->peer_auto_publish[0] = "false"; Repeat for each repository changing the database ID, database name, and repository name, as needed. All the databases will have the same user. and so on......$default->owl_db_id[1] = "1"; $default->owl_db_user[1] = "<username>_owl"; $default->owl_db_pass[1] = "owlpass"; $default->owl_db_host[1] = "localhost"; $default->owl_db_name[1] = "<username>_second"; $default->owl_db_display_name[1] = "Second"; $default->owl_db_ldapserver[1] = "your.ldap.server.address"; $default->owl_db_ldapdomain[1] = ""; //$default->owl_db_filedir[0] = "/var/www/html/owl-0.90"; $default->owl_db_filedir[1] = "/home/<username>/second"; $default->peer_auto_publish[1] = "false";

8 7. Using FTP, upload the modified owl.php to /Intranet/config/owl.php. You will have to overwrite the existing file. (Note: you may wish to rename the original file on the host computer back-owl.php before uploading the modified file). Open a browser and type You should see the login screen and can login: admin / password: admin If you get an error on startup, the use of 'Error Logs', on your cpanel page, can help you to determine the problem. The most common difficulty is permissions. Some ISP are satisfied with 755, others have indicated that the permissions must be set to 644 or 744, before the script will run. Yet other ISPs will not allow unapproved scripts at all! As stated earlier, discuss your needs with your ISP, or if you are looking to find an ISP to host your Knowledgebase, do a quick web search, to find suitable hosts. Once you have installed Owl Intranet Knowledgebase, you should take a few minutes and check for updates to the files in the CVS repository at Sourceforge.net and move any recent updates to your installation.