The codeBeamer installation kit contains all components (database, web-server) required for evaluation.
For additional information please look at Installing.
Windows and Linux on 64-bit x86 architectures.
Windows 2016 Server starting from codeBeamer 8.2.1
Windows 2012 Server
Windows 2008 Server
Windows 2003 Server
Red Hat Enterprise (RHEL)
SuSE Enterprise Linux Server (SLES)
Ubuntu for long-term deployments (LTS)
It might be necessary to upgrade supported Git, Mercurial and Subversion versions from additional packages.
MySQL, InnoDB engine is required
Derby (Java DB) shipped with codeBeamer for demo purposes, it is not supported for production use.
Client Web Browsers
Microsoft Internet Explorer
The settings below are required:
Cookies must be enabled
SSD disk with RAID is strongly recommended for best performance and reliability. 30-50 GB for database storage and 100-500 GB for documents, attachments and SCM repositories. The size of the required storage strongly depends on the size of documents, attachments and SCM repositories managed by codeBeamer.
CPU / Memory
Multicore (x86 architecture) Intel Xeon® Platinum CPU-2.3 GHz frequency per Core. Please also check our the Performance test results
Active/concurrent Users refers to the number of users which are actively (concurrently) working in codeBeamer at a given time, e.g. creating, editing Work Items, adding Comments and/or other artefacts.
The number of registered users (accounts) may be a much higher number than the number if concurrent users, so this guidance should be used to refer to the total number of expected active (concurrent) users.
Failover, Clustering and Mirroring options
For failover, clustering and mirroring there are different options depending your IT landscape. Intland has no recommendation for any system, however we see that some customers with Linux operating systems prefer DRDB (free open source software). DRDB can be also combined with Heartbeat for failover and data mirroring services together.