Creating a shared repository

Repositories serve as a centralized place which stores QMF objects, such as queries, procedures, forms, dashboards, and reports. Each repository can have its own independent objects, security models, and users.

About this task

To add a repository to the repository storage, perform the following steps:

Procedure

  1. In the Repositories view, click Create a Shared Repository. The Create New Shared Repository wizard opens.
  2. In the Name field, specify the name for the repository.
  3. From the Repository storage field, select the repository storage that you want to use to host the new repository.
  4. Optional: To make the repository unavailable for QMF clients, select the Hide from QMF clients check box.
  5. Optional: To manage any driver-specific connections string keywords for the repository, click Advanced.
  6. Optional: To configure a PassTickets-based Single Sign-on connection between QMF and Db2 for z/OS database, click Single Sign-on.
  7. Optional: If you are using the Direct DRDA Connection to connect to the repository for the first time, you must bind Direct DRDA packages. To do so, complete the following steps:
    1. Click Bind Packages.
    2. In the Owner ID field, enter a privileged SQLID with the necessary rights for the binding process. If the value of this field is not specified, the user name from the Set User Information dialog will be used.
    3. Click Install.
  8. Optional: To specify the login name and password for the repository, click Set Use Information.
  9. Optional: In the Comment field, type a comment that describes the repository.
  10. From the Security provider list, select the security type that you want to apply to the repository. The following security types are available:
    • None: Specifies that no additional security beyond what is provided by the host database will be applied. All users will have full access to the contents of the repository.
    • Internal: Specifies that a layer of security beyond what is provided at the database level will be applied. This level of security allows you to define users and groups, and then assign them permission to access the repository. This level of security also allows you to control which data sources and workspaces a user or a group can access or view when they are connected to the repository. User and group definitions, and their assignments, are stored within the repository. Users will log on to QMF using their defined user IDs and passwords. They will be granted access to repositories, data sources, and workspaces based on the permissions that they are assigned by the QMF administrator.
    • LDAP: Specifies that a layer of security beyond what is provided at the database level will be applied. This level of security allows you to control the users and groups who are permitted access to the repository. This level of security also allows you to control which data sources and workspaces a user or a group can access or view when connected to the repository. If you choose the LDAP security option, the user identities and group affiliations are obtained from an existing LDAP server. Users will log on to QMF using their LDAP user names and passwords. They will be granted access to repositories, data sources, and workspaces based on the permissions that they are assigned by the QMF administrator.
    • Database-based: Specifies that the security settings of the host database will be used to protect the shared repository.
  11. If you want to automatically create default workspaces for users in secured repositories, select the Enable home workspaces support check box.
  12. Click Next.
  13. Depending on the security type that you selected in previous step, one of the following wizard pages opens:
    • If you selected the Database-based option, the DB security provider options page opens. On the page, specify whether you want to import the list of database users from the QMF Catalog table that is stored in the database and click Next.
    • If you selected the Internal option, the Internal security provider options page opens. On the page, specify the user name and password that will identify the QMF administrator account. The QMF administrator account is the account that is used to create additional administrative accounts, as well as apply security permission levels to different users and groups. Click Next.
    • If you selected the LDAP option, the LDAP security provider options page opens. On the page, specify one or more values for the LDAP fields. These fields are used to obtain all LDAP users and groups. You must specify an existing LDAP group in the directory that represents the QMF administrator account. All LDAP accounts that belong to this group will have administrator privileges and can create additional administrative accounts, as well as apply security permission levels to different users and groups. Click Next.
  14. On the Define advanced connection parameters page, in the Repository Cache area, select the Enabled check box to enable repository cache validation. Use one of the pre-defined modes or select the Use custom cache settings check box to specify a custom cache validation mode.

    The following pre-defined modes are available:

    Low relevance-High performance
    Cache validation is not performed.
    Balanced relevance/performance
    Cache validation is performed every five minutes.
    High relevance-Low performance
    Cache validation is performed every minute.
  15. Click Finish.