Comments from Methodius Dusyk:

I have attached some batch files that I use to convert Open Admin scripts so that they can be used with IIS on a Windows Server.  The oaedit.bat file is used to change into folders and then the replace.bat script is called in each folder.  The postfix.bat is also used to add the "name" attribute to a form. If the name attribute does not exist IIS just shows a blank screen.   The replace.bat is up to date for  4.75R1.  I have to add a couple of changes to the script that were needed for later releases of 4.75.  I have created a new imageadd.pl using a temp working folder.
I had to use a couple of new variables in admin.conf to make the Picture Report work.
 
I am sure there is a more elegant way to do use perl to change the scripts.
P.S.
I had to change the filenames from .bat to .bats so that I could send them via our email.
 

Email 2:
Yes you can share the files.  The files are one part of the entire setup. I need to work on proper documentation to setup OA on a Windows Server using IIS.

 Active Perl did not contain all of the modules needed. I had to install a complier and get some source code from CPAN.   IIS itself has many permissions that need to be set so that files are protected properly. For site passwords , I set up Windows Groups and Users with permissions to specific sites. I have this documented but it needs updating. Several new variables are setup in admin.conf for scripts to work.  I am using a Perl zip utility wherever Open Admin zips up files.  Mail was setup on the Windows Server to allow email to Sask Learning.  Windows versions of Perl, MySQL, Tex, APG (password generator)  were installed.  Windows does not have softlinks to files so I have copies of some files that are in cgi in the tcgi folder.


Methodius Dusyk
IT Support
Living Sky School Division No. 202
Phone: 937-7952 Fax: 445-4332
methodius.dusyk@lskysd.ca
www.lskysd.ca

