Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Web app

  Asked By: Wendy    Date: Aug 24    Category: MOSS    Views: 636

My original thought was that I was trying to increase scalability by dividing
functionality into three web applications. The first web app would handle the
"portal site" and standard team sites. The second app would be limited strictly
to MySite infrastructure, and the third application would be used for temporary,
project-based team sites. This would allow me to set different quotas as well
as enable site scavenging for stale sites.

All of this was pretty easy to deploy, but having different application and
port requirements, seemed to make navigation and support for my administration
staff more difficult. At one point, I was referred to the following link:

blogs.msdn.com/.../754902.aspx

This seemed to alleviate the aesthetic issues for the My Site infrastructure,
but at a cost of housing My Sites in the same web application which eliminates
scalability. It also doesn't help with my web application supporting temporary
sites.

Anyone have any suggestions on how to proceed? I'd like to find some way to
present these applications in a cohesive manner without having to compromise on
scalability.

Share: 

 

3 Answers Found

 
Answer #1    Answered By: Damon Garner     Answered On: Aug 24

I would like to try and help  you, but I am not sure what your perfrect scenario
would be. When I build a farm, I usually build the following web  applications:
http://centraladmin:<tcp#> http://ssp.organization.com - hosts only the
ssp http://mysite.organization.com - hosts my sites  (you can create as many
mysite Web apps as you would like, and use either global or Active Directory
group audiences to direct users to the correct web app)
http://portal.organization.com I generally install all Web apps, except Central
Admn, with standard  TCP port #s (80 or 443).

 
Answer #2    Answered By: Royce Orr     Answered On: Aug 24

So, are you then just using dns to create refer to these sites  then? I thought
that in WSS v2, the URL posted had to match up to the entry listed in the config
DB. Has that changed with v3 or are you using Alternate Access Mappings to help
out?

 
Answer #3    Answered By: Laura Walker     Answered On: Aug 24

Yes, you will need DNS entries. Either Host Headers or assigned IP addresses to
each of these Web applicatoins should work just fine. One caveat when using Host
Headers is the difficulty load balancing. Understand, I create actual Web
applications for each of these entries. I do like you your idea of having a
fourth Web application  to use for team  sites, you might possibly allow
self-service site  management in this Web application as well using automatice
site deletion.And, if you change the Web applictoin name (DNS) you simply have
to change the default internal URL (alternate access URL interface) to match the
new DNS entry. This will change the configDB. Does this help?

 
Didn't find what you were looking for? Find more on Web app Or get search suggestion and latest updates.




Tagged: