choose: sw hd | installObjy | setup: ams ls pud chs oids | confCH | maintain: ams ls pud chs oids | moveFD | creaBri

Search | Site Map .

Setting up AMS

Setting up SLAC AMS

What release should you use?

The SLAC AMS is supported for platforms as described in Supported platforms. Until there is an incompatibility, the SLAC AMS is only supported at the current Objectivity release level.

Where do I find installation files?

/afs/slac.stanford.edu/package/amsslac/distrib

The AFS group name of this directory is g-babar:com-obj

If you do not have an AFS account and would like one, use the "New users" link from the BaBar Detector Home page.

What do I install?

In this directory you will find several compressed tar files named in the form of

ams-osver[-glibcver].tar.Z

Where osver is the operating system version and glibcver is the glibc version, when applicable. Choose the appropriate file for your platform. Make sure to read the README file contained in that directory before installing any software.

Installing SLAC AMS

Perform the following steps:

  1. Pick a user to run AMS. Because AMS can write anywhere, it must never be run with root privileges.
  2. Become root. If you do not have root privileges, ask your system administrator to perform the next two steps.
  3. Create the directories named "/usr/etc/ooss", "/var/adm/ooss", "/var/adm/ooss/logs", and "/usr/spool/objy"; each owned by the user that is to run the AMS.
  4. Create the base directory where Objectivity/DB files are to be stored (for example "/objy/databases") owned by the user that is to run the AMS.
  5. Change to the user name that is to run the AMS.
  6. Set the permission of the directory either 0752 (0772, if you need group write access) along with the setgid & sticky bits (such as drwxr-sr-t or drwxrwsr-t).
  7. cd usr/etc/ooss.
  8. Uncompress and untar the chosen file into the current working directory. For example: zcat chosen_file | tar xvf - .
  9. As directed by the README file, edit the StartAMS.cf file to be compatible with your setup. The StartAMS.cf file is explained in the AMS oofs/ooss Configuration Guide.
  10. Unless you will be setting up a strong security environment you need to block AMS ports at your firewall. Ask your gateway administrator.
  11. Use the StartAMS script to start he AMS and the StopAMS script to stop AMS. Use only these scripts, or oostopams, to start or stop the AMS.

Are there any additional steps?

Probably not, unless you want to use some of the special AMS extensions, including:

Where do I find documentation on how to perform these steps?

Who to contact for problem resolution?

If you have problems, please contact Andrew Hanushevsky.

Setting up standard Objectivity/DB AMS

What release should you use?

The Standard AMS server comes with Objectivity release. The one from the Objectivity release should be used.

Where do I find installation files?

$OBJYBASE/<arch>/bin/

where $OBJYBASE is a directory where Objectivity has been installed.

What do I install?

List of files used by AMS:

By default, you do not need to move any files; they are part of the Objectivity installation. At SLAC, we run AMS from a local disk (to avoid dependency on AFS - Objectivity binaries are stored in AFS). If you choose to avoid AFS dependency as well, make a directory on a local disk of each machine where AMS will run, and copy these ooams to that directory.

Installing standard Objectivity/DB AMS

Perform the following steps:

  1. Pick a user to run AMS. Because AMS can write anywhere, it must never be run with root privileges.
  2. Become root. If you do not have root privileges, ask your system administrator to perform the next two steps.
  3. Create the directory "/usr/spool/objy" owned by the user that is to run the AMS.
  4. Create the base directory where Objectivity/DB files are to be stored (for example "/objy/databases") owned by the user that is to run the AMS.
  5. Change to the user name that is to run the AMS.
  6. Set the permission of the directory either 0752 (0772 if you need group write access) along with the setgid & sticky bits (e.g. drwxr-sr-t or drwxrwsr-t).
  7. Unless you will be setting up a strong security environment you need to block AMS ports at your firewall. Ask your gateway administrator.
  8. Use oostartams to start AMS and the oostopams to stop AMS.

Who to contact for problem resolution?

If you have problems, please contact Andrew Hanushevsky.

 


BaBar Public Site | SLAC | News | Links | Who's Who | Contact Us

Page Owner: Jacek Becla
Last Update: June 13, 2002