Cache settings - Advanced

NOTE: WinGate 7 only. WinGate 8 uses a proprietary cache index system.

The Advanced tab on the Cache settings configuration, allows you to specify an alternative System DSN you can use to connect to a index database of your choice. The database can store the indexed locations of where cache is stored on the volume being used by WinGate.

By default the HTTP Cache module will create a index database called WinGate Cache using the Microsoft Jet Engine (Microsoft Access driver). Using a default volume store, the HTTP Cache can begin to index and store cached files without further configuration after it is installed.

Creating an alternative index database:

1. Select the DBMS (Database management server/system) you will use.
2. On the DBMS, create an empty database.
3. Name the new database with an appropriate name (e.g. wg_cache). Don’t add any tables to the database, the HTTP Cache module will create the tables and indexes it needs when it connects to the database for the first time.
4. On the WinGate server install the appropriate ODBC driver that it can use to connect to the DBMS.
5. On the WinGate server set up a System DSN in the Windows ODBC configuration that will be used to connect to the DBMS . If you’re on a 64bit OS, you must use the 32 bit version of the ODBC manager (in Windows\SysWOW64). Choose the driver for the DBMS you installed in step 4. Give the DSN a name and configure it to connect to the database you created.

Setting the HTTP Cache to use an alternative System DSN:

1. Open the WinGate Management console.
2. Navigate to Control Panel > HTTP Cache.
3. On the HTTP Cache Panel right click and select Cache settings to open up the Cache settings configuration.
4. Select the Advanced tab.

   

   Close

5. To the right of the System DSN field, click on the Select button, and select the System DSN that will connect the HTTP Cache to the correct database (As described in the Creating an alternative database index section above).
6. Click OK to exit the Cache settings configuration.
7. Restart the WinGate engine for the changes to be applied.

Once WinGate is restarted, the HTTP cache module should create 2 tables, cache_index, and cache_folders. If it has difficulty creating these tables an error log will be written which will be visible in WinGate Management console > Control Panel > Logging.

Note