Chapter 3

Installing Communique!

Overview

Once you have verified that you meet the hardware requirements and have installed all of the necessary operating system packages, you are ready to install Communique!. This chapter outlines the steps necessary to install Communique!. The following topics are discussed:

CD-ROM Format

The Communique! CD conforms to the ISO 9660 standard format. Most CD-ROM drivers support the 9660 standard.

ISO 9660 specifies mono-case filenames limited to 8 characters and possible 3 character extensions. If a filename does not have a dot (.), one is appended. A semicolon and version number are also added to the end of the filename. Since some systems do not use all these features, the CD file-system's appearance will depend on how a particular platform presents the 9660 standard.

For example, the Communique! install script may appear as any of the following depending on the platform mounting the CD:

install.sh

install.sh;1

INSTALL.SH

INSTALL.SH;1

Remember, if you are installing on a UNIX system using the semicolon and version number, you must quote the semicolon (;) when specifying a filename in a shell.

Mounting the Communique! CD

You must mount the Communique! CD on your workstation before installing Communique!. Follow the instructions for your platform listed below.

Sun SPARCstation running Solaris 2.5.1 or Higher

1. Log in as root.

2. Insert the Communique! CD into the local CD-ROM drive.

Sun's volume management should automatically mount the CD. If you are not running volume management, you need to mount the CD with the command

# mount -r -f hsfs /dev/dsk/c0t#d0s0 /cdrom

c0t#d0s0 specifies the SCSI device number (i.e., c0t6d0s0).

3. Change directories to the Communique! CD with one of the following commands:

with volume management

# cd /cdrom/insoft#1

without volume management

# cd /cdrom

HP 9000 Series 700 running HP-UX

1. Log in as root.

2. Insert the Communique! CD into the local CD-ROM drive.

If a valid CD-ROM drive is attached to the system, the CD will be automatically mounted on /CDROM. If the CD does not automatically mount, you need to perform steps three and four, otherwise you can go directly to step five.

3. If it does not already exist, create a mount point in the root directory called CDROM with the following command:

# mkdir /CDROM

4. Mount the CD with the following command

# mount -r -F cdfs -o cdcase /dev/dsk/c0t#d0 /CDROM

# specifies the SCSI device number (i.e. c0t4d0).

5. Change directories to the Communique! CD with the following command:

# cd /CDROM

Digital Alpha AXP running Digital UNIX

1. Log in as root.

2. Insert the Communique! CD into the local CD-ROM drive.

3. If it does not already exist, create a mount point in the root directory called cdrom with the following command:

# mkdir /cdrom

4. Mount the CD with the following command:

# mount -t cdfs -r /dev/rz#c /cdrom

# specifies the SCSI device number (i.e. rz5c).

5. Change directories to the Communique! CD with the following command:

# cd /cdrom

IBM RS/6000 Compatible running AIX

1. Log in as root.

2. Insert the Communique! CD into the local CD-ROM drive.

3. If it does not already exist, create a mount point in the root directory called cdrom with the following command:

# mkdir /cdrom

4. Mount the CD with the following command:

# mount -r -v cdrfs /dev/cd0 /cdrom

5. Change directories to the Communique! CD with the following command:

# cd /cdrom

SGI running Irix

1. Log in as root.

2. Insert the Communique! CD into the local CD-ROM drive.

Note that Irix will normally automount the CD-ROM.

3. If it does not already exist, create a mount point in the root directory called cdrom with the following command:

# mkdir /cdrom

4. Mount the CD with the following command:

# mount -o ro,notranslate -t iso9660 /dev/scsi/sc0d5l0 /cdrom

5. Change directories to the Communique! CD with the following command:

# cd /cdrom

The MDL Package Format

The MDL Package Format (MPF) is the means by which MDL bundles its software products for distribution. The MPF is identical on all platforms, and makes it easy for users to perform multiplatform installations of software components in a single step. It also enables users to install specific software components or the entire product, and contains information with which users can carefully manage the amount of disk space they will use.

The MPF also provides version control features, and includes information on each installable component that can easily be retrieved from within the installation script.

The MPF and MDL Package Installer provide users with an easy to use, highly flexible means of installing MDL software, enabling them to perform first time installations or specific updates quickly and easily.

Running the MDL Package Installer

