Multi-NX Administators Guide

1 Creating a new Multi-NX installation

Multi-NX can be run from any internal or external hard disk with sufficient capacity to store all needed
versions. It's then only accessible from this one machine. The Multi-NX directory must be shared in
order for users to access it from the local network.

NOTE: Multi-NX is fully compatible with 64-bit NX but this will require a 2nd Multi-NX configuration.

1.1 Create and share the main directory

Create a directory called “MultiNX” (for 32-bit NX) or “MultiNX64” (for 64-bit NX), preferably as a root-
directory. Share this directory by granting domain-groups access, only ‘read’ access is required and
preferred. For 64-bit version of NX create a directory called “MultiNX64”.

1.2 Unzip the “Multi-NX” package

Download the Multi-NX package from this link and save it in the “MultiNX” directory that was just
created. Extract it using the “extract here” option. The “MultiNX.zip” file can be deleted. The directory
structure should now look like Figure 1. Please allow for changes that were made after this document
was written.

Figure 1

The root directory contains all required files and directories. Refer to chapter 2for more details.

1.3 Configuring Multi-NX

The configuration of Multi-NX is really simple. Update the MNX_HOST, MNX_UGII_LICENSE_FILE and
MNX_UGS_LICENSE_SERVER settings in the “config.ini” file. For 64-bit Multi-NX configurations the
setting MNX_64BIT_NX must be changed to “yes”. All settings include a short description that explains
their function.

Author: Marco van Malsen Page 1 of 7 Last saved on: 3-Dec-2009

 Multi-NX Administators Guide

2 Important files and directories

Please refer to Figure 1.

2.1 Start_NX.bat
Basically Multi-NX is a huge batch file. Start this batch to launch the Multi-NX program. Please do not
edit this file directly or without making a backup first. Please feel free to report any suggestions (ER) or
problems (PR) to me at marco.vanmalsen@siemens.com.

The batch, like any other, uses environment variables. There are two groups, variables that are required
for NX (Manager) and those that are needed by Multi-NX to do its job. The variables from this last group
are unset before starting the selected program.

2.2 Config.ini
This file contains the basic configuration parameters for Multi-NX. The file itself contains basic
information about the preferences being set in it.

2.3 Database.ini
This file contains configuration settings to start NX/Manager sessions. The values from the SID and
SERVER columns are used by Multi-NX to define the FMS_HOME setting.

2.4 Create_Shortcut_on_Desktop.bat
This batch will create a shortcut to Multi-NX on the desktop of the user running it.

2.5 Install_new_Maintenance_Release_or_Pack.bat
This batch can be used to add a new Maintenance Release or Maintenance Pack. Please refer to chapter
5 for further instructions.

Author: Marco van Malsen Page 2 of 7 Last saved on: 3-Dec-2009

 Multi-NX Administators Guide

3 Adding a new NX version

Please follow these steps to add a new (base) version to Multi-NX:
Install the base version of NX including the documentation on any machine.
Create the directory structure shown below underneath the Multi-NX root-directory

Copy all files and directories from your own NX installation into the lowest folder.
Move the “REL_INFO” and “UGDOC” directories underneath the main NX version directory:

Author: Marco van Malsen Page 3 of 7 Last saved on: 3-Dec-2009

 Multi-NX Administators Guide

4 Adding C.A.S.T. to Multi-NX

Please follow these steps to add C.A.S.T. to Multi-NX:

Install C.A.S.T. on any machine.

Create a “CAST” directory underneath the main NX directory and copy all the C.A.S.T. files. The
result should look like the figure below.

4.1 Installing a C.A.S.T. update

Simply start the C.A.S.T. patch executable follow the instructions, but refer to the “CAST” directory
underneath the main NX directory in the Multi-NX directory structure.

Author: Marco van Malsen Page 4 of 7 Last saved on: 3-Dec-2009

 Multi-NX Administators Guide

5 Add Maintenance Release/Pack

The “Install_new_Maintenance_Release_or_Pack.bat” batch was created to easily facilitate adding a
new Maintenance Release/Pack.

NOTE This batch must be run on the machine hosting Multi-NX.

After starting the batch, it will first ask for the NX version, the Maintenance Release and Maintenance
Pack for the NX version that has to be added.

NOTE To add a new Maintenance Release, enter 0 (zero) for the Maintenance Pack version.

The last question is a request to drag-and-drop the zip archive to the DOS-box. After entering this
information the following will happen:
Copy the directory from the previous version to a temporary directory. This is a temporary
directory so that users cannot accidentally use the version that is being added.
o Adding a new Maintenance Release. The base version will be used if available; otherwise
a search is done for the most recent Maintenance Release.
o Adding a new Maintenance Pack. The Maintenance Release will be used if available;
otherwise the most recent Maintenance Pack will be used.
o An error is reported when a usable directory is not found.
Unzip the archive to directory named “install” in the Multi-NX root-directory.
Search for the “ugs_update.bat” batch and append the “EXIT” command at the end.
Move the REL_INFO and UGDOC directories from underneath the main NX directory into the
temporary directory. (Maintenance Release only)
Run the “ugs_update.bat” batch with the “/D” parameter, so it runs without prompting.
Move the REL_INFO and UGDOC back their original location. (Maintenance Release only)
Rename temporary directory to correct name.
Delete directory that was used to extract the Maintenance Release/Pack archive to.

Author: Marco van Malsen Page 5 of 7 Last saved on: 3-Dec-2009

 Multi-NX Administators Guide

6 Adding support for NX/Manager (Teamcenter)

Documentation to be updated!!

Author: Marco van Malsen Page 6 of 7 Last saved on: 3-Dec-2009

 Multi-NX Administators Guide

7 Naming convention
The Multi-NX tool depends on a naming convention in order to be maintenance free.

NOTE The Multi-NX tool is not designed nor tested for whitespaces in directory names!!

The naming convention rules:

The 1st level directory name must start with “NX” followed by a one digit identifying the NX
version.
The 2nd level directory name begins with the name of its parent directory followed by a “0” and
one digit identifying the NX Maintenance Release.
The 3rd level directory name begins with the name of its parent directory followed by a
underscore “_” and 2 digits identifying the NX Maintenance Pack. In addition to this the name
can be extended allowing ‘custom’ text to be displayed. This is designed to allow for customer
hot-fixes.

Typical examples of 1st level directories:

NX1 Unigraphics NX1
NX5 NX 5
NX6 NX 6

Typical examples of 2nd level directories:

NX403 NX 4.0.3.3 (NX 4, Maintenance Release 3)
NX501 NX 5.0.1.2 (NX 5, Maintenance Release 1)

Typical examples of 3nd level directories:

NX403_03 NX 4.0.3.3 MP3
NX501_01 NX 5.0.1.2 MP1

Since customer patches are build on an existing Maintenance Release / Pack the following names allow
to add customer specific patches:
PR#1111111 hot-fix for NX4.0.3.3 MP3
NX403_98NX4.0.3.3_MP3_Customer1_PR1111111
(Customer 1)
PR#9999999 hot-fix for NX4.0.3.3 MP4
NX403_99NX4.0.3.3_MP4_Customer2_PR9999999
(Customer 2)

Please note that two characters reserved for Maintenance Pack information have been replaced by “98”
and “99, setting them apart from “regular” Maintenance Packs.

Author: Marco van Malsen Page 7 of 7 Last saved on: 3-Dec-2009