Configuring post-installation Oracle secure access

To securely access the Oracle database, you must configure each server in installation, which has access to the database. These servers are the domain server, primary storage server, secondary storage server, and synchronization server.

Important: In the following configuration, SSL certificates and Oracle Wallet are not allowed. Also, the configuration is enabled only for communication from the database server to a client.

Complete the following steps for the domain server, primary storage server, secondary storage server, and synchronization server.

  1. Stop the TADDM server.
  2. Configure your Oracle instance to work in the secure mode. For the detailed instructions, see the Configuring Network Data Encryption.
  3. If the database access data that you provided during the installation is invalid, correct it in the collation.properties file. Modify the following properties:
    • com.collation.db.url - a JDBC URL for the primary database.
    • com.collation.db.user- a user name that is used to access the primary database.
    • com.collation.db.password - a password that is used to access the primary database.
    • com.collation.db.archive.url - a JDBC URL for the archive database. It is usually the same as for the primary database.
    • com.collation.db.archive.user - a user name that is used to access the archive database.
    • com.collation.db.archive.password - a password that is used to access the archive database.
  4. Start the TADDM server.