7.0

Table Of Contents
15.1 Key Concepts
This section covers questions relating to PlanetPress Watch/Server Configuration program and plugin options.
It contains the following topics:
Multiple PlanetPress Suite Installations (Page 252)
PlanetPress Watch/Server Configuration Program and Plugin Options
Service Options Versus Properties (Page 255)
Languages (Page 256)
15.1.1 Multiple PlanetPress Suite Installations
Why would I run components of the PlanetPress Suite on more than one computer?
The basic reason why you may want to run PlanetPress Watch/Server, or any other PlanetPress Suite
component, on more than one computer is to take full advantage of the processing power of your network of
computers. But this call is strictly case by case. Some PlanetPress Suite installations may process hundreds of
inputs and outputs per hour, while other may process hundreds per minute. Naturally, the larger the number
of inputs and outputs, the heavier the load on the hardware, and the more important the need to spread this
load. Possible scenarios range from running a single instance of PlanetPress Watch/Server on a single
computer to running one instance of PlanetPress Watch/Server and its related components on a different
computer to process each input and output type.
In many cases though, a single instance of PlanetPress Watch/Server that sends some outputs to components,
such as PlanetPress Fax and PlanetPress Image, running on other computers will lighten a heavy burden
sufficiently to make everything run efficiently.
Sharing Resources within a LAN
Whenever you install a PlanetPress Suite component on a computer, PlanetPress Suite Messenger is installed
and configured to run continuously. It is this communication component that lets you send PlanetPress Design
documents to various instances of PlanetPress Watch/Server on your LAN, and that lets PlanetPress Watch/
Server send jobs to components running on other computers.
Sharing Resources over the Internet
Since PlanetPress Suite Messenger only enables communication within a LAN, what do you do if you want to
share your processing burden among multiple instances of PlanetPress Watch/Server running on different
networks? If you want a computer running PlanetPress Watch/Server in your main office to send jobs to a
computer running PlanetPress Image in your branch office, for example.
Quite simply, you add an FTP output task to the configuration of the PlanetPress Watch/Server instance
running at your main office, and an FTP input task to the configuration of the PlanetPress Watch/Server
instance running at your branch office. The output task will thus use the Internet to send the job to an FTP
server, from which the input task will get it and hand it down to a PlanetPress Image output task. The
following illustration shows just this. As you can see there is an action task on Computer 1 that renames the
file before the output task places it on the FTP server. This is so that jobs coming from different computers
can be identified on Computer 2.
Objectif Lune Inc. © 2009 252