FoxInCloud
Re: Production Server Setup
Messages
Reply
Edit
Delete
Apr. 8, 2013
09:46 am
3R90KYRMS![Show this entire thread in new window]()
09:46 am
3R90KYRMS
| From: | Thierry Nivelet (FoxInCloud) |
| To: | Michele |
WHen i run Web connection Setup and it asks me the script file path i leave the default or i have to modify it with another folder, that of my app ?
you can run console.exe from the trial version - http://www.west-wind.com/webconnection/download.aspx
You can install the trial version on you server, just for the sake of using console.exe
Where can i find the last version of West Wind Web Connection ? Have I to install it before all the steps you have sent ?
Ciao Michele,
Here are the main steps I would recommend; for details, please jump to the web connect documentation
1/ Install VFP*.dll on your server
We usually do a simple installshield express install for that (installshield express ships with VFP 9)
2/ Copy your files to your server
Make sure you compile xxxTest.exe in production mode.
Copy app (xxxTest.exe + dynamic resources like data, images and reports) into ...\program files\yourCompany\xxxTest\
...\site\xxxTest\ into inetpub\wwwroot\yourCompany\xxxTest\
...\VFP9\tools\aw\Scripts into ...\inetpub\wwwroot\awScripts\ except the _Source\ sub-folder
3/ Create a user account dedicated to your app
'xxxTest' looks like a good naming option ...
Make sure you open a session under this account to create alls relative folders, including a specific temp folder (useful to later purge VFP temp files)
4/ Create wc temp folder
Make sure xxxTest and IUSER* have full rights on this folder.
What we usually do is create c:\temp\ with full rights for everyone and create wc temp folders underneath.
5/ Review *.ini contents
Now that all folders are defined, review folders addresses declared in
...\program files\yourCompany\xxxTest\xxxTest.ini
and
...\inetpub\wwwroot\yourCompany\xxxTest\bin\wc.ini
6/ Register your COM server
in a command window, run "xxxTest.exe / regserver"
then run DCOMcnfg and set xxxTest.xxxTestServer to run as 'Interactive user' (we'll change that later on)
7/ set-up your site
You can use the wConnect console (console.exe) to create site or virtual directory, application pool and script-mapped extensions.
I would skip the COM object registration as we experienced some trouble with that step (reason why we do a manual registration above).
Otherwise, for a manual install, follow wConnect documentation.
In your site or virtual, create a virtual directory awScripts/ mapped to ...\inetpub\wwwroot\awScripts\ with just read rights
8/ Test your site in file mode
double-click xxxTest.exe in Windows Explorer to start your server.
do some requests against your server
9/ Test your site in COM mode
go to the admin page, ISAPI settings, switch to COM mode and 'load servers': you see your server window come up (reason why we use the interactive user above)
do some requests against your server.
10/ Change you COM user to xxxTest
run DCOMcnfg and set xxxTest.xxxTestServer to run as 'xxxTest'
when you restart your server, the server form no longer shows up.
Hi, we need a step-by-step instruction on how to install our FIC production server. We have a Windows 2003 Server.
Has someone a document or something similar with these informations.
Thanks
-- thn (FoxInCloud)