So yet again IBM documentation is terrible at guiding how to do something in MAS9. I am trying to follow this guide to setting the system properties for my Attached Documents in a MAS9 Environment using an NFS Volume linked to a PVC/PV

https://www.ibm.com/docs/en/mas-cd/maximo-manage/8.3.0?topic=documents-configuring-system-properties-persistent-storage

I followed this guide to setup the PVC/PV
How to create a Persistent Volume Claim (PVC) on Manage

I actually used the exact same values in the above guide to make sure I matched their stuff identically just using different sizes and my Storage Class that I had earlier created. It had the following settings in the Update Configuration of MAS:

MOUNTPATH     PVC name            Size        Storage Class name          Volume name

/doclinks              doclinks                100Gi    managed-nfs-storage

/mif                       mif                         10Gi       managed-nfs-storage

Having these 2 things it then created 2 folders on my NFS Volume with the huge paths:

/volume2/Attachments/mas-inst1-manage-inst1-work1-doclinks-pvc-09ca10ce-f1d7-4c62-828c-2daed85bf7d9

/volume2/Attachments/mas-inst1-manage-inst1-work1-mif-pvc-712373d8-ee32-45a5-a041-bde326107931

Anything that can be done about these names? They pretty unwieldy?

This process created 2 PVC records in my OS - inst1-work1-doclinks   &  inst1-work1-mif

So going back to the Properties Guide it is not clear what I do with these values to make my setup work its says to set

mxe.doclink.doctypes.defpath = /d01/doclinks

Would this then be my fully qualified path above?

mxe.doclink.doctypes.defpath = /volume2/Attachments/mas-inst1-manage-inst1-work1-doclinks-pvc-09ca10ce-f1d7-4c62-828c-2daed85bf7d9/

Next they say to do the

mxe.doclink.doctypes.topLevelPaths = \doclinks

Would this be same for me?

mxe.doclink.doctypes.topLevelPaths = \doclinks

or do I use my monster path

mxe.doclink.doctypes.topLevelPaths = /mas-inst1-manage-inst1-work1-doclinks-pvc-09ca10ce-f1d7-4c62-828c-2daed85bf7d9

And finally they say to do the

mxe.doclink.path01 = /d01/doclinks=https://host/doclinks

Would this be using my NFS Server IP

mxe.doclink.path01=/volume2/Attachments/mas-inst1-manage-inst1-work1-doclinks-pvc-09ca10ce-f1d7-4c62-828c-2daed85bf7d9= https://192.168.1.14/mas-inst1-manage-inst1-work1-doclinks-pvc-09ca10ce-f1d7-4c62-828c-2daed85bf7d9

Again, these guides are terrible at explaining how to deal with this in different situations.

Really need help figuring this out as I am trying all kinds of combinations of values and nothing is working. I see the PVC/PV there just cant seem to use them successfully.

Better documentation would be an ingenious idea. I cant be only person using NFS for Attached documents.

Thanks in advance for any help I can get,

------------------------------
David Miller
Managing Partner - Maximo Consultant
Enterprise Integration Partners LLC
------------------------------

Hi David,

no need to worry about the folder names that were created on Your NFS server. These PVCs are 'visible' to the Pod under the mountpath, so /doclinks or /mif. In Your case the system properties would look like this:

mxe.doclink.doctypes.defpath = /doclinks
mxe.doclink.doctypes.topLevelPaths = /doclinks
mxe.doclink.path01 = /doclinks=https://<your MAS Manage route>/maximo/oslc/doclinks
mxe.doclink.securedAttachment = true

The 'beauty' of using PVCs in OpenShift is that You do not care about what the backing storage is. You can use Ceph, vSphere CSI, EFS, Azure Files or NFS or any RWX capable storage class and the config on Manage side would always look the same.

------------------------------
Witold Wierzchowski
Solution Architect
Cohesive Poland
------------------------------

Witold, thank you for your response. I apologize for the delayed response but I was going round and round with IBM support. They finally got me to this link that ended up being the solution:
https://www.ibm.com/support/pages/how-configure-attachment-using-pvc-maximo-it

I finally ended up doing a full re-install of MAS from scratch which I am getting pretty good at (I have 19 servers in Archive now on RH..lol).  But I have it up and running and the attachments are pretty much working.

Your recommendations were close but not exact at least per my setup. Not sure if is my Synology NAS or not but I ended up needing to put the volume name (volume2) of my NFS share in my paths to get my stuff working. This is the cofiguartion that ended up working for me... The last thing I am working to resolve with IBM is the attachments are downloading when I open and not opening in a Tab. It was a known issue by IBM and they sent me this link but the property came in as true on this most recent install and it still does not work:
https://www.ibm.com/mysupport/s/defect/aCI3p000000Xm3h/dt223586?language=en_US


Her is setup that works for me:

------------------------------
David Miller
Managing Partner - Maximo Consultant
Enterprise Integration Partners LLC
------------------------------

Original Message:
Sent: Thu September 19, 2024 01:32 AM
From: Witold Wierzchowski
Subject: Setting up MAS9 Attached Documents using NFS Volume

Hi David,

no need to worry about the folder names that were created on Your NFS server. These PVCs are 'visible' to the Pod under the mountpath, so /doclinks or /mif. In Your case the system properties would look like this:

mxe.doclink.doctypes.defpath = /doclinks
mxe.doclink.doctypes.topLevelPaths = /doclinks
mxe.doclink.path01 = /doclinks=https://<your MAS Manage route>/maximo/oslc/doclinks
mxe.doclink.securedAttachment = true

The 'beauty' of using PVCs in OpenShift is that You do not care about what the backing storage is. You can use Ceph, vSphere CSI, EFS, Azure Files or NFS or any RWX capable storage class and the config on Manage side would always look the same.

------------------------------
Witold Wierzchowski
Solution Architect
Cohesive Poland
------------------------------

FYI:  mxe.doclink.attachmentOpenMethod is what was causing the attchments to download always and not open in a Tab of browser.  Setting it to inline make it open a new Tab.

APAR	Change instructions
DT223586	Set the system property mxe.doclink.attachmentOpenMethod to inline or attachment depending on desired results (Inline: file opens in browser. Attachment: file downloads)

------------------------------
David Miller
Managing Partner - Maximo Consultant
Enterprise Integration Partners LLC
------------------------------

Original Message:
Sent: Mon September 23, 2024 08:48 AM
From: David Miller
Subject: Setting up MAS9 Attached Documents using NFS Volume

Witold, thank you for your response. I apologize for the delayed response but I was going round and round with IBM support. They finally got me to this link that ended up being the solution:
https://www.ibm.com/support/pages/how-configure-attachment-using-pvc-maximo-it

I finally ended up doing a full re-install of MAS from scratch which I am getting pretty good at (I have 19 servers in Archive now on RH..lol).  But I have it up and running and the attachments are pretty much working.

Your recommendations were close but not exact at least per my setup. Not sure if is my Synology NAS or not but I ended up needing to put the volume name (volume2) of my NFS share in my paths to get my stuff working. This is the cofiguartion that ended up working for me... The last thing I am working to resolve with IBM is the attachments are downloading when I open and not opening in a Tab. It was a known issue by IBM and they sent me this link but the property came in as true on this most recent install and it still does not work:
https://www.ibm.com/mysupport/s/defect/aCI3p000000Xm3h/dt223586?language=en_US


Her is setup that works for me:

Again, thank you for your repsonce and you got me pointed in correct direction

------------------------------
David Miller
Managing Partner - Maximo Consultant
Enterprise Integration Partners LLC
------------------------------


Original Message:
Sent: Thu September 19, 2024 01:32 AM
From: Witold Wierzchowski
Subject: Setting up MAS9 Attached Documents using NFS Volume

Hi David,

no need to worry about the folder names that were created on Your NFS server. These PVCs are 'visible' to the Pod under the mountpath, so /doclinks or /mif. In Your case the system properties would look like this:

mxe.doclink.doctypes.defpath = /doclinks
mxe.doclink.doctypes.topLevelPaths = /doclinks
mxe.doclink.path01 = /doclinks=https://<your MAS Manage route>/maximo/oslc/doclinks
mxe.doclink.securedAttachment = true

The 'beauty' of using PVCs in OpenShift is that You do not care about what the backing storage is. You can use Ceph, vSphere CSI, EFS, Azure Files or NFS or any RWX capable storage class and the config on Manage side would always look the same.

------------------------------
Witold Wierzchowski
Solution Architect
Cohesive Poland