Tags:
not added yet
Upgrading from older versions - advanced
The old codeBeamer installation will be referred as OLD-CB, the new one as NEW-CB throughout this document.
Please note: The upgrade procedure transfers your installation instance data from the old version to the new version. Migration from the new version back to the old version is NOT supported.
When you upgrade mysql to a newer version, do not forget to do the followings:
You can find more information on this webpage: http://dev.mysql.com/doc/refman/5.7/en/mysql-upgrade.html Table of Contents
Step 1. Install NEW-CBInstall NEW-CB into a new directory (the installation must not be executed into an existing directory) and do not start the CB server at the end of the installation. Step 2. Copy repository dataCopy the following directories and files from OLD-CB/repository to NEW-CB/repository: (git, hg, src, svn, and acl.svn might not exist, depending on your RDBMS and SCM):
Windows:cd OLD-CB\repository xcopy docs NEW-CB\repository\docs\ /EH xcopy git NEW-CB\repository\git\ /EH xcopy hg NEW-CB\repository\hg\ /EH xcopy src NEW-CB\repository\src\ /EH xcopy svn NEW-CB\repository\svn\ /EH copy acl.svn NEW-CB\repository\ Unix:$ cd OLD-CB/repository $ find acl.svn docs git hg src svn | cpio -updv NEW-CB/repositoryIf you have customized your OLD-CB/repository structure, e.g. mounted external volumes as docs and/or git, hg or svn, then the above procedure might not be appropriate, and, for the given example, you would better unmount the external volumes from OLD-CB/repository and mount to NEW-CB/repository. Step 3. Database ConfigurationWhen you upgrade from CB 9.3 or newer, copy configuration.properties file from from OLD-CB/config to NEW-CB/config. In case you upgrade from CB 9.2 or older copy general.xml instead from OLD-CB/tomcat/webapps/cb/WEB-INF/classes/general.xml to NEW-CB/tomcat/webapps/cb/WEB-INF/classes/general.xml, MySQL
OraclePlease refer to Because this privilege was not required in older releases, it is typically missing and your database administrator has to grant it manually. GRANT CREATE VIEW to <codeBeamer schema user>
DerbyNo upgrade is supported for Apache Derby databases! Step 4. Port ConfigurationIf you had configured an Apache server in front of OLD-CB (Tomcat) (via mod_jk), you need to enable the NEW-CB Tomcat AJP 1.3 Connector (typically on port 8009) again. <Connector port="8009" enableLookups="false" redirectPort="8443" protocol="AJP/1.3" URIEncoding="UTF-8" ></Connector> If you had used a different port for this connection, please adjust the port number as well. Step 5. Runtime ParametersIf you had customised OLD-CB runtime variables, e.g. special JVM, HEAPSIZE, etc., then you should copy these settings from the OLD_CB start script to the NEW-CB start script.
cbservice codebeamer codebeamer Step 6. StartStart the NEW-CB server. The first time the codeBeamer server is started, the database schema will be upgraded to version NEW-CB. Step 7. Get and install a new licensePlease check whether your available license is compatible with target codeBeamer release. Please read the "Getting Licenses" section in
Step 8. Logo ConfigurationTo restore your custom logo and welcome text manually, you need to Login as system administrator and re-upload your logo file. Step 9. Clearing Browser CachesBecause browsers cache javascript files, the cached javascript files must be re-loaded. We strongly recommend clearing the browsers' cache and then re-starting the browser. Step 10. Starting Re-indexingAfter upgrading, the index database is empty thus searching will not provide any matching. Starting with codeBeamer 6.1, re-indexing is automatic after a completed upgrade. Step 11. Apache SVN configuration (Optional)acl.svn and .htaccess files have been moved under the <CB install directory>/repository/access/ directory, please check the configuration guide for more details |
Fast Links
codeBeamer Overview codeBeamer Knowledge Base Services by Intland Software |