Configuring Other Connectors

Multiple connectors are available by default in the Asset Quality Intelligence application: claim, asset, customer, maintenance_event, signature, and users.

In a standalone mode without ENOVIA connectivity, each connector allows you to scan a specific data model object. These connectors are provided to give a quick demo of the Asset Quality Intelligence application. All these connectors should be removed before the production phase.

Important: The signature connector is the only mandatory connector in both contexts (i.e. ENOVIA and standalone).

An ENOVIA connector (named qum) based on the QUM data model is also available in the Asset Quality Intelligence application.

This task shows you how to:

Configure the Signature connector

The signature connector is packaged with the Asset Quality Intelligence application and is almost completely configured.

  1. Connect to Exalead CloudView Administration Console (http://<HOSTNAME>:<BASEPORT+1>/admin).
  2. Click the signature connector link under Connectors.
    The signature connector Configuration tab opens.
  3. In Filesystem paths, specify the path to the folder that contains the signature sources.
  4. Click Apply.
  5. Scan your signature connector.

You can now connect to http://<HOST>:<BASEPORT>/field-issue/page/index and test that signatures have correctly been indexed. [add typical sample]

Configure the QUM connector

  1. Connect to Exalead CloudView Administration Console (http://<HOSTNAME>:<BASEPORT+1>/admin).
  2. Check that a connector named qum already exists under Connectors.
  3. Click More actions next to the qum connector.
    The qum connector More actions window opens.
  4. Configure the Bind CloudView with Enovia DMP action which forces the connection through a local Matrix context:

    Note: The URL option is then only used to build document public URL links at search time.

    1. In Matrix home, enter the path to your Studio Modelling Platform installation.
    2. In Matrix version, specify the installation version.
    3. In DSLS config, specify the ENOVIA V6 license file full location, it it is located in a custom path.
    4. Click Run.
    The ENOVIA Studio Modelling Platform rich client JAR files are copied from the <OS>/docs/javaserver/ directory to the Cloudview/<DATADIR>/javabin folder of the Asset Quality Intelligence application.

    In the <DATADIR>/config/DeploymentInternal.xml file, the gateway section is completed as follows automatically: 

    <envOverride>
 <KeyValue xmlns="exa:exa.bee" key="MATRIXHOME" value="[path]"> </KeyValue>
 <KeyValue xmlns="exa:exa.bee" key="TNS_ADMIN" value="[path]"> </KeyValue>
 <KeyValue xmlns="exa:exa.bee" key="DSLS_CONFIG" value="[path]"> </KeyValue>
</envOverride>
<envAppend> </envAppend>
<envPrepend>
 <KeyValue xmlns="exa:exa.bee" key="PATH" value="[path]"> </KeyValue>
</envPrepend>
  5. There are now two possibilities:
    • If the connector is crawling ENOVIA from a Web App URL, there is nothing to do. The connectors-server process hosting the connector is automatically restarted and you are ready to test the ENOVIA connection.
    • If you left the Web App URL empty, you must restart the product.
  6. Set up the environment variables [CHECK with Nicolas]
  7. Click Apply.
  8. Scan your QUM connector.

You can now connect to http://<HOST>:<BASEPORT>/field-issue/page/index and test that QUM data has correctly been indexed. [add typical sample].