ADM Repository Reference Guide
Configure the Synchronization Process
To configure the synchronization process
1
Configure the sync.properties file located in the adm_olap directory:
N
An example file, sync.properties.example, is provided in adm_olap, to use as a template to
OTE
configure the synchronization process.
a
Make a copy of the sync.properties.example file and name it sync.properties:
cp sync.properties.example sync.properties
b
In the sync.properties file, modify the FTP information. Enter the proper credentials, host remote
directory, and whether or not to delete the files from the FTP server after the synchronization process
completes:
ftp.user=ftp-user
ftp.password=ftp-password
ftp.host=ftp-hostname
ftp.dir=remote-dir
ftp.local.dir=tmp
# filter FTP files: consider only files starting with the prefix.
ftp.file.prefix=adm_olap
# delete files from FTP when done?
ftp.delete.files=true
c
In the sync.properties file, ensure that the loader information points to the Oracle:
loader.exec=./load_oracle.pl
loader.dir=load
loader.data.dir=data
N
Use the same user credentials when setting up the External Reports Scheme Configuration
OTE
policy as described in "Creating the External Reports Scheme Configuration Policy" on page 11
d
In the sync.properties file, modify the archiving if necessary:
# archive option will save a local copy of the compressed data at the specified directory
archive=true
archive.dir=archive
archive and archive.dir defines whether or not to store the zipped files locally for history
tracking.
You can add the hooks if necessary. hook.before.load= and hook.after.load= allow custom
behavior just before the data loading and after the loading is complete. Such hooks are used to add
or drop indices, to add client specific data for loading together with ADM data, or any other desired
actions. The property contains the path to an executable script:
# This can be used, for example, to remove indexes before the data loading
# and re-create the indexes after the load is complete.
#hook.before.load=
#hook.after.load=
2
Configure the database loader for Oracle.
The Oracle loader script is configured using the oracle.properties file, that is located in the
unzip_path/adm_olap/load/ directory. An example file, oracle.properties.example, has been
provided in unzip_path/adm_olap/load/:
a
Make a copy of the oracle.properties.example file and name it oracle.properties:
cp oracle.properties.example oracle.properties
b
If you had defined a custom adm_olap user name and password when you had created the database
user as described in "Create the External Reporting Database User" on page 17, then change the user
name and password credentials accordingly:
18
VMware, Inc.