NX Remote Manager Guide - Help!help.aviacons.ru/.../en_US/tdocExt/pdf/nx_remote_manager.pdfChapter 2 ConfiguringNX Remote Manager ConfiguringNXRemoteManager NX Remote Manager functionality

Teamcenter 10.1

NX Remote Manager Guide

Publication NumberPLM00123 G

Proprietary and restricted rights notice

This software and related documentation are proprietary to Siemens ProductLifecycle Management Software Inc.

© 2013 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.

Siemens and the Siemens logo are registered trademarks of Siemens AG. Teamcenteris a trademark or registered trademark of Siemens Product Lifecycle ManagementSoftware Inc. or its subsidiaries in the United States and in other countries. Allother trademarks, registered trademarks, or service marks belong to their respectiveholders.

2 NX Remote Manager Guide PLM00123 G

Contents

Proprietary and restricted rights notice . . . . . . . . . . . . . . . . . . . . . . . . . 2

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1NX Remote Manager interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Basic concepts about NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Configuring NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Configuring NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Enable NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Enabling automatic archiving of exported files . . . . . . . . . . . . . . . . . . . . . . . 2-1Enable batch import/export on a personal workstation . . . . . . . . . . . . . . . . . . 2-2Enable batch import/export on a remote workstation . . . . . . . . . . . . . . . . . . . 2-2Enable e-mail notification of batch import/export completion . . . . . . . . . . . . . 2-2Guidelines for part naming when using NX Remote Manager . . . . . . . . . . . . . 2-2

Using NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Using NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Establish a remote export connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Send data to an existing connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Adding datasets to a remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Manually export data to a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Refresh files in a remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Importing files from a remote connection to Teamcenter . . . . . . . . . . . . . . . . . 3-5Set connections options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Delete a remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9View transaction logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Importing and exporting assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Importing and exporting assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1How Teamcenter imports and exports assemblies . . . . . . . . . . . . . . . . . . . . . 4-1Data manager tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Export assemblies with BOM information . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Exporting without BOM information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Importing data from a remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

NX Remote Manager administration . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

NX Remote Manager administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Register custom item types with NX Remote Manager . . . . . . . . . . . . . . . . . . 5-1Preferences and utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

PLM00123 G NX Remote Manager Guide 3

Contents

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

4 NX Remote Manager Guide PLM00123 G

Chapter

1 Getting started

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

NX Remote Manager interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1NX Remote Manager buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Basic concepts about NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Export rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Analysis results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Batch export and file archival . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

PLM00123 G NX Remote Manager Guide

Chapter

1 Getting started

Getting startedNX Remote Manager provides the ability to share data between customers andsuppliers using My Teamcenter to import and export data to directories that canbe accessed by users outside of the Teamcenter environment. In addition, youcan use NX Remote Manager to work offline and then synchronize data with theTeamcenter database.

Before you beginPrerequisites • NX Remote Manager only works in the Teamcenter two-tier

architecture. It does not work in the four-tier architecture.

• NX and Teamcenter Integration for NX must be installed onthe same machine as the Teamcenter server.

Enable NXRemoteManager

NX Remote Manager must be enabled before you use it.

For more information, see Enable NX Remote Manager.

ConfigureNX RemoteManager

NX Remote Manager must be configured.

For more information, see Configuring NX Remote Manager.

NX Remote Manager interfaceThere is no separate interface for NX Remote Manager. Features are accessed usingNX Remote Manager menus in My Teamcenter.

NX Remote Manager buttons

Button DescriptionExport to connection Exports datasets to an active application

encapsulation session.

Import fromconnection

Imports datasets from an applicationencapsulation session.

PLM00123 G NX Remote Manager Guide 1-1

Chapter 1 Getting started

Button Description

Delete failedconnection

Deletes failed connections from theTeamcenter database.

Display connectionlog

Displays the transaction log for aconnection.

Basic concepts about NX Remote ManagerNX Remote Manager allows you to share files with remote users who have no accessto the Teamcenter database. Data is exported, and after modifications are made, thedata is imported back in to Teamcenter.

1 Teamcenter client

2 NX Remote Manager

3 Remote application users

4 Supplier site

5 Teamcenter server

1-2 NX Remote Manager Guide PLM00123 G

Getting started

6 Remote individual user

NX Remote Manager uses export directories to manage the connections usedto import and export data. Files that are explicitly checked out for the currentconnection are exported with read-write permission. Files that are not explicitlychecked out are exported as read-only reference files.

When you import files back in to Teamcenter, only those files that have been checkedout can be imported back in to the database. This is referred to as high security andit applies to all files that are managed by a connection.

Export rules

Option DescriptionAdd Exports the primary dataset file, its component

files, and any additional files to the connection.

If the primary file is already in the connection,the system does not check if any of the componentfiles or additional files must be updated orreplaced due to changes in the system. It ignoresthe Add function for that file.

Resend Exports the selected file, its component files,and any additional files to the connection exportdirectory, overwriting files that are already inthe directory.

Any modifications you have made to the filesin the connection export directory are lost. UseResend only when you are sure that you wantto discard file modifications. Files not previouslyexported to the connection are added.

Refresh Checks to see if the selected files have beenmodified in the system since the last export tothe connection. If modified, the system exportsthe selected files, the associated components,and any additional files to the connection. Filespreviously exported to the connection are treatedas if the Add option was used.

Analysis resultsAfter performing an analysis prior to import, the system displays any of thefollowing results.

The check mark indicates that the dataset analysis was successful.

The error symbol indicates that the analysis failed.

The warning symbol indicates that an unusual condition was found duringthe analysis of the dataset.


Chapter 1 Getting started

Double-click the warning or error icons to display an explanatory message.

Batch export and file archival

NX Remote Manager allows you to export files to a connection in batch mode andarchives the files in either .zip format (Windows) or .tar format (UNIX). The archivefile is stored in the connection directory along with the files that were selected forexport. You can request notification of completion of the batch import operation viae-mail. For more information, see Configuring NX Remote Manager.


Chapter

2 Configuring NX Remote Manager

Configuring NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Enable NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Enabling automatic archiving of exported files . . . . . . . . . . . . . . . . . . . . . . . 2-1

Enable batch import/export on a personal workstation . . . . . . . . . . . . . . . . . . 2-2

Enable batch import/export on a remote workstation . . . . . . . . . . . . . . . . . . . 2-2

Enable e-mail notification of batch import/export completion . . . . . . . . . . . . . 2-2

Guidelines for part naming when using NX Remote Manager . . . . . . . . . . . . . 2-2


Chapter

2 Configuring NX Remote Manager

Configuring NX Remote ManagerNX Remote Manager functionality allows you to import and export NX data fromTeamcenter to a connection directory for use by remote users and suppliers. The NXRemote Manager is installed as part of the Teamcenter installation; however, youmust perform the configuration steps described in this section to enable NX RemoteManager functionality.

Enable NX Remote ManagerIn Teamcenter:

1. Choose Edit→Options.

2. Click the Index link at the bottom of the dialog box.

Teamcenter displays the Preferences dialog box.

3. Type the preference name, AIE_installed, in the Search on preference name box.

4. Set the value of the preference to Yes.

In NX:

Perform the following step to enable native NX to update the IXF files:

• Copy the ug_base.dtd and ugxmlgen.dll/.so/.sl files from the%UGII_BASE_DIR%\UGALLIANCE\vendor\application to the%UGII_BASE_DIR%\UGALLIANCE\vendor\startup directory.

Enabling automatic archiving of exported filesUse the WinZip wzzip command line utility to archive exported files on Windowsplatforms. This utility is not part of the Teamcenter installation and must bedownloaded from the following location:

www.winzip.com/downcl.htm

After the utility is downloaded and installed, you must add the path to the wzziputility to the PATH system variable.


Chapter 2 Configuring NX Remote Manager

Enable batch import/export on a personal workstationWindows systems:

1. Download the jt utility from the Microsoft FTP site(ftp://ftp.microsoft.com/reskit/win2000/jt.zip).

This utility provides scheduling functionality that allows you to run a scheduledtask as a specific user. (The at command does not provide this functionality.)

2. Ensure that the Task Scheduler service is running.

This service enables you to configure and schedule automated tasks on thecomputer. If the service is stopped, the tasks are not run at their scheduledtimes. If the service is disabled, any services that explicitly depend on it fail.

UNIX systems:

• Use the UNIX at command.

To use the at command, your name must appear in the usr/lib/cron/at.allowfile. If that file does not exist, the usr/lib/cron/at.deny file is checked todetermine whether you should be denied access.

If the at.deny file exists and is empty, global usage is permitted.

If neither file exists, only users with superuser authorization can submit a job.

Enable batch import/export on a remote workstation1. Modify the values of the AIE_batch_servers preference to include the host

names of the remote machines to be used for import/export operations.

2. Ensure that the user has the same login credentials on the remote system thatthey do on their local system.

3. Ensure that the values of the TC_ROOT and TC_DATA environment variablesare identical on all computers.

4. Ensure that the connection directory is accessible using exactly the same pathinformation on all computers.

Enable e-mail notification of batch import/export completion• Set the value of theMail_server_name preference to specify the names of the

remote machines used for import/export operations.

Guidelines for part naming when using NX Remote ManagerThe following naming guidelines must be followed when importing and exportingdata using NX Remote Manager:

• Naming guidelines for import


ftp://ftp.microsoft.com/reskit/win2000/jt.zip

Configuring NX Remote Manager

Part file names matching ItemId_RevId_NonMasterTypeCode_DatasetNamebecome Non-Master-Parts-ItemId/RevId/NonMasterType/DatasetName uponimport.

Part file names matching ItemId_RevId becomeMaster-Parts-ItemId/RevId uponimport.

If neither of the previous conventions are used, the entire part file name is usedas the ItemId and a RevId of A is arbitrarily applied.

Note Underscores in generated part numbers are converted to spaces.

• Naming guidelines for export

Master parts (ItemId/RevId) become ItemID_RevID upon export.

Nonmaster parts (ItemId/RevId/NonMasterType/DatasetName) becomeItemID_RevID_NonMasterTypeCode_DatasetName upon export, whereNonMasterTypeCode is a single letter code for the type of the nonmaster part (forexample, m for manifestation and s for specification).

To create the following hierarchy:

Top Assy (with an associated drawing using manifestation relation)

- A1 (with an associated drawing using manifestation relation)

- D1 (with an associated drawing using manifestation relation)

- D2

Name the parts/drawings as follows:

123001_A.prt (UGMASTER dataset)

123001_A_m_TopAssyDwg.prt (UGPART with manifestation relation)


123002_A_m_A1Dwg.prt (UGPART with manifestation relation)


123003_A_m_D1Dwg.prt (UGPART with manifestation relation)


Note Spaces in generated names are converted to underscores.


Chapter

3 Using NX Remote Manager

Using NX Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Establish a remote export connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Remote connection behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Send data to an existing connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Adding datasets to a remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Manually export data to a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Refresh files in a remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Importing files from a remote connection to Teamcenter . . . . . . . . . . . . . . . . . 3-5Import modified data in to Teamcenter from a remote connection . . . . . . . 3-5Prevent files in a remote connection from being imported to Teamcenter . . 3-6Manually import data from a connection . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Set connections options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Delete a remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

View transaction logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9


Chapter

3 Using NX Remote Manager

Using NX Remote ManagerNX Remote Manager shares files with remote users who have no access to theTeamcenter database. Data is exported, and after modifications are made the datais imported back in to Teamcenter. This works well for suppliers or for users whowant to work independently with a laptop computer and then synchronize their datawith the Teamcenter database.

Remote connections manage files and associated information that is transferred backand forth between Teamcenter and the connection. The remote connection list showsall active and failed connections for the current user.

A remote connection is independent of both the Teamcenter session and theapplication session. The connection keeps a history of data sent to the connectionand the data received from the connection.

You can have more than one connection open at any time to send data to multiplesuppliers. This allows you to track what has been sent to and received from eachsupplier and also allows suppliers to work on multiple projects.

Note The UGII_BASE_DIR and UGII_ROOT_DIR environment variables mustbe set to export item revisions containing UGMASTER datasets. If NXis installed locally, these variables are set automatically. However, if youaccess the NX network from a mapped drive, you must manually set theseenvironment variables.

Establish a remote export connection1. Log on to Teamcenter.

2. Select one or more datasets in My Teamcenter.

3. Add the files to the connection by choosing Tools→Export→To connection.The system displays the Export Root(s) to Connection dialog box.

4. Create a new export/import connection.

You can have more than one connection open at any time to send data to multiplesuppliers.

5. Select the components in the assembly that you want to download or check out.

You can force all items in a selected branch to default to Download Only,Download and Checkout, or neither, in which case the component is not


Chapter 3 Using NX Remote Manager

exported. If the component is already checked out, or if you do not have writeprivileges to the dataset, you are not allowed to select the checkout option.

6. Click Archive to create a compressed file of the exported files. (Optional)

7. Click Interactive to set up an import/export operation to be run at a later time.(Optional)

8. After you make your selections, click OK.

Remote connection behavior

When working with remote connections, the system automatically:

• Creates the remote connection directory, as specified by your preferences.

The remote connection directory is a single directory where the separate exportdirectories reside for each connection. All files for a connection are exported toand imported from its export directory. If the connection export directory alreadyexists when the system attempts to create it, the directory is preserved and anyfiles in the directory are preserved and are not overwritten.

• Exports the primary named reference file(s) of the corresponding dataset to theconnection export directory.

If the dataset is the root of an assembly, the selected component files areexported.

• Creates a connection and adds it to your connection list.

A remote connection is a database object used internally by the system. Itmanages all files and associated information that is transferred back and forthbetween the system and the connection. The remote connection list is the list ofall connections (regardless of the application). The list contains all connectionsfor active remote connections as well as all connections for remote connectionsthat may have failed.

Send data to an existing connection1. Select a dataset in My Teamcenter.

2. Choose Tools→Export→To Connection.

The system displays the Connection dialog box.


Using NX Remote Manager

You can export, add, resend, or refresh the connection from this dialog box.

Adding datasets to a remote connection1. In My Teamcenter, select the dataset.

2. Choose Tools→Export→To connection.

The system displays the Export Root(s) to Connection dialog box.

3. Click OK.

The system begins the analysis process to determine what files to export and tocheck for errors. Before exporting any files, the system analyzes each dataset.When the analysis is complete, the dialog box shows the list of datasets and theresults for each.

4. Click OK.

The system exports the selected files to the connection export directory. If allfiles export successfully, the system displays the Transaction Log File dialog box.If one or more files do not export successfully, the system displays the log.



Manually export data to a connection1. In the Connections dialog box, select a connection.

2. Click the Export to Connection button.

Refresh files in a remote connection1. Select the dataset in My Teamcenter.

2. Choose Tools→Export→To Connection.

The system displays the Connection dialog box.

3. Click Refresh.

The system checks to see if the selected file has been modified in Teamcentersince the last export to the connection. If the file has been modified inTeamcenter but has not been modified in the connection, the system re-exportsthe selected file, its components, and its related files.

4. Click OK.

The system updates the connection directory with all changes made inTeamcenter since the last export operation, including adding new components tothe assembly, removing deleted components from the assembly, exporting newitem revisions, and exporting new dataset revisions.



Importing files from a remote connection to TeamcenterWhile working with a remote connection, you can send (import) modified data fromthe connection export directory back to Teamcenter.

The following actions occur when you import modified files from a remote connectionto Teamcenter:

• Files that have been modified in the connection export directory are imported asnew file versions.

• Files that have not been modified in the connection export directory are skippedand not imported.

• Soft links in the connection export directory are not supported. Attempting toimport soft links can cause unpredictable results.

Import modified data in to Teamcenter from a remote connection

1. Move all files that need to be imported to the connection export directory.

2. In My Teamcenter, choose Tools→Import→From Connection.

The system displays the Connections dialog box.

3. Click the Import button .

The system displays the File(s) to Import dialog box dialog box.



4. Select any files that you do not want to import and choose Skip in the Actioncolumn.

5. Click OK.

The system imports the files from the connection export directory. After the fileshave been imported, the system displays the Transaction Log dialog box.

6. Click Close to dismiss the dialog box.

Prevent files in a remote connection from being imported toTeamcenter

1. Select a connection in the Connection Name column of the Connections dialogbox.

2. Select Yes in the Export Only column corresponding to the selected connection.

Manually import data from a connection

1. Select a connection in the Connection Name column of the Connections dialogbox.



2. Click the Import from Connection button.

Set connections optionsOptions for specifying the behavior of NX Remote Manager connections are listedunder AIE in the Teamcenter Options dialog box.

1. In the Teamcenter rich client, choose Edit→Options.

2. Select AIE from the tree on the left side of the Options dialog box.

The system displays the AIE options in the dialog box.

3. Set the NX Remote Manager options as described in the following table.

General tabSave log from deletedconnections

Directs the system to save the transaction logfile for each connection after the connection isdeleted. The log file is saved in the top-levelNX Remote Manager connection directory. Thename of the file is the name of the connectionfollowed by a number to make it unique. Forexample, a connection named UG-RM_001has a corresponding transaction log file namedUG-RM_001_6671.log.

Export tabExport Directory Allows you to define the top-level NX Remote

Manager connection directory. This is themain directory where the system creates theexport directory for each connection.

Export read only files as readonly

Specifies how files associated with datasets towhich you do not have write permission areexported. If this option is selected, those filesare written in the connection export directorywith read-only privileges. If not checked, allfiles are written to the export directory withread/write privileges.



Named References to Export Specifies the named references to export to aconnection. Valid values are:

All

Exports all named references of thedataset.

Select

Displays a dialog box for selecting specificnamed references to export.

Primary

Exports the primary named reference forthe dataset.

Check out new componentsduring refresh connection

Specifies that all items that can be checkedout are checked out when the connection isrefreshed.

Import tab

File types to ignore Defines the file types to ignore during import,such as backup files.

Import Details Master Indicates if the user has permissions to modifyimport information in the XML files whenimporting them back to Teamcenter. Validvalues are:

Application

User is not allowed to change the importinformation from Teamcenter.

Both

User is allowed to modify importinformation from Teamcenter.

NX tabCopy non-master Enables the export of manifestation,

specification and other nonmaster items.

Part Family Members Specifies how to process part family membersduring import/export.

Autotranslate Mode Specifies whether autotranslate mode is thedefault behavior or whether import should belegacy compatible.

4. Click Apply or OK.



Delete a remote connection1. In My Teamcenter, choose Tools→Connection.

2. Select the connection, and click Delete Connection.

The connection export directory is deleted, and the persistent connection isremoved from your connection list and from the Teamcenter database.

View transaction logs1. In My Teamcenter, choose Tools→Connection.

2. Select the connection, and click the Reports button.

The transaction log for the selected connection is displayed. The transaction logviewer allows you to print the log file or save it as a text or HTML file.


Chapter

4 Importing and exportingassemblies

Importing and exporting assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

How Teamcenter imports and exports assemblies . . . . . . . . . . . . . . . . . . . . . 4-1Connection export directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Exchange files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1High security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Data manager tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Export assemblies with BOM information . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Exporting without BOM information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Check out a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Importing data from a remote connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Import data from a remote connection to Teamcenter . . . . . . . . . . . . . . . . 4-6Selecting item types during import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Support of subdirectories within the connection directory . . . . . . . . . . 4-8


Chapter

4 Importing and exportingassemblies

Importing and exporting assembliesNX Remote Manager enables you to import, export, check in, and check out datasetscontrolled from one location. When a top-level assembly is imported or exported, allsubassemblies and components can be managed as well.

How Teamcenter imports and exports assembliesTo understand how Teamcenter imports and exports assemblies, you mustunderstand the following concepts:

• Connection export directory

• Exchange files

• High security

Connection export directory

NX Remote Manager maintains an export directory to manage the export and importoperations of a connection. All files that are exported are accounted for in thisdirectory, which is accessed by appending the connection export directory to a rootdirectory (default or user specified). The connection directory allows a subdirectorystructure if your application can support it.

Exchange files

NX Remote Manager writes and reads XML exchange files in the connectionexport directory. An XML file is written for each file that is exported. These filescontain metadata such as product structure, attribute information, and timestampinformation. NX Remote Manager uses this information to determine which filesmust be updated when a subsequent export or import operation is performed. TheseXML files must reside in the connection export directory for the duration of theconnection. If the contents of the connection directory get moved or copied, the XMLfiles must be moved or copied along with the application files.


Chapter 4 Importing and exporting assemblies

High securityNX Remote Manager exports files with read and write permissions. Those files thatare not explicitly checked out are exported as read-only reference files. On import,only files that have been checked out can be reimported. This security behavior isreferred to as high security and applies to all files that are managed by a connection.

Data manager tasksA connection is created to support offline work or to manage a supplier data sharingenvironment. Certain functions, such as creating a new connection or decidingwhat data needs to be sent through the connection can only be done if you are aTeamcenter data manager.

The following tasks are performed by a data manager:

• Log on to Teamcenter.

• Select the data to be exported, single items (My Teamcenter) or a BOM line(Structure Manager).

• Check out the data to be modified by the supplier.

• Create a new connection, if required.

Note Connections keep a history of the data sent to the connection andthe data received from the connection. You can have more than oneconnection open at any time. This enables a single data manager tosend data to multiple suppliers and keep track of what has been sent toand received from each supplier.

Every connection has only one owner. The data manager that createsthe remote connection is the connection owner.

• Export the data.

• Import data that has been modified by suppliers.

• Export new data as it becomes available in Teamcenter.

Export assemblies with BOM information1. In Structure Manager, open the assembly to be exported.

2. Configure the assembly by applying revision rules, variants, and effectivity.

When working with NX assemblies, this configuration is limited to thefunctionality available in the ug_clone command line utility. Variants and otherconfiguration options are not supported.

3. After the assembly is configured, choose Tools→Export to Connection.The system opens the Export Root(s) to Connection dialog box, which is initiallyempty.


Importing and exporting assemblies

4. Select an existing connection or create a new connection.

The root directory is populated based on the NX Remote Manager preferencesetting for the root directory location.

Note The system does not validate whether the connection name is unique;however, you must specify a unique connection name.

5. Select an export rule. For more information, see Export rules.

6. Select the dataset type to be exported from the Dataset Type list.

The list includes all registered NX Remote Manager dataset types that can beexported if found in the assembly structure.

You can:

• Select a single dataset type to be exported.

• Select multiple dataset types to be exported.

• Select all dataset types to be exported.

• Export all registered dataset types.

After the dataset types are selected, the system displays the top BOM line.



7. (Optional) Apply export or checkout selections to an entire branch of theassembly by right-clicking the root node of the assembly and choosing an option.

8. (Optional) Apply one of the following export or checkout selections to singlecomponents:

• Skip (None of the boxes are checked.)The selected datasets under the BOM line are not exported.

• Export (Only the Export box is checked.)The selected datasets under the BOM line are exported but not checkedout (read-only copy).

• Export+CO (Both the Export and Check Out boxes are checked.)The selected datasets under the BOM line are exported and checked out.

Note You can only check out datasets to which you have write access. Inaddition, if you attempt to check out datasets that are currentlychecked out, the system automatically changes the status fromExport+CO to Export.



9. When your selections are complete, click OK.

Exporting without BOM informationWhen exporting an assembly without BOM information, you must first select anitem or item revision. If you choose an item, the default revision rule specified by thepreferences file is used to determine the appropriate item revision.

Check out a file1. Choose Tools→Export→To Connection.

The system displays the Connections dialog box.

2. Select an existing connection or create a connection.

The root directory populated in the dialog box is based on the NX RemoteManager preference setting for the root directory location. You must specify aunique connection name.

3. Click Export.The system displays the Export Root(s) to Connection dialog box.

The checkout ID displays comments that are applied to all datasets selected forcheckout, and the existing connection is displayed (if applicable).

4. If you do not have an existing connection, check the Create New Connection box.

5. Specify a unique connection name.

6. Specify the change ID and comments.

These are applied to all datasets for the selected checkout action.

7. Choose an action for each dataset, as follows:

• SkipFiles under this dataset are not exported.



• ExportFiles under this dataset are exported but not checked out (read-only copy).

• Export+COFiles under this dataset are exported and checked out (read/write copy).

Note You can only check out datasets to which you have write access. Inaddition, if you attempt to check out datasets that are currentlychecked out, the system automatically changes the status fromExport+CO to Export.

8. After you enter all the necessary information, click OK.Any errors that occur during export are logged in the transaction log for theconnection.

Importing data from a remote connectionWhile working with a remote connection, you can import modified data from theconnection export directory back to the Teamcenter database.

When you import modified files from a remote connection:

• Files that have been modified in the connection export directory are imported asnew file versions.

• Files that have not been modified in the connection export directory are skippedand not imported.

Import data from a remote connection to Teamcenter

1. Move all files that need to be imported into the connection export directory.

2. In My Teamcenter, choose Tools→Import→From Connection.The system displays the Connection dialog box, including the existingItemID/Rev-ItemName information for each primary file to be imported.

3. If you have more than one remote connection running, select a connection fromthe table.

4. Click Import in the Connection dialog box.The system analyzes the files to be imported. If no files have been modified orcreated, the system detects this and the import operation stops. The systemdisplays the analysis results in the Comments column of the File(s) to Importdialog box.

5. Apply import options to the individual files using the Action list. The followingoptions are available:

• SkipExcludes the file from the import operation.



Note Skip is the only option available if you do not have write access tothe selected dataset.

• Import–Implicit COImplicitly checks out the dataset if it was not checked out at export andimports it to Teamcenter.

• Import–OverwriteImports the dataset and overwrites the existing dataset in Teamcenter.

• Import–Next RevImports the dataset in to the next revision of the item and cancels checkouton the previous revision of the item.

6. After selecting the files to skip, click OK to import the selected files or Cancelto stop the import operation.

If you selected Retain checkout, the connection directory is updated with thenew item ID/revision and item type values.

Note In the case of an NX dataset, this implies an internal call to ug_clone(export – dry run + actual export).

NX Remote Manager imports the files from the connection’s export directory.After the files have been imported, the import results display. For import errorsfrom the ug_clone utility, refer to the syslog file.

7. Click OK to dismiss the dialog box.

Selecting item types during import

If a connection directory contains newly created files, you are given an option toselect the item type to create within Teamcenter for storing the files.



The list of item types displayed depends on the dataset type specified in the XMLfile for the new file and the item types defined in the DMS (data model service) forthe dataset type.

Support of subdirectories within the connection directory

If files exist in subdirectories under the main connection directory, the subdirectoryinformation corresponding to the files is stored in Teamcenter using a relative path.Subsequent exports of this file use the relative path information to place the file ina subdirectory under the (new) connection directory.

If a file is found more than once in the connection directory structure, only the firstoccurrence is imported and subsequent occurrences are ignored. This is captured inthe transaction log file.


Chapter

5 NX Remote Manageradministration

NX Remote Manager administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Register custom item types with NX Remote Manager . . . . . . . . . . . . . . . . . . 5-1

Preferences and utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

AIE_named_refs_to_export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4AIE_overwrite_default_import_item_types . . . . . . . . . . . . . . . . . . . . 5-5AIE_skip_class_types_for_save . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6AIE_POST_EXPORT_SCRIPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7AIE_PRE_IMPORT_SCRIPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8aie_clean_datamodel_objs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9aie_install_datamodel_objs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10BatchImp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11


Chapter

5 NX Remote Manageradministration

NX Remote Manager administrationThe NX Remote Manager requires ongoing administration which is performed usingutilities and preferences. In addition, custom item types must be registered with NXRemote Manager before they can be used with integrated applications.

Register custom item types with NX Remote ManagerNote Custom item types must be registered with NX Remote Manager before they

can be used with integrated applications. The following example registerscustom item types for the NX Remote Manager.

1. Edit the accaddwg_dms.xml and acadtmpl_dms.xml files located in theACAD_EM\Data directory by changing the existing item type to reflect theitem type you want to use when new items are created.

The following example illustrates the changes required to modify the item typefrom Item to CORP_Tool in the XML file.

…

<Info Datasettype="ACADDWG">

<Create>

<Value>Item:Specification:view</Value><Value>Document:Manifestation</Value><Value>Item:Manifestation:view</Value>

</Create>…

<Info Datasettype="ACADDWG">

<Create>

<Value>CORP_Tool:Specification:view</Value><Value>Document:Manifestation</Value><Value>CORP_Tool:Manifestation:view</Value>

</Create>…


Chapter 5 NX Remote Manager administration

2. Open the AdditionalInfo.xml file located in the AcadMgr_DIR\Supportdirectory in a text editor and add the item types to the file. This file lists theitem types that appear in the Boundary dialog boxes.

The following example shows the AdditionalInfo.xml file.

<?xml version="1.0" encoding="ISO-8859-1"?>



<BoundaryTypes><Type>MEStation</Type><Type>MEWorkarea</Type><Type>MELine</Type><Type>MEDepartment</Type><Type>MESite</Type><Type>MEPlant</Type><Type>CORP_Facility</Type><Type>CORP_Tool</Type><Type>CORP_Part</Type><Type>CORP_Vehicle</Type><Type>CORP_Criteria</Type><Type>CORP_Proc_Plan</Type><Type>CORP_Simulation</Type><Type>CORP_Analysis</Type><Type>CORP_Process</Type><Type>CORP_Equipment</Type><Type>CORP_Install</Type>

</BoundaryTypes>

3. After modifying the XML files, open an MS-DOS window in the Teamcenterenvironment, and enter the following command on a single line:

aie_install_datamodel_objs -u=user-name-p=password -g=dba —file=acaddwg_dms.xml -modify=yes

For more information about the aie_install_datamodel_objs utility, seeaie_install_datamodel_objs.

Note When modifying the XML files, consider the following guidelines:

• Do not modify the xName element of the existing xRelation.You can add new XRelation elements, but they must be constantbetween versions of XML.

• If you do not specify the -modify argument for theaie_install_datamodel_objs utility, no modifications areperformed.


NX Remote Manager administration

4. If you do not have access to the XML files used to initially install the datamodel objects, run the following program to delete existing instances of thedataset types:

aie_clean_datamodel_objs -dstype=all

Note You can selectively delete instances corresponding to a particular datasettype by specifying a dataset type name for the -dstype= argument.

For more information about the aie_clean_datamodel_objs utility, seeaie_clean_datamodel_objs.

5. After deleting the dataset type instances by running theaie_clean_datamodel_objs utility, run the aie_install_datamodel_objsutility without the -modify argument to populate the data model instances.

Preferences and utilitiesPreferences and utilities are used to set up and configure NX Remote Manager.

Preferences

Preferences are used to configure NX Remote Manager. Preferences are environmentvariables stored in the database and are read when a Teamcenter session or a sessionof an integrated application is initiated. For more information about preferences, seethe Preferences and Environment Variables Reference.



AIE_named_refs_to_export

DESCRIPTIONAllows you to specify the named references to export to a connection.

VALIDVALUES

all Exports all named references of the dataset.

select Displays a dialog box allowing you to select the named references toexport.

primary Exports the primary named reference of the dataset.

DEFAULTVALUE

primary

DEFAULTPROTECTION

SCOPESite preference.



AIE_overwrite_default_import_item_types

DESCRIPTIONControls whether the default item types can be overwritten during import using NXRemote Manager.

VALIDVALUES

on Allows the user to choose from all item types listed in the DMS whenimporting new or previously exported files.

off Disables item type selection when importing files. Files that werepreviously exported from Engineering Process Management are importedusing the item type assigned when they were exported, and new files areimported using the default item type.

DEFAULTVALUE

on

DEFAULTPROTECTION




AIE_skip_class_types_for_save

DESCRIPTIONSpecifies item types that must not be displayed as options in the Item Type list inthe Save dialog box when saving a file in an integrated application. For example,business rules in the GM Overlay prevent items of type Item from being created.Adding Item as a value for this preference prevents the item type from being achoice when items are saved in NX Remote Manager.

VALIDVALUES

Any valid item type for which creation is disallowed.

DEFAULTVALUE

This preference is unset in the Engineering Process Management environment. Inthe Teamcenter Automotive Edition–GM Overlay environment, the default valueis Item.

DEFAULTPROTECTION




AIE_POST_EXPORT_SCRIPT

DESCRIPTIONSpecifies a fully qualified path to an executable script that are executed after thecompletion of NX Remote Manager export operation.

VALIDVALUES

Path to the script. This path must not contain special characters or spaces. Inaddition, the path separator must be in accordance with the platform on which thescript runs, for example:

UNIX systems:

AIE_POST_EXPORT_SCRIPT=/usr/bin/my_export.sh

Windows systems:

AIE_POST_EXPORT_SCRIPT=C:\Utilities\my_export.bat

DEFAULTVALUE

By default, this preference is not set.

DEFAULTPROTECTION




AIE_PRE_IMPORT_SCRIPT

DESCRIPTIONSpecifies a fully qualified path to an executable script that will be executed beforethe NX Remote Manager import operation begins.

VALIDVALUES

Path to the script.

DEFAULTVALUE

By default, this preference is not set.

DEFAULTPROTECTION


Utilities

Command line utilities are used to install and maintain the NX Remote Managerdata model and to import files in batch mode. For more information about utilities,see the Utilities Reference.



aie_clean_datamodel_objs

DESCRIPTIONDeletes instances of a specific dataset type or instances of all dataset types fromthe NX Remote Manager data model.

SYNTAXaie_clean_datamodel_objs -u=user-id -p=password -g=group-dstype=all | datasettype-name

ARGUMENTS-dstype Specifies the dataset type for which instances will be deleted.

ENVIRONMENTAs specified in Configuring utilities.

FILESAs specified in Log files.

RESTRICTIONSNone.

EXAMPLES• The following example unregisters all dataset types that are registered in the

NX Remote Manager data model:

aie_clean_datamodel_objs -u=infodba -p=password -g=dba -dstype=all

• The following example unregisters the NX Remote Manager data model for theUGMASTER dataset type:

aie_clean_datamodel_objs -u=infodba -p=password -g=dba -dstype=UGMASTER



aie_install_datamodel_objs

DESCRIPTIONAdds, modifies, and deletes data model definitions based on customer-defined itemtypes.

SYNTAXaie_install_datamodel_objs -u=user-id -p=password -g=group-file=dms_definition_file [-modify=yes]

ARGUMENTS-file Specifies the name of the file containing the NX Remote Manager

data model definition. The NX Remote Manager data model file iswritten using XML syntax, which must follow the document typedefinition in the dms.dtd file.

-modify Specifies whether the NX Remote Manager data model isoverwritten. The value yes overwrites the data model.

ENVIRONMENTAs specified in Configuring utilities.

FILESAs specified in Log files and the aie_install_datamodel_objs183e5050.log andaie_install_datamodel_objs183e5050.jnl files.

RESTRICTIONSThe -modify argument must only be used with the value yes. If theaie_clean_datamodel utility was previously run for the same dataset type, you donot need to specify the -modify argument.

EXAMPLESThe following example registers the UGMASTER dataset with NX Remote Managerby providing an NX Remote Manager data model definition for the dataset type:

aie_install_datamodel_objs -u=infodba -password=password -g=dba-file=ugmaster_dms.xml -modify=yes



BatchImp

DESCRIPTIONImports multiple files in to the Teamcenter database without starting the integratedCAD application.

SYNTAXBatchImp [-r] [-q] [-n] input-file-name -u=user-id -p=password -g=group[-f=Teamcenter folder] [-n ] [-x] [-xml] [-d=dataset-type] [-dryrun]

ARGUMENTSinput file Specifies the input map file containing the list of drawings with

item ID, item type, and specified attributes.

-r Specifies that if the drawing was previously imported in toTeamcenter, it should be imported under a new item revision. Thisargument is optional.

-q Specifies whether the user should be prompted for each previouslyimported drawing to be reimported. If the drawing is to beimported as specified by the user, the -r option is used to determinewhether a new item revision is created. This argument is optional.

-n Specifies that only those drawings that have not previously beenimported in to Teamcenter are imported. This argument isoptional.

-x Specifies that the batch import only creates the according IXF filesand uses the aie_batch_import.exe utility to perform the importoperation. If this argument is not specified, the batch import .arxfile performs the import without creating the .ixf files.

-xml Generates the IXF file for a specific drawing.

This option does not import the drawing files in to the Teamcenterdatabase. It is intended to create the IXF files that are requiredwhen importing drawings in NX Remote Manager mode.

-u Specifies the user ID used to log in to the Teamcenter database.This argument is required unless single sign-on (SSO) in SecurityServices is enabled. If SSO is enabled, this argument is notnecessary and is ignored if provided.

-p Specifies the password used to log in to the Teamcenter database.This argument is required unless single sign-on (SSO) in SecurityServices is enabled. If SSO is enabled, this argument is notnecessary and is ignored if provided.

-g Specifies the group of the user logging in to the Teamcenterdatabase. This argument is required.

-f Specifies the Teamcenter folder in which items or item revisionsare created for the imported files. If not specified, the default is theNewstuff folder. This argument is optional.

-d Specifies the dataset type of the Teamcenter dataset object towhich the imported files are attached.



-dryrun Specifies a dry run that generates a new output file named byappending _dryrun to the original input map file name. For eachdrawing file specified in the input map file, the dryrun optiontraverses the drawing and transcribes the original input linealong with the file names of every component file, if inputtingan assembly, to the output file in bottom-up fashion. The outputfile gives the user a clear view of the files involved in the importoperation. The output file also serves as a new input map file tothe batch import program. When the dryrun option is specified,only the input map file must be specified.

ENVIRONMENTThis utility must be run from the command line in an MS-DOS shell with allTeamcenter environment variables set appropriately.

FILESNone.

RESTRICTIONSNone.

NOTES• All drawings imported to Teamcenter without using the -x option have the item

ID and item revision stored as attributes in the Teamcenter data directory.

• If the batch import finds the attributes for item ID and item revision in theTeamcenter data dictionary and values are assigned to them, the file is importedby default unless the -n argument is used.

• If the -r argument is not used, the drawing is imported in to the existing itemrevision.

• Automatic assignment of new item revision identifiers is supported for itemrevisions identified by alphabetic characters and numbers.

• When specifying attribute names for general attribute batch import, namesmust reflect the Teamcenter attribute name rather than the CAD applicationattribute name.

• Errors appear in the batch import log file when importing multilevel assemblies.

• During batch import, BOM view revisions are not updated when an assembly isreimported in to the current item revision. After importing the assembly usingthe batch import utility, create the BOM view revision in the two-tier rich clientby sending the parent component to Structure Manager, adding the child itemsin Structure Manager, and saving the structure.

EXAMPLESIn this example, the user imports two drawings, as follows:

test_batch_1.dwg\test_batch_3.dwgtest_batch_2.dwg

test_batch_1.dwg and test_batch_2.dwg are independent drawings.test_batch_3.dwg is attached as an external reference (attachment or overlay)to test_batch_1.dwg.



The following input file is used to import the drawings.

Attributes,itemID,itemtype,MachNumD:\IMANConnection\connection1\test_batch_1.dwg,000123,Item,23D:\IMANConnection\connection1\test_batch_2.dwg,000124,Item,24D:\IMANConnection\connection1\test_batch_3.dwg,,,25

The first line in the file is mandatory. The entries Attributes, itemID, and itemtypeare required. The MachNum entry represents the name of an attribute to be inputduring import.

The first entry in the second line of the file specifies the full path to the drawingbeing imported. The other entries in this line are the item ID, item type, and thevalue of the MachNum attribute.

The fourth line contains entries for the item ID and type. These can be left blank,in which case the item ID are generated automatically, and the item type defaultsto Item.

Warning This file must be edited using a text editor, such as Notepad. In addition,the file must end with a new-line character.


Appendix

A Glossary


Appendix

A Glossary

A

access control list (ACL)Access Manager component that contains a list of accessors and, for each accessor,the privileges granted, denied, and not set.

B

BOM view revision (BVR)Workspace object that stores the single-level assembly structure of an item revision.Access can be controlled on the structure (BOM view revision) independently ofother data. BOM view revisions are meaningful only in the context of the itemrevisions for which they are created.

C

connection nameAutomatically generated or user-provided name that identifies the connectionbetween Teamcenter and Teamcenter Integration for AutoCAD.

N

NX Remote ManagerTeamcenter component for managing the import and export of documents intoTeamcenter. NX Remote Manager is a common component across integrations thatinclude applications in fields such as CAE and ME.

PLM00123 G NX Remote Manager Guide A-1

Index

A

Adding datasets to remote connections . . 3-3aie_clean_datamodel_objs utility . . . . . . 5-9aie_install_datamodel_objs utility . . . . . 5-10AIE_named_refs_to_export preference . . 5-4AIE_overwrite_default_import_item_typespreference . . . . . . . . . . . . . . . . . . . . . . 5-5AIE_skip_class_types_for_savepreference . . . . . . . . . . . . . . . . . . . . . . 5-6Analysis results . . . . . . . . . . . . . . . . . . 1-3Failure . . . . . . . . . . . . . . . . . . . . . . . 1-3Success . . . . . . . . . . . . . . . . . . . . . . . 1-3Unknown condition . . . . . . . . . . . . . . 1-3

Archiving files during export . . . . . . . . . 1-4AssembliesExporting . . . . . . . . . . . . . . . . . . . . . 4-1Exporting with BOM information . . . . 4-2Exporting without BOM information . . 4-5Importing . . . . . . . . . . . . . . . . . . . . . 4-1Selecting item types to import . . . . . . . 4-7

B

Batch import . . . . . . . . . . . . . . . 5-11–5-12BatchImp utility . . . . . . . . . . . . . . . . . 5-11

C

Configuring NX Remote Manager . . . . . . 1-1Connection export directory . . . . . . . . . . 4-1Connections options . . . . . . . . . . . . . . . 3-7Autotranslate Mode . . . . . . . . . . . . . . 3-8Check out new components during refresh

connection . . . . . . . . . . . . . . . . . . 3-8Copy non-master . . . . . . . . . . . . . . . . 3-8Export directory . . . . . . . . . . . . . . . . . 3-7Export read only files as read only . . . . 3-7File types to ignore . . . . . . . . . . . . . . . 3-8Import Details Master . . . . . . . . . . . . 3-8Named References to Export . . . . . . . . 3-8Part Family Members . . . . . . . . . . . . . 3-8Save log from deleted connections . . . . 3-7

Custom item types . . . . . . . . . . . . . . . . 5-1

EEnabling NX Remote Manager . . . . . . . . 1-1Ending remote connections . . . . . . . . . . 3-8Environment variables . . . . . . . . . . . . . 5-3Exchange files . . . . . . . . . . . . . . . . . . . . 4-1Export rules . . . . . . . . . . . . . . . . . . . . . 1-3Add . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Refresh . . . . . . . . . . . . . . . . . . . . . . . 1-3Resend . . . . . . . . . . . . . . . . . . . . . . . 1-3

Exporting assemblies . . . . . . . 4-1–4-2, 4-5Exporting UGMASTER datasetsErrors . . . . . . . . . . . . . . . . . . . . . . . . 3-1

HHigh security . . . . . . . . . . . . . . . . . . . . 4-1

IImporting assemblies . . . . . . . . . . . . . . 4-1Importing data from a remoteconnection . . . . . . . . . . . . . . . . . . . . . 4-6Importing files . . . . . . . . . . . . . . . . . . 5-11Importing files from a remoteconnection . . . . . . . . . . . . . . . . . . . . . 3-4Importing multilevel assemblies . . . . . . 5-12Item types . . . . . . . . . . . . . . . . . . . . . . 5-6Custom . . . . . . . . . . . . . . . . . . . . . . . 5-1

NNX Remote Manager . . . . . . . . . . . . . . . 3-1Adding datasets to connections . . . . . . 3-3Establishing connections . . . . . . . . . . 3-1Importing files from a remote

connection . . . . . . . . . . . . . . . . . . 3-4Importing files, overriding default file

type . . . . . . . . . . . . . . . . . . . . . . . 5-5Refreshing files in connections . . . . . . 3-4Saving modified data . . . . . . . . . . . . . 3-5Selecting existing connections . . . . . . . 3-2

PPreferences . . . . . . . . . . . . . . . . . . . . . . 5-3

PLM00123 G NX Remote Manager Guide Index-1

Index

AIE_named_refs_to_export . . . . . . . . . 5-4AIE_overwrite_default_import_item_

types . . . . . . . . . . . . . . . . . . . . . . 5-5AIE_skip_class_types_for_save . . . . . . 5-6

Prerequisites for NX Remote Manager . . 1-1

RRefreshing files in remote connections . . . 3-4Registering custom item types . . . . . . . . 5-1Remote export connections . . . . . . . . . . . 3-1

S

Selecting existing connections . . . . . . . . 3-2

U

Utilities . . . . . . . . . . . . . . . . . . . . 5-3, 5-11aie_clean_datamodel_objs . . . . . . . . . . 5-9aie_install_datamodel_objs . . . . . . . . 5-10

Index-2 NX Remote Manager Guide PLM00123 G

Documents

NX Remote Manager Guide - Help!help.aviacons.ru/.../en_US/tdocExt/pdf/nx_remote_manager.pdfChapter 2 ConfiguringNX Remote Manager ConfiguringNXRemoteManager NX Remote Manager functionality