JMS Account

In this article

Overview

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

Prerequisites

None.

Limitations and Known Issues

None.

Account Settings

  • Asterisk ( * ): Indicates a mandatory field.

  • Suggestion icon ( ): Indicates a list that is dynamically populated based on the configuration.

  • Expression icon ( ): Indicates whether the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Add icon ( ): Indicates that you can add fields in the fieldset.

  • Remove icon ( ): Indicates that you can remove fields from the fieldset.

Field Name

Field Type

Description

Field Name

Field Type

Description

Label*

 

Default Value: [None]
ExampleJMS Account

String

Specify a unique label for the account.

 

Username

 

Default Value: N/A
Example: admin@snaplogic.com

String

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

Password

 

Default Value: N/A
Example: NAo93@$$!

String

Specify the password associated with the JMS username.

 

Connection Factory*

 

Default Value: N/A
Example: Test_Connection

String

Specify the JNDI name for the JMS connection factory.

 

JNDI Properties*

 

Default Value: N/A
Example:

Use this field set to configure additional JNDI properties for the JMS account. This field set contains the following fields:

  • Property Name

  • Property Value

Property Name*

 

Default Value: N/A
Example: java.naming.factory.initial, java.naming.provider.url

 

String

Enter the name of the JNDI property.

 

 

Property Value*

 

Default Value: N/A
Example: org.jnp.interfaces.namingcontextfactory

String

Enter the value of the JNDI property.

HTTPS protocol is not supported for this field.

Jar files

 

 

Use this field set to add Jar files.

Jar file

 

Default Value: N/A
Example: http://activemq.apache.org/download.html

 

String/Expression

Supply the necessary JAR files related to the JMS provider to produce and consume messages.

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

Popular vendors are:

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

Account Encryption

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.

Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected for this account.

Account:

  • High: Password

  • Medium + High: Username, password

  • Low + Medium + High: Username, password, Connection Factory, JNDI Property values.

Troubleshooting

Error

Reason

Resolution

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.

Snap Pack History