Using the AppServer Connect procedure

Developing AppServer Applications

Design and Implementation Considerations : Secondary performance considerations : Connect and disconnect performance issues : Using the AppServer Connect procedure

The AppServer 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 state-free Appserver never executes a Connect procedure.

You might want to perform any of the following activities independently of each other, or in combination with any other items:

Authenticate and authorize based on additional parameters you can pass to the Connect procedure (user-id, password, and/or app-server-info)

For a state-reset or state-aware AppServer, provide security for procedure execution by using the EXPORT( ) method to define the allowed export list for client applications

Note: For a stateless AppServer, you probably want to set the export list in the Startup procedure.

Connect to one or more databases, or to other AppServers on a state-aware or state-reset AppServer

Initiate application-specific audit trails and/or activity logs

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 Securityconsiderations for more information.