Option 2: Installing Sync Client in the Command Mode

To install sync client using the command mode:

  1. Unzip the sync_client.zip file and enter the resulting sync_client directory.

    $ unzip sync_client.zip -d sync_client

    $ cd sync_client

    or

    Unzip the sync-client.zip file available in the present working directory and enter the resulting sync-client directory.

    $ unzip sync-client.zip

    $ cd sync-client

  2. If on a Unix or Linux system, set the executable flag on the shell scripts.

    $ chmod u+x *.sh

  3. Edit the client_send.properties file in the sync-client directory with the following property values:
    • sync.mode: Enter the value, CLIENT.
    • sync.type: Enter the value, SENDER
    • sync.name: Enter enter the value, ds_pxsync. for PX Sync (P6 + PX data)
    • sync.number: Enter the value, 4. for PX Sync.
    • source.db.host: Enter the host name or IP address of the machine hosting the P6 source database.

      Note: P6 source database refers to an on-premises P6 database.

    • source.db.port: Enter the port number for the Oracle instance on which P6 source database is created. By default 1521.
    • source.db.service: Enter the service name of the Oracle instance on which the P6 source database is created.
    • source.db.type: Based on your sync configuration, select the value, PX, from the drop-down list.
    • source.db.schema: Enter the on-premises P6 Database schema name for PX Sync. For example, admuser.
    • source.db.syncuser: Enter any name starting with T_.

      This will be intermediate schema name and is newly created. Ensure there is no existing schema with same name on the database instance where on-premises source database is hosted.

    • source.db.sysuser: Enter a user name having SYSDBA privileges. For example, SYS or SYSTEM.
    • server.base.url: Enter the URL of the WebLogic server sync rest service you have received from Oracle Support in the format:

      http://<CloudServer Hostname><port>/DataSync/rest-service

    • server.connectuser: To access the cloud sync services, enter the name of the user who has been assigned the Primavera Data Sync Production role in the Primavera Administration Application.
    • optin.project_mode: Select the value, PX to synch any project whose publication status is set to Yes.
    • optin.project_value: Enter the value, Y.
  4. Save the edited client_send.properties file.
  5. Run the syncsetup.sh file to create and configure the database schema for the sync process.

    ./syncsetup.sh client_send.properties

    1. When prompted, enter the 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 source database schema (source.db.schema)
      • The web user who will insert the configuration into the Sync configuration (server.connectuser)

      The process will now create the t_syncuser database schema. (source.db.syncuser)

    2. After the process completes, when prompted, 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 a password of your choice.
  6. Start the sync client's server, but before that add proxy settings in startserver.sh file as given below

    java -jar ../start.jar -Dhttps.proxySet=true -Dhttps.proxyHost=<Proxy HostName> -Dhttps.proxyPort=<Proxy Port> -Dhttp.proxySet=true -Dhttp.proxyHost=<Proxy HostName> -Dhttp.proxyPort=<Proxy Port> -Dapp.name=client-sync > /dev/null &

  7. Contact Oracle Support and obtain the Proxy HostName and Proxy Port details which were used while setting up the server.
  8. Update the startserver.sh file, and start the Jetty server with following command:

    $ ./startserver.sh

  9. When prompted provide the same syncadmin password given above. You might need to wait a few seconds at this point for the local server to start up.

    The server log file is available in log/server.log.

  10. Load the sync and receive configuration into the sync client server with the commander.sh command

    $ ./commander.sh LOAD client_send.properties

  11. Re-enter the passwords for P6 source database admin user (source.db.schema) and server connection user (server.connectuser).

The sync client should now start syncing with the sync microservice.


Last Published Thursday, December 7, 2023