The command ecFlowexecutable ecflow_server is used to start an ecFlowecflow_server using the default port number or that defined by the variable environment variable ECF_PORT.
Code Block |
---|
cd ECF_dir1 nohup ecflow_server & # start ecFlow with default port3141port 3141 |
Multiple ECFs can be run on the same host using different port numbers. There are two mechanisms for specify specifying the port number:
- Using arguments on the command line. i.e. ecflow_server --port=3141
- Using the Environment variable. ECF_PORT
...
Code Block |
---|
cd ../ECF_dir2 ecflow_server –-port=3142& # start ecFlow with port number 3142 cd ../ECF_dir3 export ECF_PORT=3143 ecflow_server & # starts ecFlow with port number of 3143 |
Note: the ECFs are started in different directories so that the output and checkpoint files are not overwritten
Adding a new server to ecflowview ecflow_ui adds the definition to the file ~/.ecflowviewecflowrc/servers. This can be modified directly.
You cannot start two ecFlow servers on the same machine with the same port number. To simplify users wanting their own ecFlow servers we have a script ecflow_start.sh(an example is included in the latest releases of ECF) that sets up an ecFlow server using a port number based on the users own unique user ID
...
Figure 7 1 Viewing new ECFLOW servers with ecflowview.ecflow_ui
When using non-default ecFlow servers, ecflowview ecflow_ui needs to be configured to recognise the port used. Opening the edit-preferences under ecflowview ecflow_ui and selecting the servers tab you can describe your new ecFlow server to ecflowviewecflow_ui.
Adding a new server to ecflowview ecflow_ui adds the definition to the file ~/.xecfrc/servers. This can be modified directly.
It is a good idea to use a start up startup script that automatically sets up a unique port number.