For connecting and communicating with NX models managed in local file system or Teamcenter, you will need to collect jar files from your NX installation. These jar files will be used with the Syndeia plugin. Follow the instructions in this section to collect these jar files.

Create a folder named libNX to collect the jar files needed for NX.
Go to the following location in your NX installation.
1. For NX 9 and 10, go to the UGII folder, e.g. C:\Program Files\Siemens\NX 10.0\UGII
2. For NX 11, go to the NXBIN folder, e.g. C:\Program Files\Siemens\NX 11.0\NXBIN
Copy the following 9 jar files from the folder location above to the libNX folder created in Step 1.
1. NXOpen.jar
2. NXOpenRemote.jar
3. NXOpenRun.jar
4. NXOpenUF.jar
5. NXOpenUFRemote.jar
6. NXOpenUFRun.jar
7. NXOpenUI.jar
8. NXOpenUIRemote.jar
9. NXOpenUIRun.jar
When NX is installed, a system variable named UGII_ROOT_DIR is setup as an environment variable whose value is the location of the UGII folder in your NX installation, as shown in LHS figure below. If this variable does not exist, go ahead and add it.
Add the following location to your PATH environment variable, as shown in the RHS figure above.
1. For NX 9 and 10, add the following string: %UGII_ROOT_DIR% to the PATH environment variable, as shown in the RHS figure above.
2. For NX 11 and above, add the location of the NXBIN folder (e.g. C:\Program Files\Siemens\NX 11.0\NXBIN) instead of %UGII_ROOT_DIR% to the PATH environment variable.

The instructions above are sufficient for Syndeia to interact with NX models in local file system.

If you want to access NX models in Teamcenter, you will need the Teamcenter 4-tier or 2-tier rich client installed on your machine. This is a requirement for Siemens NX CAD tool.

If you have a 4-tier rich client installed on your machine, follow the instructions - Accessing NX models in Teamcenter using 4-tier Teamcenter rich client

Alternatively, if you have a 2-tier rich client installed on your machine, follow the instructions - Accessing NX models in Teamcenter using 2-tier Teamcenter rich client

Browser not supported