Moving KBPublisher to a new server is a relatively simple process, provided you copy all files and retain the same file structure.
To do so you need to:
If you wish, you can rename your database and/or move your folders around, but the instructions below do not cover that.
Before you start
The database contains your articles, your users and your settings and while you can reinstall pretty much everything else (except uploaded files) by re-installing KBPublisher, no-one can fix a database that isn't there.
Backup the directories and copy them across to the new server. Keep the same directory structure.
The directories you need to copy are:
Local files are files which were already on the server and which you then linked to the knowledgebase. To add local files you would have added them by either clicking on the Files menu and choosing Add Local File (these files were already on the server and you effectively just linked them to the knowledgebase), or by setting directory rules by clicking on the Files menu, then assigning directories in the Directory Rules tab.
If you haven't done either of these things then you don't have any local files to copy and can ignore this part.
UPDATE kbp_file_entry SET directory = replace(directory, '/home/old/file', '/home/new/file');
Install any third-party tools
Update the config file
Now that everything is on the server you need to update the configuration file to point to the new server.
You should now be able to log on to KBPublisher.
Set up scheduling on the new server
Scheduling and alerts are cron jobs and must be set up on the new server.
That's it. You're done. Your knowledgebase is on the new server and should be working exactly like the old one.
Licensing and right to run
Please note that before you run KBPublisher on the new server you should completely remove it from the old one. Failure to do so may lead to a licences violation.
Your purchase of a KBPublisher license grants you the right to make use of a single instance of the software. You may temporarily install a second instance of KBPublisher on an internal development server for testing and deployment planning, but only one instance of KBPublisher shall be in operation (available for access to your admin users or end users).