Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  MAS Migrate Attachments with same folder structure using mxe.cosnestedfile = 1

    Posted Mon April 28, 2025 10:56 PM

    Hi Team, 

    Did anyone migrate attachments from file server in Maximo 7.6.x to MAS 9.0.8 Amazon S3 with same folder structure by setting a new system property mxe.cosnestedfile = 1  ? 

    We tried using this property mxe.cosnestedfile = 1 and migrated the existing attachment using same folder structure. MAS is not able to open the document, but we are able to read the document using the standalone automation script. We have set the docinfo.urlname to correct one. 

    The documents uploaded to root bucket from maximo is working fine. But not the migrated documents inside folders. 

    We think it might be a product bug. Kindly provide any inputs. 

    Thanks,

    Suren



    ------------------------------
    Surender Balasundaram
    Asset Data Coordinator
    Downer
    Sydney NSW
    ------------------------------


  • 2.  RE: MAS Migrate Attachments with same folder structure using mxe.cosnestedfile = 1

    Posted Tue April 29, 2025 06:46 PM

    Hi Surender,
    I have not tried this property so I am just guessing you are following steps in the article https://www.ibm.com/support/pages/collecting-data-s3-storage-attachments, right?
    What do you get in the Maximo logs?
    If you turn on a development mode in the browser, do you get any error?

    Regards, Alexey



    ------------------------------
    Alexey Potanin
    ------------------------------

    Original Message


  • 3.  RE: MAS Migrate Attachments with same folder structure using mxe.cosnestedfile = 1

    Posted Wed April 30, 2025 04:10 AM

    Hi Alexey, 

    We have enabled the doclinks log, but it shows all the path and filename correctly. 

    But, we think it might be a product bug on OOB class class file - com.ibm.tivoli.maximo.oslc.provider.COSAttachmentStorage method getAttachment. It is not able to find the fileName if there are nestedFolder of more than 1 hierarchy. 

    So, we want to check with the community if anyone has migrated the documents from mx 7.6 NFS folder to MAS - Amazon s3 bucket with same folder structure along with mxe.cosnestedfile = 1

    Thanks,

    Suren



    ------------------------------
    Surender Balasundaram
    Asset Data Coordinator
    Downer
    Sydney NSW
    ------------------------------

    Original Message


  • 4.  RE: MAS Migrate Attachments with same folder structure using mxe.cosnestedfile = 1

    Posted Wed April 30, 2025 08:14 AM

    I tried using this property without success. As you stated, all documents are stored in the root bucket only.

    When I asked about sub (nested) folders in the root bucket, IBM informed me that it is not supported.

    Our current setup utilizes MAS version 9.0.x with NFS storage. We are in the process of transitioning to S3 storage.



    ------------------------------
    Prashanth
    Atlanta
    ------------------------------

    Original Message


  • 5.  RE: MAS Migrate Attachments with same folder structure using mxe.cosnestedfile = 1

    Posted Thu May 01, 2025 12:08 AM

    Hi Prashanth, 

    Thanks for confirming the limitation. 

    Did IBM Product team plan to accept it as defect and work on fix ? or there is no way we can maintain the sub-folder structure for migrated documents in MAS from MX 7.6 NFS storage ? 

    It looks like we need to rename the files and upload them under root document with updating docinfo.urlname to new values. 

    Thanks,

    Suren



    ------------------------------
    Surender Balasundaram
    Asset Data Coordinator
    Downer
    Sydney NSW
    ------------------------------

    Original Message


  • 6.  RE: MAS Migrate Attachments with same folder structure using mxe.cosnestedfile = 1

    Posted Wed April 30, 2025 07:28 PM

    Hi guys,

    Based on the article, IBM clearly states that mxe.cosnestedfile property (to support S3 bucket with folders) is working only for migrated attachments

    It is important to notice that S3 for attachments does not support to upload new attachments to folders and sub-folders. The files are always uploaded to the root of the COS. That makes the maintenance of Manage Folders path not necessary, as this information is not considered for COS configuration. S3 expects all files to be in the top level directory as a result any files in lower directory levels will not be found by Maximo.

    Existing files that were migrated from older Maximo environments with the original sub-folders structure may be located by Manage in S3. To deal with this set the mxe.cosnestedfile system property to 1. This allows documents in lower directories to be found by Manage.

    Though I still don't understand how you could get a folder structure with S3 bucket as a storage for attachments :(


    For people moving from NFS to S3 bucket I would recommend reading following article: https://www.naviam.io/resources/blog/prepare-for-mas-utilizing-s3-storage-for-attached-documents-in-7-6-1



    ------------------------------
    Alexey Potanin
    ------------------------------

    Original Message


  • 7.  RE: MAS Migrate Attachments with same folder structure using mxe.cosnestedfile = 1

    Posted Wed April 30, 2025 09:17 PM

    Hi Alexey, IBM article for mxe.cosnestedfile is not working as expected as per the documentation. 

    What we are planning to achieve is mx 7.6 C:\docklinks\Attachments  to MAS 9 S3 <RootBucket>/Attachments folder. Amazon S3 allows us to create sub-folders from Bucket and makes the sub-folder name as part of key of that file. 

    In your recommended article, they are renaming the file in NFS and uploading it in root bucket, instead of creating a sub-folder Attachments. What we think it IBM is not supporting the sub-folders and we won't be able to retain the same folder structure as in NFS for migrated documents. It is confirmed by Prashanth in above thread. 

    Thanks,

    Suren



    ------------------------------
    Surender Balasundaram
    Asset Data Coordinator
    Downer
    Sydney NSW
    ------------------------------

    Original Message


  • 8.  RE: MAS Migrate Attachments with same folder structure using mxe.cosnestedfile = 1

    Posted Fri May 09, 2025 04:36 PM

    Might want to look at doing this:

    UPDATE MAXIMO.DOCINFO SET URLNAME = REPLACE(URLNAME, 'doclinks/', 'cos:doclinks/') WHERE URLNAME LIKE 'doclink'

    I'm doing the same thing 7.x to 9x .. mount point on nfs to s3 bucket.  I was told by support I will need to do this after I setup the S3 bucket in mas9.  and you need mxe.cosnestedfile system property to 1

    It will be able to find your old files, but any new files will be flat file and managed by the application virtually.



    ------------------------------
    Stephen Wheet
    ------------------------------

    Original Message


  • 9.  RE: MAS Migrate Attachments with same folder structure using mxe.cosnestedfile = 1

    Posted Fri May 09, 2025 05:01 PM

    Hello Surender,   it sounds like you are able to upload/store new documents in 1 level, eg <RootBucket>/Attachments folder rather than root.  How do you archive that?  So far were only able to get the attachments uploaded to the bucket root.   

    IBM support did tell me about the mxe.cosnestedfile as well, and it only works with migrated documents.  I see you were able to migrate your documents with nested folder structure to s3,  is there any tool to do that?  I tried to use OOTB file2s3 script,  but it really does not work well with -w parameter,  plus this tool will flaten and move all files to 1 level in my case root.



    ------------------------------
    jiang monge
    ------------------------------

    Original Message


Related Content