Re: COM+ Export: how does client know where the server is?

Every COM+ application proxy will specify this name when the msi is ran on
the client.
On NT4 and prior this information is kept in the registry and a tmp file in
the program files\complus applications\{guid} directory.
On Windows 2000 and forward the information is written to these locations as
well as a proprietary relational database maintained on the local system
drive (the COM+ catalog).

A client application can also over ride the specified server name when
creating the object by using code like the following:

Dim obj as "Object.ClassName"
Set obj = CreateObject("Object.ClassName", "SomeServerName")

The advantage this code has is it allows you to specify a fully qualified
computer name (e.g. 'computername.domainname.com') where the RSN in the COM+
catalog does not allow you to do this. If you need to connect to a COM+
server in another domain in your network this is the way to go.

Also, to answer your earlier question, COM+ uses the same port primarily
that MTS did. Port 135.
If you intend to put your servers behind a network load balancing device
(e.g. Server Iron) this is the port you need to specify for the network
device.

Ed--

----- Original Message -----
From: "Greg Robinson" <[email protected]>
To: <[email protected]>
Sent: Thursday, March 27, 2003 10:43 AM
Subject: Re: [VBCOM] COM+ Export: how does client know where the server is?


"go to the properties on your COM+ server, in the options tab under the
Export frame there's a field named "Application proxy RSN", when you export
a package that's the server name that is included... if it blank by default
it uses the computer name..."

This is only available at the 'My Computer' level, not the com+ server
level.  Does this mean every exported COM+ server will use this name?  I
assume I can enter IP Address here?

Thanks,

Greg Robinson
Custom Data Systems, Inc.
www.cds-am.net


-----Original Message-----
From: Technical discussion of VBCOM [mailto:[email protected]]On
Behalf Of Rolando Ramirez
Sent: Thursday, March 27, 2003 12:38 PM
To: [email protected]
Subject: Re: [VBCOM] COM+ Export: how does client know where the server
is?


go to the properties on your COM+ server, in the options tab under the
Export frame there's a field named "Application proxy RSN", when you export
a package that's the server name that is included... if it blank by default
it uses the computer name...

in the clients if you have Windows 2000 you can go to the component services
manager and go to the properties of the COM+ application you want to check
the server for and under the "Activation" tab you will find the field
"Remote server name", if my memory doesn't fail in Win9x that info was
stored in the registry...


Rolando


>From: Greg Robinson <[email protected]>
>Reply-To: Technical discussion of VBCOM <[email protected]>
>To: [email protected]
>Subject: [VBCOM] COM+ Export: how does client know where the server is?
>Date: Thu, 27 Mar 2003 11:31:59 -0500
>
>Dumb question, when I use Component Services Snap-In to Export a COM+
>server application, how do my clients knwo where the server is...by machine
>name?  Also, what tcp ports does the communication go through?
>
>You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
>subscribe to other DevelopMentor lists at http://discuss.develop.com.


_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

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.

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