Before installing Objectivity 5.1 locally you should check that:

1- you have the right permisions to access the installation files, if not, you should fill the appropiate registration forms indicated here. 

2- your OS and C++ compiler are supported by Objectivity 5.1.

Objectivity 5.1 has to be installed locally only if the target host has no AFS access. For this task you need administrator rights on your system. 

The installation procedure is detailed in following steps and it depends on the platform and operating system you are using:

- UNIX 

- WINDOWS 

If you want to run the Lockserver on your local host, create /usr/spool/objy directory with write permissions for everybody.

There is a newer version of AMS in the export directory for each platform. After running setup, copy the ooams program into the bin subdirectory of your local Objectivity installation.

To check that the installation is correct run this simple test program.

UNIX in IBM/SUN/SGI/HP/DEC platforms

1. If you have AFS access go to /afs/cern.ch/sw/lhcxx/export/@sys/Objectivity/5.1 directory. If not, FTP to a public CERN machine and copy all files from this directory to your local host.

2. Run the installation script install.csh.

3. At the script prompt specify the product(s) to be installed following the menu items, i.e. 1,2,3. To run Objectivity you need to install minimum the DDL , ODB, and CPP products.
Note: you must have a license for each product you want to install.

4. Specify the installation directory, if there is not enough space an error will be given.

The installation script will copy the product in a subdirectory with the architecture name for your platform.

When installing DDL and C++ products, the configuration script ooconfig will run automatically after at the end of the installation. You will be prompted for compiler and environment information ooconfig script configures the DDL processor and creates its executable (see note*). You can run ooconfig always you want to configure the ooddlx processor for your local environment. 

During installation the script ooverify is executed to check if release files are loaded properly.
The Online Documentation is included already with the installation. To read it you need FrameMaker reader which you can download for free from Frame Maker Web pages. 

Note* : On IBM platforms the ooddlx executable created by ooconfig produces many warnings due to a false position of the include files. To solve this problem you should edit ooddlx for AIX and change last line in the following way: 
 
-I/usr/include -I$OBJY_INCLUDE $CPP_INCLUDES





WINDOWS NT in INTEL platforms

- Installing Objectivity/DB on Windows NT with access to NICE:

1. Mount the NICE directory containing the installation kit as a mapped drive. The directory is mirrored on the NICE servers - an example path would be:

\\SRV1_NICE\PGM\P32\lhcxx\export\Windows_NT\Objectivity\5.1

2. Run the Setup.exe program from the mapped drive (if it does not start automatically)

- Installing Objectivity/DB on Windows NT without NICE or outside CERN:

1. Copy the installation kit from AFS to any root directory on the target PC. If you don't have access to AFS from that machine, use FTP to download the kit from any CERN public machine. The files can be found in:

/afs/cern.ch/sw/lhcxx/export/nt/Objectivity/5.1

2. Run the Setup.exe program
Once the installation is finished you can delete the files.

Notes:
The setup program will ask to select the products to be installed. You should probably install all except SmallTalk and SQL modules.

In some cases we have seen the installer program fail or crash on PCs with long PATH or INCLUDE environment variables. If you run into this problem reduce the length of this variable and try again (restore what was removed after the installation). The same problem may happen if the PathDirs or IncludeDirs settings in MVC++ menu Tools/Options/Directories are too long.

The Objectivity installation program assumes it is installed from the CD (root directory in some disk) and does not work from any subdirectory, this means you must run the setup.exe from a root directory, it can be c:\  from the DOS command prompt or / from a bash shell .