Considerations for installing or upgrading using Certified Container
You can install or upgrade to Sterling B2B Integrator using a Certified Container. However, using Certified Container for Sterling B2B Integrator has certain limitations. You must consider the limitations carefully before you decide to install or upgrade.
|Integration with Global Mailbox is not supported.||Install Sterling B2B Integrator and Global Mailbox using IIM.|
|Third-party jars cannot be installed using the Customization UI or REST APIs if the size of the jar is greater than 2 GB.||Use the command line utility to install the third-part jars. For more information, see Installing third-party jars using CLI.|
|You cannot change the install order for a custom jar that is added using UI/Rest API when Sterling B2B Integrator is installed using Certified Container.||To change the install order for custom jars, you must copy the dynamicclasspath.cfg file outside the Certified Container, make the changes, and then copy the file into the container. For more information, see Changing the install order for custom jars.|
|After upgrading from previous versions (< v6.0.0) to the latest version using Certified Container, none of the customizations are copied to the latest version.||When you upgrade to Sterling B2B Integrator using Certified Container,
none of the customizations (customer override properties, custom jars, custom services, user exits,
UI branding, and custom SFG Extensions) are copied automatically to the latest version. You must
reinstall the customizations on each Sterling B2B Integrator node.
For more information on how to identify custom services by querying the database, see Identifying custom services by querying the database.
|Hardware Security Modules (HSM) integration is not supported.||There is no workaround.|
|Integration with ITX and ITXA is not supported out of the box with Certified Container deployment.||There is no workaround.|
|SPE Integration module is not supported||There is no workaround.|