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)

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:
#

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

2. Message Type: Custom Message. It sends a custom message to the destination as text or binary. Variable replacement is supported. It can loop through incoming files to sum up for example their names or paths.

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

4. 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 or 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