Prerequisite

In order to establish a secure database connection, ensure, that the DBMS's (Oracle/MSSQL) public key certificate is known by the Product 360 Supplier Portal's Java Runtime Environment (JRE). There are different possibilities to achieve this. Please refer to the JSSE Reference Guide (https://docs.oracle.com/javase/8/docs/technotes/guides/security/jsse/JSSERefGuide.html) and here especially the chapters "Creating an X509TrustManager" and "Creating a Keystore to Use with JSSE".

Configure Product 360 Supplier Portal

Ensure to do the following configuration changes on all Product 360 Supplier Portal servers. The Product 360 Supplier Portal needs to be restarted in order to have changes take effect.

• in <INSTALLATION ROOT>/configuration/configuration.properties:

  • for Oracle:

    • specify the Oracle Server's TCPS port as value of the property database.port (and naturally also the other database parameters like host, database,...). For details, please refer to the chapter "Supplier Portal Configuration".

    • change the protocol to "tcps" in the property database.url.oracle so the value is like follows: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=${database.server})(PORT=${database.port}))(CONNECT_DATA=(SERVICE_NAME=${database.name})))

  • for MSSQL:

    • specify the MSSQL Server's secure port as value of the property database.port (and naturally also the other database parameters like host, database,...). For details, please refer to the chapter "Supplier Portal Configuration".

    • add ";encrypt=true" to the end of the JDBC connection URLs in the property database.url.mssql

    • for further details, please refer to Microsoft's SQL Server documentation: https://docs.microsoft.com/en-us/sql/connect/jdbc/connecting-with-ssl-encryption?view=sql-server-ver15