How WebLogic7.0 & 8.1 JMS connect to MSMQ?

          Hi Sir,
          Is it possible that i use WebLogic JMS connect to MSMQ(Microsoft)?
          If it possible, how can i configure/implement ? Do I have to create adapter class
          for MSMQ?
          Thanks
          Yos

You may be able to find a JMS wrapper for MSMQ (search
          google), in which case you can integrate using the same
          methods as for any other JMS vendor.
          Another option is to use the the WL JMS C client
          within a MS program, or even to use "ActiveJMS"
          .net wrapper from sourceforge to wrap WL JMS
          within a MS program.
          Another option is to call into MS (or vice-versa)
          using WL's JCOM feature.
          Another option is to integrate using web services -
          which is the method often pushed by MS.
          "weblogic.developer.interest.webservices"
          Another option is to consult the WLI newsgroup,
          "weblogic.integration.developer" to see if WLI
          has pre-built MSMQ adapters.
          Tom
          Yos wrote:
          > Hi Sir,
          > Is it possible that i use WebLogic JMS connect to MSMQ(Microsoft)?
          > If it possible, how can i configure/implement ? Do I have to create adapter class
          > for MSMQ?
          > Thanks
          > Yos

Similar Messages

HOw to test the jms connection?

HI all,
how to test the jms connection in xi?
regards
kish

HI,
We can see the JMS sender or reciver side .. in RWB .. see communicaiton channel mononitoring,., also..
We can access it through browser.. it depends upon the proocol type .. like sonic or webspeare MQ..or ...
see below links
http://help.sap.com/saphelp_nw04/helpdata/en/cf/886a3c3a860657e10000000a114084/frameset.htm
/people/alessandro.guarneri/blog/2006/01/04/jms-sender-adapter-handling-too-short-lines
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
content conversion https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/97171dd3-0401-0010-5195-b43f556e6ce9
Chilla

How to use remote JMS in websphere5?

