The personalization APIs map name/value pairs to a unique set of UID, PID, and TID. The names and values are saved as strings. Using the personalization APIs, users can add, retrieve, and delete entries from the database. The personalization APIs use a JDBC connection—the data source, user name and password values are saved in the personalization.properties file.
The personalization APIs expect non-null UID, PID, and TID values; built-in triggers check for null values. Names and values are not validated. The developer must verify that names and values are correct and not duplicated. If you attempt to enter a name that already exists, the existing entry is updated.
