Restoring Access to Projects

You can restore access to an ALM project or template project that is not in your current Projects list in Site Administration. For example, you may want to access a project from another server. After you restore access to a project, it is added to the Projects list in Site Administration.

Note:  

  • Before restoring the project, make sure that the database where the project resides exists in the DB Servers tab in Site Administration on your ALM server. The ALM server needs to access the contents of the restored project from the project's database. For more information, see Upgrading Projects to a New Version.

  • When restoring a project, you should select the dbid.xml file located in the project repository. This ensures that the project retains its original ID. If a project does not have its original ID, the following cross project features may not function properly: cross project customization, importing and synchronizing libraries, and cross project graphs.

  • If you are restoring your project from a different directory, or if you renamed your schema or restored it to a different database, you must update the dbid.xml file accordingly. For details, see Updating the dbid.xml file.

  • You must first restore and upgrade any template projects before restoring and upgrading other projects. If the template project and its linked projects are in different databases, ensure that the template project’s database is accessible when restoring any linked projects.

  1. In Site Administration, click the Site Projects tab.

  2. Click the Restore Project or Restore Template button . The Restore Project dialog box opens.

  3. To locate the file that includes the project that you want to restore, click the browse button to the right of the dbid.xml file location box. The Open File dialog box opens.

  4. Locate the file. For information on the location of the dbid.xml file, see Understanding the Project Structure.

  5. Select the dbid.xml file and click Open. The Restore Project dialog box opens and displays the database type, name, server, and the directory path of the project.

  6. In the Restore Into Domain box, select the domain in which you want the restored project to be located.

  7. Click Restore.

  8. If your database server does not have the text search feature enabled, a message box opens. You can enable the text search feature before or after this process completes.

    • Click Yes to continue this process. After the process completes, you can enable the text search feature.

    • Click No to stop this process. Enable the text search feature and then restart the process.

  9. When the restore process completes, click OK.

  10. Click Close to close the Restore Project dialog box and view the restored project in the Projects list.

If you are restoring your project from a different directory, or if you renamed your schema or restored it to a different database, for example, as part of the upgrade process, you must update the following values:

  • DB_NAME. Update to the database schema name as it appears in the database server.

  • DB_CONNSTR_FORMAT. Update to the value of the empty project created in ALM. See the note for details.

  • DBSERVER_NAME. This is the name of the database server as defined in the DB Servers tab in Site Administration.

  • DB_USER_PASS. Update if the encrypted passphrase differs between the previous installation and ALM.

  • PHYSICAL_DIRECTORY. Update to the new location of the project repository. It must contain a backslash (\) at the end of the path.

Note:  

  • In order to identify the values of DB_CONNSTR_FORMAT and DB_USER_PASS, it is recommended to create a new, empty project in ALM 15.5 Site Administration, open the project's dbid.xml file, and copy these values. You can later delete the empty project.

  • Make sure not to copy/paste or change the value for PR_SMART_REPOSITORY_ENABLED.

  • If you are restoring LAB_PROJECT or LoadRunner Enterprise projects as part of the upgrade process, make sure not to edit the PROJECT_UID value. You must restore these projects with their original PROJECT_UID value in order to maintain the links between LAB_PROJECT and its associated LoadRunner Enterprise projects, important for shared data, such as timeslots, runs, and so on.

Back to top