...
The default behaviour of the ecflowview GUI client is to access the output file directly (case 1 in Figure 7 2).
When this is not possible, e.g. when the ecflowview GUI host cannot see the relevant file system, the ecFlow server is asked to request the output (case 2 in Figure 7 2). If the output file is large the ecFlow server will supply the last 10000 lines of the output. You can use the following command to get the relevant file associated with a given node:
...
This will output the file to standard output. This capability uses ecFlow to get the file. The original file can be located in a directory that is visible to the ECF, but not to the client.
To view output from a server where the ecFlow server does not have access to the file systems we can use a log server (case 3 in Figure 7 2).
Using ecflowviewthe GUI, you click on the manual, script, output or job buttons. If you configured your ecflowview GUI to retrieve files locally (Edit/preferences/SMS) ecflowview it first looks if the required file is directly accessible. If not, it looks into the suite definition for the variables ECF_LOGHOST and ECF_LOGPORT to retrieve the file from the ecFlow log server. If the log server does not respond it contacts the ecFlow server and retrieves the file from it. This consumes available resources for the ecFlow server, so the log server is useful in reducing ecFlow server load when many users try to get large output files.
Figure 7 2. Accessing job output, using ecflowviewthe GUI.
The log server consists in a Perl script 'logsvr.pl' launched by a shell script. These are available in the ecFlow distribution. The log server uses three variables set by the shell script:
...