SAINT Exporter

Išči
Experience Manager 6.3 Sites Uporabniški vodnik za skrbništvo

Na tej strani

Velja za: Experience Manager 6.3 Sites

某些 Creative Cloud 应用程序、服务和功能在中国不可用。

Ogledujete si pomoč za različico :

The SAINT Exporter exports classifications data to SiteCatalyst in a scheduled manner. The exporter is an implementation of a com.adobe.cq.scheduled.exporter.Exporter.

To configure this:

  1. Navigate to Tools > Cloudservices and add a new configuration and the SAINT Configuration template displays below a SiteCatalyst configuration.

    chlimage_1

  2. Click Create to configure the SAINT settings.

    chlimage_1
    Field Description
    Enabled Select Yes to enable SAINT settings.
    Overwrite on conflict Select Yes to overwrite any data collisions. By default, this is set to No.
    Delete processed If set to Yes, deletes processed nodes after they are exported. The default is False.
    Export job description Enter a description for the SAINT job.
    Notification E-mail Enter an email address for SAINT notification.
    Report Suite Enter the Report suite to run the import job for.
    Data Set Enter the dataset relation ID to run the import job for.
    Transformer From the drop-down menu, select a transformer implementation.
    Data Source Navigate to the path for the data container.
    Export Schedule Select the schedule for the export. The default is every 30 minutes.

    Properties include the following:

  3. Click OK to save your settings.

Modifying Page Size

Records are processed in pages. By default, the Exporter is creating pages with a page size of 1000.

A page may be 25000 in size at maximum, per definition in SAINT and can be modified from the Felix console. During the export, the Exporter is locking the source node to prevent concurrent modifications. The node is unlocked after export, on error, or when the session is closed.

To change the page size:

  1. Navigate to the OSGI console at http://<host>:<port>/system/console/configMgr and select Day CQ Analytics SAINT Exporter.

    chlimage_1

  2. Enter a page size and click Save.

SAINTDefaultTransformer

An Exporter may use a Transformer to transform the export data to a specific format. For SAINT, a subinterface SAINTTransformer<String[]> implementing the Transformer interface has been provided. This interface is used to restrict the data type to String[] which is used by the SAINT API and to have a marker interface to find such services for selection.

In the default implementation SAINTDefaultTransformer, the child resources of the exporter source are treated as records with property names as keys and property values as values. The Key column is added automatically as first column - its value will be the node name. Namespaced properties (containing :) are disregarded.

Node structure:

  • id-classification [nt:unstructured]
    • 1 [nt:unstructured]
      • Product = My Product Name (String)
      • Price = 120.90 (String)
      • Size = M (String)
      • Color = black (String)
      • Color^Code = 101 (String)

SAINT Header & Record:

Key Product Price Size Color Color^Code
1 My Product Name 120.90 M black 101

Properties include the following:

Property path Description
transformer A class name of a SAINTTransformer implementation
email SAINT notification e-mail address.
reportsuites Report suite IDs to run the import job for. 
dataset Dataset relation ID to run the import job for. 
description SAINT job description. Default is CQ SAINT Export. 
overwrite Flag to overwrite data collisions. Default is false.
checkdivisions Flag to check report suites for compatibility. Default is true.
deleteprocessed Flag to delete the processed nodes after export. Default is false.

Automating SAINT export

You can use the sample SAINT Product Export Handler workflow so that any new imports launch the workflow, creating the appropriate data in /var/export/ so that it can be exported to SAINT.

  1. Navigate to http://<host>:<port>/cf#/etc/workflow/models/saint-product-export-handler.html.

    chlimage_1

  2. Make any configuration changes, as necessary, and click Save.

  3. In the main workflow page at http://<host>:<port>/libs/cq/workflow/content/console.html, select the workflow and click Start to start the workflow.