Configuring IPLM Server for migrating to IPLM Core 2024.1

On the new IPLM Server Neo4j host:

1. Configure the piserver.yml file using the example below. In this initial configuration with no clustering or use of HA Proxy, IPLM Server is connecting directly to the Neo4j 4.4.X database using the Bolt protocol. If you installed Neo4j during IPLM Server installation, do not alter the password. Otherwise, set a password that matches the password set in step 6 of Installing and configuring Neo4j 4.4 for migrating to IPLM Core 2024.1.

   Copy

   neo4jDriver:
       # URI of the Neo4j server
       uri: "bolt://localhost:7687"
       # Neo4j credentials
       # Note that both username and password can be read from an external file.
       # The external file can have more restricted access. But it needs to be
       # readable by piserver, which by default is owned by mdxadmin.
       username: neo4j
       password:  neo4j

2. Update the Security section of the piserver.yml file with these settings:

   Copy

   # ------------------------------------------------------------------------------
   # Security
   # ------------------------------------------------------------------------------
   
   security:
       # Time a user session can be idle before it is invalidated
       # If set to 0, user sessions never expire
       accessTokenExpirationTime: 0 seconds
       #externalSynchronization:
           # The absolute location of the external synchronization file (must be executable)
           #file: FILE
           # The charset used by the output of the external synchronization
           #outputCharset: UTF-8
           # The external synchronization execution timeout
           #executionTimeout: 1 minute
       externalAuthentication:
           # The absolute location of the external authentication file (must be executable)
           file: /bin/true
           # The charset used by the input of the external authentication
           #inputCharset: UTF-8
           # The external authentication execution timeout
           executionTimeout: 5 seconds

3. Verify the databaseUpdateTimeout setting. Depending on the size of your database, you may need to increase this setting to 60 minute or even larger.

   Copy

   # The database update timeout
   #databaseUpdateTimeout: 10 minute
   databaseUpdateTimeout: 30 minute

4. PiServer automatically starts IPLM Server and Neo4j by default. However, PiServer and Neo4j can be started and stopped independently if desired, like a typical HA Production deployment. To decouple IPLM Server and Neo4j, set neo4j-local=no in /etc/mdx/piserver.conf.

   Use the following command to start IPLM Server:

   Copy

   # systemctl start piserver

5. Once IPLM Server successfully starts, monitor piserver-error.log for messages indicating the schema is being upgraded. Schema migration processing varies depending on the size of your database, so make sure you monitor the log before proceeding. Here is an example:

   Copy

   INFO  [2023-12-11 23:45:49,821] org.eclipse.jetty.server.Server: Started Server@4fa86cb8{STARTING}[10.0.14,sto=30000] @4696ms
   INFO  [2023-12-11 23:45:49,852] com.perforce.iplm.piserver.neo4j.driver.update.DatabaseUpdater: Updating database
   INFO  [2023-12-11 23:45:50,507] com.perforce.iplm.piserver.neo4j.driver.update.DatabaseUpdater: Executing migration 53 to upgrade database schema from version 52 to version 53
   INFO  [2023-12-11 23:45:50,686] com.perforce.iplm.piserver.neo4j.driver.update.DatabaseUpdater: Executing migration 54 to upgrade database schema from version 53 to version 54
   INFO  [2023-12-11 23:45:51,045] com.perforce.iplm.piserver.neo4j.driver.update.DatabaseUpdater: Current database schema version is 58, which is the latest supported version
   INFO  [2023-12-11 23:45:51,045] com.perforce.iplm.piserver.neo4j.driver.update.DatabaseUpdater: Database updated (executed migrations: [53, 58])

Next steps

After installing and configuring IPLM Server, install IPLM CLI. See Installing IPLM CLI for migrating to IPLM Core 2024.1.