There have been a number of requests on the Reddot google group recently about running ASP pages inside Liveserver. The only responses that I’ve seen are along the lines of “it’s not possible, you’ll need to publish the pages out somewhere else”. Well… I’m glad to say there is a way to simply publish pages into Liveserver and forget about it.
This would also work for any other languages that Tomcat doesn’t support, such as Cold Fusion or PHP and any other related web servers. For this example I’m going to stick to the one I know ASP/IIS, I’m sure you can work out the tiny changes necessary for your language of choice
The downside? There’s an additional license cost. Oh what a surprise! The module you are looking for in your license agreement is the Application Portal module.
Assuming you have this, we can proceed with the setup.
Step 1 – Create the IIS site
Before we start with the Liveserver configuration, or even adding some ASP into our templates, we need to set up an IIS project that Liveserver can use to temporarily store the ASP. To save us some work we’re going to use one site for every project, but it’s up to you if you want to split out the temporary files by project.
Make sure that this location allows Reddot read/write access and that the IIS site is running ASP, otherwise you’re not going to get very far!
For this example I’m going to create the folder c:inetpubwwwrootLsTemp, which can be accessed through http://[servername]/LsTemp
Make a note of the server name and folder name as you’re going to need those in a sec.
Step 2 – Create a Portal Connector
Step 3 – Setting up the Liveserver project
Step 4 – Adding some ASP
The last stage is to add some asp to your CMS project and try publishing it out. One thing to note here… make sure you’re not pre-executing your ASP code, otherwise it’ll never work, no matter how accurately you set up Liveserver!
Once you’ve added the ASP and set the page extension to be .asp, you can now publish your pages into the Liveserver project you configured in Step 3.
So what’s all that doing?
When we’re browsing through the Liveserver project, whenever you attempt to access a file with .asp as it’s extension, our Rule form step 3 kicks in. This creates a temporary copy of the file out in IIS, lets IIS do it’s magic rendering the ASP parts of the page, and then sucks the output back into Liveserver to finish the magic there. If you’ve set it up correctly you’ll never know that anything ever went outside of Liveserver.
I would, however, suggest you try and limit the number of rules that you use as it does put extra load onto the server.
There are two Liveserver documents that you’re going to want access to. One is Liveserver Connectors and the other is Liveserver Projects Content.
No related posts.