Configuration Repositories Window

The configuration repository is the storage location for the configuration data that you need to configure your applications and where organizational hierarchy information is stored, along with profile and assignment data for each element. In the Configuration Repositories window, you can create new repositories, as well as work with and synchronize existing repositories.

The Configuration Repositories Window consists of a masthead and the Configuration Repositories list.

The masthead provides a number of general links. The upper part of the masthead contains the Utility Bar, which contains four links (from left to right):

• The Console button opens the Java Web Console launch page.

• The Version button opens a window that displays version information about the Desktop Manager.

• The Log Out button logs you out of the Java Web Console, and thus the Configuration Manager, returning you to the Login page.

• The Help button opens the online help pages.

The lower section of the masthead contains the product name, the server name, and the name of the administrator currently logged in.

Configuration Repositories Table

The Configuration Repositories table consists of five columns:

• The Selection column, which contains check boxes to select repositories

  By selecting one or more repositories, the Remove, Rename, and Synchronize functions are enabled.

  ---

  Note –

  Selecting a repository disables the New button.

  ---

• Name: contains the name of the repositories

  The contents of the Name column are links. If you click on one of these links, the Configuration Repositories view is replaced by the Profile Editor page for the selected repository.

• Type: can be one of three types, LDAP, file, or hybrid

  • LDAP: an LDAP repository reads the organizational structure (users, organization, hosts, domains, and so on) of the company from an LDAP server and reads/writes the configuration settings using that same LDAP server.

  • File: a file repository reads the organizational structure of the company from the file system, and reads/writes the configuration settings using that same file system.

  • Hybrid: a hybrid repository reads the organizational structure of the company from an LDAP server, and then read/writes the configuration settings into a file system.

• Location of Organization Data: either a file, if a file repository, or LDAP URL, if an LDAP or hybrid repository. Designates the storage location of the organizational data.

• Location of Profile Data: either a file, if a file repository, or LDAP URL, if an LDAP or hybrid repository. Designates the storage location of the configuration settings. A profile is a named collection of configuration settings that is assigned to users, organizations, hosts, and domains.

You can perform the following actions within the Configuration Repositories table:

• New: creates a new configuration repository

• Remove: removes an existing configuration repository

• Rename: renames a configuration repository

• Synchronize: synchronizes configuration repositories

  This function is only enabled when one or two repositories are selected

Creating a New Configuration Repository

A configuration repository is a place where organizational hierarchy information is stored, along with profile and assignment data for each element.

Steps

1. Click the New button in the Configuration Repositories table

   The New Configuration Repository Wizard opens. The wizard is used to create a configuration repository for use with the Desktop Manager.

2. In the Repository Name field, type a name for the new configuration repository, and then click Next.

3. Select the repository type from the Repository Type list.

   The wizard can be used to configure three types of repositories:

   • LDAP: The hierarchy is taken from LDAP, and all data is stored in LDAP.

   • File-Based: The hierarchy is taken from a file, and all data is stored in directories and files.

   • Hybrid: The hierarchy is taken from LDAP, but all data is stored in directories and files.

4. Click the Next button.

5. Enter the details of the LDAP server that you want to configure for this repository.

   The Hostname and Port on which the server runs are required. You can also choose whether or not to connect to this server using SSL.

   ---

   Note –

   Note To connect to the server using SSL, the proper certifcate needs to be present in the Desktop Manager key store. This key store is located in /etc/opt/webconsole/keystore, and either the Certifcation Authority or the LDAP server certifcate needs to be present in that store. A certifcate can be added to that location by running the command:

   keytool -import -file <certificate file> -keystore /etc/opt/webconsole/keystore

   The default password for that key store is changeit. The Java Web Console must be restarted using the smcwebserver restart command for the new certifcate to be recognized by the Desktop Manager.

   ---

6. Further steps are determined by the choices made in the preceding steps. Follow the instructions provided by the wizard.

   ---

   Note –

   The directory whose URL is provided for the creation of file-based or hybrid repositories must be owned by user noaccess, group noaccess, and have permissions 755 set. This results in read and write permissions for user noaccess, and read only permissions for all others.

   ---

Removing a Configuration Repository

Steps

1. Select the check box corresponding to the configuration repository that you want to remove.

2. Click the Remove button.

   A confirmation dialog appears.

3. If you really want to remove the configuration repository, click the OK button in the confirmation dialog.

Renaming a Configuration Repository

Steps

1. Select the check box corresponding to the configuration repository that you want to rename.

2. Click the Rename button.

   A Rename dialog opens.

3. Type the new name of the configuration repository in the text field of the dialog, and click OK.

Synchronizing Configuration Repositories

With the Desktop Manager you can manage multiple back ends in parallel. This allows you to define one back end for testing and one back end for the final production. Configuration changes can now be defined and evaluated first in the test back end. Thereafter you can synchronize parts or the complete test back end with the production back end to apply the required changes quickly and safely to the production system. This method can also be used for a simple backup and restore mechanism of the production back end. The Synchronization window allows you to perform this synchronization.

Steps

1. In the Configuration Repositories window, select the repository that you want to synchronize.

   The Synchronization window opens.

2. Select the source repository from the Source Configuration Repository list.

   You can change the source repository which serves as source for the changes. This repository is not changed.

3. (Optional) You can restrict the source repository by clicking the Change button next to Source Starting Point.

   This specifies another element than the root as the source starting point for the synchronization.

   A dialog opens, which allows you to navigate to the desired organization or domain element. Once an element is selected, the new path is reflected in the Source Starting Point.

4. Select a target repository from the Target Configuration Repository list.

   You can change the target repository which serves as target for the changes. This repository is changed.

5. (Optional) You can restrict the target repository by clicking the Change button next to Target Starting Point.

   This specifies another element than the root as the target for the synchronization.

   A dialog opens, which allows you to navigate to the desired organization or domain element. Once an element is selected, the new path is reflected in the Target Starting Point.

6. Click the Compare button.

   The two trees are compared and all differences are listed in a table.

7. Select the check boxes next to the table rows containing the profiles you want to synchronize and click the Synchronize button.

   When the synchronization is finished the target repository matches the source repository regarding the selected profiles.