test

Sun Desktop Manager 1.0 Installation Guide

Chapter 2 Management Application Installation

This chapter provides instructions about how to install the server-side components of the Sun Desktop Manager.

Sun Desktop Manager

The Desktop Manager provides a web-based administration tool that runs on the Java Web Console. This user interface allows an administrator to traverse the hierarchy of an organization to define policies for desktop applications. These policies can be defined for each item in the hierarchy, for example, for organizations, roles, users, domains and hosts. The Desktop Manager uses several configuration templates to display settings that are specific to different desktop applications such as Gnome, Mozilla, StarOffice, and Evolution.

ProcedureInstallation

Before You Begin

The Desktop Manager requires an installed Java Web Console version 2.2.5 or higher. Please ensure that a valid version is installed on your system. To determine whether you have a valid version, become the super-user (root) and execute:

# smcwebserver status

Note –

The Java Web Console 2.2.4 is part of the SolarisTM 10 operating system, however the Desktop Manager requires version 2.2.5 or higher. A copy of version 2.2.5 is provided in the Desktop Manager archive in the server/console directory. It can be installed by running ./setup in that directory.

If the Java Web Console is not installed on your system, or the installed version is not valid for the Desktop Manager, refer to the instructions in Chapter 4, Java Web Console to first install or update the Java Web Console. Afterwards return to this chapter to continue the Desktop Manager installation.

Steps

  1. Download the Desktop Manager zip archive and extract the content in a temporary directory


    # unzip SunDesktopMgr-1.0.zip

  2. Become the super-user (root) and execute the setup script via


    # cd SunDesktopMgr-1.0/<platform>/server/manager
# ./setup

  3. View the setup script's output for any errors.

    If the installation was performed successfully, the setup script will automatically restart the Java Web Console and you can access the Desktop Manager with a Web browser.

ProcedureOperation

Steps

  1. Type the following URL in your browser:


    https://<hostname>.<domainname>:6789

  2. In the login screen, type the user name and password of an existing Unix user.

    The Java Web Console opens.

  3. In the console application launch page, click on the Desktop Manager link.

    • If you want to skip the console application launch page and go straight to the Desktop Manager, enter the following URL in your browser:


      https://<hostname>.<domainname>:6789/apoc

ProcedureRemoving the Desktop Manager

Step

    To remove the Desktop Manager from the Java Web Console, change to the temporary directory that you created for the installation, become the super-user (root) and execute


    # cd server/manager
# ./setup -u

Migration Issues

The Desktop Manager is compatible with previous versions of the JavaTM Desktop System Configuration Manager (releases 1.0 and 1.1). However, there are a few differences that you should be aware of.

In the previous Configuration Manager versions, all profile data was stored at one specified LDAP server. This LDAP server was configured as part of the overall Configuration Manager installation procedure. This also included the configuration of an LDAP login module that encapsulates the authentication against the LDAP server.

For the Desktop Manager, all the necessary configuration steps are now wizard-based and it is no longer necessary to perform any kind of configuration during the installation. The Desktop Manager now also includes support for multiple configuration repositories. Therefore, you can manage policy data stored on several different LDAP servers, file-based repositories, and so on. The configuration of a specific LDAP login module is no longer necessary.

There have been no changes in the LDAP schemata between the different versions. If you have already configured an LDAP server for a previous Configuration Manager version, there are no changes required when you switch to the Desktop Manager. Therefore, you can take advantage of the Desktop Manager without updating the client (Java Desktop System Configuration Manager1.1. Agent) or the LDAP side.

Note –

Before you install Desktop Manager, you should first remove any previous Configuration Manager or Desktop Manager installations on your system. To remove previous installations, execute (as super-user):


# cd server/manager
# ./setup -u

After you have installed the Desktop Manager, you can then create a configuration repository that points to your existing LDAP server:

ProcedureCreating a configuration repository

Steps

  1. Type the following URL in your browser


    https://<hostname>.<domainname>:6789

  2. In the login screen type the user name and password of an existing Unix user.

    The Java Web Console opens.

  3. In the console application launch page, click on the SunTM Desktop Manager 1.0 link.

  4. Click the New button to start the configuration repository wizard.

    The wizard guides you through the necessary steps for configuring an LDAP-based configuration repository.

    Caution – Caution –

    The wizard automatically offers to migrate the existing policies data to a new 2.0 format. This migration is optional and can be used mainly to improve the performance of the newer SunTM Desktop Manager 1.0 agents. As long as you still need to support the Java Desktop System Configuration Manager 1.1 agents in your environment, do NOT perform this migration.

Desktop Manager Troubleshooting

Cannot Install

Symptom: at the end of the installation of the Java Web Console a message states that it cannot start because there are no registered applications.

Possible causes: no applications have been installed, including the Desktop Manager. .

Solution: install the Desktop Manager and then start the Java Web Console.

Connection Refused

Symptom: you try to open an appropriate URL, for example http://<hostname>.<domainname>:6789, but you receive a message that the connection is refused.

Possible causes: the Java Web Console is not running on the server.

Solution: to start the Java Web Console, become superuser and execute the following commands:


#smcwebserver status
#smcwebserver start

Cannot Log In

Symptom: the user/password combination is rejected on the login page of the Java Web Console.

Possible causes: the corresponding UNIX user account does not exist.

Solution: Check that a corresponding UNIX user name and password is configured on your system. If necessary, create a local UNIX user account for your tests.

No Desktop Manager Link

Symptom: the Java Web Console application list page does not display the Sun Desktop Manager link.

Possible causes: the Desktop Manager module is not installed.

Solution: To check if the Desktop Manager is installed in the Java Web Console, become superuser and execute the following command:


# smreg list -a

If the list does not contain the com.sun.apoc.manager_<version> application, you need to reinstall the Desktop Manager.

Null Pointer Exception, Tomcat/Java error or Blank Page

Symptom: you start the Desktop Manager but only a blank page or error messages appear.

Possible causes: if the error mentions NoClassDefFoundError: sun/tools/javac/Main, then the Java Web Console is using the wrong Java version.

Solution: the current Java Web Console Java environment can be checked by executing # smreg list -p and looking at the java.home property. This property must point to a valid Java home, and that home must be a JDK. If this value is incorrectly set, you need to execute the following command:


# smreg add -p java.home=<JAVA_HOME>
Note –

<JAVA_HOME> must point to a valid installation, for example, where javac can be found in the bin subdirectory.

You then need to restart the Java Web Console with the following command:


# smcwebserver restart

Cannot Connect to an SSL LDAP Server

Symptom: after providing the LDAP server details in the repository creation wizard, including checking the Use SSL box, pressing Next yields a message box stating the server cannot be contacted.

Possible causes: the improper port number has been provided, the LDAP server is not configured to listen to connections using SSL on that port, or the proper certificates are missing in the Java Web Console key store.

Solution: first check that the LDAP server is configured to listen to SSL connections requests on the port specified in the wizard. If this is correct, ensure that either the Certification Authority or the LDAP server certificate is present in the Java Web Console key store, which is located in /etc/opt/webconsole/keystore. The certificate can be added with 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 needs to be restarted for that change to be visible by the Desktop Manager using the command smcwebserver restart.

Cannot Write to Directory

Symptom: while creating a file-based or hybrid backend, a “Cannot write to directory!” error appears.

Possible causes: noaccess user does not have the correct permissions.

Solution: assign write permissions to the noaccess user.