Known issues with BizTalk Server 2020 RosettaNet accelerator (Part 1)

As we all know, BizTalk Server 2020 thoroughly removed old native SQL adapter and replaced it with WCF-SQL adapter. This change has resulted in several known issues with some existing components like RosettaNet accelerator(BTARN) that used old SQL adapter previously.

Before Microsoft releases official fix of the BTARN problems, you can also follow the steps below to work around them by yourself.

Steps:

First of all, you need to correct the binding of receive locations: LOB_To_PrivateInitiator and LOB_To_PrivateResponder.

• Use XmlPolling
• Set Xml SP Root Node Name to:                 LOBMessage
• Set Xml SP Namespace to:                            http://schemas.microsoft.com/biztalk/btarn/2004/LOBMessage
• PolledDataAvailableStatement to:            Select 1

See the screenshots below:

After that, you also need to correct binding of Send ports: PrivateInitiator_To_LOB and PrivateResponder_To_LOB.

Especially pay attention to the SOAP Action header:

A further problem was that PrivateInitiator_To_LOB port uses an outbound map to transform LOBMessage into the schema of native SQL adapter(SQLSCMessageOut) before being inserted into MessagesToLOB table.

In this case, we also need to generate new Wcf-Sql based schema and create corresponding map to transform LOBMessage Into Wcf-Sql Insert message:

The generated schema and map files I use are in attachment. The script functoid in the map is quite simple that converts string type Delivered value("0" or "1") to boolean.

public bool getDelivered(string delivered)
{
    if(delivered == "1") 

         return true;
    return false;
}

The same changes need to be applied to PrivateResponder_To_LOB port as well.

After all the above changes, the BTARN Loopback sample should be back to work fine. Next, let's move on and continue to resolve issues with DoubleAction scenario:

Known issues with BizTalk Server 2020 RosettaNet accelerator (Part 2)