On clients running Microsoft® Windows® NT, invokable TPs are configured through the Windows NT registry.
Note With Windows NT, the recommended method for setting registry variables for autostarted invokable TPs is to use the sample TP configuration program, TPSETUP. Compile INSTALL.C, the source code for TPSETUP, for the Windows NT environment. When you write an installation program for autostarted invokable TPs, it is recommended that you add code similar to TPSETUP to the installation program. For information about TPSETUP, see Sample APPC TPs in the SDK.
For clients running Windows NT, it is recommended that autostarted invokable TPs be written as Windows NT services. Be sure to include code like that in TPSETUP in the program that installs your TPs. Among other things, TPSETUP shows how to use the CreateService function when installing a TP. For important information about how services work under Windows NT, see the documentation for Windows NT and for Win32®.
The following table lists the registry entries used for the types of invokable TPs that can be run on Windows NT-based clients:
Type of TP | Location in registry | Possible registry entries |
---|---|---|
Autostarted invokable TP running as a service on a Windows NT-based client | HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services TPName (and subkeys) |
Registry entries created by the CreateService call, including entries that specify the path, display name, and other characteristics of the service. —plus—
Linkage
Parameters
|
Autostarted invokable TP running as an application1 on a Windows NT-based client | HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services SnaBase Parameters TPs TPName Parameters |
SNAServiceType:REG_DWORD:{ 0x5 | 0x6 } PathName:REG_EXPAND_SZ:path LocalLU:REG_SZ:LUalias Parameters:REG_SZ:ParameterList TimeOut:REG_DWORD:number ConversationSecurity:REG_SZ:{ YES | NO } AlreadyVerified:REG_SZ:{ YES | NO }2 Username1:REG_SZ:Password12 ... UsernameX:REG_SZ:PasswordX2
|
Operator-started invokable TP running as a service on a Windows NT-based client | HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services TPName (and subkeys) |
Registry entries created by the CreateService call, including entries that specify the path, display name, and other characteristics of the service. —plus—
Linkage
Parameters
|
Operator-started invokable TP on a Windows NT-based client | HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services SnaBase Parameters TPs TPName Parameters |
SNAServiceType:REG_DWORD:0x1A LocalLU:REG_SZ:LUalias TimeOut:REG_DWORD:number ConversationSecurity:REG_SZ:{ YES | NO } AlreadyVerified:REG_SZ:{ YES | NO }2 Username1:REG_SZ:Password12 ... UsernameX:REG_SZ:PasswordX2 |
Notes:
1 Before an autostarted TP can be started as an application on a Windows NT-based client, the TPSTART program must be started. For more information, see Sample APPC TPs in the SDK.
2..AlreadyVerified and Username/Password entries are used only if ConversationSecurity is set to YES.