Steps to use command triggers

Hi,

i am trying to use command triggers.

Need to invoke custom script when a file is unlocked.

Followed the below steps:
1) login as su
2) edit /iw-home/local/iwlocal.cfg
3) made entry
iwatunlock nagendra unlocked.pl
4) Placed unlocked.pl in /iw-home/local
4) /etc/init.d/iw.local stop
5) /etc/init.d/iw.local start
6) ensured iwevents.log has 775 permissions
8) login into workarea
7) unlocked the file in workarea

but no execution of unlocked.pl happend :-((

if I use following command at prompt then execution of the script is happening
/iw-home/iw-perl/bin/iwperl /iw-home/bin/iwatunlock.ipl "/iw-home/local/unlocked.pl &"

Can anyone help me to understand the use of iwlocal.cfg & iwat?
what went wrong in my first set of steps?

-nagendra

Is /iw-home/local/unlocked.pl File executable? If not - chmod 751 (or whatever is required by your environment).
Does it have proper perl shebang in the first line?
To check it all, simply try to run the script from somewhere as a command, without perl, iwperl, etc...

Migrateduser

I think the problem is that you entered iwatunlock nagendra unlocked.pl into your iw.cfg file. You don't need an entry for this in your iw.cfg file. You need to run the following from a command prompt.

iwperl iwatunlock.ipl nagendra unlocked.pl

I think the problem is that you entered iwatunlock nagendra unlocked.pl into your iw.cfg file.

He did not. He entered it in iwlocal.cfg that a) is a proper place to do it and b) Does not exist in Windows
One of that places in TS where configuration is not cross-platform portable

Migrateduser

Ahhh.... since I'm not running on Unix I didn't realize that. Thanks for the heads up. Always good to learn something new.

In that case, I think you're probably correct about the permissions being a possible culprit. I would assume that Teamsite is running under a different account (on Unix) than what he is logged in with when he runs it manually.

I suggest you find the actual event that is created when you unlock a file (probably UNLOCK but I haven't checked) - and then use iwat (RTM Command Line Utilities manual for more info) to register a command to run when the event occurs.

The older iwat**** utilities require that services be created and maintained - the newer iwat utility registers the command in the backing store and is much easier to deal with.

unlocked.pl file has proper permissions to exectue.

"I would assume that Teamsite is running under a different account (on Unix) than what he is logged in with when he runs it manually." - yes

teamsite is running as
root 23909 0.0 5.5239592219040 ? S Sep 29 611:18 iwserver.sol -e /apps/iwevents.log /data/software/iw/iw-store

I logged in as nagendra while running the iwat.... on command prompt - it worked fine.

But

for iwlocal.cfg activity I have logged in as nagendra in teamsite workarea still script did not exectued.

-nagendra

The older iwat**** utilities require that services be created and maintained - the newer iwat utility registers the command in the backing store and is much easier to deal with.

There are cases where dedicated trigger offers serious advantage. To the best of my knowledge iwat does not
always set certain event-specific environment variables. By far the most important of those is Event Object ID.
Couple times I had to obtain/parse Event Object as the only way to get required event details.

That said, these cases are rear and far between. Iwat is much easier to set and maintain

unlocked.pl file has proper permissions to exectue.

"I would assume that Teamsite is running under a different account (on Unix) than what he is logged in with when he runs it manually." - yes

teamsite is running as
root 23909 0.0 5.5239592219040 ? S Sep 29 611:18 iwserver.sol -e /apps/iwevents.log /data/software/iw/iw-store

I logged in as nagendra while running the iwat.... on command prompt - it worked fine.

But

for iwlocal.cfg activity I have logged in as nagendra in teamsite workarea still script did not exectued.

-nagendra

Please post the following:

logged as you, you should be able to run the command exactly as you entered it in iwlocal(in your case without perl. iwperl, etc....)

could anybody post their iwlocal.cfg file?
so that I can compare

which one of the following is the correct entry for a custom script to register

iwatunlock nagendra unlocked.pl
iwatunlock nagendra /iw-home/local/unlocked.pl
iwatunlock nagendra /iw-home/bin/iwatunlock.ipl "/iw-home/local/unlocked.pl &"
iwatunlock nagendra /iw-home/bin/iwatunlock.ipl /iw-home/local/unlocked.pl
iwatunlock nagendra /iw-home/bin/iwatunlock.ipl "unlocked.pl &"

iw_store

He did not. He entered it in iwlocal.cfg that a) is a proper place to do it and b) Does not exist in Windows
One of that places in TS where configuration is not cross-platform portable

