I\'m working in a project that requires to send multiple messages to another application via asynchronous Websphere MQ messages. Actually I\'m opening and closing sessions for every message I send. I
I\'m working on the existing application that uses transport layer with point-to-point MQ communication.
I need to implemt a pulling consumer. Most of the examples I see are the producer pushing a message to the consumer; Assuming consumer is always up.
What is better design Is it better to have one listener and separate processing in this listener for two types of emssages.
So here\'s my problem! I Have a Tibco EMS topic with authentication I have a standalone app I\'d like to pub and consume messages from this
I need a system in which I can send SOAP request to 1 server from a few and then if server has this service it calls and returns value to client.
I have Weblogic 10.3.4 with a cluster of 2 managed servers, each with a JMS server. I also have a clustered JMS module with several \"Uniform Distributed Queue\"s. I have verified via a simple Java cl
I have a Weblogic 10.3.4 clustered JMS setup with 2 managed servers. Right now, each managed server has its own IP address. I have installed Apache and the Weblogic plugin as described here: http://do
I am trying to configure clustered JMS on Weblogic 10.3.4. I have a 4开发者_StackOverflow社区 node cluster plus my AdminServer already configured. I also have my JMS already configured and targeted
Assume there are 2 web services A and B setup in SOA infrastructure. Web services A depends on information that is available from the locally installed Desktop application (its a legacy application b
加载中,请稍侯......