Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

My Sites running on it's own web application

  Asked By: Donnell    Date: Feb 20    Category: Sharepoint    Views: 1892

When initially setting up SharePoint we configured My Sites to run on its own
web app (as well as its own iis web site and app pool on port 83).

This generated a URL with the port number, 83, included.

What I'm trying to do is give a My Sites web application in SharePoint running
on port 83 (also currently on its own iis site and app pool) a more user
friendly URL - i.e. the port number 83 doesn't show - when users browse their My
Sites page and all subsequent pages underneath it.

We definitely want to keep My Sites on its own SharePoint 2007 Web Application
for performance and administrative purposes.

Is this an acceptable method to display a more user friendly URL…

We created a C-name record in DNS that resolves mysitestest to the ip of our dev
Moss server.

When creating our SSP we made My Sites its own web application using a newly
created IIS site and app pool on port 83.

We'll call the My Sites web app http://servername:83/

The primary Web app is http://servername on port 80.

The AAM I create for the My Sites web app is http://mysitestest (note: no port
specified in the AAM)

After this when I go into the edit shared service provider properties page (My
Site Location URL) or the My Site Settings page (Personal site provider) within
the SSP Admin page I see the My Sites Location URL listed as
http://mysitesdev:80/

Is this approach acceptable? Could it cause any potential issues?

Share: 

 

3 Answers Found

 
Answer #1    Answered By: Parijat Pathak     Answered On: Feb 20

Typically you'd do this with a "host header" site running  on port  80.
There isn't really a good way to get a friendly URL on an alternate port
without involving some sort of URL re-writing proxy like ISA.

 
Answer #2    Answered By: Ella Sargent     Answered On: Feb 20

Would a DNS redirect work for this using the cname? I can't remember if
that would still want a port  80.

BTW...over the last year I have learned a ton from your posts. You have
a lot of good advice and I thought you should know that I appreciate
your work. Are you on twitter?

 
Answer #3    Answered By: Ahmad Johns     Answered On: Feb 20

DNS only handles the IP address - you need either a host header (which
allows you to run  more than 1 IIS site  on port  80) or something that
will do a port direct. A http:// URL without a port number  will always
try to contact port 80, an https:// URL port 443.

 
Didn't find what you were looking for? Find more on My Sites running on it's own web application Or get search suggestion and latest updates.




Tagged: