I have a Sandbox setup to run the scripts for the control panel (Not all my
Clients have CF and other scripting tools)
I do not change the name IIS assigns to the logfile folder only the path.
MySandBox
LogFiles
--- TheDomain.com
---- Archives
-------- 20040617 (One for each Report/Archive)
---- Reports
-------- 20040617 (One for each Report/Archive)
---- Logfiles
-------- W3SVC*
IN my Control panel I have a virtual directory setup to point to the Reports
Folder. Each Sunday a new Report is created and the old is Archived along
with the logfiles. Each Archive is listed and I use CFFILE to retrieve Raw
LogFiles into a Textarea field.
Everything Is ran out of the database (RootPath, LogFilePath,
LogFileDirectory, domains and so on) and Cold Fusion Generates the report
each Sunday using Funnel Web Analyzer.
So I do not have away to automate the setup completely as I have to manually
enter the logfileDirectory. So I am pretty close.
Rick Eidson
Partner & CTO
ArcRiver Technology, LLC
ASP, PHP, PERL, Cold Fusion Hosting Kansas City
http://www.arcriver.com/
Kansas City Musicians
http://www.1sourceentertainment.com/
-----Original Message-----
From: Burns, John D [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 17, 2004 2:40 PM
To: CF-Talk
Subject: RE: IIS Automation questions
Rick,
How/where do you store the log files? I have the following structure
set up:
Websites
|_site1
|_www (iis root)
|_logs (where I want the logs to go but IIS puts the W3SVC### folder
in here)
|_stats (virtual directory /stats for the site where I output the log
stats)
|_site2 (just like site1 and so on)
What you described is most of what I want to automate.
John
-----Original Message-----
From: cfhelp [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 17, 2004 2:59 PM
To: CF-Talk
Subject: RE: IIS Automation questions
2)
This is what I do to create Sub-Domains for current Sites but with a
little modification it will work for new sites.
You need to use the mkw3site.vbs script that comes with IIS.
AdminScripts is the Directory mkw3site script is located in.
RootPath is the Root directory where I want to create the website.
sandbox is the 3rd level Domain in your case it would be "www".
VDomain is second level domain and the Top Level Domain "kchost.net"
<cfset CMDCommand='
C:#CHR(13)#
cd #AdminScripts##CHR(13)#
mkw3site -r #RootPath#\Sandbox\#Sandbox#.#VDomain#/Public_HTML -t
#VDomain#.#Sandbox# -h #Sandbox#.#VDomain##CHR(13)# mkdir
#RootPath#\Sandbox\#Sandbox#.#VDomain##CHR(13)#
mkdir #RootPath#\Sandbox\#Sandbox#.#VDomain#\Public_HTML#CHR(13)#
mkdir #RootPath#\Sandbox\#Sandbox#.#VDomain#\Database#CHR(13)#
'>
<cffile nameconflict="OVERWRITE" action=""> File="#RootPath#\Sandbox\sandbox.txt" output="#Trim(CMDCommand)#">
<cffile action="" source="#RootPath#\Sandbox\sandbox.txt"
destination="#RootPath#\Sandbox\sandbox.cmd">
<!--
<CFexecute NAME="#RootPath#\Sandbox\sandbox.cmd" ARGUMENTS=""
TIMEOUT="60"/>
-->
1) I am not sure about this one but if you figure it out let me know. I
automate our clients Stats and Archive the logfiles each Sunday but I
have to go in and modify IIS manually.
Rick Eidson
Partner & CTO
ArcRiver Technology, LLC
ASP, PHP, PERL, Cold Fusion Hosting Kansas City http://www.arcriver.com/
<http://www.arcriver.com/>
Kansas City Musicians
http://www.1sourceentertainment.com/
<http://www.1sourceentertainment.com/>
-----Original Message-----
From: Burns, John D [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 17, 2004 1:13 PM
To: CF-Talk
Subject: SOT: IIS Automation questions
Ok, this is more specific than the average "I want to automate IIS stuff
in CF questions". I have 2 specific questions that I'd like to see if I
can get a little bit of help with.
1) In IIS, I'm choosing custom paths for each sites logs to be stored
in. My question is if there's any way to have IIS store the logs
directly in the directory I choose as opposed to /W3SVC######. I want
to automate some other stuff based on this location and that is screwing
me up. Any suggestions would be great.
2) Along the same lines (and this may partially solve my first problem),
I'm trying to create a new site from a file. I was thinking I could
create a site with the generic setup that I use across all of my sites
and use CF to automatically edit the specifics of the site (host
headers, path for logs, home directory, etc), but as far as the unique
identifier for the site goes, is that just up to me to keep that unique
or is the a larger purpose for that which needs to be handled by IIS?
I know the second question is more along the lines of a typical "how do
I automate IIS" but any specific answers toward my questions would be
helpful. (Even if it's just to expand my knowledge) Thanks!
John
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
