The Version Tool is this simple perl script that works in conjunction with a version file to put a timestamp on zipped up versions of all of the Essbase objects in an app subdirectory. In this version of version.pl which is simpler than I thought - I'll have to dig for the more expansive one - it handles single database BSO cubes.
Note that you need to modify the following snippet of code first off to assign the proper notifications and data paths.
$errdir="d:\\hyperion\\essbase\\logs\\"; $recipients='[email protected]';
$logdir="d:\\hyperion\\essbase\\logs\\";
$expdir="d:\\hyperion\\essbase\\export\\";
$tmpdir="d:\\hyperion\\essbase\\export\\temp\\";
$appdir="d:\\hyperion\\analyticservices\\app\\";
$scrdir="d:\\hyperion\\essbase\\batch\\";
$inpdir="d:\\hyperion\\essbase\\batch\\input\\";
$bindir="d:\\hyperion\\essbase\\bin\\";
$logfile="$logdir"."version_activity.log";
Then you'll have to change the parameters that you will allow for the named applications & cubes that you wish to version:
switch ($appid) {
case "back" {$type=1; }
case "hr" {$xapp="HR"; $db="HR"; $type = 2; }
case "gl" {$xapp="GL"; $db="GL"; $type = 2; }
else {$type = 0; }
}
In this case you have two single BSO cubes named HR:HR and GL:GL respectively. 'Back' is for versioning your backend itself. As I said, I'll lookup and find the code for ASO and multicube BSO shortly. That means I may have to start learning how to use Sourceforge. We'll see.
Also note that you need to have 7zip on the path.
Comments