Parameter | Description |
|---|---|
Pushed documents before checkpoint | Minimum number of documents pushed between 2 consecutive checkpoints. It is better to specify a low value when Exalead CloudView documents are sorted (default behavior), and take time to be processed (for example, documents in OnePart). |
Connect to ENOVIA on apply configuration | The connector connects to ENOVIA automatically when you click Apply, to verify that the configuration is correct. For example, to verify that you there are no references to types that do not exist. |
Push API thread count | Number of threads used to push data into the Exalead CloudView Push API Server. It is useful when converting documents using PushAPI filters. |
Push API queue size | Maximum number of intermediary documents stored between the ENOVIA database and the Exalead CloudView Push API Server. When the number of documents reaches this limit, the connector stops reading the ENOVIA database, to stop receiving more documents. |
Verbose | Useful to debug the connector configuration. Logs each event sent to the Exalead CloudView Push API. For internal use by Support teams only. |
Multithreading strategy | Choose how to organize your thread pool. • Query: for on-premises deployment, Business Object and Relationship queries are executed in parallel on a single ENOVIA source. • Tenant: for cloud deployment, it allows you to index multiple ENOVIA sources at the same time. |
Enovia indexing thread count | Number of threads used by Query or Vault Tenant Producers. |
Refresh the data model at each scan | Each time a scan starts, it looks for changes in the data model. This is a costly operation. Use it only when your data model changes regularly. Do not use it if the data model never changes, or very rarely. |
Graph management mode | • Default E/R graph manager - This is the most simple mode as it allows you to simplify the naming of URIs. You can use the Trace tenant option for cloud deployments, to trace the ENOVIA vault and tenant. • ENOVIA SBA graph manager - The connector manages graphs like the legacy SBA connector (Exalead CloudView processes URIs and Consolidation Server object graph the same way). |
File container handler | Specifies how to attach ENOVIA files as binary parts to Exalead CloudView documents. |
Incremental scan options | • Incremental timestamp offset: Specify the number of minutes to add to the last modified date checkpoint. • Force strict ordering: Specify the number of seconds between 2 consecutive scans. If the previous scan happened before this duration, then the connectors make a partial ordering over the modified date, else this is a strict ordering. ◦ Negative value disables the partial ordering ◦ 0 forces the partial ordering ◦ Positive value gives the duration in seconds such as: Tn - Tn-1 this value, the where clause for query indexing is: modified previous checkpoint. Tn - Tn-1 > this value, the where clause for query indexation is: modified > previous checkpoint. |
Delete options | • Delete timestamp offset: Specify the number of minutes to add to the last delete date checkpoint. • Disable Where clause: If you do not select this option, the connector deletes all the documents corresponding to the reverse of the where clause, for each query made to the ENOVIA database. This can be costly. Recommendation: For better performance, select this option to avoid querying the ENOVIA database. |
Send data model in consobox | • Send the data model to consobox: Shows options to send documents describing the ENOVIA data model in the Exalead CloudView Consolidation Server. • Send dimension: Use it to see the dimensions referenced by the pushed attributes. • Arcs to interfaces: Draw arcs between the business objects or connections, and the interface types they reference. The connector requires this configuration to send interfaces to the Consolidation Server. • Arcs to relationships: Draw arcs between the connections and the relationship types they reference. The connector requires this configuration to send relationships to the Consolidation Server. • Arcs to types: Draw arcs between business objects and the types they reference. The connector requires this configuration to send types to the Consolidation Server. • Metadata type to send to the consobox can be of 3 types: Type, Relationship, or Interface. The Send attribute option sends the attributes attached to the Type. Select the User name for URI option to use the type name instead of the type id, to identify the documents stored in Exalead CloudView. |
Error management | Specifies how to handle retry on errors for Business Objects retrieved from the ENOVIA database. It does not handle errors that may occur to the document afterward, for example, a faulty Push API filter or a Consolidation Server error. • Enable error management: Enables retry on error. If disabled: ◦ The connector fails at the first error when retrieving data. ◦ It does launch a retry, even if there is a major error requiring one. • Maximum number of retries: Specifies the maximum number of consecutive fetch retrieval errors a single object can trigger before being ignored. The connector launches each retry only once per scan, provided the query that fetched the object is still present. Possible values: ◦ A negative value means that there is no upper limit. ◦ 0 means that no retry is launched. The connector discards and logs every error. ◦ A positive value (above 0) specifies the number of retries. Note: If the scan of a Business Object fails as many times as the maximum number of retries, but matches the WHERE clause in the following scan, the cycle starts once again. • Maximum number of errors: Specifies the maximum number of errors tolerated for a single scan. Once this number is reached, the connector generates an error. Possible values: ◦ A negative value means that there is no limit in the number of errors. ◦ 0 means that the first error stops the entire scan. ◦ A positive value (above 0) specifies the number of tolerated errors for a given scan. This value may sometimes be crossed as the query can be executed in parallel. |