assy_jt_creator

Creates a JT representation of a given Teamcenter assembly. The resulting file is stored in the file system and, optionally, in the database. You can use the utility to collect the JT files on each node in a configured structure and combine all JT files into a single monolithic assembly JT. You can use a monolithic JT file to view assemblies in Resource Browser. The utility can also create an assembly JT file that contains pointers to other JT files, each representing a component in an assembly. Each node can have a JT file and a transformation of that node. Additionally, the utility can create a JT file for use with Tecnomatix eMServer only. Syntax assy_jt_creator -u=user-id -p={password | -pf=password-file} [-g=group ] {-sc=structure-context | { -item=item-id | -key=[keyAttr1=keyVal1] [,keyAttr2=keyVal2]…[,keyAttrN=keyValN] }} -tar_loc=target-location [-i=batch-file] [-log=logfile-name] [-rev=revision] -rev_rule=revision-rule [-var_rule=variant-rule] [-tmode=transfer-mode-name] [-jt_type={1 | 2 | 3} ] [-pin=0 | 1] [-cof=0 | 1] [-dt_type=dataset-type] [-dt_rel=dataset-relation] [-dt_ref=named-reference] [-de=n | e | a | r] [-assy_update={create | replace} ] [-skip_root_dset_with_name=dataset-name] [-skip_remote_lines] [-debug] [-h] Arguments -u Specifies the user ID. This is a user with Teamcenter administration privileges. Note If Security Services single sign-on (SSO) is enabled for your server, the -u and -p arguments are authenticated externally through SSO rather than being authenticated against the Teamcenter database. If you do not supply these arguments, the utility attempts to join an existing SSO session. If no session is found, you are prompted to enter a user ID and password. -p Specifies the password. This argument is mutually exclusive with the -pf argument. -pf Specifies the password file. For more information about managing password files, see Manage password files. This argument is mutually exclusive with the -p argument. -g Specifies the group associated with the user. If used without a value, the user's default group is assumed. -sc Specifies the name of the structure context (see CompoundTools in the following figure). If you include this argument, item ID, revision ID, revision rule, variant rule, and transfer mode arguments are not required. Tecnomatix Integration Product Robots CompoundTools MAA18564L/001;1–EA030 Auto Weld For more information about structure contexts, see Multi-Structure Management. -item Specifies the item ID of the top line. If you do not include the -sc argument, either this argument or the -key argument is required. -key Specifies the key of the top line when multiple attributes are used to form the unique item ID. Use the following format: Copy [keyAttr1=keyVal1] [,keyAttr2=keyVal2]…[,keyAttrN=keyValN] To find the key of an object, use the get_key_string utility. For more information, see BMIDE for Data Model Design. -tar_loc Specifies the full operating system path to an existing location where Teamcenter stores the JT assembly file. This argument is required. -i Specifies an input batch file. This XML file uses elements that are equivalent to the command line arguments and contains information about the assembly JT files you want included in the monolithic JT assembly. Use this method to simplify the input of parameters. This allows you save a set of arguments you can use each time you run the utility. This file must contain the following elements as a minimum (all defaults are used in this file): Note For more information, see the equivalent command line argument description (identified in comments in the file listings). Copy <!–- Required root element --> <!–- Element holding JT file parameters --> The ParamBatch element contains all ParamSet elements. A separate ParamSet element with a unique id attribute is required for each JT file you include in the assembly. This file shows all possible elements that you can specify with empty elements for informational purposes. No defaults are used. Unless an element contains only attributes, which is not the case for an input batch file, well-formed XML requires that you provide a value between the element opening and closing tag. Therefore, do not include empty elements if you want to use the default value. Copy

  <RevId> </RevId> <!-- See -rev argument -->

  <RevisionRule> </RevisionRule> <!-- See -rev_rule argument -->
  <!-- If the revision rule is not specified, the utility uses the default 
      "Latest Working"revision rule.
  -->

  <VariantRule> </VariantRule> <!-- See -var_rule argument -->

  <TransferMode> </TransferMode> <!-- See -tmode argument -->
  <!–– If TransferMode is not specified, the utility uses the default  
       "JTDataExportDefault" transfer mode –->

  <JtAssyType> </JtAssyType> <!-- See -jt_type argument-->
  <!-- The type of assembly to be created can be specified as:
       1 - Monolithic JT 
       2 - Assembly JT
       3 - CoJT. 
       The utility uses "Monolithic" if this is not specified 
  -->

  <ProcessIntermediateNode> </ProcessIntermediateNode>        <!-- See -pin argument -->
  <!–– ProcessIntermediateNode indicates if the intermediate nodes need to be
       processed. This is s boolean value (1/0). If this is not specified, 
       The utiliy uses 1 - intermediate nodes gets processed. 
  -->

  <ContinueOnFail> </ContinueOnFail>        <!-- See -cof argument -->
  <!–– ContinueOnFail specifies whether the creation of the assembly should
       continue if any errors are encountered. This is a boolean value (1/0)
       If this is not specified, the utility uses 1 - continue with creation
       of the assembly. 
  -->

  <DatasetType> </DatasetType>        <!-- See -dt_type argument -->
  <!–– The dataset type used for attaching the resulting assembly to the Item 
       revision. If this is not specified or the type is not found, the
       utility uses a default value based on the JtAssytType value. 
  -->

  <DatasetRelation> </DatasetRelation> <!-- See -dt_rel argument -->
  <!–– The dataset relation used for attaching the dataset to the Item 
       revision. 
  -->

  <LogFile> </LogFile>             <!-- See -log argument -->
	 <!–– LogFile identifies the complete path and the file name for the log  
      file the utility generates. 
  -->

  <UpdateType> </UpdateType>        <!-- See -assy_update argument -->
  <!–– UpdateType determines how to  attach the dataset to the Item revision. 
       If this is not specified, the utility replaces the named reference, 
       if one exists, with the dataset. 
  -->

  <TargetLoc></TargetLoc>
  <!–– TargetLoc specifies the path to the location on your operating system 
       where the utility saves the new JT assembly file.-->

  <CreateDataset> </CreateDataset>        <!-- See -de argument -->
  <!–– The valid values for CreateDataset are:
       n - creates a new dataset every time. 
       e - if the dataset already exists it does not revise it. If the dataset 
           does not exist it is create. 
       a - if the dataset already exists it revises it. If the dataset does not 
           exist it is created.
       r - revises the dataset if it already exists. If the dataset does not 
           exist an error is thrown.
       If this is not specified, the utility does not create a dataset. 
  -->

  <NamedRef> </NamedRef>        <!-- See -dt_ref argument -->
  <!–– The named reference used for uploading the assembly file to the dataset. 
       If this is not specified, the utility uses the default named reference 
       attached to the dataset type. 
  -->

