Developing Applications for the MicroKernel Engine
This chapter includes information you need to consider when designing your application with PSQL’s MicroKernel Engine. These concepts are discussed in the following sections:
MicroKernel Engine Environment
Before an end user can run your MicroKernel Engine application, a version of MicroKernel Engine must be available to the end user’s computer. You should provide the end user with information about any prerequisite the MicroKernel Engine software versions and configurations that your application requires.
Documentation
End users should have access to the following PSQL documentation:
•Getting Started with PSQL. This manual describes PSQL software installation.
•Status Codes and Messages. This manual describes the status codes and system messages that PSQL components can return.
•PSQL User's Guide. This manual describes PSQL utilities.
If you are a PSQL OEM Partner, you may bundle these documents with your application.
Configuration Issues for MicroKernel Engine
End users may need to know the following information about your MicroKernel Engine application. Include this information in the documentation you provide with your MicroKernel Engine application.
•The amount of memory your application requires.
Your application may require more memory or disk space than the MicroKernel Engine requires on its own. Establish the disk space and memory requirements of your application and communicate this information to your users. For information about system requirements of the MicroKernel Engine, see Getting Started with PSQL and to the PSQL website.
•Whether the application requires the MicroKernel Engine configuration settings other than the defaults. In particular, consider whether end users need to change these MicroKernel Engine options:
•Create File Version. Does your application need backward compatibility with a previous version of the MicroKernel Engine? If so, instruct your end users to set an appropriate value for this option.
•Handles. Does your application need to use more than 60 logical file handles at one time? If so, instruct your end users to set this option to an appropriate value.
•Index Balancing. Does your application set the Index Balancing file attribute on every file it creates? If so, your end users can use the default of Index Balancing turned off. If not, you may need to instruct your end users to turn Index Balancing on at the MicroKernel level. For more information, see
Index Balancing.
•System Data. Do all files in your database have unique keys? If so, the files are transaction durable. If not, your end users may want to set System Data to If Needed or Always in order to make the files transaction durable.
For descriptions of configuration options, see Advanced Operations Guide.