|
|
The CVW Client software should be installed in a shared file space (such as NFS) so that only one version of the software need be installed and maintained. If you do not have a shared file space available from a server, you must perform the following installation procedures on each user workstation.
The following are the recommended default directory locations for the CVW Tk Client.
/opt for Solaris
/usr/local for other
Log in as root. Change to the directory where the CVW client will be
installed and extract the skeleton directory for the CVW Client software
using the following procedure. The skeleton directory will automatically be
placed in the directory CVW-3.2.
From this point on, this documentation will refer to the CVW client
directory as $CVWHOME.
cd /opt for Solaris
cd /usr/local for other
uncompress - < cvw-tk-client-3.2.*-base.Z | tar xvf
-
Once the client skeleton directory structure has been established and customized to your environment, the specific binaries and libraries for individual platforms can be added.
Change to the directory above the CVW client directory and extract the
operating specific CVW client file. The files will automatically be placed
into the correct locations in $CVWHOME. The example below
demonstrates how to add client support for Solaris.
cd /opt for Solaris
cd /usr/local for other
uncompress - < cvw-tk-client-3.2.*-sparc-Solaris2.tar.Z | tar
xvf -
Repeat the above steps for each architecture required.
The cvw.res file can be found in
$CVWHOME/etc/cvw.res
Edit the Tkmoo.hostList value in located in the CVW Server
List section of the cvw.res file to include the following:
the name of your CVW server, the host address of your CVW Server, the port
number of your CVW Server, the host address of your CVW Document Server,
and the port number of your CVW Document. Do not include spaces in the CVW
name. Do not place a line return in the string.
Tkmoo.hostList: { { servername { serveraddr port } { docserveraddr port } }
Example: Tkmoo.hostList: { {CVW {129.9.9.209 8888} {129.9.9.209 8889} } }
CVW user images can be stored locally with the client in the CVWHOME area
in $CVWHOME/lib/images/user, or if a more centralized location
is required, the images can be stored in a directory on a web server.
Edit the cvw.res file to include location where the CVW
user images will be stored by editing the Tkmoo.userImagesURL
value located in the User Images section.
To specify the location in the client CVWHOME area, enter the following
Tkmoo.userImagesURL value:
Tkmoo.userImagesURL: file:/$env(CVWHOME)/lib/images/user
To specify the location as a directory on a web server, enter the
Tkmoo.userImagesURL value with the URL of the location of the
images.
Tkmoo.userImagesURL: http://<yourWebServer> /<directoryPath>
Example: Tkmoo.userImagesURL: http://www.mitre.org/cvw/user-images
If users will be accessing user images or whiteboard backdrops from a
web server outside your firewall, set the Tkmoo.proxyServer
value located in the HTTP Proxy Server section of the cvw.res
file to use your proxy server.
Tkmoo.proxyServer: {proxy.somewhere.org 80}
Example: Tkmoo.proxyServer: {gatekeeper.mitre.org 80}
If you do not want to use a proxy server, set the
Tkmoo.proxyServer value to {}.
Tkmoo.proxyServer: {}
If you will be accessing your user images from a web server located
outside your firewall, then set the Tkmoo.userImagesBBP value
located in the User Images Bypass HTTP Proxy section of the
cvw.res file to 0.
Tkmoo.userImagesBBP: 0
If you will be accessing your user images from a web server located
within your firewall, then set the Tkmoo.userImagesBBP to
1, so that it can bypass your proxy server.
Tkmoo.userImagesBBP: 1
The CVW client contains an error reporting system, which displays a
dialog to the user with the detected error and provides the user the
ability to send the error traceback to a specified email address. The
default setting for the Tkmoo.enableErrorEmail value in the
cvw.res file is set to 0, which disables this
feature.
Tkmoo.enableErrorEmail: 0
To make use of this feature, set the value to 1 as below:
Tkmoo.enableErrorEmail: 1
Specify the email address to receive the bug reports by entering the
email address as the Tkmoo.errorEmailAddress value in the
cvw.res file.
Tkmoo.errorEmailAddress: username@example.org
The administrator may configure custom default user settings for first
time CVW users by editing the cvwprefs file located in
$CVWHOME/etc. This file is used to create the
.cvwprefs file in the user's home directory when they first
connect to CVW. If a user has previously used CVW, custom preferences will
not be overwritten by the new cvwprefs file.
It is strongly recommended that you make a backup of these files if you choose to change them.
The cvwprefs file contains default colors, audio and video
conferencing settings, display preferences, specific tools bar icons,
checkout directory location, web browser preference, and window geometry
settings.
mime-db File to Enable Users to Import
Files into CVWEdit the mime-db file located in the
$CVWHOME/lib/<architecture>/mime-db to reflect any
local customization required. Each architecture platform supported by
CVW should have a customized mime-db file.
The format for the MIME type entries is as follows:
<MIME type>;<CVW name>;<Edit application>;<View application>
Example: text/plain; ASCII Text Document; textedit; textedit
It is recommended that the file be tailored to MIME entries for the applications that will be utilized by the user environment. Entries in the sample file provided that are not applicable should be deleted. The file entries should be re-ordered so that frequently used applications appear at the top of the file (and therefore at the top of the user's selection menu in the CVW client).
Rename the client directory to CVW.
cd /opt for Solaris
cd /usr/local for other
mv CVW-3.2 CVW
xcvw Shell script to Provide the Default
HomeIt is no longer required to set the CVWHOME and other environment
variables used by the CVW client if the default home is entered into the
xcvw shell script. Edit the $CVWHOME/bin/xcvw
shell script and enter the DEFAULT_CVWHOME path to the CVW
client directory. DEFAULT_CVWHOME can be a colon separated
path list, identifying valid mount points for various CVW clients.
DEFAULT_CVWHOME=/opt/CVW:/usr/local/CVW
Set the ownership of all files in the CVW directory.
cd /opt/CVW for Solaris
cd /usr/local/CVW for other
chown -R root .
chmod -R go-w .
chgrp -R bin .
The video conferencing tool used by CVW, Lawrence Berkeley Labs VIC requires that the shared memory segment size be increased to support displaying full size 24-bit video conferencing windows.
To make these changes under Solaris, edit /etc/system and
add the following.
set shmsys:shminfo_shmmax=2097152
set shmsys:shminfo_shmseg=24
If you are running SunOS, rebuild the SunOS kernel to increase the
memory size. Edit the kernel configuration file located in
/sys/sun4m/conf with the line below and configure and install
the new kernel. Note: If you have not previously rebuilt a SunOS kernel,
it is recommended that you work with a system administrator who has this
experience.
options SHMSIZE=2048
If the CVW client is running on a Solaris 2.6 SBUS platform, the audio and video tools will fail due to inability to access a graphics library in the expected location. To avoid the error, make a symbolic link from the expected location to the actual location of the graphics library.
cd /opt/SUNWits/Graphics-sw/xil/lib
mkdir pipelines
cd pipelines
ln -s /usr/openwin/lib/xil/devhandlers/xilIO_SUNWrtvc_ucode.a xilSUNWrtvc_ucode.a
Note, you should only perform this change on the Solaris 2.6 SBUS platforms; it is not required for PCI bus based systems.
Last update: 13 October 2000
This work, including the source code, documentation and
related data, is placed into the public domain.
The original author is
The MITRE Corporation.
THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, AS TO THIS
SOFTWARE, OR TO THE ACCURACY, CAPABILITY, EFFICIENCY,
OR FUNCTIONING OF THIS SOFTWARE OR ANY DERIVATIVE WORK
OR OTHER ITEM MADE, USED, OR SOLD THAT INCORPORATES
THIS SOFTWARE. THE AUTHOR OF THIS SOFTWARE ASSUMES NO
RESPONSIBILITY FOR ANY CONSEQUENCE RESULTING FROM THE
USE, MODIFICATION, OR REDISTRIBUTION OF THIS SOFTWARE.
Information in this document is subject to change without notice.
Other products and companies referred to herein are trademarks or registered
trademarks of their respective companies or mark holders.