Statement of direction for Compatibility Matrix
While every effort is made to provide accurate, forward-looking guidance on product direction to assist our customers in buying and planning decisions, we cannot guarantee that the intentions stated here are final and binding.
Following topics are provided:
Statement of direction: Compatibility matrix
May 1, 2015
This statement of direction describes changes in the BMC Remedy Action Request (AR) System Compatibility Matrix introduced in version 9 and provides an indication of future direction.
BMC Remedy AR System supports many combinations of the most popular hardware, operating systems, web servers, databases, and browsers on the market. This support is captured in the published compatibility matrix. With each release, BMC evaluates support for the combinations listed in the compatibility matrix, including additions, removals, and minimum version changes based on customer and market feedback. All minimum versions support an "or later" policy. Certification of newer versions by BMC typically lag behind the vendor’s release. However, as long as the vendor respects backward compatibility, BMC does not anticipate major issues with certification.
For any items not mentioned in this posting, the details in the compatibility matrix are not expected to change.
Changes to database compatibility
The following list describes expected changes to the Database section of the compatibility matrix:
- Remove support for the IBM DB2 database.
- Remove Sybase from the compatibility matrix (removal of Sybase support has already been announced).
- Raise the minimum support for Microsoft SQL Server to 2008 SP2 from the current 2005.
- Raise the minimum support for Oracle database to 11gR2 patchset 3 (126.96.36.199.0) from its current 11gR1.
- Certify the platform running on SQL Server 2014 shortly after the next release.
- Certify the platform leveraging the SQL Server Always On capability in 2012 and 2014 shortly after the next release.
Changes to operating system compatibility
The following list describes expected changes to the Operating System section of the compatibility matrix:
- Add CentOS as a supported operating system (currently for BMC Remedy Mid-Tier only).
- Raise the minimum support for Microsoft Windows Server to 2008 R2 x64 from its current 2003.
- Drop support for Windows Server 32-bit for platform.
- Certification with Oracle Solaris has not been included in this release but will follow shortly after the release.
- HP-UX and AIX operating systems have not been certified for this release, and BMC is considering dropping them from the compatibility matrix.
Changes to Web Server compatibility
The following list describes expected changes to the Web Server section of the compatibility matrix:
- Raise the minimum support for Apache Tomcat to 7.0.53 from its current 6.x.
- Raise the minimum support for Microsoft IIS to 7.5 from its current 6.x.
- Raise the minimum support for Oracle Weblogic to 11g from its current 10g.
- Raise the minimum support for RedHat JBoss to EA 7.1 from its current 5.x.
- Raise the minimum support for IBM Websphere to 8.5 from its current 7.x (due to no support for Java 1.7).
BMC Remedy Smart Reporting is currently supported using the Apache Tomcat web server only. Future releases will expand this coverage.
Change to enabling technology compatibility
Raise the minimum support for Java to 1.7.0 Update 55 from its current 1.6 .
Change to third-party product compatibility
Raise the minimum support for Microsoft Internet Explorer to 9 from its current 8.
Intended direction for enhancements to the BMC Remedy AR System API
A common way to integrate with the BMC Remedy AR System platform is through either the C API or the Java API. BMC has seen an increased rate of adoption around the Java API. As we develop new features for the system, we will focus on exposing those new features through the Java API. This focus means that some new features will not be available through the C API.
Frequently asked questions
|What are my options if I am running DB2 today and I want to upgrade?||Typically, you will need to export your data and import it to another system that is running another database. If you need help, we recommend that you engage with BMC Professional Services or a BMC Partner. There is currently no automated migration tool tested by BMC to move from DB2 to another supported database.|
|Will not having all the features available to me via the BMC Remedy AR System C API impact my implementation?||Any existing implementation that leverages the C API will not be impacted. However, new system capabilities that are introduced might not be accessible through the C API.|
|Will changes in the C API impact my current implementation?||No, changes to the compatibility matrix are tied to a version release and do not typically impact previous versions.|
|Why did you change so many minimum versions?||As new technology becomes available, older versions might not support newer features. BMC constantly evaluates new and older versions of software and moves minimum supported statements as we see adoption moving forward.|
|Why are you dropping Microsoft IE 8?||Microsoft Internet Explorer 8 has been on a steady decline in usage (see http://www.theie8countdown.com/ ) and is being phased out in many organizations. Newer approaches to user experience typically require support for features that the vendor does not support. Resetting the minimum to version 9 also aligns with the minimum versions published by BMC MyIT and BMC Smart IT functionality.|