This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

About Java Message Service: https://en.wikipedia.org/wiki/Jakarta_Messaging

Supported protocol: AMQPS (https://en.wikipedia.org/wiki/Advanced_Message_Queuing_Protocol)

!!! From 10.4.0_24+: Dependency jar files must be downloaded (unzip) and placed in your CrushFTP ▸ plugins ▸ lib folder. Restart is required to load the new JMS-related dependency jars.Dependency : jms_dependency.zip

1. Solace JMS AMQPS Integration
#

About Solace JMS : https://docs.solace.com/API/AMQP/Why-AMQP.htm

Get the AMQPS URL, user name, and password for JMSTask's JNDI config from the Solace Broker Management.

2. JMSTask configuration:
#

2.1 JNDI config: Variable replacement is supported.
#

About Java Naming and Directory Interface: https://en.wikipedia.org/wiki/Java_Naming_and_Directory_Interface
It stores the connection settings and required destinations (Topic and Queue).



Configuration example:

# Context Factory
java.naming.factory.initial=org.apache.qpid.jms.jndi.JmsInitialContextFactory

# Secured AMQP Host 
connectionfactory.qpidConnectionfactory=amqps://mr-connection-XXXXd:56XX

#User name and password
username=solace-XXXX
password=rsaXXXXXX
#Topic name
topic.my_topic_name=my_topic_name
queue.my_queue=my_queue

2.2 Producer Mode:
#

Sends messages to the given destination topic or queue.



1. Destination name: Name of the Topic or Queue configured on JNDI config. Variable replacement is supported (CrushTaskVariables).

2. Advanced Options:

Persistent: Delivery mode Persistent means the message is not lost when a messaging provider goes down for any reason and comes up again.
Time to live: When the message is published, the specified time to live is added to the current time to give the expiration time
Priority: There are 10 priority levels, 0 to 9. As per the JMS standard, a message with priority 0-4 is the normal priority, and 5-9 is considered an expedited priority.

3. Message Type: Custom Message: Send a custom message to the destination as text or binary. Variable replacement is also supported. You can loop through incoming files and send as many custom messages with file-related pieces of information like name, path, or URL.

4. Message Type: Send files: It sends the file content in binary mode. Max file size allowed: 10 MB.

2.3 Consumer Mode:
#

Receive messages from the given destination topic or queue.


1. Destination name: Name of the Topic or Queue configured on JNDI config. Variable replacement is supported (CrushTaskVariables).

2. Message settings: Limit the number of messages, and control the read timeout of message reading.

3. Store settings: It saves the message (less than 10MB) as a file to the given location. Provide the file name and make it unique to avoid overwriting. Variable replacement is supported.
Message-related variables:

{message_id}, {message_priority}, {message_expiration}, {message_type}, {message_correlation_id}, {message_reply_to}