Filter
Top Products
124 Geac System21 commerce.connect: Implementation on the iSeries Server
Figure 5-17 The DataSource panel Advanced page of the WebSphere console
5.3.3 Total connections and SQL server jobs
If you estimated the number of stateful and stateless connections required by your
applications, then you can easily estimate the total number of connections. You should add
these two and the five connections used by the WebSphere administration server job
QEJBADMIN. If you are using multiple applications (for example, call.connect and
vendor.connect in different pools), then you should also add them. If you are running multiple
instances, then count each separately and then add them together. Each instance has its own
administration server job and, therefore, five connections.
It is important that sufficient SQL server jobs are available for these connections. See 5.2.1,
“SQL server job configuration” on page 109. If WebSphere attempts to use more connections
than the number of prestarted SQL server jobs, then performance may be poor.
Any time you adjust the size of your WebSphere connection pools, review the configuration of
your SQL server jobs. Remember that if you have other applications that use these server
jobs, then you should include them in the calculation of the number of server jobs required.
The normal server QSQSRVR jobs are only used by JDBC connections using the native
JDBC driver. Therefore, if do not have any other Java applications on your iSeries, then no
other applications are using these jobs. If you are using the Toolbox driver QZDASOINIT,
remember that Java applications running elsewhere and ODBC clients may use it.
5.4 Performance topics for Java virtual machine (JVM) settings
This section discusses performance-related topics regarding to JVM settings. You can specify
command line parameters for the application’s JVM using the WebSphere console. Simply
select the application and then select the General tab.