Академический Документы
Профессиональный Документы
Культура Документы
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
New Features
New Features for NXI-deas Installation
Installation Process Changes
New Name for Installation Location
Changes to IDEAS_PARAM and Site-Wide Parameter File
Licensing Changes
1
2
2
2
2
Installation
Chapter 1
Installation Requirements
What You Received
Optional
System Requirements
Installation Recommendations
Installation Preparation
Set Up the System
Set Up an NX I-deas Administrator Account
Set Up User Accounts
Review Required Operating System Tasks
Preparing to Install Licensing
Obtaining Your License File
6
6
7
7
7
8
8
8
8
9
9
9
iii
Chapter 2
Chapter 3
Chapter 4
11
12
13
13
14
16
16
17
18
Installation Migration
21
Migration Overview
Migration Process
Migration Considerations
Migrating from Older Releases
Preparing your Data for Migration
Migrating the Installation
Data Products Migration
22
22
22
22
24
27
30
Install NX I-deas 5
31
Chapter 5
Chapter 6
iv
33
33
36
TDI Wizard
39
40
41
45
46
46
47
47
48
49
50
50
50
51
51
51
Chapter 7
Chapter 8
Web
Installation Procedure
I-DEAS Access to the Help Library
52
53
55
57
58
62
63
63
64
65
65
Uninstall
67
68
68
Chapter 15 Troubleshooting
Errors During the Installation Process
IDEAS_PARAM12 and SDRC_MPATHS are not defined
Time Out Warning
I-DEAS Customer Support
69
70
70
70
71
A-1
A-2
A-2
A-3
A-3
A-4
B-1
B-2
B-2
vi
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
or
UGII_FLEX_BUNDLE = A027
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
Installation Requirements
To install NX I-deas software, youll 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
a software license, which can be requested via e-mail, fax, telephone, or the web,
according to the instructions provided later in this guide.
The guides and notes listed below are delivered as .pdf files on the Readme directory of the
installation DVD. Its 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
the NX I-deas 5 Release Notes, which contain last minute information about the NX
I-deas software and installation
Optional
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 thats 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).
Installation Preparation
Before installing the NX I-deas software, complete the following tasks.
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.)
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.
Create shortcuts
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.
10
Chapter 2
Refer to the Site Planning and Implementation Guide for information on planning your
configuration.
11
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.
12
2.
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.
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.
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.
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.
3.
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.
14
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.
Run NX I-deas.
Select Start->Programs->NX I-deas X->NX I-deas X.
b.
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.
2.
16
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 standalone 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.
4.
1.
2.
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.
6.
7.
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.
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.
.
MTS Systems License Server.msi
INSTALLDIR
LICENSEFILE
Java.msi
INSTALLDIR
ALLUSERS
Orbix.msi
18
INSTALLDIR
DOMAIN_NAME
NODE_DAEMON_PORT
The default TCP/IP port for use by the ORB node daemon.
NAME_DAEMON_PORT
CFR_DAEMON_PORT
LOCATOR_DAEMON_PORT
NX I-deas NX Series.msi
INSTALLDIR
DEFAULT_TDI
FLEXLM_PORT
LICENSESERVER
MTS_FLEXLM_PORT
MTS_LICENSESERVER
SDRC_MPATHS
STARTINDIR
JAVA_HOME
IT_PRODUCT_DIR
IT_DOMAIN_NAME
The name of the domain to use with the IONA E2A ORB
(Orbix)
ResourceLocking.msi
INSTALLDIR
SERVICENAME
FLEXLM_PORT
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.
20
Chapter 3
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).
21
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 Ideas migration.
Migration Considerations
NX I-deas data is not backward-compatible. Once its accessed by the new version of NX I-deas,
it cant 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 theres 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.
22
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.
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.
g.
Send the package file to a directory you can access from the Master Series
installation.
Installation Migration 23
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.
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.
Run a full backup of the entire I-DEAS Team Data Installation (TDI).
2.
3.
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 IDEAS 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.
24
4.
5.
Open a command prompt window and run Setup_Varbs.cmd to set your environment
variables.
b.
c.
Run dmadmin.cmd.
d.
e.
f.
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.
You should correct errors found in these three tables before continuing with migration.
h.
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 projects 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.
Installation Migration 25
The CL command removes the tables 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.
6.
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.
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
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 Ideas11\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.
26
7.
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.
Note: After the backup is complete, its important to verify the accessibility of files and the
integrity of the media on which the backed up files are stored.
2.
Exit I-DEAS.
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\Hummingbird\ Exceed
Note: The existence of registry entries from previous versions of I-DEAS can interfere with
the performance of the new version.
4.
5.
Installation Migration 27
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.
c.
Enter the domain\username and password of the account that you will use for the Ideas SFAM Component. Depending upon the SFAM level of your installation, this
is the account that will own your NX I-deas data
d.
e.
Review the information on the Confirm Selections page underneath the Selection
Summary and select Next.
28
reads the parameter file to locate the team data installation to migrate.
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.
5.
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.
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.
Installation Migration 29
30
Chapter 4
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.
31
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.
32
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.
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.
Install NX I-deas 5 33
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.
34
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.
Install NX I-deas 5 35
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.
36
7.
Pick NX I-DEAS Setup double arrows from the right side of the Launch screen.
8.
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, its 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.
Install NX I-deas 5 37
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.
38
Chapter 5
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.
39
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.
40
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.
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 TDIs in your environment in
TDI Wizard 41
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 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.
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
42
reasons, this account should not have administrator or power user privileges. It does,
however, require the following security policy settings:
Log on as a service
Log on locally
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.
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.
TDI Wizard 43
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.
44
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.
TDI Wizard 45
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.
46
This means that command line settings and system environment variables will override the
equivalent entries in the registry
TDI Wizard 47
From the Start menu, pick (All) Programs->NX IDEAS 5->NX I-DEAS Command Prompt
2.
3.
Run dmadmin.
4.
5.
6.
Enter the corresponding number for the data products you want loaded. You can enter
as many numbers as desired.
7.
8.
48
Chapter 6
49
Whats New
On Context
Help Library
Web
Quick On/Off
About I-DEAS
The Whats 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 Whats New article automatically
displays when you first log into the new version of I-DEAS.
The automatic display of the Whats 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 dont want to display the Whats 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 o ff 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 youre 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.
50
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.
2.
3.
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.
6.
Select Open under the Actions section and pick the Edit button.
7.
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 companys web site:
1.
2.
52
Installation Procedure
After installing I-DEAS, its 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.
2.
Pick Install I-DEAS NX Series 12 Help Library from the Launch screen.
3.
4.
5.
Click Next and then Install to perform the installation of the Help Library.
54
56
Chapter 7
57
2.
3.
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.
58
3.
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.
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.
60
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.
5.
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:
62
Note: To remove an installed product feature without removing the entire product, use the
REMOVE option.
Archive Reader/Writer
O002
Design Examples
O003
Manufacturing Examples
O004
Simulation Examples
O005
Test Examples
O006
O007
O008
O009
O010
IPLOT
O012
O014
O015
O016
O017
O018
O019
O020
O021
O023
Please note that optional products begin with the letter O and end in a number that may be
prefixed with zeros.
64
French
German
Italian
Japanese
Korean
Spanish
Chinese
ChineseT
66
Chapter 8
Uninstall
This chapter describes how to remove the I-DEAS software from your workstation.
67
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.
68
1.
2.
Chapter 9
Troubleshooting
This chapter includes troubleshooting information for:
Error messages and problems that could occur during the installation process
For additional error message descriptions, problem discussions, and recovery solutions, see the
Resolving Problems article in the Help Library.
69
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.
70
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.
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 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.
Troubleshooting 71
72
Appendix A
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-1
Java version 1.5.0 or higher must be defined in the PATH of the users profile.
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.
3.
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-2
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.
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.
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 Users Guide,
Solving the Model section.
From the Simulation, Model Solution application window, pick the Manage Solve icon to access
the Manage Solve form.
2.
3.
a.
b.
c.
Pick Solve. Both the QMan Client window and Submit Job forms display.
A-3
a.
Jobname (auto-fills) the name of the SAS batch job the client submits.
b.
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.
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.
3.
4.
Enter the full path of the QMan Server or browse to the directory.
5.
Pick OK.
6.
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.
From the Simulation, Model Solution application window, pick the Manage Solve icon to access
the Manage Solve form.
2.
b.
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.
A-4
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.
Note: The user only needs to specify the server the first time it is accessed.
3.
Jobname (auto-fills) the name of the SAS batch job the client submits.
b.
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.
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.
2.
3.
Pick OK.
Note: For more information on how to fill out the forms, pick Help on the QMan Client window.
A-5
2.
A-6
Appendix B
B-1
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)
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*
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.
B-2