The Host Integration Server Product Team finally released the great new Release 2013.
Microsoft Host Integration Server 2013 enables enterprise organizations to integrate existing IBM host systems, programs, messages, and data with Microsoft class leading suite of server applications.
HIS 2013 is the ninth release and includes these improvements.
- Deploy on new platforms
- Windows 8.1, Windows 8, Windows Server 2012 R2, Windows Server 2012,
- Visual Studio 2012, SQL Server 2012, .NET 4
- IBM z/OS V1.13, i5/OS V7R1, MQ V7.5, CICS V5.1, IMS V12.1, Informix IDS V12.1, DB2 V10
- Use latest protocols and formats
- DB2 client connectivity to SQL Server (DRDA Service)
- Windows client connectivity to Informix server (OLE DB Provider)
- Increase enterprise dev and IT pro productivity
- Transaction Integrator Configuration Tool and Visual Studio code snippets
- DRDA Service and TI PowerShell modules, XML schemas for app.config and web.config files
- Managed encoder and trace
- TN3270 emulator and Host File Transfer Utility
- Improve performance and scalability
- Transaction Integrator, MQ channel and host files managed runtimes
- DB2 client transaction load balancing, bulk copy and bulk insert
Here are links to the technology and documentation.
Release notes with list of new features and installation guide with list of supported IBM products are available on the Microsoft Download Center.
The HIS 2013 BPA and SCOM MP will be available in September.
The HIS 2013 Enterprise edition will be available for purchase on 1st September, licensed as supplemental technology to BizTalk Server 2013. See the BizTalk website for more information on BTS 2013 licensing.
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.
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.
- Install the Microsoft BizTalk Server
- 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
- Install the latest Microsoft BizTalk Server Cumulative Updates
- Install the IBM WebSphere MQ Client or the IBM WebSphare MQ Transactional Client
- Install the latest IBM WebSphere MQ FixPacks
- 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
- Install the latest Microsoft Host Integration Server Cumulative Updates
- 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 : http://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
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
A domain user attempts to browse to a website hosted on Internet Information Services (IIS). The website is configured to use Kerberos authentication. Instead of receiving the expected web page, the user is presented with an error message similar to the following:
HTTP 400 – Bad Request (Request header too long)
This issue may occur when the user is a member of too many Active Directory user groups. When a user is a member of a large number of active directory groups the Kerberos authentication token for the user increases in size. The HTTP request that the user sends to the IIS server contains the Kerberos token in the WWW-Authenticate header, and the header size increases as the number of groups goes up. If the HTTP header or packet size increases past the limits configured in IIS, IIS may reject the request and send this error as the response.
- Decrease the number of Active Directory groups that the user is a member of.
- Modify the MaxFieldLength and MaxRequestBytes registry keys . They are located at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters.
MaxFieldLength DWORD 65534
MaxRequestBytes DWORD 16777216
For more information, please check the Microsoft KB : http://support.microsoft.com/kb/2020943
To Download the Product Layout for Offline Installation:
This will enable you to download a complete local copy to your computer. You can run Setup later without contacting the Internet, or you can copy and paste the installation layout in another location.
Once downloaded, you can run VS2012.2.exe from the download location to install the update.
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
- Stop the SNA LU 6.2 Resync Service
- Stop DTC
- Clear DTC log è MSDTC -resetlog
- Start DTC
- Start the Resync Service
- Wait a couple of minutes and see if the event log posts a successful XLN(Exchange of Log names)
- Test again and it should work !
BizTalk Server 2013 will be available for download on MSDN starting on 21th March 2013. The English locale SKUs will be available for purchase starting April 2013. Other language SKUs will be available for purchase starting May 2013. Host Integration Server 2013 will ship at a later date, however, BizTalk Server 2013 is fully compatible with Host Integration Server 2010.
This is the eighth release of BizTalk Server, another step in the on-going investments we are making in BizTalk.
Improvements in the following areas:
- Improved Performance
- Simplified Development and Management Experience
- Cloud Connectivity
- Running BizTalk Server in the cloud (IaaS)
- Support for the latest platform and standards
Check back here for a series of blog posts going into detail on all the new features and improvements.
With this release, they are moving to a per-core licensing model. This keeps BizTalk consistent with the SQL Server licensing, and reflects the evolution of hardware capacity and the trend towards virtualization and cloud computing. With these changes, Microsoft will continue to be the Enterprise Integration server with the best TCO in the industry. Learn more about the licensing changes in this document.
Understand the BizTalk Server 2013 Licensing Model
BizTalk Server 2013 runs your on-premises integration solutions better and faster than ever before, and makes it easier to build hybrid solutions that span on-premises and the cloud.
Many thanks go to the Product Team ! You’ve done a great Job
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.