Checklist for Installing and Configuring Release Manager on New Servers

This should be a section in a larger, more comprehensive document.

Last modified: 7/20/99 6:13 PM

  1. First of all, check that the Perl language and related libraries are all installed correctly (see the Perl installation document for details of this).
  2. If this machine is currently running the release manager for another hostname/server, then the software is installed and you can skip to configuration (step 6).
  3. Obtain the latest versions of the Perl packages IMS-ReleaseMgr and ReleaseManager from the designated FTP/WWW site (this will be the subject of a future proposal, and will be filled in then).
  4. Install IMS-ReleaseMgr first, as ReleaseManager depends on it.
  5. Now install the ReleaseManager package itself:
  6. Change into the /opt/ims/ahp-bin directory.
  7. If the release manager software is already installed, copy one of the existing configuration files with a new name of "www.example.hp.com" (for examples, we’ll continue to use www.example.hp.com). Assume that the file used was "www.buy.hp.com".
  8. Edit the new file, globally replacing all occurrences of www.buy (or the previous server name), with the leading parts of the hostname for the new server (i.e., less the "hp.com" part). Save the file. See also the special notes at the end regarding the mirror specification database in Oracle.
  9. Make this file executable: "chmod 755 www.example.hp.com"
  10. If this server is not part of a larger pool of mirrored servers, create a zero-length file named www.example.hp.com.mir in the same directory as the first file, then skip ahead to step 12.
  11. Edit the file named www.example.hp.com.mir and insert all the unique server names for all hosts in the mirror pool. These are generally numbered from 1, with the number appended to the www portion of the name. Thus, if there were three machines serving the example server name, they would be called www1.example.hp.com, www2.example.hp.com and www3.example.hp.com. Add these into the file, one name per line. Save the file. See also the special notes at the end regarding the mirror specification database in Oracle.
  12. After changing back to the /opt/ims directory, create a directory named after the server: "mkdir www.example.hp.com".
  13. Change the permissions to allow writing by members of the group (the ownership and group of the new directory should have defaulted to wesadm for both values): "chmod 775 www.example.hp.com".
  14. Change into the new directory and create the following directories: htdocs, cgi-bin, fcgi-bin, local, logs, incoming and staging. Set their permissions as before (mode 775). Depending on the architecture of the system and the layout of certain system resources such as disks, some of these directories may instead be symbolic links to a different directory area on a separate device. If this is the case, simple make certain that the ownership and modes are correct on the physical locations, then link to those locations from this directory using "ln –s" (symbolic links).
  15. Change the group ownership of incoming to wesuser: "chgrp wesuser incoming".
  16. Do the same for logs: "chgrp wesuser logs".
  17. Change into the logs directory ("cd logs") and make a directory called Pushes (note capitalization): "mkdir Pushes".
  18. Change the mode as with the others: "chmod 755 Pushes".
  19. You should now have a directory structure something like (the two values at front are user and group owners, respectively):
  20. __ wesadm.wesadm 775 /opt/ims/www.example.hp.com

    __ wesadm.wesadm 775 /opt/ims/www.example.hp.com/cgi-bin

    __ wesadm.wesadm 775 /opt/ims/www.example.hp.com/fcgi-bin

    __ wesadm.wesadm 775 /opt/ims/www.example.hp.com/htdocs

    __ wesadm.wesuser 775 /opt/ims/www.example.hp.com/incoming

    __ wesadm.wesuser 775 /opt/ims/www.example.hp.com/logs

    __ wesadm.wesadm 775 /opt/ims/www.example.hp.com/logs/Pushes

    __ wesadm.wesadm 775 /opt/ims/www.example.hp.com/staging

  21. If the sysmonitord package is not yet installed, do so according to the documentation on that package (pointer to that documentation). Make sure that sysmonitord is currently running.
  22. Change directory to /opt/ims/local/sysmonitor: "cd /opt/ims/local/sysmonitor".
  23. Add a line to the file syscheck.rc to monitor and restart the release manager process. The restart command should be /opt/ims/ahp-bin/www.example.hp.com, and the path for the semaphore file should be /opt/ims/www.example.hp.com/logs/rlsmgrd.sem (no ahp-bin component). Generally, the unique ID for the rlsmgrd entry is "rlsmgrd_XXX", where XXX is the server name. Thus, rlsmgrd_example in this case.
  24. Instruct the running sysmonitord to re-read the configuration file: "kill -HUP `cat pid`". (The file "pid" should be in the current directory, as you should still be in /opt/ims/local/sysmonitor.)
  25. The monitor daemon should have sent out a mail message noting that rlsmgrd had "failed" (because it wasn’t running). A mail message saying that it had been successfully re-started (in this case, initially started) should follow this.

Adding Mirror Specifications and Host Lists to Oracle

There is now a tool for editing the mirror specification database. It operates on a CGI/HTTP model, and is as secure as can be without using SSL directly. A manual page for the tool is part of the IMS-ReleaseMgr extension package. A link to the tool should probably be put on the webmaster page (where is it thus access-controlled). The tool is called "edit_db.pl", for those with access to the IMS source code.