<!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>Routing administration</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_topic2" id="xps10_pagetitle">Routing administration</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('routingadmin/team_overview.html');return(false);">Overview</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('routingadmin/team_views.html');return(false);">Options</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Related Topics</p>
            </td>
         </tr>
      </table><br><p class="para_topic">Some configuration is necessary to use <b class="uiTerm">Classification</b> and Routing together.
      </p>
      <div class="title_division">Plug-in definition</div>
      <p class="para_division">The <b class="uiTerm">Plug-ins</b> group of the example <b class="uiTerm">XML Application View</b> (APV) file registers the plug-in when loading the Routing application, as follows:
      </p>
      <div class="figure">
         <p align="left"><img align="bottom" src="graphics/plugin_ex.gif"></p>
      </div>
      <div class="title_figure">Example</div>
      <div class="title_division">Setting up Part Library View (PLV)</div>
      <p class="para_division">The <b class="uiTerm">Part Library</b> group of the XML APV file must be modified to use the plug-in.
      </p><pre class="indent">&lt;Part_Library&gt;
  &lt;Part_Library_plugin/&gt;
&lt;/Part_Library&gt;</pre><p class="para_division">Note that when using <b class="uiTerm">Classification</b>, the <b class="uiTerm">Part Library View</b> (PLV) file and <b class="uiTerm">Part Table</b> (PTB) files are not used. The part selection hierarchy, otherwise defined by the PLV and the part characteristic assignments, otherwise made through the PTB files, are derived from the Classification structure when Teamcenter <b class="uiTerm">Classification</b> is used.
      </p>
      <div class="title_division">ITK program</div>
      <p class="para_division">Install the ITK program that connects to the classification server. The ITK program (<b class="commandName">route_inclass_itkl.exe</b>) is executed by the Routing Plug-in when loading the application. A wrapper script must be called to setup the correct Teamcenter  environment variables before executing the ITK program. The wrapper script, <b class="commandName">route_inclass_itk.bat</b>, performs this function. These files must be executed from the ZIP file <code>Inclass_Programs.zip</code> provided in the folder %UGII_BASE_DIR%\ugroute_mech\plugins.
      </p>
      <div class="title_division">Environment variables</div>
      <p class="para_division">Add the environment variable UGII_ROUTING_INCLASS_PROG to the <code>ugii_env.dat</code> file, so that it points to the ITK wrapper script. In addition, the environment variable UGII_ROUTING_INCLASS_ROOT environment variable should be added to the wrapper script. The UGII_ROUTING_INCLASS_ROOT variable specifies the root classification node for Routing. If this variable is not set then the root classification node is used, resulting in the entire classification hierarchy being used.
      </p>
      <p class="para_division">Example (in ugii_env.dat):</p>
      <p class="para_division"><b class="commandName">UGII_ROUTING_INCLASS_PROG=$(UGII_BASE_DIR)\ugroute_mech\route_inclass_itk.bat</b></p>
      <p class="para_division">Example (in route_inclass_itk.bat):</p>
      <p class="para_division"><b class="commandName">UGII_ROUTING_INCLASS_ROOT=Routing</b>.
      </p>
      <div class="title_division">Discipline start nodes</div>
      <p class="para_division">Add Routing Disciplines through the APV file (refer to <a class="links" href="javascript:void(0)" onclick="top.openFile('routingadmin/apv_disciplines.html');return(false);">APV file, Disciplines</a> topic). When addition Disciplines, specify the Start_Stock_Node and Start_Fitting_Node elements to point to the desired node in <b class="uiTerm">Classification</b>. The node is the group ( class) identifier, not the group name. In Figure 4, the class identifier is HPT_Fittings, which is the value to use in the Start_Fitting_Node if it is the desired starting node.
      </p>
      <p class="para_division">Each discipline may have a different start stock and fitting node. This allows Routing to show only those stocks and fittings appropriate to that discipline for user selection.</p>
      <div class="title_division">Limitations</div>
      <p class="para_division">There are limitations on the types of <b class="uiTerm">Classification</b> data that are supported. Arrays and Date attributes do not work. In addition, the subclass object in <b class="uiTerm">Classification</b> does not work very well. The subclass object available under <b class="uiTerm">Add View</b> should not be used.
      </p>
      <p class="para_division">There is some functionality that is missing in Teamcenter 8.1.1.4 and 8.1.1.5 that does not allow ITK programs to read classification attributes that are not visible in the view. The impact of this is that you must specify views that contain all of the attributes in the class, with the searchable attributes ordered at the top (for your convenience).</p><a class="endOfDocLinks" href="manage_team.html">Managing Routing administrative files from Teamcenter</a><br></body>
</html>