iwat trigger on windows

Hi,

I'm trying to run a script that spits out "Hello world" to a log file whenever a workflow starts up. I've done this before (years ago) on a Solaris box, and don't remember it being this hard to figure out...

I've got my perl script in $iwhome/local/bin/hello.ipl. When I run it from the command line, it writes "Hello world" to the log file, so I know that's working.

Then I ran

iwat WorkflowActivate "C:\Interwoven\....\hello.ipl"

Zilch. Nada. No peep in the log when I kick off a new workflow, even though I see the event being logged in the iwevents.log.

I read through the completely un-helpful KB #49977 and it's talking about some "iwlocal.cfg" file that I'm not familiar with. I also read some other KBs that tell you how to set up the iwat as a windows service (using the srvany.exe utility).

So, my first questions are:

1) How can you tell if your script is correctly "registered" with TeamSite as a subscriber to a given event (i.e. WorkflowActivate)

2) Is it required to run your iwat script as a service? (No, right?)

3) Does anyone know what the "iwlocal.cfg" file that the KB refers to is? I don't see any reference to it in the various docs, and I don't see a file by that name in my installation.

Thanks in advance!
Tom

Find more posts tagged with

Comments

nipper

I have used iwat a number of times. I can look and see what I needed to do to get them working. however one thing I can tell you is that you need to verify that what you are triggering off of (WorkflowActivate) is in the event log. If it is not there, then iwat will not trigger. It is a good idea to verify in the logs.

As to iw.local, that is a Unix only file. I am not even certain if that is even in use any more, but it is Unix only.

HTH

Andy

Tbag

Thanks for the info about the iwlocal.cfg . . . I knew it sounded familiar, but all the PDFs I have on my C:\ are windows-related, so it's no wonder I didn't find a hit.

In terms of the event log, I think it's doing "the right thing" :


$ tail -f iwevents.log
[Tue Sep 04 12:03:03 2007]      nyc1pmusa5\mainadmin    master  WorkflowActivate        workflow        Internet Workflow 0x8f2f
[Tue Sep 04 12:03:03 2007]      nyc1pmusa5\mainadmin    master  TaskGoActive Internet Workflow     0x8f2f  Start   0x8f31

I also double checked my spelling of the event name I pass to the iwat command, which lead me to the question about "how do you tell what events are already being subscribed to?" I can imagine registering multiple scripts to the same event over time and getting yourself in quite a mess. . .

nipper

how did you register the IPL ?

Are you able to run that alone (without iwperl) if you did not include iwperl

nipper

Also, TS has a Unix flavor, so the command you want is

iwlsat

$ iwlsat
ID: 54303 "TaskGroupTaken" C:/interwoven/iw-home/iw-perl/bin/iwperl
c:/interwoven/iw-home/custom/wft/bin/take_cgi.ipl

ISCBorisB

Hi,

I'm trying to run a script that spits out "Hello world" to a log file whenever a workflow starts up. I've done this before (years ago) on a Solaris box, and don't remember it being this hard to figure out...

I've got my perl script in $iwhome/local/bin/hello.ipl. When I run it from the command line, it writes "Hello world" to the log file, so I know that's working.

Then I ran
iwat WorkflowActivate "C:\Interwoven\....\hello.ipl"
Zilch. Nada. No peep in the log when I kick off a new workflow, even though I see the event being logged in the iwevents.log.

I read through the completely un-helpful KB #49977 and it's talking about some "iwlocal.cfg" file that I'm not familiar with. I also read some other KBs that tell you how to set up the iwat as a windows service (using the srvany.exe utility).

So, my first questions are:

1) How can you tell if your script is correctly "registered" with TeamSite as a subscriber to a given event (i.e. WorkflowActivate)

2) Is it required to run your iwat script as a service? (No, right?)

3) Does anyone know what the "iwlocal.cfg" file that the KB refers to is? I don't see any reference to it in the various docs, and I don't see a file by that name in my installation.

Thanks in advance!
Tom

1. Commands to use are:
iwat - To Register Event Handler
iwlsat - To List registered iwat programs
iwrmat - To Remove registered iwat programs

2. You should not set "iwat" as a service. It is registered in iwstore on your behalf and is persistent.
In Windows you should set iwatxxx(other than generic iwat) Triggers as Services, otherwise they will
disappear on reboot, iwserver restart, etc.

3. File iwlocal.cfg is Unix only configuration that is used to set persistent event triggers other than
generic iwat (same collection that should be set as Services in Windows)

See TeamSite® Command-Line Tools Manual for some details

Tbag

Ahhh....thanks a ton, nipper.

The resolution (in my case) was that I needed to include the iwperl bin path in the iwat command, even though I can just execute the perl script by itself on the command line. Weird.

So, for future reference, here's the full iwat command I used to get my trigger to work:


iwat WorkflowActivate "C:\Interwoven\TeamSite\iw-perl\bin\iwperl C:\Interwoven\TeamSite\bin\intracom
mon\Report\bin\hello_world.ipl"