Sterling B2B Integration

Please note that this list is not exhaustive and should be viewed as a complement to the official documentation, not a replacement for it. You may find it helpful to review this list, to prepare for common and critical steps during the upgrade process and ensure that they are not missed.

Planning - Compatibility, Prerequisites, and System Requirements

• 6.0.0 - What’s new and What’s deprecated
• 6.0.1 - What’s new and What’s deprecated
• 6.0.2 - What’s new and What’s deprecated
• 6.0.3 - What’s new and What’s deprecated
• 6.1.0 - What’s new and What’s deprecated
• Blog of major changes which are available with v6.0.X/v6.1.X releases

• Fix List for 6.0.x
• Fix List for 6.1.x

3. Upgrade/compatibility matrix link - Make sure the version of B2Bi that you are upgrading to is a supported upgrade path.



4. If upgrading to B2Bi 6.1.x, you can install or upgrade to the latest Fix Pack version of B2Bi in a single step without installing the intermediary version due to the New Media Changes.



5. Software Product Compatibility Reports – Search for “IBM Sterling B2B Integrator” and select the version you are upgrading to. Make sure you verify all System Requirements for the version of B2Bi that you are upgrading to, including the additional information found by following the “Detailed system requirements” link. This verification should include at least the following:

• • Operating System
  • Databases
  • IBM Installation Manager (comes with the media)
  • JDK
  • Web Browsers
  • Disk Space
  • Memory
  • Processors
  • IBM MQ (if using adapter containers)

• B2Bi 6.0.0
• B2Bi 6.0.1
• B2Bi 6.0.2
• B2Bi 6.0.3
• B2Bi 6.1.0

Post-Installation Steps

• If using adapter containers, configure IBM MQ properties in B2Bi.
  
  
• Remember to upgrade Remote Perimeter Servers, as they are a separate component.
  
  
• If B2B REST APIs were installed in the previous version, manually re-install B2B REST APIs using the newer b2bAPI.jar from your upgraded B2Bi.
  
  
• Upgrade to the appropriate JDBC driver
  

• Review dynamic clustering if using a clustered environment.
  • Dynamic clustering is now enabled by default via dynamic.cluster.enable=true.
  • Ensure that customer_overrides.properties doesn’t have any references to jgroups_cluster, as this will interfere with the new dynamic clustering settings.
    
    
• After upgrading, verify that any existing entries in customer_overrides.properties are still valid for the version which you have upgraded to. If not, then comment out or remove any invalid entries.