Category: Host Integration Server 2013


Hello,

You may have issues with the IBM MQ Client 7.5 and 8.0 together with BizTalk 2013 / 2013 R2 with Transactional Support set to true. You are getting an MQRC 2072 and you can see a lot of errors / warnings in the Event Log. This is actually a code defect in the 7.5.0.3 / 7.5.0.4 and 8.0.0.2 client.

IBM has worked on fixing this issues : http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg1IT07469

The issue is finally fixed in the following IBM MQ Clients :

  • 7.5.0.6
  • 8.0.0.4

Best Regards,

Advertisements

This cumulative update package for Microsoft Host Integration Server 2013 contains hotfixes for issues that were fixed after the release of Host Integration Server 2013.

We recommend that you test the hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included in the previous Host Integration Server 2013 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix.

Important This cumulative update package includes all the component packages. However, the cumulative update package updates only those features that are currently installed on the system.

Download Link : http://support.microsoft.com/kb/3019572

Many Thanks to the Product and Support TEAM ! You’ve done a great job

Hello folks,

When IBM released the IBM MQ 8 Client, there was no way to use it with BizTalk because the client was compiled in C++ 2012 and BizTalk 2013/2013 R2 still uses an older C++ Runtime. Officially this is not supported by Microsoft, but it works. Microsoft actually supports only IBM MQ Client 7.1 and 7.5 together with BizTalk Host Integration Server 2013 (MQSC). After some discussions with IBM and after some month, IBM decided to ship with its package also the C++ dlls compiled in 2005 Runtime.

IBM Article : https://www-01.ibm.com/support/knowledgecenter/#!/SSFKSJ_8.0.0/com.ibm.mq.dev.doc/q030490_.htm

The C++ 2005 Runtime dlls are available in IBM MQ Client 8.0.0.2 : http://www-01.ibm.com/support/docview.wss?uid=swg24037500

Best Regards,

Steve

Did you know that Host Integration Server 2013 supports IBM DB2 v11 ?

Yes, this is true! You only have to install Host Integration Server 2013 Cumulative Update 2 ! 🙂

This cumulative update package for Microsoft Host Integration Server 2013 contains hotfixes for issues that were fixed after the release of Host Integration Server 2013.

We recommend that you test the hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included in the previous Host Integration Server 2013 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix.

Important This cumulative update package includes all the component packages. However, the cumulative update package updates only those features that are currently installed on the system.

Download Link : http://support.microsoft.com/kb/2929767

Many Thanks to the Product and Support TEAM ! You’ve done a great job

As you have already noted, Microsoft BizTalk 2013 R2 (Host Integration Server 2013 MQSC) does not support working with IBM MQ Client 8.0. It is not even worth trying because BizTalk is using C++ 2008/2010 and IBM MQ Client 8.0 is using C++ 2012. The Process starting application must always be in the highest or equal Runtime that the client/child assemblies.

The only workaround is to use the IBM MQ Client 7.5 to connect to IBM MQ Server 8.0 (which is supported by IBM) : http://www-01.ibm.com/support/docview.wss?uid=swg21312967

You may get a MQRC Error 2072 using BizTalk 2013 together with HIS 2013.

If you are using the 7.5.0.x client, than you are facing the same issue as me. As far as I can debug the error is caused by the IBM MQ Client itself and not by the MQSC (HIS Adapter) or BizTalk. In my case changing the MQ Client from 7.5.0.3 to 7.0.1.12 fixed the issue.

Please let me know if you are facing a similar issue.

Best Regards,

Steve

The MQSC Adapter may generate excessive network traffic when it receives message from IBM WebSphere Application Server message queues. The overhead of the network traffic may be 4 to 10 times the size of the actual message that is being received from the message queue. The excessive network traffic can be observed in network traces that are used to capture data between the instance of Microsoft BizTalk Server that is using the MQSC Adapter and the IBM WebSphere system. The BizTalk Server does not report any errors or warnings when this occurs.

The MQSC Adapter uses multiple MQGET calls when it retrieves messages from an IBM WebSphere message queue. The excessive network traffic occurs because of the multiple MQGET calls that the MQSC Adapter uses when it reads the message.

  • The fix that resolves this issue is included in cumulative update package 1 for Host Integration Server 2013. Download
  • The fix that resolves this problem is included in cumulative update package 9 for Host Integration Server 2010. Download

 

This cumulative update package for Microsoft Host Integration Server 2013 contains hotfixes for issues that were fixed after the release of Host Integration Server 2013.

We recommend that you test the hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included in the previous Host Integration Server 2013 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix.

Important This cumulative update package includes all the component packages. However, the cumulative update package updates only those features that are currently installed on the system.

Download Link : http://support.microsoft.com/kb/2908834

Many Thanks to the Product and Support TEAM ! You’ve done a great job

You may encounter bad performance while mass inserting Data into a DB2 Table.

By default, the nagling is enabled on the TCP sockets. This improves overall performance, but it might briefly delay transmission of smaller packets. If the delay is undesirable or unacceptable (like delayed ACK), then you can add this entry to the registry to disable nagling only for the MsDb2 Provider :

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Host Integration Server\Data Integration\
and/or
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Host Integration Server\Data Integration\

Add the name TcpNoDelay to the subkey, set the data type to the REG_SZ data type, and then set the value to Yes.

For Host Integration Server 2009, you need to install first the following KB : KB978452

For Host Integration Server 2010, 2013, you only need to add the registry entry.