Implementing HCL Z Asset Optimizer with SQLite database

You can implement HCL Z Asset Optimizer with an SQLite database if you do not have a Db2® for z/OS® license, or if you are currently unable to deploy one. If you implement Z Asset Optimizer with an SQLite database, there are certain functional and performance limitations.

SQLite is an in-process library that implements a self-contained, serverless, transactional SQL database engine. It is an embedded SQL database engine that is unlike many other SQL databases, because it does not have a separate server process. SQLite reads and writes data directly to ordinary disk files. When you implement SQLite with Z Asset Optimizer , the complete SQL database is contained within a single z/OS® UNIX® zFS file.

Limitations

Z Asset Optimizer with SQLite database is implemented with the following configuration:
  • 500 products identified from 15 LPARs
  • 3 months usage data (about 6 million usage records)
  • Only 1 repository within a zFS file
This configuration represents the limitation for SQLite support with Z Asset Optimizer . Only one repository within a zFS file is supported. If you require a database with a larger configuration supporting multiple repositories, consider implementing Z Asset Optimizer with Db2® for z/OS®.

SQLite has limited concurrency because it uses read/write locks on the entire database file. Therefore, if any process is reading from any part of the database, all other processes are prevented from writing to any other part of the database. Similarly, if any one process is writing to the database, all other processes are prevented from reading any other part of the database.