...

By default, Partek Flow is installed under /opt/partek_flow and temporary files are housed in /opt/partek_flow/temp.

The installation procedure varies per Linux distribution. To check your distribution, open a terminal and run:
$ cat /etc/issue

...

1. Add the public key for the Partek package repository*
   $ sudo apt-key adv --keyserver keys.gnupg.net --recv-keys C82B61BF
   
   
2. Add the Partek package list to your repository*
   $ sudo wget -P /etc/apt/sources.list.d/{+}http://packages.partek.com/debian/partek-flow.list+http://packages.partek.com/debian/partek-flow.list
   *Steps 1 and 2 only need to be performed once prior to the first installation. Re-installation and updates do not require this step.
   
   
3. Update the list of available packages
   $ sudo apt-get update
   
   
4. Install Partek Flow
   $ sudo apt-get install partekflow
   When asked to continue, type the letter Y and press Enter.
   During the installation, you will be prompted for the Flow server port (Figure 1). Unless necessary, accept the default HTTP port: 8080 by pressing Enter.
   
   
   Figure 1: Configuring HTTP port for Partek Flow during installation
   
   
5. If additional configuration is needed, use the reconfigure command below. This can be run any time after Partek Flow is installed. For details regarding each setting, contact the Partek Licensing Department. In most cases, this step can be skipped.
   $ sudo dpkg-reconfigure partekflow
   
   
6. (Optional) To manually configure Partek Flow or to set additional advanced options or environment variables, edit the following configuration file:
   /etc/partekflow.conf
   Note that all changes made by the reconfigure command in step 5 are also stored in this configuration file.
   
   
7. Start the Partek Flow server
   $ sudo service partekflowd start
   A message should indicate that Partek Flow is now running:Starting Partek Flow server: OK
   Step 7 needs to be performed only once after installation. Partek Flow will start automatically whenever the server restarts.

...

1. Retrieve the Partek yum repo configuration
   $ sudo wget -P /etc/yum.repos.d
   {+}http://packages.partek.com/redhat/stable/partekflow.repo+http://packages.partek.com/redhat/stable/partekflow.repo
   Step 1 needs to be performed only once prior to the first installation. Re-installation and updates do not require this step.
   
   
2. Install Partek Flow
   $ sudo yum install partekflowXXX
   
   
3. When asked to continue, type the letter Y and press Enter
   
   
4. (Optional) To manually configure Partek Flow or to set additional advanced options or environment variables, edit the file located at:
   /etc/partekflow.conf
   
   
5. Start the Partek Flow server
   $ sudo service partekflowd restart
   The following message indicates that Partek Flow is now running:Starting Partek Flow server: OK
   Step 5 needs to be performed only once after installation. Partek Flow will start automatically whenever a server restarts.

...

1. Open a Linux terminal as a non-root user in that user's home directory.
   
   
2. Download the Partek FlexNet 11.12 distribution. Versions of FlexNet downloaded from other locations will not work as they do not contain the Partek vendor daemon (parteklm).
   $ cd
   *_$ wget http://www.partek.com/~devel/FlexNet/FlexNet11.12.zip_*
   $ unzip FlexNet11.12.zip
   
   
3. Obtain the license key from Partek. Save it in the home directory as license.dat.
   If you have not received the license.dat file, contact your Account Manager or email licensing@partek.com.
   
   
4. Determine if your linux workstation is 32 or 64-bit.
   
   
5. Start the license server.
   If you are on a 64-bit workstation (most-likely):
   $ ~/FlexNet/linux64/lmgrd -c ~/license.dat -l ~/flexlog.txt
   If you are on a 32-bit workstation:
   $ ~/FlexNet/linux32/lmgrd -c ~/license.dat -l ~/flexlog.txt
   
   
6. Verify the licensing server is running and offering features: flow_base, flow_hpc_nodes, and flow_hpc_cores:
   $ ~/FlexNet/linux64/lmutil lmstat -a (64-bit)
   $ ~/FlexNet/linux32/lmutil lmstat -a (32-bit)

...

1. Change to the user account that runs Partek Flow. Suppose it is user account flow, then:
   $ su flow
   
   
2. Then the default home directory should be/home/flow. Run the following command to make the backup database in home/flow directory, the archived file name is flowdbbackup.tar.gz:
   $ tar -czvf flowdbbackup.tar.gz .partekflow/
   
   
3. Log out of the user account that runs Flow:
   Ctrl+D

...

1. Shutdown Flow
   # service partekflowd stop
   
   
2. For this example we will use the new temporary folder location of /home/flow/partek_flow/temp. Adjust this path to meet your needs.
   
   
3. Open the configuration file /etc/partekflow.conf and append the following line to the end of the file:
   CATALINA_TMPDIR=/home/flow/partek_flow/temp
   
   
