1. Stop CodeBeamer on the source host. To avoid data loss, it is very important that all CodeBeamer related java (or javaw) and mysqld processes are stopped.
2. Make a zip (or tar) file of the following directories located under /<install_dir>/repository on the source host: /mysql/data, /docs, /svn, and /acl.svn (Note: /svn and /acl.svn only exist if there is at least one managed Subversion repository)
3. Copy the zip file to the target host.
4. Install CodeBeamer on the target host but do not start CodeBeamer. If CodeBeamer is already running, stop it completely as indicated in step 1 before proceeding.
5. Unpack the zip file created in step 2 to the /<install_dir>/repository directory on the target host. This will overwrite the initial CodeBeamer data files with the data files from the source installation. It is very important that the corresponding directories and files are appropriately overwritten by the contents of the zip file.
6. Start CodeBeamer on the target host.
7. You will need to acquire a new license key for the target host before you will be able to open any projects. To obtain a key, send an email to support@intland.com with your host ID (found on the CodeBeamer About page). 

All CodeBeamer data from the source host should now be accessible on the target host with one exception; to provide source code analysis., CodeBeamer creates a workspace from source code checked out from the source code repository (e.g., Subversion, CVS). This workspace was not copied in the procedure above, however, it will be recreated and the related analysis metrics updated upon the next nightly build.

아래와 같은 Topic으로 정리 하고자 합니다

• Application Lifecycle Ecosystem
• Application Engineering
• Static Analysis and Error Detection
• Security Testing
• Software Build Management
• Virtual Computing
• Python

회사 자체 서버에 Blog 시스템 설치 되면 전체 ”DEL” 될 수 있습니다