Start-AzureBizTalkBridgeSource
Important
Microsoft Azure BizTalk Services (MABS) is being retired, and replaced with Azure Logic Apps. If you currently use MABS, then Move from BizTalk Services to Logic Appsprovides some guidance on moving your integration solutions to Logic Apps.
If you're brand new to Logic Apps, then we suggest getting started here:
-
Create your first logic app, or quickly get started using a pre-built template
-
View all the available connectors you can use in your logic apps
You can have more than one source associated with a bridge configuration. The Start-AzureBizTalkBridgeSource starts one or all the sources deployed as part of a bridge configuration. If the <SourceName> parameter is passed, then that particular source is started. Otherwise, all the sources for the bridge are started.
Syntax
Start-AzureBizTalkBridgeSource –AcsNamespace <AcsNamespace> -IssuerName <IssuerName> -IssuerKey <IssuerKey> –DeploymentUri <DeploymentUri> -BridgePath <Path> [-SourceName <SourceName>] [<CommonParameters>]
Parameters
Parameter |
Requirement |
Description |
---|---|---|
-AcsNamespace <AcsNamespace> |
Required |
The Access Control namespace associated with BizTalk Services. |
-IssuerName <IssuerName> |
Required |
The Access Control issuer name. Specifying incorrect Access Control credentials results in an authentication error. |
-IssuerKey <IssuerKey> |
Required |
The Access Control issuer key. Specifying incorrect Access Control credentials results in an authentication error. |
-DeploymentUri <DeploymentUri> |
Required |
The deployment URI for BizTalk Services. For example, https://myDeploymentUri.biztalk.windows.net/default/. Specifying an incorrect URL will result in an ObjectNotFound error. |
-BridgePath <Path> |
Required |
The name of the bridge that you want to start the sources for. |
[-SourceName <SourceName>] |
Optional |
The bridge source name that you want to start.
|
[CommonParameters] |
Optional |
Can be used with any cmdlet and are implemented by Windows PowerShell. Options include:
get-help about_commonparameters provides detailed information about these common parameters. about_CommonParameters is also a good resource. |
Examples
Successfully start a bridge source
Start-AzureBizTalkBridgeSource –AcsNamespace myACS -IssuerName owner –IssuerKey <issuer key> –DeploymentUri https://myDeploymentUri.biztalk.windows.net/default -BridgePath XmlOneWayBridge1 –SourceName mySource
Output
Source ‘mySource’ for bridge ‘https://myDeploymentUri.biztalk.windows.net/default/XmlOneWayBridge/’ has been started successfully.
Error when the specified source does not exist
Start-AzureBizTalkBridgeSource –AcsNamespace myACS -IssuerName owner –IssuerKey <issuer key> –DeploymentUri https://myDeploymentUri.biztalk.windows.net/default -BridgePath XmlOneWayBridge1 –SourceName nonExistantSource
Output
ERROR: Source ‘nonExistantSource’ doesn’t exist for bridge ‘https://myDeploymentUri.biztalk.windows.net/default/XmlOneWayBridge/’
Successfully starting multiple sources for a bridge
Start-AzureBizTalkBridgeSource –AcsNamespace myACS -IssuerName owner –IssuerKey <issuer key> –DeploymentUri https://myDeploymentUri.biztalk.windows.net/default -BridgePath XmlOneWayBridge1
Output
The following sources were started for bridge ‘https://myDeploymentUri.biztalk.windows.net/default/XmlOneWayBridge/’ mySource1mySource2mySource3
Behavior when no sources exist for the specified bridge
Start-AzureBizTalkBridgeSource –AcsNamespace myACS -IssuerName owner –IssuerKey <issuer key> –DeploymentUri https://myDeploymentUri.biztalk.windows.net/default -BridgePath XmlOneWayBridge1
Output
No sources exist for bridge ‘https://myDeploymentUri.biztalk.windows.net/default/XmlOneWayBridge/’