Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

MOSS 2007 and web.config

  Asked By: Eliseo    Date: Jan 14    Category: MOSS    Views: 1132

I want to create multiple web applications (SPS 2003
virtual server) with each having its own site
collection.

I want to have a separate web.config for each web
application so I can easily access different setting
information. Is this pssible in MOSS?

Share: 

 

6 Answers Found

 
Answer #1    Answered By: Christen Roberson     Answered On: Jan 14

Yes - each web  app has its own web.config

However, to have a web.config for each site collection in this was is
possible but would limit you to about 20 site collections (the maximum
recommended number of web apps on a FEW server).

Why do you want to have a separate web.config for each site collection ?
I only ask as someone on the list may be able to suggest an alternative
solution for what you want to achieve.

 
Answer #2    Answered By: Faith Delgado     Answered On: Jan 14

I developed web  parts (which gets data via web
services) that I want to deploy at each web
application (virtual server). However, I want the web
part to display results based on the "location" of the
web application. If I can use a different web.config
for each web application, I can easily use an
appSettings entry to differentiate the "location"
values. The web part gets the appSettings value and
passes it as a parameter to the web service.

I'm sure there are other ways to do this.

 
Answer #3    Answered By: Alisha Itagi     Answered On: Jan 14

Could you not add this in as a variable to be input for the config  of
the web  part ?

I know this means that if anyone knew the different settings they could
get someone elses data but the chances of that have to be extremely low
?

 
Answer #4    Answered By: Maricela Conway     Answered On: Jan 14

A developer/administrator (myself) will setup the
web.config values when creating the web  applications.
This is okay because this is done only once.

FYI, I have to insure (with 100% certainty) that an
end user from one location (web application) never
sees the data from another location (another web
application). Because of this business requirement
(the end users are very possessive of their data), I
cannot chance any end user input at all to retrieve
this data.

With that said, a separate web.config for each web
application easily resolves this issue. I
programmatically get the appSetting value from
web.config.

 
Answer #5    Answered By: Vinay Thakur     Answered On: Jan 14

Sounds fair enough to me - splitting onto separate web  apps to ensure
data security is one of the reasons for using separate web apps - just
be aware of the 20 limit i guess so no more than 10, say, with one ssp
for each and one shared my sites i guess

Can you limit your portal to 10 big "buckets" of information - if you
can I would say that you are home and dry


 
Answer #6    Answered By: Caleb Gordon     Answered On: Jan 14

Yep - Only need 8..............

 
Didn't find what you were looking for? Find more on MOSS 2007 and web.config Or get search suggestion and latest updates.




Tagged: