Adding repositories to the repository storage tables
You can add repositories to the repository storage tables. Repositories serve as a centralized place in which an aggregation of data, such as queries, procedures, forms, dashboards, and, reports are developed for a specific set of data sources. Each repository that you create can have its own independent objects, security models, and users.
Before you begin
Make sure the Repository view is open in the workbench. To open the Repository view select . The Repositories tab opens in the workbench.
About this task
The information in this topic describes how to add a repository within the repository storage tables on a database.
As part of the procedure for adding repositories, you define the permissions for accessing the repositories. These permissions determine which users or user groups have access to the repositories.
To add a repository to the repository storage table, perform the following steps:
- In the Repositories view right-click the repository storage to which you want to add a repository. Select from the pop-up menu. The Create New Shared Repository wizard opens.
- Specify the name that will be used to identify the repository in the Name field.
- Optionally, type a comment that describes the repository in the Comment field. This comment will display with the properties for the repository.
- Select the type
of security that will be applied to the repository. From the Security
provider drop-down list select one of the following:
- None: Specifies that no additional security beyond what is provided by the database that is hosting the repository 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 objects a user or 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 for Workstation or QMF for WebSphere® using their defined user IDs and passwords. They will be granted access to a repository or to repository objects 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 objects a user or 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 for Workstation or QMF for WebSphere using their LDAP user names and passwords. They will be granted access to a repository or to repository objects 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.
- If you selected either Internal or LDAP security,
click Next. One of the following wizard pages
- If you selected Internal security, the Internal security provider options page opens. 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.
- If you selected LDAP security, the LDAP security provider options page opens. Specify one or more values for the LDAP fields. These fields are used to obtain all LDAP users and groups. You will be asked to specify an existing LDAP group in your directory that represents the QMF administrator account. All LDAP accounts that belong to this group will have QMF administrator privileges and can create additional administrative accounts, as well as apply security permission levels to different users and groups.
- Click Finish.
You have created and added to the list of available repositories that are contained within the shared repository storage.
What to do next
The next step is to configure data source information in the repository.
If you have applied Internal security to the repository you can choose to create the users and groups that can access the repository at this point, or after you have configured data source information. If you assigned LDAP security to the repository, all the users and groups that were obtained from your LDAP server can access the repository. For both types of secured repositories, Internal and LDAP, you assign users and groups permission to access repository objects on an ongoing basis as the needs of your environment dictate or change.
If you are just creating the repository, you must populate the repository with data source information before you can specify the level of access a user or group will have to the objects that are in the repository.