JMS Account

Overview

You can use this account type to connect JMS Snaps with data sources that use the JMS account.

Note: To let the JMS Account connection persist beyond a pipeline run, refer to JMS Account caching in Snap Configuration Settings.

JMS Account overview

Prerequisites

  • A valid JAR file.

Account settings

Note: Learn about the common controls in the Snap settings dialog.
Field/Field set Description
Label*

String

Specify a unique label for the account.

Default value: N/A

Example: JMS Account
Username

String

Optional. Specify a username necessary to create the connection to the JMS provider.

Default value: N/A

Example: [email protected]
Password

String

Specify the password associated with the JMS username.

Default value: N/A

Example: NAo93@$$!
Connection Factory

String

Specify the JNDI name for the JMS connection factory.

Default value: N/A

Example: Test_Connection
JNDI Properties*

Use this field set to configure additional JNDI properties for the JMS account. This field set contains the following fields:
Property Name Enter the name of the JNDI property.

Example: java.naming.factory.initial, java.naming.provider.url
Property Value Enter the value of the JNDI property.

Example: org.jnp.interfaces.namingcontextfactory

Note: HTTPS protocol is not supported for this field.
Jar files

Optional. Use this field set to add Jar files.

  • Jar file (String/Expression) - Specify the JAR files related to the JMS provider to produce and consume messages. The JMS account supports only SLDB and File protocols. If you do not provide a protocol, then the account uses SLDB by default.

    Example:

    • sldb:///myOrg/myProject/file1.jar
    • file:///home/snaplogic/fil2jar
    Note:
    • You can download the required JAR file from http://activemq.apache.org/download.html to your local system and upload it manually to the JMS account, which will be available in sldb (sldb:///myOrg/myProject/file1.jar) OR
    • You can directly provide the path in the account using file protocol, referring to these JAR files. (file:///home/snaplogic/fil2jar)

    You can find the JAR files associated with each vendor/provider from their web page:

    Note: You must include all ActiveMQ dependencies in the JAR files list to avoid errors upon execution of the Pipeline.

Troubleshooting

Error Reason Resolution
COULD_NOT_CREATE_SESSION The account settings are missing or invalid. Verify that the account settings are correct and valid.
NO_JAR At least one jar must be defined Define at least one jar file to use the JMS Snaps, such as activemq-all.jar.
JMS_ERROR The JMS account might not be configured properly. Verify that the JMS provider is available and that the account is properly configured.
ERROR_LOAD_FROM_CACHE Error while loading connections from the cache. Try again, if the problem persists and then raise a defect.