Changes between Initial Version and Version 1 of InstallVSO

Timestamp:

07/27/12 13:36:16 (12 years ago)

Author:

joe

Comment:

--

InstallVSO

@@ +1 @@
+= Installing VSO =
+
+Due to some concerns from the legal folks regarding distribution of software, the instructions are intentionally missing a key variable -- the location of the 'DarkPAN' site that you need to pull the software from.  Please contact [people/JoeHourcle Joe Hourclé] if you're interested (and so we can get feedback to improve these instructions).
+
+== VSO Install Script ==
+
+First, download the shell script that'll do 90% (ish) of the work:
+
+{{{
+wget http://sdac.virtualsolar.org/Installers/install_vso.sh
+}}}
+
+Modify the file as appropriate so it'll install where you want, and knows about the super-secret place where the VSO perl scripts are.  I'd also recommend that you look over what the script's doing, as it's generally a bad idea to just download stuff from the internet and run it.  (also, it's going to download a [http://sdac.virtualsolar.org/Installers/ConfigAll.PL Perl script] part way through and run it to set up all of the local configuration bits)
+
+== The Manual Bits ==
+
+
+For everyone:
+
+1. Make it so the webserver can see the static HTML files.
+
+  (I'm assuming you have it being told that the static files are it something like `http://server/vso`, and they're locally in `/opt/vso/html`, and the webserver root is `/var/www/html`)
+
+  Depending on your webserver's security, you might be able to just symlink it in:
+
+ {{{
+   ln -s /opt/vso/html /var/www/html/vso 
+}}}
+
+  But if you don't allow symlinks, you can define an alias in either `httpd.conf` or the appropriate `site/*.conf` file for that virtual host:
+
+{{{
+    Alias /vso/ /opt/vso/html
+}}}
+
+  But that might not work if you followed the CIS benchmarks to the letter (not allowing access to files outside of the web root), so in that case, just copy 'em in place:
+
+{{{
+cp -r /opt/vso/html /var/www/html/vso
+}}}
+
+2. Put all of the CGIs in place
+
+  First, you're going to have to decide which set of CGIs you're going to use, as there's multiple versions of most of 'em.
+
+  Like before, you can either symlink into `/var/www/cgi-bin/vso` add a `ScriptAlias` directive  (Alias + designate as CGI) to the webserver config, or just copy 'em in place
+
+  If you're using Fast CGI (and you've already installed the FCGI perl module, if not, run `cpanm FCGI`), you will need the following files:
+
+{{{
+        cartfi.cgi       -> carti
+        cartufi.pl       -> cartui
+        searchFormufi.pl -> search
+        show_details.pl  -> show_details
+        vsoufi.cgi       -> vsoui
+        vsofi.cgi        -> vsoi
+
+        (optional bits)
+        catalogufi.pl     -> catalog
+        vsofi_wsdl.cgi    -> vsoi_wsdl
+        vsoi_tabdelim.cgi -> vsoi_tabdelim
+}}}
+
+ If you're using mod_perl ... contact me, as it looks like they're not all packed in.
+
+ If you're using basic CGI:
+
+{{{
+        carti.cgi       -> carti
+        cartui.pl       -> cartui
+        searchForm.pl   -> search
+        show_details.pl -> show_details
+        vsoui.cgi       -> vsoui
+        vsoi.cgi        -> vsoi
+
+        (optional bits)
+        catalog.pl        -> catalog
+        vsoi_wsdl.cgi     -> vsoi_wsdl
+        vsoi_tabdelim.cgi -> vsoi_tabdelim
+}}}
+
+ It's very likely that the files won't parse clean, because we've put the perl libraries in a strange place. So, you'll need to pop them open, and add the following line (adjusted to your system):
+
+{{{
+use lib '/opt/vso/lib/perl5';
+}}}
+
+ You can then check the files using the command:
+
+{{{
+perl -wc filename
+}}}
+
+ If you get a `Can't locate` message, check to make sure that the `@INC contains:` bit includes what you have listed in the `use lib` line.  If it's still got problems, [People/JoeHourcle  e-mail me].
+
+3. Modify the `webui_config.xml` file so it knows about itself:
+  (note to self -- automate this part, as it should all come from the config, and we need to trim out the old bits)
+
+ edit : `/opt/vso/etc/webui_config.xml`
+
+ add a `'<server>'` block to describe the instance.  You'll want to use whatever you set for `INSTANCE_ID` as the `'name'`
+ The version number doesn't really matter.
+
+ then look for the `<version>` block ... change it so that only your instance ID is listed in there as a `'<current>'` element.  (or add it in, and it'll round-robin)'