NXI5_WINInstl

NX I-deas 5

Installation Guide for Microsoft® Windows®

A guide for installing the NX I-deas 5 software on supported Microsoft® Windows® systems; Windows XP and Windows Vista.

. Proprietary & Restricted Rights Notice

© 2007 UGS Corp. All Rights Reserved. This software and related documentation are proprietary to UGS Corp. LIMITATIONS TO U.S. GOVERNMENT RIGHTS. UNPUBLISHED - RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. This computer software and related computer software documentation have been developed exclusively at private expense and are provided subject to the following rights: If this computer software and computer software documentation qualify as "commercial items" (as that term is defined in FAR 2.101), their use, duplication or disclosure by the U.S. Government is subject to the protections and restrictions as set forth in the UGS Corp. commercial license for the software and/or documentation, as prescribed in FAR 12.212 and FAR 27.405(b)(2)(i) (for civilian agencies) and in DFARS 227.7202-1(a) and DFARS 227.7202-3(a) (for the Department of Defense), or any successor or similar regulation, as applicable or as amended from time to time. If this computer software and computer documentation do not qualify as "commercial items," then they are "restricted computer software" and are provided with "restrictive rights," and their use, duplication or disclosure by the U.S. Government is subject to the protections and restrictions as set forth in FAR 27.404(b) and FAR 52-227-14 (for civilian agencies), and DFARS 227.7203-5(c) and DFARS 252.227-7014 (for the Department of Defense), or any successor or similar regulation, as applicable or as amended from time to time. UGS Corp., Suite 600, Granite Park One, 5800 Granite Parkway, Plano, Texas 75024.

All trademarks belong to their respective holders.

Contents

iii

New Features

New Features for NXI-deas Installation 1

Installation Process Changes 2 New Name for Installation Location 2 Changes to IDEAS_PARAM and Site-Wide Parameter File 2 Licensing Changes 2

Installation

Chapter 1 Preparing to Install NX I-deas 5

Installation Requirements 6 What You Received 6

Optional 7 System Requirements 7

Installation Recommendations 7 Installation Preparation 8

Set Up the System 8 Set Up an NX I-deas Administrator Account 8 Set Up User Accounts 8 Review Required Operating System Tasks 9

Preparing to Install Licensing 9 Obtaining Your License File 9

iv

Chapter 2 Distributed NX I-deas Installation 11

Distributed Installation Setup Guidelines 12 How to Create a Distributed NX I-deas Installation 13

Server Workstation Tasks 13 Client Workstation Tasks 14

Automating Installation 16 How to Use the Windows Installer Option to Install I-DEAS 16 Troubleshooting 17 More Information on the Windows Installer Option 18

Chapter 3 Installation Migration 21

Migration Overview 22 Migration Process 22 Migration Considerations 22 Migrating from Older Releases 22

Preparing your Data for Migration 24 Migrating the Installation 27

Data Products Migration 30

Chapter 4 Install NX I-deas 5 31

Install the License Server 33 Install the Prerequisite Software 33 Install NX I-deas 36

Chapter 5 TDI Wizard 39

Running the TDI Wizard 40 Create and publish a Team Data Installation 41

Parameter Entries Modified during Parameter File Creation 45 Connect to an existing Team Data Installation 46 Registry Entries Created by the TDI Wizard 46 Running the TDI Wizard as a Regular User 47

Order of Precedence of TDI Settings for I-DEAS Runtime 47 Install Data Products 48

Chapter 6 Install Help Library 49

Help Library Overview 50 Installation Considerations 50

Help Library 50 Help Library Software Requirements 51 Help Library Access to the Web Browser 51 Browser Setting Requirements for Help on Context 51

v

Web 52 Installation Procedure 53 I-DEAS Access to the Help Library 55

Chapter 7 Advanced Installation Options 57

Running Software from a Server 58 Command Line Installation Options 62

Product Feature Names 63 Optional Product Feature Names 63 Language Interface Feature Names 64 Windows Installer Service Additional Information 65

Customizing Product Databases 65

Chapter 8 Uninstall 67

Uninstall an I-DEAS Installation 68 Uninstall Help Library 68

Chapter 15 Troubleshooting 69

Errors During the Installation Process 70 IDEAS_PARAM12 and SDRC_MPATHS are not defined 70 Time Out Warning 70 I-DEAS Customer Support 71

Appendix A Configuring I-DEAS Stand Alone Solver A-1

Installing QMan and SAS A-2 Configuring I-DEAS to Run SAS A-2 Configuring QMan Client – Server for Batch Solves A-3

Configuring QMan Client – Server for Local Batch Jobs A-3 Configuring QMan Client – Server for Remote Batch Jobs A-4

Appendix B I-DEAS Installation Files B-1

File Placement Table B-2 Files Generated by I-DEAS B-2

1

New Features for NX I-deas Installation

NX I-deas 5 incorporates enhancements and new capabilities to increase the flexibility and ease of use of the software.

This section covers information that affects the installation of the software.

Note: The NX I-deas 5 installation software for Windows is compatible with Microsoft Windows 2000, Microsoft Windows XP and Microsoft Vista operating systems.

2

Installation Process Changes

The NX I-deas installation programs have been converted to Microsoft MSI Windows Installer installations. The process of installing NX I-deas has changed dramatically with this conversion. It is recommended that you read this installation guide to familiarize yourself with the process of installing NX I-deas 5 before beginning an installation.

Significant changes from previous environmental settings for I-DEAS by the installation programs will be identified with “Installation Change:” in bold type throughout this guide.

New Name for Installation Location

The name of the default path for the NX I-deas installation location has changed to:

...\UGS\NXI5

Changes to IDEAS_PARAM and Site-Wide Parameter File

The name of the environment variable that directs NX I-deas software to the site-wide parameter file has changed. For I-DEAS 12, the environment variable was named IDEAS_PARAM21; for NX I-deas 5, it’s IDEAS_PARAM13. This means users who have the IDEAS_PARAM13 environment variable defined can’t accidentally access an earlier version data site when they start the current version of the software.

In addition, the name of the site-wide parameter file has changed from ideas_param1 2.dat to ideas_param13.dat.

The following path shows the default location for this file.

<drive>:\Team\Master\Config\ideas_param13.dat

The Team parameters are extracted from the ideas_param13.dat file. If the location of the ideas_param13.dat file is not explicitly defined somewhere else, it is defined by the IDEAS_PARAM13 environment variable in %SDRC_INSTL%\bin\Setup_Varbs.cmd.

Licensing Changes

NX I-deas 5 license servers and applications use FLEXlm version 10.8.2.1 on SUN, HP, and 10.8.5 on Windows.

The NX I-deas 5 release uses the UGS common license server for license management. This change removes the use of NX I-deas passwords for license file generation. License files are provided directly from UGS instead of passwords. Instructions for obtaining license files are included later in this guide.

Some products are now implemented as license bundles. This enables license sharing with NX. Users need to include a new environment variable on their hardware systems to operate these bundles. Set the new variables as:

UGII_FLEX_BUNDLE = A026 or A026G for NX I-deas MasterFEM

New Features for NX I-deas Installation 3

or

UGII_FLEX_BUNDLE = A027 for NX Nastran Desktop with NX I-deas MasterFEM

Additional bundles are available and will be identified in your license file with the PACKAGE line name. If a bundle other than A026, A026G, or A027 exists in the license file, set the UGII_FLEX_BUNDLE variable to the bundle name immediately following the PACKAGE word on the license file line.

Chapter 1

5

Preparing to Install NX I-deas

The NX I-deas engineering software supports NX I-deas users in a concurrent work environment. As the NX I-deas administrator, you must install and maintain both the executable software and the data management environment, which enables users to manage and share the data they generate.

This chapter lists installation requirements and tasks you should perform to prepare for installation.

Note: To find out which versions of third-party products are supported in a specific release of NX I-deas, see the documentation provided with those products.

6

Installation Requirements

To install NX I-deas software, you’ll need:

• a Windows system that meets the minimum system configuration requirements as defined on the support web site at http://support.ugs.com

• a local hard disk with a partition large enough for all the NX I-deas software you intend to install, and a disk on which you can set up your NX I-deas data management installation

• an NX I-deas administrator account to use for NX I-deas software installation and administration. The account must have local administrator group privileges during installation of the software.

• a software license, which can be requested via e-mail, fax, telephone, or the web, according to the instructions provided later in this guide.

What You Received

In your NX I-deas shipment, you received the following items that you need for installation:

• one or more NX I-deas DVDs for each platform at your site

The guides and notes listed below are delivered as .pdf files on the Readme directory of the installation DVD. It’s recommended that you review the following documentation to prepare for installing the NX I-deas software:

• the NX I-deas Site Planning and Implementation Guide, which helps you determine the NX I-deas installation and data management environments that best suit your engineering environment

• this Installation Guide for Windows

• the NX I-deas 5 Release Notes, which contain last minute information about the NX I-deas software and installation

Preparing to Install I-DEAS 7

Optional

• a Drafting Symbols Catalog CD. The Drafting Symbols Catalog CD contains an independent installation program that will start when the CD is inserted into a drive.

Note: Drafting symbols were not updated for I-DEAS 8, I-DEAS 9, I-DEAS 10, I-DEAS 11, I-DEAS 12 or NX I-deas 5, so if you have a Drafting Symbols Catalog CD with MS7, you will not receive another one with this release. The installation program will prompt you for the MS7 CD.

• a Mold Design Course CD. This CD contains separate installation programs for each supported platform. See the README.html (or README.txt) file on the CD for installation instructions.

System Requirements

The latest configuration settings and system requirements are defined on the support web site at http://support.ugs.com.

Installation Recommendations

Consider the following when installing NX I-deas:

• Follow the conventions for naming directories, establishing user accounts, setting system parameters, and so on, which are specified in this guide. The recommendations create an installation that’s easy to maintain and troubleshoot.

Note: Throughout this guide, NX I-deas X is used where X represents the software version number.

• Use consistent, concise path names for team data directories, user home directories, and NX I-deas software locations. NX I-deas cannot resolve paths that include spaces or are longer than 80 characters (including the filename).

Note: It is recommended that NX I-deas software be local to each workstation. Consistent path names to team data are necessary.

8

Installation Preparation

Before installing the NX I-deas software, complete the following tasks.

Set Up the System

Verify the following system setup prior to NX I-deas installation:

• A DVD-ROM drive is attached to the local workstation or to a mapped network drive.

• The ethernet adapter (for licensing) is installed and configured.

• The TCP/IP protocol software is installed and configured for the desired adapter.

• The disk is NTFS formatted. (NTFS is the required file system for NX I-deas data.)

Set Up an NX I-deas Administrator Account

Set up a unique account, such as ideasadm, to use only for NX I-deas installation and administration. This account must be a member of the local administrator group, giving it administrator rights on the local machine during installation. It is recommended that administrative privileges be removed after installation and configuration of NX I-deas in order to enhance system security.

Refer to your Windows operating system documentation for instructions on how to set up an administrator group account.

Certain tasks, which are performed automatically by the NX I-deas installation program, require administrator rights. These tasks include:

• Installing shared software.

• Installing operating system components .

• Creating common startup icons/icon groups for NX I-deas.

• Configuring the Windows Firewall (if present).

• Installing the required NX I-deas services and components.

Set Up User Accounts

Set up user login accounts with defined local home drives and home paths and temporary folders.

Installation Change: In previous versions of I-DEAS the installation defaulted the working directory to %HOMEDRIVE%%HOMEPATH%. This has now been changed to default to %TEMP% folder.

Preparing to Install I-DEAS 9

By default, the I-DEAS installation software icons define the working directory as %TEMP%. If a user does not have a %TEMP% defined, the system will probably use C:\Documents and Setting\%username% as the home directory, by default. Since this path includes spaces, it is recommended that set a %TEMP% folder without spaces or use the command line option of the installation program to set the working directory to a pre-defined location. Use of the command line options for installing I-DEAS will be described later in this guide.

It is recommended that you use the DataMgmt.UserDirectory and DataMgmt.ScratchDirectory in the NX I-deas parameter file instead of the Start In folder of the shortcuts to set the locations for files to be written and read from for your NX I-deas users. A default location can be set in the global NX I-deas parameter file and users can set their own locations on the Options->Preferences, Data Management… form in NX I-deas. These locations should be set to directories that do not contain spaces.

Review Required Operating System Tasks

This guide assumes a certain level of experience administering a Microsoft Windows operating system. You should be able to complete the following tasks in order to successfully install and administer the NX I-deas software. The procedures for these tasks are not explained in this guide:

• Create a user account

• Create files and directories

• Edit network system files, such as etc\hosts

• Set permissions on files and directories

• Create shortcuts

• Map network drives

• Start and stop services

• Edit registry entries

Preparing to Install Licensing

The license server installations assume at the appropriate point during license configuration, you can obtain or have obtained your license file from UGS GTAC (or your appropriate contact) and have it stored on disk accessible to the license server installation program.

Obtaining Your License File

To be able to use the license management software, you should contact UGS Global Technical Access Center (GTAC) to receive your NX I-deas/NX license file. Use your web browser to navigate to http://support.ugs.com to have UGS send your product license file to you. Please note that you will need a WebKey account to access the product licensing features of the GTAC web site.

10

If you are using a network license, you will need to supply GTAC with the UGS Common Licensing composite hostid of the computer that will run the FLEXlm License Server. See the UGS Licensing.pdf, and ugslicensing_user_guide.pdf files on the NX I-deas installation media for information on obtaining your composite hostid for all supported platforms.

MTS Test customers should contact MTS for a license file.

After you receive your license file, copy it to disk on your license server workstation and then use the NX I-deas/NX license server installation program to copy and rename the file into the appropriate place for license management.

More information on the license management system can be found in the UGS Licensing.pdf and ugslicensing_user_guide.pdf files on the installation media.

Chapter 2

11

Distributed NX I-deas Installation

You can install NX I-deas software executables on multiple client workstations and still have the benefit of concurrent engineering through shared licenses and shared data.

This can be accomplished by creating a distributed NX I-deas installation.

This chapter describes the following:

• the process used to create a distributed NX I-deas installation

• how to use Windows Installer to set up a distributed installation

Refer to the Site Planning and Implementation Guide for information on planning your configuration.

12

Distributed Installation Setup Guidelines

Use the following guidelines when setting up a distributed NX I-deas installation:

• Use consistent drive letter and path name conventions for the NX I-deas software installation on each client.

This is recommended for easier system administration, but is not required.

• The NX I-deas license manager and MTS License manager services must be installed on a local, fixed (non-mapped) drive.

This ensures that the license manager is available for automatic startup when the system is booted.

Note: The installation software will not allow installation of the license service on a removable or mapped drive.

• NX I-deas software should be installed on a local disk to ensure optimum performance of the NX I-deas applications software.

Note: If you plan to use the mapped drive installation on your client machines, the NX I-deas software will be installed on the server, not a local disk. Running NX I-deas over a network will increase network activity, so be sure your network can handle the increased traffic. See the Site Planning and Implementation Guide for additional information.

Note: The NX I-deas installation path cannot include spaces as NX I-deas cannot handle Windows long file names.

• Use consistent team drive mappings across clients running NX I-deas.

This is required for team data sharing. Failure to follow this requirement will result in error messages upon NX I-deas startup.

• Don’t locate the team data installation on a boot drive.

It’s undesirable to share a boot drive because the amount of disk I/O caused by data reads and writes can:

• degrade the performance of the OS

• fragment the OS drive

• degrade the speed of NX I-deas data read/write activity

• create an undesirable security risk

Distributed NX I-deas Installation 13

How to Create a Distributed NX I-deas Installation

The process for creating a distributed NX I-deas installation requires that some tasks be performed on the server workstation and others on the client workstations.

Before you begin this process, determine which installation configuration you want to set up, including the location and path of the shared team data installation.

See the Site Planning and Implementation Guide for guidelines on installation configurations and team data installation setup.

Server Workstation Tasks

Perform the following tasks to set up the server workstation:

1. Install the desired license server(s).

The NX I-deas media contain several different license server programs. Normally only the NX License Manager is required for NX I-deas products, however, if you have purchased any MTS Systems products you will need to install the MTS Test License Server as well.

2. Install the NX I-deas prerequisites.

If you intend to serve a Team Data Installation (TDI) from the Server or you intend to serve NX I-deas code, you must install the NX I-deas prerequisites. You may either use the wizard that is started from the Launch screen or you can manually install the software which consists of the Java 1.5.0_06 SDK and the Open NX I-deas Server (Orbix).

Manual installation of these packages allows you to customize various properties such as installation folder and TCP/IP ports used for the packages.

3. Install NX I-deas.

If you intend to serve code, you should select all products that you want to allow your users to access and install them.

If you simply want to serve a Team Data Installation (TDI), you should use the selection list in the Custom Setup window to deselect the unnecessary features that are pre-selected for you. To deselect a feature and its sub-features, click on the feature and pick “This feature will not be available”.

You should ensure that at least one product underneath the “Design Product Group” feature is selected for installation in order to install the tools required to manage the Team Data Installation.

1. Create The Team Data Installation (TDI) .

Run the TDI Wizard from the NX I-deas 5 program group in the start menu in order to create your TDI. Ensure that the folders that you select are local drives that can be mapped with a consistent drive letter and path by all client workstations that will connect to the TDI.

14

The TDI Migration wizard will automatically install the NX I-deas Resource Lock Server and Open NX I-deas Server (Orbix) for you into the “Program Files” folder of your Windows partition. If you want to manually install the NX I-deas SFAM Component or the NX I-deas Resource Lock Server in order to change the default installation location, you should use the Windows Installer Packages located on the first disk of the NX I-deas media. This option allows you to modify the installation folder as well as various other properties of the packages.

If you wish to catalog NX I-deas data products, you should do so now. See the instructions in the Install Data Products section of chapter 5.

2. Share your Team Data Installation (TDI) folders.

Share the TDI folders using share-level security in order to secure your data.

3. Ensure that the team disk is scheduled for backup on a regular basis.

Note: It is recommended you use one of the Windows Server products for the operating system of your server in order to ensure that you do not violate your Microsoft Software Agreement.

For details, please see the license that came with your copy of Windows.

Client Workstation Tasks

Perform the following tasks on all client workstations you set up:

1. Map the Team Data Installation directories from the server workstation using the same drive letters that were used on the server. This letter must also be available on all clients.

2. Install the NX I-deas prerequisite software.

3. Install the desired NX I-deas products.

During the installation process, you should ensure that the server computer is selected as the license server for the software.

4. Run the TDI migration wizard from the NX I-deas 5 product group in the Start menu and select the option; “Connect to an existing Team Data Installation”.

Follow the prompts of the TDI wizard. Make sure that you choose or enter the ideasadm account and enter the password in the “Select Heterogeneous Team Account” page of the wizard. As stated in Chapter 1, after you install NX I-deas with your ideasadm account, you should remove the administrator privileges on the account so that the SFAM Component user authentication does not pose a security risk in your network.

During the installation process:

a. The TDI Migration wizard will install and configure the NX I-deas SFAM Component if it is not already present.


b. The TDI Migration wizard will set the default Team Data Installation (TDI) for the local machine to the selected TDI.

5. Verify the client workstation setup:

a. Run NX I-deas.

Select Start->Programs->NX I-deas X->NX I-deas X.

b. Create some simple geometry and check it into a library.

You may also want to browse the library data using Manage Libraries and perform some sample library retrievals to verify that you can interact with the libraries. Also, open any migrated model files to verify that the associations exist.

16

Automating Installation

Installation of NX I-deas software can be automated using the various options and exposed properties of the Windows Installer packages that are delivered on the NX I-deas media.

Automating your installations can be useful in situations where tasks must be repeated many times such as when setting up a distributed NX I-deas installation, where the various setup tasks must be repeated on each client workstation. Automating the installation tasks can help reduce your workload immensely.

Automation of the NX I-deas Windows Installer packages enables the system administrator to script the NX I-deas installation components in order to only install those components that are required on each computer.

How to Use the Windows Installer Options to Install NX I-deas

The following information will assist you in manually installing NX I-deas packages onto your computer. This information can also be used in order to script NX I-deas installations on multiple machines.

1. Determine the package(s) that you want to install

Each installable package for NX I-deas is located in a file with a “.msi” extension. Some packages such as the Java installer are single-file packages with an “.exe” extension. Each package is located within a separate directory on the NX I-deas media.

There are several packages that are required for installation of the NX I-deas software; however, the NX License Server and MTS Systems License Server software have no requirements beyond the correct version of the operating system.

2. Determine the package properties to modify

Each .msi package may be installed using the Windows Installer executable msiexec.exe from a command prompt window as shown in the following example

msiexec.exe /i “NX I-deas NX Series.msi” INSTALLDIR=D:\UGS\IDEAS12 STARTINDIR=C:\ ideaswrk

The above command installs the default NX I-deas packages (A001 and A002 products and the Archive Reader/Writer and Design Examples optional products) into the folder D:\UGS\IDEAS12 by setting the INSTALLDIR property on the command line. By setting the STARTINDIR property on the command line it als o creates the shortcuts to NX I-deas with a Start In folder of C:\ ideaswrk.

There are various properties that are available for modification via the command line for each package. Additionally, by downloading the Microsoft Windows Platform SDK and using the tools in the SDK you can access the complete Windows Installer database for each package.


More information regarding the customizable properties of each Windows Installer package is included at the end of this chapter.

3. Install the package(s) via the command line or script

Run the selected Windows Installer package by running the msiexec.exe program with the proper switches and options.

Note: A complete list of available command-line options for the msiexec.exe executable can be seen by using the “/?” option.

Note: If you are scripting your installation by using a batch file or a Windows Script Host script, it is a good idea to create a restore point on your computer in the event that the script has errors in it.

Note: Packages should be installed in the following order if you plan to install a stand-alone system. For client systems in which the License Server(s) and Team Data Installation reside on a remote server, you should skip the installation of the first two packages.

1. UGS NX4.0 FLEXlm.msi located in the Licensing\NX4 folder on first CDROM of the media.

2. MTS Systems License Server,msi located in the Licensing\MTS folder on the first CDROM of the media.

3. Java.msi located in the Java folder on the first CDROM of the media.

4. Orbix.msi located in the Orbix folder on the first CDROM of the media.

5. NX I-deas NX Series.msi located in the IDEAS\I386 folder on the first CDROM of the media.

6. ResourceLocking.msi located in the ResLock folder on the first CDROM of the media.

7. NX I-deas SFAM Component.msi located in the SFAM folder on the first CDROM of the media.

4. Verify the client workstation setup by running the NX I-deas software.

Select Start->Programs->NX I-deas X-> NX I-deas X .

Troubleshooting

There are many things that can go wrong when installing Windows Installer packages by hand. Fortunately the Windows Installer Service includes many detailed debugging tools and options.

When installing Windows Installer packages by hand, always consider setting the command line option to create a log file of the installation. Always using the logging option will speed up error identification and troubleshooting.

18

In addition to the command line options provided by the Windows Installer Service itself, there are several external tools that are provided in the Windows SDK which is free for download from Microsoft.

Chief among these free tools is Orca which allows you to “peek inside” the Windows Installer database and manually modify settings in order to make a customized installer for your site.

More Information on Windows Installer Options

The following tables show the public properties that are available for modification by the end-user via the command-line and the purpose of each property

UGS NX 4.0 FLEXlm.msi

INSTALLDIR The folder into which the package is installed

.

MTS Systems License Server.msi


LICENSEFILE The MTS Systems license file

Java.msi


ALLUSERS Determines if the product is installed shared for all users (1) or just the person performing the installation (2).

Orbix.msi


DOMAIN_NAME The name of the default domain created for the ORB

NODE_DAEMON_PORT The default TCP/IP port for use by the ORB node daemon.

NAME_DAEMON_PORT The default TCP/IP port for use by the ORB name daemon.

CFR_DAEMON_PORT The default TCP/IP port for use by the ORB configuration repository daemon.

LOCATOR_DAEMON_PORT The default TCP/IP port for use by the ORB locator daemon.


NX I-deas NX Series .msi


DEFAULT_TDI The value to be used for IDEAS_PARAM12

FLEXLM_PORT The port number to be used for the NX License Manager

LICENSESERVER The name of the machine on which the NX License Manager is installed.

MTS_FLEXLM_PORT The port number to be used for the MTS Systems License Manager

MTS_LICENSESERVER The name of the machine on which the MTS Systems License Server is installed.

SDRC_MPATHS The value to be used for the NX I-deas Help Library.

STARTINDIR The value to be used for the Start in directory for the NX I-deas program shortcuts

JAVA_HOME The path to the folder where the selected version of Java has been installed

IT_PRODUCT_DIR The folder in which the IONA E2A ORB (Orbix) was installed

IT_DOMAIN_NAME The name of the domain to use with the IONA E2A ORB (Orbix)

ResourceLocking.msi


SERVICENAME The display name of the resource locking service.

FLEXLM_PORT The TCP/IP port used by the service.

Note: The NX I-deas SFAM Component package does not contain any useful modifiable public properties.

For more information about the options provided by the Windows Installer Service and the tools provided by the Windows Platform SDK, please visit the following internet site:

http://msdn.microsoft.com/library/en-us/msi/setup/windows_installer_start_page.asp?frame=true

For additional information on command line options of the packages included on the NX I-deas media, see the Command Line Installation Options section of Chapter 7.

Chapter 3

21

Installation Migration

Migration involves preparing an existing data installation(s) for access by the new version of NX I-deas and installing a new version of NX I-deas software.

This chapter describes the procedures for migrating your NX I-deas software and data installation(s).

22

Migration Overview

After you migrate a data installation, you will be able to use NX I-deas 5 to access the existing data.

CAUTION: After data is migrated to NX I-deas 5, it cannot be accessed by a previous version of NX I-deas.

Migration Process

Migration of the .imd and all .pmd files must be done at one time by an administrator, using dmadmin, before any users can access NX I-deas 5. Once the installation has been migrated, library and model file data automatically migrates when accessed by users.

The migration procedure gives all library items a new identifier, known as a GUID (Globally Unique Identifier). Model file references to library items are tracked (using the library items’ GUIDs) in a mapping table, which is created during migration. Since this table is not updated again, all GUIDs for migrated items must be assigned when the table is created. Therefore, the .imd and all .pmd files must be migrated at one time.

If you import a project at a later time, rather than migrating it with the rest of the data installation, it will be assigned a GUID, but this GUID will not be included in the mapping table. Since the mapping table will not be updated again, model file references to that project are lost.

See the Site Planning and Implementation Guide for additional information on planning for NX I-deas migration.

Migration Considerations

NX I-deas data is not backward-compatible. Once it’s accessed by the new version of NX I-deas, it can’t be accessed by a previous version. To ensure data integrity, please follow the recommended preparation and migration procedures.

Using a new version of NX I-deas may include a learning curve for some users. This depends on which NX I-deas applications are in use and the number and types of changes to their functionality for the new software release.

If the product development status of a particular project(s) is at a critical stage, you may want to postpone migration of the installation. Migrate the installation later, when there’s time to allow for the learning curve.

NX I-deas 5 code cannot be used to prepare for the migration. It must be done with the current software version. So it is important not to uninstall the current version of NX I-deas software until migration preparation is complete.

Migrating from Older Releases

You can migrate Artisan and/or Master Series (through I-DEAS 12) data installations to NX I-deas 5. Therefore, you will have one of the following situations:

Installation Migration 23

• Migrating only an Artisan installation(s) to NX I-deas 5.

To migrate an Artisan 4 installation, follow the procedures in the next sections, Preparing your Data for Migration and Migrating the Installation .

To migrate an installation(s) from a pre -Artisan 4 release, first migrate to Artisan 4 (see the Installation Migration chapter in the NX I-deas Artisan Installation and Migration Guide for Artisan 4), and then continue with the next sections.

• Migrating only a Master Series through I-DEAS 12 installation to NX I-deas 5.

Follow the procedures in the next sections, Preparing your Data for Migration and Migrating the Installation.

• Migrating both an Artisan installation and a Master Series installation into one NX I-deas 5 installation.

Complete the following procedures and then continue with the next sections, Preparing your Data for Migration and Migrating the Installation.

When migrating both Artisan and Master Series data installations into one NX I-deas 5 data installation, the recommended approach is to first export Artisan 4 library data to the Master Series installation.

If you are using Artisan 3, you must first migrate to Artisan 4. To do so, see the Installation Migration chapter in the I-DEAS Artisan Installation and Migration Guide for Artisan 4.

To migrate both Artisan and Master Series installations into one NX I-deas 5 installation:

1. In Artisan 4, use the data sharing functionality to create a package file.

a. Check in your data to the library.

b. In I-DEAS, pick File, Export, NX I-deas Library Data to display the I-DEAS Export form. If necessary, double-click to expand the project and the library.

c. Shift-click to select all library items that you want to export. You may want to select All in the View drop-down list to display all types of library items.

d. Select the Export for Checkout toggle. This option enables users in the importing installation to check out and modify the items.

e. Type in the full path and the new filename for the package file so that it is written to the new directory you created in step 1. (You cannot create a new directory from this form.) The path and the filename combined cannot exceed 80 characters.

f. Pick Export. I-DEAS writes all selected items to a package file.

g. Send the package file to a directory you can access from the Master Series installation.

24

2. In the Master Series (through I-DEAS 12) data installation, import the package file.

a. Pick File, Import, I-DEAS Library Data to display the I-DEAS Import form.

b. Type the name of the package file (*.pkg) or use the file folder icon to find it on your operating system.

c. Pick the green “activate” button or press Enter to list the contents of the file.

d. Pick Options, Check for Conflicts to display a report of any errors and information messages that will be generated as a result of the import. This allows you to resolve the problems before continuing with the import.

e. Pick Import. The file type is checked prior to importing.

The Artisan data and Master Series data are now combined in one Master Series data installation.

3. Migrate this Master Series data installation to NX I-deas 5. Complete the procedures in the next sections, Preparing your Data for Migration and Migrating the Installation.

Preparing your Data for Migration

To avoid the possibility of data corruption, complete the steps listed below before performing data migration.

Note: Make sure users are not running I-DEAS when you perform steps 5 and 6.

1. Run a full backup of the entire I-DEAS Team Data Installation (TDI).

2. Also, create a backup of the following:

• the ideas_paramX .dat file (for I-DEAS 12, the default location for this file was <drive>:\Team\Master\Config\ideas_param12.dat)

• the I-DEAS security files (%SDRC_INSTL%\sec\eds _idX.dat (where X represents the I-DEAS release number) and secDB.dat)

• any additional files, such as program files, in the I-DEAS directory structure that were modified or created for site-specific purposes.

• %SDRC_INSTL%\bin\custom_varbs.cmd (if it exists)

3. Have users check model file items into libraries.

The more model file data there is, the longer the migration process will take. However, model file data that has never been checked into a library does not affect migration performance.


4. Have users delete any model files they no longer need.

Model files should be deleted using I-DEAS, not from a command prompt. Deleting unneeded model files results in smaller file sizes for the .imd and .pmd files.

Note: You will need to keep model files that store NC data. You also will need to keep files created prior to I-DEAS 8 that contain CAE data.

5. Clean the projects using dmadmin.

Note: You can migrate “clean” or “unclean” data; however, the migration process is faster for clean data.

Note: If you are migrating a data installation in a heterogeneous team environment, run dmadmin on the platform type compatible with the .imd and .pmd files in your installation.

Use the following procedure to identify and correct any corrupted project data.

a. Open a command prompt window and run Setup_Varbs.cmd to set your environment variables.

