Hi Pradnya,
I agree with having a consistent migration strategy, but in this case, it is not MXLoader as it does not support your use case.
There is nothing wrong with using MXLoader as your prime migration tool, however, there will be times when you must use the most appropriate tool and document your strategy so that everyone knows what that is. Every tool has its issues, use cases, and ease of use.
I'm going to assume a number of things that I hope you've looked into:
- Should the data be stored in a flat/xml/other format or transferred directly from one DB to the next? For example, using migration manager.
- Should the file go through a check-in/out CVS type system?
- How easy is it to export that data?
- How easy is it to import that data?
- What level of error checking is needed?
- Can I wipe the imported data if needed so I can do a clean import?
- Who does the export?
- Who does the import?
- What checks are needed to validate that the import is successful?
- What is the most appropriate tool to use?
- ...
None of that should be a surprise. There are many ways to export/import, but in general, you want to ensure that you have ALL of the required data. Some of the tools don't do this and require some knowledge of data sources to get right.
One instance where (for myself) I would use the Migration Manager is for Workflow. This is because when it is imported, Maximo will generate a new revision and disable/deactivate it, but even so, I've had to modify the standard (read as copy and edit) of the OOTB migration groups as it does not cover all the area needed to make Workflow work.
So what are the tools that are available?
- DBC scripts. Built in via the command line. Great for DB changes including if you have a whole new application with a new object(s).
- Migration Manager. Built in via the UI. Can capture a point-in-time or progressive change. Can migrate via a file or directly to another DB, but they must be at the same patch level (though this can be overcome if needed)
- Maximo Integration Framework. Built-in. Can export to a file, can import from a file, plus many more options.
- SQL. Nope, don't do this.
- ODBC. MS-Excel or MS-Access for instance. Nope, don't do this.
- MXLoader. A great 3rd-party tool.
- Command line for exporting/importing reports. Usually where you have bulk reports that you've customized or created, rather individually.
There are more, just not listed, sorry. A lot of the tools do require knowledge of where the data is coming from, and that takes time to build up the knowledge. Some of the tools cause issues, though unknown at the time, with ID's being allocated, yet Maximo was not told about them (MAXSEQUENCE or SEED values).
In the end, don't become blinded by using only one tool, especially when it just does not meet your needs. I hope that this gives you some thought.
------------------------------
Regards,
Craig Kokay
ISW
Maximo Practice Manager
eMail:
ckokay@isw.net.auPhone: +61-411-682-040
#IBMChampion2023
------------------------------
Original Message:
Sent: 06-28-2023 01:02
From: Pradnya Maximo
Subject: MXLoader for custom report
@Matt McGuire Manual export/import options is there in our list, but we were trying to be consistent with migration strategy as we are planning all other components with MXLoader.
Thank you!
------------------------------
Pradnya Maximo
EY GDS
Original Message:
Sent: 06-27-2023 12:15
From: Matt McGuire
Subject: MXLoader for custom report
I suppose you could use Application Export to export into a CSV file. What is your end goal?
------------------------------
Matt McGuire
Aquitas Solutions
https://www.aquitas-solutions.com/
Original Message:
Sent: 06-27-2023 10:34
From: Pradnya Maximo
Subject: MXLoader for custom report
HI @Matt McGuire , thank you for your response.
I guess, you are correct. I see the length of the exported xml is 33687.
One follow-up question please, do you have any other suggestion for report migration than MXLoader and Migration Manager?
------------------------------
Pradnya Maximo
EY GDS
Original Message:
Sent: 06-27-2023 10:03
From: Matt McGuire
Subject: MXLoader for custom report
Hi Pradnya,
What's the length of the value you received? Excel cells have a limit of 32,767 characters so this may be an excel limitation.
For example, the asset_availability.rptdesign has 46,964 characters (I exported to word and did a character count) but when I run MxLoader on the MXL_REPORTDESIGN OS I only get the 32,767 characters which is as expected based on Excel's limitations.
Thanks,
------------------------------
Matt McGuire
Aquitas Solutions
https://www.aquitas-solutions.com/
Original Message:
Sent: 06-26-2023 03:16
From: Pradnya Maximo
Subject: MXLoader for custom report
Hi Team, Greetings for the day!
We are trying to utilize MXLoader with MAS instance to extract custom report.
We see, there is no object structure in MAS to export report definition along with design, params, security configurations etc. SO tried creating OS MXL_REPORTDESIGN(as this is available in MXLoader) with just 2 objects primary - REPORTDESIGN.
WIth this, reqport is getting queried fine but the deisgn xml extract is partial. It is not extracting complete report design xml.
Would like to ask if any specific properties are there we need to setup before we could extract BIRT report successfully in MXLoader? Any suggestion/input is much appreciated. Thank you
@Bruno Portaluri
#EverythingMaximo
------------------------------
Pradnya Maximo
EY GDS
------------------------------
------------------------------
Pradnya Maximo
EY GDS
------------------------------