Teamcenter NX Remote Manager Guide. Publication Number PLM00123 G

Transcription

1 Teamcenter 10.1 NX Remote Manager Guide Publication Number PLM00123 G

2 Proprietary and restricted rights notice This software and related documentation are proprietary to Siemens Product Lifecycle Management Software Inc Siemens Product Lifecycle Management Software Inc. All Rights Reserved. Siemens and the Siemens logo are registered trademarks of Siemens AG. Teamcenter is a trademark or registered trademark of Siemens Product Lifecycle Management Software Inc. or its subsidiaries in the United States and in other countries. All other trademarks, registered trademarks, or service marks belong to their respective holders. 2 NX Remote Manager Guide PLM00123 G

3 Contents Proprietary and restricted rights notice Getting started Getting started Before you begin NX Remote Manager interface Basic concepts about NX Remote Manager Configuring NX Remote Manager Configuring NX Remote Manager Enable NX Remote Manager Enabling automatic archiving of exported files Enable batch import/export on a personal workstation Enable batch import/export on a remote workstation Enable notification of batch import/export completion Guidelines for part naming when using NX Remote Manager Using NX Remote Manager Using NX Remote Manager Establish a remote export connection Send data to an existing connection Adding datasets to a remote connection Manually export data to a connection Refresh files in a remote connection Importing files from a remote connection to Teamcenter Set connections options Delete a remote connection View transaction logs Importing and exporting assemblies Importing and exporting assemblies How Teamcenter imports and exports assemblies Data manager tasks Export assemblies with BOM information Exporting without BOM information Importing data from a remote connection NX Remote Manager administration NX Remote Manager administration Register custom item types with NX Remote Manager Preferences and utilities Glossary A-1 PLM00123 G NX Remote Manager Guide 3

4 Contents Index Index-1 4 NX Remote Manager Guide PLM00123 G

5 Chapter 1 Getting started Getting started Before you begin NX Remote Manager interface NX Remote Manager buttons Basic concepts about NX Remote Manager Export rules Analysis results Batch export and file archival PLM00123 G NX Remote Manager Guide

6

7 Chapter 1 Getting started Getting started NX Remote Manager provides the ability to share data between customers and suppliers using My Teamcenter to import and export data to directories that can be accessed by users outside of the Teamcenter environment. In addition, you can use NX Remote Manager to work offline and then synchronize data with the Teamcenter database. Before you begin Prerequisites NX Remote Manager only works in the Teamcenter two-tier architecture. It does not work in the four-tier architecture. Enable NX Remote Manager Configure NX Remote Manager NX and Teamcenter Integration for NX must be installed on the same machine as the Teamcenter server. NX Remote Manager must be enabled before you use it. For more information, see Enable NX Remote Manager. NX Remote Manager must be configured. For more information, see Configuring NX Remote Manager. NX Remote Manager interface There is no separate interface for NX Remote Manager. Features are accessed using NX Remote Manager menus in My Teamcenter. NX Remote Manager buttons Button Export to connection Import from connection Description Exports datasets to an active application encapsulation session. Imports datasets from an application encapsulation session. PLM00123 G NX Remote Manager Guide 1-1

8 Chapter 1 Getting started Button Delete failed connection Display connection log Description Deletes failed connections from the Teamcenter database. Displays the transaction log for a connection. Basic concepts about NX Remote Manager NX Remote Manager allows you to share files with remote users who have no access to the Teamcenter database. Data is exported, and after modifications are made, the data 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

9 Getting started 6 Remote individual user NX Remote Manager uses export directories to manage the connections used to import and export data. Files that are explicitly checked out for the current connection are exported with read-write permission. Files that are not explicitly checked out are exported as read-only reference files. When you import files back in to Teamcenter, only those files that have been checked out can be imported back in to the database. This is referred to as high security and it applies to all files that are managed by a connection. Export rules Option Add Resend Refresh Description 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 component files or additional files must be updated or replaced due to changes in the system. It ignores the Add function for that file. Exports the selected file, its component files, and any additional files to the connection export directory, overwriting files that are already in the directory. Any modifications you have made to the files in the connection export directory are lost. Use Resend only when you are sure that you want to discard file modifications. Files not previously exported to the connection are added. Checks to see if the selected files have been modified in the system since the last export to the connection. If modified, the system exports the selected files, the associated components, and any additional files to the connection. Files previously exported to the connection are treated as if the Add option was used. Analysis results After performing an analysis prior to import, the system displays any of the following 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 during the analysis of the dataset. PLM00123 G NX Remote Manager Guide 1-3

10 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 and archives the files in either.zip format (Windows) or.tar format (UNIX). The archive file is stored in the connection directory along with the files that were selected for export. You can request notification of completion of the batch import operation via . For more information, see Configuring NX Remote Manager. 1-4 NX Remote Manager Guide PLM00123 G

11 Chapter 2 Configuring NX Remote Manager Configuring NX Remote Manager Enable NX Remote Manager Enabling automatic archiving of exported files Enable batch import/export on a personal workstation Enable batch import/export on a remote workstation Enable notification of batch import/export completion Guidelines for part naming when using NX Remote Manager PLM00123 G NX Remote Manager Guide

12

13 Chapter 2 Configuring NX Remote Manager Configuring NX Remote Manager NX Remote Manager functionality allows you to import and export NX data from Teamcenter to a connection directory for use by remote users and suppliers. The NX Remote Manager is installed as part of the Teamcenter installation; however, you must perform the configuration steps described in this section to enable NX Remote Manager functionality. Enable NX Remote Manager In 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 files Use the WinZip wzzip command line utility to archive exported files on Windows platforms. This utility is not part of the Teamcenter installation and must be downloaded from the following location: After the utility is downloaded and installed, you must add the path to the wzzip utility to the PATH system variable. PLM00123 G NX Remote Manager Guide 2-1

14 Chapter 2 Configuring NX Remote Manager Enable batch import/export on a personal workstation Windows 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 scheduled task 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 the computer. If the service is stopped, the tasks are not run at their scheduled times. 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.allow file. If that file does not exist, the usr/lib/cron/at.deny file is checked to determine 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 workstation 1. 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 that they do on their local system. 3. Ensure that the values of the TC_ROOT and TC_DATA environment variables are identical on all computers. 4. Ensure that the connection directory is accessible using exactly the same path information on all computers. Enable notification of batch import/export completion Set the value of the Mail_server_name preference to specify the names of the remote machines used for import/export operations. Guidelines for part naming when using NX Remote Manager The following naming guidelines must be followed when importing and exporting data using NX Remote Manager: Naming guidelines for import 2-2 NX Remote Manager Guide PLM00123 G

15 Configuring NX Remote Manager Part file names matching ItemId_RevId_NonMasterTypeCode_DatasetName become Non-Master-Parts-ItemId/RevId/NonMasterType/DatasetName upon import. Part file names matching ItemId_RevId become Master-Parts-ItemId/RevId upon import. If neither of the previous conventions are used, the entire part file name is used as 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) become ItemID_RevID_NonMasterTypeCode_DatasetName upon export, where NonMasterTypeCode is a single letter code for the type of the nonmaster part (for example, 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: _A.prt (UGMASTER dataset) _A_m_TopAssyDwg.prt (UGPART with manifestation relation) _A.prt (UGMASTER dataset) _A_m_A1Dwg.prt (UGPART with manifestation relation) _A.prt (UGMASTER dataset) _A_m_D1Dwg.prt (UGPART with manifestation relation) _A.prt (UGMASTER dataset) Note Spaces in generated names are converted to underscores. PLM00123 G NX Remote Manager Guide 2-3

16

17 Chapter 3 Using NX Remote Manager Using NX Remote Manager Establish a remote export connection Remote connection behavior Send data to an existing connection Adding datasets to a remote connection Manually export data to a connection Refresh files in a remote connection Importing files from a remote connection to Teamcenter Import modified data in to Teamcenter from a remote connection Prevent files in a remote connection from being imported to Teamcenter Manually import data from a connection Set connections options Delete a remote connection View transaction logs PLM00123 G NX Remote Manager Guide

18

19 Chapter 3 Using NX Remote Manager Using NX Remote Manager NX Remote Manager shares files with remote users who have no access to the Teamcenter database. Data is exported, and after modifications are made the data is imported back in to Teamcenter. This works well for suppliers or for users who want to work independently with a laptop computer and then synchronize their data with the Teamcenter database. Remote connections manage files and associated information that is transferred back and forth between Teamcenter and the connection. The remote connection list shows all active and failed connections for the current user. A remote connection is independent of both the Teamcenter session and the application session. The connection keeps a history of data sent to the connection and the data received from the connection. You can have more than one connection open at any time to send data to multiple suppliers. This allows you to track what has been sent to and received from each supplier and also allows suppliers to work on multiple projects. Note The UGII_BASE_DIR and UGII_ROOT_DIR environment variables must be set to export item revisions containing UGMASTER datasets. If NX is installed locally, these variables are set automatically. However, if you access the NX network from a mapped drive, you must manually set these environment variables. Establish a remote export connection 1. 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 multiple suppliers. 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 PLM00123 G NX Remote Manager Guide 3-1

20 Chapter 3 Using NX Remote Manager exported. If the component is already checked out, or if you do not have write privileges 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 export directories reside for each connection. All files for a connection are exported to and imported from its export directory. If the connection export directory already exists when the system attempts to create it, the directory is preserved and any files in the directory are preserved and are not overwritten. Exports the primary named reference file(s) of the corresponding dataset to the connection export directory. If the dataset is the root of an assembly, the selected component files are exported. Creates a connection and adds it to your connection list. A remote connection is a database object used internally by the system. It manages all files and associated information that is transferred back and forth between the system and the connection. The remote connection list is the list of all connections (regardless of the application). The list contains all connections for active remote connections as well as all connections for remote connections that may have failed. Send data to an existing connection 1. Select a dataset in My Teamcenter. 2. Choose Tools Export To Connection. The system displays the Connection dialog box. 3-2 NX Remote Manager Guide PLM00123 G

21 Using NX Remote Manager You can export, add, resend, or refresh the connection from this dialog box. Adding datasets to a remote connection 1. 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 to check 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 the results for each. 4. Click OK. The system exports the selected files to the connection export directory. If all files 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. PLM00123 G NX Remote Manager Guide 3-3

22 Chapter 3 Using NX Remote Manager Manually export data to a connection 1. In the Connections dialog box, select a connection. 2. Click the Export to Connection button. Refresh files in a remote connection 1. 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 Teamcenter since the last export to the connection. If the file has been modified in Teamcenter but has not been modified in the connection, the system re-exports the selected file, its components, and its related files. 4. Click OK. The system updates the connection directory with all changes made in Teamcenter since the last export operation, including adding new components to the assembly, removing deleted components from the assembly, exporting new item revisions, and exporting new dataset revisions. 3-4 NX Remote Manager Guide PLM00123 G

23 Using NX Remote Manager Importing files from a remote connection to Teamcenter While working with a remote connection, you can send (import) modified data from the connection export directory back to Teamcenter. The following actions occur when you import modified files from a remote connection to Teamcenter: Files that have been modified in the connection export directory are imported as new file versions. Files that have not been modified in the connection export directory are skipped and not imported. Soft links in the connection export directory are not supported. Attempting to import 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. PLM00123 G NX Remote Manager Guide 3-5

24 Chapter 3 Using NX Remote Manager 4. Select any files that you do not want to import and choose Skip in the Action column. 5. Click OK. The system imports the files from the connection export directory. After the files have 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 to Teamcenter 1. Select a connection in the Connection Name column of the Connections dialog box. 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 dialog box. 3-6 NX Remote Manager Guide PLM00123 G

25 Using NX Remote Manager 2. Click the Import from Connection button. Set connections options Options for specifying the behavior of NX Remote Manager connections are listed under 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 tab Save log from deleted connections Export tab Export Directory Export read only files as read only Directs the system to save the transaction log file for each connection after the connection is deleted. The log file is saved in the top-level NX Remote Manager connection directory. The name of the file is the name of the connection followed by a number to make it unique. For example, a connection named UG-RM_001 has a corresponding transaction log file named UG-RM_001_6671.log. Allows you to define the top-level NX Remote Manager connection directory. This is the main directory where the system creates the export directory for each connection. Specifies how files associated with datasets to which you do not have write permission are exported. If this option is selected, those files are written in the connection export directory with read-only privileges. If not checked, all files are written to the export directory with read/write privileges. PLM00123 G NX Remote Manager Guide 3-7

26 Chapter 3 Using NX Remote Manager Named References to Export Specifies the named references to export to a connection. Valid values are: All Exports all named references of the dataset. Select Displays a dialog box for selecting specific named references to export. Primary Check out new components during refresh connection Import tab File types to ignore Import Details Master Exports the primary named reference for the dataset. Specifies that all items that can be checked out are checked out when the connection is refreshed. Defines the file types to ignore during import, such as backup files. Indicates if the user has permissions to modify import information in the XML files when importing them back to Teamcenter. Valid values are: Application User is not allowed to change the import information from Teamcenter. Both NX tab Copy non-master User is allowed to modify import information from Teamcenter. Enables the export of manifestation, specification and other nonmaster items. Part Family Members Autotranslate Mode Specifies how to process part family members during import/export. Specifies whether autotranslate mode is the default behavior or whether import should be legacy compatible. 4. Click Apply or OK. 3-8 NX Remote Manager Guide PLM00123 G

27 Using NX Remote Manager Delete a remote connection 1. In My Teamcenter, choose Tools Connection. 2. Select the connection, and click Delete Connection. The connection export directory is deleted, and the persistent connection is removed from your connection list and from the Teamcenter database. View transaction logs 1. 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 log viewer allows you to print the log file or save it as a text or HTML file. PLM00123 G NX Remote Manager Guide 3-9

28

29 Chapter 4 Importing and exporting assemblies Importing and exporting assemblies How Teamcenter imports and exports assemblies Connection export directory Exchange files High security Data manager tasks Export assemblies with BOM information Exporting without BOM information Check out a file Importing data from a remote connection Import data from a remote connection to Teamcenter Selecting item types during import Support of subdirectories within the connection directory PLM00123 G NX Remote Manager Guide

30

31 Chapter 4 Importing and exporting assemblies Importing and exporting assemblies NX Remote Manager enables you to import, export, check in, and check out datasets controlled from one location. When a top-level assembly is imported or exported, all subassemblies and components can be managed as well. How Teamcenter imports and exports assemblies To understand how Teamcenter imports and exports assemblies, you must understand 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 import operations of a connection. All files that are exported are accounted for in this directory, which is accessed by appending the connection export directory to a root directory (default or user specified). The connection directory allows a subdirectory structure if your application can support it. Exchange files NX Remote Manager writes and reads XML exchange files in the connection export directory. An XML file is written for each file that is exported. These files contain metadata such as product structure, attribute information, and timestamp information. NX Remote Manager uses this information to determine which files must be updated when a subsequent export or import operation is performed. These XML files must reside in the connection export directory for the duration of the connection. If the contents of the connection directory get moved or copied, the XML files must be moved or copied along with the application files. PLM00123 G NX Remote Manager Guide 4-1

32 Chapter 4 Importing and exporting assemblies High security NX Remote Manager exports files with read and write permissions. Those files that are 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 is referred to as high security and applies to all files that are managed by a connection. Data manager tasks A connection is created to support offline work or to manage a supplier data sharing environment. Certain functions, such as creating a new connection or deciding what data needs to be sent through the connection can only be done if you are a Teamcenter 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 and the data received from the connection. You can have more than one connection open at any time. This enables a single data manager to send data to multiple suppliers and keep track of what has been sent to and received from each supplier. Every connection has only one owner. The data manager that creates the 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 information 1. 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 the functionality available in the ug_clone command line utility. Variants and other configuration 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 initially empty. 4-2 NX Remote Manager Guide PLM00123 G

33 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 preference setting 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 be exported 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. PLM00123 G NX Remote Manager Guide 4-3

34 Chapter 4 Importing and exporting assemblies 7. (Optional) Apply export or checkout selections to an entire branch of the assembly 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 single components: 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 checked out (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. In addition, if you attempt to check out datasets that are currently checked out, the system automatically changes the status from Export+CO to Export. 4-4 NX Remote Manager Guide PLM00123 G

35 Importing and exporting assemblies 9. When your selections are complete, click OK. Exporting without BOM information When exporting an assembly without BOM information, you must first select an item or item revision. If you choose an item, the default revision rule specified by the preferences file is used to determine the appropriate item revision. Check out a file 1. 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 Remote Manager preference setting for the root directory location. You must specify a unique 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 for checkout, 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: Skip Files under this dataset are not exported. PLM00123 G NX Remote Manager Guide 4-5

36 Chapter 4 Importing and exporting assemblies Export Files under this dataset are exported but not checked out (read-only copy). Export+CO Files under this dataset are exported and checked out (read/write copy). Note You can only check out datasets to which you have write access. In addition, if you attempt to check out datasets that are currently checked out, the system automatically changes the status from Export+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 the connection. Importing data from a remote connection While working with a remote connection, you can import modified data from the connection 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 as new file versions. Files that have not been modified in the connection export directory are skipped and 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 existing ItemID/Rev-ItemName information for each primary file to be imported. 3. If you have more than one remote connection running, select a connection from the table. 4. Click Import in the Connection dialog box. The system analyzes the files to be imported. If no files have been modified or created, the system detects this and the import operation stops. The system displays the analysis results in the Comments column of the File(s) to Import dialog box. 5. Apply import options to the individual files using the Action list. The following options are available: Skip Excludes the file from the import operation. 4-6 NX Remote Manager Guide PLM00123 G

37 Importing and exporting assemblies Note Skip is the only option available if you do not have write access to the selected dataset. Import Implicit CO Implicitly checks out the dataset if it was not checked out at export and imports it to Teamcenter. Import Overwrite Imports the dataset and overwrites the existing dataset in Teamcenter. Import Next Rev Imports the dataset in to the next revision of the item and cancels checkout on the previous revision of the item. 6. After selecting the files to skip, click OK to import the selected files or Cancel to stop the import operation. If you selected Retain checkout, the connection directory is updated with the new 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 errors from 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 to select the item type to create within Teamcenter for storing the files. PLM00123 G NX Remote Manager Guide 4-7

38 Chapter 4 Importing and exporting assemblies The list of item types displayed depends on the dataset type specified in the XML file for the new file and the item types defined in the DMS (data model service) for the dataset type. Support of subdirectories within the connection directory If files exist in subdirectories under the main connection directory, the subdirectory information 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 in a subdirectory under the (new) connection directory. If a file is found more than once in the connection directory structure, only the first occurrence is imported and subsequent occurrences are ignored. This is captured in the transaction log file. 4-8 NX Remote Manager Guide PLM00123 G

39 Chapter 5 NX Remote Manager administration NX Remote Manager administration Register custom item types with NX Remote Manager Preferences and utilities Preferences AIE_named_refs_to_export AIE_overwrite_default_import_item_types AIE_skip_class_types_for_save AIE_POST_EXPORT_SCRIPT AIE_PRE_IMPORT_SCRIPT Utilities aie_clean_datamodel_objs aie_install_datamodel_objs BatchImp PLM00123 G NX Remote Manager Guide

40

41 Chapter 5 NX Remote Manager administration NX Remote Manager administration The NX Remote Manager requires ongoing administration which is performed using utilities and preferences. In addition, custom item types must be registered with NX Remote Manager before they can be used with integrated applications. Register custom item types with NX Remote Manager Note Custom item types must be registered with NX Remote Manager before they can be used with integrated applications. The following example registers custom item types for the NX Remote Manager. 1. Edit the accaddwg_dms.xml and acadtmpl_dms.xml files located in the ACAD_EM\Data directory by changing the existing item type to reflect the item type you want to use when new items are created. The following example illustrates the changes required to modify the item type from Item to CORP_Tool in the XML file. <Info Datasettype="ACADDWG"> <Create> <!-- <Value>[<itemtype>:<iMANrelation>:<viewtype>]</Value> --> <Value>Item:Specification:view</Value> <Value>Document:Manifestation</Value> <Value>Item:Manifestation:view</Value> </Create> <Info Datasettype="ACADDWG"> <Create> <!-- <Value>[<itemtype>:<iMANrelation>:<viewtype>]</Value> --> <Value>CORP_Tool:Specification:view</Value> <Value>Document:Manifestation</Value> <Value>CORP_Tool:Manifestation:view</Value> </Create> PLM00123 G NX Remote Manager Guide 5-1

42 Chapter 5 NX Remote Manager administration 2. Open the AdditionalInfo.xml file located in the AcadMgr_DIR\Support directory in a text editor and add the item types to the file. This file lists the item types that appear in the Boundary dialog boxes. The following example shows the AdditionalInfo.xml file. <?xml version="1.0" encoding="iso "?> <!-- Copyright (c) 2005 Unigraphics Solutions Unpublished - All rights reserved THIS PROGRAM IS AN UNPUBLISHED WORK FULLY PROTECTED BY THE UNITED STATES COPYRIGHT LAWS AND IS CONSIDERED A TRADE SECRET BELONGING TO THE COPYRIGHT HOLDER. The Item Types that will appear in the Boundary Dialogs that can be accessed from NX Remote Manager. Update this file if new Item types, which are known to Teamcenter Engineering, need to be supported by the Boundary Dialogs This is the GM Overlay version of this file. 28-Jun-2005 aputhenp Initial creation 28-Jun-2005 aputhenp The first line has to be?xml... $HISTORY$ --> <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 Teamcenter environment, 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, see aie_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 constant between versions of XML. If you do not specify the -modify argument for the aie_install_datamodel_objs utility, no modifications are performed. 5-2 NX Remote Manager Guide PLM00123 G

43 NX Remote Manager administration 4. If you do not have access to the XML files used to initially install the data model objects, run the following program to delete existing instances of the dataset types: aie_clean_datamodel_objs -dstype=all Note You can selectively delete instances corresponding to a particular dataset type by specifying a dataset type name for the -dstype= argument. For more information about the aie_clean_datamodel_objs utility, see aie_clean_datamodel_objs. 5. After deleting the dataset type instances by running the aie_clean_datamodel_objs utility, run the aie_install_datamodel_objs utility without the -modify argument to populate the data model instances. Preferences and utilities Preferences and utilities are used to set up and configure NX Remote Manager. Preferences Preferences are used to configure NX Remote Manager. Preferences are environment variables stored in the database and are read when a Teamcenter session or a session of an integrated application is initiated. For more information about preferences, see the Preferences and Environment Variables Reference. PLM00123 G NX Remote Manager Guide 5-3

44 Chapter 5 NX Remote Manager administration AIE_named_refs_to_export DESCRIPTION Allows you to specify the named references to export to a connection. VALID VALUES DEFAULT VALUE all select primary primary Exports all named references of the dataset. Displays a dialog box allowing you to select the named references to export. Exports the primary named reference of the dataset. DEFAULT PROTECTION SCOPE Site preference. 5-4 NX Remote Manager Guide PLM00123 G

45 NX Remote Manager administration AIE_overwrite_default_import_item_types DESCRIPTION Controls whether the default item types can be overwritten during import using NX Remote Manager. VALID VALUES DEFAULT VALUE on off on Allows the user to choose from all item types listed in the DMS when importing new or previously exported files. Disables item type selection when importing files. Files that were previously exported from Engineering Process Management are imported using the item type assigned when they were exported, and new files are imported using the default item type. DEFAULT PROTECTION SCOPE Site preference. PLM00123 G NX Remote Manager Guide 5-5

46 Chapter 5 NX Remote Manager administration AIE_skip_class_types_for_save DESCRIPTION VALID VALUES DEFAULT VALUE DEFAULT PROTECTION SCOPE Specifies item types that must not be displayed as options in the Item Type list in the 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 a choice when items are saved in NX Remote Manager. Any valid item type for which creation is disallowed. This preference is unset in the Engineering Process Management environment. In the Teamcenter Automotive Edition GM Overlay environment, the default value is Item. Site preference. 5-6 NX Remote Manager Guide PLM00123 G

47 NX Remote Manager administration AIE_POST_EXPORT_SCRIPT DESCRIPTION VALID VALUES DEFAULT VALUE DEFAULT PROTECTION SCOPE Specifies a fully qualified path to an executable script that are executed after the completion of NX Remote Manager export operation. Path to the script. This path must not contain special characters or spaces. In addition, the path separator must be in accordance with the platform on which the script 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 By default, this preference is not set. Site preference. PLM00123 G NX Remote Manager Guide 5-7

48 Chapter 5 NX Remote Manager administration AIE_PRE_IMPORT_SCRIPT DESCRIPTION VALID VALUES DEFAULT VALUE DEFAULT PROTECTION SCOPE Specifies a fully qualified path to an executable script that will be executed before the NX Remote Manager import operation begins. Path to the script. By default, this preference is not set. Site preference. Utilities Command line utilities are used to install and maintain the NX Remote Manager data model and to import files in batch mode. For more information about utilities, see the Utilities Reference. 5-8 NX Remote Manager Guide PLM00123 G

49 NX Remote Manager administration aie_clean_datamodel_objs DESCRIPTION SYNTAX Deletes instances of a specific dataset type or instances of all dataset types from the NX Remote Manager data model. aie_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. ENVIRONMENT FILES RESTRICTIONS EXAMPLES As specified in Configuring utilities. As specified in Log files. None. 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 the UGMASTER dataset type: aie_clean_datamodel_objs -u=infodba -p=password -g=dba -dstype=ugmaster PLM00123 G NX Remote Manager Guide 5-9

50 Chapter 5 NX Remote Manager administration aie_install_datamodel_objs DESCRIPTION SYNTAX Adds, modifies, and deletes data model definitions based on customer-defined item types. aie_install_datamodel_objs -u=user-id -p=password -g=group -file=dms_definition_file [-modify=yes] ARGUMENTS -file -modify Specifies the name of the file containing the NX Remote Manager data model definition. The NX Remote Manager data model file is written using XML syntax, which must follow the document type definition in the dms.dtd file. Specifies whether the NX Remote Manager data model is overwritten. The value yes overwrites the data model. ENVIRONMENT FILES RESTRICTIONS EXAMPLES As specified in Configuring utilities. As specified in Log files and the aie_install_datamodel_objs183e5050.log and aie_install_datamodel_objs183e5050.jnl files. The -modify argument must only be used with the value yes. If the aie_clean_datamodel utility was previously run for the same dataset type, you do not need to specify the -modify argument. The following example registers the UGMASTER dataset with NX Remote Manager by 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 5-10 NX Remote Manager Guide PLM00123 G

51 NX Remote Manager administration BatchImp DESCRIPTION SYNTAX ARGUMENTS Imports multiple files in to the Teamcenter database without starting the integrated CAD application. BatchImp [-r] [-q] [-n] input-file-name -u=user-id -p=password -g=group [-f=teamcenter folder] [-n ] [-x] [-xml] [-d=dataset-type] [-dryrun] input 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 to Teamcenter, it should be imported under a new item revision. This argument is optional. -q Specifies whether the user should be prompted for each previously imported drawing to be reimported. If the drawing is to be imported as specified by the user, the -r option is used to determine whether a new item revision is created. This argument is optional. -n Specifies that only those drawings that have not previously been imported in to Teamcenter are imported. This argument is optional. -x Specifies that the batch import only creates the according IXF files and uses the aie_batch_import.exe utility to perform the import operation. If this argument is not specified, the batch import.arx file 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 Teamcenter database. It is intended to create the IXF files that are required when 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 Security Services is enabled. If SSO is enabled, this argument is not necessary 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 Security Services is enabled. If SSO is enabled, this argument is not necessary and is ignored if provided. -g Specifies the group of the user logging in to the Teamcenter database. This argument is required. -f Specifies the Teamcenter folder in which items or item revisions are created for the imported files. If not specified, the default is the Newstuff folder. This argument is optional. -d Specifies the dataset type of the Teamcenter dataset object to which the imported files are attached. PLM00123 G NX Remote Manager Guide 5-11