<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>Managing Routing administrative files from Teamcenter</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic3" id="xps10_pagetitle">Managing Routing administrative files from Teamcenter</div>
      <hr noshade="true">
      <p class="para_topic">The Routing programs, Routing Electrical, Routing Mechanical, and Routing Logical, can import data contained in several non-.prt files into NX from Teamcenter. Teamcenter can be the central repository for all Routing information. Data files containing Routing information can be managed, revised, and imported from Teamcenter into NX like any other part file.</p>
      <p class="para_topic">The following Routing files can be managed by Teamcenter in addition to the NX part files:</p>
      <ul>
         <li>
            <p class="para_item">Application view (.xml)</p>
         </li>
         <li>
            <p class="para_item">Part Library view (.plv)</p>
         </li>
         <li>
            <p class="para_item">Part table (.ptb)</p>
         </li>
         <li>
            <p class="para_item">Routing Configuration (.cfg)</p>
         </li>
         <li>
            <p class="para_item">XML Schema viewer (.xsd)</p>
         </li>
         <li>
            <p class="para_item">Routing Component (.cmp)</p>
         </li>
         <li>
            <p class="para_item">Routing Harness (.hrn)</p>
         </li>
         <li>
            <p class="para_item">Format (.fmt)</p>
         </li>
         <li>
            <p class="para_item">Filter (.flt)</p>
         </li>
      </ul>
      <p class="para_topic">An NXRouting dataset type is available in the Teamcenter database in order to manage the above listed file types. This dataset should not manage the NX part files. The following named reference types are available in the NXRouting dataset type to represent non-NX part files.</p>
      <table cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="121*">
            <col span="1" width="128*">
            <col span="1" width="129*">
         </colgroup>
         <thead>
            <tr>
               <td align="center" bgcolor="silver" colspan="1" rowspan="1">
                  <p class="para_td">References</p>
               </td>
               <td align="center" bgcolor="silver" colspan="1" rowspan="1">
                  <p class="para_td">Files</p>
               </td>
               <td align="center" bgcolor="silver" colspan="1" rowspan="1">
                  <p class="para_td">Tool</p>
               </td>
            </tr>
         </thead>
         <tbody>
            <tr bgcolor="#f0f0f0">
               <td colspan="1" rowspan="1" valign="top">
                  <p class="para_td">NXRoutApplView</p>
               </td>
               <td colspan="1" rowspan="1" valign="top">
                  <p class="para_td">*.xml</p>
               </td>
               <td colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Text editor</p>
               </td>
            </tr>
            <tr bgcolor="#f0f0f0">
               <td colspan="1" rowspan="1" valign="top">
                  <p class="para_td">NXRoutPrtLibView</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">*.plv</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Text Editor</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">NXRoutPrtTable</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">*.ptb</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Text Editor</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">NXRoutConfiguration</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">*.cfg</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Text Editor</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">NXRoutXMLSchema</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">*.xsd</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Text Editor</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">NXRoutComponent</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">*.cmp</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Text Editor</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">NXRoutHarness</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">*.hrn</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Text Editor</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">NXRoutFormat</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">*.fmt</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Text Editor</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">NXRoutFilter</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">*.flt</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Text Editor</p>
               </td>
            </tr>
         </tbody>
      </table><br><div class="title_division">Creation of NXRouting datasets</div>
      <p class="para_division">Routing administrators should create NXRouting datasets and associate all routing files as named references of these datasets. The specific requirements for each dataset is given below.</p>
      <table cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="112*">
            <col span="1" width="137*">
         </colgroup>
         <thead>
            <tr>
               <td align="center" bgcolor="silver" colspan="1" rowspan="1">
                  <p class="para_td">Dataset</p>
               </td>
               <td align="center" bgcolor="silver" colspan="1" rowspan="1">
                  <p class="para_td">Requirements</p>
               </td>
            </tr>
         </thead>
         <tbody>
            <tr bgcolor="#f0f0f0">
               <td colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Application View files (.xml)</p>
               </td>
               <td colspan="1" rowspan="1" valign="top">
                  <p class="para_td">The dataset should be named &ldquo;Application View&rdquo;. The value of the variable defining the application view file in ugii_env.dat should be the name of the item containing the &ldquo;Application View&rdquo; dataset in Teamcenter</p>
               </td>
            </tr>
            <tr bgcolor="#f0f0f0">
               <td colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Part Library View (.plv)</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">The dataset shoul dbe named &ldquo;Part Library View&rdquo;. The value of the variable UGII_EPLIB_PART_LIB_VIEW_PATH in ugii_env.dat should be the name of the item containing the &ldquo;Part Library View&rdquo; dataset in Teamcenter.</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Part Table (.ptb)</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">The dataset shoul dbe named &ldquo;Routing Part Tables&rdquo;. The value of the variable UGII_EPLIB_TABLE_PATH in ugii_env.dat should be the name of the item containing the &ldquo;Routing Part Tables&rdquo; dataset in Teamcenter.</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Routing Configuration file (.cfg)</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">The dataset and the item containing it should be named &ldquo;Routing Configuration&rdquo;.</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">XML schema viewer file (.xsd)</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">The dataset should be named &ldquo;XML Schema File&rdquo; and the item containing it in Teamcenter should be named &ldquo;XML Schema View&rdquo;.</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Routing Component file (*.cmp)</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">The dataset should be named &ldquo;Routing Component View&rdquo; and should be present under the item selected when importing component files from Teamcenter.</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Routing Harnes file (*.hrn)</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">The dataset should be named &ldquo;Routing Harness View&rdquo; and should be present under the item selected when importing harness files from Teamcenter.</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Format files (*.fmt)</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">The dataset should be named &ldquo;Routing Format&rdquo; and should be present under the item selected when importing format files from Teamcenter.</p>
               </td>
            </tr>
            <tr>
               <td bgcolor="#F0F0F0" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">Filter files (*.flt)</p>
               </td>
               <td bgcolor="#F4F4F4" colspan="1" rowspan="1" valign="top">
                  <p class="para_td">The dataset should be named &ldquo;Routing Filter&rdquo; and should be present under the item selected when importing filter files from Teamcenter.</p>
               </td>
            </tr>
         </tbody>
      </table><br><div class="title_division">Accessing NXRouting datasets</div>
      <p class="para_division">To access .xml, .plv, .ptb, .cfg, and .xsd files the value of the environment variable UGII_ROUTE_UGMANAGER_MODE in ugii_env.dat should be set to TRUE, indicating that the Routing Administrative files are to be loaded from Teamcenter. If set to FALSE, the files will be loaded by looking for appropriate files in theNX file system installation. The files will be searched only at one place, such as, in either Teamcenter or the NX file system installation. An error will be raised if they are not found.</p>
      <p class="para_division">For accessing .cmp, .hrn, .flt, or .fmt files from Teamcenter, the Routing Electrical preference <b class="uiTerm">Import Data From Teamcenter Integration</b> should be turned on. This will allow you to import these files using <b class="uiTerm">File&rarr;Open</b> from Teamcenter.
      </p>
   </body>
</html>