3D PLM PPR Hub Open Gateway

PDM Object Hub

Generating the ENOV_DATAX Data Structure


How to migrate data to ENOVIA
Use Case

ENOV_DATAX is a model used as entry point for all file-based exchanges. It represents the basic ENOVIA V5 data structure.

The ENOV_DATAX generation is the next action to perform after data extraction from VPM1.

  1. Position the run time environment:
    1. Open a window on the ENOVIA V5 server
    2. Launch the command
      $ROOT_INSTALLATION_PATH/$OS/code/command /SetEnv -c /bin/ksh

      Where:

      $ROOT_INSTALLATION_PATH The pathname of the directory whenre ENOVIA V5 is installed
      $OS The operating system:
      • aix_a for AIX
      • hpux_b for HP-UX
      • solaris_a for Solaris
  2. In your ENOVIA V5 environment, launch the command:
    GenerateEDX.sh -h

    The following information is displayed:

  3. Key in the parameters defining your customization schema, your ENOVIA schema and the output directory using the syntax indicated below:
    GenerateEDX.sh [ -h] || [ -c schemaCust -e schemaEnov -o outputDir ]

    Where:

    schemaCust A file in which you indicate the domains containing the customization schema, e.g.:
    • APLAFL
    • APLECO
    • Domain 1
    • Domain 2
    schemaEnov The ENOVIA schema, here ENOV_DATAX
    outputDir The directory in which the customized ENOV_DATAX data structure will be generated.

    The basic ENOV_DATAX schema is stored in the environment variable CATStartupPath/STEP/samples.

    The name of the ENOVIA schema is identical to the name of the generated express schema. An ENOV_DATAX.express file containing the ENOV_DATAX express schema is generated.

  4. Use mkmk to compile the schema.
  5. Export the environment variables to point on the new library generated by the schema compilation.

    The global content of ENOV_DATAX represents the data that is supported, i.e. Product Structure, Configuration, Action Flow and Change Management.


Copyright © 1994-2002, Dassault Systèmes. All rights reserved.