Initial Setup

Before using the log warehouse, perform the following setup and configuration steps on both servers in your environment: production server and log warehouse (CLW) server.

The following prerequisites must be met:
  • The CLW server must be installed and properly licensed.
  • Have the Cleo_Log_Warehouse.zip file available (provided by Cleo as part of fulfilment). This contains the objects necessary to perform log archiving and un-archiving.
  • From the CLW installation directory, edit the EbiServer_Standard.ini file to include this property:

    -Debi.isDataWarehouse=true

  1. The contents of the Cleo_Log_Warehouse.zip file will need to be extracted to a location on both servers. When extracted, several folders and files should appear, as shown here.
  2. On the production server, go to the conf folder and open the DataArchiver.properties file. Configure the following properties:
    For this Property... Enter...
    jdbc.driver The driver used to connect to the database.
    jdbc.url The URL required to access the production server database.
    jdbc.username The username required to access the production server database.
    jdbc.password The password required to access the production server database.
    storageManagerPath The location of the Storage Manager inside the production server from which the archiver will archive files.
    Note: This path must be specified correctly otherwise data can be lost.
    archiveDirectoryPath The location to output archived data zip files.
    Note: This directory must exist before running the Archiver.
    archiveNamePrefix The prefix to be applied to archive files (* .zip).
    archiveHarmony Determines if Harmony tables are included in the archive. Value of true will cause Harmony transfer data in the Clarify installed Postgres database to be archived along with the Clarify data. A value of false (default) will ignore checking Harmony tables for data.

    If including Harmony tables to be part of the archive process, then you must change the false to true. For example: archiveHarmony=true

    See Database Tables included in the CLW for a list of Harmony tables that may be archived.

    Note: All values are preset to Clarify server installation defaults. It is strongly recommended to not change any other properties in this properties file. Please first contact Support before making changes to any property files.
  3. On the production server, update the runArchiver batch file variable CLARIFY_HOME with the root folder of the production server installation. See the example below.
  4. On theCLW server, open the DataUnarchiver.properties file (located in conf sub-directory) and configure the following properties:
    All values are preset to Clarify server installation defaults.
    For this Property... Enter...
    jdbc.driver The driver used to connect to the database.
    jdbc.url The URL of the CLW server database.
    jdbc.username The username necessary to access the CLW database.
    jdbc.password The password necessary to access the CLW server database.
    archiveZipPath The path to the directory that contains the archive files to be processed (unarchived).
    storageManagerPath The location of the Storage Manager inside the CLW server that contains the transaction data.
    modeFlag The indicator for which mode the unarchiver should run; options include Insert (I) or Verification (V).
    • I – Insert Mode: This mode inserts any records into the database that are in the archive currently being processed, which are not in the database. Any files from the Storage Manager in the archive, which are not in the specified target Storage Manager, are copied over.
    • V – Verification Mode: This mode processes all detected .zip files, and indicates, through the unarchive log, the number of records that are in the unarchive log, but not in the database. No data is inserted into the database, and no files are copied into the Storage Manager.

    If unspecified, the unarchiver defaults to verification mode (V).
    Note: All values are preset to Clarify server installation defaults. It is strongly recommended to not change any other properties in this properties file. Please first contact Support before making changes to any property files.
  5. On the CLW server, update the runUnarchiver batch file variable CLARIFY_HOME with the root folder of the CLW server installation. See the example below.