Configuring the Nodinite LDAP Adapter for Microsoft BizTalk Server
This guide describes additional configuration post installation steps that are required
License
The product requires a valid license key. The license key is available as either a full version and a trial version.
The license has the following two properties:
- Customer Name : The name of the licensee. This name will always be part of the XML Response message summary within the
element. Note, this value must be entered exactly as given from Integration Software product support team (case sensitive). - License key : The per customer unique encrypted license key value.
You must add this information to the config file (IS.BizTalk.Adapters.LDAP.Windows.ClientTestUtility_v1_0.exe
) of the test client and on each send handler associated with the Nodinite LDAP Adapter for Microsoft BizTalk Server in the BizTalk administration console.
Repeat the process for each send handler by selecting the handler and click on 'Properties'
Associate the appropriate Host Instance(s) as Send Handler
Click Apply/Ok when you are done editing.
If the provided license information is invalid, you are faced with the following error dialogue:
Contact support @ nodinite.com to obtain a valid license for this product and/or to resolve issues with this mandatory step.
Image example from the BizTalk Server administration console
Important
You must apply the license key for each new and/or changed BizTalk host instance associated with the adapter.
For example: You have 2 send handlers associated with the adapter. You must repeat and enter the license key information 2 times. 1 for each send handler.
SSO
This step is only required if you intend to use the SSO feature.
The LDAP Adapter 1.0 was built targeting BizTalk Server 2013 R2. The SSO assembly being loaded during run-time may be of another version. The .NET framework version is 4.0 so the adapter can be used on all BizTalk Server versions beginning with BizTalk Server 2010 and later.
To determine the version of SSO on the computer, check the Server and Administration values at the following registry location. The correct value for a BizTalk Server 2013 R2 environment is 9.0.2096.0.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ENTSSO
The assembly Microsoft.BizTalk.Interop.SSOClient.dll file can also be used to verify the version of SSO. The default location for this assembly is C:\Program Files\Common Files\Enterprise Single Sign-On. For BizTalk 2013 R2 environment, the file version is 9.0.2096.0 and the .NET version is 9.0.1000.0.
Manual changes:
If your version of BizTalk is not BizTalk Server 2013 R2 you must edit the content of your BizTalk configuration file with an assembly redirect as shown in the example below.
Important
You must backup your configuration files BEFORE changing them. If you invalidate these file BizTalk may not be able to start the host instances, see http://msdn.How to Back Up The BizTalk Server Configuration for help on performing a backup your configuration files.
Files to edit (usually in C:\Program Files (x86)\Microsoft BizTalk Server 201x folder):
- BTSNTSvc.exe.config – for 32 bit enabled host instances
- BTSNTSvc64.exe.config – for 64 bit enabled host instances
Change the version number highlighted in yellow according to the SSO Assembly version you have installed on your machine, see table for additional information about these versions.
BizTalk 2013 R2 example:
<configuration>
…
<runtime>
<assemblyBinding xmlns='urn:schemas-microsoft-com:asm.v1' appliesTo='v4.0.30319'>
<dependentAssembly>
<assemblyIdentity name='Microsoft.BizTalk.Interop.SSOClient' publicKeyToken='31bf3856ad364e35' culture='neutral' />
<bindingRedirect oldVersion='0.0.0.0-1000.0.0.0' newVersion=' 7.0.2300.0'/>
</dependentAssembly>
</assemblyBinding>
…
Important
Make sure to change both 32 and 64 bit versions on all nodes.
Target environment:
BizTalk Version | Change required | SSO Assembly Version | SSO Product Version |
---|---|---|---|
BizTalk 2020 | No | ||
BizTalk 2016 | No | ||
BizTalk 2013 R2 | Yes | 9.0.1000.0 | 9.0.2096.0 |
BizTalk 2013 | Yes | 7.0.2300.0 | 9.0.1865.0 |
BizTalk 2010 | Yes | 5.0.1.0 | 6.0.4219.0 |
If you changed the content of the configuration files you must now restart the host instances.