b. The default location of this file is \ugsplm\ ideasX\bin\Setup_Varbs.cmd.

c. Run dmadmin.cmd.

d. The dmadmin tool launches.

e. Enter DIAG;CH;4 to check for errors in the installation.

f. Enter 1 to display the error-checking status on the screen, 2 to save it to a file, or 3 to do both. If you entered 2 or 3, you must then enter a filename. This file is stored in the data management user directory.

The tool checks the integrity of the references between projects in the installation, looking for missing files. Any errors are listed in a generated file named idm_int.err. This file is created in your data management user directory.

g. Check idm_int.err for errors found in these core tables: COR_Hier_Version, COR_Version_Item, and COR_Version_Hierarch. Open the file in a text editor and search for COR. Note which projects contain the errors.

You should correct errors found in these three tables before continuing with migration.

h. Correct any COR_Hier_Version and COR_Version_Item errors by entering PROJ;CLRW from the main menu.

When you are prompted to enter the project to be cleaned, enter ? to show a list of projects. Enter the number of the project you want to clean. Verify that no one is using the project.

The CLRW command corrects invalid rows in the project’s database tables. You will be prompted to verify any row deletions.

Be sure to correct these errors before correcting any COR_Version_Hierarch errors. Once you correct these errors, hidden COR_Version_Hierarch errors will become visible.

26

Note: The CLRW command is not visible in the dmadmin menus.

i. Correct any COR_Version_Hierarch errors by entering PROJ;CL from the main menu. When you are prompted to enter the project to be cleaned, enter ? to show a list of projects. Enter the number of the project you want to clean. Verify that no one is using the project.

The CL command removes the table’s corrupt rows. If you are prompted about missing files, enter $ to abort. The COR_Version_Hierarch errors are still cleaned.

j. If migrating from a software release previous to NX I-deas 8, check for drafting files that need to be updated.

From the main menu, enter DIAG;DRAW.

Enter 1 to display the results on the screen, 2 to save them to a file, or 3 to do both. If you entered 2 or 3, you must then enter a filename. This file is stored in the %SDRC_INSTL% directory.

The results show drafting files that will be out-of-date in NX I-deas 5. Before proceeding with the migration, you may want to update the files in Master Series 7, or the previous software release you’re currently using. This is recommended but not required for migration.

k. You may also want to check for assemblies that are out-of-date. Use the same procedure for checking drafting files, but enter DIAG;ASSM at the main menu. Updating assemblies is not required for migration.

6. Run idfvfy to check your .pmd files for errors that could cause corruption.

The recommended syntax to check a .pmd file is:

idfvfy.exe -e <path to .pmd file>

However, this command will check only the specified .pmd file. Using *.pmd in the path produces an error. To check all .pmd files in the installation, use the following script:

FOR /R <path to .pmd files> %a in (*.pmd) DO %SDRC_INSTL%\prl\idfvfy.exe -e %a

For example:

FOR /R c:\team\projects %a in (*.pmd) DO c:\ugsplm\NX I-deas11\prl\idfvfy.exe -e %a

The -e parameter causes only errors to display. If you include this parameter and no results display, the .pmd files passed the check. If you exclude the -e parameter, you will see messages for each .pmd file, indicating whether the .pmd has passed or failed the check.

If all .pmd files pass the check, you can continue preparing your data for migration. If any files fail the check, contact your local support representative.

Note: If you are migrating a data installation in a heterogeneous team environment, verify that the .pmd files do not return any “incompatible database type” errors. If you do receive these errors, run the HDS convert utility on those .pmd files.

For information on using the HDS utility, see “Data Sharing Administration” in I-DEAS General Administration in the I-DEAS online help library.


7. Run another full backup of the entire data installation.

Store this backup separately from the previous backup run in step 1.

8. Use the Microsoft Windows rdisk utility to create an emergency repair disk to back up the I-DEAS installation and license file registry entries.

9. Verify that all users have exited I-DEAS.

Note: After the backup is complete, it’s important to verify the accessibility of files and the integrity of the media on which the backed up files are stored.

Migrating the Installation

To migrate an existing data installation to NX I-deas 5:

1. Complete the preparation steps listed in the previous section.

2. Uninstall the previous version of I-DEAS :

• Exit I-DEAS.

• Use the Add/Remove Programs utility in the Control Panel.

This utility also removes associated registry entries and Orbix (if it was installed during the I-DEAS installation pro cess). The team data installation and any user-created files remain intact. Be sure to uninstall Orbix if it was not uninstalled for you.

3. Verify that all registry entries related to I-DEAS were removed. If any registry entries remain under the following paths, remove them before continuing:

• HKEY_LOCAL_MACHINE\SOFTWARE\EDS\I-DEAS\X (where X stands for the NX I-deas release number)

• HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\Exceed

• HKEY_LOCAL_MACHINE\SOFTWARE\IONA Technologies\Orbix\X (where X stands for the installed Orbix release number)

• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Orbix Daemon

If you remove the Orbix daemon registry entry, specified above, reboot the workstation.

Note: The existence of registry entries from previous versions of I-DEAS can interfere with the performance of the new version.

4. Install NX I-deas 5 using the procedures detailed elsewhere in this guide

5. Run the TDI Migration Wizard

Run Start->(All) Programs->NX I-deas 5->TDI Wizard . Select the option “Prepare an existing Team Data Installation for migration.”

28

The Select Team Data Installation screen, shown below, is displayed when running the TDI Migration Wizard.

a. Browse for the ideas_paramX.dat file underneath your selected Team Data Installation you wish to migrate. The ideas_paramX.dat is typically found in \Team\Master\Config.

b. Select Next to continue.

c. Enter the domain\username and password of the account that you will use for the I-deas SFAM Component. Depending upon the SFAM level of your installation, this is the account that will “own” your NX I-deas data

d. Select Next to continue

e. Review the information on the Confirm Selections page underneath the “Selection Summary” and select Next.

The installation software does the following:

• reads the parameter file to locate the team data installation to migrate.

• creates a new parameter file (ideas_param1 3.dat) in the Team\Master\Config directory by default.

• updates the new parameter file with any custom entries found in the previous parameter file.

• Installs the I-deas SFAM Component and Resource Locking Service if required.


f. Complete the installation process by clicking “Finish”.

5. In NX I-deas 5, run dmadmin for migration:

Note: You must run dmadmin as the installation administrator to perform migration.

a. Open an NX I-deas command prompt window by selecting the appropriate icon from the NX I-deas 5 product group on the Start menu and type dmadmin to launch the program.

Only the MIG option is available. If you run dmadmin after migrating, the other options are available.

b. Enter MIG;MG to migrate the installation.

The .imd and all .pmd files are migrated to NX I-deas 5. The library data and model file data will be migrated when opened by users.

A log file is created in the Team\Master directory.

Any projects that cannot be migrated are listed with the reasons the migration did not work. You will be prompted to continue with migration or stop to correct the problems. If you continue with migration, these projects are not migrated, and their relationships with other projects are lost. Contact customer support for assistance.

Note: Users cannot use NX I-deas 5 to access the data installation until it has been migrated.

6. Verify that the migration was successful by starting NX I-deas 5 and creating and checking in data.

30

Data Products Migration

Data products consist of a variety of catalogs, libraries, and read-only projects that provide standard parts, features, and materials as well as parts and assemblies used in NX I-deas tutorials.

To make data products accessible in the team data installation, they are installed and copied to the shared team directory.

Existing data products may be updated with each release of the NX I-deas software. If you do not remove the existing data products, the new data products are added incrementally. This prevents users from losing associations they have created between the earlier versions of data products and their existing project data.

Use the dmadmin utility and select the INST (installation) and IN (install data products) options to install the new data products. (This procedure is described in detail in the Install Data Products section of chapters 5 in this guide.)

The original data products remain intact in your data installation.

Note: To ensure consistency of data product ownership, only the NX I-deas installation account should install data products. Otherwise, you may run into problems when adding new versions of products or updating existing products.

Warning: This release of NX I-deas contains updated material catalogs. UGS strongly recommends that you delete the material catalog projects from each Team Data Installation (TDI) that was created using previous releases of NX I-deas before importing the updated material catalogs.

For information on deleting projects from your Team Data Installation, see “Deleting a Project” in the Data Management User’s Guide in the NX I-deas Online Help Library.

Chapter 4

31

Install NX I-deas 5

This chapter describes how to start the NX I-deas 5 software installation. The initial steps you will complete for all setup types are explained here, and are referenced by subsequent chapters.

See the Site Planning and Implementation Guide for a detailed description of setup types.

Note: An installation of Exceed is no longer required before installing NX I-deas software. However, some third-party products may require Exceed. You will receive an Exceed CD if it is required for your licensed products.

CAUTION: All anti-virus software must be disabled before installing NX I-deas. Anti-virus software could interfere with the installation of DLLs, slow down the installation process, or cause the installation program to fail.

32

To begin the NX I-deas 5 installation:

1. Log in to the system using the NX I-deas administrator account.

2. Insert the NX I-deas installation media labeled Volume 1 into the device drive.

Note: If autorun is enabled, the Launch screen displays. If autorun is disabled, use Windows Explorer to display the installation media upper-level directory. Double-click the launch.hta file.

The launch application on the NX I-deas product installation media is designed to step you through a standard installation of NX I-deas products on a single local workstation. It can be used to configure multiple workstations and distributed installations. For instructions on using the MSI-Based installers for all NX I-deas related software packages, refer to the Advanced Installation Options section of this guide.

The Launch screen displays.

UGS Common License Server Setup – launches the UGS Common License Server setup program.

I-DEAS Prerequisites –

The I-DEAS Prerequisites selection installs the software that is required before you begin the installation of the NX I-deas software. The required software includes the Java 1.5.0_06 SDK and the IONA Orbix ORB. This selection launches a wizard that allows you to change the default installation location of the required software. If this selection is not present on the launch form, then the prerequisite products are already installed on your system.

NX I-DEAS Setup – installs NX I-deas 5. It this selection is not present on the launch form, then the prerequisite products have not been completely installed on your system.

Install NX I-deas 5 33

I-DEAS Online Help Library – installs the Online Help Library.

Readme – provides last minute instructions and changes for the installation program. Always review this file before installing NX I-deas.

Install the License Server

3. Pick UGS Common License Server Setup

This example installation will demonstrate installing the NX license server.

The Welcome screen will appear. Select Next to continue.

4. Destination Folder

Select the Change… button to choose a destination for installing the NX license server. Click Next to accept the location shown on the dialog.

5. License file selection

Select the Browse… button to locate and pick your license file provided by UGS. Click Next once you have located and selected your license file. On the screen that follows, click Install to load and configure the license server on the local machine. Click Finish to complete the installation of the license server.

Install the Prerequisite Software

6. Pick the I-deas Prerequisites double arrows from the right side of the Launch screen.

The Java development environment and Orbix runtime environment must be installed on all machines where any aspect of NX I-deas software will be installed.

34

Click Next to continue with the requirements wizard. You will only be presented with the next screens if you do not have the prerequisite software loaded. If you have one of these software products already installed, the installation folder screen for that product will not be presented.

Enter the installation folder to which you want to install Java or accept the default. You can modify the destination location of the product without any adverse effects. Click Next. If this is the only software that needs to be installed, the installation of Java will start immediately.


Enter in the installation folder to which you want the Orbix software loaded of accept the default. Note: this disk location must be on a local disk as Orbix is a service application and will not start if installed to a mapped drive. Click Next. After clicking Next the installation of the prerequisite software product(s) will start immediately.

NOTE: After the Orbix software is installed, you will need to reboot your machine to start the services. Rebooting of your system is not automated during the installation, you will need to reboot your system. You can reboot at this point in the installation process or wait until you complete the NX I-deas installation before rebooting. Orbix services will not be neede d during installation of NX I-deas; they will only be needed when you run NX I-deas.

36

Install NX I-deas

After the software prerequisites have been installed the launch application will change the I-DEAS Prerequisites installation option to the NX I-DEAS Setup installation option.

7. Pick NX I-DEAS Setup double arrows from the right side of the Launch screen.

8. Pick Next on the Welcome screen.


7. Read the license agreement that displays. Select I accept the terms in the license agreement and click Yes when done.

8. Customer Information

Enter your user information and select whether to install NX I-deas for all users or only for you. Click Next to continue.

9. Product selections

Use the drop down lists to select the products and features you want to install. Click the plus/minus boxes to expand each section and use the drop down selections to choose to install a specific feature, all sub-features under a feature or to not install the feature.

Click the Change… button when the Install to: text appears. Changing the location for one feature will change it for all features so you need only make this change once during the installation.

Note: The Install to: folder name and associated path cannot contain spaces. The total path to the NX I-deas installation directory (%SDRC_INSTL%) should be less than 30 characters. If you use more than 30 characters, it’s more likely that the 80 character limit for the path to NX I-deas data items will be surpassed.

Click the Space button to see the amount of disk space required for all features to be installed.

After making all of your installation selections, click Next to continue.

38

10. Select License Server

Enter in the server name of your license server or click Change… to browse your network places for your server machine. If you have loaded the license server on the same machine that you are loading NX I-deas, you can leave the license server name as LocalHost for the local machine installation.

Note: For the NX I-deas 5 release, the installation program will accept one license server on this entry form. If you want to use redundant license servers, leave the License Server entry as LocalHost. Then manually set the system variable UGS_LICENSE_SERVER after installation to define the redundant license servers. See the flexlm.pdf file on the installation media for a discussion on redundant servers and properly setting the UGS_LICENSE_SERVER.

Click Next to continue.

11. Install the software

The program is now ready to install and configure NX I-deas based on your selections. Click Install to begin loading software or Back to make modifications to your selections.

After the software is installed your Start menu will now contain an NX I-deas 5 program group with five shortcuts. Before you can use NX I-deas, you will need to run the TDI Wizard from the program group to configure your default Team Data Installation.

12. Run the TDI Wizard

Run Start->(All) Programs ->NX I-deas 5->TDI Wizard to configure a default team data installation for NX I-deas on this computer. Click Next on the Welcome screen of the wizard.

Proceed to chapter 5 for TDI Wizard information.

Chapter 5

39

TDI Wizard

The TDI Wizard, when run by the system administrator, is used to set up your default Team Data Installation for the local computer.

40

Running the TDI Wizard

Start the TDI Wizard by running Start->(All) Programs->NX I-DEAS 5->TDI Wizard .

The TDI Wizard gives you three possible tasks to perform:

• Create and publish a Team Data Installation

Use this task to create a new Team Data Installation and set up your ideas_paramX.dat file. This task will install a local Resource Locking Server associated with the team data installation and also install and configure the SFAM Component on the local machine.

• Connect to an existing Team Data Installation

Use this task to point your I-DEAS software to an existing NX I-deas 5 parameter file and Team Data Installation environment. This task will also install the local SFAM Component on your machine if necessary. It assumes that the Resource Locking Service is already installed on your network or local machine as defined in the parameter file of the team data installation and will not install it again.

• Prepare an existing Team Data Installation for migration

Use this task to create a new NX I-deas 5 parameter file by copying values from a previous release parameter file. This will set up NX I-deas 5 to use the previous release team data installation and install the SFAM Component and Resource Locking Service if required. See Chapter 3 for more information on using this option and preparing your team data installation for migration to NX I-deas 5.

Click Next to continue after making your task selection. If you choose to Create and publish a Team Data Installation proceed to the Create and Publish a Team Data Installation section of this chapter. If you choose to Connect to an existing Team Data Installation skip to the Connect to existing Team Data Installation section of this chapter. If you want to Prepare an existing Team Data Installation for migration return to chapter 3 for more information on data migration and the use of the TDI Wizard.

TDI Wizard 41

Create and publish a Team Data Installation

1. Choose your Team Data Installation name

Enter in a valid 1-63 ASCII character name for your Team Data Installation. This will write the name in the Team.MasterName entry in your parameter file. Click Next to continue.

2. Select your Team Master ID

Enter in a Team Master ID number or use the up/down arrows to scroll to a Team Master ID number for your Team Data Installation. Enter 0 or a positive number if this is a shared data installation; enter a negative number if it is a single user team data installation. This number must be different than the Team Master ID used in all other TDI’s in your environment in

42

order to avoid data corruption. The Team Master ID number is written to the Team.MasterID entry in your parameter file. Click Next to continue.

3. Select your SFAM Level

Select whether to define your SFAM level as Level 1 or Level 2. The TDI Wizard will not configure SFAM for Level 3. You must use the “dmadmin” utility to configure your TDI to use SFAM Level 3 after setting up your default team data installation.

4. Select your Heterogeneous Team Account – SFAM Component account

If you selected SFAM Level 2, you should enter the domain\username and password of the account that you will use for the I-DEAS SFAM Component. Depending on the SFAM level of your installation, this is the account that will “own” your I-DEAS data. For security

TDI Wizard 43

reasons, this account should not have administrator or power user privileges. It does, however, require the following security policy settings:

• Impersonate a client after authentication

• Log on as a service

• Increase quotas/Adjust memory quotas for a process

• Log on locally

• Act as part of the operating system

These privileges will be checked when you enter in a user name and password in this dialog. An error: “A required privilege is not held by the client” will be presented if any of the policy settings do not meet the requirements.

5. Select Resource Lock Server

Enter the name of the computer that will serve as the Resource Lock Server for this Team Data Installation. Resource locking controls concurrent access to shared files, and items within those files, in a team data environment.

The Resource Lock Server is normally installed on the computer that hosts the Team Data Installation.

44

6. Select the folder locations for your Team Data Installation folders

Double-click on the Filesystem Folder entry to change the location of each folder. The browse button (…) allows you to browse for a folder on the local system. Click Next to continue when you have set your folders to your desired locations. The installation program will create the folders, if necessary, and set the parameter file entries for each folder.

Note: The team data installation folder names and associated paths cannot contain spaces.

7. Confirm your selections and create the team data installation

Confirm that the selections you made are correct and click Next to create your team data installation. This will also install the SFAM Component and I-DEAS Resource Locking Service if required.

TDI Wizard 45

Parameter Entries Modified during Parameter File Creation

During the creation of a team data installation, the TDI Wizard will only modify the following global parameter file entries:

• Team.MasterId

• Team.MasterName

• Team.MasterDirectory

• Team.ProjectsDirectory

• Team.ScratchDirectory

• Team.SharedDirectory

• Team.DflexlmConfiguration

• Team.SecFileAccessLevel

If you need to have any other parameter file entries set in the new team data installation for heterogeneous team environments or other customizations you will need to edit the ideas_paramX.dat file manually and change the settings. The ideas_paramX.dat is typically found in the \Team\Master\Config folder.

If you are connecting to an existing team data installation, none of the global parameter file entries are modified in your connected parameter file.

If you are migrating a parameter file from a previous release all customized parameter file entries will be migrated forward from the previous release so you will not need to edit the parameter file to customize for your environment.

46

Connect to an existing Team Data Installation

1. Select the default Team Data Installation

Enter or Browse… to your existing NX I-deas 5 parameter file that you want to use for your Team Data Installation when running I-DEAS. The parameter file can be on the local system or on a network mapped drive. Click Next once you select a parameter file.

2. Confirm your selections and configure your team data installation

Confirm that the correct parameter file is selected and click Next to configure your team data installation. This will also install the SFAM Component if needed.

Registry Entries Created by the TDI Wizard

The TDI Wizard creates registry entries for use by the I-DEAS start menu applications to identify the location of your team data installation.

When running the TDI Wizard as an administrator (administrative privileges) user, the TDI Wizard sets the default team data installation for all users of I-DEAS on the local workstation.

The HKLM\SOFTWARE\UGS Corp.\NX I-DEAS\5.00.0000\Default TDI is defined to the folder containing the I-DEAS parameter file to be used by the default TDI.

TDI Wizard 47

Running the TDI Wizard as a Regular User

After the administrator has executed the TDI Wizard one time on a machine to configure the default TDI and install the SFAM Component and I-DEAS Resource Locking service, the TDI Wizard can be executed by regular I-DEAS users . With the TDI Wizard, I-DEAS users can connect to existing team data installations. This allows a method for users to choose between available team data installations by selected the appropriate I-DEAS parameter file before running a session of I-DEAS.

When the regular user runs the TDI Wizard, the wizard creates registry entries under the HKEY_CURRENT_USER registry hive. These registry entries override the Default TDI setting in the HKEY_LOCAL_MACHINE at I-DEAS runtime for the one user, but do not change the Default TDI for other users on the system.

To limit the ability of your regular users from overriding the default TDI using the TDI Wizard, you may choose to remove the TDI Wizard start menu shortcut and also remove the %SDRC_INSTL%\bin\TDIMigrationWizard.exe application after you have completed the set up of your default TDI.

Order of Precedence of Team Data Installation Settings for I-DEAS Runtime

The ability to override the default TDI is accomplished in multiple ways. The order of precedence is as follows from lowest to highest precedence:

• HKEY_LOCAL_MACHINE Default TDI registry setting

• HKEY_CURRENT_USER registry setting

• IDEAS_PARAM13 user or system environment variable

• Command line settings on the start menu applications

