Distributed mode

In distributed mode, the report engine is started as a daemon in listen mode, and report applications connect to this daemon.

To set up your system to run reports in distributed mode:

Place report design documents on the daemon server

Place your report design documents (.4rp) on the server where the GRE daemon runs (the machine where you execute greportwriter). Ensure that all resources (images, schemas, etc.) are on the same server.

Ensure that the fonts, images, and printers required for the reports are available; see Configure fonts and Configure printers.

Start the GRE daemon

Start the GRE daemon in listen mode with the

-l
                        portname

option. The GRE daemon listens on the port specified by the -l option, and for each connection attempts to read an XML document from the socket. For example (on UNIX®):

export FGLRESOURCEPATH=/usr/JohnDoe/TrackOrders/reports/
greportwriter -l 6500

If the Genero Report Engine daemon resides on the same machine as the running report application, or if you are using SSH port forwarding, you can use the -o option. The -o option provides extra security by ensuring that the daemon accepts only local incoming connections. It must be used in conjunction with the -l option. For example:

greportwriter –l 5900 -o

Configure environment variables

If the server running the daemon has different resource paths to the client machine calling the report process, you may need to configure the distributed environment variables.

Connect to the daemon using the reporting API

In the Genero Report Writer APIs, specify the instance of Genero Report Engine that handles the report.

For Java applications, see Java APIs for Distributed Mode.
For .NET applications, see .NET APIs for Distributed Mode.
For PHP applications, see PHP APIs for Distributed Mode.

Set up logging

If the GREDEBUG environment variable is set, the daemon logs messages of the specified level to the file gre.log in the home directory of the user invoking the daemon.

Important:

Sensitive and personal data may be written to the output. Make sure that the log output is written to files that can only be read by application administrators.

You can redirect the log messages to a different file.