Migrating to IPLM Core 2024.1

IPLM Core 2024.1 is a major upgrade with new infrastructure, features, and functionality. Contact your Account Executive to schedule your migration to this new release.

Provision a dedicated server for this process, and follow the instructions for a new installation in IPLM package installation. At a minimum, install Java-11, Neo4j 4.4, IPLM Server, and IPLM Client. Read and understand all of the following procedures and instructions, and please contact Perforce Support with any questions or concerns prior to proceeding.

IPLM Core feature changes and current limitations

  • The PiServer license must be reinstalled after the migration.

  • Server-side hooks have been moved from the neo4j.conf file to the piserver.yml file in this release. Please reference the validation section of the piserver.yml file.

  • Some operations may be slower the first time they are performed due to a query plan being created by the database. Subsequent calls to that operation should be faster after the query has been cached.

  • When file lists are stored, they are compressed immediately in a synchronous operation, rather than being done asynchronously. This may cause a performance issue for very large file lists.

  • Property values are now much more strongly typed. Searches must take this into account. A search for var=5 and var='5' will give different results.

  • The PUT /public/v1/iplvs API endpoint now requires a uc field to be specified to prevent updating stale data.

  • DELETE endpoints for the public API no longer return an empty links attribute in the response payload. This was previously returned, but was always empty.

  • DELETE endpoints for the public API now return information in the response payload on the resource that has just been deleted.

Next steps

Video

To learn how to migrate to IPLM Core 2024.1, watch this video.