Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

> ## <properties> node

> The `<properties>` node contains a separate node for each parameter that is set and available to the entire session. Any parameters that are set inside the `<properties>` node are available to the session through a call to `getSessionParam` in the Configuration File Manager. Certain of the properties that can be set have a special usage:

> - Most properties prefixed by `session_` map to attributes of the `4GL` `SESSION` system handle. Thus, `session_date_format` specifies the `SESSION:DATE-FORMAT` attribute value. Similarly, `session_year_offset` specifies the `SESSION:YEAR-OFFSET` session attribute value.

> Note: The `session_propath` is the one special case that specifies the value of the session `PROPATH` environment variable.

> - The `startup_procedure` property specifies non-persistent procedures that are executed in alphabetical order after the managers and service connections have been established.

> - Properties prefixed by `ICFCM_ point` at an entry in the `<managers>` node that contains the name of a specific Service Type Manager. For example, in the `icfconfig.xml` file, the `ICFCM_AppServer` property specifies a value of `AppServerConnectionManager`. In the services node, the `cServiceType` property indicates the type of service (AppServer or Database in this example). When the session is started, the Configuration File Manager automatically starts the Connection Manager and all Service Type Managers that are specified by `ICFCM_ properties` so the Connection Manager can connect to all the required startup services. The filename of the Service Type Manager to be started is specified by a `cFileName` node in a `<manager>` node that also contains a `cManagerName` node whose value matches the `ICFCM_ property` value that specifies the Service Type Manager. Thus in the default `icfconfig.xml` file, the `ICFCM_AppServer` property specifies the value `AppServerConnectionManager`, which is also specified by a `cManagerName` node in the `<managers>` node for the same session type. For more information, see the "<managers> node" section.

> - The `run_local` property specifies if the entire environment for the session type runs locally or on an AppServer. If this property is set to `yes`, the local 4GL client session handles all AppServer calls.

> - The `physical_session_list` property provides a list of valid physical session types for a particular Progress Dynamics session (logical session type). Each physical session type identifies a physical Progress session in which the specified logical session type can run. The enumerated list of supported physical session types appears in Table C–1. In other words, there might be more than one valid physical session type that can run the specified Progress Dynamics session. You can determine the current physical session type by a call to `getPhysicalSessionType` in the Configuration File Manager.

> Table C–1: Physical session types
> Physical session type | Description
> --- | ---
> APP | AppServer
> BTC | Batch client
> CUI | Character client
> GUI | Graphical client
> WBC | WebClient
> WBS | WebSpeed Transaction Agent

> - The `valid_os_list` property lists the operating systems that can run the specified Progress Dynamics session. Thus, this property can contain an enumerated list of operating systems identified by the same values as are returned by the Progress 4GL `OPSYS` function.

> You can also add your own properties to the configuration XML file, making them accessible from inside the Progress Dynamics environment using the Configuration File Manager API. For more information, see OpenEdge Development: Progress Dynamics Managers API Reference .

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