To send P6 EPPM on-premises data using incremental sync after dump restoration:
- Contact Oracle Support with a service request to enable Primavera Analytics Cloud Sync.
Note: To use Primavera Analytics Cloud Sync, you must have a license for Primavera Analytics on-premises or Primavera Data Warehouse on-premises software.
- When the service request is completed, download sync_client.zip from the Cloud portal landing page.
- Extract sync_client.zip and enter the sync_client directory.
$ unzip sync_client.zip
$ cd sync_client.
- Extract sync-client.zip and enter the sync-client directory.
$ unzip sync-client.zip
$ cd sync-client.
- For Unix or Linux systems, update permissions on .sh files using the following command.
$ chmod u+x *.sh
- To send on-premises data, edit client_send.properties in the sync-client directory with the following information:
- sync mode = CLIENT
- sync type = SENDER
- sync.name=<Name of the sync> A unique sync name pre-populated to identify the sync configuration. For example, p6clouddata_receiver.
- sync.number= This number is pre-populated.
- source.db.host= The host name (or IP) of the machine on which the P6 source database is hosted. For example, localhost.
- source.db.port= The port number for the Oracle instance on which P6 source database is created. For example, 1521.
- source.db.service= The service name of the Oracle instance on which P6 source database is created. For example, pdborcl.
- source.db.type=P6. .
- source.db.schema= Database user name of the admin user (admuser) of P6 source database.
- source.db.syncuser= The username of sync-client database schema that will be created on same Oracle instance as the P6 source 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.
- source.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. This URL is pre-populated. For example, http://<hostname>:<port#>/sync/rest-service.
- server.connectuser= The username of a user who has permissions to create sync configurations. For example, weblogic or admin. This user is pre-populated.
- optin.project_mode= The P6 projects to be synced. Values can be PX, CODE, or UDF.
For incremental sync, values can be INCRPX, INCRCODE, or INCRUDF.
- optin.project_value= Enter Y when optin.project_mode is set to PX, or INCRPX.
Respective CODE column name for which the anticipated CODE VALUE is "SEND" should be provided when optin.project_mode = "CODE or INCRCODE".
Respective UDF column name for which the anticipated UDF VALUE is "SEND" should be provided when optin.project_mode = "UDF or INCRUDF".
- Save client_sender.properties.
- Run syncsetup.cmd or syncsetup.sh to create and configure the database schema for the sync process:
$ ./syncsetup.sh client_send.properties
- Enter passwords for the following users:
- syncuser (source.db.syncuser)
- The sysdba user on that same Oracle instance (source.db.sysuser)
- The admin user for the P6 target database schema (source.db.schema)
- The web user who will insert the configuration into the sync configuration (server.connectuser)
The process creates the t_syncuser database schema (source.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_send.properties
- Re-enter the passwords for P6 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, execute 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,execute 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, execute 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, execute 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.