The registry locations that are created when you use Tpsetup.exe to install invokable transaction programs in Host Integration Server 2004 (904553)

INTRODUCTION

This article discusses the registry locations that are created when you use Tpsetup.exe to install invokable transaction programs. A transaction program (TP) that can be called upon to start a conversation by another TP is known as an invokable TP. Invokable TPs are generally server-type applications. A TP that is automatically started when the TP is invoked is known as an autostarted invokable TP.

Tpsetup.exe is a utility that is included in Microsoft Host Integration Server 2004. You can use Tpsetup.exe to install autostarted invokable TPs. Autostarted invokable TPs can be either queued or nonqueued. Queued TPs and nonqueued TPs function differently:

When a queued TP is invoked multiple times, the TP loads one time. Then, the TP queues requests to be dealt with one at a time.
When a nonqueued TP is invoked multiple times, the TP loads multiple times. The TP loads one time for every time that the TP is invoked.

MORE INFORMATION

We recommend that you use Tpsetup.exe to install autostarted invokable TPs. The registry locations that Tpsetup.exe creates for the Host Integration Server 2004 client depend on the Host Integration Server 2004 client deployment type. The deployment types include the following options:

Just me (run as application)
Everyone (run as application)
Windows service

Tpsetup.exe creates the following registry locations for these deployment types.

Just me (run as application)

When the TP runs as a service, Tpsetup.exe creates the following registry subkeys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\<TPNAME>\Parameters
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<TPNAME>
When the TP runs as an application, Tpsetup.exe creates the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SnaBase\Parameters\TPs\<TPNAME>\Parameters

Everyone (run as application)

When the TP runs as a service, Tpsetup.exe creates the following registry subkeys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\<TPNAME>\Parameters
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<TPNAME>
When the TP runs as an application, Tpsetup.exe creates the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SnaBase\Parameters\TPs\<TPNAME>\Parameters

Windows service

When the TP runs as a service, Tpsetup.exe creates the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<TPNAME>\Parameters
When the TP runs as an application, Tpsetup.exe creates the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SnaBase\Parameters\TPs\<TPNAME>\Parameters

REFERENCES

For more information, see the Host Integration Server 2004 documentation.

For more information about TPs and related topics, click the following article numbers to view the articles in the Microsoft Knowledge Base:

182576 NT client does not support dynamic definition of invokable TPs

158515 Auto started TP is not invoked if TP has mixed-case TP name

118382 Making and running AREXEC/AREXECD samples

118381 Making and running APING/APINGD samples

316787 Invokable transaction program registry locations that Tpsetup.exe creates