Calling MTS components from Seperate IIS server

I would like to design a 3-tier solution with Com components and SQL server.
To make scalable solution I intend to make IIS , SQL server and MTS on seperate
server.

Q1. Can MTS be installed without IIS.

Q2. So now if I have three machines ( taking the assumption that
MTS will not install seperate of IIS)
A.One Server with IIS running ASP calling another MTS server
(Only services component requests) and this server calls SQL
Server.
Will this scenario work

B. Will Createobject called from the 1st IIS /ASP Server to create component
on another server running MTS with the following command

Set objComponent = createobject("oPerson.Address", MTSserver)

where MTSserver refers to the second MTS Server

C. Will I have to do anything special for DCOM to work.

Thanks.

sajid
see answeres inline
ranga
"sajid" <shshaikh@onebox.com> wrote:
>
>I would like to design a 3-tier solution with Com components and SQL server.
>To make scalable solution I intend to make IIS , SQL server and MTS on seperate
>server.
>
>Q1. Can MTS be installed without IIS.
Yes, definitely -- IIS is a web server - MTS is a transaction server ..
2 different things

>Q2. So now if I have three machines ( taking the assumption that
> MTS will not install seperate of IIS)
>A.One Server with IIS running ASP calling another MTS server
> (Only services component requests) and this server calls SQL
> Server.
>Will this scenario work

you can install iis and mts in one server
or you can install them in separate servers


>B. Will Createobject called from the 1st IIS /ASP Server to create component
>on another server running MTS with the following command
>
>Set objComponent = createobject("oPerson.Address", MTSserver)
>
>where MTSserver refers to the second MTS Server

your question is incomplete . if are you asking if your syntax is correct
.. yes it is .. since you will be exporting the proxies of the mts components
from the MTS server and installing it in the IIS server, you don't need the
MTSServer parameter in the CreateObject method .. if you give it, it won't
hurt either.

>C. Will I have to do anything special for DCOM to work.

you need to make sure dcom is enabled on the servers - it is by default --
if it is not, then type dcomcnfg and check the appropriate box.
>Thanks.
good luck

I just wanted to ******** something...IIS, MTS - are two different entities,
however - IIS must have MTS as a host for some of its objects. IIS is then
dependant on MTS, but not the other way around.

Ian



"ranga raghunathan" <ranga1@msn.com> wrote:
>
>sajid
>see answeres inline
>ranga
>"sajid" <shshaikh@onebox.com> wrote:
>>
>>I would like to design a 3-tier solution with Com components and SQL server.
>>To make scalable solution I intend to make IIS , SQL server and MTS on
seperate
>>server.
>>
>>Q1. Can MTS be installed without IIS.
> Yes, definitely -- IIS is a web server - MTS is a transaction server ..
>2 different things
>
>>Q2. So now if I have three machines ( taking the assumption that
>> MTS will not install seperate of IIS)
>>A.One Server with IIS running ASP calling another MTS server
>> (Only services component requests) and this server calls SQL
>> Server.
>>Will this scenario work
>
>you can install iis and mts in one server
>or you can install them in separate servers
>
>
>>B. Will Createobject called from the 1st IIS /ASP Server to create component
>>on another server running MTS with the following command
>>
>>Set objComponent = createobject("oPerson.Address", MTSserver)
>>
>>where MTSserver refers to the second MTS Server
>
>your question is incomplete . if are you asking if your syntax
is correct
>.. yes it is .. since you will be exporting the proxies of the mts components
>from the MTS server and installing it in the IIS server, you don't need
the
>MTSServer parameter in the CreateObject method .. if you give it, it won't
>hurt either.
>
>>C. Will I have to do anything special for DCOM to work.
>
>you need to make sure dcom is enabled on the servers - it is by default
--
>if it is not, then type dcomcnfg and check the appropriate box.
>>Thanks.
>good luck
>
>

Thanks Ian and Ranga.

My Question was regarding the correctness of the syntax
Set objComponent = createobject("oPerson.Address", MTSserver)

Again clarifying I will be calling this from an IIS server to another MTS
server. Is there any problems I should anticipate with setting DCOM and working
like that.

After digging thru MSDN I found what Ian has said:

"Microsoft Internet Information Server version 4.0 is integrated with MTS
2.0 and uses MTS for many run-time services, such as
transaction management. Transaction support lets IIS Active Server Pages
access databases, mainframe applications, and message queues with full data
integrity protection. MTS integration also provides IIS with process isolation
to prevent individual failures from affecting other parts of a Web site,
enhanced run-time services such as thread and connection pooling for better
performance, and easier component management. "


"ian drake" <ian.drake1@home.com> wrote:
>
>I just wanted to ******** something...IIS, MTS - are two different entities,
>however - IIS must have MTS as a host for some of its objects. IIS is then
>dependant on MTS, but not the other way around.
>
>Ian
>
>
>
>"ranga raghunathan" <ranga1@msn.com> wrote:
>>
>>sajid
>>see answeres inline
>>ranga
>>"sajid" <shshaikh@onebox.com> wrote:
>>>
>>>I would like to design a 3-tier solution with Com components and SQL server.
>>>To make scalable solution I intend to make IIS , SQL server and MTS on
>seperate
>>>server.
>>>
>>>Q1. Can MTS be installed without IIS.
>> Yes, definitely -- IIS is a web server - MTS is a transaction server ..
>>2 different things
>>
>>>Q2. So now if I have three machines ( taking the assumption that
>>> MTS will not install seperate of IIS)
>>>A.One Server with IIS running ASP calling another MTS server
>>> (Only services component requests) and this server calls SQL
>>> Server.
>>>Will this scenario work
>>
>>you can install iis and mts in one server
>>or you can install them in separate servers
>>
>>
>>>B. Will Createobject called from the 1st IIS /ASP Server to create component
>>>on another server running MTS with the following command
>>>
>>>Set objComponent = createobject("oPerson.Address", MTSserver)
>>>
>>>where MTSserver refers to the second MTS Server
>>
>>your question is incomplete . if are you asking if your syntax
>is correct
>>.. yes it is .. since you will be exporting the proxies of the mts components
>>from the MTS server and installing it in the IIS server, you don't need
>the
>>MTSServer parameter in the CreateObject method .. if you give it, it won't
>>hurt either.
>>
>>>C. Will I have to do anything special for DCOM to work.
>>
>>you need to make sure dcom is enabled on the servers - it is by default
>--
>>if it is not, then type dcomcnfg and check the appropriate box.
>>>Thanks.
>>good luck
>>
>>
>

Hi,

There are some white papers from MS @
http://www.microsoft.com/ISN/ind_sol...osting_444.asp
which might be of interest to you.

One of their recommendations is to NOT call directly call off an IIS
machine. Why? Because of the nature of script languages and COM. Script
languages call IDispatch interface, and query if a certain method is
implemented. This means 2 calls over the network. It's better to create a
local wrapper for the function you're trying to call remotely.

BR, YRE