Related Documents

• SSWDB Description and Site Configuration
• SolarSoft Installation
• SolarSoft Upgrades

At a low level, this procedure is simular to the SSW software upgrade procedure in that the Perl application Mirror is used. The local SolarSoft environment is examined and SSW IDL routines are used to generate the appropriate Mirror Packages implied by your site configuration files. Dynamic and automatic regeneration of the packages in terms of your local SSW environmental path definitions permits single point additions, removals or relocations of SSW instrument branches and SSWDB data base files. See the SSW software upgrade document for more details.

SSWDB Configuration and Installation

1. Fill out the SSWDB Configuration FORM That FORM includes simple descriptions of each of the available databases and the current data base size. ( Some interaction with an instrument specialist may be required to determine which data bases you need for a given type of data analysis )

   Select SSWDB sets you wish to install and maintain at your site. When the FORM is submitted, the WWW server will generate a customized ascii data file listing the desired data bases. The FORM configuration and submit step can be repeated as desired since no action at your site is taken - for example, you can check sizes of various SSWDB configurations

2. Copy the WWW generated configuration file to your local SSW disk, into SSW directory $SSW/site/setup (a hyper-link to the ascii file will show up after you submit your FORM in the preceeding step)

3. Execute the sswdb installation by running the appropriate SSW ( SSW-IDL) command. The low level installation/upgrade routine is sswdb_upgrade.pro. If no parameters (data base sets) are input, it will look for the site configuration file: $SSW/site/setup/setup.sswdb_upgrade which was generated and copied in the previous steps.

   The accepted calling sequences are:

   IDL> sswdb_upgrade [,/spawn] ; Use SITE configuration file
   -OR-
   IDL> sswdb_upgrade,DBSETS [,/spawn] ; Use user specified DBSETS vector

   When calling sswdb_upgrade, the /SPAWN switch is required to actually execute the mirror - leaving the /SPAWN switch off will just generate the mirror package but not execute it (useful for testing or mirroring at a later date) ( analogous to use of /SPAWN switch in the sister routine for software upgrades ssw_upgrade.pro ) [see the sswdb_upgrade IDL documentation header for additional keyword options and permissible formats for DBSETS]

4. It is highly recommended that remote sites keep SSW and SSWDB systems current. The program go_update_ssw includes calls to ssw_upgrade and sswdb_upgrade to simplify customized updates based on the local site configuration files for SSW and SSWDB. It is designed to run as a background job, since updating the software and data bases is not typically done interactively. The use of go_update_ssw routine in a cron is described in the SolarSoft upgrade document

For comments and suggestions regarding this document: freeland@sxt1.lmsal.com