Configuring the Connector in Local Context Mode

In Local Context mode, the ENOVIA ER Connector requires a local installation of Studio Modeling Native Apps (DMP) or LiveCollaborationServer.

Important: This mode is supported to simplify the legacy ENOVIA SBA Connector migration. In that case, the connectivity only requires to provide login / password, as we used to do with the ENOVIA SBA Connector.

This task shows you how to:

Before you begin: To successfully deploy the ENOVIA connector locally:
  • Install Exalead CloudView V6R2016x or higher.
  • Install ENOVIAStudio Modeling Platform native apps on the same host as the Exalead CloudView platform. Depending on your Studio Modeling Platform version, you may need to switch to 32-bit. You must be able to execute the following MQL command and create a context without any error: 
    ./mql -c "push context user USER [password PASSWORD]
See Also
Connectivity Modes
Appendix - Configuration Parameters
Importing a Legacy XML Configuration
  1. Open the Administration Console.
  2. Go to Connectors and click Add connector:
    1. Enter a descriptive name for the connector.
    2. From Type, select the ENOVIA ER connector.
    3. Click Accept.
    The connector Configuration tab opens.
  3. Expand Connection parameters and for:
    1. Component class name, select On premise.
    2. Connectivity mode, select Local Context.
    3. URL, leave the field empty.
    4. Login, enter the same admin login that you set up for the ENOVIA SBA Connector.
    5. Password, enter the same admin password that you set up for the ENOVIA SBA Connector.
    6. Vault, enter the name of the vault you need to index.
  4. Click Check connectivity to run the connector’s connectivity test.
    If the connection is successful, a green "OK" message displays. Otherwise, a message in red indicates what is wrong.
  5. Click Save and Apply.

Bind Exalead CloudView with ENOVIA DMP Automatically

The Bind CloudView to ENOVIA DMP action forces the connection through a local Matrix context. The URL option is then only used to build document public URL links at search time.

  1. Go to the ENOVIA ER Connector Operation tabConnectors and click More actions.
  2. In the Bind CloudView with ENOVIA DMP section:
    1. For Matrix home, enter the path to your Studio Modeling Platform installation.
    2. For Matrix version, specify the installation version.
    3. (Optional) For DSLS config, specify the ENOVIA license file full location, if it is located in a custom path.
    4. Click Run.
    • The ENOVIA Studio Modeling Native Apps JAR files are copied from the <OS>/docs/javaserver/ directory to the CloudView/<DATADIR>/javabin folder.
    • 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>
  3. 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 automatically restarted and you are ready to test the ENOVIA connection.
    • If you left the Web App URL empty, you must restart the product.

You can now set up the environment variables.

Set up the Environment Variables

  1. Open the Exalead CloudViewAPI Console at http://<HOSTNAME>:<BASEPORT+1>/api-ui
  2. Click Manage > Configuration > setCloudviewDeploymentInternalConfig to add environment variables in the DeploymentInternal.xml for name="connectors.*" and name="gateway".

    For example: 

    <envOverride>
  <KeyValue xmlns="exa:exa.bee" key="MATRIXHOME" value="/data/ev6apps/V6R2011x/studio" />
  <KeyValue xmlns="exa:exa.bee" key="GALAXYHOME" value="/data/ev6apps/V6R2011x/studio/linux_a64/code/bin" />
  <KeyValue xmlns="exa:exa.bee" key="TNS_ADMIN" value="/data/ev6apps/common/" />
  <KeyValue xmlns="exa:exa.bee" key="DSLS_CONFIG" value="/data/ev6apps/common/DSLicSrv.txt" />
</envOverride>
<envAppend>
</envAppend>
<envPrepend>
  <KeyValue xmlns="exa:exa.bee" key="LD_LIBRARY_PATH"
	value="/data/ev6apps/V6R2011x/studio/linux_a64/code/bin:/data/ev6apps/V6R2011x/studio/linux_a64/code/lib:" />
</envPrepend>

    See also the code samples in Set up the Environment Variables.

  3. Click Save and then Apply.
  4. Restart Exalead CloudView.

You are now ready to:

  • Add an ENOVIA connector in the Administration Console. Make sure that the URL configuration parameter is empty.
  • Import your ENOVIA SBA connector legacy XML configuration.

Environment Variables

Define the following environment variables on the Java connector server hosting the ENOVIA connector.

Use the following table to determine the environment variables to add to the <DATADIR>/config/DeploymentInternal.xml file.

Environment variable Context Action Description
MATRIXHOME override Path to ENOVIA Studio
GALAXYHOME Linux with ENOVIA versions before V6R2011x only override Path to the ENOVIA Studio /galaxy/linux folder
DB2INSTANCE IBM DB2 only override DB2 instance name
TNS_ADMIN Oracle only override Override the path to the folder containing the tnsnames.ora file.

This variable is not required if you are not referencing tnsnames.ora entries in your MATRIX-R file.

LD_LIBRARY_PATH Linux only prepend

Add the following paths to the variable:

  • <path_to_studio>\<OS>\code\bin
  • <path_to_studio>\<OS>\code\lib

You may also need to add the path to the SQL client for your database.

PATH Windows only prepend Add the following paths to the variable:
  • <path_to_studio>\win_b64\code\bin
  • <path_to_studio>\win_b64\code\lib

You may also need to add the path to the SQL client for your database. For example, for DB2: C:\DATA\DB2\IBM\SQLLIB\BIN

