Restoring from a backup

With the databases, the persist folders, and some configuration files, you can recover your IBM® Rational® Asset Manager repository and server configuration.

Before you begin

Create a backup of your repository, as described in Creating a backup of a Rational Asset Manager repository.

You must have the following permissions:
  • Administrative access to the application server
  • Administrative access to the database server
  • Access to the directories where you want to store the asset files (the Persist folder) and, optionally, the search index files (the Index folder)

Procedure

  1. From your backups, restore both the asset and lifecycle databases to your database server.
  2. From your backups, restore the Persist disk storage folder. If you cannot restore the Persist folder to the same path, you can change the location of the Persist folder.
  3. Optional: From your backups, restore the Index disk storage folder. If you are using an IBM WebSphere® Application Server cluster, you must restore the Index folder for each node. If you restore the index folders, Rational Asset Manager can rebuild the search index faster.
  4. From your backups, restore the configuration for your application server:
    • For WebSphere Application Server:
      1. Run the WebSphere Application Server restoreConfig script, specifying the backup configuration file that you made.
        • The restoreConfig script is in the websphere_install_directory/bin directory.
        • For example, on AIX®, the command might be restoreConfig.sh WebSphereConfig_2010_07_01.zip
      2. If you are using a WebSphere Application Server cluster, run the restoreConfig script for every node on your cluster.

      The restoreConfig command can completely restore the configuration and deployed applications for an entire node. For more information about the restoreConfig command, see the WebSphere Application Server documentation.

    • For Tomcat:
      1. From your backups, restore the startup files for the 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
        If necessary, modify the variables in the startup files to point to the following locations:
        • The /shared/lib/ Java™ libraries
        • The JDBC .jar files for your database server
        • The location of the IBM Rational Team Concert™ files (JAZZ_INSTALL_DIR)
        For more information, see Deploying the Rational Asset Manager server applications on Tomcat 6 or 7 and Deploying the included Rational Team Concert server application on Tomcat.

      2. From your backups, restore the server.xml files: tomcat_install_directory/conf/server.xml and tomcat_for_rtc_install_directory/conf/server.xml

        If necessary, modify the <resource name="jdbc/RAM_con"> tag with the correct location and authorization for the database for Rational Asset Manager.

        For the server for Rational Team Concert, check the <connector> tag that contains the secure port. You might need to update that tag with the location and authorization for the security certificate for the server.

      3. From your backups, restore the user configuration file: tomcat_install_directory/conf/tomcat-users.xml and tomcat_for_rtc_install_directory/conf/tomcat-users.xml
      4. From your backups, restore the database connection configuration file for Rational Team Concert: rtc_install_dir/jazz/server/conf/ramjazz/teamserver.properties
        Note: If you are restoring a database from a release earlier than Rational Asset Manager 7.5.1, you might receive an error that the URL http://host:port/jazz is not valid. You can use the suggested value http://host:port/ramjazz to the update the URL.

        If necessary, modify the connection properties for the database server.

  5. Start the application servers.
  6. If it is not already started, start the Rational Asset Manager web application.
    • 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 Start.
    • 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 Start.
  7. If you cannot restore the Persist and Index folders to the same location, with the same path to the directories, you can change the location of the folders.
    • For WebSphere Application Server:
      1. Start the application server.
      2. In a web browser, open the server setup application. By default, the application is at http://host_name:port/ram.setup/. The Summary page opens.
      3. In the Repository Settings section, find the Disk Storage Settings property and click Edit.
      4. On the Disk Storage Settings page, update the location of the Persist folder.
      5. Update the location of the Index folder for each node.
      6. Click Next.
      7. From the server setup application, stop and then restart the application server by clicking Tools > Restart the server.
    • For Tomcat:
      1. Start the application server.
      2. In a web browser, open the Rational Asset Manager web application.
      3. Log in to the web application as a repository administrator.
      4. Click Applications.
      5. Click Configuration.
      6. In the Disk Storage section, update the locations of the Persist and Index folders to reflect the restored directories.
      7. Click Save.
      8. Using the Tomcat /manager application, stop and restart the Rational Asset Manager web application.

Results

Your repository is restored from the point of your backup. Depending on the size of your repository and whether you restored the Index folders, it might take several minutes for the search index to rebuild.
Feedback