Consultor Eletrônico

Status: Unverified

GOAL:

Is there any sample code demonstrating the use of temp-table based SDOs on a stateless AppServer?

FIX:

Progress does not provide such sample code. However, one way of deploying temp-table based SDOs on a stateless AppServer is to ensure the temp-table is managed on the client-side is by pulling the entire SDO to the client. Following are general guidelines that may be used to implement such a solution:

1. Define an extra AppServer partition using the Service Parameter Maintenance.
2. Set the configuration for this partition to "Local".
3. Set the SDO to use this local AppServer partition by default using its Procedure Settings.
4. Include the full SDO in the client deployment package.
5. Modify the SDO to populate the temp-table and process any modifications.
6. To (re)populate the temp-table from a database, call a procedure that can access that database.
7. Depending on when/how often you need the temp-table to be populated / refreshed, this call would be in an override of initializeObject or openQuery(), before the RUN SUPER.
8. The call itself can be a call to another SDO, or it can be a remote procedure call to an AppServer (which in turn can be a stub procedure to an SDO running solely on the AppServer).
9. For AppServer side processing of updates to the temp-table similar techniques can be used. In this case the call to the AppServer would be placed in endTransactionValidate or possibly postTransactionValidate.
10. The best way to run the logic that populates the temp-table and processes any modifications made to it depends on the application-specific needs.