<?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>AutoUpdater</title> <meta name="keywords" content="omnis studio, autoupdater documentation" /> <link rel="stylesheet" type="text/css" href="http://www.studiotips.net/css/codedoc.css" /> <link rel="stylesheet" type="text/css" media="print" href="http://www.studiotips.net/css/codedoc_print.css" /> </head> <body> <div id="container"> <p><a href = ../index.html > Autoupdater </a> &nbsp &gt; &nbsp <a href = index.html > About </a> &nbsp &gt; &nbsp AutoUpdater</p> <a name="autoupdater" /> <h2>AutoUpdater</h2> <p>AutoUpdater is a utility can be implemented for any Omnis Studio application. AutoUpdater can be used by developers to simplify and automate the process of updating runtime clients with newer release files of any Omnis Studio application which the developer creates.</p> <p>AutoUpdater is a single Omnis Studio library. The AutoUpdater library is unlocked. All of the AutoUpdater code is good old Omnis Studio code which developers can read, step through, and if necessary debug.</p> <p>AutoUpdater supports serving newer release files on:</p> <ol> <li><strong>FTP</strong> - any FTP server accessible by the runtime clients.</li> <li><strong>DB</strong> - any database accessible by the runtime clients.</li> <li><strong>LAN</strong> - any mountable drive accessible by the runtime clients on a local area network. (This is the least recommended approach)</li> </ol> <p>Runtime clients can specifiy:</p> <ol> <li>Release type of <em>Final</em> or <em>Beta</em> and switch back and forth at any time.</li> <li>Update frequency of <em>Manual</em> or <em>On Launch</em>.</li> <li><em>Prompt before Installing Updates</em> or automatically download and install newer releases.</li> </ol> <p>Developers can specify:</p> <ol> <li><em>Expiry Date</em> - after which period the runtime client must obtain an new AutoUpdater library from the developer in order to be able to download new updates.</li> <li><em>Server Type</em> (<span class="code">FTP, DB, LAN</span>), and the address, user name and password. The user name and password are not accessible by the runtime clients.</li> <li><em>Package(s)</em> to be included with the application. Each package specifies the files included in the package.</li> </ol> <p>Developers upload files to their AutoUpdater files server and prepare an AutoUpdater library for their specific application and client. The AutoUpdater library is shipped to the runtime client. When the AutoUpdater library is opened it immediately downloads and installs the packages and files included with the application and then opens the application.</p> Newer release files are uploaded to the files server by the developer. The runtime client AutoUpdater library checks the file server for new updates and if found, downloads and installs the newer version files on the client's computer. <a name="aboutthismanual" /> <h3>About this Manual</h3> <p>This manual begins with a <span class="nav">QuickStart Tutorial</span> which will take you through the basics of setting up <span class="nav">AutoUpdater</span> to work with your Omnis Studio application.</p> The more detailed documentation is after the <span class="nav">Quickstart Tutorial</span>. You should scan through the <span class="nav">AutoUpdater Documentation</span> after you complete the <span class="nav">Quickstart Tutorial</span> to get a deeper understanding of AutoUpdater and to learn about the advanced features of AutoUpdater. <p class="footer">AutoUpdater Documentation - Copyright 2006 Vencor Software </p></div> </body> </html>