Application server checklist
You can review the application server checklist for specific recommendations.
| Recommendation | Section | Dev | Prod | Comments |
|---|---|---|---|---|
| Connection Pool | WebLogic connection pool | C | Database connection establishments are very expensive operations. For performance
and scalability, Sterling Order Management System Software uses
connection pooling in the application servers. The Sterling Order Management System Software agents are automatically started with a connection pool that is implemented in the agent infrastructure. |
|
| Assign each Sterling Order Management System Software agent to its own JMS destination | Dedicated queues | NA | C | For production, dedicated JMS queues are critical for performance. They are also easier to monitor. For ease of configuration and deployment in development, you can continue to use the single DefaultAgentQueue for all agents. |
| Assign integration- based queues to a separate JMS server | Integration queues | NA | C | Put integration-based queues (e.g., queues used to receive orders from an external system) into a separate JMS server especially if the number of messages in that queue could grow to large numbers. |
| Precompile the JSPs | WebLogic tuning: JSP pre-compilation | R | C | The application servers compile JSPs the first time they are
used. The compilation phase can take over 30 seconds which could lead
users to perceive poor user interface response times. Note:
For WebLogic, we recommend the use of |