Hi,

Just a question here..

If this needs to be done in windows, then what is the event registaration file is it iw.cfg or some other file.

[size=2]As iwlocal.cfg does not exist in windows.. [/size]

Hi,

Just a question here..

If this needs to be done in windows, then what is the event registaration file is it iw.cfg or some other file.

[size=2]As iwlocal.cfg does not exist in windows.. [/size]

Read the manuals - you have to create services out of them and register them with Windows and then make sure the services are running.

Again - unless you run into something that requires some aspect of the iwatxxx that doesn't exist by using iwat - I suggest just using iwat (note there is a difference in the way they get arguments, iwatxxx uses environment variables, iwat uses command-line parameters [e.g.: @ARGV])

could anybody post their iwlocal.cfg file?
so that I can compare

which one of the following is the correct entry for a custom script to register

iwatunlock nagendra unlocked.pl
iwatunlock nagendra /iw-home/local/unlocked.pl
iwatunlock nagendra /iw-home/bin/iwatunlock.ipl "/iw-home/local/unlocked.pl &"
iwatunlock nagendra /iw-home/bin/iwatunlock.ipl /iw-home/local/unlocked.pl
iwatunlock nagendra /iw-home/bin/iwatunlock.ipl "unlocked.pl &"

You should use #1 or #2 for registration in iwlocal.cfg. It will work if both of the following conditions are met:

1. File mode includes "executable", eg "ls -l unlocked.pl" shows something akin to
-rwxr-x--x 1 foo moo 99999 unlocked.pl

AND

2. You have correct Perl shebang in your "unlocked.pl" script, something like
#!/iw-home/iw-perl/bin/iwperl

TestReport.rptdesign

I have following setup (solaris 9 ts 6.5 sp 2)

ecoapp24-lgs: ls -al /data/software/iw/iw-home/local/iwlocal.cfg
-rwxrwxrwx 1 root other 31 Oct 17 10:41 /data/software/iw/iw-home/local/iwlocal.cfg

ecoapp24-lgs: more /data/software/iw/iw-home/local/iwlocal.cfg
iwatunlock kumarn35 unlocked.pl

ecoapp24-lgs: ls -al /data/software/iw/iw-home/local/unlocked.pl
-rwxrwxr-x 1 kumarn35 iwadmin 377 Oct 14 13:33 /data/software/iw/iw-home/local/unlocked.pl

ecoapp24-lgs: ls -al /data/software/iw/iw-home/local/bin/unlocked.pl
-rwxrwxr-x 1 kumarn35 iwadmin 377 Oct 14 13:33 /data/software/iw/iw-home/local/bin/unlocked.pl

ecoapp24-lgs: more /data/software/iw/iw-home/local/unlocked.pl
#!/data/software/iw/iw-home/iw-perl/bin/iwperl -w
use TeamSite::Config;
my $iwhome = TeamSite::Config::iwgethome(); # Get the iw-home from environment

if (open(TXT,">>$iwhome/local/unlocked.log")) {
print TXT ("==========================================" . "\n");
my $numArgs = $#ARGV + 1;
foreach $argnum (0 .. $#ARGV) {
print TXT "$ARGV[$argnum]\n";
}
}
close(TXT);

