ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [Solved]Audit messages in a clustered WF setup.

Post new topic  Reply to topic
 [Solved]Audit messages in a clustered WF setup. « View previous topic :: View next topic » 
Author Message
chintu
PostPosted: Mon Mar 03, 2008 9:24 am    Post subject: [Solved]Audit messages in a clustered WF setup. Reply with quote

Acolyte

Joined: 27 Dec 2004
Posts: 64

Hello all,

We are migrating our WF system from a 1-tier setup to a 2 tier setup with multiple systems( same group).

Current setup
Box A has WF runtime(FMC,FMCGRP,FMCSYS,FMCWFQM), a java custom client using 3.6 jars running on websphere app server,Runtime DB

Our application is driven primarily by the MQ audit messages( Audit_to_MQ local queue on FMCWFQM). A.NET application (mq client libraries) picks up these audit messages. The order of these messages needs to be maintained. For a given process instance, the"workItem created" message should not be processed before "process instance created" message. Currently this works fine since the .NET client gets these messages FIFO.


Future setup
Box A will have the same WF runtime(FMC,FMCGRP,FMCSYS,FMCWFQM), a java custom client using 3.6 jars running on websphere app server.
Box B will have 2d WF runtime(FMC,FMCGRP,FMCSYS1,FMCWFQM1), a java custom client using 3.6 jars running on websphere app server.
Box C will have the runtime DB.


With this setup there will be 2 audit queues...Audit@FMCWFQM(Box A) and Audit@FMCWFQM1(Box B).


Question:
For a particular process instance..If PICreated audit message goes to BoxA and WI created audit message goes to BoxB...and if for some reason there is a queue backup on BoxA( .NEt client is down and did not GET the PICreated message on Audit@FMCWFQM) then the WI created message on Audit@FMCWFQM1 (upon processing)will throw an application error since the PICreated message needs to be processed prior to WI creation.

If FMCSYS(box a) gets a createProcessInstance request..will all the processing of this process instance be done on box A?(will all audit messages for this instance always got to Audit@FMCWFQM). If not..is there a way to achieve this? This would solve our problem since this way PICreated will always be picked up before WI created message.


Last edited by chintu on Mon Mar 17, 2008 8:05 am; edited 1 time in total
Back to top
View user's profile Send private message
hos
PostPosted: Tue Mar 04, 2008 1:54 am    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470

You cannot define multiple audit queues in a system group. An audit queue is defined by the qmgr name and the queue name in a system group.

Therefore it is not important whether all requests are processed on the same system. Your .Net application needs to be able to filter out any other events on the queue that are not related to the particular PI you are interested in. But this needed to be the case in a single system environment as well.

You cannot get any WI events for a specific PI before this PI has been created i.e. before the PICreated event has been put to the audit queue.
Back to top
View user's profile Send private message
chintu
PostPosted: Tue Mar 04, 2008 8:40 pm    Post subject: Reply with quote

Acolyte

Joined: 27 Dec 2004
Posts: 64

Thanks for your reply hos.

Quote:

You cannot define multiple audit queues in a system group.


We are able to send audit messages to 2 queues...audit@QM1 and audit@qm2 by not specifying the qmgr name in the group fdl.

-------
GROUP 'SV1GRP'
DESCRIPTION '20040113 1200 : Default system group'
RELATED_DOMAIN 'DOMAIN'
AUDIT_QUEUE_NAME '1BR1.AUDITTRAIL.DATAGRAM'

// ---------------------------------------------------------------------------
// System
// ---------------------------------------------------------------------------
SYSTEM 'SV1SYS'
DESCRIPTION '20040113 1200 : Default system'
RELATED_GROUP 'SV1GRP'
PRIMARY_SYSTEM
SYSTEM_IDENTIFIER 1
VERSION 3
RELEASE 6
LEVEL 0
END 'SV1SYS'

SYSTEM 'SV1SYS1'
DESCRIPTION ''
RELATED_GROUP 'SV1GRP'
NO PRIMARY_SYSTEM
SYSTEM_IDENTIFIER 2
VERSION 3
RELEASE 6
LEVEL 0
END 'SV1SYS1'

// ---------------------------------------------------------------------------
// QueueManager
// ---------------------------------------------------------------------------
QUEUE_MANAGER 'SV1QM'
DESCRIPTION 'Default queue manager'
QUEUE_MANAGER_NAME 'SV1QM'
RELATED_SYSTEM 'SV1SYS'
SYSTEM MQSERIES
END 'SV1QM'

QUEUE_MANAGER 'SV1QM2'
DESCRIPTION ''
QUEUE_MANAGER_NAME 'SV1QM2'
RELATED_SYSTEM 'SV1SYS1'
SYSTEM MQSERIES
END 'SV1QM2'

---------

We did some testing today on our pilot setup and found that the sequencing of audit messages is maintained within a system. If a PI is created via systemA then both its PI created,WI created audit messages always seem to go to Qmgr@sysA...and like wise for a PI created in systemB... its PI,WI created audit messages always seem to go to Qmgr@sysB. This is our desired behaviour. We did not want PI created to go to Qmgr@sysA andWI created message to go to Qmgr@sysB.

I hope this is not just plain luck.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [Solved]Audit messages in a clustered WF setup.
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.