Trying Out v5.0 - Server Installation Options
The beta release for Code Collaborator v5.0 is now available (check out the highlights of the new features or browse the complete list).
If you are not currently using Code Collaborator then trying out v5.0 is easy: download it from the web site and install it. No muss, no fuss.
If you are currently using Code Collaborator then you have three options for how to install the Code Collaborator v5.0 server software:
- Install the v5.0 Code Collaborator server software into its own directory and start from scratch. This is easy enough to do, but you won't have access to all your existing review and user data, so it's not practical for most situations.
- Upgrade your existing Code Collaborator server installation. Also easy to do, but if you decide the v5.0 beta is not what you want, you will have to switch back to the older version, which will involve re-installing and then restoring a backup.
- Make a copy of your existing Code Collaborator server installation and then upgrade the copy. This allows you to continue running the old version of Code Collaborator in parallel with v5.0.
Option 1 is the easiest: just download and install the Code Collaborator v5.0 server software and you are ready to go. If you are installing onto the same machine as your existing Code Collaborator server software, be sure to specify a different directory, port number, and database instance.
Option 2 is almost as easy: do a complete backup of your existing Code Collaborator server. That's the most important step! :-) Then download and install the Code Collaborator v5.0 server software and when prompted, select the directory that contains your existing Code Collaborator server software. This will cause the installer to upgrade your existing installation.
Option 3 is not difficult, but requires an additional step. Do a complete backup of your existing Code Collaborator server - as with option 2, this is the most important step! After the backup finishes, install the exact same build of the Code Collaborator server software that you are currently using, but if you are installing onto the same machine then install it into a different directory so that the installer will not upgrade your current installation. You will also need to specify a different port number and database instance.
For example, if you are currently running v4.0.854, then install build 854 of v4.0 (older versions of the installer are available here). After the installer finishes it will display a web page in your default browser. That web page will have a button for creating the Code Collaborator database tables - do not push that button! You don't want those tables to be created because you are about to restore from your existing database.
Restore the backup that you just created to the new installation of Code Collaborator. Then run the installer for v5.0 and when prompted select the directory that contains the Code Collaborator server that you just installed. This will cause the installer to upgrade that installation.
One final note: if you chose Option 1 or Option 3 then you will end up with two instances of the Code Collaborator server running: one for your older version and one that is running v5.0. If you are running both instances on the same machine and if the operating system on that machine is Windows, then there is one additional step. The Code Collaborator server installer for Windows always uses the same Windows service name: ccollab-server. This means that after you install a second instance of the Code Collaborator server on a Windows system, the Windows service named ccollab-server points to the new installation. The original installation no longer has a Windows service entry and is therefore no longer running.
This problem is easy to fix. In a command window set the working directory to the original installation of the Code Collaborator server software. Then enter this command:
ccollab-server /install <service-name>
You can specify anything you want for <service-name> except for ccollab-server. This will create a new Windows service with its own name for your existing Code Collaborator server installation.