Show Menu
TOPICS×

Configuring the Replication Service

You must configure the target Insight Server(s) to retrieve data from the Repeater on which the original event data is stored.
To configure the retrieval of data from a Repeater to a target Insight Server, you must edit the Replicate.cfg file provided in the Components folder on the target Insight Server(s) as described in the following procedure:
To configure the Replication Service on the target machine
  1. In Insight, on the Admin > Dataset and Profile tab, click the Servers Manager thumbnail to open the Servers Manager workspace.
  2. Right-click the icon of the target Insight Server you want to configure and click Server Files .
  3. In the Server Files Manager, click Components to view its contents. The Replicate.cfg file is located within this directory.
  4. Right-click the check mark in the server name column for Replicate.cfg and click Make Local . A check mark appears in the Temp column for Replicate.cfg.
  5. Right-click the newly created check mark in the Temp column and click Open > in Insight . The Replicate.cfg window opens.
  6. In the Replicate.cfg window, click Replicate.cfg , then component to view its contents.
  7. Edit the parameters using the following example and table as guides:
    For this parameter... Specify...
    Directories
    The directories on the Repeater that are to be copied (replicated) to the target Insight Server . The Replication Service allows the replication of multiple directories from a single Repeater .
    To add a new directory, right-click Directories and click Add new > Directory .
    Flatten Paths
    True or false. The action defined by this parameter’s setting depends on the setting of the Recursive parameter in this file:
    • If Recursive is false, Flatten Paths has no effect. Only the files at the top level of the directory specified by the Remote URI parameter are replicated.
    • If Recursive is true and Flatten Paths is false, the directory structure of the remote ( Repeater ) directory is duplicated exactly in the local path on the target Insight Server .
    • If both Recursive and Flatten Paths are true, no subdirectories are created in the local path. Instead, all files from the remote directory tree are placed in the top level of the local directory.
    Note: If both Flatten Paths and Recursive are true and files in the various subdirectories on the remote machine share the same name(s), the Replication Service may stop or other undefined behavior may occur.
    Local Path The storage location for the files retrieved from Repeater . The path is relative to the Insight Server installation directory.
    Recursive True or false. If false, only the files at the top level of the directory specified by the Remote URI parameter are replicated. See Flatten Paths in this table.
    Remote URI The URI, including a file mask, to access the Repeater’s file store. The Communications.cfg file on the Repeater should be configured so that the event data can be accessed using this URI. See Monitoring Event Data Space .
    Server Parameters for the Repeater from which the target Insight Server retrieves event data files.
    Name Optional. The name to identify the Repeater .
    SSL Server Common Name Required only if Use SSL is set to true. Common name of the Repeater on which the event data is stored. This name must match the common name listed in the communications certificate for the machine.
    Address Host name or numeric IP address of the Repeater on which the event data is stored. The server’s common name is not a valid entry.
    Port Port used for data transmission. The default port is 80.
    SSL Client Certificate Required only if Use SSL is set to true. Name of the license certificate used to connect to the Repeater .
    Use SSL
    Determines whether SSL is used for the data transmission. The options are true or false, and the default value is false.
    Note: Using SSL is not recommended because it can negatively affect performance. Note that SSL is not required unless the network connecting the Repeater to the target machines is insecure.
    End Time, Start Time
    (Optional) Limits the set of event data files copied to the target Insight Server to those that contain data in the range defined by Start Time and End Time. If Start Time is set, event data files in which all log entries are from earlier than the specified start time are not copied. If End Time is set, event data files in which all log entries from the time specified or later are not copied. If only part of the data in a file is in the specified range, then the entire file is copied to the target machine.
    Adobe recommends using one of the following formats for the time:
    • January 1 2013 HH:MM:SS EDT
    • Jan 1 2013 HH:MM:SS GMT
    Note: You must specify a time zone. The time zone does not default to system time if not specified. If you wish to implement Daylight Saving Time or a similar clock-shifting policy, you must save the .dst file containing the appropriate rules in the Base\Dataset\Timezone directory on the Insight Server machine. For a list of supported time zone abbreviations and information about implementing Daylight Saving Time, see Time Zone Codes .
    Note: To use these settings, the names of the event data files must begin with an ISO date (YYYYMMDD), and each file must contain data for the 24-hour period starting at 12 AM GMT on that date.
  8. Save your changes to the server by doing the following:
    1. Right-click (modified) at the top of the window and click Save .
    2. In the Server Files Manager, right-click the check mark for the file in the Temp column and select Save to > < server name > .
This example illustrates how files are copied if both the Flatten Paths and Recursive parameters are set to true.
Suppose Remote URI is /RemoteRoot/ and Local Path is [E:\LocalRoot\]. On the remote ( Repeater) machine, the files are organized as follows:
  • /RemoteRoot/fileA.txt
  • /RemoteRoot/Dir1/fileB.txt
  • /RemoteRoot/Dir2/Subdir3/fileC.txt
When replication is complete, the local directory has the following files:
  • E:\LocalRoot\fileA.txt
  • E:\LocalRoot\fileB.txt
  • E:\LocalRoot\fileC.txt
In the local directory, no subdirectories are created, and all files from the remote directory tree are placed in the top level of the local directory.
If files in the various subdirectories on the remote machine share the same name(s), the Replication Service may stop or other undefined behavior may occur.