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

Microsoft

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.

 

 

See the screenshots below:

 

WenJun_Zhang_0-1586502445273.jpeg

 

 

WenJun_Zhang_1-1586502445283.jpeg

 

WenJun_Zhang_2-1586502445290.jpeg

 

 

WenJun_Zhang_3-1586502445295.jpeg

 

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:

WenJun_Zhang_4-1586502445300.jpeg

 

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.

 

WenJun_Zhang_5-1586502445302.png

 

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:

 

WenJun_Zhang_6-1586502445309.jpeg

 

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) 

6 Replies

@WenJun_Zhang Hi

thanks you for this post. Very usefull. What is the configurazion for Binding and Behaviour for PrivateInitiator_To_LOB and PrivateResponder_To_LOB?

Let me know

Thanks in advance

BTARN CU1 for BizTalk 2020 has been released to fix this issues. Thanks.

@WenJun_Zhang 

I use SubmitRNIF function to submit rosettanet message ,  I got the following error, any solution?

Source module:
PublicInitiatorProcess

Correlation information:

PIP Code : NotSet
PIP Version : NotSet
PIP InstanceID: NotSet
SourcePartnerName : NotSet
DestinationPartnerName : NotSet

Description:
The type initializer for 'Microsoft.Solutions.BTARN.Shared.PerformanceCounters' threw an exception.

Hi ankeyfu
The configuration on RN is ok? PIP Code : NotSet
PIP Version : NotSet
PIP InstanceID: NotSet
SourcePartnerName : NotSet
DestinationPartnerName : NotSet
are setup in BTARN Administration Console?
Best regards

@Enrico2103 

Hi Enrico2013,
Yes, the configuration on RN is ok, and the summited message can also be insert in to messagebox
table successfully,

ankeyfu_2-1637740988624.png

 

ankeyfu_0-1637740868565.png

ankeyfu_1-1637740925254.png

 

 

@WenJun_Zhang @Enrico2103 

If you've got it working, can you please paste the screenshots of the bindings for the 2 send ports and 2 receive ports in question. I'm close to get it going but missing something in the bindings. Just applying BizTalk 2020 Rosettanet Adapter CU1 did not seem to resolve the port configuration.