Setting up the ENOVIA V6 Designer Central Connector

This section details the setup for OnePart Connector for ENOVIA V6 Designer Central.

This task shows you how to:

Deploying the ENOVIA V6 Designer Central Connector

Context:

The OnePart connector components are located in a plugin zip file.

ENOVIA Designer Central connector requires the files:

  • enovia-java-connector-plugin-v6.zip

  • Dedicated security source, enovia-java-security-source.zip

  • Configuration file, OnePartEnoviaDesignerCentral.xml

Note: The connector plugins for OnePart are deployed during the OnePart installation with exception of the Agile PLM connector. However, a license is required for all the PDM connectors.

To configure the ENOVIA Local Context

  1. Open the Exalead CloudView API Console:
    1. Go to http://<HOSTNAME>:<BASEPORT+1>/api-ui
    2. Enter the administrator’s Login / Password: admin / exalead (by default)
  2. Click Manage > Configuration > setCloudviewDeploymentInternalConfig to add the environment variables to the DeploymentInternal.xml.
  3. You must update two environment variables: envOverride and envPrepend in the connectors, gateway and searchserver servers in the ProcessInternalConfig sections.

    Note:

    If there is no entry for gateway, you must create one similar to the connector's entry.

  4. Add the lines written in red and replace the values between < > by the values that correspond to your ENOVIA installation for the nvOverride and envPrepend variables. See code example below.
  5. Click Save and then Apply.

Code example

<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="-Xms128m"/>
		<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="-XX:MaxDirectMemorySize=12g"/>
</args>
<envOverride>
		<KeyValue xmlns="exa:exa.bee" key="MATRIXHOME" value="<Enovia Studio Modeling Platform 
V6R2014.GA Install Dir>\studio" />
		<KeyValue xmlns="exa:exa.bee" key="GALAXYHOME" value="<Enovia Studio Modeling Platform 
V6R2014.GA Install Dir>
\studio\win_b64\code\bin" />
		<KeyValue xmlns="exa:exa.bee" key="TNS_ADMIN" value="<Path to dir that contains 
tnsnames.ora file>" />
		<KeyValue xmlns="exa:exa.bee" key="DSLS_CONFIG" value="<Path to DSLicSrv.txt file 
that stores licence servers adresses>" />
</envOverride>
<envAppend>
</envAppend>
<envPrepend>
		<KeyValue xmlns="exa:exa.bee" key="PATH" 
		value="<Enovia Studio Modeling Platform V6R2014.GA Install Dir>\studio\win_b64\code\
bin;
		<Enovia Studio Modeling Platform V6R2014.GA Install Dir>\studio\win_b64\code\lib" />
</envPrepend>
</ProcessInternalConfig>

To deploy the ENOVIA connectivity java libs

You must deploy some required ENOVIA libs to your OnePart installation.

Note: To index R2017x and higher, you must copy a different FcsServer.jar to <ONEPART_INSTALLDIR>\datadir\javabin

This file is located on the ENOVIA server at:

  • linux_a64/docs/javaserver/FcsServer.jar
  • win_b64\docs\javaserever\FcsServer.jar

  1. Open a Windows Explorer and go to the STUDIO_HOME directory at: <Enovia Studio Modeling Platform <VERSION> InstallDir>\studio\win_b64\docs\javaserver
  2. Copy the following jar files from <STUDIO_HOME>\win_b64\docs\javaserver\:
    • consolidation_server_provider.jar

    • consolidation_server_rule_processor.jar

    • eMatrixServletRMI.jar
    • enoviaKernel.jar
    • FcsClient.jar
    • FcsClientLargeFile.jar
    • FcsBackEnd.jar
    • FcsServer.jar
    • m1jsystem.jar
    • mx_jdom_1.0.jar
    • search_common.jar
  3. Paste them into your <ONEPART_INSTALL>\datadir\javabin.
  4. In the Administration Console, click Restart CloudView on this host.

Creating the ENOVIA V6 Designer Central Connector

This section details creating the OnePart Connector for ENOVIA V6 Designer Central.

To create the ENOVIA V6 connector

  1. Log in to the Administration Console with the Login / Password: app-admin / exalead
  2. Go to Connectors page and then click Add connector.
  3. Enter a descriptive name such as EnoviaV6 in Name.

    Note: The connector name cannot be changed after.

  4. Select the ENOVIA V6 in the Type drop-down list.
  5. Click Accept.

To configure the connector

In the connector's configuration page, you need to fill in the fields with the values that correspond to your ENOVIA V6 Designer Central server configuration.

  1. Log in to the Administration Console with the Login / Password: app-admin / exalead
  2. In the Home page, select the ENOVIA connector from the Connectors list.
  3. In the Connectivity section, set:
    1. Web app URL: https://ENOVIA%20server%20host/ematrix
    2. Use local context: select this option; the connection will be made using ENOVIA Studio Modeling Platform
    3. User: your ENOVIA user name
    4. Password: the password for the ENOVIA user
    5. XML configuration file: path to OnePartEnoviaDesignerCentral.xml located at the root of the connector package.
  4. Click Check connectivity.
    This validates the connectivity between the Connector and your source; a green message displays if everything is fine.
  5. In the Indexing section, select:
    1. Index business objects
    2. Index files
    3. Index security
  6. In the PushAPI filters section, click Add item to configure:
    1. PushAPI filter type: UtilsForParts.
    2. Data model class or SDC type: mcad_model
    3. Keep the default settings.
  7. Click Apply at the top of your Administration Console screen.

    This will save and deploy your new connector configuration.

To add a connector targeting the consolidation server

If you did NOT use the OnePart Console to add your sources, then you must manually configure the connector to target the consolidation server as follows.

  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 at the top of your Administration Console screen.

    This will save and deploy your new connector configuration.

Configuring the ENOVIA V6 Designer Central security source

A key thing to remember with OnePart is that you must ALWAYS have a Multi-security source named app_login. This name maintains the link for the security enabled on both Exalead CloudView and the OnePart UI’s.

Context:

If you must use the Exalead CloudView Administration Console then you must:

  • first create the security source manually in the Administration Console and

  • add it as a source to the app_login configuration.

You will use the security source type called ENOVIA V6.

To add the security source

  1. In the Administration Console, go to the Security Sources page.
  2. Click on Add security source and create the new security source as follows:
    • in Name: Enter a name for the security source
    • in Type: Select the security source you require. It generally has the same name as the connector.
  3. Click on Accept.
    You are now ready to configure the new security source.

To configure the security source

You need to configure the security source to view your ENOVIA V6 Designer Central items in OnePart.

  1. In the Security source's configuration page, you need to fill the following fields with your ENOVIA V6 Designer Central server information:
    • ENOVIA username: ENOVIA V6 Designer Central username defined when configuring the connector.
    • ENOVIA password: ENOVIA V6 Designer Central user password defined when configuring the connector.
    • Web application URL: leave blank.
    • Security tokens hook processor: leave blank.
  2. Click Apply at the top of the Administration Console screen.

Next step is to add your security source to the app_login multi-security source configuration. See Configure the multi-security source.