...
You can use this account type to connect <Snap Pack name> JMS Snaps with data sources that use <Account Type Name> the JMS account.
Prerequisites
...
None.
...
Valid tenant URL.
Limitations
...
and Known Issues
None.
Account Settings
...
Info |
---|
|
Field Name | Field Type |
---|
Field Dependency
Description |
---|
Default Value:
Example:Label* Default Value: |
[None] |
JMS Account | String |
None.
Specify a unique label for the account. | |
Username Default Value: N/A |
String | Specify |
This field set consists of the following fields:
Field 1
Field 2
Field 3
Field 1*
Default Value:
Example:
String
Debug mode checkbox is not selected.
Field 2
Default Value:
Example:
String
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. |
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:
|
Troubleshooting
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. |
Snap Pack History
...