IPLM Server self-extracting archive

Instructions for installing IPLM Server with the Self-Extracting Archive method. The self-extracting archive can be used with any distribution, and can be installed without root access. The IPLM Server self extracting archive can be used in situations where .deb or rpm installations are not possible in the customer environment.

Installing IPLM Server self-extracting archive (2.33.0 and later releases)

Step 1: Downloading/Installing IPLM Server

1. Install Java-8. Java-8 JRE is required to run IPLM Server. In order to help troubleshooting problems that might be related with IPLM Server, Java-8 JDK is recommended. Both Oracle Java and OpenJDK are supported.
1.1 For Oracle JDK, please refer to Oracle website for download/install instructions.
1.2 For OpenJDK, please follow OS specific instructions to install from OS repos.
  - For CentOS/RHEL systems, run "yum install java-1.8.0-openjdk-headless" to install Java-8

2. The PiServer self-extractable archive, or the IPLM Server "run" package, can be used with any major Linux distributions. It can be installed and used as a non-root user.
2.1 Download "run" package from artifactory
    wget https://mdx.jfrog.io/mdx/mdx-generic/Pi/server/production/mdx-piserver-3.6.3-25.01.09_01.54.run
2.2 Add exec perms to the package
    chmod +x mdx-piserver-3.6.3-25.01.09_01.54.run
2.3 Install package,
    Run "./mdx-piserver-3.6.3-25.01.09_01.54.run" and press Enter to install into current location
2.4 PiServer is installed under "mdx-piserver-3.6.3-25.01.09_01.54.run" 
2.5 (Optional) Configure Java program path. If Java program is not installed in system paths, its path can be specified in file conf/piserver.conf under install folder.
3. Install options
3.1 Default install
    By default, when running "./mdx-piserver-3.6.3-25.01.09_01.54.run" without any optional arguments, it installs the following components.
    - Neo4j
    - MDX Redis tools
    - MDX Metrics tools
    Note: Redis tools and Metrics tools have separate service scripts under bin folder
3.2 Minimum install
    Run "./mdx-piserver-3.6.3-25.01.09_01.54.run -- --skip-redis --skip-metrics"    With minimum install, only PiServer is installed, and installation of Redis tools and Metrics tools is skipped.
3.3 Java install (Please note that this option is not preferred and included only for convenience purpose in some cases)
    Run "./mdx-piserver-3.6.3-25.01.09_01.54.run -- --with-java" or 
        "./mdx-piserver-3.6.3-25.01.09_01.54.run -- --with-java --java <JRE tarball>"    The "--with-java" option installs Java run-time inside folder mdx-piserver-3.6.3-25.01.09_01.54.run and the piserver script uses it to start PiServer.
    The "--java <JRE tarball>" allows user to specify a separate JRE tarball to be used by PiServer.
    Note: without "--java <JRE tarball>", "--with-java" option downloads and installs OpenJDK-8 JRE packaged by Perforce, which only works on RHEL/CentOS 6/7 platforms.

 
Alternatively, if the host couldn't connect to Internet during installation, follow the steps below to install piserver offline.
1.1 Open web browser and search/download "jdk-8u131-linux-x64.tar.gz", or use the command below to download
    wget --no-check-certificate --no-cookies --header "Cookie: oraclelicense=accept-securebackup-cookie" http://download.oracle.com/otn-pub/java/jdk/8u131-b11/d54c1d3a095b4ff2b6607d096fa80163/jdk-8u131-linux-x64.tar.gz
1.2 Open web browser and search/download "neo4j-enterprise-3.5.35-unix.tar.gz", or use the command below to download
   wget https://mdx.jfrog.io/artifactory/mdx-generic/neo4j/enterprise/neo4j-enterprise-3.5.35-unix.tar.gz
