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 trigger to capture workflow being ended

tanguyr

Hello,

I need to notify users if a workflow they started was ended (via the "end job" option in the Workflow tab of CCPro). I am trying to do this using an iwat trigger, but it doesn't seem to "see" the event fired when the workflow ends.

I've tried this:


iwat "WorkflowInactivate" "/usr/bin/touch /tmp/iwat_wfinactiv.txt"

and i can see this trigger in the output from the iwlsat command.

I then start a workflow, switch to the workflow tab, select it and end it - but no file "/tmp/iwat_wfinactiv.txt" shows up. I do see the following line in my $IW-HOME/local/logs/iwevents.log file:


[Tue Feb 10 17:02:00 2009]      trademak        master  WorkflowInactivate      workflow        Approval, translation and submitting workflow   0x42d41

After reading http://devnet.interwoven.com/forums_vb/showpost.php?p=100815&postcount=14, i did a simple test with:


iwat "Thaw" "/usr/bin/touch /tmp/iwatthaw.txt"

and then ran the iwfreeze -- command - this works just fine (file "/tmp/iwatthaw.txt" is created if it didn't exist, and the timestamp is updated if it did exist)

Any pointers? What am i doing wrong?

Regs,
/t

Find more posts tagged with

Comments

Adam Stoller

It looks right from what you posted - the only thing I can think of is that maybe you have a typo somewhere in your command line when you registered the trigger event...

ISCBorisB

It *looks* like TS does not fire any Event when WF is forcefully terminated from GUI ( I was surprised to see that according to your post it still logs it though ).
You may want to check by doing something like iwat ".+" YourEventLogger in the controlled Environment

tanguyr

It looks right from what you posted - the only thing I can think of is that maybe you have a typo somewhere in your command line when you registered the trigger event...

Hello Ghoti,

Thanks for your answer - i checked again to make sure, and it looks good to me:


root@bewcmd01 - /opt/interwoven/iw-home/local
# iwlsat
ID: 184758      "WorkflowInactivate"    /usr/bin/touch /tmp/iwat_wfinactiv.txt
ID: 184805      "Thaw"  /usr/bin/touch /tmp/iwatthaw.txt
root@bewcmd01 - /opt/interwoven/iw-home/local
# grep WorkflowInactivate logs/iwevents.log
[Mon Feb  9 15:05:09 2009]      trademak        master  WorkflowInactivate      workflow        Direct Deploy and submit workflow       0x41864
[Mon Feb  9 15:08:07 2009]      trademak        master  WorkflowInactivate      workflow        Direct Deploy and submit workflow       0x421a4
[Mon Feb  9 15:17:35 2009]      trademak        master  WorkflowInactivate      workflow        Approval, translation and submitting workflow   0x42b09
[Mon Feb  9 15:47:30 2009]      gvanhamm        master  WorkflowInactivate      workflow        Direct Deploy and submit workflow       0x42b31
[Mon Feb  9 15:53:08 2009]      gvanhamm        master  WorkflowInactivate      workflow        Direct Deploy and submit workflow       0x42b57
[Mon Feb  9 15:58:04 2009]      gvanhamm        master  WorkflowInactivate      workflow        Direct Deploy and submit workflow       0x42b84
[Mon Feb  9 15:58:19 2009]      gvanhamm        master  WorkflowInactivate      workflow        Direct Deploy and submit workflow       0x42bb1
[Mon Feb  9 16:00:08 2009]      gvanhamm        master  WorkflowInactivate      workflow        Direct Deploy and submit workflow       0x42bd7
[Mon Feb  9 16:00:29 2009]      gvanhamm        master  WorkflowInactivate      workflow        Direct Deploy and submit workflow       0x42bfe
[Mon Feb  9 16:02:21 2009]      gvanhamm        master  WorkflowInactivate      workflow        Direct Deploy and submit workflow       0x42c24
[Tue Feb 10 16:16:44 2009]      trademak        master  WorkflowInactivate      workflow        Approval, translation and submitting workflow   0x42c4a
[Tue Feb 10 16:21:08 2009]      trademak        master  WorkflowInactivate      workflow        Approval, translation and submitting workflow   0x42c8c
[Tue Feb 10 16:46:18 2009]      trademak        master  WorkflowInactivate      workflow        Approval, translation and submitting workflow   0x42d00
[Tue Feb 10 17:02:00 2009]      trademak        master  WorkflowInactivate      workflow        Approval, translation and submitting workflow   0x42d41
root@bewcmd01 - /opt/interwoven/iw-home/local
# ls -l /tmp/iwat_wfinactiv.txt
/tmp/iwat_wfinactiv.txt: No such file or directory
root@bewcmd01 - /opt/interwoven/iw-home/local
# /usr/bin/touch /tmp/iwat_wfinactiv.txt
root@bewcmd01 - /opt/interwoven/iw-home/local
# ls -l /tmp/iwat_wfinactiv.txt
-rw-rw-r--   1 root     root           0 Feb 10 18:02 /tmp/iwat_wfinactiv.txt
root@bewcmd01 - /opt/interwoven/iw-home/local
# ls -l /tmp/iwatthaw.txt
/tmp/iwatthaw.txt: No such file or directory
root@bewcmd01 - /opt/interwoven/iw-home/local
# iwfreeze --
All stores unfrozen.
root@bewcmd01 - /opt/interwoven/iw-home/local
# ls -l /tmp/iwatthaw.txt
-rw-rw-r--   1 root     root           0 Feb 10 18:03 /tmp/iwatthaw.txt

Regards,
/t

tanguyr

It *looks* like TS does not fire any Event when WF is forcefully terminated from GUI ( I was surprised to see that according to your post it still logs it though ).
You may want to check by doing something like iwat ".+" YourEventLogger in the controlled Environment

Hello ISCBorisB,

Thanks for the suggestion, i will try it and get back to the forum with the results.

My understanding (which seems to be incorrect) is that triggers basically work by effectively tailing the iwevents.log file looking for a match in the event column (i get this through a squinty one eyed reading of "Starting Command Triggers" in the TeamSite Command-Line Tools ref, which states that "Each trigger that is invoked tails the event log and responds to different events" and, later in the same section, "...(note: this user must have read permissions to iwevents.log)". This is what is throwing me for a loop: iwat can see the "Thaw" event but not the "WorkflowInactivate" one.

Do you know where i can see which events are actually being fired, as opposed to just logged?

Edit:

More and more and more confused. I created the following perl script to test information about the events (i am a pel noob, so i might have a glaring error in there):


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

open (MYLOG,'>>/tmp/iwatevents.log');
print MYLOG "=====================================\n";
foreach $key (sort(keys %ENV)) {
    if ($key =~ /^IW\_/){
        print MYLOG $key, '=', $ENV{$key}, "\n";
    }
}
print MYLOG "=====================================\n";
close (MYLOG)

I hooked it up for all events with the trigger:


iwat ".+" "/opt/interwoven/iw-home/local/bin/iwattest.ipl"

it "works", in that the file /tmp/iwatevents.log gets created and lines get put in it, but it only contains a never-ending repetition of:


=====================================
IW_HOME=/opt/interwoven/iw-home
IW_MOUNT=/iwmnt
IW_MOUNT_PRIVATE=/.iwmnt
IW_RELBINDIR=/opt/interwoven/iw-home/bin
IW_STORE=/opt/interwoven/iw-store
=====================================

I was expecting to see things in there like "IW_EVENT", "IW_TIMESTAMP", etc. Looking at the sample command trigger scripts, I thought the trigger system would populate these environment variables before calling the script?

Regs,
/t

ISCBorisB

I was expecting to see things in there like "IW_EVENT", "IW_TIMESTAMP", etc. Looking at the sample command trigger scripts, I thought the trigger system would populate these environment variables before calling the script?

This ENV stuff is for the older event-related (iwatxxxx) triggers, they still exist and work.
Generic iwat Event handlers get Event information through arguments. Try something like this

#! Your Shebang
use strict;
use TeamSite::Config;

(my $iwhome = TeamSite::Config::iwgethome()) =~ tr|\\|/|;
if (open(MYLOG, ">>$iwhome/tmp/iwatevents.log")) {
   print MYLOG '='x70 . "\n";
   print MYLOG "ARG: $_\n" foreach(@ARGV);
   close(MYLOG);
}
else {
   die qq(Can't open "$iwhome/tmp/iwat.log" - $!);
}
exit 0;

Use iwat ".+" "myLogger" command to intercept all events and do not forget to remove it (iwlsat/iwrmat) when you do not need it any longer

tanguyr

Thanks, that's giving me some more meaningful information. I just swapped the perl code in and left the iwat trigger as it was:


root@bewcmd01 - /opt/interwoven/iw-home/tmp
# iwlsat
ID: 184915      ".+"    /opt/interwoven/iw-home/local/bin/iwattest.ipl

... and now i see information for the Thaw events fired off by iwfreeze -- :


root@bewcmd01 - /opt/interwoven/iw-home/tmp
# tail -f iwatevents.log
=============================================
ARG: [Tue Feb 10 19:18:13 2009]
ARG: root
ARG: master
ARG: Thaw
ARG: -
=============================================
ARG: [Tue Feb 10 19:19:40 2009]
ARG: root
ARG: master
ARG: Thaw
ARG: -

... but, sadly, nothing seems to be getting fired for WorkflowInactivate (it gets logged but not, seemingly, fired... wtf?) , so it looks like i'm s.o.l. as far as using a trigger to handle my problem.

In any case, thank you for illuminating me on the arguments vs. environment variables - much appreciated.

Regs,
/t

ISCBorisB

sadly, nothing seems to be getting fired for WorkflowInactivate (it gets logged but not, seemingly, fired... wtf?) , so it looks like i'm s.o.l. as far as using a trigger to handle my problem

If you try a regular flow without forced termination you will see that your logger catches all relevant Events
like WorkflowActivate, TaskGoActive, TaskInvokeExternal, TaskCalledBack and on and on, including WorkflowInactivate at the end.

Nothing seems to be fired though as a result of GUI Action-End Job

tanguyr

If you try a regular flow without forced termination you will see that your logger catches all relevant Events
like WorkflowActivate, TaskGoActive, TaskInvokeExternal, TaskCalledBack and on and on, including WorkflowInactivate at the end.

Nothing seems to be fired though as a result of GUI Action-End Job

ehhhhh... not so much. All i see in the $iwhome/tmp/iwatevents.log file is the aforementioned lines for Thaws, but here's the relevant lines from (cut -f 1-4) iwevents.log:


[Tue Feb 10 19:57:54 2009]      root    master  Thaw
[Tue Feb 10 19:59:38 2009]      trademak        master  Lock
[Tue Feb 10 20:00:17 2009]      trademak        master  TaskAddFile
[Tue Feb 10 20:00:17 2009]      trademak        master  WorkflowActivate
[Tue Feb 10 20:00:17 2009]      trademak        master  TaskActivate
[Tue Feb 10 20:00:17 2009]      trademak        master  TaskGoActive
[Tue Feb 10 20:00:30 2009]      iwui    master  Submit
[Tue Feb 10 20:00:37 2009]      trademak        master  TaskCalledBack
[Tue Feb 10 20:00:37 2009]      trademak        master  ChooseTransition
[Tue Feb 10 20:00:37 2009]      trademak        master  TaskActivate
[Tue Feb 10 20:00:37 2009]      trademak        master  TaskInactivate
[Tue Feb 10 20:00:37 2009]      trademak        master  TaskGoActive
[Tue Feb 10 20:00:38 2009]      trademak        master  TaskCalledBack
[Tue Feb 10 20:00:38 2009]      trademak        master  ChooseTransition
[Tue Feb 10 20:00:38 2009]      trademak        master  TaskActivate
[Tue Feb 10 20:00:38 2009]      trademak        master  TaskInactivate
[Tue Feb 10 20:00:38 2009]      trademak        master  TaskGoActive
[Tue Feb 10 20:00:42 2009]      trademak        master  TaskCalledBack
[Tue Feb 10 20:00:42 2009]      trademak        master  ChooseTransition
[Tue Feb 10 20:00:42 2009]      trademak        master  TaskActivate
[Tue Feb 10 20:00:42 2009]      trademak        master  TaskInactivate
[Tue Feb 10 20:00:42 2009]      trademak        master  TaskGoActive
[Tue Feb 10 20:00:43 2009]      trademak        master  TaskCalledBack
[Tue Feb 10 20:00:43 2009]      trademak        master  ChooseTransition
[Tue Feb 10 20:00:43 2009]      trademak        master  TaskActivate
[Tue Feb 10 20:00:43 2009]      trademak        master  TaskInactivate
[Tue Feb 10 20:00:43 2009]      trademak        master  TaskGoActive
[Tue Feb 10 20:00:51 2009]      trademak        master  TaskCalledBack
[Tue Feb 10 20:00:51 2009]      trademak        master  ChooseTransition
[Tue Feb 10 20:00:51 2009]      trademak        master  TaskActivate
[Tue Feb 10 20:00:51 2009]      trademak        master  TaskInactivate
[Tue Feb 10 20:00:51 2009]      trademak        master  TaskGoActive
[Tue Feb 10 20:00:53 2009]      trademak        master  TaskInvokeExternal
[Tue Feb 10 20:00:53 2009]      trademak        master  TaskCalledBack
[Tue Feb 10 20:00:53 2009]      trademak        master  ChooseTransition
[Tue Feb 10 20:00:53 2009]      trademak        master  TaskActivate
[Tue Feb 10 20:00:53 2009]      trademak        master  TaskInactivate
[Tue Feb 10 20:00:53 2009]      trademak        master  TaskGoActive
[Tue Feb 10 20:00:55 2009]      trademak        master  TaskInvokeExternal
[Tue Feb 10 20:00:57 2009]      trademak        master  TaskCalledBack
[Tue Feb 10 20:00:57 2009]      trademak        master  ChooseTransition
[Tue Feb 10 20:00:57 2009]      trademak        master  TaskActivate
[Tue Feb 10 20:00:57 2009]      trademak        master  TaskInactivate
[Tue Feb 10 20:00:57 2009]      trademak        master  TaskGoActive
[Tue Feb 10 20:02:25 2009]      wuserthr        Unknown TaskGroupTaken
[Tue Feb 10 20:09:02 2009]      wuserthr        reviewer        ChooseTransition
[Tue Feb 10 20:09:02 2009]      wuserthr        reviewer        TaskActivate
[Tue Feb 10 20:09:02 2009]      wuserthr        reviewer        TaskInactivate
[Tue Feb 10 20:09:02 2009]      wuserthr        reviewer        TaskGoActive
[Tue Feb 10 20:09:04 2009]      wuserthr        reviewer        TaskInvokeExternal
[Tue Feb 10 20:09:05 2009]      trademak        master  TaskCalledBack
[Tue Feb 10 20:09:05 2009]      trademak        master  ChooseTransition
[Tue Feb 10 20:09:05 2009]      trademak        master  TaskActivate
[Tue Feb 10 20:09:05 2009]      trademak        master  TaskInactivate
[Tue Feb 10 20:09:05 2009]      trademak        master  TaskGoActive
[Tue Feb 10 20:09:07 2009]      trademak        master  TaskInvokeExternal
[Tue Feb 10 20:09:07 2009]      trademak        master  TaskCalledBack
[Tue Feb 10 20:09:07 2009]      trademak        master  ChooseTransition
[Tue Feb 10 20:09:07 2009]      trademak        master  TaskActivate
[Tue Feb 10 20:09:07 2009]      trademak        master  TaskInactivate
[Tue Feb 10 20:09:07 2009]      trademak        master  TaskGoActive
[Tue Feb 10 20:09:07 2009]      trademak        master  UnLock
[Tue Feb 10 20:09:07 2009]      trademak        master  Submit
[Tue Feb 10 20:09:07 2009]      trademak        master  TaskActivate
[Tue Feb 10 20:09:07 2009]      trademak        master  TaskInactivate
[Tue Feb 10 20:09:07 2009]      trademak        master  TaskGoActive
[Tue Feb 10 20:09:09 2009]      trademak        master  TaskInvokeExternal
[Tue Feb 10 20:09:10 2009]      trademak        master  TaskCalledBack
[Tue Feb 10 20:09:10 2009]      trademak        master  ChooseTransition
[Tue Feb 10 20:09:10 2009]      trademak        master  TaskActivate
[Tue Feb 10 20:09:10 2009]      trademak        master  TaskInactivate
[Tue Feb 10 20:09:10 2009]      trademak        master  TaskGoActive
[Tue Feb 10 20:09:10 2009]      trademak        master  TaskInactivate
[Tue Feb 10 20:09:10 2009]      trademak        master  WorkflowInactivate

Basically i did the iwfreeze trick to have a placeholder in the $iwhome/tmp/iwatevents.log, then did a full walk through scenario: created a new form entry, and submitted it via a workflow, switching users to approve, etc etc. All i have in iwatevents.log is the single:


===============================
ARG: [Tue Feb 10 19:57:54 2009]
ARG: root
ARG: master
ARG: Thaw
ARG: -

and yet i should be catching everything:


# iwlsat
ID: 185101      ".+"    /opt/interwoven/iw-home/local/iwattest.ipl

(i moved the iwattest.ipl from local/bin up to local to try something with iwlocal.cfg, but that didn't work out either)

So, maybe it's a configuration issue on my end? Some setting to make the workflow subsystem fire events?

/t

ISCBorisB

Here is the tail of my WF-Events output

...
======================================================================
ARG: [Tue Feb 10 12:51:35 2009]
ARG: SYSTEM
ARG: master
ARG: TaskGoActive
ARG: Production Deployment Request
ARG: 0x6cc78
ARG: End
ARG: 0x6cc82
======================================================================
ARG: [Tue Feb 10 12:51:35 2009]
ARG: SYSTEM
ARG: master
ARG: TaskInactivate
ARG: Production Deployment Request
ARG: 0x6cc78
ARG: End
ARG: 0x6cc82
======================================================================
ARG: [Tue Feb 10 12:51:35 2009]
ARG: SYSTEM
ARG: master
ARG: WorkflowInactivate
ARG: workflow
ARG: Production Deployment Request
ARG: 0x6cc78

Are you sure you are looking at the right log? Hardcode it for now to remove any ambiguity

Also, I have only the following in iw.cfg, that's I beleive standard
[event_subsystem]
ew_enable=true

tanguyr

i'm positive i'm looking at the right log - the timestamp for the Thaw event in iwevents.log:


[Tue Feb 10 19:57:54 2009]      root    master  Thaw

matches what i see in the iwatevents.log:


ARG: [Tue Feb 10 19:57:54 2009]

and i have the same lines in my /etc/iw.cfg file

i'm running iwserver: 6.7.2 Build 69622 Interwoven 20080818 on Solaris 10 - SunOS bewcmd01 5.10 Generic_127111-09 sun4u sparc SUNW,Sun-Fire-V240 to be more precise. How about you?

Regs,
/t

ISCBorisB

I run 6.5.3 and 6.7.1, the test fragment I've included was from the Development 6.5 Environment. I do not have 6.7.2

Once again, I got that only on the normally terminated flow (transitioned to the end Task)
Absolutely nothing happens if I simply kill WF from GUI

ISCBorisB

Duplicate, removed

tanguyr

OK, i'll open a case with iwov support and post any news back to this thread. Thanks again for your help.

/t