I want to use JMS in another server to send message so that I config required jndi in server. When I lookup local JMS jndi(connection factory, queue) it works correctly. But when I lookup remote connectionfactory, it throws 'javax.naming.CommunicationException'. BTW, local configuration is same as JMS server. And I use WSAD 5.1.1 to develop it.
The first question is if I need use JMS server on another server, I should lookup remote queue and JMS connection factory on that server, right?
The second question : If yes, how to obtain remote JMS connection factory? I use WSAD 5.1.1 trail, I don't know is it possible to obtain remote jndi.
The third question : do I need change any configuration for supporting remote JMS client instead of local(same compute, different jvm) environment?
The following is my client code to obtain remote queue:
public class Test {
     public static void main(String[] args) {
          Properties env = new Properties();
          env.put(Context.INITIAL_CONTEXT_FACTORY,
                "com.ibm.websphere.naming.WsnInitialContextFactory");
          env.put(Context.PROVIDER_URL, "corbaloc:iiop:10.240.4.203:2809");
          try {
               Context initialContext = new InitialContext(env);
               Object obj = initialContext.lookup("jms/IPharmQueue1");
          } catch (NamingException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
}It works ok when ip is localhost. But it can obtain remote queue or connectionfactory. I tried to lookup other EJB, it also failed.

Actually, I have application in one server and four same server as cluster. But only one server provides JMS service. So my application need to use remote JMS server instead of local server. But in my development environment I can not simulate cluster environment as customer environment. So I try to let my application access remote JMS server in different computer. When two server start up I found my application will get local JMS connection factory and queue instead of remote factory. Even I put IP of another computer in PROVIDER_URL.
I did a application client to test it. The code is above. But it can not lookup remote jndi.
I use WAS5 as server and WSAD 5.1.1 as development IDE.
Is any idea about it?

How to reconnect in case of a JMS connection lost

If JMS connection is lost during the exceution of the program, how to reconnect to the destination.
please help me.
thanks in advance.

BTW, SJS MQ (The MQ with the J2EE Reference Implementation) also supports that.
If you are using a queue, you should not loose messages. This is what the JMS spec is all about. If you are using a topic (message broadcast) then you would need to set the client as a durable subscriber, this way, if the client is not connected, the messages are kept for him to come back.
Another point, if the connection is lost because the message broker went down, then all messages that were not consumed on that destination are lost, if they were not persisted.
If the messages are persisted then you should have all the messages still available when you restart the broker and reconnect to it. Now since brokers try to be smart about persisting and minimise the disk I/O, you need to learn how the persistence of your broker works, and make sure you configure it to the performance/reliability balance you require for your application.
TE

How can a remote jms receiver detect loss of connection to Messaging server

Plan:
Messaging server (like JbossMQ /SonicMQ) is hosted on one machine.
A JMS receiver (MDB/core java program) on another machine receives messages from the messaging server.
Secnario:
The JMS receiver is now continuously listening or occasionally reading messages from a certain queue of the server using a JMS connection.
Now the messaging server has this receiver in its list of receivers for that particular queue.
For some reason the messaging server is down and then restarted.
The JMS connection of the receiver is now invalid.
When the messaging servers comes up again its list of receivers is empty.
Required Solution:
Can you please help me on how the JMS receiver can detect the above scenario and re-establish the connetion to the messaging server, the next time the server is up.
Observations:
When I create a message consumer or queue receiver in a j2se program, and take messages from JbossMQ I have some additional threads running on my JVM. These threads are not directly created by the program and servers only for receiving messages. One of these threads is catching an exception and printing a stack trace when it detects that the connection is lost. This will also result in the closing of JMS connection. The problem is that the exception is not thrown for the programmer to catch and handle it at some level. I also tried ExceptionListener and waited for ping interval. Is there a concept of receiver listening to the periodic heart beat of the server. Please give me guidance, solutions or corrections.
For comments on this, Thanks in advance

Hi Leendert,
do you want to use the JMS API directly? In this case you have to create the connection factory on system X. From system Y, you access the JNDI on system X and look up the connection factory. Since you are accessing the JNDI on system X from outside, you need to set some properties to create the InitialContext:
    Properties env = new Properties();
    env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sap.engine.services.jndi.InitialContextFactoryImpl");
    env.put(Context.PROVIDER_URL, <system X>:<p4 port>); // replace with your settings
    env.put(Context.SECURITY_PRINCIPAL, <user name>); // replace with your settings
    env.put(Context.SECURITY_CREDENTIALS, <password>); // replace with your settings
    naming = new InitialContext(env);
Hope that helps.
Regards,
Sabine

How to find out status of JMS Connection ( connected or closed )

Is there a way to find out the status ( connected or closed ) of JMS Connection at any point of time . JMS Connection interface doesn't seem to have any isAlive( ) sort of method ?
I'm using a shared instance JMS Connection and if someone calls connection.close() on this instance the code starts flunking.

Crap isn't it! Would also be useful for creating a JMS connection pool, or for testing connections that stay open for time time and may be closed by network problems etc.
I can think of a couple of options (haven't tested them so may be flawed)
1. Extend your vendors QueueConnectionFactory object to return a decorated Connection, which adds an isAlive() method and records internally whether someone has called .close(); This could be tricky if you use JNDI to retrieve the QCF - you'll have to bind your custom QCF and remove the old one. Much easier if you use a bean factory like Spring.
2. You may be able to do this with the underlying vendor's API. If you choose this option put all the vendor specific code in a separate class and abstract it behind an interface. In future if you change to a JMS provider that does not support this feature, you can always change your isAlive() method return true no matter what;
3. Wrap the JMS sender / receiver in an Adapter class. The adapter delegates send / receive methods to the wrapped class, but if it receives a JMS exception will reconnect and try again. A second JMS Exceptions should be thrown back to the client. All your client code sees is a single send / receive method as if it was using a normal JMS sender / receiver.

How Long Can I cache JMS Connection ?

Hi
My servlets need to send messages to queues. For speed, I am creating and caching JMS connection and queue session in the servlet's init() method. The questions are
1) Will the queue session or connection time out after a couple of days , assumimg the servlet never gets unloaded/reloaded in that period?
2)Is there a way to figure out a connection /session status before trying to create a sender and catching exceptions ?
Regards
-m

Hi,
The connections do expire after few days hence the easiest way would be to have a double check ....ie.. as you are caching the connection and when ure trying to create a session from the connection keep a try-catch to determine if the connection has expired and if yes then you can create a new connection and cache it again. Now you can use this cached connection to create the sessions .
Hope this helps
neo

How to find if I have lost my jms connection?

Is there a way to find if my client has lost its connection to the JMS service?

believe only approach is optimistic: expect success,
react on fail
try/catch for JMSException: send() producer-side,
receive() consumer-side
on exception: retry by close() Connection/Session,
recreate Connection/Session, and reattempt actionYes. Plus: set an ExceptionListener at the JMS connection and act properly when onException is called. The ExceptionListener is the hook where JMS providers usually report a connection lost.
-- Andreas

Problem with transacted JMS connection factory and transaction timeouts

