Add-AzureBizTalkArtifactAssembly
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
The Add-AzureBizTalkArtifactAssembly adds an assembly to the artifact store for the service namespace you enter.
Syntax
Add-AzureBizTalkArtifactAssembly –AcsNamespace <AcsNamespace> -IssuerName <IssuerName> -IssuerKey <IssuerKey> –DeploymentUri <DeploymentUri> -FilePath <FilePath> [-Overwrite] [<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. |
-FilePath <FilePath> |
Required |
The complete path to the artifact file to be uploaded. |
[-Overwrite] |
Optional |
A flag that specifies whether the existing artifacts in the artifact store must be overwritten. If an artifact already exists with the same name or at the same path, a ResourceExists error is thrown, unless the Overwrite parameter is passed. |
[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 add an assembly
Add-AzureBizTalkArtifactAssembly –AcsNamespace myACS -IssuerName owner -IssuerKey <issuer key> –DeploymentUri https://myDeploymentUri.biztalk.windows.net/default -FilePath C:\MyLocation\CustomCode.dll
Output
Successfully added artifact ‘CustomCode.dll’ to Artifact Store at https://myDeploymentUri .biztalk.windows.net/$GlobalArtifacts/$Assembly/CustomCode.CustomCode, CustomCode, Version=1.0.0.0, Culture=neutral, PublicKeyToken=15dc99171c58f11b
Error when trying to add an artifact that already exists
Add-AzureBizTalkArtifactAssembly –AcsNamespace myACS -IssuerName owner -IssuerKey <issuer key> –DeploymentUri https://myDeploymentUri.biztalk.windows.net/default -FilePath C:\MyLocation\CustomCode.dll
Output
ERROR: The specified artifact ‘CustomCode.dll’ already exists either with the same name or the same path in the artifact store at https://myDeploymentUri.biztalk.windows.net/$GlobalArtifacts/$Assembly/CustomCode.CustomCode, CustomCode, Version=1.0.0.0, Culture=neutral, PublicKeyToken=15dc99171c58f11b
Error when the provided artifact type is not supported
Add-AzureBizTalkArtifactAssembly –AcsNamespace myACS -IssuerName owner -IssuerKey <issuer key> –DeploymentUri https://myDeploymentUri.biztalk.windows.net/default -FilePath C:\MyLocation\PO.trfm
Output
ERROR: Artifact of type .trfm is not supported by this cmdlet
Successfully overwriting an existing artifact
Add-AzureBizTalkArtifactAssembly –AcsNamespace myACS -IssuerName owner -IssuerKey <issuer key> –DeploymentUri https://myDeploymentUri.biztalk.windows.net/default -FilePath C:\MyLocation\CustomCode.dll -Overwrite
Output
Successfully added artifact ‘CustomCode.dll’ to Artifact Store at https://myDeploymentUri .biztalk.windows.net/$GlobalArtifacts/$Assembly/CustomCode.CustomCode, CustomCode, Version=1.0.0.0, Culture=neutral, PublicKeyToken=15dc99171c58f11b