| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Options for .NET |
« View previous topic :: View next topic » |
| Author |
Message
|
| stubie |
 Posted: Wed Jun 11, 2003 5:25 pm Post subject: Options for .NET |
 |
|
Novice
Joined: 05 Nov 2001
Posts: 14
Location: Charlotte, NC
|
I have the need, possibly, to interface with MQWF via clients developed using .NET technology. We will likely have an ASP.NET thin client for casual and extranet participants, and a VB.NET or C# rich client for back office users.
The question is how to interact. For process instantiation, I can use the XML interface and I am language/platform/environment independent. Same for UPES. But then there is the session-based stuff -- worklists, workitem actions, etc.
I see two options. One is to wrap the COM API that is available for purchase from IBM. I have concern about scalability, since COM can be problematic there. The other option is to create webservice(s) to front end these functions, but I am then concerned about session management and performance.
Any thoughts or experience? |
|
| Back to top |
|
 |
| Bobbo |
| Posted: Fri Jun 13, 2003 10:53 am Post subject: |
|
|
Acolyte
Joined: 17 Jun 2002
Posts: 50
Location: Buffalo, New York
|
| My company is also embarking on using ASP.NET against the COM API. I would be interested in your experience with this. Also, do you have any metrics associated with your concern for the scaleability relative to wrapping the COM API via .NET? Have you used the COM API? |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
