Is there an equivalent //ODHOME just like the //IWSERVER token?

Hi,

I know you can specify "//IWSERVER" as a special token in a deployment configuration's area="...." attribute and OpenDeploy will magically replace it with the right mount point for the backing store (e.g. "Y:/")

Is there an equivalent magic token for the "$odhome" localtion (e.g. "C:/Interwoven/OpenDeployNG") ??

This would be super handy for filelist deployments where one's external processes are creating all sorts of filelist-$jobid.txt files under the $ODHOME/tmp directory. To paramaterize the OD configuration, you wouldn't need to specify something like "-k $filelist_loc=C:/Interwoven/OpenDeploy/tmp/filelist-123.txt", you could just 'hardcode' the "//ODHOME" magic key in your configuration file and then have a more portable "-k $filelist_loc=tmp/filelist-123.txt" parameter.

Anything like that exist?

Find more posts tagged with

Comments

nipper

This is code I cut from wft_opendeploy.ipl


if ($^O eq "MSWin32" ) { 
    $OD_DIR = &canonicalizePath($ENV{IWOD60HOME});
    $PATH_SEPERATOR = "\\";
} else {
   # reads the /etc/defaultiwod60home file to get the ODHOME
   $PATH_SEPERATOR = "/";
   my($odhomeConfigFile)="/etc/defaultiwod60home";
   if ( ! (-r "$odhomeConfigFile") ) {
        debug("$dbgInfo", " Unable to find the $odhomeConfigFile  '\n");
        # ::TODO:: probably should callback-and-die here
   }
   open (READIN, "<$odhomeConfigFile");
   while ()
   {
      chomp($_);
      $OD_DIR = $_;
      last;
   }
   close READIN;

Net answer is there is an environment variable you can use. If you are using Perl, you can read /etc/defaultodhome on Solaris or Linux

Of course now that I reread your post, I really did not answer it too well. :eek:

AchasPercent.rptdesign.tar.gz

Adam Stoller

Hi,

I know you can specify "//IWSERVER" as a special token in a deployment configuration's area="...." attribute and OpenDeploy will magically replace it with the right mount point for the backing store (e.g. "Y:/")

Is there an equivalent magic token for the "$odhome" localtion (e.g. "C:/Interwoven/OpenDeployNG") ??

This would be super handy for filelist deployments where one's external processes are creating all sorts of filelist-$jobid.txt files under the $ODHOME/tmp directory. To paramaterize the OD configuration, you wouldn't need to specify something like "-k $filelist_loc=C:/Interwoven/OpenDeploy/tmp/filelist-123.txt", you could just 'hardcode' the "//ODHOME" magic key in your configuration file and then have a more portable "-k $filelist_loc=tmp/filelist-123.txt" parameter.

Anything like that exist?

In short - no - there is no single all-purpose magic cookie that you can use for this in a portable fashion.

That being said - if you're on Windows - you can use a wrapper script for your deployments that will use the value from $ENV{IWOD60HOME} - and if you're on Unix you can retrieve the value from the contents of /etc/defaultiwod60home (similar to the code that was posted).

You might consider opening up a feature request with IWOV Support (this kind of thing has come up before for various parts of various IWOV products - so there might already be a FR logged, that you can get your organization's name added to)