 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
david johnson Guest
|
Posted: Sat Jan 28, 2006 6:39 pm Post subject: DCOM & NT services |
|
|
Just a quick question, didn't know the best newgroup for this though.
This probably shows my lack of understanding but hopefully someone will
explain this two me. I've been developing a client / server applicaiton
with DCOM where the server runs on one machine and has many clients
connecting to it form other machines. The server has a management interface
for controlling the connections.
When a run a client, it instanciates the server and the server is loaded up
on the "server" machine. What I want to know is, what happens if no one is
logged on to the windows machine i.e. it is just sitting at the login
screen. Will the server app still start? If so, what then happens when
someone logons on - will they see the server GUI on there desktop?
I'm not sure what sure what the results are... I need to server to run
regardless of if a user is logged on to the server PC and so this is
strating to sound a bit like a service with a seperate configuration GUI.
Is it possible to wrap DCOM into an NT service? Are there any issues with
this.
Any pointers would be greatly appreshiated. I've reasd all the DCOM
references I can find but no seem to answer this question...
|
|
| Back to top |
|
 |
Colin B Maharaj Guest
|
Posted: Sun Jan 29, 2006 1:29 am Post subject: Re: DCOM & NT services |
|
|
Hi David, I have done a couple of things with DCOM, except that the DCOM
application I have came in a VC++ bundle (jikes sorry) that I got from
Nortel, and I used VC++ to compile the code except the application is
not a Service. It is an interactve application.
I then used the srvany.exe utility to setup and run the application as a
service. This seems to work fine. What you should do however is to add a
dependancy called RpcSs (thanks to Remy on this ) to ensure RPC
services are running before you "service wrapped application" is executed.
The only issues is authentication in that you need to create an account
and add the 'RUN as service' privilege to the account and assign this
account to the srvany service, since DCOM is heavly dependant on MS
access control stuff.
Another snag (If you have not come across it) is that DCOM on XP SP2 is
kinda turned off and gives the appearance that it is broken in XP SP2.
Took me a while to get it working but I figured it out, and I can send
you this if you like.
Hope this helps....
david johnson wrote:
| Quote: | Just a quick question, didn't know the best newgroup for this though.
This probably shows my lack of understanding but hopefully someone will
explain this two me. I've been developing a client / server applicaiton
with DCOM where the server runs on one machine and has many clients
connecting to it form other machines. The server has a management interface
for controlling the connections.
When a run a client, it instanciates the server and the server is loaded up
on the "server" machine. What I want to know is, what happens if no one is
logged on to the windows machine i.e. it is just sitting at the login
screen. Will the server app still start? If so, what then happens when
someone logons on - will they see the server GUI on there desktop?
I'm not sure what sure what the results are... I need to server to run
regardless of if a user is logged on to the server PC and so this is
strating to sound a bit like a service with a seperate configuration GUI.
Is it possible to wrap DCOM into an NT service? Are there any issues with
this.
Any pointers would be greatly appreshiated. I've reasd all the DCOM
references I can find but no seem to answer this question...
|
|
|
| Back to top |
|
 |
Remy Lebeau (TeamB) Guest
|
Posted: Mon Jan 30, 2006 7:23 am Post subject: Re: DCOM & NT services |
|
|
"david johnson" <davidjohnson (AT) gmail (DOT) com> wrote
| Quote: | When a run a client, it instanciates the server and the server is loaded
up on the "server" machine. What I want to know is, what happens if
no one is logged on to the windows machine i.e. it is just sitting at the
login screen.
|
That depends - is the DCOM server implemented in a standalone application,
or as an actual service?
| Quote: | Will the server app still start? If so, what then happens when someone
logons on - will they see the server GUI on there desktop?
|
If you implement the server as a true service, then everything will work
fine as expected - the server can be started even if no user is logged in,
and the service will continue to run when a user does eventually log in.
| Quote: | I'm not sure what sure what the results are...
|
Did you actually try it as see what really happens?
| Quote: | I need to server to run regardless of if a user is logged on to the server
PC |
Then you must implement the server as a service.
| Quote: | Is it possible to wrap DCOM into an NT service?
|
Yes. Microsoft even provides extra support in the OS for that specific
condition, in the form of additional Registry values that you need to set up
during the service's installation. Read the following article for more
details:
Creating and Registering COM Components with LocalService
http://msdn.microsoft.com/library/en-us/dncomg/html/localserv.asp
Gambit
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|