Difference between revisions of "Migrating an iPortalDoc from IPBRICK 5.x to 6"
Line 1: | Line 1: | ||
− | + | = Before Migrating: = | |
- You need to have IPBrick configurations migrated to version 6.0. Please send the last configuration file of IPBrick server v5.x to support@ipbrick.com and wait for the reply with a configurations file ready to be uploaded to version 6.0. | - You need to have IPBrick configurations migrated to version 6.0. Please send the last configuration file of IPBrick server v5.x to support@ipbrick.com and wait for the reply with a configurations file ready to be uploaded to version 6.0. | ||
Line 28: | Line 28: | ||
iPortalDoc is compatible with Google Chrome and Mozilla Firefox. | iPortalDoc is compatible with Google Chrome and Mozilla Firefox. | ||
− | + | = After the installation of IPBrick version 6.0: = | |
- Install iPortalDoc v4.2 [http://eshop.ipbrick.com/eshop/software_info.php?cPath=3_40_85&products_id=694] | - Install iPortalDoc v4.2 [http://eshop.ipbrick.com/eshop/software_info.php?cPath=3_40_85&products_id=694] | ||
Line 61: | Line 61: | ||
− | + | = Useful links: = | |
IPContacts v4.3 update to install in an IPBrick v5 [http://downloads3.ipbrick.com/ipbrick-contacts_4.3_all_IPBrick-v5.deb] | IPContacts v4.3 update to install in an IPBrick v5 [http://downloads3.ipbrick.com/ipbrick-contacts_4.3_all_IPBrick-v5.deb] | ||
Line 86: | Line 86: | ||
md5sum: 5d071c63f9a0a9a23802682a45f9e9fa | md5sum: 5d071c63f9a0a9a23802682a45f9e9fa | ||
+ | |||
+ | = Known Issues = | ||
+ | |||
+ | == Licence Error == | ||
+ | Problem: After restoring /home1/_dbdoc and the database dump, when you try to access IPortalDoc web interface you get an error in IPortalDoc homepage. | ||
+ | |||
+ | Solution: remove the old licence files, delete files: | ||
+ | * /home1/_dbdoc/ficheiros/erro_acesso1.php | ||
+ | * /home1/_dbdoc/ficheiros/erro_acesso2.php | ||
+ | |||
+ | Example: | ||
+ | root@ipbrick:~# rm /home1/_dbdoc/ficheiros/erro_acesso1.php | ||
+ | root@ipbrick:~# rm /home1/_dbdoc/ficheiros/erro_acesso2.php | ||
+ | |||
+ | Afterwards you can access to IPortalDoc web interface, you are now prompted to insert a new valid licence. Please refer to IPortalDoc Installation manual, licence activation procedure. | ||
+ | |||
+ | == Other Issues == | ||
+ | If you get different error messages, please report to support@iportaldoc.com | ||
+ | |||
+ | |||
+ | In case of the foll |
Latest revision as of 12:02, 20 June 2016
Contents
Before Migrating:
- You need to have IPBrick configurations migrated to version 6.0. Please send the last configuration file of IPBrick server v5.x to support@ipbrick.com and wait for the reply with a configurations file ready to be uploaded to version 6.0.
- Check iPortalDoc version: iPortalDoc need to be in version 4.2.1 (or greater) before the migration to an IPBrick version 6.0 or greater.
iPortalDoc update 1 for IPbrick versions 5.x is available here: [1]
Note: If iPortalDoc is in version 4.2.1 you don't need to apply any update now.
- Check IPBRICK Contacts version: Contacts need to be in version 4.3 before the migration to an IPBrick version 6.0.
Note: If Contacts is in version 4.4 or greater you don't need to apply any update now.
- Backup the DB (command [2])
Eg:
./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path
- If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data
Eg:
./ipbrickdb_ipb5 --dump --dbname dbdoc_leve --file dump_file_path
NOTE: Check your browsers version if you are using Internet Explorer. iPortalDoc is fully compatible with Internet Explorer version 9 or greater.
iPortalDoc is compatible with Google Chrome and Mozilla Firefox.
After the installation of IPBrick version 6.0:
- Install iPortalDoc v4.2 [3]
- Install update 1 [4]
After the installation of IPBrick v6.0 and iPortalDoc v4.2.1 the next step will be to replace IPBrick configurations file that you have previous received from our support. Please upload that configrations file and replace those configurations.
If there are any updates that need to be installed in order to have a successful configuration replacement, you will be presented with that information. Follow the instructions given and install all the necessary updates.
- Restore the dbdoc DB [5]
Eg:
./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql
- If there is an iPortalDoc Light, restore the DB
Eg:
./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_leve --file file_com_dump
- Rebuild iPortalDoc workflow accounts:
a) Definitions Menu -> Configuration Interface b) Poplist on the right (Menu) -> Workflows c) Click on the Rebuild button
- Rebuild share "Access" and the account of Associated Emails to Documents, of iPortalDoc:
a) Access Share: Definitions -> Configuration Interface-> Build Global FS b) Emails associated to documents: Definitions -> Configuration Interface -> Build Global mailFS (This task is scheduled to be executed at midnight);
Useful links:
IPContacts v4.3 update to install in an IPBrick v5 [6]
IPContacts v4.4 update to install in an IPBrick v6.0 [7]
IPContacts v4.5 update to install in an IPBrick v6.0 [8]
IPContacts v4.6 update to install in an IPBrick v6.0 [9]
IPContacts v4.7 update to install in an IPBrick v6.0 [10]
IPContacts v4.8 update to install in an IPBrick v6.0 [11]
Script ipbrickdb_ipb5: [12]
md5sum: 7339475f75c10cd7b54347f0cf6a5361
Script ipbrickdb_ipb6: [13]
md5sum: 5d071c63f9a0a9a23802682a45f9e9fa
Known Issues
Licence Error
Problem: After restoring /home1/_dbdoc and the database dump, when you try to access IPortalDoc web interface you get an error in IPortalDoc homepage.
Solution: remove the old licence files, delete files:
- /home1/_dbdoc/ficheiros/erro_acesso1.php
- /home1/_dbdoc/ficheiros/erro_acesso2.php
Example:
root@ipbrick:~# rm /home1/_dbdoc/ficheiros/erro_acesso1.php root@ipbrick:~# rm /home1/_dbdoc/ficheiros/erro_acesso2.php
Afterwards you can access to IPortalDoc web interface, you are now prompted to insert a new valid licence. Please refer to IPortalDoc Installation manual, licence activation procedure.
Other Issues
If you get different error messages, please report to support@iportaldoc.com
In case of the foll