The latest delivered MongoDB version is 4.2. It can be used by the latest U9, V11 and V12 Syracuse releases.
Important: You must be running MongoDB 4.0 to upgrade to MongoDB 4.2.
Sage delivers a MongoDB setup to upgrade your MongoDB instance.
For each release, the minimum Syracuse upgrades compatible with MongoDB 4.2 are the following:
|Product version||Minimum Sage X3 Syracuse Server version|
Upgrade your MongoDB instance
Upgrade from MongoDB 4.0
- Starting in version 4.2, MongoDB removes the deprecated MMAPv1 storage engine. If upgrading to MongoDB 4.2 from a MongoDB 4.0 deployment that uses MMAPv1, you must upgrade to WiredTiger.
To check if your mongo deployement uses MMAPv1 please run this command in your mongo client db.serverStatus().storageEngine
If you are in MMAPv1 you must to do the following steps before upgrading
- export your data usingmongodump command
- stop the mongodb server
- remove all files from mongodb data directory
For more informations about WiredTiger migration please follow this link
- Launch the MongoDB 4.2 setup. Use the reinstallation procedure
If you previously mongodb instance was in MMAPv1 (see step 2) you must restore the saved data using mongorestore command
- If you are using a Java Oracle platform and if the MongoDB server will use an SSL connection, you need to :
- Be at at least on Java 8 update 151.
- Add Java Bouncy Castle to the security providers’ list on your platform:
- Unzip the content of the bcprovider.zip file to the $JAVA_HOME/jre/lib/ext/ directory.
- Register the Bouncy Castle provider by adding the security.provider.=org.bouncycastle.jce.provider.BouncyCastleProvider line in the $JAVA_HOME/jre/lib/security/java.security file.
- Check in $JAVA_HOME/jre/lib/security/java.security that your crypto policy is set to unlimited: crypto.policy=unlimited.
- If the original installation was set only to accept secure connection, pay attention to The server uses and accepts only SSL encrypted connections option.
- Restart your Sage X3 Syracuse Server.