NX Using NX Launcher ugii_env.dat is not read as per Environment definition.

2021-10-06T23:27:30Z
NX for Design

Summary


Details

Is using NX Launcher to start NX in NX Manager mode using only NX as UI for Teamcenter, (no RAC, No Active Workspace). Have 3 Environments defined in NX Launcher and have defined 3 different ugii_env.dat files to be used, one for each Environment.
How to get NX Launcher to read the expected ugii_env.dat when invoking NX?



Solution

The 3 different Environments in NX Launcher is defined as Cust_1, Cust_2 and Cust_3. The 3 different ugii_env.dat files are stored in a folder structure as follows:
D:\apps\PLM_x64\NX\nx_launcher\env\Cust_1\ugii_env.dat
D:\apps\PLM_x64\NX\nx_launcher\env\Cust_2\ugii_env.dat
D:\apps\PLM_x64\NX\nx_launcher\env\Cust_3\ugii_env.dat

In the OEM_Environment_def.xml you need to define a startup override. A typical entry would look like:
-------------------------------
<StartupOverrideList>
 <Override IsRun="true" Name="Custom Script"> <ScriptLocation>D:\workdir\NX\override.bat</ScriptLocation>
 </Override>
</StartupOverrideList>
-------------------------------

In order to read the expected ugii_env.dat based on choice of Environment in NX Launcher the content of the override.bat would look like:
------------------------------
@echo off
set UGII_ENV_FILE=D:\apps\pLM_x64\NX\nx_launcher\env\%UGII_CUSTOMER_ENV_NAME%\ugii_env.dat
exit /b 0
------------------------------
where UGII_CUSTOMER_ENV_NAME carries the Environment choice in NX Launcher.


The solution will of course also work if you run NX native.



Notes and References


Hardware/Software Configuration

Platform: INTL64
OS: windows
OS Version: 1064
Product: NX
Application: NXMANAGER
Version: V1872
Function: STARTUP

Ref: 001-9561836

KB Article ID# PL8015997

Contents

SummaryDetails

Associated Components

Teamcenter Integration for NX