Documentation Center

Configuring the State Store database as part of an upgrade

The Content Deployer upgrade adds a section for the new State Store database to your Content Deployer configuration file, deployer-conf.xml. By default, the State Store is configured to reuse your Content Delivery Broker database. To give the State Store its own database (a recommended setup), reconfigure it in your deployer-conf.xml file(s).

Procedure

  1. In the configuration location of your combined Content Deployer, or in both your Content Deployer worker and your Content Deployer endpoint, open deployer-conf.xml for editing.
  2. Find the new <State> section, which looks as follows:
    <State>
      <Storage Adapter="DBVENDOR" driver="DBDRIVER">
        <Property Name="host" Value="DBHOST"/>
        <Property Name="port" Value="DBPORT"/>
        <Property Name="database" Value="DBNAME"/>
        <Property Name="user" Value="DBUSERNAME"/>
        <Property Name="password" Value="DBPASSWORD"/>
      </Storage>
    </State>
    where:
    • DBVENDOR is the database type of your Broker database (either mssql if your Broker database is Microsoft SQL Server, or oracle if it is Oracle), or a variable
    • DBDRIVER is the fully qualified class name of your JDBC driver, or a variable
    • DBHOST is the host name of your Broker database, or a variable
    • DBPORT is the port number of your Broker database, or a variable
    • DBNAME is the name of your Broker database, or a variable
    • DBUSERNAME is the user name of a user able to access your Broker database, or a variable
    • DBPASSWORD is the password for that user, or a variable
  3. Replace these items with the values for your dedicated State Store database. Note the following:
    • In some cases, you can keep things as they are. For example, if both your Broker database and your State Store database have the same database type (say, they are both Oracle databases), the Adapter and driver attributes can stay the same.
    • In some cases, you may want to introduce a new variable. For example, if DBNAME was a variable string like ${dbname} (which resolves to the name of the Broker database), you may want to replace it with, say, ${ssdbname} and ensure that it resolves to the name of your State Store database. To make it resolve to that name, set them as environment variables when you run your Content Deployer startup script or scripts, so that the system passes them to your configuration.
  4. After you have modified your deployer-conf.xml file or files in this way, save and close these files to commit your changes.