Bookshelf Home | Contents | Index | PDF     

Siebel Analytics Web Administration Guide > Administering the Siebel Analytics Web Catalog > Replicating Siebel Analytics Web Catalogs >

Using the Siebel Analytics Web Replication Agent

The Siebel Analytics Web Replication Agent (sawrepa) is a command line utility that carries out the common replication tasks such as copy, export, import, mark for replication, and purge log.

The Siebel Analytics Web Replication Agent needs information about the Siebel Analytics Web servers and the replication tasks. This information is stored in the config.xml configuration file, which is located in the same directory as sawrepa executable.

The command line for the Siebel Analytics Web Replication Agent uses the following format:

sawrepa [/C path] command [command parameters]

The path following the /C specifies the path to the config.xml file. The command can be one of the following:

  • mark
  • purge
  • remotecopy
  • run

mark

Adds or removes the Replicate flag on specified folders on all or specified Siebel Analytics Web servers. Setting the Replicate flag does not mean that the corresponding catalog item is immediately replicated. Only future modifications are noted in the catalog log and subsequently get replicated. The syntax for the mark command is:

sawrepa [/C configfile] mark {all|servername} [/n] [catalogfolders]

  • all | servername. The name of the Siebel Analytics Web server (or all) on which to run the mark command. If you use a specific server, the name you specify must match the name attribute of the corresponding server tag in the config.xml file.
  • /n. If present indicates that the Replicate flag should be removed, otherwise it is added.
  • catalogfolders. A list of folders on which to add or remove the Replicate flag. Separate each folder in the list with a space. If you do not specify any folders, then sawrepa executes the mark command on every folder for the specified servers listed in the config.xml file.

    purge

    Cleans up obsolete log entries on specified folders on all or specified Siebel Analytics Web servers. The configuration file contains an entry (LogExpiresHours) which defines the minimum time period for which a replication log should be preserved. The timestamp for determining obsolete items is set using this period. The syntax for the purge command is:

    sawrepa [/C configfile] purge {all|servername} [catalogfolders]

  • all | servername. The name of the Siebel Analytics Web server (or all) on which to run the purge command. If you use a specific server, the name you specify must match the name attribute of the corresponding server tag in the config.xml file.
  • catalogfolders. A list of folders to clean. Separate each folder in the list with a space. If you do not specify any folders, then sawrepa executes the purge command on every folder for the specified servers listed in the config.xml file.

    remotecopy

    Exports the contents of the specified catalog folders from the source server and imports them in the destination server. The syntax for the remotecopy command is:

    sawrepa [/C configfile] remotecopy sourceServer destinationServer catalogfolders

  • sourceServer. The name of the source server as specified in the config.xml file.
  • destinationServer. The name of the destination server as specified in the config.xml file.
  • catalogfolders. A list of folders to clean. Separate each folder in the list with a space. If you do not specify any folders, then sawrepa executes the purge command on every folder for the specified servers listed in the config.xml file.

    run

    Executes all replication tasks that are setup in config.xml file and that have not expired. This command does not have any runtime arguments. The syntax for the run command is:

    sawrepa [/C configfile] run

    Replication tasks can expire if the replication log was cleaned after its last successful run. If that is the case manual intervention is required. An administrator can synchronize the contents of replicated folders using the remotecopy command, then purge the replication log and then reenable the task by deleting lastPerformed timestamp in the config.xml file.

    •     
    Siebel Analytics Web Administration Guide