Recently I was asked by a customer about saving JT files for weldment parts, in which SolidWorks replaces the usual Default configuration with its own Default<As Machined> configuration. The Administration guide does state that the file_name tag is available for use with the JT auxiliary file map, but does not provide a working example.
The weldment part scenario actually spans two configuration points, because (a) the integration must be informed that Default<As Machined> is a valid master configuration, and (b) the integration must be aware that the JT translator will generate a JT file with a compound and sanitized file name.
The first requirement is easily handled by adding Default<As Machined> to the sw.configurations.masters preference, in swim.properties:
The second requirement calls for special configuration of the JT file map, in swim.xml. In the OOTB client installation, it is condensed to this:
<jt_file action="translate" cad_type="sldprt:sldtbx" eai_dir="C:\apps\swjt"/>
which only works when the JT file name (minus extension) exactly matches the name of the CAD model being translated. In the case of a weldment part, the JT file is both extended to include the name of the .sldprt or .sldasm file, and it is santized to remove the < and > characters, which, interestingly, are used by SolidWorks, which runs only on Windows, but are not accepted by Windows as legal file name characters. For example, given a weldment part that looks like this in SolidWorks:
the JT translator will write a file like this to disk:
This JT file does not even come close to matching the CAD model name, and so the integration cannot recognize and save it to Teamcenter, without additional configuration.
The solution is to add a 2nd JT file map, with a file name pattern, while preserving the OOTB map that handles non-weldment default configurations. The required entries look like this:
The first map handles JT files with a standard Default configuration, while the second map is specific to weldment parts that have a Default<As Machined> configuration. Other non-standard master configurations can be managed with additional JT auxiliary file maps.