|The CATDMUBuilder is intended to
save DMU loading time by:
This capability fills the local cache with all necessary data to avoid
tessellation or access to the PDM cache during interactive loading of given
product structures. This loading will use only the local and release cache.
DLNames are now supported for the CATDMUBuilder batch process.
|When using input data that contains references to a PDM system, it is imperative that you be connected to that PDM system while the CATDMUBuilder process is running.|
|On Windows, it is always necessary
to specify the -env and -direnv options. Note also
that these options should always be specified at the end of the command
line. For more information, see the Infrastructure User's Guide,
Starting a Session on Windows.
|When you build a product using CATDMUBuilder with a PSN file and the selected instances option, all documents attached to Parts on the branches of the selected leaves are taken into account.|
Invoking the CATDMUBuilder help:
Feeding the cache with tessellated data corresponding to product structures contained in a directory /u/product
Moving CATProducts corresponding to product structures contained in a distant directory /distant/product, storing them on a local directory /local/product and feeding the local cache:
Feeding the cache with tessellated data corresponding to product structures contained in a directory /u/product, which refers to VPM documents:
|When using CATDMUBuilder in
conjunction with ENOVIAVPM, it is necessary to first
launch the ENOVIAVPM server:
Documents of the following types are treated: CATProduct,
CATVpm, psn, xml.
: To extract products and store them in the directory dir.
|-nocache : To run the
batch without generating cache content. Note: This option has no effect
when the product needs to be built from scratch.
-copycache : To copy all cache content from released caches to the local cache.
-force : To force re-calculation of cache content.
-onlyone dircgr : To resolve all links to external products and save the resulting product locally as one unique product.
|-static : To open a psn
file with static option (valid only for psn). By default it is open with
-selins : To open a psn file with selected instances (valid only for psn). By default it is open with all instances.
-replacebycgr dircgr : To replace all components by related cgr copied in the directory dircgr.
-activate : To activate all shapes and save the activation state.
-deactivate : To deactivate all shapes and save the activation state.
-prefix prefix : To save all products with a prefix in their name.
|-db : Input database type:
For processing data stored in a PDM database.
|-mp : To enable multi-processing for
product building. Multi-process parameters must be set in :
Tools -> Options -> Digital MockUp ->
-timeout : -timeout time: set the time out. After this time, child processes will be killed, on the assumption that they've entered a CPU loop. Available with multi-process mode (-mp) only.
|- outputformat wrl : To generate a VRML file as output. Note: In batch mode, as there is no editor, the wrl file will not contain any viewpoints.|
-listcomp : To list all the components of each product. The directory will contain one text file per product, the name of which will be the same as the product. Each file has one component per line.
-noreplace : During the running of the batch process, it could happen that a file has to be copied in a directory where it already exists. Without the noreplace option, the file will be overloaded. With the noreplace option, the file will not be replaced.
-savedata: To save referenced data in the product directory (see -product above).
|A user interface is now available
for running the CATDMUBuilder utility.
For more information on using the Batch Monitor, see the Infrastructure User's Guide, Basic Tasks, Running Batches, Running Batches Using the Batch Monitor.
The utility can open an ENOVIAVPM assembly corresponding to all nodes under a given root or a CATProduct stored as Black-box. This is done using a new type of document CATVpm. This document is a text file:
Example 1: a simple node
Example 2: a simple node with two config handlers
Example 3: a Black box