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

Event Subsystem - Using Log Data

mstradling

I've just finnished setting up the event subsystem to log to Oracle and everything seems to be working so far as I can see.

What I can't see is how to make use of any of the data in the tables. I've tried a few trigger events (branch/workarea/edition creates, file submit) but the only table that seems to eb updating is MESSAGES and I'm not seeing anything especially useful in there.

Is there any way of making sense out of the logged data, or have I missed a concept somewhere along the line?

Find more posts tagged with

Comments

stefanmaier

Hi,
if you want to use triggers to synchronize the DCRs of a workarea with a table in your DB server,
have a look into od.602.ddadmin.pdf.
Steps in short:
- configure OD to use Database Auto-Synchronization (see pdf document)
- create dd.config-files e.g. for every DCT you want to sync with iwsyncdb -ddgen ...
- create db tables with iwsyncdb -initial ...

We use this mechanism to extract some data out of every submitted DCR into a database.
But this is only one possibility of using event triggers.

Stefan

Migrateduser

The event subsystem primarily exists to support indexing for search when a file changes, DAS, and the optional reporting system. If you want to tie into it to do any of your own event driven stuff, that's certainly possible - it's just an instance of OpenJMS, so you could register your own consumers.

I've seen differing opinions expressed within the forums by IWOV personnel about whether adding your own consumers is something they would consider supported or not.

mstradling

The intention was to use the Event Subsystem as the basis of a custom reporting application (IWov Reporting module isn't licenced and isn't an option).

chunk

Same here. We'd like to use the event data for live-workflow reporting. For some reason Management don't want to pay for a reporting package for our enterprise content management system even though we originally licensed that awesome Global Report Center from TS 4.5 & 5.

On a related note, is there any documentation on the event subsystem event data?

Migrateduser

I haven't seen any documentation surrounding the messages (or for that matter even the topics) for the eventsubsystem. My assumption had been that the messages would be serialized objects (ObjectMessage) - since the data in the db looks like a binary string to me, but one of my colleagues who has messed with it a bit more than I have says that it isn't and that it's trivial to build a browser to read the messages (a browser being a listener that doesn't consume messages). I have it as an item on my to do list to continue playing with that, but I have a lot of other stuff on my plate, so unless I end up with a client who has a need for me to figure it out, it will probably continue to be put on the back burner.

ryandev

You could try using JMS to subscribe to the event subsytem. It is all trial and error work as there is no documentation.

String topicName = "";
eventSS = "tcp://" + props.getProperty("event_subsystem_server") + ":" +
props.getProperty("event_subsystem_port");

Hashtable properties = new Hashtable();
properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.exolab.jms.jndi.mipc.IpcJndiInitialContextFactory");
properties.put(Context.PROVIDER_URL, eventSS);

Context context = new InitialContext(properties);

TopicConnectionFactory topicConnectionFactory = (TopicConnectionFactory)context.lookup("JmsTopicConnectionFactory");

Topic topic = (Topic)context.lookup(topicName);
TopicConnection topicConnection = topicConnectionFactory.createTopicConnection();

TopicSession topicSession = topicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);

topicConnection.start();
TopicSubscriber topicSubscriber = topicSession.createDurableSubscriber(topic, "SomeConsumerSubscriber");
topicSubscriber.setMessageListener(this);

Then you would have to set up onMessage() events to listen.. and react.

Interwoven, please document!!! ;D

and then there is iwat triggers...

mstradling

...and then there is iwat triggers...

I believe this cunning plan all came about because the client had previously tried implimenting a solution using itat triggers but ran in to issues - a task could transition from task A to task B, then transition to task C before the iwat trigger for the transition to task B was registered which meant trying to grab infor for task B failed as task B no longer existed.

Or some-such.

Thanks for the subscriber info - will look in to that.

On a related note, is there any documentation on the event subsystem event data?

Not that I've found - the best you get is the wonderfully evasive entries in the Admin guide, such as:

"TeamSite server events include (but are not limited to): CreateBranch, Submit, TaskActivate"

and no full list anywhere to be found.

dazzlad

Hi,

I am just wondering if anyone got a response as to whether or not subscribing to the topic was supported by Interwoven and also whether anyone has a working implementation.

We tried to implement a solution using AT triggers but the sheer number of them being fired slows the server, mainly because of the footprint of starting a new JVM from the command line for each event.

Thanks.
Darren