Creating a backup of a Rational Asset Manager repository

To create a backup of your repository:

1. Create a backup of your installation directory with the application files and documentation from the installation media. If you used IBM Installation Manager, this directory is the install_package_location/ram/ folder. You do not need these files for most backups; however, if the backup and restore do not go as planned and you need to completely re-install and configure the applications, you need the files.
2. Log in to the Rational Asset Manager web client as an administrator.
3. Click Administration > Configuration.
4. In the Disk Storage section, note the location of the Persist and Index folders. If you are on an IBM WebSphere® Application Server cluster, there is an Index folder for every node.
5. Stop the Rational Asset Manager application. Stopping the application helps prevent data corruption.
   • For WebSphere Application Server:
     1. Log in to the WebSphere Application Server administrative console.
     2. Click Applications > Application types > WebSphere enterprise applications.
     3. Select the RAM1WebApplication.ear application and click Stop.
   • For Tomcat:
     1. Log in to the Manager application.
     2. In the Applications section, find the Rational Asset Manager application. Most likely, it is /ram.
     3. In the Commands list for the application, click Stop.
   The Rational Asset Manager application is now offline.
6. Stop the application servers. Your other applications are now offline.
7. On the computer where the database is located, create a backup of the database for Rational Asset Manager, which is the database for assets. For instructions, see the documentation for your database application.
8. Create a backup of the database for IBM Rational Team Concert™, which is the database for lifecycles. For instructions, see the documentation for your database application.
9. Create a backup of the Persist folder that you noted in step 4.
10. Optional: Create a backup of the Index folder for every node. Rational Asset Manager can completely rebuild the Index folder after you restore the repository. However, for large repositories, if you restore the Index folders, the search index rebuilds faster.
11. Create a backup of your configuration files:
    • For WebSphere Application Server:
      • Run the backupConfig script for WebSphere Application Server. This script is located in the websphere_install_directory/bin directory. Because security is enabled for your server, run the script with the -user administrator_username and -password administrator_password options, and use the user name and password of the server administrator. By default, running the script creates a .zip file of your configuration in the websphere_install_directory/bin directory.
      • If you are using a WebSphere Application Server Network Deployment cluster, run the backupConfig script for every node on your cluster.

      For more information about the backupConfig script, see the WebSphere Application Server documentation.

    • For Tomcat, create copies of the following files:
      • The start-up scripts for your Tomcat servers:
        • On Windows, tomcat_install_directory\bin\startup.bat and tomcat_for_rtc_install_directory\bin\startup.bat.
        • On Linux, AIX®, or Linux for zSeries, tomcat_install_directory/bin/startup.sh and tomcat_for_rtc_install_directory/bin/startup.sh
      • The server.xml files: tomcat_install_directory/conf/server.xml and tomcat_for_rtc_install_directory/conf/server.xml
      • The user security configuration file: tomcat_install_directory/conf/tomcat-users.xml and tomcat_for_rtc_install_directory/conf/tomcat-users.xml
      • The database connection configuration file for Rational Team Concert: rtc_install_dir/jazz/server/conf/ramjazz/teamserver.properties

        For Rational Asset Manager releases earlier than 7.5.1, the database connection configuration for Rational Team Concert is: rtc_install_dir/jazz/server/conf/jazz/teamserver.properties