Loading...

JMS listener

Table of Contents

    JMS Listener

    The JMS listener is used to read from a JMS destination.

    This listener is a Message-driven listener. This means that the arrival of a message on the destination queue or topic, will activate the consumer. The listeners  output is a ConnectMessage.

    The ObjectToConnectMessageTransformer will convert the message from the destination to a fitting MessagePart and write it into a new message. 
    If a progress MultipartMessage is received, a ConnectMessage MultipartMessage will be generated. The JMS headers will be copied to the ConnectMessage headers.

    You can choose between Queues or Topics, the screen will adjust accordingly.

    Queues

    In the table below, you will find an explanation about these properties. All attributes with a ‘*’ are mandatory.

    All attributes with a ‘***, require at least one of these properties having been set.

    All attributes with a ‘°°°’, require at most one of these properties having been set.

    Attribute

    Description

    Name*

    By default, we fill this out with the technical ‘tag’, followed by a serial number. Changing the name is optional.

    Enabled

    Check this box if you want this consumer to be enabled.

    Consumer Autostart

    Consumer will be started at startup of the interface

    JMS Topology

    Here you can choose between Queue or Topic. The screen will adjust accordingly

    Request Queue Name***

    Name of queue to receive from. Only one request-destination-ref, request-queue-name OR request-topic-name can be set.

    Reply Queue Name

    Default queue to send reply to if sync=true and no header attribute JMSREPLY_TO.

    Synchronized

    Defines the consumer as request-response(true) or fire-forget(false). The default is false.

    When the synchronized mode is used, you must use a Message Reply in the Producer. The default setting is ‘false’, which means it is set to asynchronized. Setting this property to ‘true’ will make it synchronized.

    Timeout

    Time-out in miliseconds. After time-out has passed response will be sent to JMS Reply To when dealing with  a synchronized consumer.

    MessagePart

    Name of the MessagePart in a ConnectMessage where the content of the file is being stored. Not applicable when receiving a Progress Multipart.

    Connection Factory

    Reference to the connection factory to use. Default connection factory is named in property connect.connectionfactory.name in connectplaza-agent.properties. The default connection factory is activeMQ.

    Concurrent Consumers

    Specify the number of concurrent Consumers to create. The default value is 1.

    Specifying a higher value for this setting will increase the standard level of scheduled concurrent Consumers at runtime: This is effectively the minimum number of concurrent Consumers which will be scheduled at any given time. This is a static setting; for dynamic scaling, consider specifying the maxConcurrentConsumers" setting instead. Raising the number of concurrent Consumers is recommendable in order to scale the consumption of messages coming in from a queue. However, note that any ordering guarantees are lost once multiple Consumers are registered."

    Max Concurrent Consumers

    Specify the maximum number of concurrent Consumers to create. The default value is 1.

    If this setting is higher than concurrentConsumers", the listener container will dynamically schedule new Consumers at runtime, provided that enough incoming messages are encountered. Once the load goes down again, the number of Consumers will be reduced to the standard level ("concurrentConsumers") again. Raising the number of concurrent Consumers is recommendable in order to scale the consumption of messages coming in from a queue. However, note that any ordering guarantees are lost once multiple Consumers are registered."

    Description

    Description of the specific consumer. This is for documentation purposes.

    Topics

    In the table below, you will find an explanation about these properties. All attributes with a ‘*’ are mandatory.

    All attributes with a ‘***, require at least one of these properties having been set.

    All attributes with a ‘°°°’, require at most one of these properties having been set.

    Attribute

    Description

    Name*

    By default, we fill this out with the technical ‘tag’, followed by a serial number. Changing the name is optional.

    Enabled

    Check this box if you want this consumer to be enabled.

    Consumer Autostart

    Consumer will be started at startup of the interface

    JMS Topology

    Here you can choose between Queue or Topic. The screen will adjust accordingly

    Request Topic Name***

    Name of topic to receive from. Only one request-destination-ref, request-queue-name OR request-topic-name can be set.
    Reply Topic Name

     

    Default topic to send reply to if sync=true and no header attribute JMSREPLY_TO.

    Durable Topic

    Only valid if the request-topic-name is set. The topic will be durable if the value is set to true. The default is false.

    Durable Subscription name

    Name of the Subscription in case of a durable subscription.

    Synchronized

    Defines the consumer as request-response(true) or fire-forget(false). The default is false.

    When the synchronized mode is used, you must use a Message Reply in the Producer. The default setting is ‘false’, which means it is set to asynchronized. Setting this property to ‘true’ will make it synchronized.

    Timeout

    Time-out in miliseconds. After time-out has passed response will be sent to JMS Reply To when dealing with a synchronized consumer.

    MessagePart

    Name of the MessagePart in a ConnectMessage where the content of the file is being stored. Not applicable when receiving a Progress Multipart.

    Connection Factory

    Reference to the connection factory to use. Default connection factory is named in property connect.connectionfactory.name in connectplaza-agent.properties. The default connection factory is activeMQ.

    Concurrent Consumers

    Specify the number of concurrent Consumers to create. The default value is 1.

    Specifying a higher value for this setting will increase the standard level of scheduled concurrent Consumers at runtime: This is effectively the minimum number of concurrent Consumers which will be scheduled at any given time. This is a static setting; for dynamic scaling, consider specifying the maxConcurrentConsumers" setting instead. Raising the number of concurrent Consumers is recommendable in order to scale the consumption of messages coming in from a queue. However, note that any ordering guarantees are lost once multiple Consumers are registered."

    Max Concurrent Consumers

    Specify the maximum number of concurrent Consumers to create. The default value is 1.

    If this setting is higher than concurrentConsumers", the listener container will dynamically schedule new Consumers at runtime, provided that enough incoming messages are encountered. Once the load goes down again, the number of Consumers will be reduced to the standard level ("concurrentConsumers") again. Raising the number of concurrent Consumers is recommendable in order to scale the consumption of messages coming in from a queue. However, note that any ordering guarantees are lost once multiple Consumers are registered."

    Description

    Description of the specific consumer. This is for documentation purposes.

    Adding a new broker for JMS

    When you want to use a new JMS Broker within ConnectPlaza, you need to creat a new connectionfactory with the correct settings for your new JMS Broker. For instance you want to use ActiveMQ as an external Messaging broker. What to do?

    Open the file <connectplaza-install-directory>/context/custom-connection-factories.xml and add the settings for the ActiveMQ Broker.

    <bean id="amqConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
        <property name="brokerURL">
          <value>tcp://localhost:61616</value>
        </property>
    </bean>

    Change the default Connection Factory to the ID in this bean, i.e. amqConnectionFactory.

    After changing the XML file, restart the ConnectPlaza Agent.


    Copyright © 2018 ConnectPlaza.   For pricing, account management and more go to https://www.connectplaza.com

    About Connectplaza

    Si components version:   

    Lorem ipsum delore set

    Lorem ipsum delore set

    Window size is not optimal. Please enlarge for optimal experience

    No connection

    No response from the server. This window will automaticly disappear by an valid connection