In this article
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
You can use this account type to connect Azure Service Bus Snaps with data sources that use Azure Service Bus accountsaccount.
Prerequisites
None.
Limitations and Known Issues
...
Field Name | Field Type | Field Dependency | Description |
|---|---|---|---|
Label* | String | N/A | Specify a unique label for the account. Default Value: ELT Database Account None |
Connection String Source | Dropdown list | Yes | Choose the source of the connection string. Available options are:
Default Value: User Provided |
Namespace* | String/Expression | Enabled on selecting Snap Generated for Connection String Source. | Specify the name of the Namespace that you have created on Azure portal. Default Value: N/A |
Shared Access Key Name | String/Expression | Enabled on selecting Snap Generated for Connection String Source. | Specify the shared access key name of the keys for Azure Service Bus on Azure portal. Default Value: RootManagerSharedAccessKey |
Shared Access Key* | String/Expression | Enabled on selecting Snap Generated for Connection String Source. | Specify the primary key from the connection string for Azure Service Bus. Default Value: N/A |
Connection String | String/Expression | N/A | Specify the connection string from the Azure Service Bus portal for the namespace. Default Value: N/A |
...
Error
Reason
Resolution
Account validation failed.
The Pipeline ended before the batch could complete execution due to a connection error.
Verify that the Refresh token field is configured to handle the inputs properly. If you are not sure when the input data is available, configure this field as zero to keep the connection always open.
Snap Pack History
| Expand | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438341/Getting+Started
Configuring Azure Service Bus Account
Application configuration in Azure Portal for Azure Service Bus account