The instructions as explained in Chapter 2, A first encounter work on a system where Flumotion is not integrated. You are responsible yourself for providing a working configuration file, and starting the binaries.

Alternatively, we have also provided a service-like script called flumotion that provides some basic integration, much like a standard service script. This script is installed in your sbin directory. You can list managers and workers configured, and start and stop them.

In a well-configured system, Flumotion is integrated into the system using Unix service scripts. In this section, we use the Fedora Core installation of Flumotion as an example. Depending on your distribution, these instructions might slightly vary.

To start flumotion with the service scripts, you start it like any other service, by typing as root:

service flumotion start

which results in:

Starting manager default:                                  [  OK  ]
Starting worker default:                                   [  OK  ]

Configuration files for flumotion are stored under /etc/flumotion/. In that directory, there is one subdirectory for managers and one for workers. Under each of these, there is one directory with the name of the manager or worker, containing the relevant configuration information.

Typically, the managers directory contains a planet.xml file detailing general configuration for the manager, and a flows/ subdirectory containing all flows that should be loaded onto this manager.

One of the most powerful features of Flumotion is its ability to run distributed over many seperate computers. In this section, we cover basic configuration instructions for Flumotion in this mode.

By default, the installation of Flumotion only allows connections to the manager from the local host, for security reasons. If you want to allow other hosts to log in workers or administration clients, you should change the authentication settings and remove the host entry from planet.xml.

For a production setup the best way to configure the Flumotion workers to log into a remote host is by adding the needed configuration for it in the default.xml file found in /etc/flumotion/workers. When configured for remote connections this file will look something like this:

<worker>
     <manager>
	<host>stream.test.com</host>
	<port>7531</port>
  </manager>

  <authentication type="plaintext">
    <username>user</username>
    <password>test</password>
  </authentication>

	</worker>

In this example we have used stream.test.com as the example remote server where you are running your manager and we are using the default Flumotion SSL port of 7531.

You could also connect the worker directly from the command line by using this syntax:

flumotion-worker -H stream.test.com -P 7531 -u user -p test

You can get more information on these and other command line parameters by reading the flumotion-worker manpage (type man flumotion-worker) or by running flumotion-worker -h on the command line.