Attention! Helicon Tech Blog has moved to www.helicontech.com/articles/

Friday, November 13, 2009

Helicon Ape remote management using IIS 7

Management on local machine

After installation of Helicon Ape (Full or Free Edition) on Windows 2008 Server or Windows 7 you have a possibility to edit httpd.conf and .htaccess files directly in IIS Manager in the same way as in Helicon Ape Manager.


To edit particular .htaccess file select the corresponding folder in the sites tree and double-click on Helicon Ape icon. To configure httpd.conf select the tree root (usually having the host name).


Helicon Ape snap-in empowers you to manage not only configuration files but also licenses via License Manager available in Help -> License Manager.

Management on remote server

In IIS 7 the remote administering functionality was introduced. It became possible to manage IIS on remote server from local machine even with Windows XP on it. Here's the Microsoft story about it.

Let's have a closer look at this function.
Capabilities of remote IIS Manager are outlined here. IIS Manager itself may be downloaded here.


  1. Having the IIS Manager installed, run it.
  2. Select 'Connect to a server...' option if you need to connect to the whole server or 'Connect to a site...' if you want to connect to a particular site.
  3. Input the desired host name, access credentials.

  4. If you use self-signed certificate, you will get a warning message expressing concerns on whether this cert may be trusted or not. Be persistent and press 'Connect' button.
  5. After that IIS Manager will suggest to download Helicon.Ape.Editor.dll from the server to make remote Ape management possible. Accept this prompt.

  6. Now you have Ape snap-in for the server/site running locally. And you can manage configuration files (httpd.conf, .htaccess) and licenses (in License Manager) as if working directly on the server.

Summing up it's worth mentioning that this remote management functionality may be particularly useful for shared hosting clients as they get an opportunity to handle their site(s) by themselves without having to bother the server administrator on the slightest occasion.

Best wishes,
Ruslan, Anton - HeliconTech Team

Helicon Ape 3.0.0.29 released

Just wanted to let you know that we have slightly improved Ape 3 and released a new build - 3.0.0.29. The enhancements relate to incorrect snap-in and License Manager behavior in certain situations and address improper installation package actions under specific conditions.

Feel free to download.

Best wishes,
HeliconTech Team

Wednesday, November 11, 2009

Guide: Helicon Ape License Manager

In this article we are going to shed some light on the licensing policy implemented in Ape 3 and tell about its new feature—License Manager.

We'll review each of the possible license types so you could opt for the one that best fits your needs.

To start with, there are two distinct installation packages supporting various license types:
  • Full (including 45-day trial)
    • free licenses
    • per-site licenses
    • server-wide license
  • Free (gratis for up to 3 sites only)
    • free licenses

1. Full version


Free licenses

Ape 3 has obtained a new license type—Free. From now on you can use Ape for up to 3 sites at no cost.
To use Ape on up to 3 sites absolutely free choose Free mode during installation.


After installation process is over, run Helicon Ape Manager and open Help -> License Manager to specify the sites for which free licenses will be used. To do that Per-site licensing policy should be selected. In the list of sites you must tick the sites (up to 3!) you want Ape to work for free for and press "Enable free license" button.


Per-site licenses

If you need more than 3 sites to use Ape, you can either buy individual per-site licenses or (if you want Ape for a bunch of sites) buy a server license (see the next sub-item).

Having bought a per-site license you just run the License Manager, and being in Per-site mode tick the site you want this license for and press "Enable License". You'll be offered to enter the registration data and press "Enable". After that, assuming your credentials are correct, Ape will be enabled for the chosen site.

Server license

If you have a large number of sites to use Ape, it's more appropriate (and economically efficient) to register Ape for entire server. This means all sites on this server will be able to use Ape when properly configured.

To register Ape on entire server select Server License mode in License Manager and enter registration credentials when prompted. Then necessarily press "Apply" button.


Note! If you want to test Ape on your entire server prior to buying it, you may select "45 Day Trial" mode during installation and enjoy it for 45 days period at no cost without functionality limitations.

