Author |
Message
|
kash3338 |
Posted: Tue Jun 30, 2009 4:26 am Post subject: Invoke C or C++ application from Message Flow |
|
|
Shaman
Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India
|
Hi,
How do i invoke a legacy C or C++ application from my ESQL??? Can any one guide me on this??? |
|
Back to top |
|
 |
harish_td |
Posted: Tue Jun 30, 2009 4:52 am Post subject: |
|
|
Master
Joined: 13 Feb 2006 Posts: 236
|
|
Back to top |
|
 |
zpat |
Posted: Tue Jun 30, 2009 5:07 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
You should not use WMB as an application hosting platform. You should host the application somewhere else and invoke it by sending it a MQ message to which it responds with another MQ message.
If the application is not MQ enabled then code a wrapper for it so that it is (IBM provide a ready made .NET trigger monitor and other such).
WMB flows should be stateless (or near stateless). |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jun 30, 2009 6:13 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
zpat wrote: |
You should not use WMB as an application hosting platform. You should host the application somewhere else and invoke it by sending it a MQ message to which it responds with another MQ message.
If the application is not MQ enabled then code a wrapper for it so that it is (IBM provide a ready made .NET trigger monitor and other such).
WMB flows should be stateless (or near stateless). |
 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
kash3338 |
Posted: Tue Jun 30, 2009 9:28 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India
|
zpat wrote: |
WMB flows should be stateless (or near stateless). |
Can you please elaborate on this??? |
|
Back to top |
|
 |
zpat |
Posted: Tue Jun 30, 2009 10:34 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
This means that they should not wait for other applications to do things during the flow.
E.g. a message flow that wanted to invoke another application would generate an output message to it and terminate the flow.
The response message would be processed in another message flow entirely, any state data would be carried in the message (or perhaps retrieved from a database).
This sort of approach makes the broker highly scaleable with high throughput. It also makes it decoupled and not dependent on the other application responding in a timely fashion. |
|
Back to top |
|
 |
kash3338 |
Posted: Tue Jun 30, 2009 10:49 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India
|
zpat wrote: |
This means that they should not wait for other applications to do things during the flow.
E.g. a message flow that wanted to invoke another application would generate an output message to it and terminate the flow.
The response message would be processed in another message flow entirely, any state data would be carried in the message (or perhaps retrieved from a database).
This sort of approach makes the broker highly scaleable with high throughput. It also makes it decoupled and not dependent on the other application responding in a timely fashion. |
Thanks for the elaborate explanation. So do yu mean to say the only way to do this is through MQ or a Wrapper???? |
|
Back to top |
|
 |
zpat |
Posted: Tue Jun 30, 2009 11:03 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
The best way, not the only way.
You can drive a racing car over rocks but I wouldn't recommend it. |
|
Back to top |
|
 |
kash3338 |
Posted: Tue Jun 30, 2009 6:58 pm Post subject: |
|
|
Shaman
Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India
|
zpat wrote: |
The best way, not the only way.
You can drive a racing car over rocks but I wouldn't recommend it. |
Thanks a lot. I agree that this is the best approch, but i just want to know the others ways of acheiving this. Just to know how it can be done. |
|
Back to top |
|
 |
|