Troubleshooting global property values

When migrating a Maximo® SaaS Flex 7.6.1.2 database, you might see an error in the mxe.int.globaldir property value.

Symptoms

If you have a database in Maximo SaaS Flex 7.6.1.2 and want to refresh this database to Maximo Application Suite, you might see the following error in the mxe.int.globaldir property value.

[Default Executor-thread-7] ERROR maximo.graphite - [DatabaseResourceLoader] Expand App manage-shell failed. 
Message: /opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/MAXIMO_b1dk/maximo/maf/manage-shell/8.0.0.0-0/app-source.zip
java.nio.file.NoSuchFileException: /opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/MAXIMO_b1dk/maximo/maf/manage-shell/8.0.0.0-0/app-source.zip
\tat sun.nio.fs.UnixException.translateToIOException(UnixException.java:92) ~[?:?]
\tat sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) ~[?:?]
\tat sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116) ~[?:?]

Causes

In your database, the mxe.int.globaldir property value is set to something that does not exist in the image.

Resolving the problem

Make sure that the globaldir value is either a mounted persistent volume, or it is a directory that already exists in the image because it is used as a default system directory. If you want to temporarily use a non persistent volume by default, set the value for mxe.int.globaldir as blank or null.

You can also set the environment variable through the MAF_APP_ROOT encryption property. For example, set MAF_APP_ROOT to /tmp.

Attention: Any Maximo properties that refer to a directory or doclink root must be validated. If you need persistence, a Persistent Volume must be mounted to host that directory, or, point to any existing writable directory, for example, any sub-folder under /tmp.