Re: Problem connecting to weblogic JMS with dotnet

> Hi
> 
> I have a similar requirement in which I need a .net
> application which has to monitor a weblogic JMS queue
> and recieve messages. I tried by adding reference to
> TIBCO.EMS.dll. I think this one is meant to use with
> TIBCO JMS queue. Could you please let me know how you
> achieved this in .net. 
> 
> Thank You
> Rahul

You have multiple options.    

The easiest of which would likely be to use the WebLogic JMS .NET client, which
will be available for the upcoming version 10.3 and is out in beta (see beta
docs for more info).   The 10.3 WLS server can in turn redirect the .NET JMS
client requests to older WLS versions as far back as 8.1.   Note that what's
publicly available is an early version of the code - it might be possible to get
a newer version via your sales rep.

Here's a cut-and-paste of some relatively old, but still useful notes I have on
some other alternatives:

Non-Java Integration Options
----------------------------

- WL JMS has a JNI based C client which is available for Windows and some UNIX
platforms.  This C client supports 7.0 and up, and is officially packaged with
WLS in 9.0 (virtually unchanged).  The C API is currently only supported through
the jms newsgroup.  See "JMS C API", here:
http://dev2dev.bea.com/technologies/jms/index.jsp

- WL supports direct Windows COM access through its "JCOM" feature.
This doesn't include the JMS API, but one can invoke EJBs which in turn invoke
JMS.  See
http://e-docs.bea.com/wls/docs61/jcom.html
http://e-docs.bea.com/wls/docs70/jcom/
http://e-docs.bea.com/wls/docs81/jcom/

- Similar to JCOM, but more advanced and supported on more platforms, WL
supports access via the standard IIOP protocol.   You can use the BEA Tuxedo C
client for this purpose (no license fee).  This doesn't include the JMS API, but
one can invoke EJBs which in turn invoke JMS.  See
http://e-docs.bea.com/wls/docs81/rmi_iiop/
http://e-docs.bea.com/wls/docs70/rmi_iiop/
http://e-docs.bea.com/wls/docs61/rmi_iiop/
Unlike most other approaches, the IIOP client approach also allows the client to
begin and commit user (JTA) transactions (not configured).

- If you already have a BEA Tuxedo license, one option is communicate through
BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server
to respond to these requests via the WTC bridge.   Search for "WTC" in
the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows
the client to begin and commit user (JTA) transactions.

- Another approach is to interop via web-service standards. Or even to simply to
invoke a servlet on the WL server using a basic HTTP call from the client. 
These operation in turn can invoke the JMS API.   There is a white-paper on
"Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1
Web Services", that demonstrates web-services here:
http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf

- Yet another approach is to use a third party product that is designed to wrap
any JMS vendor.   There are even open source versions.  In no particular order,
here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft

- Finally, there are .NET/C/C++ integration libraries that are not necessarily
specific to JMS, some examples are JNBridge, Jace, and CodeMesh.