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

> ## Overview

> The Connection and Service Type Managers work together to establish and maintain connections to services in the Progress Dynamics environment, such as AppServers and databases. The Connection Manager uses the Service Type Manager for a service type as a device driver to handle the details of connections to all services of that type. All these managers run on the server-side of the environment.

> At session start, the Configuration File Manager retrieves the session type data from the configuration file. The Connection Manager is always the next manager started. After it has started, any necessary Service Type Managers start. The precedence for starting the Service Type Managers is generally AppServer, Database, and then any other.

> You can retrieve the handle of these Managers by running code like the following example for the Connection Manager:

>     ASSIGN hConnectionManager =
>     DYNAMIC-FUNCTION("getManagerHandle":U, INPUT "ConnectionManager":U).

> Table 2–1 shows the files that contain the Connection Manager’s code.

> Table 2–1: Connection Manager files
> Type | Path
> --- | ---
> Client-side wrapper | NA
> Server-side wrapper | NA
> Main code |
>     af\app\afconmgrp.p
> Included files |
>     af\sup2\afglobals.i
>     af\app\afconttdef.i

> The Progress Dynamics framework comes with prebuilt Service Type Managers for AppServers, databases, and Web services. In the configuration file, these managers are referred to as the AppServer Connection Manager, Database Connection Manager, and WebService Connection Manager.

> You can also create custom Service Type Managers to handle other services. You can find a template for new Service Type Managers in `af\app\afsvrconmgrp.p.`

> Table 2–2 shows the files that contain the AppServer Connection Manager’s code.

> Table 2–2: AppServer Connection Manager files
> Type | Path
> --- | ---
> Client-side wrapper | NA
> Server-side wrapper | NA
> Main code |
>     af\app\afasconmgrp.p
> Included files |
>     adecomm\_adetool.i
>     adecomm\appsrvtt.i
>     af\sup2\aficfcheck.i
>     af\sup2\afsrvtype.i
> Other important files |
>     af\app\afservicetype.p

> Table 2–3 shows the files that contain the Database Connection Manager’s code.

> Table 2–3: Database Connection Manager files
> Type | Path
> --- | ---
> Client-side wrapper | NA
> Server-side wrapper | NA
> Main code |
>     af\app\afdbconmgrp.p
> Included files |
>     af\sup2\aficfcheck.i
>     af\sup2\afsrvtype.i
> Other important files |
>     af\app\afservicetype.p

> Table 2–4 shows the files that contain the WebService Connection Manager’s code.

> Table 2–4: WebService Service Type Manager files
> Type | Path
> --- | ---
> Client-side wrapper | NA
> Server-side wrapper | NA
> Main code |
>     af\app\afwebconmgrp.p
> Included files |
>     af\sup2\afsrvtype.i
> Other important files |
>     af\app\afservicetype.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