Step 1: Stop applications with a reference

Note

For a BizTalk Enterprise environment with several processing nodes, the following steps must be repeated on each server before you perform the restart!

In this step, you will make sure to unload the binaries in use.

1. Stop all the BizTalk Host Instance(s) associated with the Nodinite LDAP Adapter for Microsoft BizTalk Server
2. Close the BizTalk administration console

Repeat sub-step 1 and 2 on all nodes before proceeding to the next step

Step 2: Remove the old binaries

In this step, you will remove the old binaries from the GAC.

As the local administrator, using an elevated Powershell command prompt, execute the script below:

[System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")
$publish = New-Object System.EnterpriseServices.Internal.Publish
$publish.GacRemove("C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\IS.BizTalk.Adapters.LDAP.Mgmt_v1_0.dll")
$publish.GacRemove("C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\IS.BizTalk.Adapters.LDAP_v1_0.dll")
$publish.GacRemove("C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\Primer.dll")

You may need to adjust the actual folder. The template script uses the default settings from what was set during the installation

Step 3: Copy new binaries

In this step, you will update the binaries in the installation folder.

1. Read the [Release Note][] to make sure you are aware of all changes (breaking changes are rare)
2. Unzip the ZIP package with the new version to the installation folder, usually: C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\
3. Make sure to unblock all the new files. You can use the template Powershell script below:

Get-ChildItem -Path 'C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\' -Recurse | Unblock-File

Repeat sub-step 1 and 2 on all nodes before proceeding to the next step

Step 4: Register the new binaries

In this step, you will re-register the binaries from the installation folder.

1. Use the template Powershell script below to get the new binaries properly registered with the GAC:

[System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")
$publish = New-Object System.EnterpriseServices.Internal.Publish
$publish.GacInstall("C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\IS.BizTalk.Adapters.LDAP.Mgmt_v1_0.dll")
$publish.GacInstall("C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\IS.BizTalk.Adapters.LDAP_v1_0.dll")
$publish.GacInstall("C:\Program Files (x86)\IS BizTalk LDAP Adapter 1.0\Test Client Utility\Primer.dll")

Repeat sub-step 1 on all nodes before proceeding to the next step

Step 5: Validate the update

In this step, you will validate the new binaries.

1. Make a Test using the Windows Forms-based client.

Repeat sub-step 1 on all nodes before proceeding to the next step

Step 5: Restart BizTalk Host Instances

In this step, you will restart the BizTalk Host Instances using the new binaries.

1. Start the BizTalk Host instance(s)
2. Re-open the BizTalk Server Administration console (MMC) to re-read the DLLs from the GAC

Troubleshooting

Common problems are further detailed in the troubleshooting guide.

Support

Contact our Support for additional guidance if you fail to resolve the update problem.

Note

Additional information to aid the troubleshooting may exist in the Windows Event Logs.

Next Step

[Developer guide] LDAP Documentation for developers

Related

Prerequisites