QUICK INSTALL: Step by Step Instructions
Setup
Copy over the entire ATiM application code in the document ‘root’ of your web server or in a sub-directory of this one.
Please note that the entire application code can be located elsewhere on your server but some specific changes have to be done (alias creation on apache server or rewrite rules creation on either IIS server).
Set up the database
To activate the user ‘administrator’ (username=’administrator’ & password=’administrator’)
To install a ATiM ‘demo’ application like v2.7.1
Database Access Configuration
Open the database.php file in the ‘ ./app/config/ ‘ directory and complete following information.
Change Mode Access
Open the core.php file in the ‘ ./app/config/ ‘ directory and change the value of the ‘$debug’ variable to switch from debug mode to prod mode. Changing the ‘$isTest’ variable from 0 to 1 will also change the ATiM installation header color to red and add a ‘Test’ word at the end of the header.
-
Set Up Password Business Rules
Many core variables will help you to apply your institution policies regarding users passwords management. See Login and Password Rules Configuration.
-
Set Up ATiM Folders Permissions
- Upload file on the server (See core variable ‘uploadDirectory’ in core.php and How to upload a file on the server with ATiM feature).
- Record any ATiM user log into a txt file (See core variable ‘atim_user_log_output_path’ in core.php).
Change security properties of following folders ‘ ./app/tmp ‘ and ‘ ./app/Locale ‘ (see either Apache, IIS6 or IIS8 documentation).
For ATiM versions >= v2.7.1, same permissions should be applied on folders used to :
-
Two Factor Authentication (TFA or 2FA)
An extra layer of protection used to ensure the security of online accounts beyond just a username and password
To activate this feature you need to
- At least the ATiM 2.8.2
- Set the
2fa_microsoft_google_authvariable in core.php - Set the number of the super admins to manage the 2FA for the users in core.php by modifying the
num_of_super_adminvariable. Minimun one super admin is required
-
Security Salt Variable
A cryptographic salt is made up of random bits added to each password instance before its hashing. Salts create unique passwords even in the instance of two users choosing the same passwords. Salts help us mitigate hash table attacks by forcing attackers to re-compute them using the salts for each user.
- To change the salt you need to modify the Security.salt variable in core.php
- Run the script scripts\Modify The Salt Password\Modify_the_salt.bat to have a MySQL script file to change the password for all active users and also CSV file contains the user information
-
Other Core Variables
- Order
Launch Application
According to the ATiM source code directory, the application can be launched from your web browser with the following URL:
Setup Troubleshooting
This section contains a list of some troubleshooting for ATiM.
Possible Cause: The default timezone used by the date functions has probably not be defined in your php.ini
Solution:
Open your php.ini file. Add the following lines and restart your server.
Possible cause: Non-consistent definition of php variables and ATiM variables that will generate an error when using the data browser.
Solution:
Open the php.ini file and change max_input_vars value to the biggest value then restart the server
OR
Open the core.php of the ATiM source code and change core variable databrowser_and_report_results_display_limit to a lowest value.
Possible cause : Non-consistent definition of php variables and ATiM variables that will generate an error when uploading file into ATiM.
Solution :
Open the php.ini file and change upload_max_filesize value to the biggest value then restart the server
OR
Open the core.php of the ATiM source code and change core variable max upload filesize to the lowest value.
Possible cause: Non-consistent definition of PHP variables and ATiM variables that will generate an error when uploading a file into ATiM.
Solution:
Open the php.ini file and change post_max_size value to the biggest value then restart the server
OR
Open the core.php of the ATiM source code and change core variable upload_max_filesize to the lowest value.
Possible cause:
Premature cookie expiration. The client (your computer) time is in advance compared to the server time (regardless of the time zones). This difference between the client and the server can reduce your allowed session length or even make it impossible to log to the system.
The tmp folder cannot be written to.
Solution:
You need to synchronize both systems time. You should also enable automated time synchronizing on both machines to avoid future problems. If you are in a situation where you can’t synchronize the system time, setting the client time to a future time should resolve the issue.
Change the permissions to allow the web server to write to the tmp directory and subdirectories.
Possible cause: There is an error in the installation and the output buffer crashes before it can print anything.
Solution:
Turn main output buffering off. Go to app/views/layous/default.ctp and comment .
If after that you have no warning message at all, it means that the ob_gzhandler is not installed. Otherwise, keep on debugging.
Possible Cause: ?
Solution: ?
Possible cause: You’re accessing ATiM on the local network, and the compatibility view is activated.
Solution:
In the URL bar, there is an icon representing a sheet of paper torn in two halves. Click on it.
OR
Disable the “Display intranet sites in Compatibility View” option. Go to “Tools” (might be hidden, press the Alt key to show it) and then “Compatibility View Settings”.
Possible cause: The database is empty.
Solution: Fill the database with ATiM creation script.
Possible cause: Your version of PHP is below 5.2.6.
Solution: Upgrade PHP to a version greater or equal to 5.2.6. (PHP 5.3+ is required for ATiM 2.5+)
Possible cause: Your mod-rewrite config might be wrong
Solution: Check your mod-rewrite config.
Possible cause: The proxy settings might interfere.
Solution: Go to preferences (possibly under tools) > advanced > network > settings… > and select “no proxy”.
Possible cause: This keyword is part of a MySQL full text search and it’s part of the stop words list.
Solution: See MySQL Full-Text Stopwords
Possible cause: Missing .htaccess files.
Solution:
Be sure to upload the hidden .htaccess files to the appropriate folders
Verify that mod_rewrite is activated.
Possible cause: Cake is not in the include path because mod_rewrite is not enabled/working. To confirm this, use
Solution:
Possible cause: Your database configuration is wrong.
Solution: Verify your
Possible cause:Your are running a old version of ATiM. In PHP version 5.4.19 – developers closed the ability to set session.auto_start option from user script.
Solution: You can simply comment out a lines [‘session.auto_start’ => 0,] in /lib/Cake/Model/Datasource/CakeSession.php (around line 557):
Possible cause: PHP was not compiled with multibyte string support.
Solution: Compile PHP with the flag –enable-mbstring.
Possible cause:
The problem may be a low “max_input_vars” PHP setting.
See: http://stackoverflow.com/questions/10084014/php-json-post-array-is-received-incomplete
Solution: Add max_input_vars=5000; to your php.ini
Possible cause:
The problem may be a low “max_input_vars” PHP setting.
See: http://stackoverflow.com/questions/10084014/php-json-post-array-is-received-incomplete
Solution: Add max_input_vars=5000; to your php.ini
Possible Cause: session.auto_start may not be changed at all times. It is better to turn it on from php.ini.
Solution: Go to your php.ini file and set session.auto_start = 1. Then restart your web server.
Possible cause: PDO_MYSQL driver has net been activated
Solution: Uncomment the following line in
https://php.net/function.strtotime
Possible cause: –
Solution: you need to uncomment the line
Possible cause: A lot of newer Linux servers do not have PHP Multibyte modules installed by default. A simple solution is often to install php-mbstring
Solution: