Exporting Pro/ENGINEER Models from Teamcenter with ipemexport

The ipemexport utility exports Pro/ENGINEER models from Teamcenter Engineering. Datasets may also be checked out, i.e. reserved, when exporting models. Models that are checked out by ipemexport may be checked back into Teamcenter with the ipemimport utility.

Usage
ipemexport [-login] [-u username -p password [-g group]] [-bypass] [-help] [-site_preferences true|false] [-user_preferences true|false] [-work_preferences true|false] [-preferences path] [-delete_files] [-skip_files] [-export_dir path] [-export true|false] [-export_related true|false] [-checkout true|false] [-checkout_related true|false] [-change_id id] [-comment string] [-use_bom true|false] [-config rule] [-precise_is_imprecise] [-precise_relation_is_imprecise true|false] [-precise_family_table_is_imprecise true|false] [-no_filters] [-filter name] [-levels limit] [-item_id id] [-item_revision_id rev] [-model_name datasetname] [-model_type type] [-dry_run] [-output instructionfile] [-log logfile] [-incomplete_operation_fatal | -incomplete_operation_ok] [-marker markername] file1 file2 ...

Description
The ipemexport utility will export a Pro/ENGINEER model, and the models on which it depends, from Teamcenter to a local directory. The model to export may be identified with the – item_id, –item_revision_id, –model_name and –model_type options on the command line, or several models may be specified in instruction files, given by arguments file1, file2, etc., following any command line options. Instruction files are text files that list models to export, one model per line. Some options affect only explicitly specified models identified on the command line or in instruction files. Other options affect implicitly specified models that are not identified on the command line or in instruction files, but which are also exported because explicitly specified models depend on them. The default action is to export all explicitly specified models and the models on which they depend, but this can be changed using the –export option for explicitly specified models and the –export_related option for implicitly specified models. To reserve models, the –checkout option reserves explicitly specified models and –checkout_related reserves implicitly

59

The default is false. but it does not export any files or reserve datasets (optional). -checkout_related true | false True specifies that implicitly specified models should be reserved (optional). The ipemexport utility uses the same mapping file and user preferences used by the Teamcenter Engineering 2005 Manager for Pro/ENGINEER. To reserve implicitly specified models. -checkout true | false True specifies that explicitly specified models should be reserved (optional). If both -delete_files and -skip_files are given on the command line.bomrevisionruledefault user preference or the default Teamcenter rule. The ipemexport options are described below.specified models. This option does not affect implicitly specified models. -config rule Specifies the name of a configuration rule (optional). the program will abort if any conflicts are found. One significant difference between the ipemexport utility and the Teamcenter Engineering 2005 Manager for Pro/ENGINEER is that ipemexport does not copy attribute values from Teamcenter to parameters in the Pro/ENGINEER models. this option can be used to reserve a dataset without exporting the model file in it. The default is to use the rule specified by the iman. Files that do not conflict with the models to be exported are not affected. When used 60 . Note that if –export is false. which means that these models will not be reserved. Only users with Teamcenter administrator privileges may enable bypass. Models that have been reserved may be checked back into Teamcenter using the ipemimport utility. which means that these models will not be reserved. -comment string Specifies a comment to assign to all datasets that are checked out (optional). this option can be used to reserve datasets without exporting the model files in them. Note that if –export_related is false. -bypass Enables bypass of access controls in Teamcenter (optional). use the –checkout_related option. -dry_run The utility goes through most of the actions it would ordinarily execute. -change_id id Specifies a change ID to assign to all datasets that are checked out (optional). -delete_files Specifies that conflicting files already in the export directory should be deleted before any models are exported (optional). The default is false. the last one specified takes effect. If neither -delete_files nor -skip_files is specified.

Each use of this option adds another filter to any filters previously specified.default user preference.checkout.choices user preference for the names of filters that can be used with this option. This is the default.properties file located in the directory where the Teamcenter Engineering 2005 Manager for Pro/ENGINEER is installed. -export true | false True specifies that explicitly specified models should be exported. User preferences are described in the ipem.in conjunction with the –output option. use the –export_related option. -incomplete_operation_ok Causes the program to continue when an operation on a model cannot be completed due to an error (optional). -export_related true | false True specifies that implicitly specified models should be exported. This option does not affect implicitly specified models. The default filters are those specified by the filters. an instruction file can be generated for use in a subsequent run of this utility. Ignored when –login is specified. This option may be used only once on the command line.checkout. Later filters can override the actions of previous filters. which is the default (optional). -g groupname Specifies the group name to use when connecting to Teamcenter (optional). -incomplete_operation_fatal Causes the program to exit when an operation on a model cannot be completed due to an error (optional). 61 . -item_id id Specifies the Teamcenter item ID of a model to export (optional). False means that these models will not be exported. which is the default (optional). To export implicitly specified models. Note that the –checkout_related option may be true even when –export_related is false. -help Prints usage information and exits. -export_dir path Specifies the path to the export directory (optional). Note that –checkout may be true even if –export is false. -filter name Specifies a filter to use when collecting implicitly specified models (optional). The default is -incomplete_operation_ok. but note that the -no_filters option can erase those prior filters. The default is to export models to the current working directory. but wildcards are allowed. False means that these models will not be exported. See the filters.

and -marker options are ignored.properties file located in the directory where the Teamcenter Engineering 2005 Manager for Pro/ENGINEER is installed. However. -model_type type Specifies the dataset type or the three-letter extension that identifies the Pro/ENGINEER model type. but wildcards are allowed. the default marker is that of the first server in the client_specific.properties file. and its dataset is of type ProPrt. -marker markername The Teamcenter server marker name or URI. Ignored when –login is specified. although ipemexport ignores limit. -g. When this option is specified. a new list of filters will be created if this option is followed by one or more -filter options. the -u. the log file will be ipemexport. -log logfile Defines the name of the log file that will be created (optional). the name of a model stored in the file widget. described in the ipem. the type of a model stored in the file widget.2 is PRT. the number of implicitly specified models is unlimited. or if limit is a negative number.prt.2 is WIDGET. If not specified. For example. -model_name datasetname Specifies the name of a Pro/ENGINEER model. but otherwise the logging preferences in ipem. -p.properties have their usual effect.levels user preference. The limit can only be set using this command line argument. 62 . If not specified. The model name is the same as the dataset name. This option may be used only once on the command line. -login Uses the Teamcenter login dialog. A positive number sets the maximum number of levels of implicitly specified models that can be collected. Logging cannot be disabled and warning messages cannot be suppressed. This is the name alone.prt. such that no filters will be used when collecting implicitly specified models. -no_filters Causes any previous list of filters to be erased. If not specified. so type for a Pro/ENGINEER part model may be either PRT or ProPrt. without any extension or path. For example. -levels limit Specifies the number of levels to include in the hierarchy of dependencies when collecting implicitly specified models (optional).levels.txt in the current directory. This option has the same purpose as the limit.-item_revision_id rev Specifies the Teamcenter revision of a model to export (optional). found in the Teamcenter Portal installation directory.

properties file in the installation directory should be read. See the ipem. This option does not affect the treatment of relations between family table instances and their generic. which is the default (optional). Files that do not conflict with the models to be exported are not affected.properties file and is read after reading ipem.properties files in the installation directory. which means the rule given by the –config option will be used to select item revisions (optional).-output instructionfile Defines the name of an instruction file to be written (optional). -preferences path Defines the path to an additional user preferences file (optional). the last one specified takes effect. so it may redefine properties specified in those other files. This option is a shortcut for the two options: -precise_relation_is_imprecise true -precise_family_table_is_imprecise true -precise_family_table_is_imprecise true | false True causes precise family table relations to be treated as if they are imprecise. The default is to not skip files. except for those that are locked. Ignored when –login is specified. False means that user preferences in this file should be ignored. -skip_files Specifies that conflicting files already in the export directory should be preserved by skipping export of the corresponding files from Teamcenter (optional). and working directory. -precise_is_imprecise Causes precise relations to be treated as if they are imprecise. which means the rule given by the –config option will be used to select item revisions (optional). 63 . which means the rule given by the –config option will be used to select the generic’s item revision (optional). except for locked user preferences. This option cannot be used to override locks. This option may be repeated on the command line to read several additional files. If neither -delete_files nor -skip_files is specified.properties file in the installation directory for more information about user preferences. -precise_relation_is_imprecise true | false True causes precise general relations to be treated as if they are imprecise. If both -delete_files and -skip_files are given on the command line. This file has the same format as an ipem. This file lists each model exported or reserved from Teamcenter. -site_preferences true | false True specifies that the ipem. the program will abort if any conflicts are found. -p password Specifies the password to use when connecting to Teamcenter. user’s home directory.

Family Tables Every Pro/ENGINEER model in Teamcenter is represented by a dataset. This option cannot be used to override locks. However. even models that are family table instances.properties file in the working directory should be read. -work_preferences true | false True specifies that the ipem. If you reserve a family table instance. the instances in a family table depend on the family table generic.properties file in the user’s home directory should be read. 64 . use ipemimport’s –no_family_table_expansion option so only the reserved instance will be saved. In either case.properties file in the installation directory for more information about user preferences. the implicitly specified models associated with an assembly include the items that were last saved with the assembly. in the case of a family table instance. -use_bom true | false True causes BOMs to be used when finding implicitly specified models (optional). the dataset does not contain the model’s file. in case the BOM has been modified since the assembly was last saved to Teamcenter. Instead. which is the default (optional). See the ipem. which means that BOMs will be ignored when determining the dependencies of assemblies. except for locked user preferences. except for locked user preferences. False means that user preferences in this file should be ignored. See the ipem. -user_preferences true | false True specifies that the ipem. ipemimport will attempt to regenerate and save every instance in the family table.-u username Specifies the user name to use when connecting to Teamcenter. ipemexport will actually export the model file from the family table generic’s dataset. If you “export” a family table instance. Ignored when –login is specified. which is the default (optional).properties file in the installation directory for more information about user preferences. and it is in the dataset for the generic where the Pro/ENGINEER model file can be found. Without this option. ipemexport will also reserve the generic. The default is false. This option cannot be used to override locks. When saving a family table instance back to Teamcenter with the ipemimport utility. but setting this option to true makes it possible to also include items from the assembly’s BOM. False means that user preferences in this file should be ignored.

prt. the Pro/ENGINEER part BOLT_A in revision B of item 702283. # Sample ipemexport instruction file item_id=702283 item_revision_id=B model_name=BOLT_A model_type=PRT item_id=702284 item_revision_id=A export=false checkout=false item_id=702285 item_revision_id=A The first line is a comment.prt.Multiple Model Versions Only one version of any given Pro/ENGINEER model will be exported in one run of the ipemexport utility. The value may be either true or false. Each line in the file should identify one model. By default. Blank lines and comments are also allowed. it must be enclosed in double quotes. but it applies only to the model specified on the line where this keyword appears. if several revisions of a model are specified on the command line or in instruction files. Instruction Files An instruction file is a text file that lists Pro/ENGINEER models. and keyword is one of the following: checkout This is the same as the –checkout command line option. the value of the –export command line option applies. A value containing spaces must be enclosed in double quotes. so the value may be either PRT or ProPrt. and its dataset is of type ProPrt.2 is PRT. A simple instruction file is shown below. The value is the revision. but it applies only to the model specified on the line where this keyword appears. the type of a model stored in the file widget. so the command line options –checkout and –export will be used to decide whether to export and/or reserve this model. The value is the dataset type or the three-letter file extension that identifies the Pro/ENGINEER model type. Any text between the comment character and the end of the line will be ignored. 65 . The comment character is #. This is the name alone. The model name is the same as the dataset name. model_type If a value contains spaces. For example. For example. For example. A model is identified by several keyword=value pairs. without any extension or path. If this keyword is not specified. the name of a model stored in the file widget.2 is WIDGET. No checkout or export keyword is given on this line. The value is the item ID. only the first one encountered will actually be exported. ipemexport will export the model without reserving it. This is the same as the –export command line option. The second line identifies a particular model. The value may be either true or false. the value of the –checkout command line option applies. export item_id item_revision_id model_name The value is the name of the Pro/ENGINEER model. If this keyword is not specified.

