Installing the Oracle Calendar Desktop Client for Solaris

Before you begin

The Oracle Calendar client for Solaris is an X11 application built atop the Motif toolkit and requires Solaris 8 or 9 on the SPARC architecture. In order to install the Oracle Calendar client, you will need an X11 server with Motif runtime libraries installed on your system. If you need to access dCal from other versions of Solaris, use the Oracle Calendar Web client.

Download and install the client

The Oracle Calendar desktop clients for use with dCal are available from the dCal software downloads page. To begin the installation process, download the package for Solaris to your home directory.

After downloading the installer, create a temporary directory and unpack the tarchive into it:

mkdir /tmp/calinstall
cd /tmp/calinstall
gzip -d -c /cal_solaris_1012.tar.gz | tar xvf -

The tarchive unpacks into an OracleCalendar_inst subdirectory.

The Oracle Calendar client uses a Java-based installer. If you plan to install the client for system-wide availability (or into a directory you don't have write privileges for), run the installer as root. If you run the installer as a "normal" user, you'll be restricted to installing into a directory to which you have write privileges.

To run the installer:

  1. Change to the OracleCalendar_inst directory and do one of the following:
    • To use the X-based GUI installer, run ./gui_install.sh
    • To use the text-based installer, run ./text_install.sh
  2. Follow the prompts to select a destination directory and to (optionally) create symbolic links to the executables associated with the client (for example, in /usr/local/bin).

To start the client, execute the ocal script. You may need to specify the full path (/bin/ocal).

Next steps

Now that you have the Oracle Calendar desktop client for Solaris installed, configure the client to connect to the dCal server. Server-based authentication provides a reasonable level of security and requires no additional software; Kerberos authentication provides a higher level of security and provides a persistent login lasting at least 10 hours. Also, other Kerberos-aware applications (SAP's "Authentic Login", Mulberry, etc.) will use the same Kerberos ticket as dCal. Select the desired method below.