SLES 12

SLES installation instructions for package based installs, either automatically using zypper or manually with pre-downloaded rpm packages.

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

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 PiClient 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 Perforce.

Setting up the Repo

Install the Perforce rpm package repo.

1. zypper addrepo -t rpm-md http://mdx.jfrog.io/mdx/yum/production/Pi/sles/x86_64/ mdx_rpm
2. zypper --gpg-auto-import-keys ref mdx_rpm
   Note: Since Perforce package repos are constantly updated, run the above command before trying to install any latest Perforce packages. 
3. wget http://mdx.jfrog.io/mdx/mdx-generic/RPM-GPG-KEY-mdx-v2
4. rpm --import RPM-GPG-KEY-mdx-v2

Metrics Installation

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

The Metrics package is installed as a standard rpm package using the zypper command.

1. Install mdx-metrics package,
   zypper in mdx-metrics
2. Refer to the Metrics Monitoring page in the Reference Guide for configuration file modifications
3. Start mdx-metrics service, which includes the Prometheus and Grafana servers and the Node and StatsD Exporters,
   service mdx-metrics start

IPLM Server installation

Perforce IPLM Server is installed as standard Linux rpm packages using the zypper command.

Install Java

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

Both Oracle Java and OpenJDK are supported.

For Oracle Java packages, check https://www.oracle.com/java/technologies/downloads/#java11.

For OpenJDK, install java-1.11.0-openjdk_headless package that comes with the OS.

zypper install java-11-openjdk-headless
# To verify Java program version, run command
# should return 'openjdk version "11.0_xxx"'.
java -version

Install IPLM Server packages

Follow the instructions below to install IPLM Server for the latest Pi 2024.1 release. If an earlier version of IPLM Server is installed already, refer to Migrating to IPLM Core 2024.1.

1. (Optional) If events support is to be enabled, install and start backend redis server
1.1 Install backend redis server, run
    zypper in iplm-backend-redis
1.2 Start redis server, run
    service iplm-backend-redis start

2. Install IPLM Servers
2.1 As root, run
    zypper in -y iplm-server
    Note: Neo4j is installed automatically when iplm-server package is installed.
          The behavior of Neo4j installation can be controlled with MDX_PISERVER_NEO4J_INSTALL environmental variable.
          The following command uses neo4j-enterprise-4.4.183 tarball that is pre-downloaded,
              MDX_PISERVER_NEO4J_INSTALL=<full path of Neo4j tarball> zypper install -y iplm-server
          The following command skips installation of Neo4j and only installs files for PiServer,
              MDX_PISERVER_NEO4J_INSTALL=0 zypper install -y iplm-server
2.2 (Optional) Configure Java executable for IPLM Server
    vi /etc/mdx/piserver.conf # configure javaexe option with full path of preferred Java executable
    Note: If the system default Java program is the preferred Java executable, no need to configure javaexe option.
2.3 (Optional) If Neo4j is not installed or should not be started on the node where IPLM Server is installed, disable local Neo4j
    vi /etc/mdx/piserver.conf # configure "neo4j-local=no"
2.4 (Optional) If Neo4j is installed on a separate node or cluster, specify Neo4j node in piserver.yml
    vi /etc/mdx/piserver.yml 
2.5 Start IPLM Server, run
    service piserver start
    Note: If "neo4j-local=yes" is configured 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/iplm-server/.
2.6 Start IPLM Server automatically after reboot, run
    chkconfig piserver on

IPLM Client installation

Install IPLM Client package

As root, run

   zypper in -y iplm-cli

IPLM Client upgrade

Update IPLM Client on system that has an older version of IPLM Client installed already

As root, run:

   zypper up -y iplm-cli
   Note: the iplm-cli-lib package will be updated automatically, if needed

IPLM Web Installation

Perforce IPLM Web server is installed as standard Linux packages using the 'zypper' command.

1. As root, run
   zypper in -y iplm-web
   Note: the iplm-web-lib package will be downloaded and installed automatically
2. To start IPLM Web, run
   systemctl daemon-reload 
   service piweb start
3. To start IPLM Web automatically after reboot, run
   chkconfig piweb on

IPLM Web upgrade

Update IPLM Web on system that has IPLM Web installed already
1. As root, run:
   zypper up -y iplm-web
   Note: the iplm-web-lib package will be updated automatically, if needed

IPLM Web HTTP port customization

IPLM Web 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 un-changed during upgrade

IPLM Web Document Installation

Perforce IPLM Document package can be installed using the 'zypper' command.

Note: IPLM Web document requires IPLM Web service. So install IPLM Web first as noted above.
As root, run
   zypper in -y iplm-doc
# To view document on IPLM Web, start piweb service and browse http://<piweb service host name>/media/docs/

IPLM Webdocument package upgrade

To update IPLM Web Document
As root, run:
   zypper up -y iplm-doc

PiExtras installation

Perforce IPLM PiExtras tool is installed as standard Linux packages using the 'zypper' command.

Install PiExtras package
1. As root, run
   zypper in -y iplm-piextras

PiExtras upgrade

Update PiExtras on system that has PiExtras installed already
1. As root, run:
   zypper up -y iplm-piextras

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.

Perforce IPLM Cache server is installed as standard Linux packages using the 'zypper' command.

1. As root, install backend server packages
   zypper in -y iplm-backend-redis
   zypper in -y iplm-backend-mongodb
2. Install IPLM Cache packages
   zypper in -y iplm-cache
   Note: iplm-cache-lib will be installed automatically
3. Review/Update IPLM Cache settings in /etc/mdx/picache.conf
3.1 "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.
3.2 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.
3.3 "dm-program" needs to point to valid p4 executable
4. Start IPLM Cache daemons
   service iplm-backend-redis start
   service iplm-backend-mongodb start
   service picache start
5. To stop IPLM Cache, run:
   service picache stop
   Note: IPLM Cache can normally be stopped/restarted alone, without having to stop
         iplm-backend-redis/iplm-backend-mongodb
   Note: In case iplm-backend-redis/iplm-backend-mongodb needs to be shut down, stop picache first
6. To start IPLM Cache automatically after reboot, run
   chkconfig iplm-backend-redis on
   chkconfig iplm-backend-mongodb on
   chkconfig picache on

IPLM Cache upgrade

Update IPLM Cache on system that has IPLM Cache installed already
1. As root, run:
   zypper up -y iplm-cache
   Note: the iplm-cache-lib package will be updated automatically, if needed

IPLM PiForce installation

Perforce IPLM PiForce server is installed as standard Linux package using the 'zypper' command.

1. Install IPLM PiForce package
   zypper in -y iplm-piforce

2. Review/update IPLM 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
3. Start/stop IPLM PiForce daemon
   service piforce start
   service piforce status
   service piforce stop
4. To start IPLM PiForce automatically after reboot, run
   chkconfig piforce on

PiForce upgrade

Update IPLM PiForce on system that has IPLM PiForce installed already
1. As root, run:
   zypper up -y iplm-piforce