Page History

...

• The only restriction on Map Messages is that this component does not support Objects in Map Messages.
• When adding the Initial Context Factory class for non Fiorano MQ server, the jar file(s) should be added as resource(s) to the JMSAdapters system library.
• For creating Durable Subscriber, use Topic Connection Factory in place of Unified Connection Factory.
• If IsDurableSubscriber property is changed to No or Destination Type is changed from Topic to Queue or ClientID is changed - the durable subscriptions created earlier should be unsubscribed to avoid persisting messages for the durable subscriber in runtimedata. For more information on unsubscribing, please refer to FioranoMQ Handbook - Section 29.3: Connecting to Web Management Tool - DurableSubscribers view.
• If a timeout is not specified (left as zero – infinite), and after starting the component, the JMS server (to which the component is connected) crashes, the receive call on the Queue or Topic waits endlessly. Therefore, it is advisable to give a definite timeout value.
• If the component is being used in scheduling mode, the execution timeout for the component should be less than the scheduler interval if the message is being received from a Queue.
• The property 'Cleanup resources (excluding connection) after each document' is set to 'No' by default. If this is set to 'Yes', then only one message is received by JMSOut and after that resources like message consumers are closed and the component will not receive further messages.

...

• %BEA_HOME%\server\lib\wlclient.jar
• %BEA_HOME%\server\lib\wljmsclient.jar (required only when the Weblogic server is running on a remote machine)

• %BEA_HOME%\server\lib\wlthint3client.jar (required only when the Weblogic server is running on a remote machine)

  Note
  Note: For For BEA Weblogic 10.3, %BEA_HOME% refers to <BEA WebLogic Installation directory>\wlserver_10.3

...

• %JBOSS_HOME%\client\jnp-client.jar
• %JBOSS_HOME%\client\jboss-common-client.jar
• %JBOSS_HOME%\client\jbossmq-client.jar
• %JBOSS_HOME%\client\jboss-client.jar

JBOSS6.0.0

Along with the JBoss jars mentioned above, add the below jars as well:

• hornetq-core-2.2.13.Final.jar
• hornetq-jms-2.2.13.Final.jar
• hornetq-ra-2.2.13.Final.jar
• jboss-as-build-config.jar
• jboss-ejb-api_3.1_spec.jar
• jboss-ejb-client.jar
• jboss-logging.jar
• jboss-marshalling.jar
• jboss-marshalling-river.jar
• jboss-remote-naming.jar
• jboss-remoting.jar
• jboss-sasl.jar
• jboss-transaction-api_1.1_spec.jar
• jgroups.jar
• netty.jar
• xnio-api.jar
• xnio-nio.jar

...