Discussion:
installing client side proxies
Greg Robinson
2002-10-16 13:06:44 UTC
Permalink
I have always had control over my clients (usually just another server)
when using DCOM. On my current project, I do not. We developed a DCOM
Object that will run on a server that hundreds of clients will remote to.
I exported a client side proxy that we run locally for testing. I would
rather not have to ask hundreds of clients to run the setup file on their
workstations. I would like this to be invisible to them.

Is there a way I can 'hide' this or 'install this for them' without their
knowledge? Our exe also runs on their workstations and we do monthly updates.
I was thinking of adding some script that shells out to the set up program
and runs it for them.






Greg Robinson
Director of Training and .NET Technologies
Scribble Software and Training
www.scribblesoftware.com
www.scribbletraining.com

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Hitesh Shah
2002-10-16 14:40:12 UTC
Permalink
Is any one can tell me how many tier the following application (Diagram)
has ? and how

Thank you in advance
Rgds
Hitesh
_________________
| |
| |
| Database Server | (SQl SERVER 2000 +MTS)
| + |
| MTS Server(DLL) |
|_________________|
^
||
||
||
________||_________
| |
| |
| EXE(Application) | (Exe is lying on this server from where client is
accessing)
| |
| |
|_________________|
^
||
||
||
________||_________
| |
| |
| Client PC | (User)(it doesnt have direct access to
database server)
| |
| |
|________________ |

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Greg Robinson
2002-10-16 15:03:15 UTC
Permalink
Your client calls an exe, then calls a MTS DLL which calls your database?


I would say this is a classic 3 tier, unless you want to consider the client
2 tiers, than I would say 4.
-- Original Message --
Date: Wed, 16 Oct 2002 20:10:12 +0530
Subject: Re: [VBCOM] Tier?
Is any one can tell me how many tier the following application (Diagram)
has ? and how
Thank you in advance
Rgds
Hitesh
_________________
| |
| |
| Database Server | (SQl SERVER 2000 +MTS)
| + |
| MTS Server(DLL) |
|_________________|
^
||
||
||
________||_________
| |
| |
| EXE(Application) | (Exe is lying on this server from where client is
accessing)
| |
| |
|_________________|
^
||
||
||
________||_________
| |
| |
| Client PC | (User)(it doesnt have direct access to
database server)
| |
| |
|________________ |
You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Greg Robinson
Director of Training and .NET Technologies
Scribble Software and Training
www.scribblesoftware.com
www.scribbletraining.com

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Andrew Gayter
2002-10-17 08:01:45 UTC
Permalink
Physical separation of components does not dictate the number of tiers.
DNA is broken down into 3 logical tiers - presentation, business and
data access. N-tier is when we describe DNA models that contain proxy
layers to cater for cross process communication complexities.
To know how many tiers you have look at what your code does, rather than
where it is placed.

I'm not sure what the (EXE) application does, but it's sure going to be
a bottleneck in your system!

A

-----Original Message-----
From: Technical discussion of VBCOM [mailto:***@DISCUSS.DEVELOP.COM]
On Behalf Of Hitesh Shah
Sent: 16 October 2002 15:40
To: ***@DISCUSS.DEVELOP.COM
Subject: Re: [VBCOM] Tier?

Is any one can tell me how many tier the following application
(Diagram)
has ? and how

Thank you in advance
Rgds
Hitesh
_________________
| |
| |
| Database Server | (SQl SERVER 2000 +MTS)
| + |
| MTS Server(DLL) |
|_________________|
^
||
||
||
________||_________
| |
| |
| EXE(Application) | (Exe is lying on this server from where
client is
accessing)
| |
| |
|_________________|
^
||
||
||
________||_________
| |
| |
| Client PC | (User)(it doesnt have direct access to
database server)
| |
| |
|________________ |

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Andrew Gayter
2002-10-17 08:02:16 UTC
Permalink
Windows Installer and Active Directory/SMS will do what you want.

-----Original Message-----
From: Technical discussion of VBCOM [mailto:***@DISCUSS.DEVELOP.COM]
On Behalf Of Greg Robinson
Sent: 16 October 2002 14:07
To: ***@DISCUSS.DEVELOP.COM
Subject: [VBCOM] installing client side proxies

I have always had control over my clients (usually just another server)
when using DCOM. On my current project, I do not. We developed a DCOM
Object that will run on a server that hundreds of clients will remote
to.
I exported a client side proxy that we run locally for testing. I
would
rather not have to ask hundreds of clients to run the setup file on
their
workstations. I would like this to be invisible to them.

Is there a way I can 'hide' this or 'install this for them' without
their
knowledge? Our exe also runs on their workstations and we do monthly
updates.
I was thinking of adding some script that shells out to the set up
program
and runs it for them.






Greg Robinson
Director of Training and .NET Technologies
Scribble Software and Training
www.scribblesoftware.com
www.scribbletraining.com

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Greg Robinson
2002-10-17 11:04:43 UTC
Permalink
I am using Windows Installer. I create a MSI file and then run the SetUp.


