Using the PAS for OpenEdge Server Connect procedure
The PAS for OpenEdge Connect procedure provides a convenient place to perform connection activities. Although these connection activities have value for a variety of reasons, be aware that using these could, to various extents, affect your overall connection performance.
Note: A client connection using the session-free application model never executes a Connect procedure. To perform initial application tasks that apply to all session-free clients of a PAS for OpenEdge instance, you must use the Multi-session or Session Startup procedure, as appropriate.
You might want to perform any of the following activities independently of each other, or in combination with any other items:
Authenticate and authorize access to PAS for OpenEdge resources based on additional parameters you can pass to the Connect procedure (user-id, password, and/or app-server-info)
For a session-managed application, provide security for procedure execution by using the EXPORT( ) method to define the allowed export list for client applications
Note: For a session-free application, you must set the export list in the Session Startup procedure.
Connect to one or more databases, or to the other OpenEdge application servers
Note: To make a self-service database connection for a PAS for OpenEdge instance, you must use the Multi-session Startup procedure.
It might be difficult to predict exact connection speed and the effects of using any, all, or some combination of these options. However, in general, each of these options has some overhead. Although none of these options are required, you might want to consider them as part of your security model. See Security considerations for more information.
Authenticate and authorize access to PAS for OpenEdge resources based on additional parameters you can pass to the Connect procedure (user-id, password, and/or app-server-info)