In this article
You can use this account type to connect JMS Snaps with data sources that use the JMS account.
None.
None.
|
Field Name | Field Type | Description | |
---|---|---|---|
Label* Default Value: [None] | String | Specify a unique label for the account. | |
Username Default Value: N/A | String | Specify a username necessary to create the connection to the JMS provider.
| |
Password Default Value: N/A | String | Specify the password associated with the JMS username. | |
Connection Factory* Default Value: N/A | String | Specify the JNDI name for the JMS connection factory. | |
JNDI Properties* Default Value: N/A | Use this field set to configure additional JNDI properties for the JMS account. This field set contains the following fields:
| ||
Property Name* Default Value: N/A
| String | Enter the name of the JNDI property. | |
Property Value* Default Value: N/A | String | Enter the value of the JNDI property.
| |
Jar files | Use this field set to add Jar files. | ||
Jar file Default Value: N/A
| String/Expression | Supply the necessary JAR files related to the JMS provider to produce and consume messages.
Popular vendors are:
You can find the JAR files associated with each vendor / provider from their web page. |
Error | Reason | Resolution |
---|---|---|
| The account settings are missing or invalid. | Verify that the account settings are correct and valid. |
| At least one jar must be defined | Define at least one jar file to use the JMS Snaps, such as |
| The JMS account might not be configured properly. | Verify that the JMS provider is available and that the account is properly configured. |
| Error while loading connections from the cache. | Try again, if the problem persists and then raise a defect. |