IIBDS Installation Instructions


The IIBDS is contained in several compressed tar files (
IIBDS1.tar.Z, IIBDS2.tar.Z, etc).  When uncompressed and tar
extracted, the IIBDS environment will have been created.
The expanded system will require approximately 33 Mbytes of
disk.

IIBDS has been compiled for the following environment:
Sun 4 Workstation - minimum 8MB RAM, monochrome monitor,
SunOS 4.1 (or later), X Windows (Version 11 Release 5),
and standard Fortran and C compilers/libraries.

The following shared libraries are required for run-time
linking:

        -lX11.4 => /usr/lib/X11/libX11.so.4.10
        -lF77.1 => /usr/lang/libF77.so.1.1
        -lc.1 => /usr/lib/libc.so.1.6

Define the LD_LIBRARY_PATH environment variable for other
locations of these libraries.

After "un-taring" the following directory structure will
have been created:

IIBDS/ife/README		this file
         /bin			holds system executables
         /docs			system documentation
         /lib			support structure, including
				interface definition and
				knowledge bases
        /misc			operational tips, training exercises, etc.
        /model			example problems for use by demo
        /src			infrastructure source code
        /sys			3rd party binaries and libraries

Make a symbolic link to the ife directory called /usr/esru/ife/.
In the ife directory there is a file .iferc_c.  You must change
the lines

setenv host iota
setenv IFE_HOME /usr/esru/ife/

        to

setenv host x
setenv IFE_HOME y

where x = your machine name
      y = your ife directory path with a trailing
          / as in the above example.

In order to be able to change user types at run time, all
users should be granted write permission for directory
/usr/esru/ife/lib/uc.

To run the IIBDS (assuming a C-shell) type the commands:

  source .iferc_c
  iibds

The window in which the commands were given will be the
place where the blackboard journal will appear if you
request it (directions later).  Follow these steps to
explore the IIBDS facilities:

1)   Supply your name in the "user name" box or accept the
     one given (no carriage return required).

2)   Change the user type to COMBINE by means of the left
     mouse button (only release when COMBINE image is upper-
     most).

3)   Fill in something in the "problem name box", signal
     completion by moving out of the box and clicking the
     middle button.

4)   A new pop-up "models of design" will appear, select
     "Unconstrained" and a form with a number of different
     design tool pop-ups will appear.

5)   Selection of one of the Design Tools from one of the
     tool sets will start up the required tool, or in the
     case of the tool not being available, will display an
     image of a session with that tool.  Currently the sys-
     tem is setup to allow access to one tool at a time. You
     can activate a tool by placing a link to it in sys/bin
     and informing the program handler about the tool.  In
     the next week or so we will supply a tutorial on this
     issue.

6)   To see the journal of your session, type in the follow-
     ing (tab separated) command in the text window from
     which the IIBDS was started (this is the BB):

     update_me <tab> user_dialog

To see the chronicle of the data exchange type in the fol-
lowing command:

update_me <tab> data_exchange

7)   To quit simply type "abort" in the text window.

8)   If you wish to browse the facilities of the IFe, select
     the engineer user type rather than the COMBINE user
     type.

Background material on the operation of the blackboard is
included in the directory "docs".  Exercises which show com-
munication between applications and the blackboard are
included in the directory misc/OPERATION/learn_2.

Because the IIBDS is a prototype you will find that there
are some facilities which are not instantiated and we would
not be suprised if some of you are devious enough to make
the system fall over.  You can email combine-task5 if you
have specific questions or comments.
