test

Sun Desktop Manager 1.0 Administration Guide

ProcedureCreating 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.