In the majority of cases, development occurs on a Windows desktop with the final release target for UltraLite being the mobile device. However, depending on your deployment environment, you can use various deployment mechanisms to install UltraLite.
UltraLite application projects may evolve with different iterations of the same UltraLite database: a development database, a test database, and a deployed production database. During the lifetime of a deployed database application, changes and improvements are first made in the development database, then propagated to the test database, before finally being distributed to the production database.
Initially installing your UltraLite solution on a device is a required step so that the device can be continuously maintained.
The majority of the benefits and costs are associated with the application being deployed and used in the field. To that end, UltraLite supports includes various mechanisms to deliver applications and synchronize data, both of which are key features in any UltraLite deployment that make UltraLite so flexible.
|Technique||Windows Mobile||Palm OS||Java|
|File transfers||yes||record based and VFS|
|UltraLite as a MobiLink synchronization client||yes||record based and VFS|
|On device file system browsing tool or card reader||VFS only (true)1|
|HotSync||n/a||record based only|
|ALTER DATABASE SCHEMA||yes||yes|
1 You cannot deploy UltraLite databases with the Palm install tool, if the target is a VFS volume. Instead, you need to copy the database directly onto the media using a card reader, or some other tool.
Deploy Multiple UltraLite applications with the UltraLite engine
Deploy UltraLite with AES_FIPS database encryption
Deploy UltraLite with TLS-enabled synchronization
Deploy the UltraLite HotSync conduit
Deploy the ActiveSync provider for UltraLite
Register applications with the ActiveSync Manager
Deploying UltraLite schema upgrades
|Envoyer votre avis sur cette page par email.||Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|