Release 10.1A: OpenEdge Development:
Progress Dynamics Repository Reference

> ## gsm_session_service table — gsmsv

> This table defines the different physical services needed to establish the logical service for each session type.

> Table 13–17 lists the table’s FLA, fields, and foreign keys.

> Table 13–17: gsm_session_service table information
> Table FLA | Fields (data type) | Foreign keys
> --- | --- | ---
> gsmsv | session_service_obj (Decimal) session_type_obj (Decimal) logical_service_obj (Decimal) physical_service_obj (Decimal) | logical_service_obj physical_service_obj session_type_obj

> Table 13–18 gives details of the table’s indexes.

> Table 13–18: gsm_session_service index information
> Index name | Elements | Type
> --- | --- | ---
> XPKgsm_session_service | session_service_obj | Primary Unique
> XAK1gsm_session_service | session_type_obj logical_service_obj | Unique
> XAK2gsm_session_service | logical_service_obj session_type_obj | Unique
> XIE1gsm_session_service | physical_service_obj | Nonunique

> For example, an AppServer might require a shared memory connection to the Repository. However, a client session would require a network connection to the Repository. The physical connection parameters are different for each of these services. The logical service identifies the database that needs to be connected, and the physical service describes the mechanism for the connection dependant on the session type.

> If no session service record exists, then the logical service can only run locally.

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