<div>
Hi Gurvinder,<br />
<br />
Thanks for the reply,<br />
are there any more typical suggestion that anyone could provide.
</div>


Hi Gurvinder,

Thanks for the reply,
are there any more typical suggestion that anyone could provide.

<div>
Closing the issue due to lack of further responses from the forum.
</div>


Closing the issue due to lack of further responses from the forum.

<div>
<div class="content wysiwyg-content">
The application uses -<br />
<br />
Websphere 6.1 clusters with identical clones on nodes,<br />
Websphere MQ thorugh datasources<br />
Oracle database through datasources.<br />
IHS thorugh Websphere plugin.<br />
<br />
Could you please guide me to any primer tuning document (preferably from IBM) that suggests<br />
how the various websphere pools (thread / datasource / plugin etc) should be arranged.<br />
<br />
I faintly remember the concept of pool funnelling where the number of database pool should be less that server thread pool that in turn should be less than server thread pool. The concept was that keep more of the requests outside than bringing them in and making them wait.<br />
<br />
Thanks.
</div>
</div>


The application uses -

Websphere 6.1 clusters with identical clones on nodes,
Websphere MQ thorugh datasources
Oracle database through datasources.
IHS thorugh Websphere plugin.

Could you please guide me to any primer tuning document (preferably from IBM) that suggests
how the various websphere pools (thread / datasource / plugin etc) should be arranged.

I faintly remember the concept of pool funnelling where the number of database pool should be less that server thread pool that in turn should be less than server thread pool. The concept was that keep more of the requests outside than bringing them in and making them wait.

Thanks.

Websphere performance tuning basics

Java application servers that support the Java EE platform and features include JOnAS from Object Web, WildFly (formerly JBoss AS) from JBoss, Geronimo from Apache, TomEE from Apache, Resin Java Application Server from Caucho Technology, Blazix from Desiderata Software, Enhydra Server from Enhydra.org, and GlassFish from Oracle. Commercial Java app servers include WebLogic by Oracle, WebSphere from IBM and the open source JBoss Enterprise Application Platform (JBoss EAP) by Red Hat.

Java App Servers

An application server is a software framework that provides both facilities to create applications and a server environment to run them. Most application server frameworks contain a comprehensive service layer model, acting as a set of components accessible to the software developer through an API defined by the platform itself. For Web applications, these components are usually performed in the same running environment as their web server(s), and their main job is to support the construction of dynamic pages. However, many application servers target much more than just Web page generation: they implement services like clustering, fail-over, and load-balancing.

Application Servers

Java Enterprise Edition (Java EE) is a specification defining a collection of Java-based server and client technologies and how they interoperate. Java EE specifies server and client architectures and uses profiles to define technology sets targeted at specific classes of applications. All Java EE profiles share a set of common features, such as naming and resource injection, packaging rules and security requirements.