Topic: What is the better way of processing MQ messages at webMethods - serial or concurrent ? where can we set this property at Adapter or notification or at listener level
What is the better way of processing MQ messages at webMethods - serial or concurrent ? where can we set this property at Adapter or notification or at listener level ??
We are running wM 8.0 sp2 with MQ Adapter 6.5 in a clustered environment where MQ messages will be picked by and published to JMS Broker queues.
No where you can set the property for processing at Adapter/Listener/Listener Notification. All the messages at MQ quues will be picked by wM MQ Adapter and then filtered by listeners in Concurrent mode. But depending on your requirements you can set this property Serial/Concurrent while creating a [b]Trigger[/b] for subscribing the messages from Broker/JMS queuues and processing at webMethods.
[b]Serial:[/b]
Where volume of messages received is slow you can go for Serial message processing at wM.
[b]Concurrent:[/b]
When you have huge volumes of messages then you can opt for concurrent processing while creating the triggers and optimize processing by creating no of threads based on your requirement.
Leave a Reply
Guest User
Not sure what solution is right for you?
Choose the right one for you.
Get the help of the experts and find a solution that best suits your needs.
Vikas
Hi,
What is the better way of processing MQ messages at webMethods - serial or concurrent ? where can we set this property at Adapter or notification or at listener level ??
We are running wM 8.0 sp2 with MQ Adapter 6.5 in a clustered environment where MQ messages will be picked by and published to JMS Broker queues.
Thanks.
Pradip
No where you can set the property for processing at Adapter/Listener/Listener Notification. All the messages at MQ quues will be picked by wM MQ Adapter and then filtered by listeners in Concurrent mode. But depending on your requirements you can set this property Serial/Concurrent while creating a [b]Trigger[/b] for subscribing the messages from Broker/JMS queuues and processing at webMethods.
[b]Serial:[/b]
Where volume of messages received is slow you can go for Serial message processing at wM.
[b]Concurrent:[/b]
When you have huge volumes of messages then you can opt for concurrent processing while creating the triggers and optimize processing by creating no of threads based on your requirement.