Integrated Link Service Setup Procedure

For each link service selected by the operator, SNA Server Setup performs these operations. If you provide a custom IHV link service setup, it must do likewise.

1. Copy the link service, device driver, and any detection DLL to the target server's \<snaRoot>\SYSTEM directory. These files do not need to be copied to \<snaRoot>\SYSTEM\HWSETUP, as was done in SNA Server 2.x.
2. Copy the SNA Explorer configuration DLL (if any) to \<snaRoot>\SYSTEM\HWSETUP\<cpu>. Since the configuration DLL may be run from a management workstation of any CPU type, you should provide multiple flavors of the configuration DLL, even if your link service itself only supports a single CPU type.
3. Add a registry entry to register your link service so that SNA Explorer can list your link service in the Insert New Link Service dialog box. This registry entry should be added to the following subkey:

   SYSTEM\CurrentControlSet\Services\SnaBase\LinkServicesInstalled

   This is a new subkey for SNA Server 3.0 and later that contains one value for each link service chosen to be copied to the target server's hard disk during SNA setup. The value name and value data are as follows:

   <value>: REG_SZ: <configDllName>

   where:

   <value> is the friendly name of your link service, for example, "IBM SDLC Link Service".

   <configDllName> is the file name and extension of the configuration DLL, for example, IBMSDCFG.DLL.

Note This registry entry is defined in the registry on the target server, not on the management workstation on which SNA Explorer happens to be invoked.

Setup for SNA Server 3.0 and later asks for a list of link services to install, and copies only those link services to the target server. This speeds up setup and reduces the disk space required for SNA Server. Setup does not define a Windows NT service or other registry entries as was done in SNA Server 2.x; it merely copies files.

There is an alternate way of calling the Link Service Configuration DLL if the link services from the vendor were not included with the released SNA Server CD-ROM. Depending on the setup tool used by the vendor, the vendor's setup software may not be able to read the registry and locate the directory where link services are installed. To resolve this problem, the SNA Manager scans the LinkServicesInstalled key prior to making the call to the Link Service Configuration DLL. The SNA Manager checks for a % character in the configDllName and if it exists \\ServerName will be prepended and the %s will contain the processor architecture (i386 or Alpha). The following example illustrates this:

Under the SYSTEM\CurrentControlSet\Services\SnaBase\LinkServicesInstalled key,

"Our Link Service Friendly Name" with a REG_SZ for the configDllName as follows:

"share\%s\<RelativePath and DLL Name>"