Note! If you selected "I have a key" licensing option during installation and now have Ape registered for the entire server, transition to Free license mode will no longer be available for you as it just doesn't make sense.



Notice that License Manager is just a handy tool and licenses may also be set manually in Helicon Ape Manager by editing licenses.conf file.

To apply free Ape licenses to 3 specific sites the following directive should be written:
FreeSites id#1 id#100001456 id#789
where the numbers represent sites' IDs in IIS.

To add a per-site license for specific site having ID=1 in IIS the following structure should be used:
<VirtualHost id#1>
RegistrationName= Name
RegistrationCode= Code
</VirtualHost>

The server license is enabled in a similar way but without VirtualHost tags:
RegistrationName= Name
RegistrationCode= Code

2. Free version



Alternatively to installing Helicon Ape Installation Package you may choose Helicon Ape Free Installation Package to use Ape on up to 3 web sites absolutely free without opportunity to by additional per-site or server licenses.

But not to worry, if once you need to use Ape for more sites and want to upgrade, you can do that by clicking "Update to Full version" button in License Manager.


This article was aimed to cover all Helicon Ape licensing capabilities which are rather flexible and let you benefit from using the most appropriate one.

Best wishes,
Anton, HeliconTech Team

Monday, November 9, 2009

Helicon Ape 3 Release

New version of Helicon Ape has recently been released!

It offers:
  • free use on up to 3 sites;
  • 30+ Apache-like modules;
  • admin-free installation on shared hosting;
  • improved performance;
  • redesigned, easier-to-use manager;
  • license manager

Test Ape 3 for free during 45 days.
Looking forward to your feedback.

P.S. New articles on Ape 3 features are coming soon. Stay tuned!

Friday, October 30, 2009

From the inside: ISAPI_Rewrite x64 installation on Windows 2008 Server x64

Installation of ISAPI_Rewrite x64 on Windows 2008 Server x64 may seem a trivial task and it really is of that kind, but nevertheless we'd like to show you the steps installer is making so you could fix possible (though unlikely) problems.

First of all ISAPI_Rewrite installer ensures that ISAPI Filters and ISAPI Extensions components are installed in IIS.