          We encountered an interesting problem using transacted JMS connection factories.
          An EJB starts a container managed transaction and tries to validate a credit card
          before creating some information to a database for the user, in case of success
          an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          duration is about the same as the transactions timeout (in this case the default
          30 seconds) sometimes the database inserts is committed but the JMS insert is
          rollbacked. How can this be?
          If the authorization duration is much longer than 30 seconds everything works
          fine (both database and JMS inserts rollbacked), the same is true if a rollback
          is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          if the duration is approximately the same as the transaction timeout, it appears
          that the database insert is not timeouted but the JMS insert is. How can this
          be if they are both participating in the same transaction.
          The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          configure our own factory with user transactions enabled.
          Any help appreciated!


Tomas Granö wrote:
          > We encountered an interesting problem using transacted JMS connection factories.
          > An EJB starts a container managed transaction and tries to validate a credit card
          > before creating some information to a database for the user, in case of success
          > an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          > duration is about the same as the transactions timeout (in this case the default
          > 30 seconds) sometimes the database inserts is committed but the JMS insert is
          > rollbacked. How can this be?
          It should not be.
          >
          > If the authorization duration is much longer than 30 seconds everything works
          > fine (both database and JMS inserts rollbacked), the same is true if a rollback
          > is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          > if the duration is approximately the same as the transaction timeout, it appears
          > that the database insert is not timeouted but the JMS insert is. How can this
          > be if they are both participating in the same transaction.
          >
          > The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          > is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          > configure our own factory with user transactions enabled.
          >
          > Any help appreciated!
          Make sure that your session is not "transacted". In other words,
          the first parameter to createSession() must be false. There is an
          unfortunate name re-use here. If a session is "transacted", it
          maintains an independent "inner transaction" independent of the
          outer transaction. From the above description, it seems unlikely
          that your application has this wrong, as you say that
          "setRollbackOnly" works - but please check anyway.
          Make sure that you are using a true XA capable driver and database
          (XA "emulation" may not suffice)
          Beyond the above, I do not see what can be going wrong. You
          may want to try posting to the transactions and jdbc newsgroups. Note
          that JMS is appears to be exhibiting the correct behavior, but the
          JDBC operation is not. The JDBC operation appears to have
          its timeout independent of the transaction monitor's timeout.
          Tom

How to send a JMS message to a remote Queue?

Hi,
I know how to create a JMS message and send it to an MDB that listens to a topic in the same container in which the JMS is created.
In other words, if I have the following MDB:
@MessageDriven(mappedName = "jms/MyQueue", ...)
public class MyMDB implements MessageListener {
Elsewhere in my JEE app I can create a Queue like this:
@Resource(mappedName = "jms/MyQueue")
Queue queue;
and use it to send a message to the MDB.
But How can I send a message to an MDB that's deployed in another app server on another machine in the network? Both of the app servers are Glassfish.
Thanks in advance.
Edited by: EJP on 9/08/2011 21:49: fixed your meaningless title

Hi,
The first thing I would like to suggest is, we never/can't send message directly to MDB. We always send/receive message(s) to/from the destination. In case of MDB, the application server register the MDB as message listener against particular destination, and invoked the onMessage() method when message arrives on particular destination.
If I am not wrong, what you want to achieve is asynchronous communication between two applications deployed in two different machine. In your case, you want your one application works as message producer and other act as an message consumer, and both are deployed in different machine.
In this situations, you only need to configure the JMS administration object, connection factories and destinations, on one Application server and configure other application server to use those configuration using JMS resource adapter. you can well achieve this by configuring the JMS Resource Adapter. you need to check the Glassfish documentation.
If you don't want to break the JMS specification, always communicate with Messaging Provider through Resource Adapter.
I hope this helps.

JMS Adapter (for DI) does not allow passing username and password to JMS connection

Post Author: PLed76
CA Forum: Data Integration
JMS Adapter (for DI) does not allow passing username and password to JMS connection. It has those fields only for MSMQ. Our Production environment does not allow us to connect to JMS (we use Tibco EMS) anonymously, so it prevents us from use of Data Integrator. Is there any way to pass those params, or obtain the correct version of JMS Adapter, or obtain source codes of the JMS Adapter so we can correct them ourselves (we can send you the corrected sources back) ? Thanks in advance for any help. (PL)ed76 Renaissance Capital

Bump - Were having the same issue.
Has anyone found a way to connect to Tibco with a user/pwd?
Version 14.0.297.

How to control the jms transactiion in WLI

Hi,
I’m new to WLI integration area; I have JPD which will subscribe message from message broker channel via JMS event generator. i have requirement to put business validation and needs to rollback the message if validation fails with few seconds time delay(Thread. sleep(1000)). Not sure how to handle the JMS transaction explicit in JPD,
Any one have idea how to do the JMS transaction in JPD ?
thanks
Edited by: user650952 on Jul 26, 2009 7:35 PM
Edited by: user650952 on Jul 26, 2009 7:36 PM

I'm not familiar with WLI, but if you're using WebLogic JMS as the source destination, you can configure a "redelivery delay" on the destination and then force a message redelivery.
I assume that your JPD code doesn't have direct access to the javax.jms connection or session? In which case, you might be able to force a message redelivery by rolling back the current XA/JTA transaction (if there is one), or throwing a runtime exception. If the code is running from within an MDB, you can throw a "weblogic.ejb.NonDestructiveRuntimeException" exception to avoid the overhead of the MDB automatically destroying and recreating itself in response to the exception.
Tom

How to create OEMS JMS In-Memory and File-Based Persistence?

Anyone knows how to create OEMS JMS In-Memory and File-Based Persistence? Any help it is appreciated. I m working with Oracle BAM 11g TP4 and I want to test the capability of connecting directly to a JMS queue, and reading Oracle´s "complex" documentation I couldnt find the right way to make this happen.
tks

Hi Mario
This is explained in the soa developer's guide. Chapter 43 "Enterprise message source"should help you. You will find how to connect OEMS or JMS in-memory/file based to your BAM data objects with or without xpath transformation.
You can find sample of advanced XML formating in the 10g tech note: "Oracle BAM 10.1.3 configuration for BPEL 10.1.2 using JMS sensors" (useful even if you don't plan to use BPEL).
Anyway, if you plan to use BPEL, forget JMS and use the BAM adapter (chapter 42), it's quicker & easier.
Dominique

How to create OEMS JMS In-Memory and File-Based Persistence ? Anyone?

Anyone knows how to create OEMS JMS In-Memory and File-Based Persistence? Any help it is appreciated. I m working with Oracle BAM 11g TP4 and I want to test the capability of connecting directly to a JMS queue, and reading Oracle´s "complex" documentation I couldnt find the right way to make this happen.
tks

Hi Mario
This is explained in the soa developer's guide. Chapter 43 "Enterprise message source"should help you. You will find how to connect OEMS or JMS in-memory/file based to your BAM data objects with or without xpath transformation.
You can find sample of advanced XML formating in the 10g tech note: "Oracle BAM 10.1.3 configuration for BPEL 10.1.2 using JMS sensors" (useful even if you don't plan to use BPEL).
Anyway, if you plan to use BPEL, forget JMS and use the BAM adapter (chapter 42), it's quicker & easier.
Dominique

Maximum JMS Connections

          Hi,
          I would like to know what is the maximum JMS connections weblogic server can
          handle anytime. And where do we set this parameter? we have a group of Message
          Listeners listening to a Queue on weblogic by opening JMS connections at the same
          time. So I was wondering how many JMS clients can Weblogic handle?? And also does
          it impact the performance of weblgic server.
          Thanx,
          Sankas


          Thanks for the information guys. It was very helful.
          -Sankas
          Tom Barnes <[email protected]> wrote:
          >Each remote JVM to the WL server multiplexes network calls over a single
          >socket
          >connection, and each remote JVM may have many JMSConnections into the
          >WL server. A
          >single server can support thousands of remote JVMs, and tens of thousands
          >of
          >JMSConnections -- even with the default thread-pool sizes. Clustering
          >and
          >distributed destinations can help one scale higher. Of course, performance
          >and
          >scalability are highly application and hardware dependent, and the best
          >thing to do
          >is create a benchmark that emulates your particular apps characteristics
          >and see
          >how it scales...
          >
          >Tom, BEA
          >
          >Sankas wrote:
          >
          >> Shean,
          >> I did not have anything in mind. But if you see the weblogic console
          >there
          >> is a default parameter "JMS Thread Pool Size = 15" under the Server
          >section in
          >> the services/JMS Tab .
          >> I thought this was the JMSConnections count in the server.
          >> Well I think it would be good to know how far can we go
          >> with the JMS connections thing.
          >>
          >> Thanx,
          >> Sankas
          >>
          >> "Shean-Guang Chang" <[email protected]> wrote:
          >> > It will depend on the memory resource you used for the JVM (both
          >WLS
          >> >server
          >> >and client). There is no design limit for this. Do you have a number
          >> >in
          >> >mind?
          >> >"Sankas" <[email protected]> wrote in message
          >> >news:[email protected]...
          >> >>
          >> >> Hi,
          >> >> I would like to know what is the maximum JMS connections weblogic
          >> >server can
          >> >> handle anytime. And where do we set this parameter? we have a group
          >> >of
          >> >Message
          >> >> Listeners listening to a Queue on weblogic by opening JMS connections
          >> >at
          >> >the same
          >> >> time. So I was wondering how many JMS clients can Weblogic handle??
          >> >And
          >> >also does
          >> >> it impact the performance of weblgic server.
          >> >>
          >> >> Thanx,
          >> >> Sankas
          >> >
          >> >
          >

How WebLogic7.0 & 8.1 JMS connect to MSMQ?

Similar Messages

Maybe you are looking for