Maximo Open Forum

 View Only

 Deploying MAF Application Changes Across Environments

  • Maximo Application Suite
Kasey Dixon's profile image
Kasey Dixon posted 10-14-2025 14:26

Hello,

I've recently been working within the MAF to customize some of the OOB applications. In this case, I've made some adjustments to the TECHMOBILE app. I would like to "deploy" these changes to another environment. In order to do so, I've been following the walkthrough found here: Migrating Maximo Mobile Changes - A Migration Manager Use Case

Linkedin remove preview
Migrating Maximo Mobile Changes - A Migration Manager Use Case
Having customized the TECHMOBILE app to a very significant level, the changes were scattered within app.xml, AppCustomization.
View this on Linkedin >


I've created the object structure as well as the migration group in the source environment as outlined above. (Note: I named the OS / MG M4MAPPDATA instead of MAFAPPDATA)

In order to deploy only the most recent version of the TECHMOBILE app, I set the following where clause:

I've confirmed that this where clause should result in only 1 row being returned from the database, and that there are no dependent object structures in the migration group:



All seemed to be going as intended, as I was able to successfully create and download my initial test package:


However, upon uploading this package to the other environment, I was met with the following message:


I thought this was odd, as I wouldn't expect the single app to contain more than 10MB of information. However, upon exploring the ZIP file, I see that this is likely the case:


Now, theoretically, I could simply increase the file size that is allowed for attachments. However, for lack of a better analogy, this feels like kicking the can down the road. If the app, or customizations within, were to grow in size, this problem would be reached again.

My question is: Is there a different way that is recommended to move customizations to the mobile apps from one environment to another? Have I missed something in my setup for the migration groups / object structure to facilitate this process?

I'm happy to provide more information as needed, just let me know!


Thank you,
Kasey Dixon

FREDRICK NDWARU's profile image
FREDRICK NDWARU posted 10-15-2025 10:35

Hi Kasey, 

Thank you for providing sufficient supporting context to address the issue you are facing. 

The root cause of the Error you are encountering is that the file you are attempting to upload exceeds the current file size limit of 10 MB. The updated file is 12.964 MB.

Options to resolve the issue:

  1. Option 1 - Property Name: mxe.doclink.maxfilesize from 10 to a size greater than 12.964 MB. Please see the attached step. 
  2. Option 2 - Migrate the package using Migration Manager APIs.
    • IBM Maximo REST API Guide Link - https://ibm-maximo-dev.github.io/maximo-restapi-documentation/migrationmanager/api 
    • For Option 2, POSTMAN is an appropriate API tool 
    • Migration Manager API high-level summary: 
      • Migration manager APIs (part of 7613 and 8.x) help move migration packages from a source maximo to target environments in Maximo.
      • To facilitate this, IBM developed a set of REST APIs accessible from the provided link
      • Note that these APIs were designed to handle MM Changes and Snapshot, and not migration collections at this point.
      • Also note that these APIs are not designed to define a package, which should be configured by a technical SME as part of MM setup.
Attachment  View in library
Option 1 - Increase MM mxe.doclink.maxfilesi...txt 4 KB
Kasey Dixon's profile image
Kasey Dixon posted 10-20-2025 11:13

Hey Frederick,

I appreciate your response, thank you! Unfortunately, I've hit a little bit of a hiccup. According to the documentation that you listed for option 2, the Migration Manager API is only for Maximo 7.6 and 8.x. Apologies for neglecting to mention the version in my original post, but I am making these changes to an instance running on version 9.0.

Is there an equivalent API for MAS9 instances, or another alternative to increasing the file size? The more I've read, the more that an increased allowed file size will be the path forward... just wanted to check.

Thank you very much!

Related Content