Latest Entries »

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

Microsoft announced at Tech Ed North America that BizTalk 2013 hit RTM and that it will be available soon !

Feature Description
Platform support BizTalk Server supports the following platform stack:

  • Windows Server 2012 R2, Windows Server 2012, Windows 8.1, Windows 7 SP1.
  • Microsoft Office Excel 2013 or 2010.
  • .NET Framework 4.5 and .NET Framework 4.5.1
  • Visual Studio 2013
  • SQL Server 2014 or SQL Server 2012 SP1
  • SharePoint 2013 SP1
Updates to the SB-Messaging adapter SB Messaging adapter is enhanced to support SAS (Shared Access signature) based authentication, in addition to ACS.  With this new improvement, BizTalk Server can now also interact with the on-prem edition of Service Bus. For more information, see SB-Messaging Adapter.
Updates to the WCF-WebHttp adapter WCF-WebHttp adapter now supports sending and receiving JSON messages. BizTalk Server includes a wizard to generate XSD schema from a JSON instance. BizTalk Server also provides two new pipelines for processing JSON messages. An Encoder and Decoder component is also available for use in custom pipelines. For more information, see WCF-WebHttp Adapter.
Updates to the SFTP adapter SFTP adapter now supports two-factor authentication and provides an option to specify a temporary folder while uploading/downloading large files. You can also select the Encryption cipher value specific to your target server. For more information, see SFTP Adapter.
Updates to HL7 Accelerator HL7 Accelerator now supports the following:

  • Provides capability to include free-text data as part of the message that can be processed by the HL7 pipelines.
  • 64-bit support for hosting Hl7 adapter.

You don’t need to wait until Host Integration Server vNext in order to use BizTalk 2013 R2, because Host Integration Server (HIS) 2013 works and is supported to work with BizTalk Server 2013 R2 !

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

Traditionally, the WebSphere MQ Extended Transactional Client (also known as the XA Client or XTC Client) was not part of the standard WebSphere MQ client and you had to purchase the XA Client separately. As per the WebSphere MQ V7.5 announcement letter on April 24, 2012, the Extended Transactional Client (XA) is now a free product which comes with the standard WebSphere MQ v7.x client.

With the availability of WebSphere MQ V7.5 the capability previously delivered within the Extended Transactional Client is incorporated into the standard WebSphere MQ client. Customers using WebSphere MQ V7.0.1 and WebSphere MQ V7.1 gain the benefit of use of the Extended Transactional Client without charge from the date of this announcement. IBM is making available refreshed code including updated License Information. Customers can realize this benefit through the download and acceptance of this new License Information.

The WMQ V7.5 client has contained the XA client functionality from inception. The WMQ V7.0.1 and V7.1 client downloads have been updated to contain a license to use the XA client functionality.

For the WMQ V7.1 and V7.0.1, Client, APAR IV43443 has been created to include the XA enablement component as part of the client installation. After APAR IV43443 is completed and closed the WMQ V7.1 and V7.0.1 clients will include the XA component as well as the license to use it.

For WMQ V7.1 or V7.0.1 prior to APAR IV43443, the XA enablement component must be installed as a part of a server installation. You must install the client portion plus the XA enablement component from a server installation. The change is that the updated client code will have the license to use the XA enablement component. Please note that we do not support copying files around. You must install the XA enablement component as part of the server install for WMQ V7.1 or V7.0.1 prior to APAR IV43443.

The WebSphere MQ client code is available at no extra cost.

  • The WebSphere MQ V7.5 XA enabled client code is available as a part of the server install code or may be installed separately as a WebSphere MQ Client SupportPac.
  • The WMQ V7.1 and V7.0.1 client code prior to APAR IV43443 must install the XA enablement component as a part of the server install code.
  • The WMQ V7.1 and V7.0.1 client code AFTER APAR IV43443 will contain the XA enablement code as part of the V7.1 and V7.0.1 SupportPac downloads.
  • APAR IV43443 is included in Fix Packs V7.0.1.12 (or later) and V7.1.0.5 (or later).

Download

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

During migration from a previous version of Host Integration Server to 2013 you may encounter some issues because some behaviors have changed.

In case of the Mirror Transaction Id, in previous versions of HIS, you have to specify in the Transaction Integrator a Mirror Transaction Id. There are two defaults MSCS and CSMI. If you have also specified a Mirror Transaction Id in your TI Assembly that you want to use to identity the CICS Transaction on the Mainframe, HIS 2006, 2009, 2010 have always used the value of the TI Assembly.

Now with HIS 2013, there’s no Transaction Integrator and you should use the new Transaction Integration Tool in order to configure the TI Environment. There are 3 scenarios :

  1. mirrorTransactionId=”XXXX” : the result will be “XXXX” on the Host side
  2. you are not using the mirrorTransactionId item : the result will be “CSMI” on the Host side
  3. mirrorTransactionId=”” : the result will be the value of the Mirror Transaction Id from the TI Assembly

I wish you all a Merry Christmas and Best Wishes for 2014

Write me your wishes for HIS vNext and I will address them to Santa Claus :-)

Follow

Get every new post delivered to your Inbox.