nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Selective loads of PM ?

nipper

OK, I am working on an all purpose DNR for TS/LS

If it is on a TS server & I send out a new jar file I want to run build.sh (or .bat) if it is a prod server I want to restart LS. Unix and DOS.

So my first issue is that I do not want to hard code the OD library path. I tried setting $OD_HOME and using

use lib $OD_HOME."/solutions/perl";

But that did not work (INC was /solutions/perl)

The other thing is how can I tell if this is running on a TS server ? There is not an ENV set like IWOD60HOME on DOS. Maybe try to load TeamSite::Config in a block and if it errors ?

Other ideas ?

Find more posts tagged with

Comments

ISCBorisB

OK, I am working on an all purpose DNR for TS/LS

If it is on a TS server & I send out a new jar file I want to run build.sh (or .bat) if it is a prod server I want to restart LS. Unix and DOS.

So my first issue is that I do not want to hard code the OD library path. I tried setting $OD_HOME and using

use lib $OD_HOME."/solutions/perl";

But that did not work (INC was /solutions/perl)

The other thing is how can I tell if this is running on a TS server ? There is not an ENV set like IWOD60HOME on DOS. Maybe try to load TeamSite::Config in a block and if it errors ?

Other ideas ?

Environment Variables may be tricky in DNR. TS often wipes out Env and sets it's own collection, perhaps OD does something similar.

If I were you I would've considered passing OD Location, TS/LS Flag and whatnot as Script Parameters. Then you can pass values using -k
from OD Configuration - after all on that level you know what is the Target. Not as elegant as "self-sufficient" code but...

Adam Stoller

OK, I am working on an all purpose DNR for TS/LS

If it is on a TS server & I send out a new jar file I want to run build.sh (or .bat) if it is a prod server I want to restart LS. Unix and DOS.

So my first issue is that I do not want to hard code the OD library path. I tried setting $OD_HOME and using

use lib $OD_HOME."/solutions/perl";

But that did not work (INC was /solutions/perl)

The other thing is how can I tell if this is running on a TS server ? There is not an ENV set like IWOD60HOME on DOS. Maybe try to load TeamSite::Config in a block and if it errors ?

Other ideas ?

]For Using ODHOME to dynamcially augment the INC path, I believe you would need something like*:

...
BEGIN {
    my $odhome = getodhome(); # routine for determining ODHOME regardless of platform
    eval(qq(use lib "$odhome/solutions/perl"));
};
...

For determining if this is running on a TS server... well on Unix you can check the existence of

/etc/defaultiwhome

. On Windows, perhaps check the existence of

Y:/default/main

- or testing the loading of

TeamSite::Config

as you suggested ... however ... isn't there an issue here which kind of excludes being able to do this generically (at least on Unix):

Personally, I'd probably just keep 2 scripts in my toolbag - one for being run on a TS server, and one for being run on a non-TS server - and just copy it into place with the correct #! line as needed.

nipper

I use a smart shebang line to help between Unix/DOS. I know it may not work all times, but it is a start. I thought what I was trying was a pipe dream, but I truly do want this as portable as possible. I know it won't be perfect but I am going to make it as easy to transport as possible.

Andy

SampleData4Birt.xlsx

second x-axis.rptdesign

Adam Stoller

I use a smart shebang line to help between Unix/DOS. I know it may not work all times, but it is a start. I thought what I was trying was a pipe dream, but I truly do want this as portable as possible. I know it won't be perfect but I am going to make it as easy to transport as possible.

Andy

Okay - but does the code with the eval within the BEGIN block solve your issue with including the OD Perl module?

vpatel

IMHO, your best bet is going to be to have a properties/config file for your DnR. There are just too many things that could get out of sync. Alternatively, you could enforce (and assume) a consistent installation process across all of your environments (i.e. if it is unix then iw-home is /opt/Interwoven/TeamSite and if it is Windows C:\Interwoven\TeamSite).

I also pondered the idea of verifying this information through some sort of a service or something. In that case you still have dependency on service name, port, etc. -- which could change (at least in theory) from one server to another.

Config/properties file or consistency is probably going to be your friend here :-)

nipper

Config/properties file or consistency is probably going to be your friend here :-)

And since you go to maybe twice the number of clients (OK, probably more than twice) that I do, how would you feel about banking on your old buddy Mr. Consistency ?

vpatel

And since you go to maybe twice the number of clients (OK, probably more than twice) that I do, how would you feel about banking on your old buddy Mr. Consistency ?

If the stakeholders are extremely-well-disciplined then probably :-)! Unless they are willing to accept the consequences from their mistakes / inconsistencies you can forget about it :-)!

Report.jpg

DataCube.jpg