Installing and configuring Neo4j 4.4 for migrating to IPLM Core 2024.1
On the new server host, use these steps to install, configure, and migrate the Neo4j database for IPLM Core 2024.1.
By default, Neo4j 4.4 is installed and configured during PiServer package installation. If you chose to not install Neo4j 4.4 along with IPLM Server, you can follow steps 1-3 below to install it manually. If Neo4j 4.4 was installed with IPLM Server, start with step 4 below.
-
Install Neo4j 4.4.35.
Copy# cd /opt
# tar zxvf /<downloadPath>/neo4j-enterprise-4.4.18-unix.tar.gz -
Copy Neo4j certificates from the 3.5.9 installation to the 4.4.x installation. In this example, the 3.5.9 database installation is at
/var/lib/neo4j/. Your database installation location may vary. Replace <old_neo4j_host> with the hostname or IP address of the machine hosting the PiServer 3.5.9 database.Copy# scp <old_neo4j_host>:/var/lib/neo4j/certificates/* /opt/neo4j-enterprise-4.4.18/certificates -
Create the neo4j.conf configuration file.
Start with the original Neo4j 4.4.X
neo4j.conffile and add the specific settings required for the system. Replace the IP address below with the correct address for the system, and choose a location for your dbms.directories subfolders. Make sure those subfolders exist and can be written to by the user ID that will be running the Neo4j server, typicallyneo4j:neo4j.In this example, most of theneo4j.confdefaults are used, and no clustering parameters are included.Copydbms.default_database=neo4j
dbms.allow_upgrade=true
dbms.connector.bolt.enabled=true
dbms.default_listen_address=0.0.0.0
dbms.default_advertised_address=10.5.10.98
dbms.security.auth_enabled=true
dbms.tx_log.rotation.retention_policy=1 files
dbms.tx_log.rotation.size=1048576
dbms.directories.logs=/var/log/mdx-neo4j
dbms.directories.run=/var/run/mdx-neo4j
dbms.directories.data=/var/lib/mdx-neo4j/data -
Migrate the database from 3.5.9 to 4.4.35.
All neo4j-admin calls must be run as the user that will run the Neo4j server instance (typically neo4j:neo4j or neo4j:adm).Save a copy of ALL your log files in case Perforce must review. If you installed Neo4j during IPLM Server installation,
<neo4j_install_dir>will be:/usr/share/mdx/neo4j.If the graph.db does not reside on a filesystem accessible to this server, you must either create an NFS mount point or copy it to a local filesystem.
Use the following command to perform the migration:
Your paths to the transactions and databases subfolders may vary based upon thedbms.directories.datasetting in yourneo4j.conffile.Copy# <neo4j_install_dir>/neo4j-enterprise-4.4.18/bin/neo4j-admin copy --from-path=/path_to_neo4j_3x_home_directory/data/databases/graph.db --to-database=neo4jIgnore the instructions to manually CREATE BTREE INDEX entries. IPLM Server handles this step for you.If you need to re-do theneo4j-admin copycommand for any reason, you must rename the following directories and create new empty directories:/opt/neo4j-enterprise-4.4.35/data/transactions/opt/neo4j-enterprise-4.4.35/data/databases -
Verify that the
neo4j-admin copywas successful. Use one of these two options:-
Confirm the
neo4j-admin copyreturn code (echo $?) is 0 (zero) or -
Send a copy of the copy log to Perforce Technical Support
-
-
If you installed Neo4j with IPLM Server, this step is not required.
Once the copy results have been reviewed by Perforce Technical Support, set the desired password for the new database BEFORE starting the Neo4j server for the first time (a password of “neo4j” is used in this example):
Copy# <neo4j_install_dir>/neo4j-enterprise-4.4.18/bin/neo4j-admin set-initial-password neo4j -
Start Neo4j with the following command:
Copy# <neo4j_install_dir>/neo4j-enterprise-4.4.18/bin/neo4j start
Neo4j is started stand-alone. Review the Neo4j log files to verify that the database comes up intact and looks valid. Neo4j and IPLM Server are started and stopped independently.
To stop the Neo4j service, use the following command:
# <neo4j_install_dir>/neo4j-enterprise-4.4.18/bin/neo4j stop
Next steps
After installing and configuring Neo4j for IPLM Core 2024.1, see Configuring IPLM Server for migrating to IPLM Core 2024.1.