Over the years, a lot of companies invested in IBM mainframe (zSeries) or midrange (iSeries) systems. The mainframe architecture is not compatible with nowadays standards and architectures. Rewriting applications is not always feasible and desired. These applications are often very large systems with high reliability and performance. If possible
people's skills must be reused. This leads to the need of integrating with existing host systems. Microsoft created Host Integration Server (HIS) to integrate with host systems.
This session will cover all important components of HIS and how Mainframe functionality is exposed to newer technologies:

Network integration
As mentioned earlier, IBM host systems (most of the time mainframe systems) use a proprietary network architecture. HIS network integration will allow other systems to connect to those networks and expose functionality higher up in the stack (MQ, Applications, Data).

Data integration
HIS data integration will allow Microsoft systems to access data stored in DB2 databases or in VSAM files. This is either done with by using .NET data providers (DB2 or VSAM) or by using BTS adapters (DB2 or VSAM).

Application integration
HIS application integration will allow Microsoft systems to interface with IBM host applications as CICS transactions (Transaction Integrator) or IMS. Application integration is without any doubt one of the most powerful features of HIS.

Messaging integration
By using HIS, Microsoft BizTalk server can communicate with MQSeries on any other platform. HIS provides a WebSphere MQSeries client-based adapter. This adapter does not require a MQSeries installation on a Windows Server box. The WebSphere MQSeries client-based adapter allows direct access to MQSeries on host systems.