Deploying the filesLast Updated: 9/16/2008 | |
| Sections above here: Home » Development » Page Mode » IntraWeb Pages | |
|
Sections below here: Topics in this section: |
Deploying IWP is a very simple task. Other than configuring the web server to process IWP pages, the only other task is to copy the files to the correct location. Independently of what web server you use, there are two things that need to be deployed: the static and dynamic pages are the first, and the actual web application are the second. The pages (independently of whether the are static or dynamic) need to be placed in the folder where your web server hosts web pages. In IIS this is normally wwwroot by default. In Omni it is htdocs. The application needs to be deployed to the physical path where your virtual scripts folder points to. This must coincide with the ApplicationURL value entered in the IWPageController. Calling the IWP pagesOnce you have deployed all the files, all you need to do is call the page in question. For example, if your site is www.mydomain.com, and your IWP page is called first.iwp, then just open the browser and type http://www.mydomain.com/first.iwp. The web server (via the association we made in Preparing the Server) automatically knows that when an IWP extension (or whatever extension you put) is requested, it will launch the corresponding web application (in our case project1.dll). As you can see, IWP introduces a very easy yet powerful way of creating dynamic websites. There is hardly any code that needs to be written on the server side to handle the actual processing of the pages, other than the forms you wish to serve dynamic pages with. |
(C) 2002-2009 - Atozed Software Ltd. | |