This means that command line settings and system environment variables will override the equivalent entries in the registry

48

Install Data Products After completing the TDI Wizard, you should catalog the I-DEAS data products. Data products consist of a variety of catalogs, libraries, and read-only projects that provide standard parts, features, and materials, as well as parts and assemblies used in the tutorials.

To make a data product accessible in the data management installation, the data product must be installed and copied to the shared directory. This process is called “cataloging” the data product.

Note: To ensure consistency of data product ownership, only the I-DEAS installation account should install and catalog data products. Otherwise, you may encounter problems when adding new versions of products or updating existing products.

To install data products, use the dmadmin utility:

1. From the Start menu, pick (All) Programs->NX IDEAS 5->NX I-DEAS Command Prompt

2. CD to a directory where you can write files.

3. Run dmadmin.

4. Enter INST for installation.

5. Enter IN for installing data products.

6. Enter the corresponding number for the data products you want loaded. You can enter as many numbers as desired.

7. Enter 0 when done.

The selected data products are cataloged.

Note: For additional information on the dmadmin utility, see An Overview of dmadmin in the online Help Library.

8. Enter EXIT to exit dmadmin.

Chapter 6

49

Install Help Library

This chapter provides instructions on how to install the help library files.

50

Help Library Overview

The Help Library consists of the following types of documentation and training. You access the Help Library from the I-DEAS icon panel Help menu:

• What’s New

• On Context

• Help Library

• Web

• Quick On/Off

• About I-DEAS

The What’s New menu pick takes you to an article in the I-DEAS Help Library that describes the new features for the current version of the software. The What’s New article automatically displays when you first log into the new version of I-DEAS.

The automatic display of the What’s New article is controlled by the help.whats_new_seen_in_release parameter in the username_param file for each user in the Team.MasterDirectory. Set the parameter to OFF if you don’t want to display the What’s New article upon initial login.

On Context displays a question mark that you use to pick any selectable interface item such as an icon, menu option, or form field. The I-DEAS Help Library then displays the documentation for the picked item.

Web provides an Internet link to our home page and your company home page (if you have one).

Quick On/Off turns on and off I-DEAS Quick Help. Quick Help provides a brief explanation of an item (e.g., icon, menu option, or form field) at the bottom of the graphics window when the cursor is placed over the item.

About I-DEAS displays the copyright message for the I-DEAS software you’re using.

Installation Considerations

Help Library

The Help Library is HTML- and Java-based online documentation viewed using a web browser. (See the next section, Help Library Software Requirements, for information on supported browsers.) Most of the Tutorials in the Help Library use Adobe Acrobat PDF format (a few are in HTML), so you also need to have the Acrobat Reader available to your users either as a web browser plug-in or as a helper application launched externally from the web browser.

Install Help Library 51

Help Library Software Requirements

The Help Library uses a web browser (for product online documentation) and the Adobe Acrobat Reader (for online tutorials). To use the Help Library you will need:

• The Netscape Navigator or Microsoft Internet Explorer web browser:

Netscape 7.0 or later version of the Netscape Navigator web browser. The web browser must be able to support Java.

Note that we don’t provide technical support for Netscape. If you require such support, you can purchase it from Netscape.

• Internet Explorer 6.0. This is not provided on the CDs.

Note that we don’t provide technical support for Internet Explorer.

• Adobe Acrobat Reader 5 or later version. The Acrobat Reader is provided on the Help Library CDs. See the utilities\acroread5 directory on the Help Library CDs for an executable file to install AcroRead for supported Microsoft Windows platforms.

Help Library Access to the Web Browser

The Help Library uses the default web browser identified in the Microsoft Windows Registry. It must be able to display HTML files in that web browser. To perform a check to see if the web browser connection to the Help Library works, double-click on an HTML file in Windows Explorer. If the file is displayed in the web browser, then the Help Library HTML files should also display in the web browser.

Note: You still must ensure that the minimum required version of the web browser software is installed.

Browser Setting Requirements for Help on Context

Your browser must be set to use DDE when opening an HTML file (which is the default). Use the following procedure to verify the DDE settings are correct for your browser:

1. Open a Windows Explorer window.

2. Pick Tools, Folder Options.

3. Select the File Types tab.

4. Find the HTML file type in the list and select it.

Note: The HTML file type may be listed as “HTML Document,” or “Microsoft HTML Document 4.0,” or “Netscape HTML Document,” or some other variant. The correct listing displays the Extension as “HTM HTML” in the File Type Details section of the window.

5. Pick the Edit button.

6. Select Open under the Actions section and pick the Edit button.

52

7. Verify that the Use DDE box is checked.

8. Verify that the DDE properties are set correctly for your browser. The correct settings are shown in the following table:

DDE Property Netscape Internet Explorer

DDE Message: “file:\\\%1” “file:%1”,,-1,,,,,

Application NSShell Iexplore

Web

The Web link is a quick access to the our home page and your company home page (if you have one).

The web link to our home page is installed automatically when I-DEAS is installed. Selecting Help, Web, UGS runs the %SDRC_INSTL%\bin\WebSdrc.exe program. This program accesses the UGS home page using the browser registered on the local workstation.

A simple procedure is necessary to set up access to your local web site.

To set up the Help, Web, Local option to access your company’s web site:

1. Create a text file named WebLocal.txt in the %SDRC_INSTL% \bin directory.

2. Include your company’s web site address in the file.

Use the syntax shown in the Example.txt file located in the %SDRC_INSTL%\bin directory. It is set up to access the UGS home page.


Installation Procedure

After installing I-DEAS, it’s recommended you install the Help Libra ry to the same location as your I-DEAS software. However, you can install it to a central location separate from I-DEAS but accessible to all I-DEAS workstations, or direct the I-DEAS software to access the Help Library from CD.

1. Insert the I-DEAS Help Library media in the device drive.

Note: If autorun is enabled, the Launch screen displays. If autorun is disabled, use Windows Explorer to display the installation media upper-level directory. Double-click the launch.hta file.

2. Pick Install I-DEAS NX Series 12 Help Library from the Launch screen.

54

3. Pick Next on the Welcome screen.

4. Select License Agreement.

Select the “I accept the terms in the license agreement” option and click Next to continue.

5. Pick features and/or choose installation location.

Select the features to install and the installation location for the Help Library.

Click Next and then Install to perform the installation of the Help Library.


I-DEAS Access to the Help Library

I-DEAS identifies the location of the Help Library based on the registry entries in the HKEY_LOCAL_MACHINE\SOFTWARE\UGS Corp.\NX I-DEAS Help Library\5.00.0000 hive and HKLM\SOFTWARE\UGS Corp.\NX I-DEAS\5.00.0000 hive.

(Default) - contains the installation location of the Help Library. If you install the Help Library to prior to installing I-DEAS, the location contained here is copied to the registry key SDRC_MPATHS under the NX I-DEAS\5.00.0000 registry hive. The SDRC_MPATHS setting under the I-DEAS NX Series registry hive is not required if the (Default) key is set under I-DEAS NX Series Help Library.

Installed Components – identifies which languages were installed with the Help Library. Used for information purposes, this entry is not used by the I-DEAS product.

If you choose to access the Help Library on a mapped drive or from the distribution media and not to install the Help Library to disk, you will need to modify the HKLM\ SOFTWARE\UGS Corp.\NX I-DEAS\5.00.0000\SDRC_MPATHS key to point to the installation location of the I-DEAS Help Library. Eg. If you installed Help to D:\UGS\NXI5, you should set the SDRC_MPATHS registry key to D:\UGS\NXI5.

Chapter 7

57

Advanced Installation Options

There are a variety of installation options supported by the new I-DEAS installation programs. These options previously had special terms such as the Network Client Installation setup type from I-DEAS 11 which referred to a situation where I-DEAS code was served from a central server and only the bare minimum of software was loaded onto each client.

The following sections describe the advanced installation options available in this release of I-DEAS and list the previous I-DEAS installation options that they are intended to replace.

58

Running Software from a Server

In previous releases of I-DEAS there was a specialized setup type that allowed the system administrator to install the I-DEAS software executables on a server machine and then run a specialized setup program on each client computer that allowed the user to run I-DEAS as if it were installed on the local machine.

The current release of I-DEAS has removed the “Network Client Installation” type and has replaced it with the option within setup to run specific product features from “the network”. This allows you to install the product executables once on a server and run them from any client computer capable of running I-DEAS.

By using this option, all software and services required to run the I-DEAS executables will be installed on the local machine, however, the actual I-DEAS executables and Team Data Installation can reside on a remote server.

To run I-DEAS software from a server you should follow the following procedure:

1. Install Licensing and I-DEAS onto the server

Using the procedures described earlier in this guide, install the licensing, I-DEAS prerequisites and I-DEAS onto the server.

Ensure that the code is installed to a drive and path that can be shared and mapped by all clients using a consistent local path. If necessary, you can remap a local drive in order to ensure that none of the client computers has a conflict with the chosen drive.

Ensure that all product features that you want your users to access have been installed.

2. Create a Team Data Installation on the server

Using the procedures described earlier in this guide, use the TDI Migration Wizard to create a Team Data Installation that will be accessed by the I-DEAS client machines on the network.

Note: The Team Data Installation must be created in such a way as to allow all clients to be able to connect to it using a consistent drive and path. Failure to do this will result in errors upon I-DEAS startup.

3. Install the I-DEAS prerequisite software on the client computer

Using the procedures described earlier in this guide, install the I-DEAS prerequisite software onto the client computer.

4. Map the server drive(s) on which the I-DEAS executables and Team Data Installation reside

Ensure that you use consistent paths on each client computer in order to ensure the proper operation of I-DEAS.

Note: The drive and path used for the Team Data Installation must exactly match that of the server on which the Team Data Installation was created.

Advanced Installation Options 59

3. Install I-DEAS Network Client onto the client computer

Run the Network Client installation program found on the NX I-deas 5 DVD under the NetClient folder. Double-click on the setup.exe in the NetClient folder to begin the installation.

Click Next and then accept the license agreement and click Next again. On the Custom Setup form, select the installation location into which you want to load the local files necessary to run NX I-deas as a network client and click Next.

60

Select the folder in which the network installed NX I-deas software is contained. Use the Change… button to select the folder and then press Next. This will be on a drive mapped to your local machine.

Select the folder in which the team data installation I-DEAS parameter file for this installation resides. Use the Change… button to select the folder and then click Next on this form when finished.


Enter the license server string for this installation. The license server string will be the definition of the license server variable necessary for NX I-deas to obtain licensing.

Finish the installation. Note that some such as shared product DLLs will be installed onto your computer on your Windows partition.

4. Connect to the Team Data Installation

