Contributions
Re: Migrating CC to a new server
Indeed there is. We cover the process of backup, restore, and migration in the manual here: http://codecollaborator.smartbear.com/docs/manual/6.0/index.html?server_backup.html Our internal backup tool creates a representation of the database and file cache that can be moved between servers. To move between devices: (1) Use the internal backup tool to generate a backup. (2) Install a copy of Code Collaborator on the new device. Be sure to use the same version. (3) Restore from that backup on the new device per the instructions linked above. Note that, if you have a lot of file content, it will take quite a while to generate the backup. This is expected.1.5KViews0likes0CommentsRe: How can I figure out what my LDAP settings should be?
Most 6.0 releases of Code Collaborator will provide a very non-intuitive error message if LDAP settings are not correct: Name jdbc is not bound in this Context If this error appears in your logs or on screen, you should probably follow the steps above.5.5KViews0likes0CommentsRe: Updating Perforce changelist numbers?
Ken, I just verified that this link is working from a non-smartbear location - is it still failing for you? http://collab.smartbear.com/docs/manual/6.0/renumber-collab-changes.py If so, please e-mail support@smartbear.com and hopefully they can get the website team to resolve the issue. I'm attaching a .zip file that contains the script in question as of today.2.7KViews0likes0CommentsRe: Updating Perforce changelist numbers?
Per my coworker Will: We ship a python script meant to be run as a cron job that will update the changelist ID's in the reviews. http://collab.smartbear.com/docs/manual/6.0/renumber-collab-changes.py With a few modifications to the CONFIG hash at the top you'll probably be in business. Hope that helps!2.7KViews0likes0CommentsRe: Deploying Code Collaborator Server to a URL other than the base
The above assumed that Code Collaborator Server was initially in a 'stopped' state. Please execute 'ccollab_server stop' before following the above instructions - otherwise, there is a chance that tomcat will attempt to redeploy the application before you've completed your changes.1.8KViews0likes0CommentsDeploying Code Collaborator Server to a URL other than the base
Disclaimer: Code Collaborator Server 6 is intended to be deployed as a stand-alone application with its own dedicated sub-domain. Deploying in any other configuration, including the configuration described below, is unsupported. The following steps move Code Collaborator from the root of a dedicated subdomain (ie. http://your.ccollab.domain/) to a top-level URI located within that domain (http://your.ccollab.domain/your-desired-application-name/.) If you haven't already, install, configure, and initialize the database of code collaborator server. Within the ccollab_server directory: 1. Copy or link tomcat/conf/Catalina/localhost/ROOT.xml to tomcat/conf/Catalina/localhost/context.xml.default. 2. Rename tomcat/webapps/ROOT/ to tomcat/webapps/your-desired-application-name/. 3. Restart ccollab_server. Your Code Collaborator server should be accessible at http://your.ccollab.domain/your-desired-application-name/ instead of http://your.ccollab.domain/. Due to assumptions made in the upgrade process, you should follow these instructions again immediately after any upgrades to Code Collaborator Server. Note: Verified with Code Collaborator server v.6.1.6102 - linux.9.5KViews0likes1Comment