Solution missing IWOD60HOME for opendeploy & cgi

RonaldV

With much, much thanks and gratitude to Frank Teusink, Amsterdam Netherlands who pointed me to the correct solution!

Following gives you a solution for, what I think is, a (documentation) bug in Opendeploy 6.0 (TS65, Win2k).

When running opendeploy 6.0 from within a custom cgi-perl script you might see this problem (though running the command from the command line works fine):

Cmd: d:\iw-home\OPENDE~1\bin\iwodstart.bat <your pars>
System environment variable IWOD60HOME is not set.
It must be set to the OpenDeploy home directory.
To set, from a DOS window issue: set IWOD60HOME=pathToYourODHome
Example: set IWOD60HOME=C:\iw-home\OpenDeploy
To check, from a DOS window issue: echo %IWOD60HOME%

This is due to that the cgi-environment does not include the IWOD60HOME var, though it is probably set in the windows system-vars. To include the variable in the cgi env add this to httpd.conf.template (iw-wedb/conf) so it says something like this:

#
# For OpenDeploy triggers.  Harmless if OpenDeploy not installed.
#
#<IfModule mod_env.c>
    PassEnv IWODHOME IWODRMIPORT IWOD60HOME
#</IfModule>

AND run iwreset -ui afterwards. To check, run the show_env.cgi and check if the variable shows here.

Hope this will help you, Ronald

TS552, Win2k
OD560

Adam Stoller

Actually, this should probably be reported as a bug in the TeamSite installation (post OD-6 release) in that the new envirionment name should be listed in the httpd.conf.template like the old one is -- I remember filing the request to get those added to the OOTB installation of TeamSite several years ago, it just simply needs to be updated to include *both* the old and the new environment variables that need to be passed through.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com