Run the TDI Migration Wizard by selecting the TDI Wizard icon from the NX I-deas 5 program group from the Start menu. Select the “Connect to an existing Team Data Installation” option from the “Select Task” page.

In the “Select the Default Team Data Installation” page, select the ideas_param13.dat file that is located in your Team Data Installation.

As you continue with the wizard, it will install the I-DEAS SFAM Component on your local computer (if required) and will set the default Team Data Installation for the machine to the one just selected.

Note: If you are using SFAM level 2 or a heterogeneous Team Data Installation you are required to manually set the “identity” tab of the SFAM Component in the Component Services snap-in in order to use the Team Data Installation.

Finish the installation normally.

5. Run I-DEAS and verify the installation

62

Command Line Installation Options

Previous releases of I-DEAS used the InstallShield 5.5 setup engine that allowed a rudimentary “silent install” capability. This ability allowed system administrators to “record” an installation as it occurred and then “playback” the installation on multiple machines where I-DEAS was to be installed.

Using the Windows Installer Service this release of NX I-deas allows system administrators to specify all of the customizable attributes of the product via the command line by exposing the options as public properties of the installer package.

Combined with the scripting options available from the operating system, this release of I-DEAS provides better and more robust “silent installation” capability than previous versions. Add to that the additional logging capabilities of the Windows Installer; debugging silent installation response files is happily absent from this release.

By installing a package from the command-line rather than double-clicking on the package or by having another program launch the installer, you can access many of the most commonly modified properties of the installation. In addit ion, you can enable or disable Windows Installer features such as the debugging log and user interface elements.

To launch a Windows Installer package via the command line, in a command-prompt window type the following command:

msiexec /i <path to database>

In the above command, <path to database> should be replaced by the full path to the Windows Installer database file (.msi) that you are attempting to install.

Many common options may be set via the command line. Some examples of different properties that you can set to influence the installation of the software are listed below. A complete listing of modifiable installation properties is included elsewhere in this guide.

Example:

msiexec /i /qn D:\Orbix\Orbix.msi INSTALLDIR=”F:\Program Files\IONA”

The above example installs the Orbix package that is required for I-DEAS into the F:\Program Files\IONA folder and shows no user interface (/qn).

Example:

msiexec /x D:\Orbix\Orbix.msi

The above example removes the Orbix package that was installed as a result of the previous example. The uninstaller will display the complete UI of the package.

Example:


msiexec /i “D:\IDEAS\I386\ NX I-deas.msi” ADDDEFAULT=”A001,A002,A003,French”

The above example starts the installation of I-DEAS with the full user interface, but pre-selects the A001, A002, A003 products and the French user interface for I-DEAS.

This command reveals the true power of the Windows Installer as we could easily modify the above command to install the product into a different directory by setting the INSTALLDIR property and then select a default Team Data Installation by setting the DEFAULT_TDI property on the command line.

Note: If you use the command line options to select a product feature that does not exist, you will receive an error message similar to the one shown below. In this particular case, the user attempted to install the feature A299 which did not exist.

Note: To remove an installed product feature without removing the entire product, use the REMOVE option.

Product Feature Names

Each I-DEAS product feature has been given a name that corresponds to the product number in the product catalog. For example, product A001 Core Master Modeler can be selected by using the feature name “A001”.

Optional Product Feature Names

Optional product selections that do not appear in the product catalog are named as follows:

O001 Archive Reader/Writer

O002 Design Examples

O003 Manufacturing Examples

O004 Simulation Examples

O005 Test Examples

O006 Open Architecture Development Library

O007 Open Architecture Documentation

64

O008 Icon Editing Tools

O009 Unsupported User Library (complete)

O010 IPLOT

O012 GDR scripts/programs from ULIB

O014 STL to Universal File Conversion Program from ULIB

O015 Test program files from ULIB

O016 Czech localizations from ULIB

O017 Greek localizations from ULIB

O018 Hungarian localizations from ULIB

O019 Polish localizations from ULIB

O020 Russian localizations from ULIB

O021 Turkish localizations from ULIB

O023 WSGTST directory from ULIB

Please note that optional products begin with the letter “O” and end in a number that may be prefixed with zeros.

Language Interface Feature Names

Language interface features are named as follows:

French Installs the French user interface components

German Installs the German user interface components

Italian Installs the Italian user interface components

Japanese Installs the Japanese user interface components

Korean Installs the Korean user interface components

Spanish Installs the Spanish user interface components

Chinese Installs the simplified Chinese user interface components

ChineseT Installs the traditional Chinese user interface components


Windows Installer Service Additional Information

For a complete explanation of all of the options available to end-users and administrators for the Windows Installer service, please see the Windows Installer documentation at http://msdn.microsoft.com/library/en-us/ms i/setup/windows_installer_start_page.asp?frame=true

For a complete list of product feature and component names included with each Windows Installer package, please use the Orca tool that is available from the Windows Platform SDK.

Customizing Product Databases

Previous releases of I-DEAS used the InstallShield 5.5 setup engine which was a “black box” installer technology in that the end user could not see what was happening and could only see the results of what the install engine was doing on the local system.

The InstallShield 5.5 setup engine allowed a rudimentary “silent install” capability. This ability allowed system administrators to “record” an installation as it occurred and then “playback” the installation on multiple machines where I-DEAS was to be installed.

This release of NX I-deas uses Microsoft Windows Installer technology to deliver the installation program logic. With the installation of a few free tools from the Microsoft Platform SDK, it is possible for a knowledgeable system administrator to modify all aspects of each installation package delivered with I-DEAS from simple properties such as the target location to advanced features such as the default software to be installed and the name of the program group in which product icons will be created.

The most useful tool for customizing Windows Installer packages is Orca, the Microsoft Windows Installer database graphical editing tool. This tool is downloaded, but not installed with the platform SDK. Orca allows system administrators to view and more importantly change the internal tables in the Windows Installer database for a particular package. This allows you, the system administrator to customize the behavior of the I-DEAS installer in your environment.

Note: While the I-DEAS installation package provides you with the ability to manually customize the I-DEAS database, UGS cannot support any installation related problems that result from customization of the database file.

By using the Orca tool, system administrators can create an installation database with all of the appropriate defaults for their network.

Chapter 8

67

Uninstall

This chapter describes how to remove the I-DEAS software from your workstation.

68

Uninstall an I-DEAS Installation

You can remove an I-DEAS installation using the Microsoft Windows Add/Remove Programs utility.

Note: Each component of I-DEAS such as the Resource Locking Service and SFAM component must also be removed in order to completely remove I-DEAS products from your computer.

1. Remove the I-DEAS software using the Microsoft Windows Add/Remove Programs utility.

2. Remove any user-created folders/files manually after the Add/Remove Programs utility is complete.

3. Verify that I-DEAS registry entries have been removed. These are located under HKEY_LOCAL_MACHINE\SOFTWARE\UGS Corp.\NX I-DEAS.

4. Uninstall the I-DEAS Resource Locking Service (if installed) by clicking on the product in the Add/Remove programs applet.

5. Uninstall the I-DEAS SFAM component (if installed) by clicking on the product in the Add/Remove programs applet

6. Remove IONA Orbix ORB by clicking on the “Orbix” product in the Add/Remove programs applet.

7. Remove any service-created folders/files manually in the Orbix folder after the Add/Remove Programs utility is complete.

8. Remove the Java SDK and Java JRE by clicking on the appropriate product selections in the Add/Remove programs applet.

Uninstall Help Library

You can remove the Help Library using the Microsoft Windows Add/Remove Programs utility.

1. Select NX I-DEAS Help Library and pick Remove.

2. Reboot the machine, if necessary, to complete the removal of the products.

Chapter 9

69

Troubleshooting

This chapter includes troubleshooting information for:

• Error messages and problems that could occur during the installation process

• Unable to locate IDEAS_PARAM13 or SDRC_MPATHS from command line execution of I-DEAS application.

• Time Out Warning while running I-DEAS

• How to contact customer support

For additional error message descriptions, problem discussions, and recovery solutions, see the Resolving Problems article in the Help Library.

70

Errors During the Installation Process

If you get a runtime error because the Orbix environment is not started and you can not manually start the services, make sure you have rebooted the system after installation to attempt to start the services before taking any other corrective action. Rebooting after the installation of Orbix is necessary to start the Orbix services, you can reboot as soon as Orbix is installed or defer to reboot until after you have completed the entire I-DEAS installation.

If you get other errors when you try to start I-DEAS, contact the support center.

IDEAS_PARAM13 and SDRC_MPATHS are not defined

The Start->(All) Programs->NX I-DEAS 5->NX I-DEAS Command Prompt is the preferred method of starting a command prompt session for running I-DEAS command line programs. Run the I-DEAS Command Prompt program to define the needed environment for running all I-DEAS command line programs found in the %SDRC_INSTL%\bin folder. After running NX I-DEAS Command Prompt you do not need to run setup_varbs.cmd before running any of the applications; all necessary variables are defined when the NX I-DEAS Command Prompt is started.

If, however, you must run in a regular command prompt and want to execute setup_varbs.cmd before running an I-DEAS command line program, you may find that the IDEAS_PARAM13 and SDRC_MPATHS variables are not defined in the setup_varbs.cmd after running the TDI Wizard or installing Help.

To update the setup_varbs.cmd script to contain the values for IDEAS_PARAM13 and SDRC_MPATHS, run the program %SDRC_INSTL%\bin\BatchEdit.wsf. This program will read the registry settings containing the location information and variables for the I-DEAS runtime and update the %SDRC_INSTL%\bin\setup_varbs.cmd to contain the most up-to-date values.

Time Out Warning

A time out warning means that you cannot communicate with the license or resource lock server.

If the program cannot make contact, a warning is issued by the I-DEAS license system/resource locking service indicating that contact was lost, and informing you of the time frame for reconnection (reconnection is automatic once contact is established).

The following situations can cause lack of contact:

• The I-DEAS license manager service has terminated: the license system/resource locking service must be restarted.

Note: Use the license system Secdaemon script or the Microsoft Windows Control Panel, Services tool to start the I-DEAS license management service.

• The I-DEAS license manager service or the project file is in use by other users: try again.

• I-DEAS is started before the license system/resource locking service started: verify that the license system/resource locking service is running; exit and restart I-DEAS.

Troubleshooting 71

Note: Use the license system Secdaemon script or the Microsoft Windows Control Panel, Services tool to start the I-DEAS license management service.

• The network connection to the license or resource lock server is broken: have the system administrator correct network problems.

Use the license system Statdaemon script or lmstat utility to get information about the status of the I-DEAS license manager service. The lmstat utility is in the %SDRC_INSTL%\sec directory.

