Mainframe Integration (Host Integration Server - HIS)
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.
HIS was first developed as an SNA (Systems Network Architecture) gateway. Through this gateway, host systems
on an SNA network are made available to Microsoft systems. The product evolved by adding functionality: data access, application access, security integration,...
Today Microsoft Host Integration Server allows these types of integration:
HIS network integration will allow other systems to connect to those networks and expose functionality higher up in the stack (MQ, Applications, Data).
This is either done with by using .NET data providers (DB2 or VSAM) or by using BTS adapters (DB2 or VSAM)
By exposing host resources as a service using Host Integration Server, these resources can be made available to
any system anywhere... In this way, host system can become a key part of a company's SOA architecture.
More info about Microsoft Host Integration Server can be found on the HIS homepage.
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.
HIS was first developed as an SNA (Systems Network Architecture) gateway. Through this gateway, host systems
on an SNA network are made available to Microsoft systems. The product evolved by adding functionality: data access, application access, security integration,...
Today Microsoft Host Integration Server allows these types of integration:
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).
Identity management
Using SSO, HIS can provide end-users with a single sign on experience for host systems.Data integration
HIS data integration will allow Microsoft systems to access data stored in DB2 database 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). Even �screen scraping� is possible with HIS by using the Session Integrator.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 an MQSeries installation on a Windows Server box. The WebSphere MQSeries client-based adapter allows direct access to MQSeries on host systems.By exposing host resources as a service using Host Integration Server, these resources can be made available to
any system anywhere... In this way, host system can become a key part of a company's SOA architecture.
More info about Microsoft Host Integration Server can be found on the HIS homepage.