Category: Host Integration Server 2010


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

 

Advertisements

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.

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

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 2010 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/2897923

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

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

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 2010 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/2850493

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

Over the last months I’ve read a lot of articles why the MQSC Adapter is missing in the BizTalk Administration Console, but none of them are complete.

Installation guide
So in order to install the adapter, you need to install the client tool from HIS (Microsoft BizTalk Adapters for Host Systems) and you will also need the to install the IBM WebSphere MQ Client or the IBM WebSphere MQ Transactional Client (which is part of the IBM WebSphere MQ Server).

Be aware that for any BizTalk version prior to BizTalk 2009 you can only run this adapter as a 32bit. You need to install the following KB939202 to force it to run as a 32bit on a 64bit environment.

Installation order

  1. Install the Microsoft BizTalk Server
  2. After the installation of the Microsoft BizTalk Server, don’t forget to configure the BizTalk Server using the Configuration Tool (if you skip the configuration, the BizTalk Adapters (MQSC, HostApps, DB2) will not be installed correctly
  3. Install the latest Microsoft BizTalk Server Cumulative Updates
  4. Install the IBM WebSphere MQ Client or the IBM WebSphare MQ Transactional Client
  5. Install the latest IBM WebSphere MQ FixPacks
  6. Install the Microsoft BizTalk Adapters for Host Systems (1.0 : 2006, 2.0 : 2009) or the Microsoft Host Integration Server 2010, 2013 and check the BizTalk Adapters to install
  7. Install the latest Microsoft Host Integration Server Cumulative Updates

Troubleshooting

  • You are getting an error that the MQSC COM+ are not correctly registered

Check if the MQSC Com+ Object is registered (Administrative Tools => Component Services => My Computer => COM+ Applications => Microsoft.BizTalk.Adapter.MQSC

If it’s missing you can try the following to register the COM+ Objects again :

  • Go to the “Programs and Features”
  • Modify the Host Integration Server Installation by using the repair feature

If it’s still missing, please try the following commands :

  • %windir%\Microsoft.NET\Framework\v2.0.50727\RegSvcs.exe /u “%snaroot%\Microsoft.BizTalk.Adapter.MQSC.dll” %windir%\Microsoft.NET\Framework\v2.0.50727\RegSvcs.exe “%snaroot%\Microsoft.BizTalk.Adapter.MQSC.dll”

If this is a 64-bit box, and they are installing the 64-bit MQSC adapter, then the commands would be slightly different (“Framework64” instead of “Framework”), so they would be:

  • %windir%\Microsoft.NET\Framework64\v2.0.50727\RegSvcs.exe /u “%snaroot%\Microsoft.BizTalk.Adapter.MQSC.dll” %windir%\Microsoft.NET\Framework64\v2.0.50727\RegSvcs.exe “%snaroot%\Microsoft.BizTalk.Adapter.MQSC.dll”
  • The MQ Transactional is not working and you are getting an MQRC 2354

Check my other article : https://stevemelan.wordpress.com/2011/09/12/using-ibm-mq-transactional-client-with-biztalk/

Check if you have installed the latest IBM WebSphere MQ FixPack : http://www-01.ibm.com/support/docview.wss?uid=swg1IC81688

Best Regards,

Steve MELAN

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

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 2010 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/2783797

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

When a two-phase commit transaction is performed in a Microsoft Host Integration Server 2010 environment, the Host Integration Server TCP/IP Resync service may not start. This problem occurs because an incorrect IP structure is passed back when the IP addresses of the resource managers are enumerated.

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

You may get the following error when using 2 Phases Commit together with the HIS LU62 Resync Service :

HISETBG0001 Application Integrator has intercepted an exception in method XXXXX. Following is the exception description:

HISMSNA0022 The SNATransport, when processing method XXXXX, has failed when attempting to enlist in a transaction.

Ensure that the remote LU name XXXXX is configured to EnableSyncPoint. “Error in call to iDtcLuRmEnlistmentFactory ->Create,

HRESULT = 8004D10D or HRESULT = 8004D108

To resolve this issue, you only have to do the following steps

  1. Stop the SNA LU 6.2 Resync Service
  2. Stop DTC
  3. Clear DTC log è MSDTC -resetlog
  4. Start DTC
  5. Start the Resync Service
  6. Wait a couple of minutes and see if the event log posts a successful XLN(Exchange of Log names)
  7. Test again and it should work ! 🙂

When a table is configure for CCSID 1208 Unicode on the Mainframe DB2 V9, an Insert statement fails with SQLCODE 80 when the data to be inserted are containing special characters like ‘Ä’.

This issue only happens when the value being inserted fills up the column and contains the special characters.

This is due to the fact that special unicode characters are mapped to more chars exceeding the buffer length.

No Fix is available at this time !

Hope this will be fixed in the next major HIS Release 2013.

We recently worked on a support case where a customer was using the Data Access Tool (DAT), which is included with Host Integration Server and the Microsoft OLE DB Provider for DB2 that is included in SQL Server Feature Packs, We often suggest that you use the DAT to create the connection string (UDL) that is used to connect to your IBM DB2 systems and then to run the Sample Query to the connection string to see if you are able to make a basic query without error.

In this case, the data returned by the Sample Query was incomplete.

The Sample Query issues a query against the SYSTABLES table in DB2. SYSTABLES is a system catalog tables that contains information about each table that is defined in the database. When you run the Sample Query in the DAT, it sends a query to DB2 to get a list of the tables that are defined in the Schema that is specified in the connection string.

To read the complete post, please visit Stephen Jackson’s Blog : http://blogs.msdn.com/b/sjackson/archive/2013/01/08/missing-data-when-querying-ibm-db2-tables-due-to-code-page-issues.aspx