This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Notes: G.A - General Availablity Primavera 7.1.2 support - Maximo 7.1.1.7 and above will support running on WebSphere 7 (jdk 1.6) only for Primaver 7.1.2 users.* TPM 7.1 - supports Maximo Base Service v7.1.1.3 only**Maximo Mobile - products will add support for Microsoft Windows Mobile 6.0/6.1 Operating System. Support planned for May 2009.*** Tivoli Policy Driven Software Distribution 7.2 is now called Tivoli Endpoint Manager 7.2****Spatial 7.1.1 and Utilities 7.1.1 SQL Server 2005 does not support Spatial Data Types which was released in SQL Server 2008. We leverage this in our Spatial workflow which would require SQL Server 2008.Planned End of Service (EOS) - Products that are listed in red font are planned for End of Service.
SupportedNot Needed/Not SupportedSupported with restrictions
● ~~~ ● **
Legend:
IBM Maximo Products Group 1 Group 2/3
English French German Italian Japanese Korean Portuguese Spanish S Chinese T Chinese Arabic Croatian Czech Danish Dutch Finnish Hebrew Hungarian Norwegian Polish Russian Slovenian Slovakian Swedish
NOTES:-Planned End of Service (EOS) - Products that are listed in red font are planned for End of Service.
SupportedNot Needed/Not Supported
● ~~~
Legend:
M22
IBM_USER: 7.1.1
N22
IBM_USER: 7.1.1
O22
IBM_USER: 7.1.1
Q22
IBM_USER: 7.1.1
T22
IBM_USER: 7.1.1
W22
IBM_USER: 7.1.1
M23
IBM_USER: 7.1.1
N23
IBM_USER: 7.1.1
O23
IBM_USER: 7.1.1
Q23
IBM_USER: 7.1.1
T23
IBM_USER: 7.1.1
W23
IBM_USER: 7.1.1
M24
IBM_USER: 7.1.1
N24
IBM_USER: 7.1.1
O24
IBM_USER: 7.1.1
P24
IBM_USER: 7.1.1
Q24
IBM_USER: 7.1.1
S24
IBM_USER: 7.1.1
T24
IBM_USER: 7.1.1
U24
IBM_USER: 7.1.1
V24
IBM_USER: 7.1.1
W24
IBM_USER: 7.1.1
Y24
IBM_USER: 7.1.1
C28
IBM_USER: 7.1.1
D28
IBM_USER: 7.1.1
E28
IBM_USER: 7.1.1
F28
IBM_USER: 7.1.1
G28
IBM_USER: 7.1.1
H28
IBM_USER: 7.1.1
I28
IBM_USER: 7.1.1
J28
IBM_USER: 7.1.1
K28
IBM_USER: 7.1.1
N28
Mike_Foster: 7.1.2, available Nov. 12, 2010
P28
IBM_USER: 7.1.1, available Dec. 18, 2009
S28
Mike_Foster: 7.1.2, available Nov. 12, 2010
U28
Mike_Foster: 7.1.2, available Nov. 12, 2010
V28
IBM_USER: 7.1.1, available Dec. 18, 2009
L34
IBM_USER: 7.1.1
N34
IBM_USER: 7.1.1
P34
IBM_USER: 7.1.1
S34
IBM_USER: 7.1.1
T34
IBM_USER: 7.1.1
U34
IBM_USER: 7.1.1
Y34
IBM_USER: 7.1.1
L36
IBM_USER: 7.1.1
N36
IBM_USER: 7.1.1
R36
IBM_USER: 7.1.1
S36
IBM_USER: 7.1.1
T36
IBM_USER: 7.1.1
U36
IBM_USER: 7.1.1
V36
IBM_USER: 7.1.1
Y36
IBM_USER: 7.1.1
L37
IBM_USER: 7.1.1, available Dec. 18, 2009
N37
IBM_USER: 7.1.1, available Dec. 18, 2009
R37
IBM_USER: 7.1.1, available Dec. 18, 2009
S37
IBM_USER: 7.1.1, available Dec. 18, 2009
T37
IBM_USER: 7.1.1, available Dec. 18, 2009
U37
IBM_USER: 7.1.1, available Dec. 18, 2009
V37
IBM_USER: 7.1.1, available Dec. 18, 2009
Y37
IBM_USER: 7.1.1, available Dec. 18, 2009
L39
IBM_USER: 7.1.1
M39
IBM_USER: 7.1.1
N39
IBM_USER: 7.1.1
R39
IBM_USER: 7.1.1
S39
IBM_USER: 7.1.1
U39
IBM_USER: 7.1.1
V39
IBM_USER: 7.1.1
W39
IBM_USER: 7.1.1
D46
IBM_USER: 7.1.1
F46
IBM_USER: 7.1.1
L46
IBM_USER: 7.1.1
M46
IBM_USER: 7.1.1
N46
IBM_USER: 7.1.1
O46
karinl: 7.1.1,available Dec.18,2009
Q46
IBM_USER: 7.1.1
R46
IBM_USER: 7.1.1
S46
IBM_USER: 7.1.1
T46
IBM_USER: 7.1.1
U46
IBM_USER: 7.1.1
V46
IBM_USER: 7.1.1
W46
IBM_USER: 7.1.1
Y46
IBM_USER: 7.1.1
N48
karinl: 7.1.1,available Dec.18,2009
Q48
karinl: 7.1.1,available Dec.18,2009
S48
IBM_USER: 7.1.1
U48
IBM_USER: 7.1.1
Y48
karinl: 7.1.1,available Dec.18,2009
F50
IBM_USER: 7.1.1
L50
IBM_USER: 7.1.1
M50
IBM_USER: 7.1.1
N50
IBM_USER: 7.1.1
O50
IBM_USER: 7.1.1
Q50
IBM_USER: 7.1.1
R50
IBM_USER: 7.1.1
S50
IBM_USER: 7.1.1
T50
IBM_USER: 7.1.1
U50
IBM_USER: 7.1.1
V50
IBM_USER: 7.1.1
W50
IBM_USER: 7.1.1
Y50
IBM_USER: 7.1.1
D53
IBM_USER: 7.1.1
L53
IBM_USER: 7.1.1
M53
IBM_USER: 7.1.1
N53
IBM_USER: 7.1.1
O53
IBM_USER: 7.1.1
Q53
IBM_USER: 7.1.1
R53
IBM_USER: 7.1.1
S53
IBM_USER: 7.1.1
T53
IBM_USER: 7.1.1
U53
IBM_USER: 7.1.1
V53
IBM_USER: 7.1.1
W53
IBM_USER: 7.1.1
Y53
IBM_USER: 7.1.1
L55
Mike_Foster: 7.1.1, available Sept. 17, 2010.
R55
Mike_Foster: 7.1.1, available Sept. 17, 2010.
B97
IBM_USER: 1.1
C97
IBM_USER: 1.1.1
D97
IBM_USER: 1.1.1
E97
IBM_USER: 1.1.1
F97
IBM_USER: 1.1.1
G97
IBM_USER: 1.1.1
H97
IBM_USER: 1.1.1
I97
IBM_USER: 1.1.1
J97
IBM_USER: 1.1.1
K97
IBM_USER: 1.1.1
N97
IBM_USER: 1.1.1
S97
IBM_USER: 1.1.1
U97
IBM_USER: 1.1.1
V97
IBM_USER: 1.1.1
For Internal Use Only - Not For Distribution
IBM Maximo Products Group 1
Documentation Translation English
IBM Maximo Asset ManagementIBM Maximo Asset Management 7.5 - Information Center ●IBM Maximo Calibration 7.5 - Information Center ●IBM Maximo for Life Sciences 7.5 - Information Center ●IBM Maximo Everyplace 7.5 - Information Center ●IBM Maximo Linear Asset Manager 7.5 - Information Center ●IBM Maximo Scheduler 7.5 - Information Center ●IBM Maximo Essentials 7.5 - Information Center ●IBM Maximo Change and Corrective Action Manager 7.5 - Information Center ●IBM Maximo Health,Safety & Environment Manager 7.5 - Information Center ●IBM Maximo Mobile Suite 7.5 - Information Center ●IBM Maximo Project 7.5 - Information Center ●IBM Maximo Primavera 7.5 - Information Center ●IBM Maximo Enterprise Adapter for SAP 7.5 ● - Info Center ● - Installation Guide ● - System Administrator Guide ●IBM Maximo Enterprise Adapter for Oracle 7.5 ● - Info Center ● - Installation Guide ● - System Administrator Guide ●IBM Maximo Enterprise Adapter for SAP 7.5 ●IBM Maximo for Oil and Gas 7.5 - Information Center ●IBM Maximo Asset Configuration Manager 7.5 - Information Center ●IBM Maximo for Service Providers 7.5 - Information Center ●IBM Maximo for Service Providers 7.5.1 - Information Center ●IBM Maximo for Utilities 7.5 - Information Center ●IBM Maximo for Nuclear Power 7.5 - Information Center ●IBM Maximo for Transportation 7.5 - Information Center ●IBM Maximo Spatial Asset Management 7.5 - Information Center ●IBM Maximo for Government 7.5 ●
●
IBM Maximo Space Management for Facilities 7.5 ● - SM Info Center ● - User Guide ● - Vertical Space User Guide ● - Drawing Linking User Guide ● - Layer Manager User Guide ● - Legends User Guide ● - Move Manager User Guide ● - MEP Manager User Guide ● - Space Planner User Guide ●IBM Maximo Data Center Infrastructure Management 7.5 ● - DCIM Info Center ● - User Guide ● - Vertical Space User Guide ● - Drawing Linking User Guide ● - Layer Manager User Guide ● - Legends User Guide ●
IBM Maximo Archiving with InfoSphere Optim Data Growth Solution 7.5 - Information Center
- Move Manager User Guide ● - MEP Manager User Guide ● - Space Planner User Guide ●IBM Intelligent Building ManagementIBM Intelligent Building Management 1.1 - Information Center ●NOTES:
TranslatedNot translatedPlanned date to be translated and available
● (blank)MM-DD-YY
Legend:
Group 1
French German Italian Japanese Korean Spanish S Chinese T Chinese
IBM DB2 ESE 9.5 for Unix - Does not support Linux 32bit OS
IBM DB2 ESE 9.7 for Unix - Does not support Linux 32bit OS
TPM 7.1 - Supports Maximo Base Service v7.1.1.3 only
*Maximo Spatial Asset Management 7.1.1 & Maximo for Utilities 7.1.1 - IE6 is NOT supported if Spatial is Deployed this is a continued Deviation from previous releases.
**Maximo Spatial Asset Management 7.1.1 - IE8 is only supported in compatibility mode with IE7 (ESRI ArcGIS Server does not support this and is unable to until Microsoft issues the fix,) This applies to Utilities if Spatial is deployed
*** Maximo Scheduler 7.1 requires JRE 1.6
SupportedNot Needed/Not SupportedSupported with restrictions
● ~~~ ● **
Legend:
J3
Tivoli Provisioning Manager 7.1 supports 7.1.1.3
J7
TPM 7.1 - supports Maximo Base Service v7.1.1.3 only
D8
Maximo 7.1 March2009
F8
TAMIT 7.1 March2009
D9
Maximo 7.1 March2009
F9
TAMIT 7.1 March2009
L9
CCMDB 7.1 Refresh
D11
Runs on support only, 7.1.1.9 or higher
L13
IBM_USER: Support for RKI customer on 7.1.1.5 still undertermined, no general support
S13
SRM 7.1.0.2 & base services 7.1.1.3 or later
C14
IBM_USER: 6.2.1
C15
IBM_USER: 6.2.1
T15
Limited support: Oracle 10G R2
D16
7.1.1.4
F16
7.1.1.4
M16
Limited support: Oracle 10G R2
P16
Limited support: Oracle 10G R2
S16
IBM_USER: SRM 7.1.0.3 & base services 7.1.1.4
C18
IBM_USER: 6.2.1
J18
Includes Standard Edition TPM 7.1 - supports Maximo Base Service v7.1.1.3 only
K18
Includes Standard Edition
R18
Juergen Sauter: prereq is that CCMDB supports this OS
C19
IBM_USER: 6.2.1
J19
Includes Standard Edition TPM 7.1 - supports Maximo Base Service v7.1.1.3 only
K19
Includes Standard Edition
B20
Release Date
D20
Maximo Asset Mgmt 7.1 March2009 Includes Windows 2008 Enterprise & Datacenter on 32bit & 64 bit
F20
TAMIT 7.1 March2009 Includes Windows 2008 Enterprise & Datacenter on 32bit & 64 bit
L20
7.1.1 Refresh 2 Includes Windows 2008 Enterprise & Datacenter on 32bit & 64 bit
O20
7.1.1 Refresh 2 Includes Windows 2008 Enterprise & Datacenter on 32bit & 64 bit
P20
7.1.1 Refresh 2 Includes Windows 2008 Enterprise & Datacenter on 32bit & 64 bit
S20
SRM 7.1 1Q Refresh Includes Windows 2008 Enterprise & Datacenter on 32bit & 64 bit
D21
Refresh 3 on 2/22/10 will officially support Win2008 R2 with the MWI
L21
IBM_USER: 7115 must be installed on Win 2008 first and the OS upgraded to Win 2008 R2 at which time 7116 can also be installed
R21
IBM_USER: 7115 must be installed on Win 2008 first and the OS upgraded to Win 2008 R2 at which time 7116 can also be installed
W22
DS: Support requires TSAM 7.2.0.1 (fixpack 1)
J23
TPM 7.1 - supports Maximo Base Service v7.1.1.3 only
D24
Maximo 7.1 March2009
F24
TAMIT 7.1 March2009
D25
7.1.1.3
F25
7.1.1.3
L25
IBM_USER: 7.1.1.3 Manual Middleware Automated MWI planned for CCMDB 7.2
O25
IBM_USER: 7.1.1.3 Manual Middleware Automated MWI planned for CCMDB 7.2
P25
IBM_USER: 7.1.1.3 Manual Middleware Automated MWI planned for CCMDB 7.2
R25
Juergen Sauter: prereq is that CCMDB supports this OS
S25
SRM 7.1.0.2 & base services 7.1.1.3 or later
C26
6.2.8
D26
Maximo 7.1 March2009
F26
TAMIT 7.1 March2009
L26
IBM_USER: 7.1.1.5
O26
IBM_USER: 7.1.1.5
P26
IBM_USER: 7.1.1.5
C27
6.2.8
D27
Maximo 7.1 March 2009
F27
TAMIT 7.1 March2009
L27
IBM_USER: 7.1.1.5
O27
IBM_USER: 7.1.1.5
P27
IBM_USER: 7.1.1.5
S27
SRM 7.1.0.4 & base services 7.1.1.5 or later
C28
6.2.8
D28
7.1.1.3
F28
7.1.1.3
L28
IBM_USER: 7.1.1.5
O28
IBM_USER: 7.1.1.5
P28
IBM_USER: 7.1.1.5
R28
Juergen Sauter: prereq is that CCMDB supports this OS
S28
SRM 7.1.0.2 & base services 7.1.1.3 or later
W28
Support requires TSAM 7.2.0.1 (fixpack 1)
X28
Support requires TSAM 7.2.0.1 (fixpack 1)
D29
Runs on support only, 7.1.1.9 or higher
E29
Middle ware installer not surpported. DB2 not supported in production systems.
D30
Runs on support only, 7.1.1.9 or higher
D31
Runs on support only, 7.1.1.9 or higher
M32
IBM_USER: Deprecate on 7.2.1
P32
Will not be support on any release in 2010
M33
IBM_USER: Deprecate on 7.2.1
P33
Will not be support on any release in 2010
L34
IBM_USER: 7.1.1.3 Manual MWI
M34
IBM_USER: Deprecate on 7.2.1
P34
Will not be support on any release in 2010
R34
Juergen Sauter: prereq is that CCMDB supports this OS
S34
SRM 7.1.0.2 & base services 7.1.1.3 or later
D35
Maximo 7.1 March 2009
L35
IBM_USER: 7115
O35
7115
P35
7115
S35
SRM 7.1.0.2 & base services 7.1.1.3 or later
D36
Maximo 7.1 March 2009
L36
IBM_USER: 7115
O36
7115
P36
7115
S36
SRM 7.1.0.4 & base services 7.1.1.5 or later
X36
DS: SLES 10 SP3 or higher
D37
7.1.1.3
F37
7.1.1.3
L37
IBM_USER: 7.1.1.3 Manual Middleware Automated MWI planned for CCMDB 7.2
O37
IBM_USER: 7.1.1.3 Manual Middleware Automated MWI planned for CCMDB 7.2
P37
IBM_USER: Manual Middleware
R37
Juergen Sauter: prereq is that CCMDB supports this OS
S37
SRM 7.1.0.2 & base services 7.1.1.3 or later
D38
Manual install.
F38
Manual Install
L38
IBM_USER: 7115 must be installed on SLES 10 first and the OS upgraded to Win SLES 10 at which time 7116 can also be installed
O38
IBM_USER: 7115 must be installed on SLES 10 first and the OS upgraded to Win SLES 10 at which time 7116 can also be installed
D39
Manual install.
L39
IBM_USER: 7115 must be installed on SLES 10 first and the OS upgraded to Win SLES 10 at which time 7116 can also be installed
O39
IBM_USER: 7115 must be installed on SLES 10 first and the OS upgraded to Win SLES 10 at which time 7116 can also be installed
D40
Manual install.
L40
IBM_USER: 7115 must be installed on SLES 10 first and the OS upgraded to Win SLES 10 at which time 7116 can also be installed
O40
IBM_USER: 7115 must be installed on SLES 10 first and the OS upgraded to Win SLES 10 at which time 7116 can also be installed
W40
Only via OS upgrade from SLES, no native install.
D45
7.1.1.4 IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
F45
7.1.1.4 IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
G45
IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
J45
IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
K45
IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
L45
IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
M45
IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
O45
IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
R45
IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
S45
IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
T45
IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
V45
IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
W45
IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
Y45
IBM Remote Technical Support will accept usage/defect-related service requests for IBM SWG IPLA products running in a VMware® ESX Server or VMware® Server environment. If it appears that the problem is unique to the VMware® environment, IBM may require the client to recreate the problem in a non-VMware® environment. If the client has purchased an IBM ServicePac Agreement® (for VMware®), the IBM VMware® support team can assist in reproducing the problem in accordance with the terms of that agreement.
TPM 7.1 - supports Maximo Base Service v7.1.1.3 only
R51
Juergen Sauter: prereq is that CCMDB supports this OS
D52
Runs on support only, no automated middle ware install support. 7.1.1.7 or higher fixpack
C54
Maximo 6.2.4 - BEA Weblogic Server Version 9.2.2 Maximo 6.2.6 - WLS 9.2.3
M54
Toleration for Weblogic 9.2.3 with Oracle
N54
Toleration for Weblogic 9.2.3 with Oracle
P54
Toleration for Weblogic 9.2.3 with Oracle
S54
Solaris 10 and Windows
T54
Solaris 10 and Windows
D55
Post GA certification with 7.1.1.6, CD available for existing Maximo Weblogic clients by request
B60
IBM User: APRIL 31, 2007: End of support date 4/30/2012 - End of extended support
M60
Includes zLinux
J61
TPM 7.1 - supports Maximo Base Service v7.1.1.3 only
M61
Includes zLinux
C62
Maximo 6.2.4 - DB2 Version 9.5 Service Pack 3a Maximo 6.2.6 - DB2 9.5 SP4
D62
DB2 9.5 supported on Windows 2008 & Windows 2003 with Maximo 7.1 March2009 Customers who are on zLinux can also use DB2 9.5 as their Relational Database Management System. Instructions for installing DB2 9.5 are in the DB2 9.5 Installation Guide. The installation requirements, release notes, and installation instructions are available from the DB2 9.5 Information Center at http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp.
F62
DB2 9.5 supported on Windows 2008 & Windows 2003 with TAMIT 7.1 March2009 Customers who are on zLinux can also use DB2 9.5 as their Relational Database Management System. Instructions for installing DB2 9.5 are in the DB2 9.5 Installation Guide. The installation requirements, release notes, and installation instructions are available from the DB2 9.5 Information Center at http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp.
G62
DB2 9.5 supported on Windows 2008 & Windows 2003 Customers who are on zLinux can also use DB2 9.5 as their Relational Database Management System. Instructions for installing DB2 9.5 are in the DB2 9.5 Installation Guide. The installation requirements, release notes, and installation instructions are available from the DB2 9.5 Information Center at http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp
J62
DB2 9.5 Custom manual install TPM 7.1 - supports Maximo Base Service v7.1.1.3 only
L62
Supported on Windows 2008 and Windows 2003 for refresh 2, planned full support on CMDB 7.2
S62
Windows 2008 only
C63
Maximo 6.2.4 - DB2 Version 9.5 Service Pack 3a
D63
Customers who are on zLinux can also use DB2 9.5 as their Relational Database Management System. Instructions for installing DB2 9.5 are in the DB2 9.5 Installation Guide. The installation requirements, release notes, and installation instructions are available from the DB2 9.5 Information Center at http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp
F63
Customers who are on zLinux can also use DB2 9.5 as their Relational Database Management System. Instructions for installing DB2 9.5 are in the DB2 9.5 Installation Guide. The installation requirements, release notes, and installation instructions are available from the DB2 9.5 Information Center at http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp
G63
Customers who are on zLinux can also use DB2 9.5 as their Relational Database Management System. Instructions for installing DB2 9.5 are in the DB2 9.5 Installation Guide. The installation requirements, release notes, and installation instructions are available from the DB2 9.5 Information Center at http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp
M63
Includes AIX and zLinux
C64
6.2.8 DB2 9.7 FP3
D64
Install not supported
S64
SRM 7.1.0.6 and MBS 7.1.1.7
C65
6.2.8 DB2 9.7 FP3
D65
Install not supported
B66
Henry Richardson: EOS for 9iv2 was July 31 2007. In Oracle terms, that means they will no longer accept new bugs. Unless you pay for extended support. They will continue to provide online downloads of patches for another year or two and you can still download the software and run it. No info on when it will roll off the download selection list.
J66
TPM 7.1 - supports Maximo Base Service v7.1.1.3 only
L66
Windows 32-bit Only
O66
Windows 32-bit Only
P66
Windows 32-bit Only
S66
Windows 32-bit Only
L67
Windows 32-bit Only
O67
Windows 32-bit Only
P67
Windows 32-bit Only
S67
Windows 32-bit Only
B69
RELEASED
C69
Fixpack 6.2.8 - Actuate 8 does not support Oracle 11g.
D69
7.1.1.5
F69
7.1.1.5
C70
Fix pack 6.2.8 - Actuate 8 does not support Oracle 11g
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
D71
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
F71
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
G71
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
L71
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
M71
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
N71
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
O71
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
P71
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
Q71
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
R71
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
S71
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
T71
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
C72
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
D72
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
E72
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
F72
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
G72
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
H72
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
M72
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
N72
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
P72
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
Q72
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
T72
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
U72
IBM will accept usage/defect-related service requests for customers using Oracle RAC for high availability business continuity planning. If it appears that the problem is unique to the high availability tooling in use, IBM may require the client to recreate the problem in a non-RAC environment.
B73
IBM User: Mainstream Support Retired: April 8, 2008 Extended Support Retired April 9, 2013
SupportedNot Needed/Not SupportedSupported with restrictions
● ~~~ ● **
Legend:
IBM Maximo ProductsSupported Platform Versions
Operating SystemsAIX 5.2 (32 bit) ~~~ ~~~AIX 5.3 (32 bit) ~~~ ~~~AIX 5.3 (64 bit) ~~~ ~~~AIX 6.1 (32 bit) ~~~ ~~~AIX 6.1 (64 bit) ~~~ ●AIX 7.1 (64 bit) ~~~ ~~~Solaris 9 (Sparc) ~~~ ~~~Solaris 10 (Sparc) ~~~ ~~~HP-UX 11i v1 (PA-RISC) ~~~ ~~~HP-UX 11i v2 (PA-RISC) ~~~ ~~~HP-UX 11i v2 (Itanium) ~~~ ~~~HP-UX 11i v3 (Itanium) ~~~ ~~~Windows XP (x86, 32bit) ● ●Windows XP (x86, 64bit) ● ●Windows Vista (x86, 32bit) ~~~ ●Windows Vista (x86, 64bit) ~~~ ~~~Windows 7 (x86, 32bit) - Excluding Home Edition ~~~ ~~~Windows 7 (x86, 64bit) - Excluding Home Edition ~~~ ~~~Windows Server 2000 ~~~ ~~~Windows Server 2003 DataCenter SP2 (32-bit, 64-bit) Intel ● ●Windows Server 2003 DataCenter R2 SP2 (32-bit, 64-bit) Intel ~~~ ~~~Windows Server 2003 Enterprise Edition SP2 (32-bit, 64-bit) Intel ● ●Windows Server 2003 Enterprise Edition R2 SP2 (32-bit, 64-bit) Intel ~~~ ~~~Windows Server 2003 Standard Edition SP2 (32-bit, 64-bit) Intel ● ●Windows Server 2003 Standard Edition R2 (32-bit, 64-bit) Intel ~~~ ~~~Windows Server 2008 Enterprise Edition (32-bit, 64-bit) Intel ~~~ ●Windows Server 2008 Enterprise Edition R2 (64-bit) Intel ~~~ ~~~Windows Server 2008 Standard Edition (32-bit, 64-bit) Intel ~~~ ●Windows Server 2008 Standard Edition R2 (64-bit) Intel ~~~ ~~~Red Hat Enterprise Linux 3 (x86, 32 bit) ~~~ ~~~Red Hat Enterprise Linux 4 (x86, 32 bit) ~~~ ~~~Red Hat Enterprise Linux 4 (x86, 64 bit) ~~~ ~~~Red Hat Enterprise Linux 4 (zLinux) ~~~ ~~~Red Hat Enterprise Linux 5 (x86, 32 bit) ~~~ ~~~Red Hat Enterprise Linux 5 (x86, 64 bit) ~~~ ~~~Red Hat Enterprise Linux 5 (zLinux) ~~~ ~~~SUSE Linux Enterprise Server 9 (x86 32 bit) ~~~ ~~~SUSE Linux Enterprise Server 9 (x86 64 bit) ~~~ ~~~SUSE Linux Enterprise Server 9 (zLinux) ~~~ ~~~SUSE Linux Enterprise Server 10 (x86 32 bit) ~~~ ●SUSE Linux Enterprise Server 10 (x86 64 bit) ~~~ ●SUSE Linux Enterprise Server 10 (zLinux) ~~~ ~~~SUSE Linux Enterprise Server 11 (x86 32 bit) ~~~ ~~~SUSE Linux Enterprise Server 11 (x86 64 bit) ~~~ ~~~SUSE Linux Enterprise Server 11 (zLinux) ~~~ ~~~
CCMDB7.1
CCMDB 7.2
Supported Not Needed/Not SupportedPlanned date to be supportedDate not determined, approvedDeprecatedIn discussionSupported with restrictionsIn Prog for limited support; not supported on Actute
● ~~~ MM-YYIn ProgDPlanning ● **In Prog ● **
Legend:
B23
kpatel: 32-bit Only
C23
kpatel: 32-bit Only
B25
kpatel: 32-bit Only
B27
kpatel: 32-bit Only
Supported Not Needed/Not SupportedPlanned date to be supportedDate not determined, approvedDeprecatedIn discussionSupported with restrictionsIn Prog for limited support; not supported on Actute
Network connection between Administratorsystem and middleware
O1
DTM 7.2 name changed to TEM 7.2
H15
: • Windows/Linux: 2.4 GHz x86 64-bit or AMD64 processor • Linux: on IBM® System z®: z/Architecture® (z800) • AIX: 1.5 GHz Power5 (100% of one processor if using micropartitioning) • Solaris: 1.4 GHz SPARC64/UltraSPARC