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; } } }

iwat triggers

Mashuk

Hi,
I am trying to use an iwat trigger to cater for a WorkflowActivate event. I have read documentation on the clt manuals and taken a couple of docs off the support site, but I can't seem to activate the trigger.

Im not sure if I am following the correct procedures but this is what I have done so far:-

On Solaris platform

1) Write a custom wrapper script e.g. "iwat_wfactivate" which lives in the /iw-home/bin directory. As far as Im aware the wrapper script should contain a call such as:

#!/iw-home/iw-perl/bin/iwperl

`/iw-home/bin/iwat WorkflowActivate /iw-home/path/to/my/script`;

2) the next step is to include an entry in the /iw-home/local/config/iwlocal.cfg such as

iwat_wfactivate root /iw-home/path/to/my/script

3)The third step is to stop and restart Teamsite. Following on from that every time I submit a workflow, the WorkflowActivate event should be captured as coded in my custom script.

The above are the assumptions I have used, but at this moment in time the trigger is not working.

On another note how does the iwat clt come into the equation, Im still baffled!

Thanks
Mashuk

Noticed that I have put the iwlocal.cfg file in the wrong directory. should go in the /iw-home/local directory.

Still no joy!

Edited by Mashuk on 07/25/03 06:00 AM (server time).

Find more posts tagged with

Comments

Adam Stoller

There seems to be some confusion here.
If you are using 'iwat' (as opposed to 'iwatxxx' scripts) - you do *not* need to wrap it into another script *nor* do you want to use iwlocal.cfg

Just run the command:
iwat WorkflowActivate /iw-home/path/to/my/script
from the command line

Windows users will probably need to specify the script engine like:
iwat WorkflowActivate c:\iw-home\iw-perl\bin\iwperl c:\iw-home\path\to\my\script

--fish
(Interwoven Senior Technical Consultant)

Mashuk

Thanks Ghoti

The initial procedure I followed was documented in KB article 49977, which explains how to create an iwat trigger for a non-standard event. There seems to be a conflict between your solution and the KB.

But I tried doing as you have said, but still does not work.

I can then check to see if that iwat WorkflowActivate was added to the system as a process by running iwlsat.

However the script I have created does not run. when the WorkflowActivate event takes place. The script is a simple script which just prints out a line to a log file. I have attached the script.

Mashuk

Edited by Mashuk on 07/28/03 02:45 AM (server time).

Sunil Mugalavally

Test to see if the script works on command line like..

/iw-home/iw-perl/bin/iwperl "<path to .ipl>"

Make sure it works here and then try with triggers.

Mashuk

Done that, it works on the command line.

Do i need to stop and re-start Teamsite for the triggers to take effect?

Sunil Mugalavally

You don't need to re-start the server for triggers to apply.
Well, can u post the "iwat"command u run and the result of the "iwlsat" command.
Are you on Windows or solaris?

Mashuk

I am on solaris.

the first command I run is :-
iwat WorkflowActivate /iw-home/custom/bin/iwat_act.ipl

When I run the iwlsat I get:-

ID: 197166 "WorkflowActivate" /iw-home/custom/bin/iwat_act.ipl

Is this what you expect?

jbonifaci

Did you try the following yet?

iwat WorkflowActivate /iw-home/iw-perl/bin/iwperl /iw-home/custom/bin/iwat_act.ipl

Mashuk

If I do that, when I run iwlsat I get the following:-

ID: 190xxx WorkflowActivate /iw-home/iw-perl/bin/iwperl

The path to the script is dropped off, I presume because the iwat command is expecting 2 arguments and not 3, and therefore the path to the script is interpreted as the third argument.

I checked the root profile and the iwperl is included in the $PATH environment variable, therefore it should be fine to just run
iwat WorkflowActivate /path/to/script.ipl

jbonifaci

Can you run just '/path/to/script.ipl' from the command line? or do you need to run 'iwperl /path/to/script.ipl'?

Mashuk

Got it to work now.

I did the following

iwat WorkflowActivate '/iw-home/iw-perl/bin/iwperl /iw-home/custom/bin/iwat_act.ipl'

Thanks for your help

Adam Stoller

Windows requires that you provide the 'engine' for the script.
Unix requires that the script is executable and that the #! line at the beginning point to the engine for the script.

Glad you got it working.

The KB you referred to was, I believe, intended for CLT functionality that wasn't otherwise within a script - the example I've heard of most recently was for using the xcopy command. Someone was having trouble getting:

iwat pattern xcopy arguments

to work - so they put the
xcopy arguments
into a perl script and did
iwat pattern path-to-iwperl path-to-script
and that seemed to resolve the problem
(I only have sketchy details because this is 3rd-hand knowledge)

--fish
(Interwoven Senior Technical Consultant)