Originally posted by: SystemAdmin

Hi,
Just for my understanding - want to know how the event based triggering happens in the launcher
Say for instance we want to trigger the launcher whenever there is a message on the queue, we define the queue in map and set the trigger to be event based.
Now my question is how this triggering happening ?
Is the launcher continuously watching the queue , if so where do we define the parameter that launcher should watch every 1 minute.
If the above holds true then whats the difference between event based and time based triggering.

Cheers
Sid
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: phil2030

I would hope the launcher is registering a listener for a specific event (a message arriving on a queue) with the queue manager and then going to sleep until woken up be the queue manager notifying the launcher that such an event has occured (a message has arrived).
There is nothing to stop you polling a queue based on time, but obviously you have to handle messages not being there when you poll and potentially messages arriving on the queue quicker than you handling and removing them. (You still have the potential issue of a backlog when registering a listener dependent on handling/processing times.)
Polling will (probably) use more system resources and there is likely to be more latency.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: repanzer

The dtx.ini file contains most settings like you mentioned. There is one specifically for files and how many milliseconds between checking the directory. Not sure if there's one for MQ.

; time in milliseconds between directory processing - 50 is the default
; increase this value if the CPU level is high when Launcher is idle
;ListenSleepTime=50
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

for MQ , we have -REFRESH option to refresh the queue after specific time interval
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: phil2030

If memory serves, I think the refresh puts the cursor at the head of the queue every 'n' seconds. Primarily used when you use priority based messaging.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Hi, every body
thanks for your replies, but i haven't received the answer i am looking for -
basically just want to know in the event based triggering does the launcher monitor queue or not. if yes, what parameter we set for to watch it. If not, how the event is triggered and launcher comes to know.

Appreciate your time and help here.
cheers
Sid
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: phil2030

You asked how it works... that's the answer you got. What event based triggering are you talking about? Time? Message Arrival? I am pretty sure the documentation will tell you how to set these up in the IFD.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: repanzer

All I know is; as soon as a message hits our queues, the maps kick off, and we have not set any parameters. I'm not that familiar with MQ pasted utilizing them, but from what I gather, the technology is pretty smart. It may be something other then the map checking the queue for messages, and may be something from the queue triggering the map. (if you know what I mean), but I'm not sure of what is exactly taking place.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: graham.saltern

Repanzer,
If by message queues you mean IBM Websphere MQ message queues then from the information center documentation it seems that the MQ Adapter has implemented the standard MQ API. There are a variety of settings that are covered in this section, and some familiarity with MQ helps, but hopefully it is reasonably clear. There is also a particularly important section that outlines potential performance issues associated in integrating WTX & MQ that is worth reading.

The link below take should take you to the relevant pages.

http://publib.boulder.ibm.com/infocenter/wtxdoc/v8r2m0/index.jsp

Look under the following headings
1. Resource Adapters->IBM WebSphere MQ Adapter overview
2. IBM WebSphere MQ Adapter overview->Using the messaging adapter->Threading for IBM WebSphere MQ

Typically, when an application requests messages from an MQ Queue it performs a get against a queue on a queue manager. This can optionally be specified with a wait period in which case MQ pause for the specified period or until a message appears on the queue. From your description of the behaviour happening it sounds like the adapter has been configured to run as a timed event where it polls the mq queues periodically, assuming you have the default settings for the system and just the basic information for the MQ this will result in the launcher firing an event every few seconds which in turn results in 20 instances of the map being initiated with the same number of gets being performed on the target queue.

This may give the appearance of files disappearing from the queues as soon as they get there, but in reality it is simply due to a reasonably high number of gets being performed against a single queue in short succession.

Hope this helps explain what may be happening...

Regards,
Graham Saltern
mob 00 44 7875 809502

erebor limited
Premier Systems Integration Consultancy
IBM Premier Business Partner
Cisco Systems Partner - Premier Certified
Tel: +44 (0) 845 241 1536
Fax: +44 (0) 845 241 1537
Office: Trinity House, Bryer Ash Business Park, Trowbridge,
Wiltshire BA14 8HE
www.erebor.co.uk
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: graham.saltern

Err did I say Repanzer sorry that should have been Sid.

Cheers
Graham
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender