They have one server currently.  We are getting ready for their new site to go live.  The new site will go live on their app server for the time being.  So, they developed the site under the app - http://imis.abc-hq.org/imis15/abc.  Their live site will be http://www.abc.org.  At the moment, we are using the ip address.  Once we get this working we will switch the dns over to the new ip address to hit that site.  So, in the URL(s) pointing to the site, I have added http://imis.abc-hq.org/imis15/abc, http://{ip address}.  In the URL Name for the site, is ABC.  According to how I read the docs (page 70 of the web content management docs) since there are two URLs in the URL(s) pointing to the site, the url should be dymanically built based upon the URL and the URL Name of the site, so when the user goes to http://{ip address} the URL should be build dynamically and render as http://{ip address}/ABC, but it is not.  It is rendering as http://{ip address} which is bringing up the casual site.

The virtual directory needs to be in both URLs; try http://{url address}/imis15/abc instead.

Eric Means
System Architect, ASI

We actually have two publishing servers set up.  One (A) port 15151 to http://imis.abc-hq.org/imis15 and (B) port 15152 to http://www.abc.org.  I tried setting up the second url to point to http://{ip address}/abc but that didn't seem to matter.  This was also based upon the docs for setting up the WCM site under the site and not as an app.  Was that not correct or needed?

If there is a virtual directory involved, then WCM needs to know it. You need to enter the full address to get to the actual WCM install. Since you're using the appserver to serve the WCM site, you have to include the appserver's virtual directory, even when using the IP address. Essentially, the IP address is a direct replacement for the hostname, it won't automatically make IIS understand what path it needs to load.

Try http://{ip address}/imis15/abc

Eric Means
System Architect, ASI

Maybe that's where I am confused.  Yes, we are using the app server and the app server has two webs set up.  One for imis.abc-hq.org where iMIS is running as a virtual app under the web and antoher web set up in IIS as www.abc.org.  We copied the net folder into the root of the www.abc.org web and want to serve that as a website, not a virtual app.  I followed the docs for setting this up. The docs indicate that it doesn't really matter if you are on the same server or not (recommended you be on a seperate server for security) but none the less. 

I tried adding the url as you indicate and I still get the casual site instead of the WCM site.

Okay, I think I see what you're doing. To be clear, it sounds like imis.abc-hw.org is the default website and www.abc.org is set up as a secondary site, using host headers and a different IP.

Make sure that the default website is not bound to all IP addresses (which is the default IIRC), otherwise unless the browser sends a hostname/host header it will get the default website.

You could also try setting the IP address to be the first URL listed instead of the second; if you are running an earlier version than 15.1.1.3632 (see SMR 200162), then the first URL will be used for all navigation items, which may cause some oddities. I don't think that's the case here, but it's worth mentioning.

Eric Means
System Architect, ASI

Actually we are on 15.1.2.  The default site is set to all unassigned.  What should it be set for?  I only have the two IP addresses for this machine. 

I actually have tried it where the http://{ip address} is the only url in the list.  I have tied http://{ip address}, http://{ip address}/abc, http://{ip address}/imis15/abc, etc. Nothing changes the fact that it serves the casual site.  I can, from the browser, open url http://{ip address}/abc without any problems,but that doesn't get me where I need to be.

You could try setting only the first IP address for the default website and only the second for the WCM website.

One other thing to try would be to try the IP http://{ipaddress}/abc/home/abc/default.aspx, in case using the full nav/physical path works.

Eric Means
System Architect, ASI

Still get the casual site.

another thing to note:  When I have only the one url in the list, when I click on the link in the Site Manager to open the web, I get a strange url rendered:

http://%20http://{ip address}/abc/abc/home/abc/default.aspx?...

And the only thing in the Website Root URL field is http://{ipaddress}/ ?

Make sure the Secure Website Root URL field matches (except potentially for using https: rather than http:) the Website Root URL field exactly.

Eric Means
System Architect, ASI

If I have just http://{ip addrss}/ in the list of urls, the URL listed in Manage Websites is http://{ip address}/abc/home/abc/default?...  If I click on it, it tries to open

http://%20http//{ip address}/ABC/Home/ABC/Default.aspx?hkey=b785de57-98a1-48ec-859d-7354ab3b5115

Matches exactly.  And it is the only thing in the list of urls.

It's really odd that it's putting an http://%20 in there. I notice that the second http doesn't have a : after it -- that's definitely odd. Can you export the website object and e-mail me the XML (emeans at advsol dot com)?

Eric Means
System Architect, ASI

Did you ever get this to work? And if so, how? I have a customer going live very soon on domain name 1, but creating a new site within the same WCM application that will need to be under a different domain.

Terry Hammond enSYNC Corporation Fort Worth, TX terry@ensync-corp.com