7.5
Table Of Contents
- Copyright Information
- Table of Content
- Overview
- Understanding PlanetPress Search
- The PlanetPress Search Program
- Search Profiles And Databases
- Searching in PlanetPress Search
- Advanced Concepts
l (-rebuild|-refresh):Mandatory. Use -rebuild to empty the database and rescan all PDFs in the search folders, or -
refresh to scan for any new PDFs in the search folders and add them to the database.
l ["c:\path\to\profile.prf"]:Optional. Specifies the search profile to be used. If no profile is specified, the default profile
for the currently logged on user (C:\Documents and Settings\lachance\Application Data\Objectif
Lune\PlanetPress Suite 7\PlanetPress Search\ppsearch.prf)will be used.
Example Usage
ppsearch.exe -rebuild "c:\planetpress\searchprofiles\userinvoices.prf"
Notes
l If your database requires a username and password, the credentials set in the PlanetPress Search User Options for the
currently logged on user will be used.
l In order to call ppsearch.exe directly without using the full path, you can add this path in your system. This page
describes how to add to your path variable (it is the same in all versions of Windows).
Database Considerations in a Network Installation
In a standalone installation, PlanetPress Search exists on the local machine and the individual user creates the search profiles
they require. A standalone configuration is common when a single user performs searches. In most circumstances a stand-
alone configuration offers better performance than a network installation. For optimal performance in a standalone con-
figuration, Access databases are recommended.
In a network installation, PlanetPress Search exists on a network and is accessible to the users on that network. A network
installation is common when many users perform searches. SQL Server databases offer the best performance in network
installations.
Database Integrity in a Network Installation
In a network installation, it is common to want to restrict permission to refresh and rebuild a search database to the database
administrator. For example, if any user can refresh or rebuild a database, and one user launches a search just after another
user initiates a rebuild of the database, the first user may unwittingly obtain inaccurate search results.
There are three things an administrator must control to restrict access to the databases PlanetPress Search creates.
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
Advanced Concepts
©2010 Objectif Lune Inc - 42 -