7.0

1. Search profile permissions on the search database
The ReadOnly entry in a search profile controls whether that profile permits updates on its database. You set this entry
to 1 to disable all the rebuild and refresh features available through the PlanetPress Search user interface when that
search profile is loaded. You must open the profile in Windows to edit the ReadOnly entry; you cannot modify it through
the PlanetPress Search user interface.
2. Windows permissions on search profiles
If users have write permission on the file containing the search profile in Windows, they can edit that profile either
through the PlanetPress Search user interface or by opening the file directly.
A user could thus open the file in Windows and edit the ReadOnly entry to permit database updates from that search
profile. They could also modify the file from PlanetPress Search, for example, changing the printer PlanetPress Search
uses when it prints search results from searches accomplished with that profile. Even in an environment where users
are trusted not to edit the ReadOnly entry, it may be preferable to ensure the contents of the search profile do not
change unpredictably.
3. Windows permissions on the search database
Even if the ReadOnly entry is set to prevent database updates and the file containing the search profile is read-only, a
user could create a new search profile that accesses the database, by creating the profile from scratch, or by loading a
search profile that prevents database updates, saving it out under a different name or in a different folder, and editing
the ReadOnly entry to permit database updates. The only way to prevent this is to ensure users cannot write to the
database from outside PlanetPress Search.
Restricting Database Access in a Network Installation
The following illustrates how an administrator might implement the control of search database access, and thereby ensure the
integrity of the searches performed on that database.
1. The administrator takes responsibility for creating all the search profiles available to users, and for placing those pro-
files in a folder accessible to all users.
2. The administrator sets the ReadOnly entry of every search profile they create to 1 to prevent updates of the databases
those profiles reference.
3. The administrator, in the case of search profiles that reference SQL Server databases, ensures the user name and pass-
word set in the connection string permit all users of the search profile to access the database. See "Set User Options"
(page 12), and in particular, the Database access for new profiles option in Search options.
4. The administrator sets the necessary database and/or folder permissions to prevent users from writing to the data-
base, and from editing the search profiles that access those databases.
5. The administrator takes responsibility for performing the necessary refreshes and rebuilds of each database. They
could create a separate profile that permits database updates and that they use when they need to refresh or rebuild a
database, and set up and publish a regular maintenance schedule for the databases so that users know when data-
bases may be undergoing updates.
PDI File Structure
Note that you never edit a PDI file. Examining its contents, however, can be useful in a debugging situation where you want to
verify the values it contains are the ones you expect.
The PDI format described here is in the native format PlanetPress Image generates and PlanetPress Search reads. If you are
examining a PDI file in XML format, you should not have difficulty locating the information described here, in the XML file.
Each entry in the PDI file has the syntax:
~<name>=<value>
For example, the entry:
~FormName=conference.ps4
Advanced Concepts
©2010 Objectif Lune Inc - 42 -