Considerations for upgrading from version 5.2.0.x

Upgrading from Sterling B2B Integrator version 5.2.0.x to the latest version has certain impacts.

In addition to the following information, you must also see the information in Considerations for upgrading from version 5.2.5.x and Considerations for upgrading from version 5.2.6.x.

JDK 7 does not support the TLS_RSA_WITH_3DES_EDE_CBC_MD5 cipher

If you are using JDK 7 with Sterling B2B Integrator V5.2.5, and you want to use a cipher to secure the Sterling B2B Integrator dashboard, you must set one of the following values in the dashboardCipherSuite parameter in the security.properties_platform_asi_ext.in property file or in customer_overrides:
  • JDK (includes all strong ciphers except the one not supported by JDK 7)
  • Weak

Do not use Strong or All with JDK 7 or Sterling B2B Integrator will not start.

Reconciliation of HIPAA Level 5 code lists

When you upgrade to Sterling B2B Integrator, the customized HIPAA Level 5 code lists from the previous version are preserved in the system where they were entered. However, they are not the default code lists after the upgrade. After the upgrade, you must manually make any customized code lists the default code lists.

For example, if you have customized the ICD9 or HCPCSCPT code list in the previous version of Sterling B2B Integrator, after upgrading to the latest version, you must replace the default ICD9 or HCPCSCPT code list with the customized ICD9 or HCPCSCPT code list.