<!–– End of JT file parameters ––> ⋮ <!–– Additional ParamSet elements for each set of JT file parameters are here in ––> <!–– End required root element ––> See Examples for a sample XML file listing. Note If an input XML file is specified, all other command line arguments (with the exception of the log on (-u, -p or -pf, and-g arguments) are ignored. -log Specifies the full path file name of the log file that stores PLM XML and load library errors. -rev Specifies the revision ID of the top line. If you do not include the -sc argument, this argument is required. -rev_rule Specifies the revision rule for configuring the assembly. -var_rule Specifies the variant rule for configuring the assembly. -tmode Specifies the name of the transfer mode. The transfer mode is not stored in the system but is created at run time. If you do not include this argument, the utility uses the default JTDataExportDefault transfer mode. -jt_type Specifies the type of assembly to be created. Valid values are: 1 A monolithic JT file is a single file containing all the graphics for a specific assembly. 2 An assembly JT file is an assembly file that contains pointers to other JT files, each representing a component in an assembly. 3 A CoJT file is for use with Tecnomatix eMServer only. If you do not specify this argument, the utility uses 1 (Monolithic JT). -pin Indicates whether to process intermediate nodes. Intermediate nodes are any nodes that are not leaf nodes. Valid values are: 0 Do not process intermediate nodes. 1 Process intermediate nodes. If you do not specify this argument, the utility uses 1 (process intermediate nodes). -cof Indicates whether to terminate assembly creation upon encountering errors. Valid values are: 0 Stop process when encountering an error. 1 Continue processing when encountering an error. If you do not specify this argument, the utility uses 1 (continue processing). -dt_type Specifies dataset type used for attaching the resulting assembly to the item revision. -dt_rel Specifies the dataset relation used for attaching the dataset to the item revision. -dt_ref Specifies the named reference used for uploading the assembly file to the dataset. If no named reference is given, the default named reference attached to the dataset type is used. -de Specifies the behavior of dataset creation. If you do not enter a value for this parameter, Teamcenter creates a JT file without an associated dataset. Valid value are: n Creates a new dataset. e Does not revise an existing dataset. If the dataset does not exist, it creates the dataset. a Revises an existing dataset. If the dataset does not exist, it creates the dataset. r Revises an existing dataset. If the dataset does not exist, it generates an error. -assy_update Specifies how the assembly JT is added to the dataset. create Assembly file is uploaded if no named reference is found in the dataset. replace Assembly file is always created and replaces the current named reference, if it exists. -skip_root_dset_with_name Prevents the utility from exporting the dataset of this name that is associated to the root node by an IMAN_Rendering relation. -skip_remote_lines Prevents the utility from exporting BOM lines that are not loadable. -Debug Turns on the debug mode that creates additional debug information files in the log file location. -h Displays help for this utility. Environment As specified in Setting up a Teamcenter command-line environment. Files As specified in Log files produced by Teamcenter. Restrictions None. Examples The following example is for an input XML file (robots.xml) that uses the StructureContext element and therefore does not require the ItemId, RevId, RevisionRule, VariantRule or Transfermode elements. The default Latest Working revision rule and JTDataExportDefault transfer mode are used. The default dataset type for a monolithic JT assembly is used to attach the dataset to the JT assembly because the DatasetType element is not specified: Copy CompoundTools 1 1 1 IMAN_reference c:\temp\monolithicJTUtility\logfile.log create c:\temp\monolithicJTUtility n JTPart <!–- uncomment this section to add additional JT file parameters ⋮ --> Use the following command to create the JT assembly using the robots.xml file: Copy assy_jt_creator -u=Tc-admin-user -p=password -g=group -i=robots.xml The following example shows the same command line version creating the same monolithic JT assembly shown in the previous XML file example. However, the command line version does not continue to create the assembly if an error is encountered during the process, does not revise the dataset if one exists, and uses a custom transfer mode. A debug file is also created in the log directory. The entire command must be entered on a single line. Copy assy_jt_creator -u=Tc-admin-user -p=password -g=group -sc=Robots -jt_type=1 -tar_loc=c:\temp\monolithicJTUtility -tmode=JTDataExportCustomTM -pin=1 -cof=0 -dt_rel=IMAN_reference -assy_update=create -de= -dt_ref=JTPart -debug Related Topics Manufacturing Process Planning ─ Usage