Configuring PASOE for client server for stability.

Configuring PASOE for client server architecture for stability.
Configuring PASOE for remote connections architecture for stability.
PASOE instance is not stable.
PASOE instance is not available.
PASOE keeps crashing.
 

When looking for stability with PASOE, moving the architecture to Client-Server (Remote connections) is one of the most recommended and effective change.
By connecting to databases via Network (and not shared memory) databases continue to run even if any client disconnects while still holding a latch or resource in the database. 
This also allows for quickly scaling up PASOE instances without having to create a larger database machine to handle the extra processing.
Removes other applications and processes from the database machine so they don’t adversely affect the performance of the database.

Please also consider for stability the content of the article, 000102274 Guidelines and best practices for High Availability and Fault Tolerance for an OpenEdge Application.

References to Other Documentation:
Progress Article(s):
 How to monitor PASOE instance via Tomcat Manager?
 Monitoring Progress Resources, PASOE, and WebSpeed