1.3 Open web browser and search/download "mdx-redis-bin-5.0.7.tgz", or use the command below to download
   wget https://mdx.jfrog.io/mdx/mdx-generic/redis/mdx-redis-bin-5.0.7.tgz
1.4 (Optional) If metrics is to be used, open web browser and search/download following packages,
     mdx-grafana-bin-6.1.6.tgz
     mdx-jmx-exporter-0.11.0.tgz
     mdx-prometheus-bin-2.9.2.tgz
   or use the command below to download,
     wget https://mdx.jfrog.io/mdx/mdx-generic/grafana/mdx-grafana-bin-6.1.6.tgz
     wget https://mdx.jfrog.io/mdx/mdx-generic/jmx-exporter/mdx-jmx-exporter-0.11.0.tgz
     wget https://mdx.jfrog.io/mdx/mdx-generic/prometheus/mdx-prometheus-bin-2.9.2.tgz
1.5 Open "https://mdx.jfrog.io/mdx/mdx-generic/Pi/server/production/" in web browser and download mdx-piserver "run" package, or use the command below to download
   wget https://mdx.jfrog.io/mdx/mdx-generic/Pi/server/production/mdx-piserver-3.6.3-25.01.09_01.54.run
1.6 add exec permission to the downloaded package 
   chmod +x mdx-piserver-3.6.3-25.01.09_01.54.run
1.7 Install piserver
1.7.1 As any user(user home dir should exist), run
   ./mdx-piserver-3.6.3-25.01.09_01.54.run -- --java jdk-8u131-linux-x64.tar.gz --neo4j neo4j-enterprise-3.5.35-unix.tar.gz --redis mdx-redis-bin-5.0.7.tgz --skip-metrics
  Note: (optional) Replace "--skip-metrics" with "--prometheus mdx-prometheus-bin-2.9.2.tgz --grafana mdx-grafana-bin-6.1.6.tgz --jmx mdx-jmx-exporter-0.11.0.tgz" in the above command if metrics is to be used.
1.7.2 press Enter to install at current location
1.8 The PiServer is installed under "mdx-piserver-3.6.3-25.01.09_01.54.run"

Step 2: Starting/Stopping IPLM Server

1. Check system settings for current user
1.1 Block device ID
    It's recommended to give current user sudo privilege to run "blkid" command. Please check with system administrator to have this enabled.
    At a minimum, make sure when running as current user, the "blkid" command can properly report the underlying block device UUID.
1.2 Number of open files
    It's recommended to have 40000 maximum number of open files for Neo4j process.
    Run "ulimit -n 40000" to configure the maximum number of open files to 40000.
    Run "ulimit -n" to check the current number of maximum number of open files.
    If "ulimit -n" doesn't report the expected maximum number of open files, please check with system administrator.
    The problem can typically be resolved by running command below,
     echo '<current user> hard nofile 40000' > /etc/security/limits.d/piserver.conf
    (please replace <current user> with current user name).
 
2. Start/stop piserver
    cd mdx-piserver-3.6.3-25.01.09_01.54.run
2.1 start piserver, run
    ./bin/piserver start
    Note: the piserver script requires running blkid command with sudo. If it's not configured with sudo and blkid has been run previously, simply type Ctrl-C to skip typing sudo password and the script will continue to start piserver.
2.2 stop piserver, run
    ./bin/piserver stop
    
3. (Optional) Manage Redis backend service
   By default, Redis backend component is also installed when the PiServer "run" package is installed.
   Use the script ./bin/mdx-backend-redis.sh to start/stop Redis backend server
3.1 Start Redis backend server
   ./bin/mdx-backend-redis.sh start
3.2 Stop Redis backend servder
   ./bin/mdx-backend-redis.sh stop

Download Links for Manual Install

Installing IPLM Server Self-Extracting Archive (Pre-2.33.0 release)

Step 1: Downloading/Installing IPLM Server

IPLM Server Install 
1.1 Download self-extractable package from mdx package repo 
    wget https://mdx.jfrog.io/mdx/mdx-generic/Pi/server/production/mdx-piserver-2.32.2-19.08.27_15.00.run
1.2 add exec permission to the downloaded package
    chmod +x mdx-piserver-2.32.2-19.08.27_15.00.run
1.3 Install piserver
1.3.1 As any user(user home dir should exist), run
     ./mdx-piserver-2.32.2-19.08.27_15.00.run
1.3.2 press Enter to install at current location
1.4 The PiServer is installed under "mdx-piserver-2.32.2-19.08.27_15.00" 
Alternatively, if the host couldn't connect to Internet during installation, follow the steps below to install piserver offline.
1.1 Open web browser and search/download "jdk-8u131-linux-x64.tar.gz", or use the command below to download
    wget --no-check-certificate --no-cookies --header "Cookie: oraclelicense=accept-securebackup-cookie" http://download.oracle.com/otn-pub/java/jdk/8u131-b11/d54c1d3a095b4ff2b6607d096fa80163/jdk-8u131-linux-x64.tar.gz
1.2 Open web browser and search/download "neo4j-enterprise-3.5.35-unix.tar.gz", or use the command below to download
   wget https://mdx.jfrog.io/artifactory/mdx-generic/neo4j/enterprise/neo4j-enterprise-3.5.35-unix.tar.gz
1.3 Open web browser and search/download "mdx-redis-bin-5.0.7.tgz", or use the command below to download
   wget https://mdx.jfrog.io/mdx/mdx-generic/redis/mdx-redis-bin-5.0.7.tgz
1.4 Open "https://mdx.jfrog.io/mdx/mdx-generic/Pi/server/production/" in web browser and download mdx-piserver "run" package, or use the command below to download
   wget https://mdx.jfrog.io/mdx/mdx-generic/Pi/server/production/mdx-piserver-2.32.2-19.08.27_15.00.run
1.5 add exec permission to the downloaded package 
   chmod +x mdx-piserver-2.32.2-19.08.27_15.00.run
1.6 Install piserver
1.6.1 As any user(user home dir should exist), run
   ./mdx-piserver-2.32.2-19.08.27_15.00.run -- --java jdk-8u131-linux-x64.tar.gz --neo4j neo4j-enterprise-3.5.35-unix.tar.gz --redis mdx-redis-bin-5.0.7.tgz
1.6.2 press Enter to install at current location
1.7 The PiServer is installed under "mdx-piserver-2.32.2-19.08.27_15.00"

Step 2: Starting/Stopping IPLM Server

IPLM Server Install 
Start/stop piserver
2.1 start piserver, run
    cd mdx-piserver-2.32.2-19.08.27_15.00
2.2 run
    ./bin/piserverd --site-dir . --property conf/piserver.properties
2.3 stop piserver, run
    killall ./jdk1.8.0_131/bin/java

Currently we do not provide init.d start/stop scripts for IPLM Server installed using a self-extracting archive

Alternative IPLM Server Property Configuration File (2.35.0 and Later Releases)

In Pi 2.35.0 release, IPLM Server uses a new format of property configuration file internally. After IPLM Server gets started for the first time, a new configuration file conf/piserver.yml is created. File  conf/piserver.yml is in YAML format. It's converted from conf/piserver.properties when it's first created. Further IPLM Server configuration changes can be done in either of conf/piserver.properties and conf/piserver.yml.  IPLM Serverwill use the configuration file that has newer timestamp. If conf/piserver.properties is newer, it will be converted and overwrite conf/piserver.yml. If conf/piserver.yml is newer, it will be used directly by IPLM Server.

Upgrading IPLM Server Self-Extracting Archive

The IPLM Server Self-Extracting Archive installation is completely self-contained, this means that the graph db data storing all of the PiServer data is located inside the install directory.  To upgrade the version of IPLM Server and retain the existing IPLM Server data, it is necessary to shut down the existing piserver and neo4j processes and copy the graph.db into the new install location.

IPLM Server Install 
1. Follow the instructions above to shut down IPLM Server and Neo4j server, if they are running.
   Note: Make sure IPLM Server and Neo4j server have stopped by checking the related processes.
    ps -elf | grep neo4j
    ps -elf | grep piserver
2. Back up the Neo4j DB in a safe location.
   # Assume /methodics is the backup folder,
   cp -a /var/lib/mdx-neo4j /methodics
   Note: The backup will not normally be used and mainly serves as a safe measure here.
3. Follow the instructions above to download and install the new version of the self-extractable package.
   Note: The new install should be in completely new folder.
4. Copy the Neo4j DB from old install to the same location in the new install.
   rm -rf <path of the new piserver install>/neo4j-enterprise-3.5.35/data/databases/graph.db
   cp -a <path of the old piserver install>/neo4j-enterprise-3.5.35/data/databases/graph.db <path of the new piserver install>/neo4j-enterprise-3.5.35/data/databases
5. Enable Neo4j DB upgrade.
   echo "dbms.allow_upgrade=true" >> <path of the new piserver install>/neo4j-enterprise-3.5.35/conf/neo4j.conf
   Note: If the neo4j.conf file in the old install was manually modified before, apply the same changes here in the new neo4j.conf file.
6. Check PiServer config files and apply changes as needed.
   vi <path of the new piserver install>/conf/piserver.conf
   vi <path of the new piserver install>/conf/piserver.properties
7. Follow the instructions above to start PiServer.
8. After verifying PiServer and Neo4j are working properly, follow the instructions above to shut down PiServer and Neo4j server.
9. Disable Neo4j DB upgrade.
   sed -i -e 's/^dbms.allow_upgrade=true.*/dbms.allow_upgrade=false/g' <path of the new piserver install>/neo4j-enterprise-3.5.35/conf/neo4j.conf
10. Follow the instructions above to start PiServer and Neo4j server.
 

Rollback

IPLM Server Install 
As root, follow the steps below to roll back IPLM Server to an older release of Pi.
1. Follow the instructions above to shut down IPLM Server and Neo4j server, if they are running.
   Note: Make sure IPLM Server and Neo4j server have stopped by checking the related processes.
    ps -elf | grep neo4j
    ps -elf | grep piserver
2. Back up the Neo4j DB in a safe location.
   # Assume /methodics is the backup folder,
   cp -a /var/lib/mdx-neo4j /methodics
   Note: The backup will not normally be used and mainly serves as a safe measure here.
3. Follow the instructions above to download and install the old version of the self-extractable package.
   Note: The new install should be in completely new folder.
4. Install the Neo4j DB that corresponds to the old Pi release.
   rm -rf <path of the old Pi release>/neo4j-enterprise-3.5.35/data/databases/graph.db
   cp -a <graph.db corresponding to the old Pi release> <path of the old Pi release>/neo4j-enterprise-3.5.35/data/databases
   Note: If the Neo4j DB of the Pi release before rollback is to be used, simply copy the Neo4j DB from the install before rollback to the same location in the new install.
   cp -a <path of Pi install before rollback>/neo4j-enterprise-3.5.35/data/databases/graph.db <path of the old Pi release>/neo4j-enterprise-3.5.35/data/databases
5. If the neo4j.conf file in the install before rollback was manually modified before, apply the same changes here in the neo4j.conf file of the old Pi release.
6. Check IPLM Server config files and apply changes as needed.
   vi <path of the old Pi release>/conf/piserver.conf
   vi <path of the old Pi release>/conf/piserver.properties
7. Follow the instructions above to start IPLM Server.

IPLM Server and Neo4j Metrics

Refer to the Perforce IPLM Metrics page for use of IPLM Server and Neo4j metrics for the self extracting archive.

Instructions for installing IPLM Server with the Self-Extracting Archive method. The self-extracting archive can be used with any distribution, and can be installed without root access. The IPLM Server self extracting archive can be used in situations where .deb or rpm installations are not possible in the customer environment.

Installing IPLM Server Self-Extracting Archive (2.33.0 and Later Release)

Step 1: Downloading/Installing IPLM Server

1. Install Java-8. Java-8 JRE is required to run IPLM Server. In order to help troubleshooting problems that might be related with IPLM Server, Java-8 JDK is recommended. Both Oracle Java and OpenJDK are supported.
1.1 For Oracle JDK, please refer to Oracle website for download/install instructions.
1.2 For OpenJDK, please follow OS specific instructions to install from OS repos.
  - For CentOS/RHEL systems, run "yum install java-1.8.0-openjdk-headless" to install Java-8

2. The IPLM Server self-extractable archive, or the Piserver "run" package, can be used with any major Linux distributions. It can be installed and used as a non-root user.
2.1 Download "run" package from artifactory
    wget https://mdx.jfrog.io/mdx/mdx-generic/Pi/server/production/mdx-piserver-3.6.3-25.01.09_01.54.run.run
2.2 Add exec perms to the package
    chmod +x mdx-piserver-3.6.3-25.01.09_01.54.run.run
2.3 Install package,
    Run "./mdx-piserver-3.6.3-25.01.09_01.54.run.run" and press Enter to install into current location
2.4 IPLM Server is installed under "mdx-piserver-3.6.3-25.01.09_01.54.run" 
2.5 (Optional) Configure Java program path. If Java program is not installed in system paths, its path can be specified in file conf/piserver.conf under install folder.
3. Install options
3.1 Default install
    By default, when running "./mdx-piserver-3.6.3-25.01.09_01.54.run.run" without any optional arguments, it installs the following components.
    - Neo4j
    - MDX Redis tools
    - MDX Metrics tools
    Note: Redis tools and Metrics tools have separate service scripts under bin folder
3.2 Minimum install
    Run "./mdx-piserver-3.6.3-25.01.09_01.54.run.run -- --skip-redis --skip-metrics"    With minimum install, only PiServer is installed, and installation of Redis tools and Metrics tools is skipped.
3.3 Java install (Please note that this option is not preferred and included only for convenience purpose in some cases)
    Run "./mdx-piserver-3.6.3-25.01.09_01.54.run.run -- --with-java" or 
        "./mdx-piserver-3.6.3-25.01.09_01.54.run.run -- --with-java --java <JRE tarball>"    The "--with-java" option installs Java run-time inside folder mdx-piserver-3.6.3-25.01.09_01.54.run and the piserver script uses it to start PiServer.
    The "--java <JRE tarball>" allows user to specify a separate JRE tarball to be used by PiServer.
    Note: without "--java <JRE tarball>", "--with-java" option downloads and installs OpenJDK-8 JRE packaged by Perforce, which only works on RHEL/CentOS 6/7 platforms.

 
Alternatively, if the host couldn't connect to Internet during installation, follow the steps below to install IPLM Server offline.
1.1 Open web browser and search/download "jdk-8u131-linux-x64.tar.gz", or use the command below to download
    wget --no-check-certificate --no-cookies --header "Cookie: oraclelicense=accept-securebackup-cookie" http://download.oracle.com/otn-pub/java/jdk/8u131-b11/d54c1d3a095b4ff2b6607d096fa80163/jdk-8u131-linux-x64.tar.gz
1.2 Open web browser and search/download "neo4j-enterprise-3.5.35-unix.tar.gz", or use the command below to download
   wget https://mdx.jfrog.io/artifactory/mdx-generic/neo4j/enterprise/neo4j-enterprise-3.5.35-unix.tar.gz
1.3 Open web browser and search/download "mdx-redis-bin-5.0.7.tgz", or use the command below to download
   wget https://mdx.jfrog.io/mdx/mdx-generic/redis/mdx-redis-bin-5.0.7.tgz
1.4 (Optional) If metrics is to be used, open web browser and search/download following packages,
     mdx-grafana-bin-6.1.6.tgz
     mdx-jmx-exporter-0.11.0.tgz
     mdx-prometheus-bin-2.9.2.tgz
   or use the command below to download,
     wget https://mdx.jfrog.io/mdx/mdx-generic/grafana/mdx-grafana-bin-6.1.6.tgz
     wget https://mdx.jfrog.io/mdx/mdx-generic/jmx-exporter/mdx-jmx-exporter-0.11.0.tgz
     wget https://mdx.jfrog.io/mdx/mdx-generic/prometheus/mdx-prometheus-bin-2.9.2.tgz
1.5 Open "https://mdx.jfrog.io/mdx/mdx-generic/Pi/server/production/" in web browser and download mdx-piserver "run" package, or use the command below to download
   wget https://mdx.jfrog.io/mdx/mdx-generic/Pi/server/production/mdx-piserver-3.6.3-25.01.09_01.54.run.run
1.6 add exec permission to the downloaded package 
   chmod +x mdx-piserver-3.6.3-25.01.09_01.54.run.run
1.7 Install IPLM Server
1.7.1 As any user(user home dir should exist), run
   ./mdx-piserver-3.6.3-25.01.09_01.54.run.run -- --java jdk-8u131-linux-x64.tar.gz --neo4j neo4j-enterprise-3.5.35-unix.tar.gz --redis mdx-redis-bin-5.0.7.tgz --skip-metrics
  Note: (optional) Replace "--skip-metrics" with "--prometheus mdx-prometheus-bin-2.9.2.tgz --grafana mdx-grafana-bin-6.1.6.tgz --jmx mdx-jmx-exporter-0.11.0.tgz" in the above command if metrics is to be used.
1.7.2 press Enter to install at current location
1.8 The IPLM Server is installed under "mdx-piserver-3.6.3-25.01.09_01.54.run"

Step 2: Starting/Stopping IPLM Server

1. Check system settings for current user
1.1 Block device ID
    It's recommended to give current user sudo privilege to run "blkid" command. Please check with system administrator to have this enabled.
    At a minimum, make sure when running as current user, the "blkid" command can properly report the underlying block device UUID.
1.2 Number of open files
    It's recommended to have 40000 maximum number of open files for Neo4j process.
    Run "ulimit -n 40000" to configure the maximum number of open files to 40000.
    Run "ulimit -n" to check the current number of maximum number of open files.
    If "ulimit -n" doesn't report the expected maximum number of open files, please check with system administrator.
    The problem can typically be resolved by running command below,
     echo '<current user> hard nofile 40000' > /etc/security/limits.d/piserver.conf
    (please replace <current user> with current user name).
 
2. Start/stop piserver
    cd mdx-piserver-3.6.3-25.01.09_01.54.run
2.1 start piserver, run
    ./bin/piserver start
    Note: the piserver script requires running blkid command with sudo. If it's not configured with sudo and blkid has been run previously, simply type Ctrl-C to skip typing sudo password and the script will continue to start piserver.
2.2 stop piserver, run
    ./bin/piserver stop
    
3. (Optional) Manage Redis backend service
   By default, Redis backend component is also installed when the PiServer "run" package is installed.
   Use the script ./bin/mdx-backend-redis.sh to start/stop Redis backend server
3.1 Start Redis backend server
   ./bin/mdx-backend-redis.sh start
3.2 Stop Redis backend servder
   ./bin/mdx-backend-redis.sh stop

Download Links for Manual Install

Installing IPLM Server Self-Extracting Archive (Pre-2.33.0 release)

Step 1: Downloading/Installing IPLM Server

IPLM Server Install 
1.1 Download self-extractable package from mdx package repo 
    wget https://mdx.jfrog.io/mdx/mdx-generic/Pi/server/production/mdx-piserver-2.32.2-19.08.27_15.00.run
1.2 add exec permission to the downloaded package
    chmod +x mdx-piserver-2.32.2-19.08.27_15.00.run
1.3 Install IPLM Server
1.3.1 As any user(user home dir should exist), run
     ./mdx-piserver-2.32.2-19.08.27_15.00.run
1.3.2 press Enter to install at current location
1.4 The IPLM Server is installed under "mdx-piserver-2.32.2-19.08.27_15.00" 
Alternatively, if the host couldn't connect to Internet during installation, follow the steps below to install piserver offline.
1.1 Open web browser and search/download "jdk-8u131-linux-x64.tar.gz", or use the command below to download
    wget --no-check-certificate --no-cookies --header "Cookie: oraclelicense=accept-securebackup-cookie" http://download.oracle.com/otn-pub/java/jdk/8u131-b11/d54c1d3a095b4ff2b6607d096fa80163/jdk-8u131-linux-x64.tar.gz
1.2 Open web browser and search/download "neo4j-enterprise-3.5.35-unix.tar.gz", or use the command below to download
   wget https://mdx.jfrog.io/artifactory/mdx-generic/neo4j/enterprise/neo4j-enterprise-3.5.35-unix.tar.gz
1.3 Open web browser and search/download "mdx-redis-bin-5.0.7.tgz", or use the command below to download
   wget https://mdx.jfrog.io/mdx/mdx-generic/redis/mdx-redis-bin-5.0.7.tgz
1.4 Open "https://mdx.jfrog.io/mdx/mdx-generic/Pi/server/production/" in web browser and download mdx-piserver "run" package, or use the command below to download
   wget https://mdx.jfrog.io/mdx/mdx-generic/Pi/server/production/mdx-piserver-2.32.2-19.08.27_15.00.run
1.5 add exec permission to the downloaded package 
   chmod +x mdx-piserver-2.32.2-19.08.27_15.00.run
1.6 Install IPLM Server
1.6.1 As any user(user home dir should exist), run
   ./mdx-piserver-2.32.2-19.08.27_15.00.run -- --java jdk-8u131-linux-x64.tar.gz --neo4j neo4j-enterprise-3.5.35-unix.tar.gz --redis mdx-redis-bin-5.0.7.tgz
1.6.2 press Enter to install at current location
1.7 The PiServer is installed under "mdx-piserver-2.32.2-19.08.27_15.00"

Step 2: Starting/Stopping IPLM Server

IPLM Server Install 
Start/stop piserver
2.1 start piserver, run
    cd mdx-piserver-2.32.2-19.08.27_15.00
2.2 run
    ./bin/piserverd --site-dir . --property conf/piserver.properties
2.3 stop piserver, run
    killall ./jdk1.8.0_131/bin/java

Currently we do not provide init.d start/stop scripts for PiServer installed using a self-extracting archive

Alternative IPLM Server Property Configuration File (2.35.0 and Later Releases)

In Pi 2.35.0 release, IPLM Server uses a new format of property configuration file internally. After IPLM Server gets started for the first time, a new configuration file conf/piserver.yml is created. File  conf/piserver.yml is in YAML format. It's converted from conf/piserver.properties when it's first created. Further IPLM Server configuration changes can be done in either of conf/piserver.properties and conf/piserver.yml. IPLM Server will use the configuration file that has newer timestamp. If conf/piserver.properties is newer, it will be converted and overwrite conf/piserver.yml. If conf/piserver.yml is newer, it will be used directly by IPLM Server.

Upgrading IPLM Server Self-Extracting Archive

The IPLM Server Self-Extracting Archive installation is completely self-contained, this means that the graph db data storing all of the PiServer data is located inside the install directory.  To upgrade the version of Piserver and retain the existing IPLM Server data, it is necessary to shut down the existing piserver and neo4j processes and copy the graph.db into the new install location.

IPLM Server Install 
1. Follow the instructions above to shut down IPLM Server and Neo4j server, if they are running.
   Note: Make sure IPLM Server and Neo4j server have stopped by checking the related processes.
    ps -elf | grep neo4j
    ps -elf | grep piserver
2. Back up the Neo4j DB in a safe location.
   # Assume /methodics is the backup folder,
   cp -a /var/lib/mdx-neo4j /methodics
   Note: The backup will not normally be used and mainly serves as a safe measure here.
3. Follow the instructions above to download and install the new version of the self-extractable package.
   Note: The new install should be in completely new folder.
4. Copy the Neo4j DB from old install to the same location in the new install.
   rm -rf <path of the new piserver install>/neo4j-enterprise-3.5.35/data/databases/graph.db
   cp -a <path of the old piserver install>/neo4j-enterprise-3.5.35/data/databases/graph.db <path of the new piserver install>/neo4j-enterprise-3.5.35/data/databases
5. Enable Neo4j DB upgrade.
   echo "dbms.allow_upgrade=true" >> <path of the new piserver install>/neo4j-enterprise-3.5.35/conf/neo4j.conf
   Note: If the neo4j.conf file in the old install was manually modified before, apply the same changes here in the new neo4j.conf file.
6. Check IPLM Server config files and apply changes as needed.
   vi <path of the new piserver install>/conf/piserver.conf
   vi <path of the new piserver install>/conf/piserver.properties
7. Follow the instructions above to start PiServer.
8. After verifying IPLM Server and Neo4j are working properly, follow the instructions above to shut down IPLM Server and Neo4j server.
9. Disable Neo4j DB upgrade.
   sed -i -e 's/^dbms.allow_upgrade=true.*/dbms.allow_upgrade=false/g' <path of the new piserver install>/neo4j-enterprise-3.5.35/conf/neo4j.conf
10. Follow the instructions above to start PiServer and Neo4j server.
 

Rollback

IPLM Server Install 
As root, follow the steps below to roll back IPLM Server to an older release of Pi.
1. Follow the instructions above to shut down IPLM Server and Neo4j server, if they are running.
   Note: Make sure IPLM Server and Neo4j server have stopped by checking the related processes.
    ps -elf | grep neo4j
    ps -elf | grep piserver
2. Back up the Neo4j DB in a safe location.
   # Assume /methodics is the backup folder,
   cp -a /var/lib/mdx-neo4j /methodics
   Note: The backup will not normally be used and mainly serves as a safe measure here.
3. Follow the instructions above to download and install the old version of the self-extractable package.
   Note: The new install should be in completely new folder.
4. Install the Neo4j DB that corresponds to the old Pi release.
   rm -rf <path of the old Pi release>/neo4j-enterprise-3.5.35/data/databases/graph.db
   cp -a <graph.db corresponding to the old Pi release> <path of the old Pi release>/neo4j-enterprise-3.5.35/data/databases
   Note: If the Neo4j DB of the Pi release before rollback is to be used, simply copy the Neo4j DB from the install before rollback to the same location in the new install.
   cp -a <path of Pi install before rollback>/neo4j-enterprise-3.5.35/data/databases/graph.db <path of the old Pi release>/neo4j-enterprise-3.5.35/data/databases
5. If the neo4j.conf file in the install before rollback was manually modified before, apply the same changes here in the neo4j.conf file of the old Pi release.
6. Check IPLM Server config files and apply changes as needed.
   vi <path of the old Pi release>/conf/piserver.conf
   vi <path of the old Pi release>/conf/piserver.properties
7. Follow the instructions above to start IPLM Server.

IPLM Server and Neo4j Metrics

Refer to the Perforce IPLM Metrics page for use of IPLM Server and Neo4j metrics for the self extracting archive.