# Administrator Guide

# Synchronizing Analytics

This chapter includes the following topics:

- Overview of Analytics Synchronization
- Strategizing Synchronization Scheduling

## Overview of Analytics Synchronization

Analytics synchronization is a process by which object dimension data is sent from the remote database to the dimension tables of the Analytics database, where the data is stored. Dimension data is transferred through a JDBC connection.

If you are using Streaming Portal Mode, use the command line to run Analytics sync jobs. To schedule jobs, create scheduled tasks (Windows) or cron jobs (UNIX/Linux). An Analytics sync job exists for each type of portal object. For the commands you use to run sync jobs, see Analytics Sync Jobs. For synchronization scheduling guidelines, see Strategizing Synchronization Scheduling.

You can find details of sync jobs in the portal's job history log or in Analytics's sync.log file. For the location of the Analytics sync.log file, see Overview of Logs.

#### Analytics Sync Jobs

Analytics is delivered with sync jobs that synchronize your portal's objects with the Analytics database. You can either run all three of the sync jobs at the same time using one command, or run each sync job separately. Separate sync jobs exist for synchronizing desktop, page, and portlet objects with Analytics.

##### Analytics Sync Jobs (Windows)

To synchronize desktop, page, and portlet objects at the same time, type the following command in the Windows Command Prompt:

- C:\bea\alui\ptanalytics\2.1\bin\AnalyticsRunJobs.bat

Following are the commands you use to run each sync job separately:

- C:\bea\alui\ptanalytics\2.1\bin\AnalyticsRunJobs.bat RUN_COMMUNITY_SYNC
- C:\bea\alui\ptanalytics\2.1\bin\AnalyticsRunJobs.bat RUN_COMMUNITY_PAGE_SYNC
- C:\bea\alui\ptanalytics\2.1\bin\AnalyticsRunJobs.bat RUN_PORTLET_SYNC

To schedule a sync job, create a scheduled task and use one of the above commands appropriate to the sync job you are scheduling.

##### Analytics Sync Jobs (UNIX/Linux)

To synchronize desktop, page, and portlet objects at the same time, type the following command in the command line:

- /opt/bea/alui/ptanalytics/2.1/bin/AnalyticsRunJobs.sh

Following are the commands you use to run each sync job separately:

- /opt/bea/alui/ptanalytics/2.1/bin/AnalyticsRunJobs.sh RUN_COMMUNITY_SYNC
- /opt/bea/alui/ptanalytics/2.1/bin/AnalyticsRunJobs.sh RUN_COMMUNITY_PAGE_SYNC
- /opt/bea/alui/ptanalytics/2.1/bin/AnalyticsRunJobs.sh RUN_PORTLET_SYNC

To schedule a sync job, create a cron job and use one of the above commands appropriate to the sync job you are scheduling.

## Strategizing Synchronization Scheduling

Because some dimension data in you environment might change more frequently than other dimension data, we recommend that you adopt a job scheduling strategy that reflects your environment's unique circumstances.

Following are some examples of scheduling strategies that you can adopt:

- If your portal contains objects that rarely change, run the appropriate Analytics sync job manually. For example, if your portal's desktop objects rarely change, run the desktop sync job manually.
- If your portal contains objects that change only once per week, schedule the appropriate Analytics sync job to run once per week. For example, if new portlets are added to your production portal once per week, schedule the portlet sync job to run once per week.
- If your portal contains data that changes on a constant basis, schedule the appropriate Analytics sync job to run frequently. For example, if new pages are added to your production portal throughout the day, schedule the pages sync job to run once per hour.