Setting up the ENOVIA VPM V5 Connector

This section details the setup for the NETVIBES OnePart Connector for ENOVIA VPM V5. It requires the connector zip file, vpm5-onepart-connector.zip.

Note: This also requires the ENOVIA VPM V5 Connector deployment - see 3DEXPERIENCE User Assistance: Installing and Deploying the ENOVIA VPM V5 Connector

This task shows you how to:

Deploy the ENOVIA VPM V5 connector

A license is required for all this connector. You can deploy the connector for OnePart as follows.

Configure the ENOVIA VPM V5 Connector

After restart, you must create an instance of the new ENOVIA V5 Connector and configure as follows in the Administration Console.

  1. Go to Connectors and click Add connector.
  2. Create a connector with the name ENOVIAV5:
    1. Select Creation mode: new
    2. Select Type: ENOVIA V5 for OnePart
    3. Click Accept.
  3. In Connectivity, set the following:
    1. Server URL: the ENOVIA V5 webservice API URL; it must be a URL starting with http(s)://<HOST>:<PORT>
    2. Login: the ENOVIA V5 user login (for example, AdminUser)
    3. Password: the password for this user
    4. Role: the ENOVIA V5 role used to index
    5. Webapp root: the ENOVIA V5 webservice API root path; by default /LPMServerMgt, but this URI is configurable when installing webservices
  4. In Connectivity > Advanced, set the following:
    1. Connection timeout : an integer > 0; the default is 2 minutes
    2. Connection timeout time unit : Seconds / Minutes; these 2 connection values will tell the webservices client the timeout for a query.
    3. Meta data connection pool size : the maximum number of simultaneous connections on webservices API for meta datas; 3 is recommended
    4. Vault connection pool size : the maximum number of simultaneous connections on webservices API for vault download; 5 is recommended. Note that changing this value will increase concurrent downloads on vault.
    5. Push API thread count : how many threads are writing on the PushAPI. Useful for OnePart to enable concurrent convert on XCV; 4 is recommended
    6. Push API list document count : the number of documents simultaneously pushed in a batch to PushAPI. For OnePart 1 is recommended due to the XCV conversion process.
  5. For each indexing purpose the queries are preconfigured. In Queries, only the following parameters can be set :
    1. Choose not to index files or only some file extensions
    2. Indexing custom attributes
  6. In Advanced, you can set the following:
    • Verbose : setting this option to true will enable a specific log level called verbose. The connector will write more logs. Useful for debugging
    • Query output dir : the directory into which queries will be verbosed. Only if verbose is checked. If empty no queries will be verbosed
    • Date log formatting : the connector logs dates in seconds because it is the date format in ENOVIA V5. Dates are also written in human readable mode using this date format
  7. Validate the connectivity between the Connector and your source by clicking on Check connectivity; a green message displays if everything is fine.
  8. Click Save at the top of the screen.

Targeting the Consolidation server

Target the consolidation server in the ENOVIA VPM V5 connector configuration as follows.

Note: The OnePartPAPIFilters connector contains PAPI Filters that are required for any connector deployed in OnePart.

  1. In Deployment > Push to PAPI server, select consolidation server cs_onepart
  2. In Configuration > PushAPI filters, click Add item to configure:
    1. PushAPI filter type: Push API Filters Runner
    2. Push API filters config key: PushApiFilters (default)
    3. Use Push API filter from connector: OnePartPAPIFilters
    4. Enable this PushAPI filter: yes
  3. Click Apply to save and deploy your connector configuration.

Keeping CGR for Consolidation

Prevent OPPartsCleaner PAPI filter from cleaning cgr in the Exalead CloudView Administration Console as follows.

  1. Click the OnePartPAPIFilters from the Connectors list.
  2. Expand PushAPI filters.
  3. Go to item OPPartsCleaner.
  4. Expand Kept part names.
  5. Add item with value cgr.
  6. Click Apply to save and deploy the connector configuration.



Configuring the ENOVIA VPM V5 security source

Security source is not available in the current version.