To receive data from the cloud to an on-premises database, setup and configure client_receive.properties as follows:
- Extract sync-client.zip.
$ unzip sync_client.zip
$ cd sync_client
- If the target Unifier database exists and is not empty, then run clear_all_unifier.sql from current directory against the target Unifier schema.
- Unzip sync-client.zip available in the present working directory and enter the resulting sync-client directory.
$ unzip sync-client.zip
$ cd sync-client
- If on a Unix or Linux system, set the executable flag on the shell scripts.
$ chmod u+x *.sh
- To receive data from the cloud to an on-premises database, edit client_receive.properties as follows:
- sync mode: CLIENT This information is pre-populated.
- sync type: RECEIVER This information is pre-populated.
- sync.name: A unique sync name to identify the sync configuration. Obtain this information when you contact Oracle Support. For more details, see Prerequisites to Sync Unifier Cloud and On-Premises Data..
- sync.number: The number of the sync configured in the sync server. Obtain this information when you contact Oracle Support. For more details, see Prerequisites to Sync Unifier Cloud and On-Premises Data.
- target.db.host: The host name (or IP) of the machine on which the Unifier target database is hosted. For example, localhost.
- target.db.port: The port number for the Oracle instance on which Unifier target database is created. For example, 1521.
- target.db.service: The service name of the Oracle instance on which Unifier target database is created. For example, pdborcl.
- target.db.type=UNIFIER
- target.db.schema=Database username of the Unifier target database.
- target.db.syncuser=The username of the sync-client database schema that will be created on same Oracle instance as the Unifier target database. It should not be the name of an existing schema, as this schema will be created during setup. This schema user must contain an underscore ("_") character. For example, t_syncuser.
- target.db.sysuser=The name of the sysdba user. For example, SYS.
- server.base_url=The URL of the WebLogic server sync rest service received from Cloud support. Obtain this information when you contact Oracle Support. For more details, see Prerequisites to Sync Unifier Cloud and On-Premises Data. For example, http://<hostname>:<port#>/sync/rest-service.
- server.connectuser= The user name who has permissions to create sync configurations. For example, weblogic or admin. Obtain this information when you contact Oracle Support.
- Save client_receive.properties.
- Run syncsetup.cmd or syncsetup.sh to create and configure the database schema for the sync process:
$ ./syncsetup.sh client_receive.properties
- Enter passwords for the following users:
- syncuser (target.db.syncuser)
- The sysdba user on that same Oracle instance (target.db.sysuser)
- The admin user for the Unifier target database schema (target.db.schema)
- The web user who will insert the configuration into the sync configuration (server.connectuser)
The process creates the t_syncuser database schema (target.db.syncuser).
- After the process completes, enter the password of syncadmin user. This is the user credential for local Jetty server. Subsequent processes will use this credential to communicate with the server.
- Enter passwords for the following users:
- Start the sync client server.
$ . /startserver.sh
Note: Server startup will take up to a minute. If you load the configuration without starting the server, you will get an error.
- Load the sync and receive the configuration into the sync client server.
$./commander.sh LOAD client_receive.properties
- Re-enter the passwords for Unifier database user (source.db.schema) and server connection user (server.connectuser).
The sync client should now start syncing with the sync microservice.
- To check if the sync process is running, use any of the following options:
- See server.log in the sync-client/log folder or
- Connect as T_SYNCUSER, and check the sync progress from the database.
- To see details of the file posted successfully to the database, run:
select * from sync_config;
- To get an update of the global tables being synced and the status of the sync process for each specific table, run:
select * from sync_control;
The entry_value column status changes from New to Complete. No records are present in this table as the target schema details are on the client side.
- To display all the projects registered to be synced, run:
select * from sync_whitelist;
Synced projects will have a Status of Sent and projects waiting to be synced will have a Status of New. No records are present in this table as the target schema details are on the client side.
- To view the blob records corresponding to the source schema, run:
select * from sync_transfer_data;
The status of the record changes from Receiving, Received, Applying, and finally to Applied. After the record status is Applied, check the corresponding data in target schema.
- To see details of the file posted successfully to the database, run: