Engine

Use the preferences option in the Operations Dashboard to manage engine configuration data.

QueueBasedFutureFactory

The QueueBasedFutureFactory manages responses in synchronous channel implementations.

  • Preferences node: /businesslayer/com/sybase365/mobiliser/util/messaging/channelmanager/engine/impl/QueueBasedFutureFactory
  • ConfigAdmin PID: com.sybase365.mobiliser.util.messaging.channelmanager.engine.impl.QueueBasedFutureFactory
You can set these configuration options:
Key Default Description
synchronousPollTimeout 60000 Sets the amount of time, in milliseconds, the queued thread waits for an answer before returning null. You can update this value at runtime.
synchronousOfferTimeout 60000 Sets the amount of time, in milliseconds, the response thread waits while trying to place the response on the queue before giving up. You can update this value at runtime.

PickupJmsMessages

The PickupJmsMessages picks up messages from configured JMS queues and forwards them to ChannelManager to be sent through a channel implementation. This links the JMS feature with the OSGi ChannelManager.

  • Preferences node: /businesslayer/com/sybase365/mobiliser/util/messaging/channelmanager/engine/jmspickup/PickupJmsMessages
  • ConfigAdmin PID: com.sybase365.mobiliser.util.messaging.channelmanager.engine.jmspickup.PickupJmsMessages
You can set these configuration options:
Key Default Description
sessionCacheSize 1 Sets the number of sessions to cache. Runtime updates are ignored. The pickup class makes use of a CachingConnectionFactory. See the Javadoc at: http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/jms/connection/CachingConnectionFactory.html.
maxConcurrentConsumers 1 Sets the number of consumers to create. Runtime updates affect only newly registered queues after the update. Listener containers that are already created are not destroyed and re-created. The pickup class makes use of a DefaultMessageListenerContainer. See the Javadoc at: http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/jms/listener/DefaultMessageListenerContainer.html.
mode standard Defines the mode for the picking up messages. For backward compatibility with older SMS Builder, such as Mobiler wizard, instances should set this value to legacy.

JmsReceiveCallback

The JmsReceiveCallback forwardsincoming messages to a JMS queues with the name of the destination supplied by the receiving channel. This links the JMS feature with the OSGi ChannelManager.

  • Preferences node: /businesslayer/com/sybase365/mobiliser/util/messaging/channelmanager/engine/jmsreceiver/JmsReceiveCallback
  • ConfigAdmin PID: com.sybase365.mobiliser.util.messaging.channelmanager.engine.jmsreceiver.JmsReceiveCallback
You can set these configuration options:
Key Default Description
sessionCacheSize 1 Sets the number of sessions to cache. Runtime updates are ignored. The pickup class makes use of a CachingConnectionFactory. See the Javadoc at: http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/jms/connection/CachingConnectionFactory.html.
mode standard Defines the mode for the picking up messages. For backward compatibility with older SMS Builder, such as Mobiler wizard, instances should set this value to legacy.

ActiveMQConnectionConfiguration

The ActiveMQConnectionConfiguration configures a JMS connection factory that is used by some OSGi ChannelManager components.

  • Preferences node: /businsslayer/com/sybase365/mobiliser/util/messaging/channelmanager/engine/jmsconnection/ActiveMQConnectionConfiguration
  • ConfigAdmin PID: com.sybase365.mobiliser.util.messaging.channelmanager.engine.jmsconnection.ActiveMQConnectionConfiguration
You can set these configuration options:
Key Default Description
brokerURL tcp://localhost:61616 Defines the URL of the JMS broker to use for the connection.
startBroker false Indicates whether to start the broker.  If true, the broker starts automatically.
Related concepts
Node and System Preferences
Related tasks
Adding a Preference Node