<!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>Installation</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">Installation</div>
      <hr noshade="true">
      <p class="para_topic">To access I-deas library parts and assemblies from within NX, the I-deas data installation must be accessible and properly configured in NX. If NX cannot connect to the I-deas server, then all NX menus and buttons that access I-deas library data will be insensitive or not available. </p>
      <div class="title_division">Set up the NX to I-deas Connection</div>
      <p class="para_division">There are two ways in which the NX to I-deas connection can be established, depending on whether the server and client share a common file system. </p>
      <div class="title_division">Separate File System Setup</div>
      <p class="para_division">This method is now the preferred method of installation.</p>
      <p class="para_division">Use the connection mechanism setup if the client and the server are on separate file systems. This method also works if the client and server are on the same file system, or even if they are the same machine. In all of these cases, this is still the preferred method of connecting NX and I-deas. </p>
      <p class="para_division">An application called ug_ideas_connector.exe is provided to facilitate the connection to the I-deas server from  NX. This application will be located in the \Ugs directory of the I-deas installation. The following initial setup needs to be performed on the NX client side and the I-deas server side.   </p>
      <div class="title_division">I-deas server side setup</div>
      <p class="para_division">I-deas has a standard program file called userprof.prg that is automatically run when I-deas is started. This file needs to be either in the I-deas installation directory or the I-deas launch directory.  In the \Ugs directory of the I-deas installation a sample  userprof.prg program file is provided for Windows and UNIX. This program file contains the command required to launch the  ug_ideas_connector application. Users need to place this program file in either of the locations specified above. If users already have a  userprof.prg file of their own then they need to merge the commands specified in this sample file into their  userprof.prg file.  Alternatively, an administrator can simply issue the oaxx command when starting the I-deas session that will support the NX to I-deas connection: oaxx execute %SDRC_INSTL%\UGS\ug_ideas_connector.exe (Windows sessions)   oaxx execute $SDRC_INSTL/UGS/ug_ideas_connector.exe (unix sessions). This does not require any userprof.prg manipulation, but must be done each time.</p>
      <div class="title_division">NX client side setup</div>
      <p class="para_division">On the NX client side users need to set the  UGII_INOP_SERVER_HOST environment variable to the name of the host machine on which the I-deas server is running. There must be a running session of I-deas waiting to take the commands from the OI server. The machine name here is the machine that the I-deas session is running on, and the 'server' is the OI server (not the software server or the TDM server), which corresponds to that session's machine.</p>
      <div class="title_division">Common file System Setup</div>
      <p class="para_division">This is an older method, and is no longer recommended. It is only listed here to support sites that may still use this method.</p>
      <p class="para_division">Use this connection mechanism only if the client and the server share a common file system. </p>
      <p class="para_division">In this connection mechanism users are provided with scripts that can be run automatically and will write to disk a file called  UgIdeasInterop.ior. This file then needs to be referenced on the client side via an environment variable. The following initial setup steps need to be performed on the NX client side and the I-deas server side.  </p>
      <div class="title_division">I-deas server side setup</div>
      <p class="para_division">A batch file (UgIdeasIORGenerator.bat) for Windows and a shell script (UgIdeasIORGenerator.sh) for UNIX is provided in the \Ugs directory of the I-deas installation. Using the  userprof.prg file these scripts can be executed automatically whenever I-deas is launched. When the script is executed it will write a file called  UgIdeasInterop.ior. This file is written to the I-deas startup directory by default. Users can change the default location by setting the environment variable  UGII_INOP_IOR_DIR_PATH to the desired directory path. </p>
      <div class="title_division">NX client side setup</div>
      <p class="para_division">On the NX client side users need to set the environment variable  UGII_INOP_SERVER_IOR_FILE to the location of the  UgIdeasInterop.ior file on the I-deas Server. Specify the full path, including the filename.</p>
      <div class="title_division">Variables and Parameters</div>
      <p class="para_division">There are several environmental variables in NX and parameters in I-deas that control the transfer process and feature behavior. Because these settings should be set site-wide, the administrator must set these values for the users. No control over these settings is provided in the software. </p>
      <div class="title_division">NX Variables</div>
      <p class="para_division">UGII_INOP_SERVER_HOST </p>
      <p class="para_division">Set UGII_INOP_SERVER_HOST='hostname' to define the I-deas server host machine name. </p>
      <p class="para_division">This represents the machine that the I-deas session is running on, not the team server or software server or something else.</p>
      <p class="para_division">UGII_IDEAS2UG_AUTO_UPDATE_CHECK</p>
      <p class="para_division">Set UGII_IDEAS2UG_AUTO_UPDATE_CHECK=ON to check TDM (I-deas Team Data Manager) for out-of-date status. (ON=default.) UGII_INOP_SERVER_HOST must be set up also.</p>
      <p class="para_division">UGII_IDEAS2UG_UPDATE_FROM_LATEST</p>
      <p class="para_division">Set UGII_IDEAS2UG_UPDATE_FROM_LATEST=ON to enable 'update to latest' buttons on forms. (ON=default.) UGII_INOP_SERVER_HOST must be set up also. Turning this option on may slow performance.</p>
      <p class="para_division">UGII_INOP_AUTO_HEAL_GEOMETRY</p>
      <p class="para_division">Set UGII_INOP_AUTO_HEAL_GEOMETRY=TRUE to automatically heal geometry on import. (TRUE=default.)</p>
      <p class="para_division">UGII_INOP_AUTO_CHECK_GEOM_FIDELITY</p>
      <p class="para_division">Set UGII_INOP_AUTO_CHECK_GEOM_FIDELITY=TRUE to automatically check fidelity on import. If fidelity data doesn't exist in the file (for example if an older .xpk file is being imported), the user will receive a warning message. (FALSE=default.)</p>
      <div class="title_division">I-deas Parameters</div>
      <p class="para_division">You must be defined the following I-deas parameters to use some of the new functionality of this release of interoperability. These can be defined in the users param file or in a site-wide ideas_param file.</p>
      <p class="para_division">de.uirelease.rrtm: 1</p>
      <p class="para_division">This parameter must be defined to turn on the new user interface features. If this parameter is not turned on, the Update from NX icon will not be available on the Manage Bins form. (Default = 0 or not defined.)</p>
      <p class="para_division">mm.interoperability.healing.off: 0 or 1</p>
      <p class="para_division">If this parameter is set to 1, I-deas will skip the step of healing surfaces before exporting the data. You should define this variable only if you want to manually control the healing process within NX instead of letting I-deas perform this step automatically. (Default = 0 or not defined.)</p>
      <p class="para_division">mm.interoperability.fidelity.on: 0 or 1</p>
      <p class="para_division">If this parameter is turned on, I-deas will generate and store fidelity checking data in the interoperability .xpk files. This parameter is normally left off (or undefined), since healing is done by default before export, and most users won't need this fidelity checking data. Writing this data will increase the size of the file. </p>
      <p class="para_division">This parameter also turns on fidelity checking, which is performed when NX files are opened in I-deas. (Default = 0 or not defined.)</p>
      <div class="title_division">Recommended variable and parameter settings</div>
      <p class="para_division">Typical users</p>
      <p class="para_division">Most sites should set the variables and parameters described above at the default values mentioned. This setup is for companies that want geometrically consistent models but do not require reports on the fidelity of the imported data. This setup will emulate the interoperability behavior of previous releases. The geometry is healed in the sending system and no fidelity data is included in the exchanged model. No checks are performed in the receiving system.</p>
      <ul>
         <li>
            <p class="para_item">UGII_INOP_AUTO_HEAL_GEOMETRY=TRUE</p>
         </li>
         <li>
            <p class="para_item">UGII_INOP_AUTO_CHECK_GEOM_FIDELITY=FALSE </p>
         </li>
         <li>
            <p class="para_item">de.uirelease.rrtm: 1 </p>
         </li>
         <li>
            <p class="para_item">mm.interoperability.healing.off: 0 </p>
         </li>
         <li>
            <p class="para_item">mm.interoperability.fidelity.on: 0 </p>
         </li>
      </ul>
      <p class="para_division">Fidelity users</p>
      <p class="para_division">For sites that want to actively exert a higher level of control over the healing process and fidelity checking where surface accuracy is critical, the following settings are recommended. </p>
      <p class="para_division">This setup is for companies that wish to guarantee the surface and curve fidelity of the imported data. This set of variables configures the sending and receiving applications to maintain the geometry exactly. This can occasionally result in inconsistent geometry being imported; but it is exact. The model contains fidelity data (sample points from the sending system) that enables the user to verify the fidelity of the imported data.</p>
      <p class="para_division">A model that contains inconsistent geometry can still be visualized and used within modelling operations, but some downstream operations that rely on the model region where there are inconsistencies may result in modeling failures.</p>
      <ul>
         <li>
            <p class="para_item">UGII_INOP_AUTO_HEAL_GEOMETRY=FALSE</p>
         </li>
         <li>
            <p class="para_item">UGII_INOP_AUTO_CHECK_GEOM_FIDELITY=TRUE </p>
         </li>
         <li>
            <p class="para_item">de.uirelease.rrtm: 1 </p>
         </li>
         <li>
            <p class="para_item">mm.interoperability.healing.off: 1 </p>
         </li>
         <li>
            <p class="para_item">mm.interoperability.fidelity.on: 1 </p>
         </li>
      </ul>
      <table border="0">
         <tr>
            <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
            <td valign="bottom" align="left" width="100%">
               <div class="para_note">
                  <p class="para_note_body"> For information on the I-deas installation, see the <em>I-deas Installation Guide</em> or the  <em>General I-deas Administration</em> user's guide. (The latter can be found in the I-deas online help library.)
                  </p>
                  <p class="para_note_body">For help with the installation procedures or accessing required files, contact the GTAC support system.</p>
               </div>
            </td>
         </tr>
      </table>
   </body>
</html>