-
Page 1 / 16
2009 SAP. All rights reserved.
Platforms and Technologies Support Policy Guide for SAP
BusinessObjects Products (2012)
February 2012 Revision 2.0 draft 3
Table of Contents
1 DOCUMENT DEFINITIONS
.......................................................................................................
2
2 SUPPORT POLICY - GENERAL STATEMENT
......................................................................
2
3 PLATFORMS APPROVALS
........................................................................................................
3
4 PLATFORMS SCOPE CATEGORIES OF PLATFORMS
.................................................... 3
5 PLATFORMS SUPPORT - PRODUCT APPLICABILITY
...................................................... 3
5.1 SAP PRODUCT APPLICABILITY
.........................................................................................................
3 5.2 PLATFORMS SUPPORT IN SAP MAJOR, MINOR AND MAINTENANCE
RELEASES. ...................................... 3
6 LEVELS OF SUPPORT
................................................................................................................
4
6.1 SUPPORT LEVELS DEFINED
...........................................................................................................
4 6.1.1 Direct Support
...................................................................................................................
4 6.1.2 Compatible Support
..........................................................................................................
4 6.1.3 Conditional Support
..........................................................................................................
6
6.2 SAP PLATFORMS SUPPORT TIMETABLE
.............................................................................................
8 6.3 MODIFICATIONS IN SUPPORT
LEVEL..................................................................................................
8
6.3.1 Support Level Graduation
.................................................................................................
8 6.3.2 Support Level Downgrade
.................................................................................................
8
7 SUPPORT POLICY - GENERAL GUIDANCE
.........................................................................
9
7.1 C-1 PLATFORMS MAJOR & MINOR RELEASE SUPPORT
........................................................................
9 7.1.1 Exceptions to the c-1 Platforms Support policy
................................................................
9
7.2 PRE-SAP CODE BETA PLATFORMS RELEASES - VENDOR
.......................................................................
9 7.3 PLATFORMS SUPPORT DISCONTINUED - VENDOR
..............................................................................
10
8 MINIMUM HARDWARE REQUIREMENTS DEFINITION
................................................ 10
9 REQUESTING PLATFORMS SUPPORT
................................................................................
10
10 COMMUNICATING PLATFORMS SUPPORT AND PLATFORMS END-OF-LIFE
.... 10
10.1 EXTERNAL COMMUNICATION WITH CUSTOMERS
..............................................................................
11
11 APPENDIX
...............................................................................................................................
12
11.1 OPERATING SYSTEMS VERSION IDENTIFICATION MATRIX
.....................................................................
12 11.2 APPLICATION SERVER VERSION IDENTIFICATION
MATRIX.....................................................................
12 11.3 PORTAL SERVER VERSION IDENTIFICATION MATRIX
............................................................................
13
-
Page 2 / 16
2009 SAP. All rights reserved.
1 Document Definitions Following is a list of terms used within
this document
Term Usage Definition
+SP/Minor Short form for Next SAP XI 3.1 Service Pack
Increment/BI 4.x Minor Release.
c Current, as in current product release
c-1 Current minus 1, as in the release immediately previous to
the now current release.
c-2 current minus 2, as in two releases immediately previous to
the now current release.
FP Fix Pack(s)
GA General Availability or Generally Available. The point at
which the product is available externally to the public.
IE Microsoft Internet Explorer
OS Operating System
PAM Platform Availability Matrix contains release and
maintenance lifecycle dates and some other product information. PAM
document contains details of supported platforms and 3
rd
party products for individual SAP BI 4.x product releases in the
SAP format
PAR Product Availability Report, document containing details of
supported platforms and 3rd party products for individual SAP XI
3.1 product releases in the original BusinessObjects format
SBOP SAP Portfolio
SP Service Pack in XI 3.1 product line
2 Support Policy - General Statement The Platforms and
Technologies Support Policy Guide is the policy governing the
supported
platforms and 3rd
party products for the SAP Portfolio (SBOP) and is intended to
serve as general guidance specifically focused on when and how SAP
will endeavor to support or supplement existing platforms for the
SBOP products. The guidance outlined below is not contractually
binding, and shall not in any way commit or legally obligate SAP.
This Platforms and Technologies Support Policy Guide only applies
to SAP products currently within active patch support (SAP product
releases definitions in the section 6.1 below).
o Details of supported platforms and 3rd party products for
individual releases are
documented in Products Availability Report (PAR) document for XI
3.1 product line and in Product Availability Matrix (PAM) document
for BI 4.x product line, and can be found on three locations:
o SMP: https://websmp108.sap-ag.de/bosap-supportedplatforms o
SDN: http://www.sdn.sap.com/irj/boc/articles -> Go to Supported
Platforms/PARs o SMP: https://websmp204.sap-ag.de/pam -> select
desired SBOP product
In addition, you can find the following reference documents to
help you navigate through SBOP products lifecycle management:
The policy determining the availability of new releases and
maintenance lifecycle is explained in SAP's Release Strategy for
Large Enterprises and SAP's Release Strategy for Small
Businesses
and Midsize Companies (Release Brochure):
http://service.sap.com/releasestrategy
-
Page 3 / 16
2009 SAP. All rights reserved.
o The Release and Maintenance lifecycle dates for SAP
applications can be
determined by referring to the Product Availability Matrix
(PAM): http://service.sap.com/pam
3 Platforms Approvals Approval/acceptance for platforms support
additions, support discontinuation or deviations from this policy
is the mandate of SAP Solution and Product Management.
4 Platforms Scope Categories of Platforms The Platforms and
Technologies Support Policy covers the following platforms
categories:
Acrobat Reader
Directory servers (Active Directory, LDAP, etc.)
Administrative (i.e. Citrix)
Adobe Flash Player
Data Connectivity (RDBMS/OLAP/)
Developer Tools
Java (JVM/JDK)
Microsoft Office Products
Operating Systems
Portal Servers
Reverse Proxy
Technology Connectivity (i.e. Java Beans, Web Services)
Virtualization
Web Application Servers
Web Browsers
Wireless [back to top]
5 Platforms Support - Product Applicability
5.1 SAP Product Applicability
This Platforms and Technologies Support Policy Guide only
applies to the Business Intelligence and Information Management
line of products from SAP portfolio
(http://www12.sap.com/solutions/sapbusinessobjects/large/intelligenceplatform/bi/index.epx
and
http://www12.sap.com/solutions/sapbusinessobjects/large/intelligenceplatform/im/index.epx)
currently within active patch support as indicated on the SAP
Release Maintenance page.
5.2 Platforms Support in SAP releases.
The platforms support rules may vary depending on the type of
releasedescribed below.
Major release Commercial release offering new features (new
source branch). It may include major design changes. Platforms
support will be defined using the previous SAP release as a
baseline and will include additions, modifications and
discontinuation of support.
Minor release Commercial refresh release (AKA point release)
that contains minor design
changes (same source branch as major) oriented towards defect
correction. Continuous
-
Page 4 / 16
2009 SAP. All rights reserved.
support of the platforms from the previous release is provided
and may include additions or support discontinuation of some
platforms versions.
Service Pack Distribution that contains the XI 3.1 maintenance
release modules (product
defect corrections in Fix Packs). Changes to the platforms
support are generally offered here to keep product aligned with the
support policy.
Fix Pack Distribution that contains the XI 3.1 defect
corrections. Changes to the platforms support are generally not
offered here.
Support Pack Distribution that contains the BI 4.x defect
corrections. Changes to the platforms support may be offered here
to the extend that the short release cycle allows (major operating
systems upgrades are not likely to be offered here).
6 Levels of Support SAP Portfolio platforms support has three
levels of support. These definitions are described in more detail
below.
6.1 Support Levels Defined
6.1.1 Direct Support
Directly Supported Platforms include those platforms that have
gone through formal internal testing and SAP commits to fully
supporting them. SAP commits to providing code fixes found on all
directly supported platforms.
Directly supported platforms are listed in the published PAR/PAM
documents.
6.1.2 Compatible Support
Platforms that are granted compatible support have not gone
through formal internal testing by engineering. Compatible support
is provided through reference to a platform that is already
directly supported. The eligibility of platforms for compatible
support is based upon the two conditions described below:
1) Platform vendors guarantee to ensure compatibility with their
major / minor / incremental version releases already supported
directly by SAP. As such, the platforms vendor must have a
documented policy or public support statement in place which
clearly indicates compatibility to a previous major / minor /
incremental platforms version that is directly supported by
SAP.
2) SAP engineering assessment grants and extends Compatible
support to the vendors
platforms in question.
Given the different nature of various platform types, vendors
compatibility definitions between releases and SAP engineering
evaluation of risk, there are specific definitions and exceptions
of compatible support as described below. Operating Systems
compatible support Major or Minor Releases of operating systems are
not eligible for compatible support, consult version identification
matrix for versions definitions.
-
Page 5 / 16
2009 SAP. All rights reserved.
Windows Windows Service Packs may be considered for compatible
support based on the SAP engineering assessment. In this case
compatible support will be provided through reference to the major
release/service pack that is already directly supported. If
compatible support is granted, it will be explicitly listed in the
PAR/PAM documents. Windows security patches receive automatic
support and are not listed in the PAR/PAM documents. Unix (AIX,
HP-UX, Solaris) and Linux (Red Hat, SUSE) The PAR/PAM explicitly
lists the operating system version tested by SAP (direct support) -
this is the required minimum install level for support. Higher
incremental releases issued by vendor (as classified by SAP version
identification matrix) are not tested by SAP, but their support is
based upon the compatibility statements from vendor. These
incremental releases are not specifically listed in the PAR/PAM.
SAP customer support will consider customer messages and
investigate the issue, but will proceed with processing the issue
only if it is determined that the issue lies with the SBOP product.
SAP is not obligated to fix issues that result from product
inter-operability with untested incremental releases of operating
system (for example performance degradation specific to an untested
incremental release). Issues resulting from vendor compatibility
break will be documented using SAP Note describing a workaround if
possible. Compatible Support - Other platforms (Application
Servers, Browsers, Database, etc) Major platform releases are not
eligible for Compatible support. Minor platforms releases accepted
to receive Compatible support are explicitly listed in the PAR/PAM
documents. Incremental updates (as identified by SAP version
identification matrix) receive automatic Compatible support when
compatibility statement is provided by the vendor, and are not
presently documented in the PAR/PAM documents. Exceptions to this
support will be noted. Compatible Support - Database middleware
cross-version Versions of database server along with supported
middleware connectivity are explicitly listed in the SAP PAR/PAM
documents. These server / middleware combinations have gone through
formal internal testing by engineering. There are instances where
the vendor will permit cross-version connectivity of their
middleware release with multiple database version releases:
Example: DBMS example1: Version 3.50 of IBM Informix ODBC is
supported with IBM IDS Enterprise Edition versions 11.10 and 11.50.
DBMS example2: IBM DB2 Version 9.1 clients can access a remote DB2
Version 9.5 server. In scenarios where the vendor permits
middleware connectivity between cross-version database releases,
SAP Business Objects will grant automatic Compatible support under
the following conditions:
Middleware version must be listed in the SAP PAR/PAM
documents.
Database server release name must be listed in the SAP PAR/PAM
documents.
Vendor must issue official policy or publish support statement
which qualifies the
middleware connectivity with cross-version database server
releases.
Platforms restricted from receiving Compatible support:
-
Page 6 / 16
2009 SAP. All rights reserved.
Platforms not classified as general release (GA) by platforms
vendors (e.g. Beta releases, Candidate releases) are generally not
eligible for Compatible support consideration.
Vendor does not provide an explicit compatibility statement to
the directly supported platform
The functional scope of reference support for Compatible
platforms is limited to the same functionality supported by SAP
products in the referenced directly supported platform. Compatible
support for the platform in question does not include any newer
functionality beyond the supported scope in the reference platform.
If backwards compatibility cannot be guaranteed by the vendor, then
the platform version will remain unsupported until direct support
can be delivered. Any issues being reported on Compatible accepted
platforms will first need to be reproduced on the referenced
directly supported platform as a matter of isolating the locus of
the issue. Issues logged against Compatible platforms cannot be
escalated until or unless reproduced on the referenced and directly
supported platform. If issues are not reproduced on directly
supported platform, the responsibility for further review lies with
the vendor as solicited by the customer. Request for Platform
Support (RPS) process should be followed to request a compatible
support not already provided (refer to section 10),
Example:
DBMS example: Microsoft SQL Server 2005 SP1 is a directly
supported platform. When SQL Server 2005 SP2 ships, SAP will
support it as compatible and, by policy, include it in the next
applicable Service Pack release, at which time SQL Server 2005 SP2
will move from Compatible to Direct support.
[back to top]
6.1.3 Conditional Support
Conditionally Supported platforms cover those that are
considered to be non-core, have not been formally tested by and are
not planned for formal testing by SAP.
Note: The policy for Conditional Support applies at this time
ONLY to database platforms.
Currently, there are two types of conditional support:
a) SAP ICC (Integration and Certification Center) Certified
Conditional Support
b) Standards Based Conditional Support
6.1.3.1 SAP ICC (Integration and Certification Center) Certified
Conditional Support
This covers the Standards-based (ODBC/JDBC) Database Access for
database as well as the provider being used that have successfully
passed the SAP Integration and Certification (ICC) Program and have
been granted SAP Certified - Integration with SAP designation.
The link to databases and vendors that are SAP ICC certified and
qualify for this support will be provided in the PAR/PAM
document.
6.1.3.1.1 Support Process for ICC Certified Database Access
-
Page 7 / 16
2009 SAP. All rights reserved.
First line support for the database in use as well as the
provider is the responsibility of the database vendor and not SAP.
If contacted in case of issues, the SAP Customer Support will refer
the customer to the database vendor. The database vendor is
required to attempt to reproduce the issue by reference to SQL
Server for ODBC and MySQL for JDBC standard-based database access
(for products where Generic JDBC access is supported).
If the issue being reported cannot be demonstrated to reside
with an SAP product (cannot be reproduced on reference database),
the issue will be deemed to reside with the database vendor. On the
other hand, if the above test results show that SAP product is at
fault, the issue will be logged for review within the SAP standard
bug review process.
Additionally to this, support assistance may be found in the
applicable Business Objects areas of the SAP Community Forums.
6.1.3.2 Standards Based Conditional Support
Standards-based drivers are normally used when a database
environment is not specifically listed in the SAP PAR/PAM document,
and there is an available, vendor-supported ODBC or JDBC driver for
the database that meets the conditions as described below.
6.1.3.2.1 Requirements for Standards-based Drivers
Standards Based drivers must, at a minimum, comply with the
following design guidelines;
Database server, Client and ODBC/JDBC driver used must support
multiple threads.
Vendor-supported drivers: o ODBC drivers must be ODBC Level
2-compliant o ODBC driver must support multiple connections (for IM
products only) o JDBC drivers must be JDBC Type 4-compliant
6.1.3.2.2 Support Process for Standards-based Drivers
In case of issues, the customer is requested to attempt to
reproduce issue by reference on SQL Server for ODBC (SQL Server
Express is acceptable), and for IM products on one of the certified
ODBC to generic data support listed in the PAR/PAM, such as Data
Direct OBDC, SQL Anywhere, etc. For JDBC standard-based database
access (for products where Generic JDBC access is supported)
customer is requested to try to reproduce the issue on MySQL. It is
of utmost importance for the customer to provide SAP Customer
Assurance with as much detail as possible to establish that the
issue is an SAP product issue and not an issue with the database or
database driver being used.
SAP will consider all issues reported provided that the
conditions mentioned above have been met and Customer Assurance
will have further validated where the locus of the problem
originates. Customer Assurance may require access to the customers
environment and/or software to carry out further testing and
diagnosis.
If the issue being reported cannot be demonstrated to reside
with a SAP product, the issue will be deemed to reside with the
database vendor. Customers should be aware that standards-based
drivers most likely will not work out of the box and may require
additional configuration (sbo, etc.) and in depth technical
understanding of SAP BusinessObjects products and related
middleware technology.
Note that Standards based drivers are only supported for
relational databases unless otherwise noted in the PAR/PAM
document. OLAP data sources are currently excluded, as are
databases to be used as repositories (CMS, Audit etc.)
Important: It is advisable, whenever possible, to use an
explicitly listed, fully supported driver configuration, listed in
the PAR/PAM document, rather than a Standards-based driver.
-
Page 8 / 16
2009 SAP. All rights reserved.
[back to top]
6.2 SAP Platforms Support Timetable
SAP shall target to support vendor releases within the timeline
in the table below (timelines relative to the General Availability
of the software from the vendor).
SAP Direct Support
SAP Compatible Support
Vendor Major Release +SP/Minor No (1)
Vendor Minor Release +SP/Minor Immediate (2)
Vendor Incremental Updates
+SP/Minor Immediate (3)
(1) Compatible support for Vendor Major Release is generally not
granted due to high risk. If exceptionally granted, it will be
listed in the PAR/PAM documents (also refer to the conditions as
outlined in section 6.1.2). (2) If conditions as outlined in
section 6.1.2 are met, the platform Compatible Support will be
listed in the PAR/PAM documents. (3) Compatible Support is granted
automatically. Any exception will be documented in the PAR/PAM
documents.
6.3 Modifications in Support Level
6.3.1 Support Level Graduation
Platforms classified as Compatible, SAP ICC Certified or
Standard-based can all be graduated to Direct support using the
following as guidance.
Compatible platforms are automatic candidates for Direct Support
as they are supportable based on reference to their directly
supported parent. The objective is that Compatible platforms will
be targeted to become directly supported at the next SAP
BusinessObjects Service Pack and/or Major release. Acceptance for
Direct candidacy will be based on an overall assessment and
alignment with business need and investment focus. In the event
there are more platforms to graduate than resources permit within
the scope of any given project, Compatible platforms may be held
over in that status until the next increment. In the event of
vendor issuing another incremental release of a platform in
compatible support before the next SAP BusinessObjects Service Pack
and/or Major release, the higher version release will be targeted
for direct support.
Conditionally Supported (ICC Certified and Standards Based)
platforms can be requested for Direct Support consideration and
require a full business case justification outlining the value and
benefits to SAP that would be realized by this graduation.
6.3.2 Support Level Downgrade
Under certain circumstances, justified by reduced market share
and/or customer usage, Solution Management may decide to downgrade
the support level of a given platform. This modification will
generally, but is not limited to take place in a major release of
an SBOP product.
[back to top]
-
Page 9 / 16
2009 SAP. All rights reserved.
7 Support Policy - General Guidance The guidance outlined as a
part of the Platforms and Technologies Support Policy is that
Directly supported platforms additions are applicable to be
delivered in either SAP Service Packs or Major/Minor releases,
subject to the product applicability policy (5.1 above).
7.1 c-1 Platforms Major & Minor Release Support
This is also to be known as current minus one (c: the latest
current version, c-1: version before the now current version). In
general, SAP will simultaneously provide Direct Support to at most
two Major versions and within each version no more than two Minor
releases of any particular platform. SAP will generally, and when
possible, message end of support of platforms for SAP products one
Service Pack in advance.
7.1.1 Exceptions to the c-1 Platforms Support policy
In some cases, there are exceptions to the above described c-1
platforms support rule.
7.1.1.1 c platforms support
SAP will consider exceptions to the above defined policy for
those platforms considered to be strategic investments (but not yet
with large customer adoption) and consideration will be based on
the overall merit of a business case.
7.1.1.2 c-2 platforms support
Exceptions to support more than two versions and/or two releases
will be considered if a platforms prevalence is so great amongst
SAP customers that continued support of it is necessary. This
exception is granted by Solution/Product Management based on the
understanding of customer deployments and general market
direction.
7.2 Pre-SAP Beta Platforms Releases - Vendor
SAP products have a development cycle and release plan that is
independent of any supported vendor roadmap. As such, there will be
times when a supported vendor will release a new product that was
not in the originally planned scope of a SAP release (major or
service pack/minor release).
In the event that a new version of a directly supported vendor
product is released to GA before a planned SAP product reaches Code
Complete (end of code changes) stage, then SAP will consider GA
support for the newer vendor product as a part of the planned
release if possible, but is not committed to do so.
If the SAP product has reached the Code Complete stage when a
vendor releases a newer version and it was not included in the
scope of the product, then SAP will not provide Direct support for
the newer version at the planned SAP GA date, but will consider
Compatible support if it meets qualifying criteria.
Example: SAP Product X is planned for Code Complete on June 1.
Product X is set to support Application Server Z v1 and Database Y
v3; however the vendors release to GA Application Server Z v2 and
Database v4 prior to Product X reaching Code Complete. Product X
will attempt the inclusion of support for both Application Server Z
v1 and v2 as well as Database Y v4 and v4 at Product X RTM.
[back to top]
-
Page 10 / 16
2009 SAP. All rights reserved.
7.3 Platforms Support Discontinued - Vendor
End of support for specific platforms will be managed through
official SAP project releases. This encompasses SAP major, minor,
and service pack release vehicles. The decision to end support of a
platform in a project release will be made based on the vendor
communicated end of maintenance dates:
1. Vendors End of (Mainstream) Support
In general, SAP will discontinue support for a platform after
the end of support takes effect;
some vendors have a single end of maintenance date that ends it
all, and some have end of
mainstream support followed by an extended supported. In that
case, this is the end of
mainstream support.
2. Vendors End of Extended Support
SAP will continue to provide support for a platform in extended
support phase if the
customer deployment rate makes it prohibitive to discontinue.
For example, a Microsoft
Windows operating system release will often be supported by SAP
until the end of Microsoft
extended support period for that release.
IMPORTANT NOTE: a customer is expected to have an active
extended support contract
with the vendor. SAP does will not take responsibility for
problems that may stem from the
third party software that is in extended support.
The platforms support discontinuation decisions shall generally
be communicated internally to the Field and AGS one service pack /
minor release in advance.
[back to top]
8 Minimum Hardware Requirements Definition SAP will list for
each product release a recommendation on the minimum hardware
requirements for the product release to function normally. Minimum
hardware requirements are listed in the PAR/PAM documents. If a
listed minimum hardware requirement is found to be insufficient at
a customers deployment, it is suggested that the customer log a
Customer Support case on the topic and have it logged as a bug so
it is captured in the database. This information is valuable to the
engineering department and could lead to specific Business Object
fixes or a Customer Support authored Knowledge Base article.
9 Requesting Platforms Support Customer should submit their
request for new platforms support directly to the Idea place
https://cw.sdn.sap.com/cw/community/ideas/businessanalytics/sboenterprisesuitesupportedplatforms
(SAP Enterprise suite Supported platforms & Technologies).
10 Communicating Platforms Support and Platforms End-of-Life
This section deals specifically on how Platforms Support and/or End
of Life messages are communicated externally.
-
Page 11 / 16
2009 SAP. All rights reserved.
10.1 External Communication with Customers
Proposed platforms support changes (new or ending support) are
communicated externally to customers using avenues described below.
Primary external communication happens through the following
internal stakeholder groups:
AGS
Sales Consulting Stakeholder notification, where applicable,
will be comprised of any combination of the following
o Online PAR/PAM documents on BOPedia
https://cw.sdn.sap.com/cw/community/bobjtc/platforms
o Visible notice on Customer Support Portal
o SAP Notes
[back to top]
-
Page 12 / 16
2009 SAP. All rights reserved.
11 Appendix
11.1 Operating Systems version identification matrix
(Specific OS versions below are examples only)
Incremental Release Support for Operating Systems
Portal Server
Major Release
Minor Release
Incremental Release
Windows Name SPn (2008 R2 SP1)
Name SPn (2003 R2 SP2)
AIX x.y TLn (7.1 TL1)
x.y TLn (7.1 TL1)
Technology Level
x.y TLn (7.1 TL1)
HP-UX x.y patch nm (11.23 PHSS_nm)
x.y patch nm (11.23 PHSS_nm)
Patch x.y patch nm (11.23 PHSS_37201, )
Solaris x patch nm (10 kernel patch 112233,...)
- Patch x patch nm (10 kernel patch 112233, )
Red Hat x.y (6.2)
Update/Point Release
x.y (6.2 )
SuSe x SP (11 SP2)
Service Pack x SPn (11 SP)
11.2 Application Server version identification matrix
SAP Nomenclature
Application Server
Major Release
Minor Release*
Incremental Release
Oracle WebLogic XgRY PSn (11gR1 PS5) (aka 10.3.5)
xgRy PSn (11gR1 PS5) (aka 10.3.5)
Websphere X.Y.n.m (7.1.0.7)
x.y.N.m (7.1.0.7)
Fix Pack + Cumulative Patch
x.y.n.M (7.1.0.7)
Tomcat X.y.n (7.0.23)
x.Y.n ** (7.0.23)
x.y.n (5.0.23)
JBoss X.y.z.n (4.0.4 GA)
x.Y.z.n (4.0.4 GA)
Patch + bug fixes x.y.Z.n (4.0.4 GA)
SAP Netweaver X.Y EHPn SPSm (7.3 EHP1 SPS1)
(7.3.1 SPS1)
x.y EHPn SPSm (7.3 EHP1 SPS1)
(7.3.1 SPS1)
Support Package x.y EHPn SPSm (7.3 EHP1 SPS1)
(7.3.1 SPS1)
* - Minor release is typically indicated by a point release. **
Tomcat 5.5 is considered a major release because it is the first
Tomcat implementation of JDK 1.5.
[back to top]
-
Page 13 / 16
2009 SAP. All rights reserved.
11.3 Portal Server version identification matrix
SAP Nomenclature
Application Server
Major Release
Minor Release*
Incremental Release
Oracle WebLogic XgRY PSn (11gR1 PS5) (10.3.5)
xgRy PSn (11gR1 PS5) (10.3.5)
Websphere X.Y.n.m (7.1.0.7)
x.y.N.m (7.1.0.7)
Fix Pack + Cumulative Patch
x.y.n.M (7.1.0.7)
SAP Netweaver X.Y EHPn SPSm (7.3 EHP1 SPS1) (7.3.1 SPS1)
x.y EHPn SPSm (7.3 EHP1 SPS1) (7.3.1 SPS1)
Support Package x.y EHPn SPSm (7.3 EHP1 SPS1) (7.3.1 SPS1)
11.4 Browsers version identification matrix
Incremental Release Support for Portal Servers
Browser
Major Release
Minor Release
Incremental Release
Internet Explorer X SPn (IE9 SP1)
x SPn (IE9 SP1)
-
Safari X.y.z (5.1.2)
x.Y.z (5.1.z)
Maintenance Update
x.y.Z (5.1.2)
Firefox X (10)
- - -
Java (JRE) X Update n (Java 6 Update 30) (JRE 1.6 Update 30)
- Update x Update n (Java 6 Update 30) (JRE 1.6 Update 30)
[back to top]
-
Page 14 / 16
2009 SAP. All rights reserved.
x
11.5 RDBMS version identification matrix
RDBMS
Major Release
Minor Release*
Incremental Release
Apache Derby X.y.n.m Eg 10.8.1.2
X.y.n.m Eg 10.8.1.2
X.y.n.m Eg 10.8.1.2
Greenplum X.y.n.m Eg 4.1.1.5
X.y.n.m Eg 4.1.1.5
X.y.n.m Eg 4.1.1.5
HP Neoview X.y SPn Eg: HP Neoview 2.4
N/A Service pack
X.y SPn Eg: HP Neoview 2.4 SP4
HSQLDB X.y Eg 2.2
X.y Eg 2.2
IBM DB2 for LUW X.y.n Eg: IBM DB2 for LUW 9.5
X.y.n Eg: IBM DB2 for LUW 9.5
X.y.n
IBM DB2 for zOS
IBM DB2 for i
IBM Informix Dynamic Server
11.7
Ingres* X.y.m
Eg 10.1.0-121 X.y.m Eg 10.1.0-121
X.y.m Eg 10.1.0-121
MS SQL Server X.y.n.m1
Eg : 9.00.1399.06 V8 = MS SQL 2000 V9 = MS SQL 2005 V10= MS SQL
2008
X.y.n.m E.g.: 2008 R2
Service Pack
X.y.n.m Eg : 9.00.1399.06 1xxx= RTM 2xxx=SP1
MySQL X.y.m Eg 5.5.21
X.y.m Eg 5.5.21
X.y.m Eg 5.5. 21
Netezza X.y.n Eg: Netezza 5.0
X.y.n Eg: Netezza 4.6
X.y.n
Oracle DB X.y.n.m eg : 10.2.0.2
X.y.n.m eg : 10.2.0.2 aka : 1OgR2
X.y.n.m eg : 10.2.0.2
PostgreSQL* X.Y.Z Eg 8.3.16
X.Y.Z Eg 8.3.16
X.Y.Z Eg 8.3.16
Progress X.Yz X.Yz X.Yz
1 According to MS Knowledge base article (ID: 321185)
(http://support.microsoft.com/kb/321185), this is the MS SQL
Server product version
number returned by the following SQL command :
SELECT SERVERPROPERTY('productversion')
In addition, the product level (RTM, SP1, SP2, etc) and the
edition (Enterprise,
etc) can be consulted using the following command:
SELECT SERVERPROPERTY ('productlevel'), SERVERPROPERTY
('edition')
-
Page 15 / 16
2009 SAP. All rights reserved.
OpenEdge* Eg 10.2b Eg 10.2b NOT TESTED
Eg 10.2b
SAP HANA 1.0 SPS X (Revision Y) Eg 1.0 SPS3 (Rev 21)
Revision 1.0 SPS X (Revision Y) Eg 1.0 SPS3 (Rev 21)
SAP MaxDB X.y.m Eg 7.8.02
X.y.m Eg 7.8.02
X.y.m Eg 7.8.02
Sybase Adaptive Server
X.Y.Z
X.Y.Z X.Y.Z
Sybase IQ X.Y.Z X.Y.Z X.Y.Z
Sybase SQL Anywhere
X.Y.Z X.Y.Z X.Y.Z
Teradata X.y.n.m Eg : 13.10.00.01
X.y.n.m Eg : 13.10.00.01 Also referred to as v 13.1
X.y.n.m
-
Page 16 / 16
2009 SAP. All rights reserved.
2009 SAP BusinessObjects. All rights reserved. SAP and its
logos, BusinessObjects, Crystal Reports, SAP Rapid Mart, SAP Data
Insight, SAP Desktop Intelligence, SAP Rapid Marts, SAP Watchlist
Security, SAP Web Intelligence, and Xcelsius are trademarks or
registered trademarks of Business Objects, an SAP company and/or
affiliated companies in the United States and/or other countries.
SAP is a registered trademark of SAP AG in Germany and/or other
countries. All other names mentioned herein may be trademarks of
their respective owners.
[back to top]