Configuring the Microsoft SQL Server database

Before you install Sterling B2B Integrator with the Microsoft SQL Server database, you must configure the database.

  • If you are reinstalling the software, be aware that data in your existing database is deleted. To preserve the data, either back-up your existing database or save it with a different name.
  • After you create and configure your database, recycle the database. Restart the database to apply the changes.
  • You can use the Microsoft SQL Server Always ON feature-enabled database to install Sterling B2B Integrator. This feature provides high availability at the database level. In a multi node environment, if failover occurs, the secondary node takes over as the primary node with minimal interruption.
Note: Named instances of MS SQL server are not supported.
Use the following checklist to configure Microsoft SQL Server for Sterling B2B Integrator:
Item Microsoft SQL Server Database Configuration Checklist
1 If you do not have Microsoft SQL Server installed, follow the installation procedures in the SQL Server installation manual.

Refer to the Microsoft SQL Server documentation on creating the database, including creating a schema repository, login, and table space.

Be sure to install the correct version and patches.

See Software Product Compatibility Reports for supported version information.
2 Allow DBO (Database Owner) permission to the user.
3 Set Microsoft SQL Server parameters.
4 Install the JDBC driver in Microsoft SQL Server.
5 Configure Sterling B2B Integrator for data traffic encryption.
6 Configure the snapshot feature.
During the upgrade of Sterling B2B Integrator, if you wish to use the latest versions of TLS (1.1 and 1.2) with Microsoft SQL Server (2012, 2014 or 2016), perform the following steps:
  1. Replace the existing MS SQL JDBC driver jar from the following locations with mssql-jdbc-6.4.0.jre7.jar file.

    <B2Bi Install Dir>/dbjar/jdbc/MSSQL

    <B2Bi Install Dir>/jdk/jre/lib/ext
    Note: Make sure that there are no spaces in the directory name for the JDBC drivers.
  2. Change the following entries of the old jar file to the new jar file in sandbox.cfg file under <B2Bi Install Dir>/properties/sandbox.cfg.

    DB_DRIVERS=

    JDBC_DRIVER=

  3. Add the following at the end of the sandbox.cfg file to disable server authentication.
    
trustServerCertificate=true
tls_version=TLSv1.2. The allowed values are TLSv1.0, TLSv1.1 or TLSv1.2.

    Save the changes.

  4. Change the DB_JAR= references of the old jar file to the new jar file in dynamicclasspath.cfg.in under <B2Bi Install Dir>/properties/dynamicclasspath.cfg.in.
  5. Save the changes.
  6. From <B2Bi Install Dir>/bin, run setupfiles.cmd for Windows or setupfiles.sh for Linux or Unix.
  7. From <B2Bi Install Dir>/bin, run deployer.cmd for Windows or deployer.sh for Linux or Unix.

Installing Sterling B2B Integrator with TLS enabled Database Connections

For fresh installations of the Sterling B2B Integrator version 6121, make sure to use TLS version 1.2 if the DB connection is required to be established over TLS. You can update this setting in the IIM GUI when the DB vendor chosen is MSSQL.