the command above will also reserve the family table generic regardless of how –export_related is set. If the models in 702283 should be reserved. plus all models on which it depends. the command would be: ipemexport -u infodba -p infodba exports. Suppose an instruction file named exports. checkout The fourth line also identifies a model using only its item ID and revision. None of these models will be reserved. neither will be exported or checked out because export and checkout are both false on this line.txt 66 .The third line specifies an item ID and revision. For example. the command becomes: ipemexport -u infodba -p infodba –item_id 702283 –item_revision_id=B \ -checkout true –comment "Changes per 4283" This reserves only the model in revision B of 702283.txt exports. and the models on which it depends also should not be exported. Examples The following example shows a simple use of this export utility. use the –dry_run option and ask ipemexport to generate an instruction file: ipemexport -u infodba -p infodba –dry_run –output out. the model will be exported or reserved according to the command line options –export and –checkout. this line affects all of them. If revision A of item 702284 has several Pro/ENGINEER datasets.txt To find out what will really be exported or reserved prior to executing the command above. In this case. if revision A contains both a part and a drawing. Since no export or keyword is included on this line. If the Pro/ENGINEER model in revision B should be reserved without being exported. but the model name and type are not given.txt specifies the models to export. but the models on which it depends are still exported. ipemexport -u infodba -p infodba –item_id 702283 –item_revision_id=B This command will export the Pro/ENGINEER model(s) in revision B of item 702283. the command would be: ipemexport -u infodba -p infodba –item_id 702283 –item_revision_id=B \ -checkout true –export false –export_related false \ –comment "Changes per 4283" If 702283 is a family table instance. The model files will be placed in the current working directory.

This noninteractive utility saves models to Teamcenter after opening them in Pro/ENGINEER. item revisions. Teamcenter objects (items.. directories containing Pro/ENGINEER models. Usage ipemimport [-login] [-u username -p password [-g group]] [-bypass] [-help] [-site_preferences true|false] [-user_preferences true|false] [-work_preferences true|false] [-preferences path] [-dry_run] [-output instructionfile] [-log logfile] [-folder folder] [-overwrite | -revise] [-precise] [-precise_bom true|false] [-precise_relation true|false] [-precise_family_table true|false] [-no_create] [-no_attributes] [-no_boms] [-auxiliary_files_only] [-no_family_table_expansion] [-convert_ipro] [-existing_dataset_fatal | -existing_dataset_ok] [-changed_dataset_fatal | -changed_dataset_ok] [-incomplete_operation_fatal | -incomplete_operation_ok] [-missing_child_fatal | -missing_child_ok] [-missing_file_fatal | -missing_file_ok] [-unmapped_type_fatal | -unmapped_type_ok] [-marker markername] [-except exceptfile] file1 file2 . parameter values may be copied to attributes in Teamcenter.. and datasets) are created as needed and the model files are imported into the datasets. obtains information concerning parent-child relationships. parameter values are copied from Pro/ENGINEER to attributes of the Teamcenter objects. items. and datasets may be created. 67 . In the first step. -no_attributes. parameter values. file2. Description The arguments file1.. Each of these steps can be disabled with the -no_create. In the second step. or -no_boms option. During the import process. The final step updates BOMs and other references between objects. or instruction files. Models are imported in three steps. and BOMs may be updated. then imports the models into Teamcenter.Importing Pro/ENGINEER Models into Teamcenter with ipemimport The ipemimport utility imports Pro/ENGINEER models into Teamcenter Engineering.. and so on. respectively. are Pro/ENGINEER models to import. family tables.. item revisions. This utility opens all of the models specified by these arguments in a single. An instruction file is a text file in which each line is either the path to a Pro/ENGINEER model file or a directory containing Pro/ENGINEER models. . nongraphical Pro/ENGINEER session.

This also implicitly sets –no_attributes and –no_boms.compatibility user preference. Models will not be imported into datasets that are reserved by another user. -convert_ipro Causes the program to convert data previously saved with iPRO to the scheme used by the Teamcenter Engineering 2005 Manager for Pro/ENGINEER (optional). The models specified by this option will be opened in Pro/ENGINEER. Compatibility mode is controlled with the ipro. This option may be repeated to add more models to the exception set. This is the default when the checkin. The other arguments for ipemimport are described below. an instruction file. but it does not import any files or other data to Teamcenter (optional). -changed_dataset_ok Causes the program to continue regardless of whether a model’s dataset appears to have changed since the model was exported (optional). Also. When used in conjunction with the –output option. if you reserve a dataset using check out with export.properties file. described in the ipem. or a directory (optional).pdmversion. Only users with Teamcenter administrator privileges may enable bypass.ignore user preference is always and -changed_dataset_fatal when the checkin. you must either use the –overwrite option or check out the dataset prior to running ipemimport (the ipemexport utility may be used to check out datasets). but will not be imported to Teamcenter. -dry_run The utility goes through most of the actions it would ordinarily execute. The default is -changed_dataset_ok when the checkin. 68 . the model can only be imported from the export directory that was specified at the time you reserved the dataset.ignore user preference is never or prompt. -changed_dataset_fatal Causes the program to exit when a model’s dataset already exists in Teamcenter and it appears to have changed since the model was exported (optional). and the model will be deleted from that directory after it is imported. an instruction file can be generated for use in a subsequent run of this utility. The exceptfile argument may be a Pro/ENGINEER model file.pdmversion. -bypass Enables bypass of access controls in Teamcenter (optional). -auxiliary_files_only Only auxiliary files are imported. the program exits when attempting to save a model in an item revision that was created with iPRO. This option is ignored when iPRO compatibility mode is disabled.When importing a model into an existing dataset. -except exceptfile Specifies Pro/ENGINEER models to skip. Without this option.ignore user preference is always. without Pro/ENGINEER models.pdmversion.

properties have their usual effect.txt in the current directory. the -u. The default is -missing_child_ok when the checkin. If not specified. -p.properties file. -incomplete_operation_ok Causes the program to exit when an operation on a model cannot be completed due to an error (optional). and -marker options are ignored. This argument is ignored when -no_create or -overwrite is specified. -missing_child_fatal Causes the program to exit when a model being imported depends on another model that cannot be found (optional). but otherwise the logging preferences in ipem.ignoremissing user preference is never. When this option is specified. -incomplete_operation_fatal Causes the program to exit when an operation on a model cannot be completed due to an error (optional). -help Prints usage information and exits. the log file will be ipemimport. -existing_dataset_ok Causes the program to continue when a model cannot be imported because its dataset already exists (optional). belonging to the user. the default marker is that of the first server in the client_specific. into which new items will be placed (optional). The default is -existing_dataset_ok. found in the Teamcenter Portal installation directory. -login Uses the Teamcenter login dialog. Logging cannot be disabled and warning messages cannot be suppressed.-existing_dataset_fatal Causes the program to exit when a model cannot be imported because its dataset already exists (optional). If not specified. 69 . -g groupname Specifies the group name to use when connecting to Teamcenter (optional). -folder folder Specifies the name of a Teamcenter folder. This is the default. Ignored when –login is specified. -marker markername The Teamcenter server marker name or URI. -log logfile Defines the name of the log file to be written (optional). The default is -incomplete_operation_ok.ignoremissing user preference is always or prompt and -missing_child_fatal when the checkin. This is the default. Ignored when –login is specified. -g.

-overwrite Causes existing model files already in Teamcenter to be replaced if a new file is imported (optional). The default is to regenerate all family table instances in the Pro/ENGINEER session. The default is to create imprecise BOMs and relations that refer to items. This option is recommended when saving models that were previously checked out by the ipemexport utility. .-missing_child_ok Causes the program to continue when a model being imported depends on another model that cannot be found (optional). This option is a shortcut that is equivalent to: 70 Skips the step in which BOMs and other references are updated in Teamcenter (optional). This file lists all of the models imported into Teamcenter. -missing_file_ok Causes the program to continue when a file specified on the command line or in an instruction file cannot be found (optional). This is the default. The default is to skip models that already exist in the latest revision. This option is incompatible with -revise. item revisions. -no_family_table_expansion Skips the step in which all family table instances are regenerated (optional). and datasets are created in Teamcenter (optional). -missing_file_fatal Causes the program to exit when a file specified on the command line or in an instruction file cannot be found (optional). so only family table instances that were checked out will be saved back to Teamcenter. This also skips the step in which Pro/ENGINEER model files are imported into the datasets. The default is -missing_file_fatal.ignoremissing user preference is always or prompt. Ignored when –login is specified. -precise Causes precise BOMs and relations to be created. -output instructionfile Defines the name of an instruction file to be written (optional). -no_attributes Skips the step in which attribute values are copied from Pro/ENGINEER to Teamcenter (optional). -p password Specifies the password to use when connecting to Teamcenter. -no_boms -no_create Skips the step in which items. This is the default when the checkin. which means the BOMs and relations will refer to item revisions instead of items (optional). then to save every family table instance to Teamcenter as a separate dataset.

which creates imprecise relations. it will reference the other model’s item revision instead of its item (optional).-precise_bom true -precise_relation true -precise_family_table true -precise_bom true|false True causes precise BOMs to be created (optional). Ignored when -login is specified. -u username Specifies the user name to use when connecting to Teamcenter. or refer 71 . -preferences path Defines the path to an additional user preferences file (optional). -unmapped_type_ok Causes the program to continue when a model cannot be imported because the model’s type has not been mapped to a Teamcenter dataset type (optional). skipping any model if the latest revision already contains a version of the model. This option is incompatible with -no_create. -unmapped_type_fatal Causes the program to exit when a model cannot be imported because the model’s type has not been mapped to a Teamcenter dataset type (optional). and revision can be specified in an instruction file or by mapping parameters from the Pro/ENGINEER model to these attributes in Teamcenter. user’s home directory. which creates imprecise relations. Names. Types. -revise Causes a new revision to be created for each model imported into Teamcenter (optional).properties files in the installation directory. This option may be repeated on the command line to read several additional files. and Revisions A model’s item ID. which creates imprecise BOMs.properties file and is read after reading ipem. The default is false. and working directory. The default is to import into the latest revision. Item IDs. name. so it may redefine properties specified in those other files. This is the default. type. This file has the same format as an ipem. which means the instances will reference the generic’s item revision (optional). which means that when a Pro/ENGINEER model depends on another model. The default is false. The default is -unmapped_type_fatal. except for those that are locked. -precise_family_table true|false True causes precise relations to be created between family table instances and their generic. -precise_relation true|false True causes precise relations to be created. See the section on Instruction Files below for more information on how to do this in an instruction file. The default is false. This option does not affect BOMs or the relation between a family table instance and its generic.

or -no_create option will ensure no models are skipped. the item ID and item name will both be WIDGET. except for those specified with the –except option. Each family table instance is treated as a model in its own right. Specifying the -overwrite. both will be stored in the item whose ID is WIDGET. • The default item ID is assumed to be the same as the model name. • • When several Pro/ENGINEER models have the same item ID. all of the instances are also imported into Teamcenter.prt and no other item ID is specified for either model. Attributes This utility will copy parameter values from Pro/ENGINEER models to attributes in Teamcenter.drw contains a drawing of widget. the following defaults apply. -revise.precisebom preference. item revision. An item. type. Family Tables If a model contains a family table.prt is imported into Teamcenter. described in the ipem. except for those instances specified with the –except option in instruction files.to the section on the Attribute Mapping for more information on how to set up an attribute map.xml in the Teamcenter Engineering 2005 Manager for Pro/ENGINEER installation directory.itemtypedefault preference. -revise. The model name is also used as the default item name. If a model was skipped during the file import step because its item revision already has a dataset for the model. For example. The default item type is specified by the iman. if a part file widget. The default type is Item. it will also be skipped during the step that updates BOMs. For example. and the BOMs that are affected. If a model was skipped during the file import step because its item revision already has a dataset for the model. described in the ipem. except for those specified with the –except option. and dataset will be created 72 . if widget. are specified by the Teamcenter Engineering 2005 Manager for Pro/ENGINEER mapping file. The default mapping file is ipem. This can be changed by using the –precise option or by setting the iman. The types of models that are added to the BOMs. The attribute values that are copied are specified by the Teamcenter Engineering 2005 Manager for Pro/ENGINEER mapping file. BOMs BOMs will be created or updated by this utility.properties file in the Teamcenter Engineering 2005 Manager for Pro/ENGINEER installation directory. BOMs are imprecise by default. The default revision is the latest revision of an item unless the -revise option is specified. they will be imported into the same item. If the model’s item ID. The default mapping file is ipem.xml in the Teamcenter Engineering 2005 Manager for Pro/ENGINEER installation directory. name. Specifying the –overwrite. or revision is not specified. it will also be skipped during the step that copies attribute values.properties file in the Teamcenter Engineering 2005 Manager for Pro/ENGINEER installation directory. or –no_create option will ensure no models are skipped.

1 will be loaded instead of widget.prt.prt. consider using the import_file utility. This information can be used later to import auxiliary files with import_file. to provide the item ID. which means that if two directories contain different versions of a model. If you do not want to import models.prt. Models are loaded in the order in which they appear on the command line. and named reference for each auxiliary file required when a model is saved to Teamcenter.prt. revision. This behavior can be changed with the –no_family_table_expansion option.prt. but only auxiliary files.prt.6 will be imported into Teamcenter.6.1 but this path must be quoted: "D:\Pro Models\widget. preventing the other directory’s version from being loaded.1 and directory B contains widget.for it. For example. For more information on auxiliary files and the map file. refer to the section on The Map File. ipemimport does not attempt to import all family table instances. but instead it imports only those instances that are implicitly opened in the Pro/ENGINEER session because they are used by other models. Blank lines and comments are also allowed. the following path does not have to be quoted: D:\Models\widget. even if widget. Multiple Model Versions Version numbers are ignored in Pro/ENGINEER file names. When specified.2.prt.2 if directory A appears before directory B on the command line. dataset name. via the auxiliary file map. Instruction Files An instruction file is a text file that lists Pro/ENGINEER model files or directories containing Pro/ENGINEER models.prt. This program loads only the highest-numbered version of a Pro/ENGINEER model when several versions occur in a directory. dataset type. For example. For example. if a directory contains widget. Auxiliary Files The ipemimport utility will create and import auxiliary files when importing models if an auxiliary file map exists. If the path to a file or directory contains spaces. Note that the Teamcenter Engineering 2005 Manager for Pro/ENGINEER can be configured. widget. although the Pro/ENGINEER model file will be stored only in the dataset of the family table’s top generic. if directory A contains widget. Each line in the file should contain the path to one file or directory. the model in the directory specified first will be loaded first. The comment character is #. it must be enclosed in double quotes.1" 73 .5 is specified on the command line. only widget. Any text between the comment character and the end of the line will be ignored.5 and widget.prt. which is included with Teamcenter.prt.