The MDL Package Installer copies Communique! to your workstation and configures it for conferencing. To begin installation of Communique!, make sure that you are in the Communique! CD’s directory, and follow these instructions:

1. Use the command appropriate to your system's interpretation of the 9660 format to start the install script:

# ./install.sh

or:

# ./install.sh\;1

or:

# ./INSTALL.SH

or:

# ./INSTALL.SH\;1

Note the quotation (using the slash, "\") of the semicolon as needed.

When the Installer is launched, a title screen will appear giving you some basic information on the installation process. After you press the enter key, the Installer searches the CD for packages that can be installed on your workstation. When the Installer has located the available packages, a screen listing available packages will appear. There should be at least two packages listed, Communique! and OpenDVE runtime. The OpenDVE runtime is required for Communique! but is shared by all OpenDVE based products. If this is a first time installation, you will need to install both of them.

2. Check to make sure that there is an x in the box beside both Communique! and the OpenDVE runtime.

You can enter Q at any prompt to automatically leave the Installer without copying any files to disk.

The next screen will provide you with a list of the architectures that are supported by Communique!. The architecture that you are currently running the install script on will be automatically selected. If you want to install Communique! for more than one architecture on this machine, you should select the other architectures by entering the numbers that correspond to them. By installing support for several platforms and exporting the Communique! directory to your network, you can provide a single access point to Communique! software for workstations from a variety of vendors (i.e., both Sun and HP workstations running Communique! from the same directory).

3. Once you have selected the architectures you wish to install software for, verify that they are correct and press D for Done.

Any workstation attempting to run Communique! will still require the appropriate licenses. See your MDL representative for information on purchasing additional licenses for your network.

Next, a screen will appear listing all of the Plugins that are available on the platforms that you selected. The list includes all of the Plugins that are supplied with the based Communique! package as well as the optional Plugins that can be purchased from MDL. If there is more than one page of Plugins available for installation, you can use the N action to see the next page. When you are on the second page, you can use P to return to the previous page.

At this point you should select the Plugins that you wish to install for use with Communique!. By default, all of the entries in the list of Plugins are selected. You can enter the number corresponding to a Plugin to toggle its selection. You can also obtain information on an individual Plugin by entering I# (with # being the number of the Plugin in the list).

4. Once you have chosen the Plugins that you wish to install, you should verify that your selections are correct, then press D for Done.

The next screen will allow you to select the directory in which Communique! will be installed. Communique! is installed in /opt/insoft/ by default, but you can choose another directory if you wish.

5. If you wish to accept the default, press Enter, or enter the path to the directory where you wish to install Communique!.

A screen displaying the path where the installation log will be stored will appear, and you are given a final opportunity to abort the installation. At this point, if you press Enter, the Installer will copy the selected filesets from the CD to your hard drive.

While you are waiting, please complete and fax the MDL Product Registration Form included with your Communique! software if you have not already done so. You need to complete this form in order to obtain your license keys from MDL. See Chapter 4, "Licensing Communique!", for information on licensing and completing the MDL Product Registration Form. You need to install your Communique! license keys before you can use Communique!

After the Installer has finished installing Communique!, it will return to the architectures screen in order to install the OpenDVE runtime package. The OpenDVE runtime package is required to run all of MDL’s products. For information on OpenDVE, see Appendix B, "Technical Issues".

The steps for installing OpenDVE are identical to those required to install Communique!. It is suggested that you choose the same directory for OpenDVE installation that you did for Communique!.

When installation has been completed, you will need to install license keys to run Communique!.

6. Run the license installation program as outlined in Chapter 4, "Licensing Communique!", when you are ready to license Communique!.

User Customization

After installing Communique!, you may wish to change the default selection or otherwise limit Plugins' controls. One example of a control typically limited or changed is the video capture card selection in the TV Tool.

Instructions for customizing Plugin configurations are found in the Customizing Communique! section of Appendix B, "Technical Issues".

For instructions on configuring Communique! to locate users not on your local network automatically, refer to the Broadcast Tunneling section of Appendix B, "Technical Issues".

If your workstation has more than one network interface, and you wish to specify the one you wish to use, the instructions are found in the Multiple Interfaces section of Appendix B, "Technical Issues".

If you plan on utilizing multicast routing, see Appendix B, "Technical Issues".

Return to MDL Home Page