Its getting a little clearer. e.g. you could have one folder on the hd 
managed by IIS and another folder managed by Apache, correct?

Now that you mentioned authentication, I plan to do that, but can't find any 
documentation on mg's groups and users. I read some blurb somewhere that 
everyone is requred to log in but I haven't experienced that requirement using 
Sheboygan. I should start another thread on that when I get to that point.

I'll definitely try to post my finding on trac, if I can stay on track.  ;-)
 
Ed Jobe



----- Original Message ----
From: "Kenneth Skovhede, GEOGRAF A/S" <[EMAIL PROTECTED]>
To: MapGuide Users Mail List <[email protected]>
Sent: Wednesday, October 1, 2008 9:02:52 AM
Subject: Re: [mapguide-users] MGOS2.0.2 bundled installation won'tsupportphpon 
IIS6

Apache has its own strengths, and if you are not using IIS features (integrated 
authentication, .Net, etc) in MapGuide,
I can see why you would want to use Apache. 
If you have a .Net application on the same server, you may want IIS too.

The install documents assume that you choose Apache and PHP.
Anythin else means you're on your own.

If you get a list of changes, please do post them as a ticket in Trac.

Regards, Kenneth Skovhede, GEOGRAF A/S


[EMAIL PROTECTED] skrev: 
Thanks Kenneth,
I didn't realise you could install Apache and IIS. What would be the reason for 
doing so? I guess, then, that when the install guide was written, it was with 
Apache in mind (i.e. specifying 8008)? I found other discrepancies and things 
that need updating in the install guide. I was thinking of making some 
corrections and submitting it.
 
Ed Jobe



----- Original Message ----
From: "Kenneth Skovhede, GEOGRAF A/S" <[EMAIL PROTECTED]>
To: MapGuide Users Mail List <[email protected]>
Sent: Wednesday, October 1, 2008 12:02:24 AM
Subject: Re: [mapguide-users] MGOS2.0.2 bundled installation won'tsupportphpon 
IIS6

If you install Apache, it will use port 8008, because you may have other stuff 
(IIS?) using port 80.

Whenever you do something with the Site Admin, it communicates with the 
MapGuide service over a port on the loopback interface.
This port is NOT 8008, and should not be either.

Whenever your application communicates with the MapGuide service, it uses 
another port on the loopback interface.
This port is NOT 8008, and should not be either.

(It may redirect to another machine, but usually it is the same machine, and 
thus a loopback).

Regards, Kenneth Skovhede, GEOGRAF A/S
  

[EMAIL PROTECTED] skrev: 
Are the port numbers the same in the web config file and the server config 
file? 
Yes, there are 3 ports config'd and they were the same in both files. They 
weren't 8008 though. I didn't get prompted to specify them during install like 
I did with 2.0.1. 
 
Speaking of ports, the doc's mention localhost:8008. If I use that, it can't 
find login.php. If I just use localhost, it can. Could someone explain why?

________________________________

_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users

Reply via email to