The value is the item name. the name of a model stored in the file widget. For example.units. the type of a model stored in the file widget. For example.prt. The value may be one of the following strings: cm ft in m micron mil mm model_type units_length Alternatively. The Pro/ENGINEER file name does not have to be given if the model_name and model_type options are included on the line. where keyword is one of the following: dataset_desc The value is the dataset description. If a value contains spaces. Although these two options are not sufficient to identify the file to load.length user preference. item_revision_id item_type model_name The value is the item type.prt. It is unnecessary when using Pro/ENGINEER Wildfire. For example. This is the name alone. suppose three different 74 . it must be enclosed in double quotes. This option is redundant if the file name is given. the value may be a real number. The value is the revision. which is described in the ipem. If not specified. This is used only with Pro/ENGINEER 2001. It cannot be used to rename the model. without any extension or path. The value is the three-letter extension that identifies the Pro/ENGINEER model type. This option is redundant if the file name is given. The value is the units used to measure lengths in the Pro/ENGINEER model.properties file in the Teamcenter Engineering 2005 Manager for Pro/ENGINEER installation directory. they can be used to refer to a model that is loaded implicitly or explicitly by a file specified elsewhere in the arguments given to ipemimport. This is ignored if the item already exists. which specifies the number of inches per unit of length used in the model. The value is the name of the Pro/ENGINEER model. It cannot be used to change the type of the model. the default is taken from the pe. This is ignored if the item already exists. item_desc item_name item_id The value is the item description. The value is the item ID.2 is WIDGET. This is ignored if the item already exists. Each argument has the form keyword=value. This is ignored if the dataset already exists.The path to a Pro/ENGINEER model may be followed by several optional arguments on the same line.2 is PRT.

Two optional arguments appear on this line to specify the model’s item ID and.txt has been created to specify the item ID to use for the model: model_name=WIDGET model_type=PRT item_id=184786 The ipemimport utility can then be executed three times to load the revisions: ipemimport –u infodba –p infodba –revise widget. In this example. The ipemimport utility automatically imports all family table instances. the models will be imported into each item’s latest revision. attribute values will be copied to Teamcenter and BOMs will be created or updated. The third line specifies a Pro/ENGINEER part file bolt.1 ipemimport –u infodba –p infodba –revise widget. To force all models to be imported. replacing Pro/ENGINEER model files that may have been imported previously. Since the file name cannot identify the individual instances.2 item_id=702283 item_desc="Bolt family generic" model_name=BOLT_A model_type=PRT item_id=702284 model_name=BOLT_B model_type=PRT item_id=702285 model_name=BOLT_C model_type=PRT item_id=702286 The first line is a comment.8 In each case. The model identified in the instruction file depends on the file that the utility loads.revisions of widget.2 contains a family table. and a single instruction file named widget. new items. the path to the model’s file is specified on the command line. the last three lines use the model_name and model_type keywords to identify these models. but in this case the user wants to specify the item ID where each instance is to be stored. use the –overwrite option: ipemimport -u infodba -p infodba –overwrite c:\ProeMdls For items that already exist. but it will skip any model that already has a dataset in Teamcenter.txt revb\widget. revb.2.prt.prt are stored in directories named reva.txt revc\widget. a description to include with the item.txt reva\widget. which is what the last three lines accomplish.prt.prt. and revc. ipemimport -u infodba -p infodba c:\ProeMdls This command will load the latest version of each Pro/ENGINEER model from the c:\ProeMdls directory into Teamcenter. Another simple instruction file is shown below. suppose bolt. The second line specifies a directory D:\wwc\models. and datasets will be created as needed.3 ipemimport –u infodba –p infodba –revise widget. the import utility could be used this way: ipemimport -u infodba -p infodba -revise c:\ProeMdls 75 . # Sample ipemimport instruction file D:\wwc\models D:\wwc\bolts\bolt. The ipemimport utility will load all Pro/ENGINEER models that it finds in that directory. If a new item revision should be created for those items that already exist.prt. item revisions. Examples The following example shows a simple use of this import utility. For the models that are imported.prt. if the item has to be created.prt.

Sign up to vote on this title
UsefulNot useful