PDA

View Full Version : multiple webapps in a workspace?



Raveen Ryan Sundram
18-Sep-2005, 04:04 PM
Hi,

We have just designed our first web application for the our mutli-store
system. But the webapp is currently target for interbranch ordering and
transaction viewing. As there is a master branch or warehouse, and the other
branches order their stock from it.

We are now planning to have an online shopping cart system for the
customers, but VDF10.1 only allows for 1 webapp per workspace? Is there a
reason for this? Has this changed in VDF11? How can I workaround this
problem?

Raveen

Knut Sparhell
18-Sep-2005, 07:21 PM
Raveen Ryan Sundram wrote:

> We are now planning to have an online shopping cart system for the
> customers, but VDF10.1 only allows for 1 webapp per workspace? Is there a
> reason for this? Has this changed in VDF11? How can I workaround this
> problem?

One webapp per workspace, up to VDF 11.1 beta.

There are two kinds of workarounds:

1. It's quite easy to merge two or more web applications into one. A
webapp may be seen as a collection of web objects, each serving a
purpose or a set of related purposes.

There is no common application panel visible to the user, no
autogenerated menu system, except for the "test menu". Properties
should pnly hold temporary vaules, anyway. Session variables should be
kept in the IIS Session object, anyway. For descrete login to one
application use separate session variables for this status.

Have some web objects for logical application A and some for logical
application B.

Keep separate ASP files for each logical application.

What will be common are the process itself and the global.asa.

Have a default.asp directing the user to a menu depending on the URL or
host name requested. Have two virtual folders or two sites (by host
names) pointing to the same AppHtml folder.

Example:

WebApp A is accessed through URL:
http://www.yourserver.com/webapp-a/

WebApp A is accessed through URL:
http://www.yourserver.com/webapp-b/

Content of global.asa:

If InStr(Request.ServerVariables("url"),"webapp-a")>0 Then _
Request.Redirect "menu-a.asp" Else _
Request.Redirect "menu-b.asp"


2. Design your own development folder structure, where typically the
DDSrc is a common folder and set up two workspaces that both use this or
these common folder(s). As long as the AppSrc and the Programs folder
are separate, there will be no interference during compiling.

You *may* even have the AppHtml folder in common, to be able to have
some or all the asp files in common, but this will require som spexial
coding in the global.asa to separate the initialization of two different
web applications.

Example, whith shared AppHtml, content of gobal.asa:

If InStr(Request.ServerVariables("url"),"webapp-a")>0 Then _
WebAppServerSession.Initialize("yourwebapp_a") Else _
WebAppServerSession.Initialize("yourwebapp_b")

--
Knut Sparhell, Norway

Raveen Ryan Sundram
18-Sep-2005, 10:19 PM
Knut,

Thanks for the ideas. I like the simplicity of approach #1 but approach #2
would be more efficient, I guess.
It would generate 2 smaller webapp.exe than 1 large webapp.exe, hence,
saving server resources. But it would require more management/resource in
the sense of development & deployment.

Raveen


"Knut Sparhell" <knut@sparhell.no> wrote in message
news:yqCLeALvFHA.3904@dacmail.dataaccess.com...
> Raveen Ryan Sundram wrote:
>
>> We are now planning to have an online shopping cart system for the
>> customers, but VDF10.1 only allows for 1 webapp per workspace? Is there a
>> reason for this? Has this changed in VDF11? How can I workaround this
>> problem?
>
> One webapp per workspace, up to VDF 11.1 beta.
>
> There are two kinds of workarounds:
>
> 1. It's quite easy to merge two or more web applications into one. A
> webapp may be seen as a collection of web objects, each serving a purpose
> or a set of related purposes.
>
> There is no common application panel visible to the user, no autogenerated
> menu system, except for the "test menu". Properties should pnly hold
> temporary vaules, anyway. Session variables should be kept in the IIS
> Session object, anyway. For descrete login to one application use separate
> session variables for this status.
>
> Have some web objects for logical application A and some for logical
> application B.
>
> Keep separate ASP files for each logical application.
>
> What will be common are the process itself and the global.asa.
>
> Have a default.asp directing the user to a menu depending on the URL or
> host name requested. Have two virtual folders or two sites (by host
> names) pointing to the same AppHtml folder.
>
> Example:
>
> WebApp A is accessed through URL:
> http://www.yourserver.com/webapp-a/
>
> WebApp A is accessed through URL:
> http://www.yourserver.com/webapp-b/
>
> Content of global.asa:
>
> If InStr(Request.ServerVariables("url"),"webapp-a")>0 Then _
> Request.Redirect "menu-a.asp" Else _
> Request.Redirect "menu-b.asp"
>
>
> 2. Design your own development folder structure, where typically the
> DDSrc is a common folder and set up two workspaces that both use this or
> these common folder(s). As long as the AppSrc and the Programs folder are
> separate, there will be no interference during compiling.
>
> You *may* even have the AppHtml folder in common, to be able to have some
> or all the asp files in common, but this will require som spexial coding
> in the global.asa to separate the initialization of two different web
> applications.
>
> Example, whith shared AppHtml, content of gobal.asa:
>
> If InStr(Request.ServerVariables("url"),"webapp-a")>0 Then _
> WebAppServerSession.Initialize("yourwebapp_a") Else _
> WebAppServerSession.Initialize("yourwebapp_b")
>
> --
> Knut Sparhell, Norway