Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Quick portal setup questions in SPS2003

  Asked By: Abhilash    Date: Dec 26    Category: Sharepoint    Views: 787

Is it possible to create a portal site in SPS 2003 with the same
convention as SPS2001? By this, I mean, can I create a site with
the
naming convention of http://servername/name <http://servername/name>
<http://servername/name <http://servername/name> >
just
like how it appears in
SPS2001? Right now the portal site appears as http://servername:81
<http://servername:81/>
<http://servername:81/>
<http://servername:81 <http://servername:81/>
<http://servername:81/> >
<http://servername:81 <http://servername:81/>
<http://servername:81/> <http://servername:81 <http://servername:81/>
<http://servername:81/> > > If
I have a bunch of portal sites (like workpsaces in 2001) with
different
port numbers it makes it more difficult to manage for users than the
naming convention in 2001 where workspaces were
http://servername/workspacename <http://servername/workspacename>
<http://servername/workspacename <http://servername/workspacename> >

Also can I have a portal site without assigning a port number?...and
by
this I mean not using the default web.

Share: 

 

13 Answers Found

 
Answer #1    Answered By: Darryl Nguyen     Answered On: Dec 26

I guess my question would be, why use ports instead of using Virtual
Servers? Perhaps this is the answer you are looking for in your
last
statement?
You can create  a limited number of virtual servers on your IIS/SPS
box
to handle each of your needs for a unique portal  with distinct
settings.
You can even give a unique URL to each virtual server without the
need
for specifying ports.

 
Answer #2    Answered By: Tom Pruitt     Answered On: Dec 26

I would like to use virtual server but every time I go to create  one
it wants to use the default web site  and then I can not create anymore.

 
Answer #3    Answered By: Sammie Lancaster     Answered On: Dec 26

Are you creating a Virtual Server in IIS first? If not, try doing
that first and then you should be able to connect your new SPS virtual server to your newly created IIS Virtual Server.

 
Answer #4    Answered By: Aron Kirk     Answered On: Dec 26

Does anyone have more info on this?

What I am trying to do is to create  a similar setup  of SPS2003 as I
had in SPS2001, whereas, the name of the server is followed by the workspace name
i.e. http://servername/workspacename Can I make a similar setup on
SPS2003?
What I want to do is to create a portal  site from the SharePoint
Portal Server Admin section (not a top level web site  which is different and part of SharePoint Services section of the Administration). In order to do this,
I need to first create a virtual server in IIS (which is referred to as a website). When I go to create a web site in IIS Manager I have to use a port number that is different than the default web site i.e. a port other than 80. When I do this the web site is accessible as http://servername:portnumber <http://servername:portnumber/>
<http://servername:portnumber/> for
example http://servername:81 <http://servername:81/>
<http://servername:81/> So then when
I go back to SharePoint Central Administration to create a portal site the web site is available to me but I still must use http://servername:portnumber <http://servername:portnumber/>
<http://servername:portnumber/> I cannot name it as
http://servername/portalname I have tried to configure alternate
access settings and put in a different name but I get an error that slashes can't be used.

First of, can this be done?
> > > If so, has anyone done this successfully and how?

 
Answer #5    Answered By: Hailey Clark     Answered On: Dec 26

I am having the same problem to which solutions have been suggested,
and
I
have followed the manual.

I have succeeded in bringing up one SPS on a machine that also uses
SQL
server (this means that there is one Central Administration on a
randomly
assigned port number which then gets me to the WSS Central Admin
and also the SPS Central Admin). After that I have succeeded in
bringing up
one portal  Site.

Using the same Portal Admin, I have tried to bring up a second Portal
Site,
but I am not successful.
By this I set up another Virtual Server on IIS ( I have tried to do
it
with
both port 80 and another port),
and then create  the Portal site  from Central Admin the same way I
created
the first portal site.
I get the message that the portal site has been created successfully,
but when I attempt to go to the home page of the second portal site, I
get
an error message, and
not even the admin page for the second Portal.

Maybe I am not understanding correctly.

1) Can I have only one portal site per portal Server? (The
documentation
suggests otherwise, and
the system goes through the process of creating a second Portal site,
but I
cannot access the second portal site even from the manage Portal sites
using
the URL provided there)
2) Has anyone personally created a second Portal Site on a Portal
Server
with SQL server or with MSDE
successfully who could share their experience of what exactly they
did?

 
Answer #6    Answered By: Nisarg Shahane     Answered On: Dec 26

