Did you ever wonder about the introduction of MIF ifixes?
KJL 270000E62R Visits (9819)
Hello Integration Framework team!
Starting in Maximo 184.108.40.206 the Maximo Integration Framework (MIF) ifixes were separated from the Maximo or Tivoli Process Automation Engine (TPAE) ifixes.
This was done to confuse you, right? :)
Actually, it was done to decouple the products so that ifixes could be released more quickly, and shared between different products which use the MIF code, like REST and OSLC. So a MIF ifix can be used with the Mobile product as well as with Asset Management.
Since the MIF ifixes are so much smaller than the Maximo ifixes it is easy to stay up to date. There are few if any manual changes and testing may not be as complex as when applying a Maximo ifix. (btw, an ifix is an interim fix which is a bundle of fixes released periodically for priority issues reported by customers.)
Here are the versions to date:
220.127.116.11 and earlier - the MIF is included with the TPAE IFIX.
18.104.22.168 - MIF 22.214.171.124
126.96.36.199 - MIF 188.8.131.52
184.108.40.206 - MIF 220.127.116.11
18.104.22.168 - MIF 22.214.171.124
126.96.36.199 - MIF 188.8.131.52
184.108.40.206 - MIF 220.127.116.11
18.104.22.168 - MIF 22.214.171.124
126.96.36.199 - MIF 188.8.131.52
184.108.40.206 - MIF 220.127.116.11
18.104.22.168 - MIF 22.214.171.124
126.96.36.199 - MIF 188.8.131.52
184.108.40.206 - MIF 220.127.116.11
18.104.22.168 - MIF 22.214.171.124
All of the latest ifixes can be downloaded from Fix Central:
Or if you are having trouble locating an ifix, support can send you a direct link to the latest released ifix.
Hope things are a little clearer now!