Maybe I do not fully understand what else it can do for me though as I do
not have much expierence in the Installer world. I do not want to have
to deploy a setup file that all my clients need to run.
-- Original Message --
Date: Thu, 17 Oct 2002 09:02:16 +0100
Subject: Re: [VBCOM] installing client side proxies
Windows Installer and Active Directory/SMS will do what you want.
-----Original Message-----
On Behalf Of Greg Robinson
Sent: 16 October 2002 14:07
Subject: [VBCOM] installing client side proxies
I have always had control over my clients (usually just another server)
when using DCOM. On my current project, I do not. We developed a DCOM
Object that will run on a server that hundreds of clients will remote
to.
I exported a client side proxy that we run locally for testing. I
would
rather not have to ask hundreds of clients to run the setup file on
their
workstations. I would like this to be invisible to them.
Is there a way I can 'hide' this or 'install this for them' without
their
knowledge? Our exe also runs on their workstations and we do monthly
updates.
I was thinking of adding some script that shells out to the set up
program
and runs it for them.
Greg Robinson
Director of Training and .NET Technologies
Scribble Software and Training
www.scribblesoftware.com
www.scribbletraining.com
You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Greg Robinson
Director of Training and .NET Technologies
Scribble Software and Training
www.scribblesoftware.com
www.scribbletraining.com

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Andrew Gayter
2002-10-17 13:07:36 UTC
Permalink
We use .MSI packages and deploy them using Active Directory and GPOs
This kind of deployment will result each Windows Installer on each
client invoking the .MSI file from a shared directory on the server.

Other techniques rely on ghosting, or taking images of OSs that have the
package installed. You can then push out the configuration onto client
machines.
You could configure your client's logon scripts to run the install, but
you will need to make sure it only runs once.

-----Original Message-----
From: Technical discussion of VBCOM [mailto:***@DISCUSS.DEVELOP.COM]
On Behalf Of Greg Robinson
Sent: 17 October 2002 12:05
To: ***@DISCUSS.DEVELOP.COM
Subject: Re: [VBCOM] installing client side proxies

I am using Windows Installer. I create a MSI file and then run the
SetUp.


Maybe I do not fully understand what else it can do for me though as I
do
not have much expierence in the Installer world. I do not want to have
to deploy a setup file that all my clients need to run.
-- Original Message --
Date: Thu, 17 Oct 2002 09:02:16 +0100
Subject: Re: [VBCOM] installing client side proxies
Windows Installer and Active Directory/SMS will do what you want.
-----Original Message-----
On Behalf Of Greg Robinson
Sent: 16 October 2002 14:07
Subject: [VBCOM] installing client side proxies
I have always had control over my clients (usually just another server)
when using DCOM. On my current project, I do not. We developed a DCOM
Object that will run on a server that hundreds of clients will remote
to.
I exported a client side proxy that we run locally for testing. I
would
rather not have to ask hundreds of clients to run the setup file on
their
workstations. I would like this to be invisible to them.
Is there a way I can 'hide' this or 'install this for them' without
their
knowledge? Our exe also runs on their workstations and we do monthly
updates.
I was thinking of adding some script that shells out to the set up
program
and runs it for them.
Greg Robinson
Director of Training and .NET Technologies
Scribble Software and Training
www.scribblesoftware.com
www.scribbletraining.com
You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Greg Robinson
Director of Training and .NET Technologies
Scribble Software and Training
www.scribblesoftware.com
www.scribbletraining.com

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Greg Robinson
2002-10-17 13:28:17 UTC
Permalink
Thanks Andrew. Your option 3 is my original plan. I will take a look at
deploying them using Active Directory and GPOs. I do not have much knowledge
of either, so it is time to learn!
-- Original Message --
Date: Thu, 17 Oct 2002 14:07:36 +0100
Subject: Re: [VBCOM] installing client side proxies
We use .MSI packages and deploy them using Active Directory and GPOs
This kind of deployment will result each Windows Installer on each
client invoking the .MSI file from a shared directory on the server.
Other techniques rely on ghosting, or taking images of OSs that have the
package installed. You can then push out the configuration onto client
machines.
You could configure your client's logon scripts to run the install, but
you will need to make sure it only runs once.
-----Original Message-----
On Behalf Of Greg Robinson
Sent: 17 October 2002 12:05
Subject: Re: [VBCOM] installing client side proxies
I am using Windows Installer. I create a MSI file and then run the
SetUp.
Maybe I do not fully understand what else it can do for me though as I
do
not have much expierence in the Installer world. I do not want to have
to deploy a setup file that all my clients need to run.
-- Original Message --
Date: Thu, 17 Oct 2002 09:02:16 +0100
Subject: Re: [VBCOM] installing client side proxies
Windows Installer and Active Directory/SMS will do what you want.
-----Original Message-----
On Behalf Of Greg Robinson
Sent: 16 October 2002 14:07
Subject: [VBCOM] installing client side proxies
I have always had control over my clients (usually just another server)
when using DCOM. On my current project, I do not. We developed a DCOM
Object that will run on a server that hundreds of clients will remote
to.
I exported a client side proxy that we run locally for testing. I
would
rather not have to ask hundreds of clients to run the setup file on
their
workstations. I would like this to be invisible to them.
Is there a way I can 'hide' this or 'install this for them' without
their
knowledge? Our exe also runs on their workstations and we do monthly
updates.
I was thinking of adding some script that shells out to the set up
program
and runs it for them.
Greg Robinson
Director of Training and .NET Technologies
Scribble Software and Training
www.scribblesoftware.com
www.scribbletraining.com
You can read messages from the VBCOM archive, unsubscribe from VBCOM,
or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
You can read messages from the VBCOM archive, unsubscribe from VBCOM,
or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Greg Robinson
Director of Training and .NET Technologies
Scribble Software and Training
www.scribblesoftware.com
www.scribbletraining.com
You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Greg Robinson
Director of Training and .NET Technologies
Scribble Software and Training
www.scribblesoftware.com
www.scribbletraining.com

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Loading...