ecoapp24-lgs: ls -al /etc/init.d/iw.local
-rwxrwxr-x 4 root daemon 6596 Sep 29 2004 /etc/init.d/iw.local

ecoapp24-lgs: /etc/init.d/iw.local stop
ecoapp24-lgs: /etc/init.d/iw.local start

ecoapp24-lgs: ls -al /data/software/iw/iw-home/local/.pids
total 4
drwx------ 2 root root 512 Oct 17 10:44 .
drwxrwxrwx 10 root daemon 1024 Oct 17 10:41 ..

ecoapp24-lgs: tail -2f /apps/iwevents.log
[Tue Oct 17 10:47:02 2006] kumarn35 editor Lock /default/main/bt/btw/portal/13_CR36383963/WORKAREA/content
/templatedata/content/binary/datacapture.cfg 0x00001008453399f34000063e kumarn35
[Tue Oct 17 10:47:07 2006] kumarn35 editor UnLock /default/main/bt/btw/portal/13_CR36383963/WORKAREA/content
/templatedata/content/binary/datacapture.cfg 0x00001008453399f34000063e kumarn35

ecoapp24-lgs: tail -10f /data/software/iw/iw-home/local/unlocked.log
tail: cannot open input

Inspite of above all things are properly setup
i am unable to get the triggers working. :-(

I have following setup (solaris 9 ts 6.5 sp 2)

ecoapp24-lgs: ls -al /data/software/iw/iw-home/local/iwlocal.cfg
-rwxrwxrwx 1 root other 31 Oct 17 10:41 /data/software/iw/iw-home/local/iwlocal.cfg

ecoapp24-lgs: more /data/software/iw/iw-home/local/iwlocal.cfg
iwatunlock kumarn35 unlocked.pl

Could you post the output of: cat -vte /data/software/iw/iw-home/local/iwlocal.cfg?
Also, you might want to try listing the full path to the script there - despite the documentation saying that the default location is iwhome/local.

ecoapp24-lgs: ls -al /data/software/iw/iw-home/local/unlocked.pl
-rwxrwxr-x 1 kumarn35 iwadmin 377 Oct 14 13:33 /data/software/iw/iw-home/local/unlocked.pl

ecoapp24-lgs: ls -al /data/software/iw/iw-home/local/bin/unlocked.pl
-rwxrwxr-x 1 kumarn35 iwadmin 377 Oct 14 13:33 /data/software/iw/iw-home/local/bin/unlocked.pl

ecoapp24-lgs: more /data/software/iw/iw-home/local/unlocked.pl
#!/data/software/iw/iw-home/iw-perl/bin/iwperl -w
use TeamSite::Config;
my $iwhome = TeamSite::Config::iwgethome(); # Get the iw-home from environment

if (open(TXT,">>$iwhome/local/unlocked.log")) {
print TXT ("==========================================" . "\n");
my $numArgs = $#ARGV + 1;
foreach $argnum (0 .. $#ARGV) {
print TXT "$ARGV[$argnum]\n";
}
}
close(TXT);

Besides some stylistic changes I could recommend - the one thing you haven't shown is the protections on the iwhome/local directory itself - since you are attempting to write a log file there - you need to make sure that you have the access to do so (which you might, but it isn't clear from the data you presented.

As for code changes (maybe I'm bored - but this is a simple script right now):

#!/data/software/iw/iw-home/iw-perl/bin/iwperl
use strict;
use warnings;
use TeamSite::Config;
my $iwhome = TeamSite::Config::iwgethome(); # Get the iw-home from environment

if (open(TXT,">>$iwhome/local/unlocked.log")) {
        print TXT '=' x 70 . "\n";
        print TXT "ARG: $_\n" foreach(@ARGV);
        print TXT "ENV: $_ => $ENV{$_}\n" foreach(sort(keys(%ENV)));
        close(TXT);
}
else {
    die " '$iwhome/local/unlocked.log' ($!)";
}

ecoapp24-lgs: ls -al /etc/init.d/iw.local
-rwxrwxr-x 4 root daemon 6596 Sep 29 2004 /etc/init.d/iw.local

ecoapp24-lgs: /etc/init.d/iw.local stop
ecoapp24-lgs: /etc/init.d/iw.local start

ecoapp24-lgs: ls -al /data/software/iw/iw-home/local/.pids
total 4
drwx------ 2 root root 512 Oct 17 10:44 .
drwxrwxrwx 10 root daemon 1024 Oct 17 10:41 ..

ecoapp24-lgs: tail -2f /apps/iwevents.log
[Tue Oct 17 10:47:02 2006] kumarn35 editor Lock /default/main/bt/btw/portal/13_CR36383963/WORKAREA/content
/templatedata/content/binary/datacapture.cfg 0x00001008453399f34000063e kumarn35
[Tue Oct 17 10:47:07 2006] kumarn35 editor UnLock /default/main/bt/btw/portal/13_CR36383963/WORKAREA/content
/templatedata/content/binary/datacapture.cfg 0x00001008453399f34000063e kumarn35

ecoapp24-lgs: tail -10f /data/software/iw/iw-home/local/unlocked.log
tail: cannot open input

Hope the above helps.
As I mentioned before, I tend to use iwat over things like iwatunlock because I find it easier and generally more reliable - but feel free to keep trying it this way if you feel so inclined.

here it is

ecoapp24-lgs: cat -vte /data/software/iw/iw-home/local/iwlocal.cfg
iwatunlock^Ikumarn35^I/data/software/iw/iw-home/local/unlocked.pl

ecoapp24-lgs: ls -al /data/software/iw/iw-home/local
total 52
drwxrwxrwx 10 root daemon 1024 Oct 17 16:02 .
drwxrwxr-x 41 root bin 1024 Oct 14 09:58 ..

I have updated the unlocked.pl also

here is the output when I run as kumarn35 on prompt

ecoapp24-lgs: /data/software/iw/iw-home/iw-perl/bin/iwperl /data/software/iw/iw-home/local/unlocked.pl
ecoapp24-lgs: tail -10f /data/software/iw/iw-home/local/unlocked.log
ENV: _INIT_PREV_LEVEL => S
ENV: _INIT_RUN_LEVEL => 3
ENV: _INIT_RUN_NPREV => 0
ENV: _INIT_UTS_ISA => sparc
ENV: _INIT_UTS_MACHINE => sun4u
ENV: _INIT_UTS_NODENAME => ecoapp24-lgs
ENV: _INIT_UTS_PLATFORM => SUNW,Sun-Fire-280R
ENV: _INIT_UTS_RELEASE => 5.8
ENV: _INIT_UTS_SYSNAME => SunOS
ENV: _INIT_UTS_VERSION => Generic_108528-27

/etc/init.d/iw.local stop
/etc/init.d/iw.local start

unlocked the file in workarea

here is the output when I run as kumarn35 on prompt

ecoapp24-lgs: /data/software/iw/iw-home/iw-perl/bin/iwperl /data/software/iw/iw-home/local/unlocked.pl

You keep doing your *sanity check* with Perl, meanwhile your iwlocal.cfg entry does not contain Perl reference. Your setting is to run unlocked.pl.
There are (or rather may be) subtle differenceies with running iwperl from shell or from shebang (Perl interpreter may have sticky bit, "Run as..." flag, etc)

What happens if you log in as "kumarn35" and simply type on prompt
ecoapp24-lgs: /data/software/iw/iw-home/local/unlocked.pl
and hit <Enter>? Does it work? If it does not either fix it, whatever "it" is or put the full command in iwlocal. Like that:

iwatunlock kumarn35 /data/software/iw/iw-home/iw-perl/bin/iwperl /data/software/iw/iw-home/local/unlocked.pl
Please note the complete absence of iwatunlock.ipl here, that's how it should be