Application server checklist

Table 1. Application server implementation recommendations
Recommendation Section Dev Prod Comments
Connection Pool WebLogic connection pool

WebSphere connection pool

JSP tuning: JSP pre-compilation

  C Database connection establishments are very expensive operations. If connection pooling is not enabled in the application servers, transactions from application server does not scale.

The Sterling Selling and Fulfillment Foundation agents are automatically started with a connection pool that is implemented in the agent infrastructure.

Assign each Sterling Selling and Fulfillment Foundation 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

WebSphere 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 weblogic.appc over the use of weblogic.jspc.