To answer your questions  below:

1. Yes, it is possible to create  multiple portal  sites on one server
as
long as you setup  multiple virtual directories. The virtual
directories
will have to have either different port numbers, host header names or
IP
addresses.
2. Yes, I have been successful creating multiple portal sites.
Currently
I have 5 portal sites running on one server. My setup is that I have 5
different IP addresses, 1 for each portal site.

 
Answer #7    Answered By: Naimish Misra     Answered On: Dec 26

A few more details would be helpful in my next attempt.

1. Yes, it is possible to create  multiple portal  sites on one server
as
long as you setup  multiple virtual directories. The virtual
directories
will have to have either different port numbers, host header names or
IP
addresses.
I am glad to hear there has been a success. Using the IIS Server,
the default web server was put at the default C:\Inetpub\wwwroot.
I created new virtual servers P2, P3 on IIS under the default machine
and gave them virtual directories C:\SPS\P2 , C:\SPS\P3 etc which were
empty directories. I used the same IP address, port 80 and other port
numbers,
and different host header names (e.g. P2).
The primary site  comes up as http:// <http:///> <machinename>
After P2 and P3 and supposedly created, the names come up as
http:// <http:///> <machinename>/P2
and http:// <http:///> <machinename>/P3 on the admin page, but going to
those pages give
me an
error.

2. Yes, I have been successful creating multiple portal sites.
Currently
I have 5 portal sites running on one server. My setup is that I have 5
different IP addresses, 1 for each portal site.

I assume that by one server you mean one machine running one SPS server,
and
that the sites are all under the same IIS server on that one machine,
but
configured
with a different IP address. Have you been successful using the same IP
address
but different ports or different Host Headers?
Also, are you using SQL Server or MSDE as the database engine. I doubt
if
it
makes a difference, but I would like to try to duplicate your success as
much
as possible before trying out the other things.
Also, what are the URLs for the various Sites?
Are they http://P1 <http://p1/> , http://P2 <http://p2/> etc
or http:// <http:///> <Machinename> http:// <http:///> <machinename>/P2
etc?

 
Answer #8    Answered By: Terence Thornton     Answered On: Dec 26

1. I'm sorry but I have not tried it with different port numbers. I've
only heard that it's doable. But I did try it with different host header
names and that works fine too as long as you make sure there are entries
for these host header names in your DNS.

2. It's one instance of SPS 2003 with multiple portal  sites using
multiple web sites in IIS with different IP addresses for each site.
Each site  has its own distinguish name, i.e., http://servera,
http://serverb, etc.. I'm using SQL and not MSDE.

 
Answer #9    Answered By: Alka Sarabhai     Answered On: Dec 26

Just to be sure, are those other servers running? They don't
necessarily start automatically.

For those of you that are having trouble with this and have not checked
the SPS admin guide, I highly recommend it. It spells the entire
process out - search for "extending virtual servers" to find the
section. The guide is located at:

www.microsoft.com/.../details.aspx
941-92F5-048BF00CF332&displaylang=en

 
Answer #10    Answered By: Eashan Nadkarni     Answered On: Dec 26

All the web sites run automatically since I assigned different IP
addresses for each one (even after the server is rebooted). Haven't had any problems so far.

 
Answer #11    Answered By: William Odom     Answered On: Dec 26

One other thing I should point out - all of our virtual servers share an
IP address. I am told that to implement SSL on the VS's we'll have to
setup separate IP addresses for each however.

 
Answer #12    Answered By: Mia Scott     Answered On: Dec 26

This is true for any web site. Each site  will have to have its own IP
address as well as its own SSL certificate.

 
Answer #13    Answered By: Kristian Chaney     Answered On: Dec 26

I think I discovered the step I was missing, and which I overlooked.
When creating the virtual server on IIS,
for a different IP address, I needed to also add the IP address to the
network connection
and make an entry in the DNS table
when using unassigned IP address with host header name, I needed to make
the appropriate
entry in the DNS table.

Thanks very much for the help; the replies you gave set me thinking along
the right direction.

 
Didn't find what you were looking for? Find more on Quick portal setup questions in SPS2003 Or get search suggestion and latest updates.




Tagged: