This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Hi,
We have Maximo 6.2.5 with a lot of MBO customizations. Can someone comment on how painful or easy it is to migrate such environment to Maximo 7? More specifically:
Did the API change much?
Can customized Java code be "plugged-in" or does most of it have to be re-written?
Are there any issues with migrating customized screens?
Any other issues are commond during migrations and what factors are important to consider?
Thanks in advance!
We are in the middle of the same upgrade right now. We have a heavily customized application with around 170 custom classes. The migration from 6 to 7 only required one minor change to a custom Java class. I did take the opportunity to do some cleanup, JavaDoc documentation and best practices type stuff while I was in there, but as far as the Java itself, it was almost completely plug and play.
Thanks!
-Chris H
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlofny
Sent: Wednesday, June 29, 2011 10:18 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Migration from MX 6 TO MX 7
Hi,
We have Maximo 6.2.5 with a lot of MBO customizations. Can someone comment on how painful or easy it is to migrate such environment to Maximo 7? More specifically:
Did the API change much?
Can customized Java code be "plugged-in" or does most of it have to be re-written?
Are there any issues with migrating customized screens?
Any other issues are commond during migrations and what factors are important to consider?
Thanks in advance!
Thanks Chris. That makes me feel a lot more optimistic. If it's not a long story, what kind of change did you have to make to that one custom java class? I am curious because it's the only change that you had to make.
I hope others had equally pain-free experience.
--- In MAXIMO@yahoogroups.com, "Hanna, Christopher CTR" <christopher.a.hanna@...> wrote:
>
> We are in the middle of the same upgrade right now. We have a heavily customized application with around 170 custom classes. The migration from 6 to 7 only required one minor change to a custom Java class. I did take the opportunity to do some cleanup, JavaDoc documentation and best practices type stuff while I was in there, but as far as the Java itself, it was almost completely plug and play.
>
> Thanks!
>
> -Chris H
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlofny
> Sent: Wednesday, June 29, 2011 10:18 AM
> To: MAXIMO@yahoogroups.com
> Subject: [MAXIMO List] Migration from MX 6 TO MX 7
>
>
>
> Hi,
>
> We have Maximo 6.2.5 with a lot of MBO customizations. Can someone comment on how painful or easy it is to migrate such environment to Maximo 7? More specifically:
>
> Did the API change much?
> Can customized Java code be "plugged-in" or does most of it have to be re-written?
> Are there any issues with migrating customized screens?
> Any other issues are commond during migrations and what factors are important to consider?
>
> Thanks in advance!
>
It was just a signature change on a base class constructor that required me to change the signature on my custom class constructor. If I recall correctly in 6 it didn't declare any checked exceptions and 7 did. I wish I could recall what class is was, but I can't off the top of my head.
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of mlofny
Sent: Tuesday, July 05, 2011 10:04 AM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Migration from MX 6 TO MX 7
Thanks Chris. That makes me feel a lot more optimistic. If it's not a long story, what kind of change did you have to make to that one custom java class? I am curious because it's the only change that you had to make.
I hope others had equally pain-free experience.
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "Hanna, Christopher CTR" <christopher.a.hanna@...> wrote:
>
> We are in the middle of the same upgrade right now. We have a heavily customized application with around 170 custom classes. The migration from 6 to 7 only required one minor change to a custom Java class. I did take the opportunity to do some cleanup, JavaDoc documentation and best practices type stuff while I was in there, but as far as the Java itself, it was almost completely plug and play.
>
> Thanks!
>
> -Chris H
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ] On Behalf Of mlofny
> Sent: Wednesday, June 29, 2011 10:18 AM
> To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
> Subject: [MAXIMO List] Migration from MX 6 TO MX 7
>
>
>
> Hi,
>
> We have Maximo 6.2.5 with a lot of MBO customizations. Can someone comment on how painful or easy it is to migrate such environment to Maximo 7? More specifically:
>
> Did the API change much?
> Can customized Java code be "plugged-in" or does most of it have to be re-written?
> Are there any issues with migrating customized screens?
> Any other issues are commond during migrations and what factors are important to consider?
>
> Thanks in advance!
>