Installing and Running CBE Servers

DistView Home

User Guide
   Overview
   DistView Tools
   Related Services
   Installing and Running CBE servers
   Compiling the package
   Running Session Manager
   Running DistView-Based Applets

Developer Docs
   Javadoc
   Registry Server
   Sample Clients
   How to ...
   Known Problems

Licensing Information

Download DistView

People

DistView Publications

Frequently Asked Questions

Acknowledgments

Installing and Running CBE Servers

Setting up the Environment

To set up the environment, please make sure of the followings first.

Unpack the package in the browser-accessible directory for browser access. For example, if the name of the downloaded package is um.tar.gz, type

Add the umich/cbe path of the package to your path. For example, if the package is installed at /usr/jangho/public_html, in C shell, type

Add the JDK 1.1.3 or later to your path. For example, if the path to the JDK 1.1.3 binaries is /usr/local/jdk1.1.3, in C shell, type

You should have /bin/ksh, and /bin/sh.

Give the permission to the package. For example, if the package is installed at /usr/jangho/public_html, type

Configure your httpd server to allow the execution of CGI script in user directory. On the Apache server, you need to uncomment the line of "AddHandler cgi-script .cgi" in srm.conf file in conf directory of the Apache package. Also, security options in Apache need to be set so that the umich directory is accessible to the server. For more information about Apache server and downloading it, see Apache Project Home Page.

It is possible to bring up DistView applets without a Web server, though those applets can then only be used on the machine on which the CBE servers (Corona specifically) are running. Go to Running Corona Server for more information.

Compiling the Package (Source Code Version Only)

If the package is the source code version, see Compiling the Package to compile the package.

Making Client-Related Files

Type "makejd" to create client-related files which will be used later by the client.
You'll be asked the following question. Enter the port number of the Corona server. (About the Corona Server, see next.)

  Please, enter the port number of the Corona server

Running CBE Servers

CBE servers consist of three servers: Corona server, RoomMgr server, and Registry server. The Corona server is a group-communication server that supports shared object. The RoomMgr server is a server for multi-applet, multi-user shared work spaces. The Registry server maintains the users' registry information.
(Note: If you want to run only the Corona server for testing purpose, (such as for running java application which connects to the Corona server), go to Running Corona Server)

To run CBE servers,

Type "runCBEServers Corona_port_number"

At the following question, type "y" if you want to log messages of chat. Type "n", otherwise.

  Do you want to log chat ? [y/n]

Enter the port number of the Registry server at the following question--the Registry server is responsible for maintaining registry information of users.

  Please, enter the port number of the Registry server

Enter the the URL of the Session.html. (Session.html is the Web page of the Session Manager client, which will communicate with the CBE servers. )

  The Session.html will be placed in the directory where the package
  is installed, which is the parent of package root(umich).
  (Session.html is the Web page of the Session Manager client, which
  will communicate with the CBE servers.)
  For example, if the package is installed in uarc directory and
  the URL to uarc is http://seoul.eecs.umich.edu/~jangho/uarc,
  the URL to the Session.html will be
  http://seoul.eecs.umich.edu/~jangho/uarc/Session.html
  (Actually, this Session.html is a link to the current CBESession-Corona
  _port_number.html (e.g. CBESession-9001.html) that is being generated.)

  Please, enter the URL of the Session.html being created.

When you run the CBE servers at a specific port for the first time, the script will collect configuration information from a user so that next time the user restarts the CBE servers at the same port, the collected configuration information is used. Your configuration is saved in umich/cbe/admin/CBE-Corona_port_number.config (e.g. CBE-9001.config) file. You can modify the configuration by editing the file. The logs of the Corona server and the Room manager will be created in ServerLog directory and RoomMgrLog directory in umich/cbe/logs directory in the package.

Killing CBE Servers

To kill CBE servers,

Type "killCBEServers port_number" (port_number is the Corona_port_number you provide when you run runCBEServers or testCorona.) If you don't provide the argument, the killCBEServers will print the port numbers which are used by current CBE servers.

Running a Client

About running a client, see Running a Client

Running CBE Servers Separately

To run CBEServers separately, use the following commands.

testCorona Corona_port_number
runRoomMgr hostname Corona_port_number path_to_the_umich/cbe/admin standard_output_log standard_error_output_log
runRegistry Registry_port_number path_to_the_umich/cbe/distview path_to_the_umich/cbe/admin standard_output_log

Killing CBE Servers Separately

To kill CBEServers separately, use the following commands.

killCorona Corona_port_number
killRoomMgr Corona_port_number
killRegistry Registry_port_number

Electrical Engineering and Computer Science Department, University of Michigan