| Author |
Message
|
| jefflowrey |
 Posted: Mon Jan 15, 2007 6:26 am Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You need to be careful with .NET about the exits.
Some of them are only for managed code, and those are not compatible with other exits.
There's some specific information I remember seeing about this in the Info Center.
What was the requirement for implementing in .NET/XMS, anyway, when there are plenty of successful implementations in Java?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| SilentWind |
| Posted: Tue Jan 16, 2007 5:59 pm Post subject: |
|
|
Acolyte
Joined: 11 Jan 2006
Posts: 58
|
| jefflowrey wrote: |
You need to be careful with .NET about the exits.
Some of them are only for managed code, and those are not compatible with other exits.
There's some specific information I remember seeing about this in the Info Center.
What was the requirement for implementing in .NET/XMS, anyway, when there are plenty of successful implementations in Java? |
Well, I require my apps to pub-sub in a .NET environment. Previously I tried using WMQ classes to do a pub-sub, but that didn't work. Hence I reverted to XMS. I would like to ask if WMQ classes can support pub-sub, if so, I may divert resources in that area instead of focusing on XMS which is not supported at this point in time. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jan 16, 2007 6:29 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can manually build an MQRFH header for use with an MQ pub/sub broker, or you can manually build an MQRFH2 header for use with a WMB pub/sub broker...
The heart of my question was why .NET, and not why XMS.
For Pub/Sub, XMS makes sense.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| SilentWind |
| Posted: Tue Jan 16, 2007 9:15 pm Post subject: |
|
|
Acolyte
Joined: 11 Jan 2006
Posts: 58
|
| jefflowrey wrote: |
You can manually build an MQRFH header for use with an MQ pub/sub broker, or you can manually build an MQRFH2 header for use with a WMB pub/sub broker...
The heart of my question was why .NET, and not why XMS.
For Pub/Sub, XMS makes sense. |
Because I require security exits, and XMS cannot support security exits at the moment. This input is from the readme.txt when the XMS is installed and also from the IBM forums. Unless someone here has a good idea of using security exits in XMS now.... (which I hoped  ) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 17, 2007 2:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
One more time.
You have many working Java apps in your shop.
Why are you using .NET instead of Java?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| SilentWind |
| Posted: Wed Jan 17, 2007 6:04 pm Post subject: |
|
|
Acolyte
Joined: 11 Jan 2006
Posts: 58
|
| jefflowrey wrote: |
One more time.
You have many working Java apps in your shop.
Why are you using .NET instead of Java? |
Yes, I have many Java apps. Also, I have .NET apps running. In fact they are communicating with each other. I would think this is a feature of MQ to allow for interoperability.
And yes, I have a very complicated shop.  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jan 18, 2007 4:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
As the Devil's advocate you could try encapsulate the java classes with J# and call those from the .NET side.... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| SilentWind |
| Posted: Thu Jan 18, 2007 10:01 pm Post subject: |
|
|
Acolyte
Joined: 11 Jan 2006
Posts: 58
|
| fjb_saper wrote: |
| As the Devil's advocate you could try encapsulate the java classes with J# and call those from the .NET side.... |
 That would be a last resort for me.
To summarize this topic, I would like to configure XMS to have security exits installed so that it can authenticate with the server security exit on Websphere MQ 6.0.2.
- I cannot use WMQ classes because there is no default-pub-sub implementation, and if I do, I require to construct the headers myself which I may run into other problems.
- I cannot use WMQ exit in a XMS factory because simply it does not make sense and the 2 packages are different.
- I use XMS because I have .NET apps which communicate with other apps like Java through the MQ server.
So once again, I would like to ask if XMS have any supported security exits or there is another workaround for this.
Thank you all for your valuable advice and assistance!  |
|
| Back to top |
|
|
| Tibor |
| Posted: Fri Jan 19, 2007 12:33 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| SilentWind wrote: |
| I cannot use WMQ classes because there is no default-pub-sub implementation, and if I do, I require to construct the headers myself which I may run into other problems. |
I think you can. I wrote an RFH2 header handling in C (ANSI C!) and it works since years. Moreover, C# is more flexible, that's why I think it wuold be a relatively simple task for you.
Tibor |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 19, 2007 12:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| SilentWind wrote: |
| I require to construct the headers myself which I may run into other problems. |
It's not that tricky, and may prove to be easier than the workaround....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Sun Jan 21, 2007 10:12 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
| fjb_saper wrote: |
| As the Devil's advocate you could try encapsulate the java classes with J# and call those from the .NET side.... |
Or you could write a standard Windows C program and compile and link it as a WMQ Security Exit DLL.
From C#, you have 2 ways to use it:
(1) In your C# code, do some thing like:
| Code: |
| factory.SetStringProperty(XMSC.WMQ_SECURITY_EXIT, "MySecurityExit.dll"); |
(2) Use a Client Channel Table with your C# code. Create a CLNTCONN channel and put your exit DLL info in the SCYEXIT field.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| saketr |
| Posted: Sat Feb 24, 2007 10:02 am Post subject: |
|
|
Apprentice
Joined: 08 Feb 2006
Posts: 41
|
|
| Back to top |
|
|
|
|
