This page guides you through the process of acquiring and installing the necessary Unix tools for doing AIDA development at SLAC. Those tools are to be kept on AFS (The Andrew File System) where they accessible to all Unix hosts. So activities carried out as part of these configurations will be available for all unix hosts.
This page also describes the AFS directory structure. This description includes the placement of tools built for both Unix and NT.
For each Unix tool, this page describes what its used for, where to get it, and how to install it. The installation instructions tell you, in a step-by-step, cookbook format, how to install the next version of each tool. It is assumed that you will be installing and running the tools from SOLARIS except where noted.
Before you begin you'll need the following (described in Appendix A below):
At slac, we support the following standard Orbacus installations:
Solaris 2.8 GCC 2.95.3
Solaris 2.8 JDK 1.3
As of Version 4.1, ORBACUS Jthreads/C++ is included with Orbacus for C++. So, it is no longer necessary to build Jthreads as a separate package.
The steps for upgrading Orbacus for C++ and Orbacus for Java are below. These two productions are interlocked because of how the Dev/Prod the directory structure is implemented by us on /afs. This is true because the Dev and Prod directories are just below the orbacus directory (there are not seperate Dev and Prod directories for C++ and Java. This means that you want to upgrade Orbacus for C++ and Orbacus for Java at the same time for each new version that is released. You should do C++ first, and then Java. To me, this coupling is a reasonable restriction because that is how Orbacus does it's releases (C++ and Java are done at the same time). It also keeps our directory structure simple.
Below, we have a description of the current PRODUCTION AFS based directory tree. The tree structure is a temporary one and will be cleaned up for the next release (when windows and solaris support the same orbacus version)..
Click HERE for a visual description of the Orbacus directory structure.
Origin: www.orbacus.com.
PATH change example TBD
Follow these steps to download, build, and install a new version. You are downloading and building in the development tree under /afs/slac/package/iona/orbacus. Before you begin these steps, you should have no files from a previous build in your development tree afs/slac/package/iona/orbacus/Dev. After you complete These steps, proceed to the next section and install Orbacus for Java.
Download
the following files from www.orbacus.com.
OB-Version.tar.gz, OB-VersionCHANGES.txt, and OB-Version.pdf
Make a screen capture of the Download page which tells the names of all files available, what they are, and what OS and compiler versions are supported. Store this screen capture in a file called README.txt.
Put
the files from Steps 1 and 2 into this DEVELOPMENT distribution
directory:
/afs/slac/package/iona/orbacus/Dev/distribution/OB-VersionNumber
Unzip the .tar.gz file containing C++ source with this command: gunzip -rd OB-Version.tar.gz
Create
the directory (if not already done) where the Orbacus for C++ source code
will be placed.
/afs/slac.stanford.edu/package/iona/orbacus/Dev/sun4_58 (or what every
version of solaris is correct)
Copy the tar file created in Step 4 to the directory created in Step 5.
Extract
the resultant .tar file with this command: tar -xfv OB-Version.tar
You now have the Orbacus for C++ source file tree created. Next, you
will be making and installing it.
Follow
the instructions in the INSTALL file under the directory you created in the
previous two steps. When you get to the point that you need to specify
the Install directory, indicate this directory:
/afs/slac.stanford.edu/package/iona/orbacus/Dev/sun4_58/OOC
Where
to find it: Origin: www.orbacus.com.
CLASSPATH change example: Add the full pathname of the
OB.jar file created by the install to your CLASSPATH
For java, we don't build the product from source. Instead, we download the pre-compiled .jar files into the "common' directory. Then, we download the platform specific pre-compiled utility executables (like jidl.exe) to the "platform" directories under the orbacus afs tree. We download the Java source just to have it available online (but as I said, we don't build it).
Follow these steps to download and install a new version. You are downloading in the development tree under /afs/slac/package/iona/orbacus.
Download
the following files from www.orbacus.com.
JOB-4.1 CHANGES.txt, JOB-4.1.0-bin-solaris.tar.gz, JOB-4.1.0-bin-win32.zip,
JOB-4.1.0.jars.tar.gz, JOB-4.1.0.tar.gz.
Put
the files from step 1 into this DEVELOPMENT distribution directory.
/afs/slac/package/iona/orbacus/Dev/distribution/OB-VersionNumber
Unzip the .tar.gz file containing java source with this command: gunzip -rd JOB-Version.tar.gz
Create
the directory (if not already done) where the Orbacus for Java source code
will be placed.
/afs/slac/package/iona/orbacus/Dev/common/JOB-Version
Copy the tar file created in step 3 to the directory create in step 4.
Extract
the resultant .tar file with this command: tar -xfv Job-Version.tar
You now have the Orbacus for Java source file tree created. We will
not be building it. We just have it here online for reference.
Unzip the .tar.gz file containing java JARS with this command: gunzip -rd JOB-4.1.0.jars.tar.gz
Create
the directory (if not already done) where the Orbacus for Java JAR files
will be placed:
/afs/slac/package/iona/orbacus/Dev/common/Version.JARS
Copy the tar file created in step 7 to the directory created in step 8.
Extract
the resultant .tar file with this command: tar -xfv Version.JARS
You now have the Orbacus for Java pre-compiled JAR files available.
Create
the directory (if not already done) where the Orbacus for Java win-32
precompiled utilities will be placed:
/afs/slac/package/iona/orbacus/Dev/win32/OOC/bin-java
Copy the zip file JOB-4.1.0-bin-win32.zip from the distribution directory to the directory you created in step 11.
Go to an NT machine an unzip the file mentioned in step 12.
Unzip the .tar.gz file containing Java pre-compiled utilities for solaris with this command: gunzip -rd JOB-4.1.0-bin-solaris.tar.gz
Create
the directory (if not already done) where the Orbacus for Java solaris
precompiled utilities will be placed:
/afs/slac/package/iona/orbacus/Dev/solaris/OOC/bin-java
Copy the tar file created in step 14 to the directory created in step 15.
Extract
the resultant .tar file with this command: tar -xfv JOB-Version-bin-solaris.tar.gz
You now have the Orbacus for Java precompiled utilities for Solaris
available.
Build the demonstration programs. Navigate to /afs/slac/package/iona/orbacus/Dev/common/<version>/ob/demo. Find the makefile in that directory and check that the "top_srcdir" is set to the "ob" level (ie ".."). Then just run it, ie just type "gmake" at the prompt. It should build all demos. You can run the demo's with the "run" script in each demo.
The
steps above created the Development Tree afs/slac/package/iona/orbacus/Dev for
Orbacus for C++ and Java.
After you have done some testing and want to use this newly created release as
the Production release do this:
Rename
the Production tree to Old like this:
mvdir /afs/slac/package/iona/orbacus/Prod /afs/slac/package/iona/orbacus/Old
Rename
the Development tree to Production like this:
mvdir /afs/slac/package/iona/orbacus/Dev /afs/slac/package/iona/orbacus/Prod
Create
a new Development tree as a placeholder for the person who will be doing the
next version like this:
mkdir /afs/slac/package/iona/orbacus/Dev
Click HERE for a visual description of the Orbacus AFS directory structure.
For the current production releases, we have a mixture of 4.0 and 4.1 in the same directory tree. This is only temporary, and for the next release, if we use the above procedure, the next prod tree will only contain the new release (for 4.2, say).
These are the bin directories we have at this point containing the mixture of 4.0 and 4.1 version code:
/afs/slac/package/iona/orbacus/Prod/sun4_58/OOC/bin
- 4.1 Orbacus for C++ is installed here.
/afs/slac/package/iona/orbacus/Prod/win32/OOC/bin - 4.0.1 Installed Orbacus for
C++ (greg built this)
/afs/slac/package/iona/orbacus/Prod/sun4_58/OOC/bin-java
- 4.1 Java pre-compiled binary utilities for solaris
/afs/slac/package/iona/orbacus/Prod/win32/OOC/bin-java - Win32 pre-compiled
binary utilities for win32.
[Aida Home Page][SLAC Controls Software Group][ SLAC Home Page]
Author: Ron
MacKenzie, 9-Nov-2001
Modified by: