RHEL 6, 7, and 8, CentOS 6 and 7

RHEL installation instructions for package based installs, either automatically using YUM or manually with pre-downloaded rpm packages. The Appliance Installation method deploys an already configured VM into the customer Hypervisor. See IPLM appliance installation for more details.

The package installation method for Perforce IPLM uses RPM packages installed via YUM. The instructions below are listed at the top of each of the following subsections. The manual RPM installation process is outlined for when YUM installation is not available at the customer site.

Disable SELinux

Perforce IPLM software does not support SELinux. It's recommended to have SELinux disabled while running Perforce IPLM software.

# make sure SELINUX=disabled is configured
vi /etc/sysconfig/selinux 
# only if /etc/sysconfig/selinux is modified in the step above
reboot

YUM Install on CentOS 6 and 7

Post 6.7 YUM requires TLS1.2 to work properly. Run the following command to update the required OS packages.

yum -y update ca-certificates openssl nss libcurl

Install Java-8

Java-8 JRE is required to run IPLM Server. In order to help troubleshooting problems that might be related with PiServer, Java-8 JDK is recommended.

Both Oracle Java and OpenJDK are supported.

  1. For Oracle Java packages, please check https://www.oracle.com/technetwork/java/javase/downloads/index.html. For example,

    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

  2. For OpenJDK, please install java-1.8.0-openjdk_headless package that comes with the OS.

    rpm -q java-1.8.0-openjdk-headless || yum install java-1.8.0-openjdk-headless
# To verify Java program version, run command
# should return 'openjdk version "1.8.0_xxx"'.
java -version

Confirm the Perforce IPLM Binary Repository is available

Confirm there are no firewalls stopping us from accessing the Perforce IPLM binary repo.

See Hotfix repo access information in Other repositories.

# Check firewall.
iptables-save 
# make sure firewall rules do not block repo access
# Install Perforce RPM repos,
wget https://mdx.jfrog.io/mdx/mdx-generic/mdx-yum-repo-4.0.0-1.noarch.rpm
rpm -ivh mdx-yum-repo-4.0.0-1.noarch.rpm

Create service account for IPLM Server maintenance

# As root, run the commands below to change mdxadmin as maintenance account(with sudo) for IPLM Server, 
rpm -q sudo || yum install sudo -y 
chsh -s /bin/bash mdxadmin 
echo "mdxVers1c" | passwd --stdin mdxadmin 
chown mdxadmin -R /etc/mdx 
echo 'mdxadmin ALL= /sbin/service piserver start, /sbin/service piserver stop' > /etc/sudoers.d/mdx

IPLM Server installation

Perforce IPLM Server is installed as a standard Linux package using 'YUM' package manager.

IPLM Server 3.0 Installation

Follow the instructions below to install IPLM Server for the latest Pi v3 release. If an older version of IPLM Server is installed already, please refer to the section of "Upgrade 2.x IPLM Server to 3.0 PiServer " below for upgrade instructions. 

The IPLM Server rpm packages can be installed on RHEL6/CentOS6, RHEL7/CentOS7 systems.

# (Optional) If events support is to be enabled and no existing redis server is to be used, install and start backend redis server
# Install backend redis server, run
yum install -y mdx-backend-redis

# Start redis server, run
service mdx-backend-redis start

###
# Install PiServer
# As root, run
yum install -y mdx-piserver

# Note: For 3.0 and later IPLM Server releases, Neo4j is installed automatically when mdx-piserver package is installed.
#      The behavior of Neo4j installation can be controlled with MDX_PISERVER_NEO4J_INSTALL environmental variable.
#      The following command uses neo4j-enterprise-3.5.3 tarball that is pre-downloaded,
#          MDX_PISERVER_NEO4J_INSTALL=<full path of Neo4j tarball> yum install -y mdx-piserver
#      The following command skips installation of Neo4j and only installs files for PiServer,
#          MDX_PISERVER_NEO4J_INSTALL=0 yum install -y mdx-piserver
#      If Neo4j is not installed or not to be started on the node where PiServer is deployed, please configure "neo4j-local=no" in /etc/mdx/piserver.conf.
# (Optional) Configure Java executable for Piserver
#     configure javaexe option with full path of preferred Java executable
vi /etc/mdx/piserver.conf 

# Note: If the system default Java program is the preferred Java executable, no need to configure javaexe option.
# To start IPLM Server, run
service piserver start

# Note: If the above command also starts Neo4j("neo4j-local=yes" in /etc/mdx/piserver.conf), it may take up to a couple of minutes for PiServer to be fully ready.
#      Neo4j log files are under /var/log/mdx-neo4j/ and PiServer log files are under /var/log/mdx-piserver/.
# To start PiServer automatically after reboot, run
chkconfig piserver on

Install 2.x IPLM Server package

This section applies to fresh install of 2.x IPLM Server. If an older version of 2.x IPLM Server is installed already, please refer to the section of "2.x IPLM Server Upgrade" below for upgrade instructions.

The IPLM Server rpm packages can be installed on RHEL6/CentOS6, RHEL7/CentOS7 systems.

# (Optional) If events support is to be enabled and no existing redis server is to be used, install and start backend redis server
# Install backend redis server, run
yum install -y mdx-backend-redis

# Start redis server, run
service mdx-backend-redis start

# Install tools for running IPLM Server.
# Java-8 JRE should be pre-installed before installing IPLM Server.
# Note: OpenJDK-8 JRE is the preferred Java run-time for Pi server 2.33.0 and later versions. Oracle JRE should continue to work.
# As root, run
yum install -y mdx-piserver-tools-2.36.3

# As root, run
/usr/share/mdx/products/piserver/bin/install-rpm-deps.sh
# Note: Without any arguments, the install-rpm-deps.sh script only downloads and installs Neo4j.
#       The script also supports two options, "--java <JRE tarball>" and "--neo4j <Neo4j tarball>".
#       The options allow user to specify local Java and/or Neo4j tarball for installation.

# Install IPLM Server
# As root, run
yum install -y mdx-piserver-2.36.3

# On RHEL7/CentOS 7 systems, run
systemctl daemon-reload

# (Optional) Configure Java executable for Piserver
#     configure javaexe option with full path of preferred Java executable
vi /etc/mdx/piserver.conf 

# Note: If the system default Java program is the preferred Java executable, no need to configure javaexe option.
# To start IPLM Server, run
service piserver start
# Note: If the above command also starts Neo4j("neo4j-local=yes" in /etc/mdx/piserver.conf), it may take up to a couple of minutes for PiServer to be fully ready.
#       Neo4j log files are under /var/log/mdx-neo4j/ and PiServer log files are under /var/log/mdx-piserver/.

# To start IPLM Server automatically after reboot, run
chkconfig piserver on

IPLM Cache installation

IPLM Cache requires a dedicated server for production deployments. IPLM Cache is I/O intensive and should be hosted on a separate server from IPLM Server and IPLM Web.

# Install IPLM Cache packages
# Install backend server packages
yum install mdx-backend-redis mdx-backend-mongodb -y

# Install IPLM Cache packages
yum install mdx-picache mdx-picache-lib -y

# Review/Update IPLM Cache settings in /etc/mdx/picache.conf
#    "root" configuration option defines the location IPLM Cache will use to populate IPVs on disk, and needs to be defined. 
#     The "root" directory path needs to be created before starting the IPLM Cache server.
# If "worker-user" is defined, make sure the user has the write permission to the "root" path.
#     If "worker-user" is not defined, make sure user "mdxadmin" has the write permission to the "root" path.
#     Note: The "root" path typically points to a folder exported from filer.
#           If so, please make sure the mount options allow "worker-user" or "mdxadmin" to write to it.
#           Typically, the "root" path is owned by "worker-user" or "mdxadmin" to avoid any permission problem.
# "dm-program" needs to point to valid p4 executable
# Start IPLM Cache daemons
service mdx-backend-redis start
service mdx-backend-mongodb start
service picache start

# To stop IPLM Cache, run:
#    Note: IPLM Cache can normally be stopped/restarted alone, without having to stop mdx-backend-redis/mdx-backend-mongodb 
#    Note: In case mdx-backend-redis/mdx-backend-mongodb needs to be shut down, stop IPLM Cache first
# service picache stop


# To start IPLM Cache automatically after reboot, run
chkconfig mdx-backend-redis on
chkconfig mdx-backend-mongodb on
chkconfig picache on

IPLM Client installation

# Install IPLM Client rpm package
# As root, run
yum install -y mdx-picli

The Pi Command Line Client (IPLM CLI) can also be installed via a self-extracting tarball (the ".run" file) to enable installation in an NFS mounted centralized tools location. See the IPLM Client self-extracting archive page for details. 

The IPLM CLI client can also be installed with the scripted Client installation method, which sets up VersIC, PiExtras, and the necessary environment setup in a single step. See the Client-Only Tutorial Installation for P4 Server.

PiExtras installation

# Install mdx-piextras
# As root, run
yum install -y mdx-piextras

IPLM Web installation

# Install IPLM Web
# As root, run
yum install -y mdx-piweb

# To start IPLM Web, run
service piweb start

# To start IPLM Web automatically after reboot, run
chkconfig piweb on

IPLM Web document installation

The mdx-piweb-doc package installs a local copy of the documentation that has been extracted from https://help.perforce.com/methodics/.

# Install IPLM Web Doc
# As root, run
yum install -y mdx-piweb-doc

# To view document on IPLM Web, start piweb service and browse http://<piweb service host name>/media/docs/

TIP: you will want to add a footer to the bottom of all IPLM Web pages that contains a link to the local hosted docs.  Append the following code snippet to piweb.conf:

#custom_footer to include local IPLM Web hosted docs
FOOTER=<b>Perforce IPLM</b> <a href='https://help.perforce.com/methodics/' target='_blank'>Perforce hosted Documentation  |</a><a href=/media/docs/Perforce_IPLM/Perforce_IPLM.html target="_blank" class="doclink">  Local PiWeb hosted Documentation</a>

Upgrade 2.x IPLM Server to 3.0 IPLM Server

For Pi 3.0 and later releases, there's no mdx-piserver-tools package any more. The mdx-piserver-tools package in Pi 2.x releases was used to install Neo4j (and Java in some cases). To upgrade 2.x IPLM Server to 3.0 IPLM Server, the mdx-piserver-tools package and mdx-piserver package need to be manually removed and the new 3.0 mdx-piserver package needs to be installed.

Make a backup!

The command rpm -e mdx-piserver is a destructive command and will remove the Neo4j database.  Please ensure your backup process is producing a viable backup of DB data PRIOR to removing mdx-piserver.

# Stop IPLM Server service if it's running.
service piserver stop

#   Note: to ensure IPLM Server and Neo4j daemons are stopped, run "ps aux | grep java" and make sure related java processes do not exist.
# Save Neo4j folders.
cp -a /usr/share/mdx/neo4j /usr/share/mdx/neo4j.bak
cp -a /var/lib/mdx-neo4j /var/lib/mdx-neo4j.bak

# Backup IPLM Server config file.
cp -a /etc/mdx/piserver.conf /etc/mdx/piserver.conf.bak
cp -a /etc/mdx/piserver.yml /etc/mdx/piserver.yml.bak

# Remove 2.x mdx-piserver-tools package and mdx-piserver package.
rpm -e mdx-piserver mdx-piserver-tools

# Copy back the saved Neo4j folders.
cp -a /usr/share/mdx/neo4j.bak /usr/share/mdx/neo4j
cp -a /var/lib/mdx-neo4j.bak /var/lib/mdx-neo4j

# Install 3.0 mdx-piserver package.
yum install mdx-piserver -y

# Review and modify IPLM Server config files as needed.
 # vi /etc/mdx/piserver.conf
 # vi /etc/mdx/piserver.yml

# Start IPLM Server service
service piserver start

HA Neo4j cluster installations

IPLM Server Upgrade Note:

When upgrading the IPLM Server in an HA environment, please upgrade the IPLM Server Neo4j plugin on ALL nodes in the HA cluster.  The mdx-piserver version and the mdx-piserver-neo4j-plugin must be at the same version.

Note that if you have a clustered installation you will need to update the mdx-piserver-neo4j-plugin on each Neo4j node, and then restart Neo4j on each Neo4j Node. See Perforce IPLM HA with HAProxy and Neo4j cluster for additional information.

yum update mdx-piserver-neo4j-plugin

During the upgrade, if the yum update does not install to the correct location, it is possible to extract the plugin file for manual installation.

[centos-7 tmp]$ mkdir /tmp/mdx-neo4j-plugin; cd !$
[centos-7 mdx-neo4j-plugin]$ sudo yum install --downloadonly --downloaddir=. mdx-piserver-neo4j-plugin
[centos-7 mdx-neo4j-plugin]$ rpm2cpio mdx-piserver-neo4j-plugin-3.1.3-21.08.09.14.33.58.noarch.rpm | cpio -id
[centos-7 mdx-neo4j-plugin]$ find
.
./mdx-piserver-neo4j-plugin-3.1.3-21.08.09.14.33.58.noarch.rpm
./usr
./usr/share
./usr/share/mdx
./usr/share/mdx/products
./usr/share/mdx/products/piserver-neo4j
./usr/share/mdx/products/piserver-neo4j/dbms
./usr/share/mdx/products/piserver-neo4j/dbms/auth
./usr/share/mdx/products/piserver-neo4j/plugin
./usr/share/mdx/products/piserver-neo4j/plugin/mdx_plugins.jar
./usr/share/mdx/products/piserver-neo4j/scripts
./usr/share/mdx/products/piserver-neo4j/scripts/neo4j.env

Upgrade 2.x IPLM Server

Make a backup!

Please ensure your backup process is producing a viable backup of DB data PRIOR to upgrading mdx-piserver.

The instructions below apply to IPLM Server upgrade to a newer version of 2.x PiServer.

# Usually, updating IPLM Server doesn't need to update its dependencies.
# As root, run
service piserver stop

# As root, run
yum update mdx-piserver-<newer 2.x PiServer version>
# As root, run
service piserver start

If "yum update mdx-piserver" command in the above steps says that no new packages are available, please run:

yum clean all
yum update mdx-piserver

Sometimes, IPLM Server dependencies also need to be updated. Please contact Perforce support for specific instructions of updating IPLM Server dependencies.

IPLM Cache upgrade

# Update IPLM Cache on system that has older version of IPLM Cache installed already
# Stop IPLM Cache if it's running
systemctl stop picache    
# service picache stop
# Update IPLM Cache package. As root, run:
yum update mdx-picache
# (Optional) Examine new picache.conf file, which is usually saved as /etc/mdx/picache.rpmnew, and merge it will old picache.conf if desired
# Start IPLM Cache
systemctl start picache    
# or service picache start

IPLM CLI upgrade

# Update IPLM Client rpm package
# As root, run
yum update mdx-picli mdx-picli-lib

IPLM Web upgrade

# Update IPLM Web on system that has IPLM Web installed already
# As root, run:
yum update mdx-piweb mdx-piweb-lib

PiExtras upgrade

# Update PiExtras on system that has PiExtras installed already
# As root, run:
yum update mdx-piextras

Download all IPLM installation files

Please request an current download script from https://www.perforce.com/support. Once downloaded, transfer them to the target installation machine. 

PiServer install (Offline)

# As root, run the commands below to change mdxadmin as maintenance account(with sudo) for piserver, 
# If sudo is not installed
# rpm -q sudo || yum install sudo -

chsh -s /bin/bash mdxadmin 
echo "mdxVers1c" | passwd --stdin mdxadmin 
chown mdxadmin -R /etc/mdx 
echo 'mdxadmin ALL= /sbin/service piserver start, /sbin/service piserver stop' > /etc/sudoers.d/mdx 
su mdxadmin

IPLM Server 3.0 Manual Install 

# Install IPLM Server.
# Define Neo4j Installation file
export MDX_PISERVER_NEO4J_INSTALL=<full path neo4j-enterprise-3.5.35-unix.tar.gz>  
rpm -ivh <mdx-piserver>
# Note: If Neo4j is NOT to be installed, use the command below.
export MDX_PISERVER_NEO4J_INSTALL=0 
rpm -ivh <mdx-piserver>
# If events support is to be enabled, install backend redis server. 
mkdir -p /usr/share/mdx/redis 
cd /usr/share/mdx/redis 
tar xf <path to mdx-redis-bin-5.0.7.tgz> rpm -ivh <mdx-backend-redis>

Post IPLM Server 3.0 Configuration

/etc/mdx/piserver.conf
  1. (Optional) Configure Java executable for Piserver
    1. Edit /etc/mdx/piserver.conf and configure javaexe option with full path of preferred Java executable
    2. Note: If the system default Java program is the preferred Java executable, no need to configure javaexe option.
  2. (Optional) If Neo4j is NOT installed or not to be started on the node where PiServer is deployed, disable local Neo4j
    1. Edit /etc/mdx/piserver.conf and configure "neo4j-local=no" in /etc/mdx/piserver.conf.

IPLM Server Property Configuration File

For Pi 3.0 and later releases, /etc/mdx/piserver.yml is the only IPLM Server property file. IPLM Server service doesn't use  /etc/mdx/piserver.properties file any more.

Note: The /etc/mdx/piserver.yml property file has been adopted since Pi 2.35.0 release. For 2.35.0 and later 2.x releases, IPLM Server creates /etc/mdx/piserver.yml property file using the settings in /etc/mdx/piserver.properties file. After IPLM Server gets started for the first time, the new configuration file /etc/mdx/piserver.yml is created. File  /etc/mdx/piserver.yml is in YAML format. Further IPLM Server configuration changes can be done in either of /etc/mdx/piserver.properties and /etc/mdx/piserver.yml. IPLM Server will use the configuration file that has newer timestamp. If /etc/mdx/piserver.properties is newer, it will be converted and overwrite /etc/mdx/piserver.yml. If  /etc/mdx/piserver.yml is newer, it will be used directly by IPLM Server.

IPLM Server Manual Install of 2.x Release 

# For manual install of 2.x releases,
# If the target system already has older version of mdx-piserver packages installed,
rpm -Uvh <mdx-piserver> <mdx-piserver-tools>
###    Stop here, manual install is done

# For fresh install, install the tools package first.
rpm -ivh <mdx-piserver-tools>
# Install Neo4j manually.
cd /usr/share/mdx/neo4j
tar xf <neo4j-enterprise-3.5.35-unix.tar.gz>ln -s neo4j-enterprise-3.5.35 current
/usr/bin/getent group neo4j || /usr/sbin/groupadd -r neo4j
/usr/bin/getent passwd neo4j || /usr/sbin/useradd -r -d /usr/share/mdx/neo4j -g neo4j -s /bin/false neo4j
chown -R neo4j:neo4j /usr/share/mdx/neo4j/

# Install PiServer.
rpm -ivh <mdx-piserver>

IPLM Client Command Line Interface Install (pi) 

# Download the required rpm packages
# Transfer the rpms to the target IPLM Server machine or IPLM Client shared install machine
 
# On the target machine install the client rpms
rpm -ivh <mdx-picli> <mdx-picli-lib>

IPLM Web Manual Install 

# Download the IPLM Web rpm packages
# Transfer the rpms to the target PiServer machine
#
# On the target machine, install the rpms.
rpm -ivh <mdx-piweb> <mdx-piweb-lib> 
# To upgrade IPLM Web, typically only <mdx-piweb> package needs to be updated
rpm -Uvh <mdx-piweb>

IPLM Web Document Manual Install 

Note: IPLM Web document requires piweb service. So install IPLM Web first as noted above.

# Download the IPLM Web document rpm package
# Transfer the rpm to the target machine
#
# On the target machine, install the rpm.
rpm -ivh <mdx-piweb-doc> 
# To upgrade IPLM Web document
rpm -Uvh <mdx-piweb-doc>
# To view document on IPLM Web, start piweb service and browse http://<piweb service host name>/media/docs/

IPLM Cache Manual Install 

# Download the IPLM Cache rpm packages
# Transfer the files to the target machine**

# On the target IPLM Cache machine install the rpm
# install IPLM Cache
rpm -ivh <mdx-picache> <mdx-picache-lib>
# install mdx-backend-redis if it's not installed already
rpm -ivh --nopost <mdx-backend-redis rpm package>cd /usr/share/mdx/redis
tar xf <path to mdx-redis-bin-5.0.7.tgz>
# install mdx-backend-mongodb
rpm -ivh --nopost <mdx-backend-mongodb rpm package>cd /usr/share/mdx/mongodb/
tar xf <path to mongodb-linux-x86_64-3.2.20.tgz>
# To start IPLM Cache automatically after reboot, run
chkconfig mdx-backend-redis on
chkconfig mdx-backend-mongodb on
chkconfig picache on

PiExtras Manual Install 

# On the target machine install the rpm
rpm -ivh <mdx-piextras>

Make a backup!

Please ensure your backup process is producing a viable backup of DB data PRIOR to upgrading mdx-piserver.

There are two options:

  1. Repeat the manual install methods preserving previously installed versions
  2. Use the rpm upgrade option which will remove previously installed versions

The general form of an rpm upgrade command is:

rpm {-U|--upgrade} [install-options] PACKAGE_FILE ...

This installs the package, or upgrades the package currently installed to a newer version. This is the same as install, except all other version(s) of the package are removed after the new package is installed.

For more information, refer to http://ftp.rpm.org/max-rpm/ch-rpm-upgrade.html

IPLM Server Upgrade Note:

When upgrading the IPLM Server in an HA environment, please upgrade the IPLM Server Neo4j plugin on ALL nodes in the HA cluster.  The mdx-piserver and the mdx-piserver-neo4j-plugin must be at the same version.

IPLM Server maintenance commands 

# to stop the IPLM Server
sudo service piserver stop
# or 
sudo systemctl stop piserver

# To start the IPLM Server
sudo service piserver start
# or 
sudo systemctl start piserver
 
# to check status, sudo is not needed
service piserver status
# or 
systemctl status piserver

Moving the Location of the Neo4j Database Directory

Enable filesystem snapshots

If the Neo4j database is installed on a local drive without filesystem snapshot capabilities, it is advised to relocate the Neo4j DB to an snapshot enabled NFS based filer with a symbolic link back to the original installation directory.
# As root, run the commands below to relocate piserver's db 
# Assume the new location is /methodics,
systemctl stop piserver 
# or service piserver stop
cd /methodics
mv /var/lib/mdx-neo4j .
ln -s /methodics/mdx-neo4j /var/lib/mdx-neo4j
chown neo4j:neo4j /var/lib/mdx-neo4j
systemctl start piserver 
# or service piserver start
As root, follow the steps below to roll back IPLM Server to an older release of Pi.
1. Stop IPLM Server
   service piserver stop
2. Backup files used by the current IPLM Server.
   # Assume /methodics is the backup folder,
   cd /methodics
   cp -a /etc/mdx/piserver.conf .
   cp -a /etc/mdx/piserver.properties . 
   # 2.x PiServer only
   cp -a /etc/mdx/piserver.yml .
   cp -a /var/lib/mdx-neo4j .
   cp -a /usr/share/mdx/neo4j/current/conf/neo4j.conf .
3. Remove current install of IPLM Server.
   rpm -e mdx-piserver mdx-piserver-tools 
   # mdx-piserver-tools is for 2.x IPLM Server only
   rpm -qa | grep mdx  
   # make sure IPLM Server packages are removed
4. Install the IPLM Server packages for the older release.
   yum install mdx-piserver-tools-<older release of Pi> 
   # 2.x IPLM Server only
   /usr/share/mdx/products/piserver/bin/install-rpm-deps.sh 
   # 2.x IPLM Server only
   yum install mdx-piserver-<older release of Pi>   Note: For offline install, please refer to "IPLM Server manual install" section.
5. Install Neo4j DB for the older Pi release.
   mkdir -p /var/lib/mdx-neo4j/data/databases
   rm -rf /var/lib/mdx-neo4j/data/databases/graph.db
   # Copy the Neo4j DB to /var/lib/mdx-neo4j/data/databases.
   # If the Neo4j DB that's just backed up is to be used, run
   cp -a /methodics/mdx-neo4j/data/databases/graph.db /var/lib/mdx-neo4j/data/databases/
   chmod neo4j:neo4j -R /var/lib/mdx-neo4j/data/
6. Compare and apply other configuration settings.
   # Edit /etc/mdx/piserver.conf as needed.
   diff /methodics/piserver.conf /etc/mdx/piserver.conf
   # For 2.x IPLM Server, edit /etc/mdx/piserver.properties as needed.
   diff /methodics/piserver.properties /etc/mdx/piserver.properties
   # If /etc/mdx/piserver.yml was manually modified before, edit the file as needed.
   diff /methodics/piserver.yml /etc/mdx/piserver.yml
   # If /usr/share/mdx/neo4j/current/conf/neo4j.conf was manually modified before, edit the file as needed.
   diff /methodics/neo4j.conf /usr/share/mdx/neo4j/current/conf/neo4j.conf
7. Start IPLM Server
   service piserver start

IPLM Web HTTP Port Customization 

Starting from version "mdx-piweb-1.3.0", PiWeb by default listens on port 80. In order to change to a different port,
1. service piweb stop
2. Edit file "/etc/mdx/piweb.conf" and modify setting of'PIWEB_PORT' as desired.
3. service piweb start
Note: the port setting will remain unchanged during upgrade

The Metrics installation can be skipped if you are not going to monitor Perforce IPLM metrics.

The Metrics package is installed as a standard Linux package using the 'yum' package manager.

The metrics service must be started before starting other Perforce IPLM services.

# As root, install repo configuration package
rpm -ivh mdx-yum-repo-4.0.0-1.noarch.rpm
 
# Install Metrics package
# Install mdx-metrics package
yum install mdx-metrics -y

# Refer to the Metrics Monitoring page in the Reference Guide for configuration file modifications
# Start the Prometheus and Grafana servers and the Node and StatsD Exporters
systemctl start mdx-metrics    
# or service mdx-metrics start

# To stop the Prometheus and Grafana servers and the Node and StatsD Exporters, run:
systemctl stop mdx-metrics    
# or service mdx-metrics stop

Metrics Upgrade 

# Update Metrics on system that has older version of the metrics files installed already
# Stop the Prometheus and Grafana servers if they're running

service mdx-metrics stop

# Update metrics package. 
# Before we update existing packages it's generally good practice to clean the yum cache 
#    to ensure we see all new package versions during an update
# As root, run:yum clean all
yum update mdx-metrics

# Start the Prometheus and Grafana servers
service mdx-metrics start
1. Download the Metrics rpm package
1.1 Browse to https://mdx.jfrog.io/mdx/yum/production/Pi/rhel/x86_64/ and download,
    <mdx-metrics>    wget https://mdx.jfrog.io/mdx/mdx-generic/grafana/mdx-grafana-bin-6.1.6.tgz (if mdx-grafana-bin is not installed already)
    wget https://mdx.jfrog.io/mdx/mdx-generic/jmx-exporter/mdx-jmx-exporter-0.11.0.tgz (if mdx-jmx-exporter is not installed already)
    wget https://mdx.jfrog.io/mdx/mdx-generic/prometheus/mdx-node-exporter-bin-0.17.0.tgz (if mdx-node-exporter-bin is not installed already)
    wget https://mdx.jfrog.io/mdx/mdx-generic/prometheus/mdx-prometheus-bin-2.9.2.tgz (if mdx-prometheus-bin is not installed already)
    wget https://mdx.jfrog.io/mdx/mdx-generic/prometheus/mdx-statsd-exporter-bin-0.11.2.tgz (if mdx-statsd-exporter-bin is not installed already)

**Transfer the files to the target machine**

2. On the target machine install the rpm
2.1 install Metrics  
    rpm -ivh <mdx-metrics>    cd /usr/share/mdx/metrics
    tar xf <path to mdx-grafana-bin-6.1.6.tgz>    tar xf <path to mdx-jmx-exporter-0.11.0.tgz>    tar xf <path to mdx-node-exporter-bin-0.17.0.tgz>    tar xf <path to mdx-prometheus-bin-2.9.2.tgz>    tar xf <path to mdx-statsd-exporter-bin-0.11.2.tgz>
# Install IPLM PiForce package
# Install mdx-piforce package
yum install mdx-piforce -y
# Review/update PiForce configuration file
#    vi /etc/mdx/piforce.yml
# Note: Please make sure that there's a space after the configuration name(and colon) 
#   and before its value and the value is on the same line of the configuration name. 
#   For example, "uri: p4java://localhost:1666"
# Note: When using p4javassl in the uri, run the following commands to trust the server fingerprint,
su - mdxadmin
p4 -p ssl:<p4 server host>:<p4 server port> trust
# Start/stop PiForce daemon
service piforce start
service piforce status
service piforce stop

IPLM PiForce upgrade

# Update PiForce package
# Stop piforce if it's running
service piforce stop
# Update package. As root, run:
yum update mdx-piforce
# Start piforce
service piforce start
# On the target machine install the mdx-piforce package.
rpm -i <mdx-piforce>