Professional Documents
Culture Documents
Contents
Introduction
Chapter 1
Chapter 2
Chapter 3
1
Best Practices for Site Planning
Migration Process
Perform the Migration in Phases
Dont Skip the Preparation Phase
Test the Migration
Migrating to a Different Platform Type
Merging Team Data Installations Using File, Import/Export
8
9
9
10
13
14
15
Configuration Considerations
Hardware Platforms
Number of I-DEAS Users
Geographic Distribution of Development Sites
Team Collaboration
Example Configurations
Standalone Workstation Configuration
Distributed Configurations
16
16
16
16
16
18
18
19
iii
Chapter 4
Chapter 5
Chapter 6
iv
25
25
26
26
29
30
30
30
31
37
37
38
40
41
44
45
46
46
47
49
50
50
51
52
52
53
54
54
54
57
Design Considerations
Installation Recommendations
Operating System Environment
I-DEAS Software Installation
I-DEAS License Manager Service
Team Data Installations
Data Management Setup
Data Flow Evaluation
58
59
59
60
60
61
61
61
Chapter 7
Chapter 8
63
63
65
66
67
68
68
68
69
70
71
71
72
73
74
74
75
75
76
77
77
78
79
80
81
82
83
85
87
System Requirements
Process Overview
HT Setup Process during Initial I-DEAS Installation
HT Setup Process after I-DEAS Installation
Setup Tasks
Plan the Heterogeneous Team Configuration
Special Considerations for Windows XP
Install I-DEAS on the UNIX Heterogeneous Team Server
Install and Configure a Validated Connectivity Solution
Prepare the Microsoft Windows Client Workstations for HT Setup
Install I-DEAS on Microsoft Windows Client Workstations
88
89
89
90
90
90
92
92
93
93
93
97
98
98
100
104
105
106
107
108
109
Appendix B
vi
A-1
A-2
A-2
A-2
A-2
B-1
B-2
B-2
B-4
B-4
Introduction
I-DEAS is a powerful software tool used as an integral part of product development in a wide
range of business environments. Because of this, there is a range of methods available to
implement I-DEAS.
Whether this is a first-time installation of I-DEAS or youre migrating from a previous software
version, its important to plan the implementation method for your site.
Purpose
The goal of site planning is to design an I-DEAS installation configuration thats efficient to
implement and maintain, and that reflects the product development environment at your company.
The purpose of this guide is to inform you of the options and considerations in designing the
I-DEAS installation configuration thats suitable for your site.
Installation Configurations
Youll use the last two sections of this guide only if your company is considering the
implementation of heterogeneous team. Heterogeneous team is described in the Installation
Configurations section as one of the I-DEAS configuration options.
UNIX uses a forward slash (/) between directory levels; Microsoft Windows uses a back slash
(\).
For certain files, UNIX precedes a filename with a dot (.) to hide the file and provide a level
of security; Microsoft Windows does not.
Microsoft Windows uses a three-character extension on some filenames; UNIX does not.
Microsoft Windows may use uppercase characters in filenames; UNIX does not.
In most cases, I-DEAS environmental variable names are the same across platforms, such as
SDRC_INSTL and IDEAS_PARAMX.
Note: The X in the names of some directories, files, and environment variables referred to
throughout this documentation represents the current I-DEAS software release number. For
NX I-DEAS 5, for example, the IDEAS_PARAMX environment variable translates to
IDEAS_PARAM13
For environment variable syntax, UNIX uses a preceding $, such as $HOME. Microsoft
Windows uses surrounding %, such as %HOMEPATH%.
Customer Support
For support on installing, configuring, or using the I-DEAS software, go to the Global Technical
Access Center (GTAC) site at the following URL:
http://support.ugs.com/
If you have a current maintenance contract you can submit a support request via the web or
contact the support center directly using the toll free number provided.
Youll need a WebKey account to file a support request via the web. Information on obtaining a
WebKey account can be found in the following document at that site:
http://support.ugs.com/webkey_faq.pdf
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.
Introduction 3
Installation Guide
There are separate versions of the installation guide, one for UNIX and one for Microsoft
Windows.
The installation guide takes up where the Site Planning and Implementation Guide leaves off. For
example, planning for migration is covered in the site planning guide, and the migration
procedures are provided in the installation guide. Also, installation guidelines are covered in this
site planning guide, but the installation procedures are in the installation guide.
For a complete understanding of the I-DEAS setup requirements, its important to use this guide
together with the installation guide for your platform.
The installation guides are delivered as .pdf files on the I-DEAS installation CD, in the Readme
directory.
Release Notes
The Release Notes supplement the I-DEAS product information and include any last minute
information you may need to know.
The Release Notes document is delivered as a .pdf file on the I-DEAS installation CD, in the
Readme directory.
Readme Files
Readme files are installed with the I-DEAS product (in the Readme directory) and provide
information on technical topics that may not be covered elsewhere in the I-DEAS documentation.
Information found in readme files is generally considered supplemental information.
Chapter 1
Learn about the I-DEAS installation configuration options and setup requirements.
Do this by studying the I-DEAS Installation Configurations chapter of this guide.
Learn about the I-DEAS data management options and setup requirements.
Do this by studying the I-DEAS Data Management Setup chapter.
Document the key information gathered, and the decisions and recommendations made during
the site planning process.
Chapter 2
Migration Process
Following are the tasks involved in the migration process:
Prepare for Migration
1.
2.
Back up the previous version parameter files, security files, and any files created or modified
for site-specific purposes, such as program files.
3.
4.
5.
Check and clean the data installation and project files. This is accomplished using dmadmin
commands, as described in the Installation Guide.
Note: For this, you should use the version of dmadmin from your current I-DEAS release (not
the NX I-DEAS 5 version).
Note: If youre migrating a data installation in a Heterogeneous Team (HT) environment, run
dmadmin on the platform type compatible with the .imd and .pmd files in your installation.
6.
Run the idfvfy utility to verify the structural hierarchy integrity of the I-DEAS data
installation.
Note: If youre migrating a data installation in an HT environment, verify that no
incompatible database type errors occur on the .pmd files. If they do, run the HDS convert
utility on those .pmd files.
For information on using the HDS utility, see the Data Sharing Administration article under
I-DEAS General Administration in the I-DEAS online help.
7.
9.
10. Install NX I-DEAS 5 using the process described in this guide and the procedures described in
the Installation Guide.
If the log file includes a warning message that indicates errors in project migration,
contact customer support.
If the log file indicates a succesful migration (no warnings), run NX I-DEAS 5 and
perform the following verification operations:
-
Browse the libraries using the Manage Libraries form to verify that the libraries you
migrated exist in the installation.
Perform some simple check in and check out operations to verify that interaction
with the libraries is operational.
If some model files were included in the migrated data, open a sampling of the
model files to verify that the expected relationships between project and model file
and model file items exist.
Performing the tasks listed in the preparation phase is also recommended as an ongoing practice
for maintaining the integrity of your I-DEAS data installation(s). Its recommended that you
include those tasks in your standard maintenance practices.
Install NX I-DEAS 5 on a disk and directory thats NOT visible (mapped or mounted) to the
I-DEAS installation (production environment) youre migrating from.
Note: See the NX I-DEAS 5 Installation Guide for UNIX or Windows for installation
procedures.
a.
During the team data installation portion of the installation process, use the method that
allows you to enter the Team Master ID for the data installation.
On UNIX, this is the default method. On Microsoft Windows platforms, this is the Create
a custom configuration option.
b.
2.
Enter the Team Master ID value assigned to the data installation for which youre
performing the test migration. (Its defined in the I-DEAS parameter file.)
Place a copy of the .imd file from the previous version data installation you want to testmigrate in the Team Master Directory you defined during the NX I-DEAS 5 installation.
This will overwrite the .imd file generated during the NX I-DEAS 5 data installation setup.
3.
Place a copy of the .pmd files from the previous version data installation you want to testmigrate in the Team Projects Directory you defined during the NX I-DEAS 5 installation.
4.
Verify that the I-DEAS production environment youre migrating from cannot be accessed
from your NX I-DEAS 5 installation environment.
5.
10
<drive>:\UGS\I-DEAS13\bin\dmadmin
a.
6.
7.
If the location of the test .pmd files is different than whats defined in the .imd file (since
youre working with copies), a prompt for the location of the .pmd files displays. Enter
the directory path to your test .pmd files. This is the Team Projects Directory you defined
during the NX I-DEAS 5 installation.
If the log file includes a warning message that indicates errors in project migration,
contact I-DEAS customer support.
If the log file indicates a succesful migration (no warnings), run NX I-DEAS 5 and
perform the following verification operations:
-
Browse the libraries using the Manage Libraries form to verify that the libraries you
migrated exist in the installation.
Perform some simple check in and check out operations to verify that interaction
with the libraries is operational.
Record any pertinent information for your migration planning. This could include:
a list of the migration preparation tasks that were performed on the data installation prior
to the test
This information is most important if you have multiple data installations to migrate. An
evaluation of the information you gather during testing could be used in defining the
migration plan and schedule to implement for your site.
UNIX
<server>->/ugs/ideas13/ideas/.ideas_param13
Microsoft Windows
<drive>:\Team\Master\Config\ideas_param13.dat
Create separate directories for the .imd and .pmd files, /team2/test/ and /team2/test/projects,
for example.
2.
Place a copy of the .imd file from data installation 2 in the directory you defined for the .imd,
/team2/test, for example.
3.
Place a copy of the .pmd files from data installation 2 in the directory you defined for the
.pmd files, /team2/test/projects, for example.
4.
Locate a copy of the NX I-DEAS 5 parameter file within that test directory structure,
/team2/test/param13, for example.
5.
6.
Set the Team Master ID parameter to the correct value for the data installation, 2 in this
example.
Set the Team Master Directory parameter to the location of the .imd file, /team2/test/ in
this example.
Set the IDEAS_PARAM 13 environment variable to point to the team2 test parameter file
location. Following is example syntax, by platform:
UNIX
IDEAS_PARAM13=/team2/test/param13; export IDEAS_PARAM13
Microsoft Windows
set IDEAS_PARAM13=\team2\test\param13
12
7.
Follow the procedures in the Test the Migration section above, beginning with step 4, to
complete the migration test for the data installation.
2.
Perform the migration process described above in your current homogeneous environment.
3.
Perform the HT setup and data migration processes described in the HT Setup chapter.
Use File, Export, I-DEAS Library Data to create package files of the shared data from one
installation that you want to add to another data installation.
2.
Use File, Import, I-DEAS Library Data to import the package files into the desired data
installation.
3.
Perform the migration process (as described in the previous sections) on the merged data
installation.
Note: HT does not automatically run HDS conversion on a package file at import. It converts
the item files at library checkout.
If you know the predominant platform type the items in the package file will be used
on, you could manually run the HDS utility on that platform type before import. This
improves performance because the need for HT conversion at library checkout is
eliminated for the library items imported from the package file by the predominant
platform type.
For information on using the HDS utility, see the Data Sharing Administration article under
I-DEAS General Administration in the I-DEAS online help.
For information on using File, Import/Export, see the Sharing Library Items with Other
Installations section of the Project Management User's Guide in the I-DEAS online help.
14
Chapter 3
I-DEAS software
This chapter provides examples of I-DEAS installation configurations and their design intent. Use
the information in this chapter as an aid in determining the appropriate installation configuration at
your site.
15
Configuration Considerations
Following are the key components that influence the design of an I-DEAS installation
configuration:
Hardware Platforms
I-DEAS runs on several hardware platform types including various Microsoft Windows and
various UNIX platforms. An I-DEAS installation can be configured with one or more of these
hardware platform types. I-DEAS data and licenses can be shared across platform types. This is
illustrated in the example configurations later in this chapter.
The latest information on I-DEAS system requirements can be found on the Global Technical
Access (GTAC) web site at:
http://support.ugs.com/
Number of I-DEAS Users
The number of users needing access to the I-DEAS software and data has a direct impact on the
design of your I-DEAS installation configuration. It will influence whether you implement
I-DEAS as a standalone or distributed installation and, if distributed, the number of servers in the
environment. This is illustrated and discussed in the example configurations later in this chapter.
Team Collaboration
Team collaboration and data sharing requirements will impact the design of your installation
configuration.
I-DEAS data management (IDM) supports team- and project-based product development.
This chapter provides an overview of IDM so you can understand the I-DEAS data installation
setup options shown in the configuration examples.
See Chapter 4, I-DEAS Data Management Setup, for a detailed description of the IDM
components and setup structure.
16
model files
libraries
catalogs
Model files are used to store private (user) data. Shared (team) data is stored in libraries and
catalogs.
Example Configurations
I-DEAS installation configurations range from a standalone workstation to a wide variety of
possible configurations in a distributed installation environment.
Some possible configurations are described in this section.
sites where designers work on separate projects and rarely, if ever, share data
mobile workstations, such as laptops, which may be periodically disconnected from the
distributed installation environment
You could use base IDM in this configuration and, when necessary, share team data using the
I-DEAS File, Export/Import capability.
Standalone Workstation
Configuration
Orbix
I-DEAS
License Manager
Software
Team Data
18
Distributed Configurations
In a distributed configuration, the components of an I-DEAS installation can be distributed across
multiple workstations.
Distributed configurations enable seamless data sharing among I-DEAS users and enhance the
efficiency of software license management at sites where many users will access the I-DEAS
software applications.
The actual configuration of a distributed environment varies from site to site. Factors such as data
sharing requirements, number and geographic location of users, available hardware, and system
performance requirements will influence the configuration design for your site.
Typical distributed configurations are described and illustrated on the following pages. Typical
distributed configurations include:
Workgroup Configuration
Multi-server Configurations
Workgroup Configuration
The workgroup configuration might be used at I-DEAS sites where there are only a few I-DEAS
users accessing I-DEAS software applications and sharing team data.
Workgroup Configuration
local disk
I-DEAS software
user data
Server Workstation
shared disk
local disk
I-DEAS
software
local disk
user data
Client Workstation A
I-DEAS
software
user data
Client Workstation B
20
local disk
I-DEAS
software
I-DEAS Help
Library
local disk
user data
Client Workstation A
I-DEAS
software
user data
Client Workstation B
This configuration includes one server workstation and multiple client workstations.
Dedicating the server workstation to serving I-DEAS licenses and team data can enhance IDEAS performance across the distributed environment.
Locating the I-DEAS software on the local client disks further optimizes performance.
Base IDM could be used successfully in this configuration. The shared library would be
located on the server disk.
Storing the I-DEAS Help Library on the server disk for remote access would save disk space
on the client workstations.
I-DEAS Software
I-DEAS Online Help
local disk
local disk
user data
Client Workstation A
user data
Client Workstation B
This configuration includes one server workstation and multiple client workstations.
The server is used to manage licensing and resource locking, serve team data, and store and
serve the I-DEAS software and online Help Library.
This configuration is suitable for small to medium sized I-DEAS installations. The network and
server disk space must be monitored to ensure the capacity is sufficient for efficient I-DEAS
processing and file service to the installations user base.
22
Multi-server Configuration
A multi-server configuration would be used only for I-DEAS sites with a large number of users
(50 or more) running I-DEAS.
Multi-server Configuration License and Team Servers
server disk
server disk
team data
license
manager
License Server
Workstation
local disk
I-DEAS
software
local disk
user data
Client Workstation A
I-DEAS
software
user data
Client Workstation B
In these large distributed configurations, its best to dedicate a single, stable workstation as the
license server. A separate workstation can be set up to serve team data.
Software Code Server
Some multi-server configurations include one or more I-DEAS software servers, also known as
code servers. Running I-DEAS software across the network will increase network activity
thereby reducing software performance. If youre considering including a code server in your
multi-server configuration, be sure your network can handle the increased traffic.
local disk
Team Directories
I-DEAS Online
Help
Shared Files
Global Parameter
File
(UNIX version)
I-DEAS Software
MPM File
UNIX/Windows
Connectivity Solution
local disk
Domain account*
user data
User Files
Client Workstation A
Windows
I-DEAS Software
I-DEAS Online
Help
Client Workstation B
UNIX
I-DEAS licenses can also be shared across platform types. For example, a UNIX license manager
service can manage I-DEAS licensing and resource locking on Microsoft Windows. This is
required in an HT environment and could also be implemented outside an HT environment.
24
Workstation Recommendations
The hardware configuration you choose for a workstation depends on:
the size and complexity of the drawings or models created or used at the workstation
the amount of disk space required for local software and data
On Microsoft Windows workstations, SCSI disks are recommended for increased performance of
3D and Simulation applications.
The latest information on I-DEAS system requirements can be found on the Global Technical
Access (GTAC) web site at:
http://support.ugs.com/
Use local (not remote) operating system, scratch space, and swap/pagefile space.
Avoid network overload by minimizing the number of workstations per subnet and putting
non-I-DEAS systems on a separate network from I-DEAS.
TCP/IP and NETBIOS are required for I-DEAS. Avoid loading the NETBEUI protocol
because it tends to send chatter on the network and is not required for I-DEAS.
Server Recommendations
When I-DEAS responds to user requests for access to team data, it relies on the performance of the
server to respond to the disk access requests. The following are important considerations for
servers:
Disk Access:
A dedicated network attachment to your main network backbone or to your isolated I-DEAS
network (if you have one).
Memory:
RAM needs are based on the number of clients and shared disks on the network.
Network Load:
Disk Management:
Attempt to balance the load across all server disks and disk controllers (RAID, etc.).
26
Filesystem Types:
Use NFS (UNIX) or NTFS (Microsoft Windows) for disk sharing. FAT is not supported.
Server Class Machine:
A server class machine should be used for any server in an I-DEAS distributed configuration. This
includes the NX license server, the I-deas resource lock server, team server, and code server.
28
Chapter 4
29
I-DEAS Projects
An I-DEAS project is a user-defined top level organization method for managing all data
created or accessed by the I-DEAS software. When you start the I-DEAS software you must
specify a project to work in. Once a project is set up, all users in a data installation can access the
project, unless access privileges are restricted through project configuration. The I-DEAS project
configuration capability is described in the Configuring Projects section later in this chapter.
Within a project, the following containers are used to store data:
model file
library
Model file
A model file is used to store private user data. Private user data is either work-in-progress data, not
yet released to the shared environment, or application data that cannot be stored in a library (such
as manufacturing data).
A model file is made up of a workbench and any number of bins.
30
Bins within a model file organize and hold data in temporary storage.
Library
A library is used to organize and manage team shared data. Shared data may include parts,
assemblies, drawings, and finite element models.
Data sharing is accomplished by the ability to check out, reference, and copy specific versions of
shared data items from a library into the users model file. Depending on the check out status, the
user can modify the item in their model file then check a new version back into the library so its
available to the team.
Catalog
A catalog is used to store standard parts, features, and materials. Only data that is not likely to
change should be placed in a catalog.
Pre-defined catalogs, such as Features, Fasteners, and Materials, are available.
Project structure
The following figure shows the typical structure of projects within a data installation. Note that
each project can have any number and combination of containers within it for storing data.
Project B
- Library
Standard Parts
- Catalog
- Model File or
other data file
Organizing Projects
Since I-DEAS data management is organized around private user data and team shared data,
consider using a combination of user projects and team projects.
User projects can be used for early development and ongoing work.
Team projects can be used to store parts, assemblies, and other files shared by the team in
product development and production efforts.
User projects
are for early
development
and ongoing
work
User1_project
User2_project
Team Project1
User3_project
Team Project 2
Following are some examples of how working within user and team projects can be organized:
User Projects: Everyone works in their own project. There are no team projects or data
sharing.
User and Team Project: Everyone works in their own project until they want to finalize a part,
then they move it into the team project.
User and Many Team Projects: This is the same as the user and team project except there are
a number of team projects.
The best data management performance can be achieved by using a combination of user and team
projects.
Keep your I-DEAS project sizes reasonable in terms of the number of parts, assemblies, libraries,
and other shared data stored in the project. For example, a product with four subassemblies could
be organized in a single project. A better solution might be to create four projects, one for each
assembly. A fifth project could be used for integrating the assemblies to create the entire product.
Design the I-DEAS project environment to complement the process you use for product
development at your site.
32
Grouping Projects
Related projects can be organized by adding a group or sub-group name as a prefix to the project
name when the project is created. This can be done by separating the group and project names
with a period (.), or other delimiter character thats defined in the I-DEAS parameter file.
Grouping projects affects only the organization of how projects are displayed on I-DEAS
screens and reports.
The top level project(s) in a project group or sub-group may contain no data and be used only
to define the project organization.
Note: The I-DEAS administrator must activate this functionality using the
DataMgmt.HierarchySeparator parameter in the I-DEAS parameter file. See the Data Installation
Setup section of this chapter for more information on the I-DEAS parameter file.
Configuring Projects
Configuring projects adds a level of security and organization to the development and
maintenance of your I-DEAS data. You can use the I-DEAS configure projects capability to create
a project structure that represents the product development cycle at your site.
The procedure for configuring projects is provided in the Project Management Users Guide in the
I-DEAS online Help Library. A general description of configured projects is provided here so you
can consider use of configured projects at your site.
In a configured project, you can control who has access to the project, their role within the project,
and when they have access to specific data as it moves through the product development cycle.
When you configure a project, youll define the following attribues:
Roles: members assignment(s) within the project. Designer, analyst, drafter, reviewer, and
project manager are all examples of roles.
States: the stages a product moves through within the product development cycle. Design,
analysis, notation, review, and release are all examples of states.
Item Access: the privileges members have to access items in a particular state. This is
managed through role assignments and permissions set for the role and state.
Only the user assigned the role of project manager can create libraries and catalogs within the
project. This enables strict adherence to the project organization.
The project manager can control user attributes for the project.
Project members can reserve items (part, assembly, etc.) within the project.
The Change Control task within the I-DEAS Management application is available. This
provides a change order tracking mechanism like ECR or ECO.
Note: The Notification.Tracking parameter in the I-DEAS parameter file must be set to ON for
e-mail notification to work. E-mail notification tracking is OFF by default. See the Data
Installation Setup section of this chapter for more information on the I-DEAS parameter file.
The following diagram illustrates the setup of a configured project used to manage access control:
Start design
or design change
no
34
Complete?
yes
Approve to
released
sta te
Within the I-DEAS software, the form that lists item access on a file as a function of data states
and roles might show something like the following:
ROLE
STATE
TEAM MEMBER
WORLD
MANAGER
ALL STATES
RWCDA
RWCDA
INITIAL
RWCDA
RWCDA
RELEASED
RC
RWCDA
As indicated by this diagram, the read (R), write (W), copy (C), delete (D), and approve (A)
abilities are assigned based on the individuals role.
There are many benefits to using configured projects. Their use provides a means of ensuring that
design changes follow the proper channels in your organization and that ISO9000 requirements
are met. It also presents an opportunity to evaluate your current design process and map your
product development strategy to I-DEAS data management.
Before configuring projects, evaluate and diagram the product development cycle, design process,
and data life cycle models at your organization. Flow chart diagrams are suitable for this purpose.
During this evaluation, youll probably identify some tasks within your cycle as paper (or
documentation) only. These tasks do not translate into a configured project state in I-DEAS. A
product data management (PDM) system is needed to track and manage paperwork online.
See the Data Installation Setup section of this chapter for guidelines on how to set up multiple data
installations.
Data Management
Installation 1
Data Management
Installation 3
Data Management
Installation 2
Export/
Import
Additional information on sharing data between installations is provided in the following articles
in the I-DEAS online Help Library:
Sharing Library Items with Other I-DEAS Installations in the Project Management Users
Guide
36
The I-DEAS parameter file controls the configuration of the data installation for an I-DEAS site
and provides default data management preferences for the installation.
The installation metadata file is the master database file for the I-DEAS data installation. It
includes the following four pieces of information:
the location of the project metadata file associated with each project
The project metadata files contain a wide range of information on all the items and item
relationships associated with each project.
The following graphic shows how these files work together.
Note: The directory locations and filenames shown below are for UNIX.
\team\master\username_param
Installation Metadata File
Parameter
Files
\t
\
t \id
Xd t
Team.MasterID=xxx
Team.MasterDirectory= \team\...
\team\master\
z_masterxxx.imd
NAME
Team.ProjectsDirectory=\team\...
PATH
ProjectA \team\projects\proja.pmd
ProjectB \team\projects\projb.pmd
\team\projects\
projb.pmd
Project
Metadata
File
PARENT
ITEM
TYPE
Test1MF
NewParts
Part1
ACCESS
zzz
yyy
xxx
Microsoft Windows
<drive>:\Team\Master\Config\ideas_paramX.dat.
UNIX
$SDRC_INSTL/ideas/.ideas_paramX.
Many parameters are contained in this file, but only a few are directly related to the definition of
the data installation. These are referred to as the team parameters. The key team parameters
include:
Team.MasterID
Team.MasterDirectory
Team.ProjectsDirectory
Team.ScratchDirectory
Team.SharedDirectory.
DataMgmt.UserDirectory
DataMgmt.ScratchDirectory
The settings for these parameters are defined during I-DEAS installation. You can use the default
settings, or customize the settings based on the configuration you design for the I-DEAS data
installation at your site. This topic will be expanded upon in the Site Planning Considerations and
Installation Guidelines chapters.
38
Hierarchical Organization
of Data
Location of Files
on Operating System
(default paths)
Team.MasterDirectory
(...\team\master)
Installation (Team.MasterId)
Project A
Project B
Team
Scratch
Files
Library Catalog
Library
DataMgmt.UserDirectory
(current working directory)
Model Other
File
File/
bins Types
Model Other
File
File/
bins Types
.mf1
.unv
.mf2
.prg
DataMgmt.ScratchDirectory
(current working directory)
User Scratch Files
.sf1
.sf2
By default, the installation program sets the Team.MasterId parameter to 0 (zero) and all users
access the same data installation.
This parameter value should not be modified unless there is a need to create multiple data
management installations or a single-user data installation.
A Team.MasterId set to a positive integer or zero indicates a team data installation that can be
accessed by many users.
A Team.MasterId set to a negative integer indicates a single user data installation. (The first
person to access the installation using I-DEAS or the dmadmin utility owns it and there is no
data sharing.)
If there is more than one data installation in your I-DEAS environment, each data installation
must have a different Team.MasterId. Otherwise, item name collisions and lockout situations
can occur.
For guidelines on creating multiple data installations and single-user data installations, see the
Multiple Team Data Installations Setup and Single-user Data Installation Setup sections later in
this chapter.
40
For users to share project items, the project metadata files (z_projname.pmd) must exist on a
common (server) disk. Following is the default location for these files, by platform:
Microsoft Windows
<drive>:\Team\Scratch\
UNIX
$SDRC_INSTL/team/projects/
Team.ScratchDirectory
The Team.ScratchDirectory contains the project shadow files, z_projname.smd. Shadow files are
essentially backup copies of the .pmd files.
For data integrity, its recommended that you locate the scratch directory on a server, outside the
I-DEAS installation path. This directory should be common to all I-DEAS users.
Following is the default location for these files, by platform:
Microsoft Windows
<drive>:\Team\Projects\
UNIX
$SDRC_INSTL/team/scratch/
DataMgmt.ScratchDirectory
The DataMgmt.ScratchDirectory contains the temporary files created by I-DEAS. These include
the model file shadow files, *.sf1, *.sf2 and I-DEAS run-time files, *.app, and *.dsp.
The default location is the I-DEAS startup directory. The location can be modified using the
I-DEAS Options, Preferences, Data Management command.
The model file shadow files are important for data recovery. If you suffer a system crash, restart
I-DEAS on the same machine using the same project, model file, and scratch directory as when the
crash occurred. Recovery should be automatic and without problems. Dont remove the shadow
files until after the model file recovery.
Its recommended that these files reside on a local directory, but never in a temporary directory
such as the /tmp directory on UNIX.
42
Default
Purpose
Team.MasterID
Team.MasterDirectory
\team\master\
Team.ProjectsDirectory
\team\projects\
Team.SharedDirectory
\team\shared\
Team.ScratchDirectory
Team.ProjectsDirectory
(always on team server)
Team.MasterName
None
Team.HierarchySeparator
None
Team.TransactionRetries
30
Team.ExportPrivilege
General User
Team.ImportPrivilege
General User
Team.AdoptDirectPrivilege
General User
DataMgmt.UserDirectory
Present working
directory
DataMgmt.ScratchDirectory
Present working
directory
Parameter
44
When a team data management installation is created using the I-DEAS installation setup
program, the I-DEAS parameter file is created under the Team.MasterDirectory location being
created.
At startup, I-DEAS accesses the parameter file in the location defined by the users
IDEAS_PARAMX environment variable. If the variable does not exist for a user, I-DEAS
accesses the parameter file defined in the SDRC_INSTL\bin\setup_varbs.cmd file.
If a parameter setting in the I-DEAS parameter file is changed for a site with multiple data
installations, youll need to change the parameter setting in the I-DEAS parameter file for each
data installation.
See the I-DEAS Help Library for information on how to share data between team data installations
using I-DEAS data sharing.
2.
Set the Team.MasterID parameter in the installations I-DEAS parameter file to a unique
NEGATIVE integer.
3.
Set the users definition of the IDEAS_PARAMX environment variable to point to the
parameter file for the data installation.
As soon as the user accesses the data installation (based on the users definition of the
IDEAS_PARAMX environment variable), the installation is owned by that user alone. The
installation is accessible only to the first user to access it, for the life of the installation.
46
Team.MasterDirectory
Team.ProjectsDirectory
Team.SharedDirectory.
Specify the path to the I-DEAS parameter file in the IDEAS_PARAMX environment
variable setting.
Use the dmadmin utility, or start I-DEAS, to create the team data installation database.
See the previous sections of this chapter for information on the team directories, Team.MasterId,
and parameter file settings.
48
Chapter 5
Backup strategy
File security
License system
Resource locking
49
Backup Strategy
The associativity inherent to concurrent engineering becomes a challenge when backup, archive
and restore requirements are considered.
Whenever restoration of data from backup is required, the retention of data associativity requires
that the data be restored at the project or even installation level.
Associativity of items within a project may be lost if less than the entire project is restored.
Associativity between projects can be lost if less than the entire installation is restored.
The only way to ensure maintenance of associativity between projects is to restore the entire
data installation.
With this in mind, plan each I-DEAS data installation so its size never exceeds your backup
capabilities.
50
Backup Schedule
Back up the following team directories at least once daily:
Team.ProjectsDirectory
Team.MasterDirectory
Team.SharedDirectory
Team.ScratchDirectory
Locate user directories in a central, or consistent location to facilitate easier backup and
restoration through an automated process.
You can archive completed assemblies or subassemblies as theyre completed using the
I-DEAS File, Export capability. This can be useful for grouping all parts and drawings related
to an assembly or subassembly in one file, referred to as a library package file. The package
file can be archived for future use.
For additional information on using I-DEAS File, Export capability, see the Export (I-DEAS
Library Data) article in the Data Management guide in I-DEAS online help.
For additional information on backing up I-DEAS data, see the Data Installation Maintenance
article in the General I-DEAS Administration guide in I-DEAS online help.
File Security
As you consider the file security setup at your site, keep in mind that your file security system is
only as good as its weakest link. Good security begins with users having secret, hard-to-guess
passwords that are not shared with other users.
I-DEAS software is installed using an I-DEAS administrator account (usually ideasadm) and is
therefore owned by the administrator.
The security of I-DEAS data files is governed by the Secured File Access Model (SFAM) level
you set during installation, using the I-DEAS installation software.
Use the information in this section to determine the SFAM level to set for your site.
SFAM Levels
There are three levels of SFAM security. All three levels are available for UNIX. Only levels one
and two are available for Microsoft Windows.
Level 1
This option, the most open at the operating system level, gives users the greatest control of their
own data.
Level 1 is the default setting for I-DEAS on Microsoft Windows and is also available on UNIX.
With level 1, the team directories are owned by the I-DEAS administrator. Shared files are created
with read and write access for all user, group, and world accounts. This means the shared files can
be deleted at the operating system level, by any user.
Non-shared user and scratch data is created with each users default permission mask (umask) for
writing files. This enables each user to determine access permissions to their private files.
Level 2
This level increases the security of I-DEAS shared data, protecting it from being overwritten or
deleted at the operating system level.
Level 2 is the default setting for I-DEAS on UNIX. SFAM level 2 is available on Microsoft
Windows only in a heterogeneous team (HT) environment. See the Site Planning for
Heterogeneous Team and Heterogeneous Team Setup chapters of this guide for more information
on HT.
With level 2, the team directories and shared files are owned by the I-DEAS administrator.
Individual users cant access these files from the operating system. They can, of course, still
access the shared files using I-DEAS.
As with level 1, non-shared user and scratch data is created with each users default permission
mask (umask) for writing files. This enables each user to determine access permissions to their
private files.
52
Level 3
This option provides the highest level of security by protecting I-DEAS team files and user files
from being overwritten or deleted at the operating system level.
Level 3 is available on UNIX only.
This option is designed for companies that need to ensure the security access of I-DEAS user data
at the operating system. As with any high security system, this model requires additional
monitoring and support by the I-DEAS administrator.
With level 3, the I-DEAS administrator owns the team shared, team scratch, and user files and
directories. Individual users cant access these files from the operating system. They can, of
course, still access the team shared files and their own user files using I-DEAS.
Interface files, user scratch files, and runtime files are created with each users default permission
mask (umask) for writing files.
SFAM Guidelines
Use the following guidelines to determine which of the SFAM levels to set up during I-DEAS
installation at your site:
Use level 1 if your site has only a few users and your security and data sharing needs are
minimal, or if your users must have control over all files they create.
Use level 2 if you want to secure shared files at the operating system level but still allow users
operating system privileges on non-shared user and scratch files.
Use level 3 only if your site has very high security requirements and you and your users are
willing to work with severely restricted file access permissions.
Note: It is possible to change the SFAM level for your site after installation. As users create more
and more data, however, the challenge of changing the directory and file permissions to the new
level increases.
License System
This section provides background and critical information on the license system and license server
configuration for I-DEAS software licensing and data management resource locking.
The license manager daemon, lmgrd, communicates with the vendor daemon. It starts and
restarts the vendor daemon and manages the number of I-DEAS users.
The vendor daemon, uglmd, communicates with I-DEAS software applications and issues
license requests to the license manager daemon.
The license data file, ugnxX.lic, is generated by the I-DEAS installation software. This file
contains licensing data and the location of the vendor daemon.
The license system supports resource locking through application operation calls to the vendor
daemon to place locks on the data installation (.imd) and project (.pmd) metadata files.
Only one copy of the vendor daemon can be run on a workstation at a time.
Therefore, dont run multiple versions of I-DEAS on one machine.
54
A single data installation must never be accessed by more than one license daemon or data
corruption will eventually occur.
Therefore, avoid installing the license management system on more than one machine in a
distributed I-DEAS configuration.
56
Chapter 6
57
Design Considerations
When designing your I-DEAS installation configuration, you need to consider both the hardware
configuration and the data installation setup.
Considerations for data installation setup include ease of administration, data sharing
requirements, disk space requirements, and backup strategy.
Considerations for hardware configuration include ease of administration, system requirements,
performance, and costs.
A system thats configured for ease of administration is efficient to install and maintain.
Your hardware configuration must meet the system requirements for I-DEAS.
To achieve the best I-DEAS performance, you may need to exceed the minimum system
requirements and make some tradeoffs between ease of I-DEAS administration and
performance.
There are hardware costs associated with achieving the best possible software performance.
You may need to sacrifice performance to stay within your hardware budget.
With this in mind, use the guidelines in this chapter as an aid to designing the optimum I-DEAS
installation configuration for your site.
58
Installation Recommendations
The overall installation consists of the following interrelated parts:
disk availability
Is there enough disk space on each of the client workstations to store I-DEAS software and
user data?
Recommendations
1.
Set up your networks with physical segments that have no more than 710 nodes per segment.
2.
Create the team directories for your data installation on a stable, high-quality storage
device(s) with lots of room to grow.
3.
Recommendations
1.
2.
Install the I-DEAS online Help Library databases at the same location you install I-DEAS
software.
3.
Use consistent drive letter and path name conventions for the I-DEAS software installation on
each client.
Recommendations
Following are the recommendations for license server installation setup:
60
In a standard distributed installation, install the license manager service on the same machine
that has your team directory structure on it (single point of failure, rather than two points of
failure).
In a large distributed installation (more than 50 users), dedicate a single, stable workstation as
the license server. A separate workstation can be used to serve team data.
Install the license manager service on the servers local, fixed (non-mapped/non-mounted)
drive.
need for simultaneous access to (contention for) installation and project metadata files
Recommendations
Following are the recommendations for team data installation setup:
Plan and manage your installations so that they stay within the bounds of your computing
environments ability to function efficiently.
the names, locations, and file access privileges of the directories used for your engineering
data
the types of data files you exchange (drawing files, universal files, etc.)
what prompts the movement of a file or prompts one user to access another users file
the names, locations, and file access privileges of the directories used for your engineering
data
Make the diagram as complete and clean as possible. Youll be adding to it after you complete the
data organization evaluation. The following example may be helpful.
Following is an example of how you might illustrate your current data flow practice:
user
workstations
directories
\initial
\pre-release
shared disks
Server
disks/directories
62
\release
Include as much detail as possible in the description of data management practices. Specify disk
letters, directory paths, and references to other detailed documentation that may already exist for
your formal data management practices.
Data Organization
Data organization is the logical model that represents how people share data at your site.
Review your data flow diagram and data management practices description. Begin to develop an
organization for your product development work and data, in terms of I-DEAS data
management projects, libraries, and catalogs.
For example, you may already have distinctions between what is shared data (company-wide,
project-wide, or team data) versus what is private user data. You may have a commonly
accessible server disk with separate directories for preliminary work, work out for review, and
final (released) work. Or you may have a policy of giving copies of design data to others only on
an as-needed basis.
Consider the following:
how people share data files that comprise distinct project deliverables (models, drawings, etc.)
where that data resides on your system and how long its likely to be there
how people share reusable data such as standard parts and features
Update your data flow diagram and data management practices with information pertinent to the
design of your data organization.
Project Planning
The goal here is to map your current project structure into I-DEAS projects, libraries, and catalogs.
The following graphic shows one possible project scenario for a product consisting of a few
simple subassemblies:
Project
product_xyz
Shared Disks
subassembly_x
subassembly_y
Libraries
Other Files
subassembly_z
...\team\projects
\projects\product_xyz
In the preceding example, libraries are used to contain all the parts of the various subassemblies.
Alternatively, each subassembly could be a project, with yet another project created to assemble
the whole product. Catalog parts are stored in a separate, neutral project.
Create a diagram or flowchart showing the ways you might set up projects for your site. Consider
the following:
64
What projects youll need to get started. By default, user projects are created as users begin
working in I-DEAS. Determine the team projects youll need to create for product
development.
What libraries and catalogs will you create to support the product development within the
project?
Do you want to create configured projects to define the data flow for the product development
cycle within projects?
The I-DEAS license manager service must be installed on the servers local, fixed (nonmapped/non-mounted) drive.
This ensures that the license manager is available for automatic startup when the system is
booted.
I-DEAS software should be installed on a local disk to ensure optimum performance of the IDEAS applications software.
Note: If you do plan to run I-DEAS software from a server, be sure your network can handle
the increased traffic.
Use consistent drive letter and path name conventions for the I-DEAS software installation on
each client.
This is recommended for easier system administration, but is not required.
Map or mount the appropriate drive letter from the clients to the server machine prior to
running the I-DEAS installation software to set up your I-DEAS installation configuration.
Implementation Guidelines
Review the next chapter, Installation Guidelines, to determine the appropriate process for
implementing the configuration using the I-DEAS installation software.
Label each workstation in the configuration diagram with the appropriate installation setup type
(for Microsoft Windows) or the installation option (for UNIX) to use on that workstation during
setup. Using this method, you can develop a process for efficient implementation of the I-DEAS
installation configuration youve designed.
Following is an example diagram for a standard I-DEAS installation configuration in a Microsoft
Windows operating system environment:
server
disk
Server
Workstation
local
disk
I-DEAS
software
user data
Client Workstation
A
Software Installation Only
Setup Type
66
local
disk
I-DEAS
software
Client Workstation
user data
B
Software Installation Only
Setup Type
Chapter 7
take advantage of the increased level of I-DEAS data security that HT makes available on
Microsoft Windows
facilitate the implementation of a corporate strategy to migrate from one platform type to
another
Along with the benefits of HT, there are some costs. Your company will need to perform a cost
and benefits analysis to evaluate whether to implement HT.
Use the information in this chapter to help determine whether implementation of HT at your
company is appropriate and, once decided, to design the optimum heterogeneous team
configuration for your site.
67
Performance Degradation
The HT capability allows I-DEAS users on Microsoft Windows and UNIX hardware platforms to
work in a single team data installation and share I-DEAS library items.
A data format conversion occurs when non-native data items are retrieved from a library. This data
conversion is transparent to the user but does increase the time it takes to retrieve a library item to
the user's model file.
Site planning for HT should include an analysis of the hardware configuration and data sharing
strategies that could be used to reduce the amount of data conversion that occurs in your HT
environment overall.
See the HT articles in the I-DEAS Help Library and the Designing the Heterogeneous Team
Environment section of this chapter for a description of some of these strategies.
68
2.
Assign a team to evaluate the feasibility of implementing HT. The evaluation team should
include I-DEAS administrators, project managers, and end users.
3.
Learn about the HT capabilities and setup requirements. To do this, the evaluation team
members should review this chapter and the Heterogeneous Team Setup chapter in this guide.
Note: For additional information on HT, see the following articles in the I-DEAS online Help
Library:
4.
5.
If you decide to implement HT at your company, design the optimum HT environment for
your site.
See the Designing the Heterogeneous Team Environment section in this chapter for guidelines on
how to design the optimum HT environment for your site.
70
Windows Client
Windows Client
UNIX HT Server
Windows Client
Windows Client
Phase 1
Windows Client
Windows Client
Drafting Team
Windows
UNIX HT Server
Windows Client
UNIX Client
Design Team
UNIX
Windows Client
UNIX Client
Analyst
UNIX
UNIX Client
UNIX Client
Phase 2
Windows Client
Windows Client
Drafting Team
Windows
UNIX HT Server
Windows Client
Windows Client
Windows Client
Design Team
Windows
Analyst
UNIX
Windows Client
72
Windows Client
Windows Client
Before HT
Windows Client
Windows Client
Design Group
Windows
UNIX Client
Windows Client
Windows Client
Design Group
Windows
& UNIX
Windows Client
UNIX Client
Windows Client
UNIX Server
HT Installation
Windows Client
Drafting Group
Windows
Windows Client
Windows Client
Windows Client
Windows Client
Drafting Group
Windows
& UNIX
UNIX Client
UNIX Client
File Import/Export
(HDS)
UNIX Client
UNIX Client
Design Group
UNIX
UNIX Client
UNIX Client
UNIX Client
Drafting Group
UNIX
UNIX Client
UNIX Client
License and team server (The team server must be a UNIX machine. If the license server is a
separate machine, it may be either UNIX or Microsoft Windows.)
Standard HT Configuration
The following diagram illustrates the standard HT configuration.
In a very large distributed configuration (50 users or more running I-DEAS) it's best to dedicate a
single, stable machine as the license server. An additional server would be dedicated as the team
server. The team server must be a UNIX machine.
Standard HT Configuration
I-DEAS License &
RL Service
I-DEAS Software
Code
Team Directories
I-DEAS Online
Help
Shared Files
Global Parameter
File
(UNIX version)
UNIX/Windows
Connectivity Solution
local disk
local disk
Domain account
accessible by all
workstations
user data
User Files
Client Workstation A
Windows
74
Client Workstation B
UNIX
Two components within the team server setup are unique to HT, the mount point mapping file
(mpm#.dat) and the Microsoft Windows global parameter file, located on the UNIX team server.
The UNIX global parameter file for HT is located on the UNIX code server.
76
78
Develop a process map. The process map illustrates the product development cycle within
your organization or workgroup, and the workflow within that cycle.
2.
Expand the process map to illustrate the data sharing points within the product development
cycle and the frequency of the data sharing at each point of data interaction.
3.
Using the process map as an aid, the HT information provided in this guide, and the I-DEAS
Help Library, design the hardware configuration and data sharing strategies for your HT
environment.
4.
Once you've designed your HT environment, define the components to use during setup of
your HT environment.
The remaining sections of this chapter provide further explanation of this design process.
Engineering
Suppliers
Manufacturing
Engine
Body
Chassis
Generative
Machining
Part Design
Part Design
Part Design
Assembly
Drafting
Assembly
Drafting
Assembly
Drafting
Post Processing
Design
Design
Simulation
Analysis
80
Design
Engineering
Suppliers
Manufacturing
Engine
Part Design
>>>>>>>>
Part Design
Generative
Machining
Chassis
Body
>>>>>>>>
Assembly
Drafting
\\\\\\\\\
Assembly
Drafting
Post Processing
Design
Design
Design
Legend
High frequency data sharing
\\\\\\\\\
Simulation
Analysis
Engineering
Windows
and UNIX
Nightly cron job
on LLOF (not HT)
Suppliers
Team Master ID = 2
Windows
and UNIX
Top Level
A
bl
UNIX
Manufacturing
Windows
Engine
Windows
>>>>>>>>
Import/
Export
Part Design
(not HT)
Chassis
UNIX
Body
Windows
Part Design
Assembly Drafting
\\\\\\\\\
Assembly Drafting
Generative
Machining
>>>>>>>>
Batch
or HT
Post Processing
Design
Design
Legend
High frequency data sharing
\\\\\\\\\
Simulation
UNIX
82
Analysis
UNIX
Design
Hardware Configuration
When designing the hardware configuration, attempt to maintain a homogeneous platform
configuration for workgroups where parts are shared frequently between members of the group. In
our example, a homogeneous platform configuration is maintained within the subassembly groups
in engineering.
Where parts are shared less frequently, heterogeneous hardware platforms may be acceptable. This
would be the case between the engineering and simulation groups in our example.
Batch Sharing
Various strategies could be used for data sharing between the engineering and manufacturing
disciplines illustrated in our example HT environment. If manufacturing needs to retain
associativity with the library items retrieved from engineering, use of HT and the Reference Latest
or Copy with Notification checkout options would be appropriate.
If retaining associativity is not a concern, and data is shared periodically in batches, use of File,
Import/Export together with the HDS utility might be more efficient. This would be the case if a
large enough percentage of the engineering data to be accessed for use in manufacturing is in a
non-native data format. Use of this strategy could improve performance by eliminating the need
for HT conversion of non-native library data on the manufacturing workstations at library
checkout.
Note: This strategy requires that engineering and manufacturing work in separate HT data
installations.
Following is the basic procedure for batch sharing in our example:
1.
On an engineering workstation, export the library items you want to send to manufacturing.
2.
Copy the exported package (.pkg) files to a manufacturing workstation using binary ftp.
3.
On a manufacturing (Microsoft Windows) workstation, run the HDS utility on the package
files.
This will convert all the non-native parts in the package file to the data format native to the
platform where the HDS utility is being run.
4.
For information on using the HDS utility, see the Data Sharing Administration article under
I-DEAS General Administration in the I-DEAS Help Library.
For information on File, Import/Export, see the Sharing Library Items with Other Installations
article in the Project Management User's Guide under the Data Management User's Guide in the
I-DEAS Help Library.
For information on the setup of multiple HT data installations, see the Multiple Heterogeneous
Team Data Installation section in the Heterogeneous Team Setup chapter of this guide.
84
Note: The team server must be a UNIX machine or a server hardware connectivity solution
validated for use with I-DEAS HT. The team server cannot be a Microsoft Windows machine.
If the license server is a separate machine, it may be UNIX or Microsoft Windows.
See the appendixes in this guide or the I-DEAS web site for more information on server
hardware connectivity solutions validated for use with I-DEAS HT.
The common drive letter(s) available on Microsoft Windows clients to map to the HT data
installation.
Choose, and if necessary, acquire the UNIX to Microsoft Windows connectivity solution.
See the appendixes in this guide and the I-DEAS web site for information on connectivity
solutions validated for I-DEAS HT.
Determine whether you want to create a new team data installation or migrate an existing
installation to HT.
If you intend to migrate an existing team data installation, determine which existing team data
installation to migrate. It probably should be the data installation in which the greatest amount
of data to be used in the HT environment resides.
Determine if any shared data that exists in other team data installations should be merged with
the HT data installation using the I-DEAS File, Import/Export capability.
Note: Multiple HT data installations can be used in an HT environment.
86
Chapter 8
System Requirements
Process Overview
Setup Tasks
Troubleshooting
Due to its complexity, only experienced UNIX and Microsoft Windows system administrators can
be expected to set up and administer heterogeneous team successfully. Experience with network
administration is also necessary in the setup and administration of HT.
See the Heterogeneous Team Administration article in the I-DEAS online Help Library for
information on maintaining a heterogeneous team data installation.
See the I-DEAS Installation guides for information on maintaining the I-DEAS installation.
87
System Requirements
The following system requirements must be met for setup of a heterogeneous team environment:
UNIX Network File System (NFS) machine for the team data installation. In a heterogeneous
team environment, the team data installation must be located on a UNIX server.
UNIX to Microsoft Windows connectivity solution which has been validated to establish
communications between the UNIX team server and Microsoft Windows client machines
AND maintain I-DEAS data integrity in an HT environment.
See the appendixes in this guide for information on connectivity solutions validated for use
with I-DEAS HT. See the GTAC web site at http://support.ugs.com for an update on any
additional validated connectivity solutions for HT.
Disk space sufficient for storage of duplicate sets of data products (one set for UNIX and one
for Microsoft Windows). Data products include standard catalogs, material databases,
libraries, and parts and assemblies used in the online tutorials. The additional space is
required only if your company plans to use
I-DEAS data products.
Additional RAM (possibly) for both UNIX and Microsoft Windows workstations to enhance
the speed of converting heterogeneous data.
The parameter setting for the Inline Converter Cache defaults to an additional 8 MB memory
requirement for HT data conversions.
88
Process Overview
You may decide to set up the HT environment at your site during the initial installation of NX IDEAS 5, or later, after NX I-DEAS 5 has been in use for a while.
The process for setting up an HT environment is different during the initial installation of NX IDEAS 5 than it is after NX I-DEAS 5 has been in use for a while.
2.
Install NX I-DEAS 5 on the UNIX team server and configure it for HT.
3.
Install and configure a connectivity solution validated for use with I-DEAS HT.
4.
5.
6.
7.
In NX I-DEAS 5, SFAM Level 2 uses only component-based SFAM. In I-DEAS 11, SFAM Level
2 used either component-based SFAM or a dedicated Windows service. The service-based SFAM
is no longer available for NX I-DEAS 5.
2.
3.
Install and configure a connectivity solution validated for use with I-DEAS HT.
4.
5.
Configure I-DEAS.
6.
7.
8.
Setup Tasks
The procedures for completing the tasks in the setup processes defined above are described in this
section. Complete the tasks for the setup process youre using at your site.
the machine to use as the license and resource locking (RL) server
whether to merge library data from multiple team data installations to the HT data installation.
90
the common drive letter(s) on Microsoft Windows clients to map to the HT data installation.
The same drive letters on the Microsoft Windows clients must map to the same file
system/directories. You can conserve drive letters by mapping to higher levels in the directory
structure (for your site) within a team server or file system. For example, if the entire team
was on a single file system on one server, you could map to /team, instead of /team/shared1
and /team/shared2.
the I-DEAS administrator account name and password. In an HT environment, this must be
the same on UNIX and Microsoft Windows.
Note: Throughout this document, the I-DEAS administrator account is referred to as the
ideasadm account, although the account can have any name.
whether separate license files are being used for the existing UNIX and Microsoft Windows
team data installations
A team data installation must be controlled by only one I-DEAS license server. If client
workstations access multiple license servers and use the same data installation, the data in that
installation will eventually become corrupt.
See the Migrate to a Single License Server section later in this chapter for more information.
Use the following guidelines to establish a heterogeneous team environment that's efficient to
install, maintain, and troubleshoot:
Follow the conventions for naming directories, establishing user accounts, setting system
parameters, and so on, which are specified in this guide.
Use consistent drive letters and path names for team data directories, user home directories,
and I-DEAS software locations.
2.
When you perform the setup for the data installation portion, select the Create Custom Data
Installation option.
3.
Use the General Settings tab to define the Team Master ID, directory locations, and SFAM
level for the heterogeneous team installation.
You must include a directory above /team in the team directory location on UNIX. The
directory above /team will be mapped on the UNIX side of the MPM file.
Following is an example of the MPM file where the UNIX team directory location is defined
as /team_data/team and the Microsoft Windows drive letter is t:
/team_data t:\
Note: To implement SFAM level 3, use the dmadmin utility after I-DEAS is installed. See An
Overview of the dmadmin Utility article in I-DEAS online help for more information.
4.
In the NT Mount Point field, enter the Microsoft Windows drive letter to map to the HT
data installation.
This is used to set up the mount point mapping (MPM) file. You may edit the MPM file
to add more than one directory level, if desired. See step 5 in the Configure I-DEAS
section later in this chapter for information on customizing the MPM file.
92
Entries in the other fields on this tab are optional and explained in the Installation Guide.
5.
After the installation is complete, copy the UNIX parameter file to the /team/master directory
on the UNIX team server. For example:
cp $SDRC_INSTL/ideas/.ideas_param13 /team/master/
Create the user accounts according to the guidelines in the I-DEAS Installation Guide for
Microsoft Windows.
The user account names must be the same on UNIX and Microsoft Windows.
2.
Map the team drive letter youve designated for the HT data installation to the HT drive on
the UNIX team server.
2.
When you perform the setup for the team data installation portion, select the Use an existing
team data installation parameter file option.
3.
Click in the Parameter File field and select the ellipsis button.
The Select parameter file to import window displays.
4.
5.
In the Account and Password fields, enter the account and password used to install the IDEAS data installation on the UNIX team server for HT.
6.
Select the I-DEAS Parameter Files (UNIX) option from the Files of type: pull-down menu.
7.
Use the Look in: field to navigate to the UNIX parameter file, .ideas_paramX, which you
copied to the /team/master directory in step 5 of the procedure to Install NX I-DEAS 5 on the
UNIX Heterogeneous Team Server.
8.
9.
10. When the installation is complete, verify that the SFAM level settings and the resource
locking server type parameters are compatible in the UNIX and Microsoft Windows versions
of the I-DEAS parameter files for HT.
-
Verify that the Team.ServerType parameter is set to the same type in both versions of the
parameter file.
11. Finally, remove the copy of the UNIX version of the I-DEAS parameter file you copied to the
/team/master directory in step 5 of the procedure to Install NX I-DEAS 5 on the UNIX
Heterogeneous Team Server.
94
2.
When you perform the setup for the team data installation portion, select the Use an existing
team data installation parameter file option.
3.
Click in the Parameter File field and select the ellipsis button.
The Select parameter file to import window displays.
4.
5.
In the Account and Password fields, enter the account and password used to install the IDEAS data installation on the UNIX team server for HT.
6.
Select the I-DEAS Parameter Files option from the Files of type: pull-down menu.
7.
Use the Look in: field to navigate to the Microsoft Windows global parameter file for the HT
data installation.
Note: The Microsoft Windows global parameter file is located in the /team/master/Config/
directory on the HT team server.
8.
9.
2.
3.
Right-click SFAM component and choose Properties, then click the Identity tab.
Option 2
96
1.
2.
3.
Right-click SFAM component and choose Properties, then click the Identity tab.
Identify the installation number you want to transfer licensing from (Microsoft Windows
license server).
2.
Identify the installation number you want to transfer licensing to (UNIX license server).
3.
4.
5.
Return the signed agreement to the password center at least one business day before you
intend to reconfigure the I-DEAS license file.
6.
Once the transfer agreement has been processed, (in approximately one business day) you'll
receive a new password from GTAC.
7.
Use the NX I-DEAS 5 installation software to configure the I-DEAS license using this new
password.
The new password configures your license file as a combination of the products and number
of licenses defined in the two license files you've selected to merge.
8.
Modify the value of the UGII_LICENSE_FILE environment variable to point to the location
of the license file for the HT installation.
The UGII_LICENSE_FILE variable can be set in the custom_varbs.cmd file (for Microsoft
Windows) and the ideascust.sh file (for UNIX). The file is customer-created and needs to be
located in the I-DEAS bin directory.
Log in to the Microsoft Windows workstation using the system administrator account.
Note: Change the default password behavior for ideasadm as follows. This helps ensure that
the I-DEAS team SFAM service starts properly.
2.
Log in to the Microsoft Windows workstation using the system administrator account.
b.
2.
3.
98
4.
Add the HT users groups or users to the IDEAS SFAM USERS group.
Go to the Groups lower pane and double-click the IDEAS SFAM USERS group
Add the user groups at your site that will use HT to the I-DEAS SFAM USERS
group.
In the control panel, select Administrative Tools, then the Component Services applet.
2.
3.
Right-click on SFAM and select properties. When the property pages display, select the
Identity tab.
You can also install I-DEAS component-based SFAM at the command prompt. To do this, you
run the following command:
Msiexec /I %SDRC_INSTL%\Install\SFAM\I-DEAS SFAM
Component.msi USERNAME=<domain\username>PASSWORD=<Password>
The Windows Installer will install the I-DEAS SFAM component.
Configure I-DEAS
This task should only be performed if youre setting up HT after NX I-DEAS 5 has been used in a
homogeneous environment and youre migrating to an HT environment.
Complete the following tasks to configure I-DEAS for heterogeneous team.
Note: The first four tasks in this process can be performed while users are running I-DEAS. For
the remaining tasks, I-DEAS must be shut down.
100
1.
Create the team data installation setup structure on the UNIX team server.
2.
If you're migrating existing Microsoft Windows team data, refer to Chapter 2, Planning for
Migration, for guidelines.
3.
Use ftp or copy the Microsoft Windows global parameter file from the current Microsoft
Windows team server (<drive>:\team\master\config\ideas_param13.dat) to the UNIX team
server, under the Team.MasterDirectory location.
Note: The UNIX global parameter file (/ugs/ideas13/ideas/.ideas_param13) is located on
the UNIX code server. If multiple UNIX platform types are used in the HT installation, a
separate version of the UNIX parameter file must exist on the I-DEAS code server for each
UNIX platform type.
4.
Modify the following parameters in the UNIX and Microsoft Windows parameter files.
Note: This can be done either manually or using the I-DEAS installation program.
SFAM Level for UNIX, run dmadmin to change. For Microsoft Windows, modify the
setting in the parameter file.
Recommended matching settings:
UNIX: LEV2 or LEV3; Microsoft Windows: LEV2
UNIX: LEV1; Microsoft Windows: LEV1
Team.SecFileAccessLevel: LEV? (as applicable to your site)
File Compression: The gzip file compression utility is used beginning with MS7m1. Refer to
the I-DEAS parameter file for the description of the gzip utility and corresponding parameter
entries.
Note: The options entered for each parameter are specifically set to work with
should not be changed.
I-DEAS and
Team compress (using the gzip utility) to enable manual compress functionality in
dmadmin
Team.CompressCommand: $SDRC_INSTL/prl/gzip-124.exe f S .Z
Team decompress (using the gzip utility) for decompression of compressed files
Team.DecompressCommand: $SDRC_INSTL/prl/gzip-124.exe df
Team compress file extension to use a different file extension for gzip files. The
standard gzip extension is .gz, I-DEAS must use .Z.
Team.CompressFileExtension: .Z
Memory: A new memory parameter is used beginning with MS7m1. This parameter speeds
up conversion of non-native library items in an HT environment. Refer to the I-DEAS
parameter file for a description of the parameter and corresponding entries. You can update
the I-DEAS parameter file with the following parameter entry:
Note: The default value is 8 MB. If you work with very large models at your site, you may
want to set this value higher.
5.
Create the mount point mapping (MPM) file on the UNIX team server:
a)
Create a .dat file in the Team.MasterDirectory. Name the file mpm# (where # is the value
for the Team.MasterID; e.g., if the Team.MasterID is 3, name the file mpm3.dat). Give
the file ideasadm ownership.
b) Map the UNIX directory path to the Microsoft Windows drive letter for each mapped
drive. The format is UNIX path, white space, Microsoft Windows drive letter. Enter one
mapped drive per line. Comment lines can be used starting with a ! or # character. For
example:
!data installation number 1 map
/team/data_installation1/
m:\
The left side of the mapping, /team/data_installation1/, is the directory level above /team,
for the team directory location defined on the UNIX team server during installation. The
actual team directory this map file points to is /team/data_installation1/team.
The right side of the mapping, m:\, is the Microsoft Windows drive letter being used to
map to the team directory location on the UNIX team server.
102
All of the I-DEAS team files (.imd, .pmd, .prt, etc.) must be visible to both UNIX and
Microsoft Windows. (Installation of the connectivity solution, as discussed in the Install
and Configure a Validated Connectivity Solution section of this chapter, allows for this.)
You can edit the MPM file from either a UNIX or Microsoft Windows platform.
Comments can be placed at the end of the line after the Microsoft Windows path.
When adding a platform to an existing installation, all new mounts should be less than or
equal in length to the corresponding old mount to ensure file name path length does not
change. An I-DEAS filename path is 80 characters or less.
Note: If youre running close to the 80 character file limit on your file name paths, you
need to be aware of mount lengths in your MPM file.
For example, if youre adding Microsoft Windows workstations to an existing UNIX
installation, there will probably not be any constraints. Microsoft Windows mounts are
drive letters (three characters, e.g., d:\) and the UNIX directory path is probably a
minimum of three characters.
If youre adding UNIX workstations to an existing Microsoft Windows installation, there
could be potential problems with the 80 character file name path limit. UNIX mounts will
probably have to be three characters to match the Microsoft Windows mounts. You may
have to use a naming convention, such as /1a, /1b, /1c.
6.
Modify the value of the IDEAS_PARAM13 environment variable to point to the parameter
files location for the HT installation.
Note: The IDEAS_PARAM13 variable is set in the custom_varbs.cmd file (for Microsoft
Windows) and the ideascust.sh file (for UNIX). The file is customer-created and must be
located in the I-DEAS bin directory.
104
Each user on a Microsoft Windows workstation must map the team drive to the HT
installation team directory at login. A script can be created to accomplish this automatically at
login, or the user can check the Reconnect at Logon option when mapping the drive. Users
should use their own login account to map the team drives. (A user must be assigned the same
login name on both UNIX and Microsoft Windows.) Users should not use the ideasadm
account when mapping the team drive.
2.
3.
4.
5.
Enter the corresponding number for the data products you want loaded.
6.
7.
I-DEAS
Before running I-DEAS, check the UNIX and Microsoft Windows versions of the I-DEAS
global parameter files to verify that the resource locking type is consistent and the SFAM
settings are compatible.
-
Verify that the Team.ServerType parameter is set to the same type in both versions of the
parameter file.
2.
Change to the team directory and team drive location specified in the MPM file for UNIX
and Microsoft Windows, respectively.
You should see the same items in each listing. If the HT data installation directories are listed,
the syntax is correct. If not, adjust the MPM file contents.
4.
Start I-DEAS on a Microsoft Windows client, create some simple geometry, and check it into
a library.
5.
Start I-DEAS on a UNIX client (if applicable), check out the part created on the Microsoft
Windows workstation and put it on your workbench.
6.
On each workstation platform type, access a part from a migrated team data installation (if
applicable) and put it on your workbench.
7.
If data products are installed, access a cataloged data product of the correct platform type and
put it on your workbench.
See the Troubleshooting section later in this chapter for guidelines on resolving any problems you
may encounter when verifying the HT installation.
106
For each user, define the IDEAS_PARAM13 variable to point to the installation the user will
work in.
For each user, map the common drives to the installation the user will work in.
Use a single ideasadm account name and password across all of the team data installations.
Both the component-based SFAM and the connectivity solution require the ideasadm
password to gain access to files that are under SFAM protection. Using the same password
permits users to access data in a part or assembly from multiple team data installations.
The UNIX UID must be the same for the authentication server and the UNIX team servers.
Troubleshooting
This section describes some installation problems and their recommended solutions.
Symptom:
Team projects are not listed on the I-DEAS startup window on Microsoft Windows.
Possible solutions:
The team drive is not mapped. Map the UNIX HT installation directory location to the Microsoft
Windows team drive.
The IDEAS_PARAM13 environment variable has not been set. Update the variable in the
custom_varbs.cmd file in the I-DEAS bin directory. The variable should point to the parameter file
location for the HT installation.
Note: The custom_varbs.cmd file is a customer-created file.
Symptom:
At I-DEAS startup, you get a message that the Team.MasterDirectory could not be found, but it
can be found for other users.
Solution:
The configuration for I-DEAS administrator access is not set correctly in the connectivity solution
or the SFAM mechanism is not set correctly on the Microsoft Windows client.
The SFAM mechanism requires the same account and password to gain access to the shared IDEAS files (under SFAM protection).
The I-DEAS administrator account and password must be the same on UNIX and Microsoft
Windows.
Note: If you change the I-DEAS administrator account password, you'll need to update the SFAM
installation on every Microsoft Windows client in the HT environment. If the connectivity
solution you use is client-based, you'll also need to update that setup for every Microsoft Windows
client in the HT environment.
Symptom:
Check in a file with uppercase in the name on Microsoft Windows, then you need to reconnect on
UNIX because it couldnt find it.
Solution:
The connectivity solution configuration is not set correctly for case. Configure the connectivity
solution to preserve case.
108
Symptom:
Receive message that you have an invalid file specification or that the directory does not exist
(read problem). Get a crash when you try to convert a file from one platform format to another
(write problem).
Solution:
DataMgmt.ScratchDirectory (for UNIX and Microsoft Windows) must have read/write
permissions set for the user and ideasadm accounts.
Symptom:
Receive error message: I-DEAS cannot access the data. The file format is not compatible with the
current hardware platform.
Solution:
The Team.MultiPlatform parameter in the parameter files must be set to 1.
110
Appendix A
A-1
System Requirements
System requirements for Network Appliance equipment used with I-DEAS HT are:
Network Appliance Model 3020, 940 and 840 were used to perform the validation tests.
Although Network Appliance models 3020, 940 and 840 were used in validation testing, the
following models are also supported for use with I-DEAS HT:
,F840, FAS250, FAS270, FAS940, FAS960, FAS980, FAS3020
Also, firmware and operating system versions released later than those listed above are expected,
based on Network Appliance claims, to support I-DEAS HT.
Troubleshooting
This section describes some symptoms and the recommended solutions for problems that may be
related to the Network Appliance configuration for HT.
Symptom:
Team directory access is denied.
Solution:
Microsoft Windows clients must be in the same domain as the Network Appliance server. This is
required to support SFAM level 2.
See the Troubleshooting section of Chapter 9, Heterogeneous Team Setup, for additional
troubleshooting guidelines.
Customer Support
Please contact Network Appliance, Inc., if you need help with their product.
A-2
Appendix B
B-1
System Requirements
System requirements for EMC equipment used with I-DEAS HT are:
The EMC Celerra File Server, Celerra SE, and NS600 were used to perform the validation tests
for I-DEAS HT. Although CLARiiON IP4700 was not used to perform the validation tests, it is
also supported for use with I-DEAS HT.
SFAM Support
To support running SFAM level 2 on Microsoft Windows, the Microsoft Windows clients must be
in the same domain as the EMC server.
Kernel Level
The minimum kernel level on Celerra is 2.2.16-0.EMC.2 on an i686.
Mount Options
The following mount option settings were used on the I-DEAS team directory:
fs2 on /team uxfs, perm, rw, rwlock, accesspolicy=SECURE
When using the accesspolicy=SECURE setting you must have both the Microsoft Windows and
UNIX access permissions set so you can read and/or write data. If permissions on either platform
type are either no read or no write, read and write access permissions are denied on both
platform types.
The rwlock setting enforces all CIFS locking modes with NFS users.
B-2
export /team
CIFS Settings
CIFS should be configured with the following settings:
Security mode = NT
Troubleshooting
This section describes some symptoms and the recommended solutions for problems that may be
related to the EMC configuration for HT.
Symptom:
Team directory or data access is denied.
Solution:
Verify the following configuration requirements are met:
Microsoft Windows clients must be in the same domain as the EMC server. This is required to
support SFAM level 2.
Data access permissions on both the Microsoft Windows and UNIX systems in the HT
environment must be set to read and/or write data. If data access permissions on either
platform type are set to no read or no write data access on both platform types is denied.
The accesspolicy=SECURE mount option setting enables this behavior.
See the Troubleshooting section of Chapter 9, Heterogeneous Team Setup, for additional
troubleshooting guidelines.
Customer Support
Please contact EMC Customer Service if you need help with their product. You can access EMC
Customer Service contact information by selecting Customer Service from the Services menu at
their web site, http://www.emc.com/.
B-4