Transferring pureQuery data about applications into repositories with the workbench

You can transfer pureQuery metadata from a Java project directly into another repository or into a file. You can import the metadata into another repository from the file. The pureQuery metadata can help you to locate underperforming SQL statements in the pureQuery application.
The metadata can identify the source file in which a problem SQL statement appears, and even identify the line number where the statement is located in that file. The metadata can be stored in a repository used by pureQuery runtime.

If you are using IBM® Optim™ Performance Manager Version 4.1 to monitor the performance of an application that uses IBM InfoSphere™ Optim pureQuery Runtime, and the code for that application is in IBM Data Studio, you can transfer metadata about that application into a repository that InfoSphere Optim Performance Manager is using.

About this task

You can transfer the pureQuery metadata directly into the repository, or you can save the metadata to a file, and then import the metadata to the repository with the ManageRepository utility.

If you want to transfer the metadata directly into a repository database, you must meet the following prerequisites:

Procedure

To transfer metadata into a repository:

  1. In the Project Explorer, right-click the Java project that contains the SQL statements.
  2. Select Data Access Development > Transfer Metadata. The Transfer window opens.
  3. Specify whether to save the metadata directly in a repository or whether to save it to a file.
    • If you want to save the metadata directly in a repository, select a repository and then follow one of the steps:
      • Specify a runtime group name that is used to store the metadata.

        You either select a name from the explorer or enter a name in Runtime group name. If you select a name, the Transfer window populates the field with that name.

      • Specify the name of the runtime group version.

        When transferring metadata to a repository, the version name can be a existing runtime group version name or a new version name. If the version is an existing name the new metadata overwrites the existing metadata. If the version name is a new name, a new version is created for the runtime group.

        If the version is an active version, the metadata is not transferred.

    • If you want to save the metadata in a file, browse to the directory in which you want to save the file and specify a file name.
  4. Click OK.

What to do next

If you saved the metadata to a file, you can import the metadata into a repository database by using the ManageRepository utility.

After the metadata is in the repository database, you can monitor the SQL statements with IBM Optim Performance Manager for DB2 for Linux, UNIX, and Windows or IBM Optim Performance Manager Extended Edition for DB2 for Linux, UNIX, and Windows.


Feedback