Setting Up the X-CAD Design Coexistence and Migration Connector

This task shows you how to set up the X-CAD Design Coexistence and Migration Connector.

This task shows you how to:

Connector Architecture

This section explains about the Connector Architecture. There are server components and client components that comprise the connector. Beginning with version V6R2010, the server components are packaged with the standard ENOVIA Business Process Services. There are some post installation steps required to support the client. There are also some customizations that can be performed.

The installation of the client requires two steps:

  1. In the first step, an administrator installs the various components of the client and applies a number of configurations to arrive at an end-user installable file.
  2. The second step simply involves running the end-user installable file on each end-user computer.

Adding Licenses to Client Machines

This task shows you how to add licenses to client machines.

  1. Unzip lum.zip to Documents and Settings\All Users\Application Data\IBM\License Use Management. Run the tool LUMtarget.exe to obtain the MAC address of your machine. Then send this information in the license request email.
  2. After receiving a license, place the license file into the Documents and Settings\All Users\Application Data\IBM\License Use Management\nodelock directory.

Version Compatibility

X-CAD Design Coexistence and Migration supports cross releases as indicated in Version Compatibility.

Required Software

You must first have an X-CAD Design server installed and configured for use as an X-CAD Design connector server. The following is a list of the required software.

You must have the 3DEXPERIENCE Platform and either Engineering BOM Management or X-CAD Design Management installed. To make use of the connector for getting ENOVIA data, you must also have at least one of the following installed:

  • Connector for CATIA V5
  • Connector for Creo Parametric
  • Connector for NX.

To use Connector for Creo Parametric or Connector for NX you must make the required changes to system properties. By default, the system settings for Connector for CATIA V5 are correct.

System Properties

This section explains about the system properties.

The emxSystem property file distributed with Business Process Services software is used to customize the X-CAD Design connector server settings.

This file is located under <<web application>>/WEB-INF/classes

Out of the box, this file is configured to provide 3D (i.e. CGR files), 2D (jpg, png files) image viewing support for Engineering BOM Management types Part, Hardware Part, Software Part, as well as for X-CAD Design types CATProduct, CATPart, Versioned CATProduct, Versioned CATPart. There is no need to make any changes to this file to support these types. If any new types need to be added for example: PRO/Engineer® or NX® objects etc., this file will need to be modified. For more information, see Describing the Environment Properties.

Modify the Metadata

There are two predefined environments available without any customizations: ENOVIA X-BOM Engineering and ENOVIA Collaborative MultiCAD Management. Additional environments can be added using the emxSystem.properties file.

Environment Relationship Used for Expand Types Exposed Attributes Table
ENOVIA Engineering BOM ManagementEBOM

Part

Hardware Part

Software Part

3DLive Part
X-CAD Design Coexistence and MigrationCAD SubComponent

CAD Model

CAD Drawing

CAT Part

CAT Product

Versioned CAT Product

Versioned CAT Part

MCAD Model

3DLive Basic

Hash Names

Due to limitations in the client, all metadata is converted to a 32-byte hex-encoded MD5 hash prefixed with an 'a'. This avoids the size limitations on the client and the fact that the client does not support spaces in names. These hash names are generated on the server and passed to the client. The client knows only of the hash names, so when requests are made back to the server, the server converts back to real names before carrying out any operation. These conversions are all done automatically but it is important to point this out since hash names will be exposed in some of the resource files on the client.

The following table lists the basic hash name mappings.

Actual NameHash Name

Engineering BOM Management

a3061342e4b0470be416896b231bba506

Designer Central

ad4050b3777720b70c3784d03f7948c9a

Part

ab1fe2fcf4b815d74d4c4b74a62cde908

Hardware Part

afe7e0aa599314cb2bc053019dda7257e

Software Part

abbc7732b06045730bf9da48cf203326f

CAD Model

a97359c642e2541027b6b6575562bc9ed

CAD Drawing

a61991402bdb580a828aa241d15bc1f9a

Type

aa1fa27779242b4902f7ae3bdd5c6d508

Name

a49ee3087348e8d44e1feda1917443987

Revision

a32c676ac5296556c0573a301ef5ab07b

Originated

abc091088001749fb05b500c23dd3ed2e

Modified

a35e0c8c0b180c95d4e122e55ed62cc64

Current

a46a2a41cc6e552044816a2d04634545d

Owner

ab6f4a2ec6356bbd56d49f2096bf9d3d3

Locker

a4e6ada6f19cc32bd67dbad5b15bd218d