You must coordinate the tuning of these server jobs with the tuning of the WebSphere datasources. For the moment, we assume a simple default WebSphere setup:
Only one instance of WebSphere is running.
Only one application (for example, call.connect) is running.
The datasource used by that application has not been modified.
There is only a small number of users.
As mentioned earlier, the WebSphere administration job uses five connections. The default datasource has a minimum size of 1 and a maximum size of 10.
One call.connect client commonly use two connections and occasionally use three connections. This way even a few users may reach this maximum.
One vendor.connect Web session uses one or occasionally two connections. However, the pooling performed by WebSphere means that unless the clients are extremely busy, the number of connections will be significantly less than the number of clients. If the maximum is likely to be reached, we recommend that your number of prestarted jobs is at least as large. For this discussion, we assume that there are 15 connections. The Display Prestart Job Entry Detail for this program would be:
Start jobs: *YES
Initial number of jobs: 20
Threshold: 2
Addition number of jobs: 2
Maximum number of jobs: *NOMAX
If other Java applications are running on the iSeries that use the native JDBC driver, you must allow for them as well. To make this change, follow these steps:
1.Sign on as QSECOFR.
2.Ensure that WebSphere is not running.
3.Ensure that no other Java applications are using native JDBC connections.
4.End the prestart jobs by using the following command:
ENDPJ SBS(QSYSWRK) PGM(QSQSRVR)
If no server jobs are running, then you receive the error message “End Prestart Jobs command is not currently allowed”. You can ignore this message.
5.Change the server settings with this command:
CHGPJE SBSD(QSYSWRK) PGM(QSQSRVR) STRJOBS(*YES) INLJOBS(20) THRESHOLD(2) ADLJOBS(2) MAXJOBS(*NOMAX)
6.Restart the prestart jobs:
STRPJ SBS(QSYSWRK) PGM(QSQSRVR)
7.Restart WebSphere and your application.
It is possible to view the server jobs in several ways. Look at the QSYSWRK subsystem:
WRKACTJOB SBS(QSYSWRK)
The results also show many other server jobs. Instead you can select a specific job name by using the following command:
WRKACTJOB JOB(QSQSRVR)
In either case, you may find fewer jobs than you expect. If you check when WebSphere is not active, then you may find none. This is because the Work with Active Jobs (WRKACTJOB)
112Geac System21 commerce.connect: Implementation on the iSeries Server
