Upgrading Sterling B2B Integrator in an SSL-enabled environment for DB2

You can upgrade to any future release of Sterling B2B Integrator in an SSL-enabled environment for DB2.

1. Stop Sterling B2B Integrator.
2. Access the following property files and revert all the changes that are applied to enable SSL option.
   Note: It is recommended to take a backup of all the property files before upgrade.
   1. Update sandbox.cfg and replace the following with non-SSL ports.

      
      DB2_PORT
      DB_PORT
      YANTRA_DB_PORT 
      

   2. Revert the changes in the jdbc.properties file that are configured with non-SSL information.

      
      db2Pool_local
      db2Pool_NoTrans
      db2Pool
      

   3. Revert the changes in the jdbc.properties_platform_ifcresources_ext file that are configured with non-SSL information.

      
      db2ArchivePool
      db2UIPool
      

3. Run setupfiles.sh on Unix/Linux and setupfiles.cmd on Windows and later run deployer.sh on Unix/Linux and deployer.cmd on Windows.
4. Start the services where the communication is now non-SSL to make sure Sterling B2B Integrator is available for access.
5. Upgrade to the latest Fix Pack release of Sterling B2B Integrator and start the services.
6. Stop the Sterling B2B Integrator services and update all the changes to enable SSL option. Run setupfiles.sh on Unix/Linux and setupfiles.cmd on Windows and later run deployer.sh on Unix/Linux and deployer.cmd on Windows.
7. Restart the Sterling B2B Integrator services.