This done installation starts (proper installation package may be downloaded here; it's called ISAPI_Rewrite3_00xx_x64.msi).
Then proxy handlers are registered in Handler Mappings snap-in.

Two records must be added: Helicon Proxy_32 and Helicon Proxy_x64:

After that ISAPI_Rewrite filters are registered in ISAPI Filters snap-in:

You must see these two filters in the list: ISAPI_Rewrite_32 and ISAPI_Rewrite_x64:

Installer also adds ISAPI_Rewrite proxy dlls (both x86 and x64) into the list of ISAPI and CGI restrictions

and marks them as Allowed.

That's all that is done by installer or (in a rare case when it fails) by you:) Now you may test ISAPI_Rewrite operation using this simple rule:
RewriteRule .? – [G]

Save the config and make request to any page on your site. "Gone" result will evidence successful installation:


Now let's turn on 32-bit applications compatibility mode (if you need to).
Click on the Application Pools node in IIS Manager:

And go to Advanced Settings of DefaultAppPool:

Set "Enable 32-Bit Applications" parameter to True:

And test if ISAPI_Rewrite still works with the same rule and URL you used above. The result should be just the same:

We find it quite helpful to know what's happening behind the scenes. And hope you also do.
Take care.

Regards,
HeliconTech Team

Thursday, October 22, 2009

Titbits: ISAPI_Rewrite double registration

Hello!

We have decided to start a series of little titbits about our software. You may find them interesting
and helpful.

Today we're gonna explain you what the “double registration” term means. It's a typical situation on our support when a user can't get ISAPI_Rewrite working while everything seems great, NTFS permissions are OK, the rules are the simplest ever but still no go.

In these cases we commonly ask the user to provide their IIS metabase.
On Windows 2003 Server you may find it here: C:\windows\system32\inetsrv\metabase.xml.
Windows 2008 provides another configuration model and we ask for C:\windows\system32\inetsrv\config\applicationHost.config.

Generally, double registration means simultaneous registration of ISAPI_Rewrite.dll on two different levels. “Web Sites” tree node is what we call “global level”. If you have ISAPI_Rewrite registered here, you will have the tool working for every web-site on your server. Saying “local level” we imply particular web-site.

So the point is you must have only one type of the registration — either on the global level, or on one or several local levels (to enable ISAPI_Rewrite for one or several sites respectively).

Within IIS metabase a double registration issue looks as follows:
<IIsFilter Location ="/LM/W3SVC/1800802984/filters/ISAPI_REWRITE"
  FilterPath="C:\Program Files\Helicon\ISAPI_Rewrite3\ISAPI_Rewrite.dll"
 >
</IIsFilter>

<IIsFilters Location ="/LM/W3SVC/Filters"
  AdminACL="49634462f0000000a400000040000000b171b2f1d344c28255ce51e983b630fed611621d5ecedb78dbe4d4cf30d63e00bb48ac0f5f50c7ecafaf6a3bc3de47b88f801eff2a1c5deda33ad14d7970891db279691971967ed7214857d1b7393ed14cb23e0c248b389f1ad5ebd7b467ef0a0f510a4a967021f12c840c0097ca7e01c449811791c3abf7594c4a61b16498d62dd88d97ac2773ca613785a820f796656421ec2a2780f31897832216525befc0e505582a3377e9928d3ace3b5c59dc00020ee64908c1d1f355776fb12408b349f691ef5761086a5b81869459e2f34e03772da0fb49dc45b8c0d7c1c12c4a252d51e69ce79bb7342d"
  FilterLoadOrder="ASP.NET_2.0.50727.0,ISAPI_Rewrite3"
 >
</IIsFilters>
If you selected automatic installation of ISAPI_Rewrite you would have the tool registered globally. Here is an example:


The next screenshot demonstrates correct local registration, which you can't get from the installation wizard, but should perform manually:


This is it. We've described the very gist of double registration and hope you won't have such misconfiguration on your system.

Yours sincerely,
Helicon Tech team.

Friday, September 4, 2009

From the inside: Installation of ISAPI_Rewrite3 x64 on Windows 2008 Server x64

We've decided to write this article, because sometimes knowing internals of what's happening to your server is beneficial and may save time and nerves.

This story may be used for two purposes:
1) to learn what's happening to your system when ISAPI_Rewrite is being installed;
2) to follow the steps outlined in the article to make sure ISAPI_Rewrite was installed correctly (in case you have any concerns or something is not working as expected).

If you already have strong desire to install ISAPI_Rewrite, firstly, please check if your IIS Server contains all required components, especially those stressed on the picture:
If it's OK, it's high time to download and install the latest build of ISAPI_Rewrite x64 available on our site.
After that make sure ISAPI_Rewrite is registered in IIS. To accomplish this:
  • open IIS Manager
  • open Handler Mappings snap-in
  • Check if required handlers are there
  • open ISAPI Filters snap-in
  • Check if required filters were added (see the pic)
  • Open ISAPI and CGI restrictions snap-in
  • Check if required restrictions were added and set as Allowed
Now launch ISAPI_Rewrite Manager and write the following test rule in httpd.conf:
RewriteRule .? – [G]
Make request to any resource you can think of to check if ISAPI_Rewrite works fine.
If the result resembles the one above (410 Gone page), ISAPI_Rewrite operates correctly.

Now we will turn on 32-bit applications compatibility and check if everything is still working great:
  • open IIS Manager
  • go to Application Pools
  • choose DefaultAppPool and Advanced Settings
  • Set “Enable 32-Bit Applications” parameter to True
  • Now check ISAPI_Rewrite operation once again by making some request in the browser
  • The result should be the same as before (410 Gone). This means that ISAPI_Rewrite works just fine in 32-bit compatibility mode.

We've tried to be as explicit and clear as possible and hope this tour around your server's settings will help you some day.

Regards,
HeliconTech Team