Post upgrade configuration checklist
After you upgrade Sterling B2B Integrator you must complete some post upgrade configurations and tasks depending on your system and business needs.
The following table lists some of the tasks that you can complete after you upgrade Sterling B2B Integrator. Review all the tasks in the checklist. Some tasks might not be required.
If you are using a clustered environment, you must consider additional tasks as applicable. For more information, see Post-upgrade tasks for a clustered environment.
| Task | Your notes |
|---|---|
| Change the Administrative Password. The upgrade process changes the administrative password to the default password. After the upgrade, change the password to minimize security risks. This is the Admin password for logging into the UI. |
|
| After installation, several default user accounts are automatically created to get you started. For security purposes, the system administrator should update all default user account passwords immediately after installation is completed. See Changing default user account passwords. | |
| Disable Services. The upgrade process enables services that might have been disabled before the upgrade. If you want to disable these services again, you must disable them in after the upgrade process. |
|
| When you upgrade to Sterling B2B Integrator v6.0 by using Docker, custom services are not copied to the database. You must reinstall custom services on each Sterling B2B Integrator node. For more information, see Identifying custom services by querying the database. | |
| Downloading the Sterling B2B Integrator tools | |
| Change the Network Interface Bindings | |
| Update Dashboard for Network Interface Binding Changes | |
| Enable Business Processes. During the upgrade process, your customized business processes are preserved, but they may not be the default business process. Review the business processes and enable the customized versions. |
|
| Configuring the property files | |
| Add cdinterop files. During the upgrade, the cdinterop files were replaced. Copy the customized version into the upgrade. |
|
| Updating the sandbox.cfg file with a new JCE file | |
| Review the EDI Sequence Check Queue | |
| Configure Document File Systems. Before upgrading, you recorded the path to the File System. After the upgrade, copy/mount the documents to the new installation directory. The directory structure (path to the File System) must be the same in the current and in the upgraded system. |
|
| Add Third-Party Libraries. If you added third-party libraries to configure adapters for the previous release, you need to add each of the libraries again after you complete the upgrade. See the documentation for each third party adapter you use. |
|
| Configure Services and Adapters | |
| Configure JDBC Adapter and Lightweight JDBC Adapter. Storage locations of the database pool properties that allow the JDBC adapter and the Lightweight JDBC adapter to communicate with your external database have been streamlined. The poolManager.properties file has been eliminated and some of its pool properties are now included in the jdbc.properties file, along with some new properties. You must manually update your existing jdbc_customer.properties.in file to add some new database pool properties. If you do not have a jdbc_customer.properties.in file, create one since customer.properties are not affected by product updates. Note: In
docker, you cannot edit the
jdbc.properties or
jdbc_customer.properties.in files directly within the container. You must use the
docker cp command and copy it outside and update it with the properties that needs
to be changed for creating data pools. Then, you must copy the updated file back into the container
using the docker cp command again. |
|
| Configure File System Adapter and Command Line2 Adapters | |
| Configure Odette FTP Adapter | |
| Add Advanced File Transfer Tab | |
| Restore Performance Tuning Configuration | |
| Reconfigure Archive Settings | |
| Correct Missing Manager IDs If you created a Manager ID with no corresponding User ID in your previous version, the Manager ID may be missing after upgrading. If this occurs, create a user in the system with a User ID that matches the missing Manager ID. |
|
| Configure JVM Containers | |
During installation, the dbVerify utility compares the list of
standard indexes with those present in the database and drops the custom indexes. You should
recreate the custom indexes after the installation is complete. |