JMS template inputs You use the Inputs tab of the activity designer to create variables to pass into the activity. You can test the JMS connection between the MID Server and the connection factory without having to run the acvitity in a workflow context. For details, see Test JMS activity template inputs.Note: Variable strings in the Inputs tab have a 255 character limit. Figure 1. JMS activity Inputs tab Table 1. JMS input fields Field Description Input Input variable builder. Create variables to map to available fields. Connection factory Connection factory that is configured to connect to a JMS provider. This value contains the name of the initial context factory and the URL of the JMS provider location. Destination type Type of destination used for this message. The choices are: Queue: Message is queued for point-to-point communications. Get operation is only supported for the Queue destination type. Topic: Message is used for publish and subscribe communication. Destination name Name of the queue or topic destination that is configured on the JMS provider. Message type Type of the message. This is the same as the JMS message type value. Currently, only the TextMessage type is supported. Make sure that a queue or topic destination is configured to receive or send only TextMessage. Other message types are dropped, since the JMS Activity cannot process them. Operation The programatic operation to perform on the destination. The choices are Put and Get. Timeout (Secs) Allowed time to wait for a message in the message queue before it times out, in seconds. The default is 30. Custom message headers Custom header values in a name/value pair format, that is available on the JMS destination Message payload Actual message content or payload that is sent to the JMS destination. Credential tag Specific credential tag this activity must use to run JMS commands on the host. Required MID Server capabilities MID Server to use, by capabilities. Test JMS activity template inputsYou can test the input parameters of a custom JMS activity during its development without having to run the activity in a workflow context.