Parameter | Description |
|---|---|
Component class name | Configure query using: • UI - that is to say through the Exalead CloudView Administration Console, by listing Business objects and Relationships below this property. This configuration type applies to the 3DSpace connectivity mode only. It is based on 3DSpace NLS files. ◦ Translate into: Translates workflow fields (for example, STATE). ◦ Translate all selects: Translates all fields. ◦ Names conform with data-model: Adapts the meta name to conform with the name rules of a data model. Names must conform with the regular expression [A-Za-z0-9_]+ • file - through a configuration file (same configuration mode than the legacy ENOVIA SBA connector). ◦ Query configuration file path: Specify the file path of the configuration file. It must be on the same server than your ENOVIA instance. The xml nodes correspond to the UI options that found in this table. See the Configuration File Example below. |
Business objects | |
Enovia type name | Name of the Business Object type. |
Make a query by subtype | Useful when data is very split. For example, when a Designer Central contains all CAD types and several subtypes, we can make a query for each subtype. This option gives you multithreading capabilities. Important: Leave empty if you have more than one object type to index. |
Where clause | Filters objects. For example, owner == <login> |
Index basics | Indexes all ENOVIA basics attributes. For example, all IDs. Recommendation: Avoid using this option as it has an impact on performance. It is better to specify Selectables in the configuration (see below). |
Index all attributes | Indexes all ENOVIA attributes. Recommendation: Avoid using this option as it has an impact on performance. It is better to specify Selectables in the configuration (see below). |
Index files | Indicates whether to index files for this Business object type. |
Trace tenant | If your server vault has multiple tenants, it traces the source tenant by storing this info in a specific tenant meta. |
Trace history | Indicates whether to trace history events as documents linked to the Business Object. |
Trace type lineage | Creates a taxonomy of Business object types. It stores the hierarchy of the object using a | (pipe) separator. For example, MCAD Model|3DPart|CATIA Part |
Preserve empty values | Shows attribute names in search results, even when these attributes have null or empty values. Without this option, when an attribute is not valuated, Exalead CloudView cannot retrieve it and cannot produce a document with a meta containing the attribute. |
CV type names | The first element in this item list must be the Data Model class and the hierarchy type root node of the Consolidation Server. |
Include policies | Includes the specified Business object policies only. |
Exclude policies | Excludes the specified Business object policies only. |
Selectables | Use selectables to use basic or other ENOVIA attributes without attribute [<ATTRIBUTE_NAME>] curly braces inclusion. You can use the target meta name to copy basics or attributes into one or several metas. |
Programs | For legacy mode we need to support JPO, TCL or MQL. The connector sends the code to the ENOVIA kernel directly. From V6R2017x, it also supports JPO servers. |
File filter | This node allows you to specify formats, extensions, etc. to accept or exclude during indexing. For example, you may want to index PDF and exclude XML files when indexing the content of a repository. The Trace reason option allows you to log why Exalead CloudView did not index files (for debug purpose). |
Relationships | The properties and options are the same that the Business Object ones. |