Use the steps in this topic to improve your WebSphere® Sensor Events database
performance.
Note: If you have installed IBM® Location Awareness Services for WebSphere Sensor Events, the
default installation can support small scenarios, using between 100
and 200 tags. To use IBM Location Awareness Services for WebSphere Sensor Events in
a production environment or to use it with more tags, tune your ATLASDB
database for additional buffer pools, and add more hard drives to
avoid bottlenecks.
Tuning DB2 Workgroup Server Edition
To
tune your WebSphere Sensor Events DB2® database, you can either run
a script or issue the commands from the DB2 command
line.
If you are using a local DB2 database,
use the scripts provided on the DVDs. The scripts are located in these
paths:
Before installation:
On the second WebSphere Sensor Events installation
disk: db_script\performance_tuning_db2.bat
On the second WebSphere Sensor Events installation
disk: db_script/performance_tuning_db2.sh
After installation:
IBM_RFID_HOME\premises\install\db\performance_tuning_db2.bat
IBM_RFID_HOME/premises/install/db/performance_tuning_db2.sh
If you have a remote DB2 database,
you may prefer to run the commands from the DB2 command line:
db2 connect to IBMRFID
db2 update database configuration using locklist 50000 immediate
db2 update database configuration using maxlocks 95 immediate
db2 update database configuration using maxappls 75 immediate
db2 update database configuration using avg_appls 40 immediate
db2 alter bufferpool IBMDEFAULTBP immediate size 20000