Things to take into account when planning the upgrade from ISBI 5.2.4.1 to ISBI 5.2.6.2 on RHEL 5

Body

When you are preparing the upgrade e.g. from ISBI 5.2.4.1 to ISBI 5.2.6.2 on a RHEL 5 environment (partly also affecting other versions and environments) please ensure to fulfil the following aspects:

1. RHEL 5 has to be upgraded to RHEL 6 or RHEL 7
Redhat Enterprise Linux (RHEL) version 5 is no longer supported for ISBI 5.2.6 (see http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=3F8014F0EC0F11E38B73BF6573FF9933&osPlatforms=Linux&duComponentIds=S001|S007|S008&mandatoryCapIds=9|13|25|26)
But "Red Hat does not support in-place upgrades between major versions 4, 5 and 6 of Red Hat Enterprise Linux." (found here: https://access.redhat.com/solutions/21964)

So you have to evaluate which is the migration path you want to follow (please call IBM Professional Services for assistance):

A) new Environment
- new RHEL 7 server with new fresh ISBI 5.2.6.2 connecting to a new blank ISBI DB
- in parallel for some month old existing ISBI 5.2.4.1 for smooth migration, as backup and to review data if needed
pro: clean setup, interfaces and partners can be migrated one after another (and not all at once), old system is running as backup in parallel
con: new hardware needed

B) new OS, keep DB and filesystem
- new RHEL 6 server
- attach ISBI 5.2.4.1 filesystem to new server (requires e.g. some IP config changes) and point to existing ISBI DB
- upgrade to ISBI 5.2.6.2 following guideline (see pullet point below: "5. IIM is mandatory for installation")
con: needs to be tested (incl. rollback scenarios)
pro: kind of in-place upgrade
- optional: upgrade afterwards RHEL 6 to RHEL 7 (please contact Red Hat if this supported)

2. SSL version 3 is no longer available
- TLS 1.2 is the default now
- partner that rely on old SSL3 cannot connect any more, so partners should be informed
- hint: no support for Java 8, thus still limited to Java 7 cipher suites

3. some Services and Adapters have been removed in ISBI 5.2.6.x
- e.g. WebSphere MQ Adapter is no longer available (if needed see IBM TechNote "How to migrate from WebSphere MQ Adapter to WebSphere MQ Suite Services in ISBI" http://www-01.ibm.com/support/docview.wss?uid=swg21976539)
- full list of removed services and adapter can be found in the IBM Knowledge Center: https://www.ibm.com/support/knowledgecenter/SS3JSW_5.2.0/com.ibm.help.manage_svcs_adpts.doc/CS_SvcsRemoved.html
- this might require migration and development effort (e.g. change of BPs needed)

4. changed list of supported Web Browsers
- IE: 10 and 11 (no IE 7)
- Firefox 41+
- no Chrome
- see http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=3F8014F0EC0F11E38B73BF6573FF9933&osPlatforms=Linux&duComponentIds=D003|D002|S001|S005|S004|S006&mandatoryCapIds=30|125|9|13|25|184|26

5. IIM is mandatory for installation
ISBI 5.2.6.x can only be installed using IBM Installation Manager (IIM)
- we do recommend to use the non-Admin mode
- there is a "Step by step guideline how to upgrade from ISBI 5.2.4.1 to ISBI 5.2.6.2 on RHEL 5" (see blog entry /support/pages/node/1121433)

6. HSM integration should be validated
The "Known issues" section in the "Sterling B2B Integrator V5.2.6.2 Release Notes" (see http://www-01.ibm.com/support/docview.wss?uid=swg27047881#knownissues) is listing two HSM related topics.
- so we do recommend to validate that handling of HSM certificates is working in ISBI 5.2.6.2 as expected and needed

7. Perimeter Servers may require also OS upgrade
http://www.ibm.com/support/knowledgecenter/SS3JSW_5.2.0/com.ibm.help.sys_rqmts_supplement.doc/supp_sys_rqmts_perim_srvr.html states "Perimeter servers are supported on the same operating system and JDK combinations as Sterling B2B Integrator. The operating system and JDK version that the perimeter server uses do not need to match the operating system and JDK version of Sterling B2B Integrator."