7.0

5.1 Multiple Sample Data Files
A single PlanetPress Watch/Server configuration can incorporate multiple “data streams”. What this means is
that a single configuration can receive differently structured data files from various sources and that it can
send those data files to various PlanetPress Design documents.
You can structure your configuration in various ways, but you should remember that a given PlanetPress
Watch/Server process can only have a single initial input task, and that a given PlanetPress Watch/Server
output task can only send data to PlanetPress Design documents that share the same data structure.
• If your configuration is only going to receive data files that share the same structure from a single
source type (serial inputs, for instance), it will typically include a single process. Since your process is
only going to send data to various PlanetPress Design documents that were created using sample data
files that share the same structure, it can include a single output task.
• If your configuration is going to receive data files that do not share the same structure from a single
source type (serial inputs, for instance), it will also typically include a single process. Since your process
is going to send data to PlanetPress Design documents that were created using sample data files that do
not share the same structure, it must include multiple output tasks.
• If your configuration is going to receive data files from multiple source types (ftp and serial inputs, for
example), it will necessarily include multiple processes.If your processes are only going to send data to
PlanetPress Design documents that were created using sample data files that share the same structure,
they can each include a single output task. If, on the other hand, they are going to send data to
PlanetPress Design documents that were created using sample data files that do not share the same
structure, they will each typically include multiple output tasks.
Note that there are many reasons why you may want to add additional processes and output tasks to a given
configuration. Schedule considerations are a good example. You may, for instance, need a process that runs
24 hours a day to capture incoming data on the spot, and another process that runs at night and that picks up
data generated by the first for additional processing.
A process that sends data to PlanetPress Design documents that do not share the same data structure needs
condition tasks, so as to be able to route each data file to the appropriate document. To edit and test such a
process, you will also need to use multiple sample data files. To create and edit those branches that lead to
PlanetPress Design documents that share the same data structure, you will choose a first sample data file.
Then to create and edit other branches leading to PlanetPress Design documents with a different data
structure, you will choose a second sample data file, and so on. Bear in mind that each sample data file is
associated with a given process, so to change the sample data file associated with a given process, you must
first select this process.
What all this translates into is that to plan out the structure of your configuration, you should typically begin
by listing all your inputs, outputs and PlanetPress Design documents, and you should then draw up a flowchart
to visually assemble them all. You should then add the additional input tasks and the action action tasks
needed to complete your whole configuration. This will tell you more surely then anything whether you need a
single process or multiple processes.
Objectif Lune Inc. © 2009 116