Configuring a connection to the Content Data Store

A number of Content Delivery microservices require a connection to the Content Data Store (also called the Broker database). To configure this connection, resolve placeholders in a Storage element in the Storage Layer configuration file of the microservice, cd_storage_conf.xml.

Before you begin

Before performing this task, you must have installed and set up the Content Data Store.

About this task

The following microservices require a connection to the Content Data Store:
  • Content Service
  • Content Deployer

Procedure

  1. Go to the configuration location of the microservice.
  2. Resolve the namespaceprefix placeholder, as found in the Namespace element in cd_storage_conf.xml, to the value ish.
  3. Resolve the following placeholders, as found in cd_storage_conf.xml, in the Storage element that has its id set to defaultdb:
    PlaceholderDescription of value
    dbtypeThe type of database:
    • MSSQL if you have a Microsoft SQL Server database
    • ORACLESQL if you have an Oracle database
    dbpoolsizeThe size of the database connection pool. Only modify this value if the default value as specified in the configuration file does not work in your setup.
    dbretryattemptsThe number of times a connection should be retried in the event of a failure to connect. "5" would be a good value for this attribute.
    dbclassThe Java class for the data source:
    • com.microsoft.sqlserver.jdbc.SQLServerDataSource if you have a Microsoft SQL Server database
    • oracle.jdbc.pool.OracleDataSource if you have an Oracle database
    dbhostThe host name of the database server. Oracle users: the attribute is called serverName, but Oracle calls this setting HOST in, for example, its tnsnames.ora file.
    dbportThe port number of the database server.
    dbnameThe name of the database. Oracle users: the attribute is called databaseName, but Oracle calls this setting SERVICE_NAME in, for example, its tnsnames.ora file.
    dbuserThe name of a user who can access the database. Oracle users: Oracle also uses the word "schema" to refer to the user name.
    dbpasswordThe (encrypted) password of the user who can access the database.
    dbencryptMicrosoft SQL Server users: Encrypt the connection to the database if this property is set to true. Defaults to false.
  4. If your microservice is connecting to Oracle RAC, do the following:
    1. Open cd_storage_conf.xml for editing.
    2. Find the Storage element with its id attribute set to defaultdb.
    3. Within this element, find the Property element with its Name attribute set to databaseName, and change databaseName to serviceName.
    4. Save and close cd_storage_conf.xml
  5. If you are connecting from Content Deployer to the Content Data Store, you can also resolve the dblogintimeout property, which specifies the amount of time (in milliseconds) after which the Content Deployer considers a login attempt to have timed out. But you should only modify this value if the default value as specified in the configuration file does not work in your setup.