Combine supportBack to main support page
Combine Repository - Sharing Environments and Containers Settings
Installing a Combine Repository to Share Environments and Containers
Combine enables users to share the settings of Environments and Containers by
using a repository. This repository is referred to as a "Combine Repository"
throughout this document (to distinguish it from other repositories that can be
used in the application). To install the repository, please follow the
1. Locate the SQL script that installs the repository. The SQL script is named "Create Combine Repository.sql" and it can be found at the download section on JNetDirect' website and is also available under the Combine installation directory (for example, under the folder: C:\Program Files\JNetDirect\Combine\Repository\CombineRepository\).
2. Create the repository database on a SQL Server: Locate the SQL Server that will hold the repository database. This SQL Server can reside anywhere on the network where it can be accessed by users, and it can be SQL Server 2000 or any later version. Log on to the server and to the Master database as an administrator (either as the sa user or as a domain administrator) and run the script "Create Combine Repository.sql".
This SQL script creates a database called CombineRepository (see notes below), the schema (tables and stored procedures) for the database, as well as three SQL roles: RepositoryReaders, RepositoryChangeManager, and RepositoryAdmins. Users that belong to the RepositoryReaders user group will be able to read and use the Environments and Containers settings that are stored in the repository, however will not be able to make any changes to the settings or repository data. On the other hand, RepositoryChangeManagers and RepositoryAdmins can make changes (e.g., create or delete Environments and Containers).
3. Define users for the Combine Repository - make sure that all users that will be using the Combine repository have access to the repository database. At this point you can also set the permissions and access restriction to the repository users by adding them to the designated SQL roles described in the earlier paragraph. For example, some users can be granted access to the CombineRepository database and then be added to the RepositoryReaders group; other users can be added to the RepositoryAdmins group. For your convenience, a SQL script called "Examples - Adding users to Repository roles.sql" contains examples of how to add users to the different SQL roles and is available on JNetDirect' website as well as under the Combine installation directory (e.g., C:\Program Files\JNetDirect\Combine\Repository\CombineRepository\).
4. Instruct users to add the Combine Repository to their Combine client application. To do so, each user will open the Container Manager, right-click the MyEnvironments node, select the Add → Add Repository menu option (see image) and start the Wizard. In the Wizard, each user will be required to specify the database and SQL Server that holds the repository, as well as provide the authentication type and login to connect to the database. Then, Combine checks that each user indeed has permissions to access the repository and then adds the repository to the Container Manager on the client user-interface.
64.1: Adding a repository in the Container
a) Name of the repository database - By default, the name of the repository database is CombineRepository. However, you can open the SQL script and change the repository name to use any other database name as you so desire.
b) Comments on security - Combine is designed to be secure: Credentials, passwords, authentication type, and any other permissions or security information that relates to Containers and Environments is not stored in the repository. Each user will have to define his or her own access permissions to the Environments and Containers in their user-interface. Once provided, those settings are stored securely on the client machine, and are not stored in the repository.
c) Installing multiple repositories - By following the steps 1-4 above you can install as many repositories as you wish, so that different groups of users in your organization can see different Environments and Containers. For example, some organizations only allow production DBAs to view the Environments and Containers settings in Production, while allowing developers and test-engineers to view all settings in Development and Quality Assurance (QA). To accommodate this scenario, one repository can be used by developers and test engineers and a second repository will be installed by DBAs in Production, which will also have access to the first repository. Developers and test-engineers will add the repository containing the Dev and QA settings to their Combine user-interface, while production DBAs will add the two repositories to see all Environments and Containers across Dev, QA and Production.