![]() You can run HIS Setup from the HIS CD or from the downloaded file set if you’re using the evaluation version. Check the HIS documentation to identify any other components you’ll need to install on your servers before you install HIS. There are a handful of other software requirements, depending on the components you plan to use. HIS also requires the MSMQ component, MMC 1.2 or later, MTS 2.0 or later, and Internet Explorer 5.5 or later. For example, remote administration requires the Remote Access Service, which is a component of Windows NT Server, Windows 2000 Server, and Windows. HIS also has other software requirements. If you’ve installed SQL Server 2000 Desktop Engine on the server, you already have MDAC 2.6 and won’t have to install MDAC again, unless you want to install a newer version. It’s a good idea to install the latest version, which you can obtain from Microsoft’s Web site. The Data Integration features of HIS require Microsoft Data Access Components (MDAC) 2.5 or later. Member servers service requests from clients, but they don’t maintain configuration data.Īnother step to take prior to installing HIS is to install the additional software HIS will need to do its job. The primary server will hold the subdomain configuration data, and the backup servers will hold read-only copies of the configuration data. Identify the server that will act as the primary and those that will act as backups. Others in the subdomain can function as backup servers or member servers. Each subdomain comprises up to 15 HIS servers, with one server in each subdomain functioning as the primary server. You can then install the desired Windows Server platform on each server and set the servers up in their respective domains.Īs you set up your servers, keep in mind that each HIS server resides in a particular HIS subdomain and fulfills a specific role. You’ll need to decide where the server will reside in the domain(s) and the type of deployment (centralized, distributed, or mixed) you’ll use for HIS. You can then obtain, install, and test the hardware as needed, and start prepping the servers for installation. Gather all of the information possible about your host servers and clients. The first step in deploying HIS is to lay the groundwork for the actual installation. To find out more, see the Daily Drill Downs “Host Integration Server can bridge the gap between Windows servers and large systems” and “Don’t forget infrastructure when planning to deploy Host Integration Server.” I can’t cover all of the possible issues you’ll face in this Daily Drill Down, so you should use it as a roadmap to follow when planning your own deployment. Because HIS is so complex and handles so many different mainframe/mini combinations, it takes a lot of planning and preparation to deploy. By enabling this type of integration, HIS eliminates the need for businesses to migrate away from their host servers to other platforms and applications, which can mean a huge savings in capital and development costs. HIS also provides the tools you need to integrate that data into Web applications and LAN- or WAN-based client/server applications. Microsoft Host Integration Server (HIS) enables organizations to serve data from a variety of host server platforms to clients running Windows and other platforms. Host Integration Server ties your platforms together In this Daily Drill Down, I’ll describe how to install and configure HIS. However, installing and deploying HIS can be a complex task, particularly if you need to install multiple servers for clustering, load balancing, or simply to provide access to several host servers. Microsoft Host Integration Server (HIS) is a powerful tool you can use to get your mainframe and/or midrange computers working in harmony with your Windows network. Jim Boyce explains this complex procedure in this Daily Drill Down. Microsoft's Host Integration Server can get your mainframe and your Windows 2000 server to work together, but only if it's properly installed and configured. Install and configure Host Integration Server to access mainframe resources from your Win2K server
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |