Deploying with the ToGo Edition
Go Up to Developing and Deploying the InterBase ToGo Edition
To deploy with the ToGo edition, your application needs to find the ToGo DLL on your computer and a directory structure such as the one found in Table 2.1.
At a minimum, InterBase requires the following files to be present for deployment:
| File name and path | File description |
|---|---|
|
<run directory>\InterBase\interbase.msg |
The .msg file contains the messages presented to the user. |
|
<run directory>\InterBase\bin\sanctuarylib.dll |
This licensing file is required by InterBase. |
|
<run directory>\InterBase\license\<ToGo edition license slip file> |
This licensing file is provided to InterBase VARs. |
|
ibtogo.dll |
This file contains the InterBase database engine.You can locate the ibtogo.dll in the application directory, or anywhere in one of the directories included in the PATH. |
|
<run directory>\InterBase\License.txt |
This file contains the InterBase legal license agreement. |
|
<run directory>\InterBase\opensll.txt |
This file contains the OpenSLL legal license agreement. |
|
<run directory>\InterBase\admin.ib |
This file contains an InterBase user name and passwords. InterBase recommends that you use Embedded User Authentication (EUA) with your application, in which case you do not need the admin.ib file. However, if you do not want to use EUA, you must copy your admin.ib to the InterBase sub-directory. For information about using EUA, see the InterBase Operations Guide. |
|
<run directory>\InterBase\intl\gdsintl.dll |
This library supports character sets and is only required if your application uses a database which has a specific character set specified. |