Progress
ADM 2 Guide
Managing SmartDataObjects in Distributed Mode
This section describes how to manage Progress SmartDataObjects in a distributed mode, using AppServer.
As described in the "Running SmartDataObjects in a Distributed Environment" section, you can compile a SmartDataObject into database-aware and non-database-aware versions, with sections that contain database references compiled in or out depending on whether the SmartDataObject version will be run client/server, on a client that talks to an AppServer, or on an AppServer.
A SmartDataObject client proxy contains the code needed to connect to an AppServer Broker, to run the complete SmartDataObject on that AppServer, and to send requests through that connection to retrieve and update database records from the database through the AppServer. To enable a SmartDataObject for this use, follow these steps, either before saving the master for a new SmartDataObject from the AppBuilder or when editing the master for an existing SmartDataObject:
Note that this runs all instances of that SmartDataObject on the AppServer. To change this for a single instance, use the SmartDataObject’s Partition instance property. For example, you might do either of the following:
- Set the procedure properties in the SmartDataObject so that all instances except one run on the AppServer, and then set the instance property for that instance to none (that is, it runs locally).
- Leave the procedure property unset in the SmartDataObject so that all instances except one run locally, and set the instance property for that instance to run on the AppServer.
Note that if the AppServer is not known earlier or is variable, you can use the Partition instance property to set it when you assemble the application.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |