Cancel
Showing results for 
Search instead for 
Did you mean: 

Windows and Linux NX/Tc issues?

Gears Phenom Gears Phenom
Gears Phenom

Has anyone had issues running some windows, and some linux workstations, both using NX and the same Teamcenter database?

 

Using NXcustom for a common setup across the company, is the only issue I can see.

 

Thanks,

 Dave

-Dave
NX 11 | Teamcenter 11 | Windows 8.1
9 REPLIES

Re: Windows and Linux NX/Tc issues?

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

What kind of issues?

 

Only thing I can think of is if ENVs in the NXcustom are defined for the "other" OS and not correctly translated.

e.g. UGII_XXX_ENV=${WHEREVER}\Folder\subfolder

 

and unix wants "/" not "\"?

 

Or case sensitivity of unix?

 

I know there's a mapping file for assemblies, but you're running TC so that's not the issue here.

 

Maybe export a syslog from both OS & compare them?

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP16/TC11.2
I'd rather be e-steamed than e-diseaseled


Re: Windows and Linux NX/Tc issues?

Gears Phenom Gears Phenom
Gears Phenom

yeah, I guess since all of the custom stuff is on a network server, it wouldn't matter, other than any path's that are called out in the files.

 

Ditto for the .bat file that launches NX, the paths ( \ vs. / ) in that would have to be different for the Linux machines...I would assume.

 

Going thru the customer defaults, it looks like we would have to define and maintain 2 sets of Printer(plotters) for each OS.  Same with Journals and macros if those are used...those are pretty obvious as you go the the Customer Defaults.

 

 

-Dave
NX 11 | Teamcenter 11 | Windows 8.1

Re: Windows and Linux NX/Tc issues?

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Note the ENV file has #if constructs for operating system, so you could maintain one ENV file and just define everything one way or the other. 

 

Macros that refer to OS files (e.g. pull in a CDF - color definition file) - you're screwed.  You need separate macros for each OS (note you could put them in separate folders with the same name for each macro, then use UGII_INITIAL_MACRO_DIR to point to the right place, which may save you some work editing TBR and RBN files.)

 

Journals are easier (except VB journals don't run on unix?) But if you convert to ?Java or Python? they should be able to be made to work (check the OS and build file specs accordingly)

 

Basically, (except for macros) try to get all ll filespecs defined in ENV variables, then use them instead of paths, should minimize the differences.

 

Ken

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP16/TC11.2
I'd rather be e-steamed than e-diseaseled


Re: Windows and Linux NX/Tc issues?

Gears Phenom Gears Phenom
Gears Phenom

So we can expand upon this:

 

# Determine 32-bit or 64-bit OS
#if x64wnt
NX_ARCH=win64
#else
NX_ARCH=win32
#endif

and have it check for a linux os, and then #if #else for any paths later on in the file.

 

Sounds like this mix of OS would be tolerable, especially since it would only be a couple workstations for a specific group that needs linux.

 

Thanks

-Dave
NX 11 | Teamcenter 11 | Windows 8.1

Re: Windows and Linux NX/Tc issues?

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Yes.

This is documented in the release notes. (system info -> platforms -> NX variables in the ugii_env.dat file)

Ken Akerboom Sr CAx Systems Engr, Moog, Inc.
Production: NX10.0.3.5 MP16/TC11.2
I'd rather be e-steamed than e-diseaseled


Re: Windows and Linux NX/Tc issues?

Gears Phenom Gears Phenom
Gears Phenom

Thanks, I forgot about the release notes, I was looking the help files.

 

So something like this, for the various paths should do it

 

#if lnx64
UGII_TABLE_TEMPLATES=${NX_CUSTOM_LIB}/Tables
#else
UGII_TABLE_TEMPLATES=${NX_CUSTOM_LIB}\Tables
#endif
-Dave
NX 11 | Teamcenter 11 | Windows 8.1

Re: Windows and Linux NX/Tc issues?

Phenom
Phenom

Or just do one #if #else #endif at the start of the file to define a path separation character:

#if lnx64
PATH_SEPARATOR=/
#else
PATH_SEPARATOR=\
#endif

UGII_TABLE_TEMPLATES=${NX_CUSTOM_LIB}{PATH_SEPARATOR}Tables

As long as the paths are the same this cuts down on a lot of editing.

Graham Inchley Snr R&D Engineer (Systems Development), Sandvik Coromant
Lenovo ThinkPad W540, Win7, 16GB. Developing in: Java | C | KF
Production: [NX8.5.3.3 MP11 64bit] Testing: [NX12.0.0.27 MP1]

Re: Windows and Linux NX/Tc issues?

Phenom
Phenom

Not sure if it works with NX env files. 

In some cases Windows will accept a forward slash as a path separator

I just tested this in windows 7

C:\Users\alexg>cd /temp

C:\Temp>

c:\>set test=c:/temp

c:\>cd %test%

c:\Temp>

Re: Windows and Linux NX/Tc issues?

Gears Phenom Gears Phenom
Gears Phenom

Thanks.  For now it looks like linux is not going to happen for these people, but I'm saving all these ideas, just in case.

 

Thanks again!

-Dave
NX 11 | Teamcenter 11 | Windows 8.1