Is it possible to deploy components within MTS (Microsoft Transaction Server) via install shield - If so how is this achieved?
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
MTS Component Deployment
Started by
richardp
, Mar 26 2002 14:32
1 reply to this topic
BobRouse
-
- Members
- 82 posts
Posted 01 April 2002 - 16:13
This may not be much help to you but...
I don't know of any intrinsic way to do this within InstallShield. However, it could be done if you are willing to do some extra programming:
1) Write an ActiveX DLL to perform the steps necessary to do the MTS package deployment. The DLL will either need to detect or be told (by the install) if installing on NT 4 or Win2K.
If deploying to NT4: http://msdn.microsof...rary....1o3.asp
If deploying to Win2K: http://msdn.microsof...rary....1o3.asp
2) Include the ActiveX DLL in the list of setup files (if a standard install), or as an installed file (for a Basic install).
3) Use the "RegSvr32" command to register the ActiveX DLL after it gets copied to the target machine.
4) Call the function(s) to deploy your package.
You could probably do this in InstallScript as well, and avoid the ActiveX DLL, but I find that other languages (VB and/or C++) are much easier to work with to do this kind of stuff, and are better at trapping and handling errors.
Sorry for the lack of detail as to the actual steps and functions to call, but if you need to do this, you'll need to dig through the MSDN documentation yourself.
I don't know of any intrinsic way to do this within InstallShield. However, it could be done if you are willing to do some extra programming:
1) Write an ActiveX DLL to perform the steps necessary to do the MTS package deployment. The DLL will either need to detect or be told (by the install) if installing on NT 4 or Win2K.
If deploying to NT4: http://msdn.microsof...rary....1o3.asp
If deploying to Win2K: http://msdn.microsof...rary....1o3.asp
2) Include the ActiveX DLL in the list of setup files (if a standard install), or as an installed file (for a Basic install).
3) Use the "RegSvr32" command to register the ActiveX DLL after it gets copied to the target machine.
4) Call the function(s) to deploy your package.
You could probably do this in InstallScript as well, and avoid the ActiveX DLL, but I find that other languages (VB and/or C++) are much easier to work with to do this kind of stuff, and are better at trapping and handling errors.
Sorry for the lack of detail as to the actual steps and functions to call, but if you need to do this, you'll need to dig through the MSDN documentation yourself.
Bob Rouse
Netuitive, Inc.
Netuitive, Inc.