About the Resource Generator

The Resource Generator can be launched in two ways:

A default out-of-the-box customization of the 3DEXPERIENCE data model is delivered with the legacy source to support access to non-customized data. To enable ENOVIA VPM V5 users to customize data, the Resource Generator creates metadata files, XML mapping files, and client resources. The mapping of V5 objects with 3DEXPERIENCE is done in two steps:

  1. The VPM V5 metadata objects are mapped with the VP5 intermediate data model in 3DEXPERIENCE. If the VPM V5 data model is to be customized, an additional operation is required using the Resource Generator:
  2. VP5 intermediate data is mapped with 3DEXPERIENCE metadata objects. This is done through Business Logics that is also used to modify and manage types and attributes.

This page discusses:

Resource Generator Input

The Resource Generator requires the following input in the form of XML files:

InputDescription
PathPath specifying the location of legacy source metadata files
Metadata file nameName of the customized V5 metadata file that generates the 3DEXPERIENCE metadata and mapping files
Custom suffixSmall suffix (two or three characters) to be used when generating files

Resource Generator Output

The Resource Generator generates the following output files:

OutputDescription
Visibility fileVisibility relates to the object types and attributes that you can access in the CoexistenceBatch search window. The metadata definition of the types and attributes determines the set of object types and attributes available to you.

Visibility also depends on your VPM V5 access rights determined by the login credentials used. The actual attribute values are derived by mapping VPM V5 data with the attributes specified in the metadata. The actual set of visible attributes is the intersection of attributes defined in the mapping with those enabled by the People and Organization (P&O) login context. The property (CATRsc) file specifies the available object types.

Display Names FileDisplay names are the labels associated with the object types and attributes in the CoexistenceBatch search window. Display names are available in CATNls files. The available values depend on the language you use to log in and the VPM V5 server you are connected to. The values also depend on the login credentials.
2D / 3D iconsAdministrators can customize the Icons_xx CATRsc files to specify certain icons for VPM V5 types.
Toolbar (PQ_) files The PQ_...CATRsc file defines the types available in the toolbar search and attributes used in the search. PQ_...CATNls defines the labels seen in the toolbar search.
Transition engine profile XMLsTransition engine profile XMLs contain information specific to V5->3DEXPERIENCE and 3DEXPERIENCE>V5 transfers.
Metadata filesMetadata files define the object types and attributes in V5 and 3DEXPERIENCE. Formats for V5 and 3DEXPERIENCE metadata files are different. The metadata files must be copied to the appropriate V5 server in the location $installpath\win_b64\resources\3dlive\[appropriate release folder, R419 for example]"
Admin filesThe admin file defines the environments. The Admin files must be copied to the appropriate V5 server in the location $installpath\win_b64\resources\3dlive\[appropriate release folder, R419 for example].
Mapping filesThe mapping file correlates the types and the attributes in V5 metadata to the corresponding metadata files in 3DEXPERIENCE.The mapping files must be copied to the appropriate V5 server in the location $installpath\win_b64\resources\3dlive\[appropriate release folder, R419 for example].
Business Logic (BL) files CATRule and CATRuleExit files required for mapping V5 types with 3DEXPERIENCE types and any changes and/or attribute mapping during coexistence operations

Multi-Metadata Support for Customization

You can create all 3DEXPERIENCE resources, customization and mapping files that are required for the connector you are using by running the Resource Generator.

This is possible even if your product and docdir customization is in separate metadata files. You can provide two metadata files from the product and docdir domains as input for the Resource Generator. All metadata, mapping and resource files are generated simultaneously. All the objects are in a single environment on the client. You can browse and navigate customized data on the client. This ensures that resource generation does not break the 3DEXPERIENCE PLM data model.

Important: Whenever two metadata files are provided as input for the Resource Generator, make sure that one file comes from the product domain and the other from the docdir domain.

Resource generation for single domain customization: From 3DEXPERIENCE R2015x onwards, even if there is only one domain, for example, PRODUCT domain customization, resources can be generated. To do this, you must have to activate the environment variable: LVV_RESOURCE_GENERATOR_ALLOW_ONE_CUSTOMIZATION=TRUE in the client CATEnv or on the command prompt from where the LegacyCustoGenerator command is executed.

BL file generation for custom types: Different sets of BLs are generated for different customizations, for example, default and other custom types.

Prior to Resource Generator Execution

Before launching the Resource Generator, some preparation is required in order to adapt customization for the ENOVIA VPM V5 connector.

To do this:

  1. Create a directory on your local machine (ex. D:\R2018x_Custo\V55CustoGenerator).
  2. Copy two files (i.e. V5V6ResourceGenerator.xml and V5V6ResourceGenerator.xsd) from the client install directory and place them in the DBDI client directory you just created (ex: <install_directory>\win_b64\reffiles\CATVP5CustoGenerator).

Get the dictionary files from the VPM V5 server (the OOTB dictionary):

  1. On the V5 server machine, go to the V5 dictionary path: <V5_Installation_directory>\win_b64\code\dictionary .
  2. Move the OOTB dictionary to DBDI client directory on your local machine.

Get the dictionary files from the VPM V5 server (the customized dictionary):

  1. On the V5 server machine, go to the V5 dictionary path: <V5_Custo_Installation_directory>\win_b64\code\dictionary .
  2. Move the customized dictionary to the DBDI client directory on your local machine.