Clients Running Windows
On clients running Microsoft Windows, invokable TPs are configured through the Windows registry.
Note
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 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.
It is recommended that autostarted invokable TPs be written as Windows 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, see the Microsoft Developer Network (MSDN®) Platform Software Development Kit.
The following table lists the registry entries used for the types of invokable TPs that can be run on Windows clients:
Type of TP | Location in registry | Possible registry entries |
---|---|---|
Autostarted invokable TP running as a service | 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 OtherDependencies:REG_MULTI_SZ:SnaBase Parameters SNAServiceType:REG_DWORD:0x5LocalLU:REG_SZ:LUaliasParameters:REG_SZ:ParameterListTimeout:REG_DWORD:numberConversationSecurity:REG_SZ:{ YES | NO }AlreadyVerified:REG_SZ:{ YES | NO }2Username1:REG_SZ:Password12 ...UsernameX:REG_SZ:PasswordX2 |
Autostarted invokable TP running as an application | HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services SnaBase Parameters TPs TPName Parameters |
SNAServiceType:REG_DWORD:{ 0x5 | 0x6 }PathName:REG_EXPAND_SZ:pathLocalLU:REG_SZ:LUaliasParameters:REG_SZ:ParameterListTimeOut:REG_DWORD:numberConversationSecurity:REG_SZ:{ YES | NO }AlreadyVerified:REG_SZ:{ YES | NO }2Username1:REG_SZ:Password12 ...UsernameX:REG_SZ:PasswordX2 |
Operator-started invokable TP running as a service | 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 OtherDependencies:REG_MULTI_SZ:SnaBase Parameters SNAServiceType:REG_DWORD:0x1ALocalLU:REG_SZ:LUaliasTimeout:REG_DWORD:numberConversationSecurity:REG_SZ:{ YES | NO }AlreadyVerified:REG_SZ:{ YES | NO }2Username1:REG_SZ:Password12 ...UsernameX:REG_SZ:PasswordX2 |
Operator-started invokable TP | HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services SnaBase Parameters TPs TPName Parameters |
SNAServiceType:REG_DWORD:0x1ALocalLU:REG_SZ:LUaliasTimeOut:REG_DWORD:numberConversationSecurity:REG_SZ:{ YES | NO }AlreadyVerified:REG_SZ:{ YES | NO }2Username1:REG_SZ:Password12 ...UsernameX:REG_SZ:PasswordX2 |
Note
Before an autostarted TP can be started as an application on a Windows client, the TPSTART program must be started.
Note
AlreadyVerified and Username/Password entries are used only if ConversationSecurity is set to YES.