Release 10.1A: OpenEdge Development:
Progress Dynamics Managers API Reference

> ## Overview

> The Repository Managers encapsulate all Repository-based access for building dynamic objects in the Progress Dynamics environment. They are used to access the data for the user interface (UI) and the objects that make up an application. The Managers coordinate the moving and caching of data between the Repository and a calling procedure. Examples of the Repository data transported include such items as object property (attribute) values, toolbar bands, and toolbar actions.

> There are two Repository Managers, one that handles development tasks and another to handle run-time tasks. The Repository Manager handles data transport for running applications. It is designed to efficiently return object definitions to applications at run time. The Repository Design Manager manages Repository access during application development tasks. It is designed to efficiently work with the AppBuilder, the Object Generator, and the other tools you use to create a Progress Dynamics application.

> In a distributed environment, the Repository Managers are started on both the client and server sides. There is a wrapper program for each side that sets the global variable, `server-side`, to either `YES` for the server-side version or `NO` for the client-side version. Each program then includes the main code of the manager from the appropriate include file. The differences in how the managers operate on each side are triggered by checking the value of the `server-side` variable.

> The Repository Manager’s handle is stored in the global shared variable, `gshRepositoryManager`.

> You can retrieve the handle of the Repository Design Manager by running code like the following example:

>     ASSIGN hRepositoryDesignManager =
>     DYNAMIC-FUNCTION("getManagerHandle":U, INPUT "RepositoryDesignManager":U).

> Table 8–1 shows the files that contain the Repository Manager’s code.

> Table 8–1: Repository Manager files
> Type | Path
> --- | ---
> Client-side wrapper |
>     ry\app\ryrepclntp
> Server-side wrapper |
>     ry\app\ryrepsrvrp.p
> Main code |
>     ry\app\ryrepmngrp.i
> Included files |
>     adm2\calltables.i
>     adm2\ttaction.i
>     adm2\tttoolbar.i
>     af\app\afdatatypi.i
>     af\app\afttsecurityctrl.i
>     af\app\aftttranslate.i
>     af\sup2\aferrortxt.i
>     af\sup2\afglobals.i
>     ry\app\rydefrescd.i
>     ry\app\rygetitemp.p
>     ry\app\rygetmensp.p
>     ry\app\rymenufunc.i
>     ry\inc\ryattstori.i
>     ry\inc\getobjecti.i
>     ry\inc\ryrepatset.i
>     ry\inc\ryrepdoori.i
>     ry\inc\ryrepgeidi.i

> Table 8–2 shows the files that contain the Repository Design Manager’s code.

> Table 8–2: Repository Design Manager files
> Type | Path
> --- | ---
> Client-side wrapper |
>     ry\app\rydesclntp.p
> Server-side wrapper |
>     ry\app\rydessrvrp.p
> Main code |
>     ry\app\rydesmngrp.i
> Included files |
>     adm2\calltables.i
>     adm2\globals.i
>     af\app\afdatatypi.i
>     af\sup2\afcheckerr.i
>     af\sup2\aferrortxt.i
>     ry\app\rydefrescd.i
>     ry\inc\rydestdefi.i
>     ry\inc\ryrepatset.i
>     ry\inc\ryreplnset.i
> Other important files |
>     ry\app\rygenomngp.p

> For more information on these Managers, see the chapter on using the Progress Dynamics Managers in OpenEdge Development: Progress Dynamics Advanced Development .

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095