
Signature
Ohad Young
Medical Informatics Research Center
Ben Gurion University
Information System Eng
Office Phone: 972-8-6477160
Cellular Phone: 972-54-518301
E-Mail: ohadyn@bgumail.bgu.ac.il
> The application consists of Webservices, for exposing my application
> API, deployed on a web-server (WIN2K with IIS 5.0). The COM+ (and its
> deployed components)
> will be installed on some other server (but in the same LAN),
> application-server (WIN2K with COM+ 1.0).
If there is no security reason i would deploy the com+ stuff on the
webserver in a com+ lib app. Performs much better.
> How do I activate the COM+ components from other machines?
> (using the COM+ export utility, remoting and etc.).
If it is on the same host, no further work needed. If remote: export an app
proxy and install it on the webserver.
> Can I upgrade from COM+ 1.0 to 1.5?
upgrade to w2k3, no other supported way.
Claudiu Tomescu - 18 Sep 2003 09:49 GMT
hi Steffen,
I have a question about remote instantion of COM+ components (actually .NET
Serviced Components developed in C#) :
I installed the COM+ components on the server (as server application). I
performed the export and obtained the proxy which should go on the clients;
I installed it on the client computer. So for so good.
Now my question is: how do I develop a client application? or more
preciselly where? If I try to develop the client app on the client machine I
need a reference to the TLB or DLL in order to use the components, right?
Well, when I am trying to do make a reference to the COM component installed
on the client I receive an error message from the server, which I believe is
okay cause it's not the actual DLL there but merely a proxy for the object.
In this case what are my options? Develop the client on the server machine
too?
Regards,
Claudiu
> > The application consists of Webservices, for exposing my application
> > API, deployed on a web-server (WIN2K with IIS 5.0). The COM+ (and its
[quoted text clipped - 14 lines]
>
> upgrade to w2k3, no other supported way.