4. Ensure the new temporary directory exists and is writeable by Flow. If you use a different Linux user account to run Flow, make sure this folder can be modified by this user.
   # mkdir -p /home/flow/partek_flow/temp
   # chown flow:flowuser /home/flow/partek_flow/temp
   
   
5. Start Flow
   # service partekflowd start

...

1. Locate the Flow installation directory. This is defined as the FLOWhome variable in the file /etc/partekflow.conf.
   $ grep FLOWhome /etc/partekflowd.conf
   For this example, we assume the Flow install directory is /opt/partek_flow. Replace this with the directory found in step 1.
   
   
2. Run the script
   $ bash /opt/partek_flow/flowstatus.sh
   After the script is run, a report will appear on the screen, then you will be asked if you wish to upload this report to Partek. If this report is uploaded, you will be contacted by support personnel who will assist with your issue. 
   
   If you are unable to find the flowstatus.sh script on your system or you want to run the most recent version of this script, then execute the following:
   *_$ wget https://customer.partek.com/flowstatus.sh_*
   $ bash flowstatus.sh

...

The relevant details of the report are:

Script running as Linux user: The user account the flowstatus.sh script was run under

Flow status: Is the Partek Flow server running or not?

Flow HTTP port: To use Partek Flow, most users will access the URL http://localhost:8080. The number associated with this URL is the HTTP port which defaults to 8080. Sometimes this port will be changed to another value. For example, if the port was changed to 8081, you will need to access Partek Flow by visiting the URL http://localhost:8081.

Flow is running as Linux user: The user account under which the Partek Flow server runs. This defaults to 'flow', however, this could have been changed to ameliorate permission issues by running Partek Flow under the same user that is the primary user of this server (i.e. the user that logs into and uses the desktop on this server).

Flow installation method: For all default installs, Partek Flow is installed with the package manager. If this is not your installation method, you are advised to contact Partek support in order to maintain your Partek Flow installation or assist with installation issues. The conversion steps are described in the next section.

Flow install directory: By default, this should be /opt/partek_flow. If this is not the case, the upgrade process for Partek Flow becomes more involved.

Flow database directory: This is a relatively small directory that stores all Partek Flow configuration and information about analysis and projects generated by Partek Flow. It is crucial that this directory be backed up regularly. If it is removed or corrupted, ALL projects in Partek Flow disappear. The actual raw input and output files for all projects are not lost, however.

...

1. Log in to the existing Linux user account used to run Partek Flow. Next, stop the Partek Flow server.
   $ cd
   $ ~/partek_flow/stop_flow.sh
   
   
2. Ensure Partek Flow is no longer running. If the output contains only "grep bin/flow" this requirement is met.
   $ ps aux | grep bin/flow
   
   
3. If Partek Flow is running and repeating step 1 above does not shut down the Partek Flow server, then use the following command where PID is the process ID of Partek Flow. The PID is found from the output of step 2 above, column two
   $ kill -9 PID
   
   
4. Backup the existing Partek Flow database and installation directories. Substitute the example paths below with those specific to the Partek Flow installation.
   $ cp -r ~/.partekflow ~/.partekflow_backup
   $ mv ~/partek_flow ~/partek_flow_backup
   
   
5. Follow the Installation steps relevant to the Linux distribution on the Partek Flow server.
   
   For Debian/Ubuntu:
   Upon reaching Configure Partek Flow installation settings enter
   $ sudo dpkg-reconfigure partekflow
   
   For Redhat/Fedora/Centos:
   Edit the following file: /etc/partekflow.conf 
   
   These prompts set the existing Linux account name and home directory used to run the previous Partek Flow server installation. 

...

1. Shutdown existing Partek Flow installation:
   $ sudo service partekflowd stop
   
   
2. Backup Partek Flow database:
   $ sudo su - flow
   $ tar cvfz partekflowdb.bkup.tgz /home/flow/.partekflow
   
   
3. Copy partekflowdb.bkup.tgz to new machine
   
   
4. Remove existing Partek Flow installation:
   Debian/Ubuntu:
   $ sudo apt-get remove partekflow partekflow-bin
   
   RedHat/Fedora/CentOS
   $ sudo yum remove partekflow partekflow-bin 

...

1. Install Partek Flow as described earlier in this document.
   When prompted for license, paste the license generated for the new machine. 
   
   
2. Shutdown Partek Flow to install previous database:
   $ sudo service partekflowd stop
   
   
3. Unpack partekflowdb.bkup.tgz:
   $ sudo su - flow
   $ tar xvfoz partekflowdb.bkup.tgz
   $ exit
   
   
4. Restart Partek Flow
   $ sudo service partekflowd start 

...