7.5

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 15), 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
has the name FormName and the value conference.ps4. A PDI file uses the following entries:
Name: Value:
~SearchDBName
The name you defined in PlanetPress for the database record for the document. This is the name of the rec-
ord PlanetPress Search creates for this document in any search database it builds that contains the doc-
ument. If you did not define a name for the database record, PlanetPress Image sets this entry to the value
of the
~FormName
entry. This is the name you see in the Document box when you set up a search.
~FormName
The name of the converted document (in your PlanetPress Suite Workflow Tool Documents folder) that Plan-
etPress Image executed to generate this PDI and its associated PDF.
PlanetPress Search uses the value of this entry to determine which of the PDF files in a PlanetPress Image
archive folder were generated from the same document. If you did not define a name for the database rec-
ord for this document (see the
~SearchDBName
description), it also uses this value as the name of the record it
creates for this document in any search database it builds that contains the document. For example, consider
two PDI files, report1.pdi and report2.pdi. Neither of these documents had a name defined for their data-
base record during document design in PlanetPress. Both of their FormName entries have the value
report.ps4. In this case, PlanetPress Search would create a database record called report and include the
Advanced Concepts
©2010 Objectif Lune Inc - 43 -