لطفا منتظر باشید ...
SNA Server Client and Components
Windows 2000 Professional uses SNA Server Client to establish connectivity to an IBM host when an SNA Server is implemented as the gateway. Included with SNA Server Client are two host emulation applications, 3270 Applet and 5250 Applet. The 3270 Applet is used for communicating with an IBM mainframe. The 5250 Applet is used for communicating with an AS/400. The SNA Server components communicate through SNA Server Client, which communicates with SNA Server. SNA Server communicates with the IBM host, as illustrated in Figure 26.6.
Figure 26.6 SNA Server Client Communication Path
NOTE
All host emulation applications that have access to an IBM host through SNA Server communicate through SNA Server Client.
Installing SNA Server Client and Components
SNA Server Client is installed on Windows 2000 Professional. During the installation of SNA Server Client, you can choose which of the included components you want to install. For basic connectivity to an IBM mainframe and an AS/400, select the 3270 Applet and the 5250 Applet, respectively. SNA Server Client is located on the SNA Server installation CD in the path ClientsWinntI386Setup.exe. Table 26.5 lists all of the components you can select during the installation of SNA Server Client.Table 26.5 SNA Server Client Components
| Components | Description |
|---|---|
| SNA Server Manager | SNA Server Manager allows you to manage SNA Server from Windows 2000 Professional. Users who have network administration privileges can use this tool to configure an SNA Server computer, LUs, LU pools, users, Host Print Service, Shared Folders Gateway Service, APPC modes, CPI-C symbolic names, and host security domains. |
| 3270 Applet | The program 3270 Applet allows you access to an IBM host on an SNA network. |
| 5250 Applet | The program 5250 Applet allows you access to AS/400 systems. |
| COM Transaction Integrator for CICS and IMS (COMTI) | COMTI provides computers running SNA Server Client with access to the IBM Customer Information Control System (CICS) and Information Management System (IMS) programs that are running on MVS mainframes. |
| OLE DB Provider for AS/400 and VSAM | Microsoft OLE DB Provider for AS/400 and VSAM allows record-level access to mainframe and AS/400 files. |
| OLE DB Provider/ODBC Driver for DB2 | Microsoft OLE DB is the component database architecture that provides universal data integration over an enterprise network—from mainframe to desktop—regardless of the data type. |
| APPC File Transfer Protocol (AFTP) Client | AFTP Client allows your computer to connect to AFTP Service to share files among different platforms. |
| Host Account Manager | Host Account Manager connects users to all servers and domains to which they have access with a single password. |
| SNA Server Remote Access Service | SNA Server Remote Access Service enables a system administrator to create a virtual LAN connection between Windows NT systems across an existing SNA network without having redundant LAN-to-LAN networks or having to install dial-up modems at each site. |
| Host Connectivity SDK | Access to the Software Development Kit (SDK) makes it possible for software developers to create specialized SNA Server applications. |
| SNA NetView Alerter | This tool allows the NetView reporting system to send alerts and other messages between the host and the computers that connect to it. |
NOTESNA Server Client is always installed, no matter what other component you choose to use from the list. During the installation and setup of SNA Server Client, you must select one of the following networking protocols for client-to-server communications. The protocol you select is used for communication between SNA Server Client and SNA Server. The available protocols are the following:
For detailed information about SNA Server Client components, refer to SNA Server Help.
Microsoft Networking (Named Pipes)Novell NetWare (IPX/SPX)TCP/IPBanyan VINES
You also must select one of the following methods for the client to use in locating computers that are running SNA Server:
Client locates servers in an SNA Server subdomain.Client locates servers by name.
To select Client locates servers in an SNA Server subdomain, you must know the name of the subdomain in which SNA Server resides. Every server that runs SNA Server is a member of a Windows NT domain. Within the Windows NT domain is an SNA Server subdomain. SNA Server subdomains form a logical grouping of computers that run SNA Server and through which SNA Server clients can connect.To select Client locates server by name, you must know the name of a specific server on which SNA Server resides in the SNA Server subdomain.For more information about installing and configuring client software, see Microsoft® SNA Server Getting Started and SNA Server Help.
