![]() |
Deploying Synchronized Systems
|
|
Distributing Application Code Within the DatabaseYou can use Cloudsync to distribute application code and code changes to targets. To do this:
The target you create with this publication will function just as if the application class files were deployed at the target. Additionally, changes to the published jar files at the source are automatically reproduced at the target when it refreshes, eliminating the need for local administration. Example of Jar Files in a DatabaseTo illustrate including source and target application code in the database, consider the application described in Chapter 7, "Designing Synchronized Applications". The following example shows how to put that application's work units directly into source and target databases rather than external files. (Note that you could do exactly the same thing for application code other than work units.) This example assumes you have already created the system described in Chapter 7, "Designing Synchronized Applications". (For more information on putting code into the database, see the Cloudscape Developer's Guide.)
The targets you create with these copy files will be able to call work units and perform refreshes exactly like the application described in Chapter 7, "Designing Synchronized Applications", but without any accompanying code outside the database. If target work unit code stored in the source database is later changed, the changes will automatically be distributed to the targets when they refresh. See the Cloudscape Developer's Guide for information on using DBClassLoad load a an application from the database. |
|
![]() Cloudscape Version 3.6 For information about Cloudscape technical support, go to: www.cloudscape.com/support/.Copyright © 1998, 1999, 2000 Informix Software, Inc. All rights reserved. |