DSLS_CONFIG override

In case the DSLicSrv.txt license file is not installed in the default location, specify the absolute path to the folder containing the file, including the file_name.

Default locations are:

  • Windows: C:\ProgramData\DassaultSystemes\Licenses\DSLicSrv.txt
  • Linux: /var/DassaultSystemes/Licenses/DSLicSrv.txt

The following samples are for an ENOVIA environment:
  • Linux 64-bit
  • Bound to an ENOVIA installation
  • Custom license server config file location

Where name="connectors.*" matches all java connectors 

<ProcessInternalConfig xmlns="exa:exa.bee.deploy.v10"
name="connectors.*" runtime="java" httpMinThreads="5"
httpMaxThreads="500" httpMaxStopTime="100" httpMaxGETQuerySize="32768"
httpMaxFormPOSTQuerySize="10000000" httpMaxIdleTimeMS="86400000"
httpAcceptorThreads="1" httpAcceptQueueSize="1200">
  <params>
  </params>
  <args>
    <StringValue xmlns="exa:exa.bee" value="-Dfile.encoding=UTF-8" />
    <StringValue xmlns="exa:exa.bee" value="-XX:+UseConcMarkSweepGC" />
    <StringValue xmlns="exa:exa.bee" value="-Xmx2048m" />
    <StringValue xmlns="exa:exa.bee" value="-Xms48m" />
    <StringValue xmlns="exa:exa.bee" value="-XX:MaxPermSize=128m" />
    <StringValue xmlns="exa:exa.bee" value="-XX:PermSize=48m" />
    <StringValue xmlns="exa:exa.bee" value="-Djava.awt.headless=true" />
    <StringValue xmlns="exa:exa.bee" value="-Dmmap_thrshold=262144" />
    <StringValue xmlns="exa:exa.bee" value="-Xmx512m" />	  
  </args>
  <envOverride>
    <KeyValue xmlns="exa:exa.bee" key="MATRIXHOME" value="/data/ev6apps/V6R2011x/studio" />
    <KeyValue xmlns="exa:exa.bee" key="GALAXYHOME" value="/data/ev6apps/V6R2011x/studio/linux_a64/code/bin" />
    <KeyValue xmlns="exa:exa.bee" key="TNS_ADMIN" value="/data/ev6apps/common/" />
    <KeyValue xmlns="exa:exa.bee" key="DSLS_CONFIG" value="/data/ev6apps/common/DSLicSrv.txt" />
  </envOverride>
  <envAppend>
  </envAppend>
  <envPrepend>
    <KeyValue xmlns="exa:exa.bee" key="LD_LIBRARY_PATH"
	value="/data/ev6apps/V6R2011x/studio/linux_a64/code/bin:/data/ev6apps/V6R2011x/studio/linux_a64/code/lib:" />
  </envPrepend>
</ProcessInternalConfig>
...

Where name="gateway" for the security source 

<ProcessInternalConfig xmlns="exa:exa.bee.deploy.v10"
 name="gateway" runtime="java" httpMinThreads="5"
 httpMaxThreads="500" httpMaxStopTime="100" httpMaxGETQuerySize="32768"
 httpMaxFormPOSTQuerySize="10000000" httpMaxIdleTimeMS="86400000"
 httpAcceptorThreads="1" httpAcceptQueueSize="1200">
  <params>
  </params>
  <args>
    <StringValue xmlns="exa:exa.bee" value="-Dfile.encoding=UTF-8" />
	<StringValue xmlns="exa:exa.bee" value="-XX:+UseConcMarkSweepGC" />
	<StringValue xmlns="exa:exa.bee" value="-Xmx2048m" />
	<StringValue xmlns="exa:exa.bee" value="-Xms48m" />
	<StringValue xmlns="exa:exa.bee" value="-XX:MaxPermSize=128m" />
	<StringValue xmlns="exa:exa.bee" value="-XX:PermSize=48m" />
	<StringValue xmlns="exa:exa.bee" value="-Djava.awt.headless=true" />
	<StringValue xmlns="exa:exa.bee" value="-Dmmap_thrshold=262144" />
	<StringValue xmlns="exa:exa.bee" value="-Xmx512m" />	
  </args>
  <envOverride>
    <KeyValue xmlns="exa:exa.bee" key="MATRIXHOME" value="/data/ev6apps/V6R2011x/studio" />
    <KeyValue xmlns="exa:exa.bee" key="GALAXYHOME"
	value="/data/ev6apps/V6R2011x/studio/linux_a64/code/bin" />
    <KeyValue xmlns="exa:exa.bee" key="TNS_ADMIN" value="/data/ev6apps/common/" />
    <KeyValue xmlns="exa:exa.bee" key="DSLS_CONFIG"
	value="/data/ev6apps/common/DSLicSrv.txt" />
  </envOverride>
  <envAppend>
  </envAppend>
  <envPrepend>
    <KeyValue xmlns="exa:exa.bee" key="LD_LIBRARY_PATH"
value="/data/ev6apps/V6R2011x/studio/linux_a64/code/bin:/data/ev6apps/V6R2011x/studio/linux_a64/code/lib:" />
  </envPrepend>
</ProcessInternalConfig>
...
Important: This sample ENOVIA configuration must appear before the standard java process configuration in the DeploymentInternal.xml file. This is because the first "internal process configuration" that matches the process is used.