Local Update Server: Distributing Protected Applications

To distribute your application, you need create two setup packages. One is the setup for installing the application on the client computers. The other is the setup for installing the Update Server as the local update server.

Creating the Application Setup

To create a setup package and distribute your application, please ensure to include the protected program file and the needed system files as listed below.

         Updshl10.exe (Updater)

         Updshlc.xml (Client Side index file)

         Kcapi.ini (Configuration file)

         \Updshlscr\Inst.bat (Optional script file e.g. Inst.bat)

         Ekc3220.dll (Win32/.NET)

         Ekc6420.dll (Win64/.NET)

The above system files must be placed in the same directory as the protected program file. Note that, if you want to include a setup script for the Updater, you must save it in the subdirectory \Updshlscr.

Creating the Local Update Server Setup

To create a setup package and deploy the Update Server as the local update server, you must include the provided Update Server package (\LocalUpdateServer\PrecompiledWeb\Manager) as a folder (e.g. \LocalUpdateServer). In addition, you must include the Updater and the needed system files as listed below.

         Updshl10.exe (Updater)

         Updshla.xml (Admin index file)

The above system files must be placed in the same directory on the local update server. The Updater on the local update server must be configured as the admin type to subscribe to the software update services. The admin index file is a configuration file for the Updater that stores the URLs of the software update server and the local update server, as well as the location to save the downloaded updates. The format of the admin index file is as follows.

<UpdateShield>

<WebServiceURL>Software update server's web service URL</WebServiceURL>

<LocalWebServiceURL>Local update server's web service URL</LocalWebServiceURL>

<TargetURI>Target URI to save the downloaded upadtes</TargetURI>

<TargetPath>Target path to save the downloaded updates</TargetPath>

</UpdateShield>

Example:

<UpdateShield>

<WebServiceURL>http://demo.eleckey.net/update.asmx</WebServiceURL>

<LocalWebServiceURL>http://hostname/localupdateserver/update.asmx</LocalWebServiceURL>

<TargetURI>http://hostname/localupdateserver/archive</TargetURI>

<TargetPath>c:\localupdateserver\archive</TargetPath>

</UpdateShield>

Since the local update server will be deployed within the corporate network, you will need to advice the administrator to edit the admin index file (UPDSHLA.XML) accordingly.

See Also

         Interfacing the Updater

         Creating a Setup Script

         Building Client Side Index File

         Managing the Software Update Server

         Offering Software Update Subscriptions

         Deploying New Versions for Download

         Deploying the Local Update Server

         Subscribing to the Software Update Service