Change the external Oracle database

If the SecureTransport Server uses an external Oracle database and any of the database settings change, you must change the corresponding settings in the Administration Tool.

  1. Log on to the SecureTransport Administration Tool as user dbsetup.
  2. Select Setup > Database Settings.
  3. The Database Setting page is displayed.
  4. Type the values necessary to connect to the new external database.
    • Host – The host name or IP address of the Oracle server
    • Port – The port used to access the server, 1521 is the default
    • User Name – The name of the user authorized to create the SecureTransport schema and populate it
    • Password – The password for the user, not displayed
    • Service Name – Used to connect a server
    • Use secure connection – When Use secure connection is checked, the connection between SecureTransport and the database server will be encrypted. If Use secure connection is checked, the following options should be configured:
      • Server Certificate DN (optional) – If the server is successfully authenticated (meaning its certificate is trusted), its DN can be checked. If a value is entered in this field, it will be compared with the server certificate DN. If they do not match, the connection won't be successful.
      • Enabled Protocols – List of enabled protocols. TLSv1 is the default protocol.
      • Enabled Cipher Suites – List of the enabled cipher suites.
      • NoteBefore secure connection is enabled, the issuers certificates of the database server certificate, should be imported in the Trusted CA certificates store.
      • TrustStore File Path – Browse and select the TrustStore file to import the trusted certificates.
    • Use Custom JDBC URL – Unchecked by default. When checked, you can specify a custom JDBC URL string for SecureTransport to use to connect to one or multiple Oracle databases. In the URL, you can specify an address list that lists the protocol, host, port, and service name of each database. In addition to the standard connection parameters, you can include additional properties to define specific behavior, for example, a connection via SSL. If the custom JDBC URL connects to your database using SSL, make sure the Use secure connection checkbox is selected.

      #Example

      JDBC URL with two support databases using both placeholders and data defined by the admin:

      jdbc:oracle:thin:${user}/${password}@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=OFF)(FAILOVER=ON)(ADDRESS=(PROTOCOL=TCP)(HOST=2.2.2.2)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=3.3.3.3)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=${databaseName})))
      NoteWhen specified, the custom JDBC configuration is kept on patch revert.
      NoteThe option to specify a custom JDBC URL is also exposed as a REST API resource.
  5. Click Test Connection to Oracle Database.
  6. If SecureTransport displays a failure message, correct the network, database, or other error reported and try again.
  7. Click Save.
Note You can enable encryption of the communication between the SecureTransport Server and the Oracle database by adding SQLNET.ENCRYPTION_SERVER=requested to the $ORACLE_HOME/network/admin/sqlnet.ora file for your Oracle server. For more information, refer to the Oracle documentation.
Note You can get the existing Oracle database configuration, update it and test the connection to an Oracle database using the respective Admin REST API resource /configurations/database/oracle.

Related topics:

Related Links