Parameter | Description |
|---|---|
Component class name | Select On premise. |
Connectivity mode | Select the connectivity mode to connect to ENOVIA. • Local Context - Use this mode to connect to ENOVIA using the DMP studio agent through OCI. This RMI In-Process (RIP) mode uses the Live Collaboration Server implementation classes. However, instead of going through a registry and invoking a separate process, the client's address space loads the server classes directly. Database communication is directly between the ENOVIA client and the database. This is more efficient in situations that involve processing an extremely large number of transactions. This mode reduces the load on the HTTP ENOVIA server. • REST - In this mode, you can crawl data from the ENOVIA Tomcat server in HTTP Rest mode. It allows you to connect remotely on a CAS-secured instance. • 3DSpace - New mode to connect to ENOVIA through the 3DSpace. • Legacy XML Servlet - Do not use this mode. |
URL | Specify the base URL of the 3DSpace, or leave empty if you use Local Context. |
Login | 3DSpace | XML Servlet | Local Context user login for indexing documents. Read-access required. |
Password | 3DSpace | XML Servlet | Local Context password for the ENOVIA user. |
Role | Role that can access ENOVIA. |
Vault | Optionally, you can specify the name of the ENOVIA vault you want to index. If you do not specify any vault, the connector scans all vaults. Important: It is possible to use different connectivity modes on several vaults in parallel. |
Event monitor name | Optional. Specifies the Event monitor name, if you want to create an Event monitor to manage incremental indexing. By default, the connector uses an incremental scan based on dates. Important: Defining the Even monitor name is one of the steps in the Event monitor configuration. To get the complete procedure, see Adding an Event Monitor for Incremental Indexing. |
Has write access | Allows the connector to modify the content of the database. It is typically useful for the following use cases: • If you use an Event Monitor, the connector can purge consumed events out of the database. If the write access is not enabled, events remain in the database and you must purge them manually. • If the FCS is remote, the connector needs to update file synchronization information. |
Tenant | This is for Cloud deployments. For Exalead experts only. |