Printable View
if you follow the link you'll learn to setup a n-tier application.......
http://support.microsoft.com/support...n_SRCH&SPR=TRS
the interesting thing is:
"This article assumes that you are running MTS 2.0 and SQL Server 6.5 on the same computer on which you develop the application. "
What if mts is runnning on a remote machine ?, how do i proceed, from the client to reference the mts object from the client ?
any help appreciated....
thank you
Dont think you are supposed to. Its for objects on ther server.
Are you trying to run the object on a different machine than the transaction server or run the asp pages on a different machine than mts?
if i'm not supposed to reference the object, how will intanciate it from the client ?
I'm trying to run a atandard exe that will use for its database accesses a com that resides in mts on a remote server
????????????????????????
You would have to run mts on the same machine as you are trying to create the object. MtS can be mapped to the object on another server and then the object can be used as if it is on that machine. Atleast it works that way in asp so I asume it would for an app also
so you mean: " if you want to run a mts-registered-component, you need to have mts running on the machine where the client that calls the component executes itself" ?
If i want 10 clients on my network to run that component i need to install mts on all the clients and so for the component ?
Finally if i want the com to reside on one server, the only way to do so is with asp-iis-mts ?
Pretty much from what i have seen so far. I could be wrong and if anybody knows that i would love to learn more about it myself. There are ways to get around it, maybe use winsock but from my experience with it, that seems to be the case.
thank you all : things are getting clearer !
bye
Hey guys, I'd like to clear some stuff up, I've worked with MTS quite a bit
You don't need MTS on each machine that needs to call the COM component. If this were the case, you'd have to distribute the COM component to each client, which totally defeats the purpose of MTS
Install your COM component on your server. You then EXPORT the package from to create an executable CAB file. Run this executable on your clients' machines -- this adds the appropriate registry entries for COM and enables the remote activation.
All you have to do then is instantiate the COM component on the client just like you would with any other component and VIOLA, It works :)
Hope this helps
Thats why i love this place, always learn something new:) Thanks for the info clunietp.
You got it :)
Heeeeeeeeeeeeeyyyyyy!
I'm a little late but i wanted to thank you clunietp for the information complement........
I'll try this ......
JUst a question: from where do i create the pseudo-package that will be distributed on the client machines ?