Configure Clients to Support TPs (CPI-C)
Overview
On client computers, invokable transaction programs (TPs) are configured through the Windows registry.
Note
On client computers, 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 target 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 clients 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.
The following table lists the registry entries used for the types of invokable TPs that can be run on Windows client computers.
| Type of TP | Location in registry | Possible registry entries |
|---|---|---|
| Autostarted invokable TP running as a service on a 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 OtherDependencies:REG_MULTI_SZ:SnaBase Parameters SNAServiceType:REG_DWORD:0x5 LocalLU:REG_SZ:LUalias Parameters:REG_SZ:ParameterList Timeout:REG_DWORD:number AcceptNames:REG_SZ:TPNameList ConversationSecurity:REG_SZ:{ YES | NO } AlreadyVerified:REG_SZ:{ YES | NO }Username1:REG_SZ:Password1 ...UsernameX:REG_SZ:PasswordX For more information, see the notes following this table. |
| Autostarted invokable TP running as an application on a client. For more information, see the notes following this table. | 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:numberAcceptNames:REG_SZ:TPNameListConversationSecurity:REG_SZ:{ YES | NO }AlreadyVerified:REG_SZ:{ YES | NO }Username1:REG_SZ:Password1 ...UsernameX:REG_SZ:PasswordX For more information, see the notes following this table. |
| Operator-started invokable TP running as a service on a 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 OtherDependencies:REG_MULTI_SZ:SnaBase Parameters SNAServiceType:REG_DWORD:0x1A LocalLU:REG_SZ:LUalias Timeout:REG_DWORD:number ConversationSecurity:REG_SZ:{ YES | NO } AlreadyVerified:REG_SZ:{ YES | NO }Username1:REG_SZ:Password1 ...UsernameX:REG_SZ:PasswordX For more information, see the note following this table. |
| Operator-started invokable TP running as an application on a client. | 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 }Username1:REG_SZ:Password1 ...UsernameX:REG_SZ:PasswordX For more information, see the note following this table. |
Note
Before an autostarted TP can be started as an application on a client, the TPSTART program must be started.
Note
AlreadyVerified and Username/Password entries are used only if ConversationSecurity is set to YES.