Note: If you are using FLEXlm-based resource locking, you also can use the FLEXlm applet in the control panel to check the status of the license manager service.

• If the service is “up,” have the user try again.

• If the service is “down,” restart the service.

• If there is no response, retry; then restart if the retry fails.

• If timeouts are too frequent, increase the value of the site-wide Team.TransactionRetries parameter in the .ideas_paramX.dat file.

See the Licensing Basics (Microsoft Windows) article in the Help Library General I-DEAS Administration for more information on the license system and license system utilities.

I-DEAS Customer Support

I-DEAS customer support is available through locations worldwide. You can access customer support through the Global Technical Access Center (GTAC) web site at the following URL:

http://support.ugs.com

For assistance during normal business hours, you can call 1-800-955-0000 to speak to a Customer Account Analyst. Outside the United States and Canada, please contact your local support office.

Appendix A

A-1

Configuring I-DEAS Stand Alone Solver

The I-DEAS Stand Alone Solver (SAS) is a batch solver delivered with the I-DEAS Simulation Solution Set product. This product uses QMan as the queue manager to launch and manage SAS batch jobs. All the files required for SAS and QMan are located in the %SDRC_INSTL%\sas and %SDRC_INSTL%\QMan directories, respectively.

The QMan product is an external program that consists of the QMan Server and the QMan Client. The QMan Server queues all the jobs and drives the analysis solver software (SAS). The QMan Client submits the batch jobs and manages the queue. Multiple QMan clients can access a single or multiple QMan servers.

SAS is used to perform solves on data submitted by clients for finite element analysis. The user initiates a solve job using the I-DEAS software Manage Solve form. The user submits the job to the QMan Server through the QMan Client by using the Submit Job form. The QMan Server orders and runs the jobs based on when they were sent, the priority specified, and if the job has been scheduled to run.

The following software must be installed to run SAS and QMan:

• I-DEAS Simulation Solution Set product (contains the QMan Server license)

• Java 1.5.0 version or higher (QMan Server looks for Java in the script)

A-2

The following must be set up to run QMan:

• The SDRC_INSTL environment variable must be set.

Note: The variable is set by starting I-DEAS software or by running NX I-DEAS Command Prompt located in the Start Menu under NX I-DEAS 5. The SDRC_QMan environment variable defaults to the SDRC_INSTL\QMan directory.

• Java version 1.5.0 or higher must be defined in the PATH of the user’s profile.

Installing QMan and SAS

The I-DEAS Simulation Solution Set contains the QMan server and client, the QMan license, and SAS. Install the Simulation Solution Set during the initial NX I-deas setup.

To install QMan and SAS:

1. Using the I-DEAS installation software, access the Select Components window.

Note: Install the Simulation Solution Set product during the initial I-DEAS setup or use the Software Installation Only setup type to add the component. For more information on adding software components, refer to one of the previous chapters on installation setup types.

2. Pick Simulation Solution Set from the list of components.

3. Continue with the remaining I-DEAS installation setup windows.

Configuring I-DEAS to Run SAS

To configure I-DEAS to run SAS:

1. Copy the global I-DEAS parameter file, ideas_paramX.dat, from its location defined for I-DEAS to the sas\PARAM directory. Create the \sas\PARAM directory if it does not exist. The resulting copied file is:

%SDRC_INSTL%\sas\PARAM\ideas_paramX.dat

Note: Keep the original global parameter file in the normal location. The copied version is only for the SAS program.

2. Copy the UGS common licensing global license file to the sas\SEC directory and rename it to license.dat. The resulting copied file is:

%SDRC_INSTL%\sas\SEC\license.dat

Note: Keep the original global license file in the normal location. The copied version is only for the SAS program.

A-3

Configuring QMan Client – Server for Batch Solves

You can configure QMan to run a local or remote batch solve:

Local batch solve:

• Both the QMan Server and QMan Client are installed on one machine.

• To simplify user interaction, the QMan Server runs in the background and is not seen by the user (no user interface).

• The user initiates a solve by using the I-DEAS software Manage Solve form.

• The user submits and schedules jobs to run by using the QMan Client.

Remote batch solve:

• The QMan Server and QMan Client(s) are installed on different machines.

• Clients must be configured to access the QMan Server. To do this, clients must be supplied with the server name and the full path to the working directory.

• Clients initiate a solve by using the I-DEAS software Manage Solve form.

• Clients submit and schedule jobs to run by using QMan Client.

• The QMan Server user interface can be viewed on the server to manage the queue of batch solve jobs.

• Depending on how your installation operates, the output file may remain in a directory on the server or can be transferred back to the client using the Internet/FTP option on the QMan Client – Server Configuration form.

Note: For information on how to use the Manage Solve form, see the I-DEAS online help articles, Initiating a Local Batch Solve or Initiating a Remote Batch Solve in the Model Solution/Optimization User’s Guide, Solving the Model section.

Configuring QMan Client – Server for Local Batch Jobs

A local batch job initiated through the Manage Solve form starts a QMan Client configured to run with the local QMan Server. To simply user interaction, QMan Server runs in the background and is not seen by the user. No special configuration is required to start the QMan Client.

A user performs the following to submit a job:

1. From the Simulation, Model Solution application window, pick the Manage Solve icon to access the Manage Solve form.

2. Select execution options and initiate the solve.

a. Pick the Local Batch radio button.

b. Enter the name of the job.

c. Pick Solve. Both the QMan Client window and Submit Job forms display.

3. Verify or enter the following information in the Submit Job form:

A-4

a. Jobname (auto-fills) – the name of the SAS batch job the client submits.

b. Filename (auto-fills) - the directory path of the file location.

c. Pick a job priority from the drop-down list or enter a time for the job to run in the Run After field.

d. Pick OK.

Note: For more information on how to fill out the forms, pick Help from the QMan Client window.

Configuring QMan Client – Server for Remote Batch Jobs

Set Up the QMan Server

Perform the following steps on the QMan Server:

1. If you have not started I-DEAS, run the Setup_Varbs.cmd located in the %SDRC_INSTL% \bin directory. Otherwise, begin at step 2.

2. Issue the following command:

%SDRC_INSTL%\QMan\server\qmanserver.cmd

3. When the QMan Server window displays, pick Configure, Directory.

4. Enter the full path of the QMan Server or browse to the directory.

5. Pick OK.

6. Pick Configure, Command Lines and create your command lines.

Note: Pick Help from the QMan Server window for information on what command lines to enter.

7. Once you have entered the required information, pick Status, Start from the QMan Server window.

Note: Supply the clients with the QMan Server name and the full directory path to the QMan Server so that they can connect to the server.

Set Up the QMan Client

The user performs the following steps on a QMan Client:

1. From the Simulation, Model Solution application window, pick the Manage Solve icon to access the Manage Solve form.

2. Select execution options and initiate the solve.

a. Pick the Remote Batch radio button.

b. Enter the name of the job.

c. Pick Solve. Both the QMan Client window and the Submit Job form display.

Note: At this point, if the client is not configured to access the server, a message displays. Pick OK and then New to display the QMan Client – New Server form. You can pick Help on the QMan Client window for information on how to fill out the form. Also, if the working directory is not correct, the Submit Form does not display (without an error message). Pick Configure, Directory on the QMan Client window and make the correction.

2. Pick Server on the Submit Job form. The Client - Server Configuration form displays.

a. Pick the Internet/FTP radio button.

A-5

b. Select a server from the list box located under Servers. The Working Directory, IP Address/Name , Username, and Password fields auto-fill.

Note: If the server configuration cannot be found or the user wants to add a new one, see Adding a Server.

c. Pick OK. The Submit Job form re-dis plays.

Note: The user only needs to specify the server the first time it is accessed.

3. Verify or enter the following information in the Submit Job form:

a. Jobname (auto-fills) – the name of the SAS batch job the client submits.

b. Filename (auto-fills) – the directory path of the file location.

c. Pick a job priority from the drop-down list or enter a time for the job to run in the Run After field.

d. Pick OK. The QMan Client status window displays.

Note: The name of the active server displays in the window title bar.

Adding a Server

If the user wants to add a server or needs to re-establish the connection to the server, the following should be performed:

1. On the QMan Client – Server Configuration form, pick New.

2. Enter the server name.

3. Pick OK.

Note: For more information on how to fill out the forms, pick Help on the QMan Client window.

A-6

Running the Remote Server as a Background Process

After you configure the remote server, you can run it as a background proces s. When you run the server as a background process, the user interface isn’t displayed to enter commands. However, users can still manage their jobs by using the client software.

Typically, you add the command to the start-up process on your system. The queue then restarts whenever you start the system.

1. To add the server as a background process, enter the following:

%SDRC_INSTL%\QMan\server\qmanserver.cmd –blind

2. Then add the command to your Startup folder.

Appendix B

B-1

NX I-deas Installation Files

The files created during installation and use of the NX I-deas software and the location of the files in the NX I-deas installation structure are described in this appendix.

B-2

Files Placement Table

The following table shows the typical default location of some of the files created for and by the NX I-deas software:

LOCATION or LOCATION PARAMETER or ENVIROMENT VARIABLE

CONTENT

...\Team\Master\Config (default parameter file location) or, if redefined, %IDEAS_PARAMX%

.ideas_paramX (X represents the current software release number)

Team.MasterDirectory (installation metadata file and user preference files)

z_master#.imd .<user>_param

Team.ProjectsDirectory (project metadata files)

*.pmd

Team.ScratchDirectory (team scratch files)

z_master#.smd z_project#.smd

Team.SharedDirectory (library and catalog parts)

*.prt, *.asm, *.drw, *.mdf, *.sprt, *.fea, *.fem, etc.

DataMgmt.UserDirectory or, if undefined, current working directory (user files)

*.mf*, *.arc, and others

DataMgmt.ScratchDirectory or, if undefined, current working directory (user scratch files)

ideas*.app ideas*.dsp ideas*.sf*

current working directory (interface files, run-time files, etc.)

STOP_SDRC##, .STOP*, error##.out errtp##.out, exec##.cmds ideas##.psf *.prg, *.unv, and others

%SDRC_SCRATCH% .ideas##.psf

Note: The .ideas_paramX system parameter file, located in the ...\Team\Master\Config folder by default, contains the specification of the Team.* directories. The DataMgmt.* directory files go by default to the current working directory. These defaults can be set globally, in the .ideas_paramX file, and those settings can be overridden by user preference settings.

Files Generated by NX I-deas

Additional information on the files generated by NX I-deas is provided in the NX I-deas online Help Library. See the Files Generated by I-DEAS article in the General I-DEAS Administration section of the NX I-deas online Help Library.

NXI5_WINInstl

Documents

Transcript of NXI5_WINInstl