ed a user guide

Teamcenter® 2005 SR1engineering process management

Teamcenter EDAUser’s Guide

Publication NumberENG00041 A

Teamcenter® 2005 SR1engineering process management

Teamcenter EDAUser’s Guide

This product is intended for use only described in this document. UGScannot be responsible for the proper functioning of undescribed featuresand parameters.

Publication NumberENG00041 A

Manual History

ManualRevision

Teamcenter EDAVersion

TeamcenterEngineeringVersion

PublicationDate

A 2005 2005 SR1 June 2006

©2006 UGS Corp.All Rights Reserved.Produced in the United States of America.

2 Teamcenter EDA User’s Guide ENG00041 A

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Teamcenter Engineering Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . 9Submitting Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Software Copyright and Trademark Notices . . . . . . . . . . . . . . . . . . . . . . . 9

Installing Teamcenter EDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Installing Prerequisite Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Installing and Configuring Teamcenter EDA . . . . . . . . . . . . . . . . . . . . . . 1-7Enabling Creation of Viewable Files (Optional) . . . . . . . . . . . . . . . . . . . . 1-19

Getting Started With Teamcenter EDA . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Teamcenter EDA Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Teamcenter EDA Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Overview of the Teamcenter Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Performing a Typical Teamcenter EDA Workflow . . . . . . . . . . . . . . . . . . . 2-5Using the Staging Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Using Teamcenter EDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Using the Teamcenter Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Opening Viewable Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13Starting Cadence Design Entry HDL With a Batch File . . . . . . . . . . . . . . 3-13

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Empty Open Dialog Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Refresh Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Component Error When Saving Designs . . . . . . . . . . . . . . . . . . . . . . . . . 4-3System Hangs When Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Packaging Error on Cadence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4BOM Template Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Customizing Teamcenter EDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Populating the Database With Components . . . . . . . . . . . . . . . . . . . . . . . 5-1Customizing Cadence BOM Templates . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Editing the TCEDAClient.properties File . . . . . . . . . . . . . . . . . . . . . . . . 5-3Changing System Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

ENG00041 A Teamcenter EDA User’s Guide 3

Contents

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

Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Teamcenter EDA Data Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Teamcenter EDA Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3About the Staging Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5Mentor Graphics Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7

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

Figures

2-1. Teamcenter EDA Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22-2. Teamcenter EDA Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3B-1. Overview of Teamcenter EDA Data Structures . . . . . . . . . . . . . . . . . . B-1

Tables

B-1. Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3B-2. Dataset Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4


Preface

This manual describes the installation and use of Teamcenter® EDA (electronicdesign automation) for Teamcenter Engineering. Teamcenter EDA belongs to theUGS® portfolio of digital product lifecycle management software and services.

Teamcenter EDA integrates ECAD design tools with Teamcenter Engineering.Designers use Teamcenter EDA to move ECAD data into and out of TeamcenterEngineering. Teamcenter Engineering is an enterprise application for the storageand management of product data.

AudienceThis manual is intended for installers and users of Teamcenter EDA. It assumesyou are familiar with ECAD design applications and the InterComm viewer. It alsoassumes you are familiar with installation, administration, and usage of TeamcenterEngineering, including the rich client interface.

OrganizationThis manual contains the following chapters:

Chapter 1 Installing Teamcenter EDA describes the procedures forinstalling the Teamcenter EDA application.

Chapter 2 Getting Started With Teamcenter EDA gives you an overview ofTeamcenter EDA.

Chapter 3 Using Teamcenter EDA describes how to use Teamcenter EDAto move data between your ECAD design tool and TeamcenterEngineering.

Chapter 4 Troubleshooting describes how to troubleshoot problems usingTeamcenter EDA.

Chapter 5 Customizing Teamcenter EDA describes how to alter TeamcenterEDA for use at your company.

Appendix A Glossary defines terms related to Teamcenter EDA.

Appendix B Reference provides background information about TeamcenterEDA.


Preface

ConventionsThis manual uses the conventions described in the following sections.

Revision Marks

Technical changes are marked by a bar adjacent to the changed text.

Note, Caution, and Warning Icons

The following icons represent note, caution, and warning messages:

A note icon identifies general instructions or comments that need to beemphasized.

A caution icon identifies practices that can either produce results contraryto what you expect or result in damage to software or data.

A warning icon identifies practices that could result in permanent loss ofdata or software.

Names and Values

This manual represents system names, file names, and values in fonts that help youinterpret the name or value. For example:

The file name is pom_schema_server-name_sid.

The conventions are:

Bold Bold font represents unvarying text or numbers within a name orvalue. Capitalization is as it appears.

In the preceding example, pom_schema_ identifies an unvaryingportion of the name.

Italic Italic font represents text or numbers that vary. The characters initalic text describe the entry. Letters are shown in lowercase, butthe varying text may include uppercase letters.

In the preceding example, server-name and sid represent varyingportions of the name.

text-text A hyphen separates two words that describe a single entry.

In the preceding example, server-name is a single value.

For example, the name of the pom_schema_server-name_sid file may be:

pom_schema_Blue5_f731


Preface

Command Line Entries, File Contents, and Code

This manual represents command line input and output, the contents of system files,and computer code in fonts that help you understand how to enter text or to interpretdisplayed text. For example, the following line represents a command entry:

create_change_types -u=user-name -p=password -g=group -f=file-name


Monospace Monospace font represents text or numbers you enter on acommand line, the computer’s response, the contents of systemfiles, and computer code.

Capitalization and spacing are shown exactly as you must enterthe characters or as the computer displays the characters.

In the preceding example, create_change_types identifies anunvarying portion of the command.

Italic Italic font represents text or numbers that vary. The words initalic text describe the entry.

The words are shown in lowercase letters, but the varying textmay include uppercase letters. When entering text, use the caserequired by the system.

In the preceding example, user-name, password, group, andfile-name identify varying portions of the command.

text-text A hyphen separates two words that describe a single entry.

In the preceding example, user-name is a single entry in thecommand.

The following example is a correct entry for the preceding create_change_typescommand:

create_change_types -u=infodba -p=KLH3b -g=dba -f=change_types.dat


Preface

Syntax Definitions

This manual uses a set of conventions to define the syntax of Teamcenter commands,functions, and properties. Following is a sample syntax format:

harvester_jt.pl [bookmark-file-name bookmark-file-name ...][directory-name directory-name ...]


Bold Bold text represents words and symbols you must enter exactlyas shown.

In the preceding example, you enter harvester_jt.pl exactly asshown.

Italic Italic text represents values that you supply.

In the preceding example, you supply values for bookmark-file-nameand directory-name.

text-text A hyphen separates two words that describe a single value.

In the preceding example, bookmark-file-name is a single value.

[ ] Brackets represent optional elements.

... An ellipsis indicates that you can repeat the preceding element.

Following are examples of correct syntax for the harvester_jt.pl: command:

harvester_jt.plharvester_jt.pl assembly123.bkmharvester_jt.pl assembly123.bkm assembly124.bkm assembly125.bkmharvester_jt.pl AssemblyBookmarks


Preface

Teamcenter Engineering DocumentationTeamcenter Engineering documentation is provided as online help and as printablemanuals:

• You can access online help by choosing Help from the menu bar of a TeamcenterEngineering rich client application or by clicking one of the links under the Helpicon in the Teamcenter Engineering thin client user interface.

• You can access the printable manuals from the Teamcenter EngineeringDocumentation CD-ROM. To view the PDF-formatted manuals, use AdobeAcrobat Reader, downloadable free-of-charge from Adobe Systems Incorporatedat the following URL:

http://www.adobe.com

Acrobat Reader allows you to view these manuals online and print selectedpages, sections, or the entire manual. UGS grants permission for TeamcenterEngineering users to print, duplicate, and distribute this documentation.

Submitting CommentsPortions of Teamcenter software are provided by third-party vendors. Specialagreements with these vendors require UGS to handle all problem reportsconcerning the software they provide. Please submit all comments directly to UGS.

Please feel free to give us your opinion of the usability of this manual, to suggestspecific improvements, and to report errors. Mail your comments to:

UGS Technical Communications4233 Lexington Avenue N., Suite 3290Arden Hills, MN 55126-6198U.S.A.

To submit an incident report, you can use the UGS GTAC online support tools atthe following URL:

http://support.ugs.com

Software Copyright and Trademark Notices© 2006 UGS Corp. All Rights Reserved. This software and related documentationare proprietary to UGS Corp.

UGS and Teamcenter are registered trademarks or trademarks of UGS Corp. or itssubsidiaries in the United States and in other countries.

Java and all Java-based marks are trademarks or registered trademarks of SunMicrosystems, Inc. in the United States and other countries.

All other trademarks or registered trademarks belong to their respective holders.


http://www.adobe.com

http://support.ugs.com

Chapter

1 Installing Teamcenter EDA

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Installing Prerequisite Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Installing CAD Design Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Installing Teamcenter Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Installing the Translation Solution Toolkit (Optional) . . . . . . . . . . . . . . . . 1-5Installing InterComm (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Installing Perl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Installing and Configuring Teamcenter EDA . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Installing Teamcenter EDA Server Support . . . . . . . . . . . . . . . . . . . . . . . 1-7Installing the Teamcenter EDA Client . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Installing the Client From TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Enabling the Teamcenter Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Enabling the Teamcenter Menu in Mentor Graphics . . . . . . . . . . . 1-14Enabling the Teamcenter Menu in Cadence . . . . . . . . . . . . . . . . . 1-16

Creating the Cache and Staging Directories . . . . . . . . . . . . . . . . . . . . 1-18

Enabling Creation of Viewable Files (Optional) . . . . . . . . . . . . . . . . . . . . . . . 1-19

ENG00041 A Teamcenter EDA User’s Guide

Chapter

1 Installing Teamcenter EDA

This chapter describes the procedures for installing the Teamcenter EDA application.

Installation OverviewPerform the following general steps to install Teamcenter EDA:

1. Ensure your system meets minimum software and hardware requirements.

2. Install prerequisite applications and licenses. Verify proper operation beforecontinuing.

3. Install the Teamcenter EDA data model to the server, and install the TeamcenterEDA client.

4. Configure creation of viewable files (optional).

Follow the directions in the subsequent sections of this chapter to perform thesesteps.

ENG00041 A Teamcenter EDA User’s Guide 1-1

Chapter 1 Installing Teamcenter EDA

System RequirementsTeamcenter EDA runs on top of Teamcenter Engineering and has the same hardwareand software requirements as Teamcenter Engineering 2005 SR1. For informationabout versions of operating systems, third-party software, and Teamcenter softwareconfigurations that are certified for your platform, see the UGS CertificationDatabase:

http://support.ugs.com/online_library/certification/

Hardware Requirements

Teamcenter EDA platform recommendations conform to EDA industry standards asdetailed by the EDA Consortium at the following URL:

http://www.edac.org/resources_roadmap.jsp

In addition to the general Teamcenter Engineering requirements, Teamcenter EDAhas the following specific hardware requirements for systems running ECAD designtools (Mentor Graphics and Cadence):

• Windows 2000 or XP

• Solaris 8, 9, or 10

• HP-UX 11.0

1-2 Teamcenter EDA User’s Guide ENG00041 A

http://support.ugs.com/online_library/certification/

http://www.edac.org/resources_roadmap.jsp

Installing Teamcenter EDA

Software Requirements

In addition to the general Teamcenter Engineering requirements, Teamcenter EDAhas the following specific software requirements:

• Mentor Graphics EN2004

If you use Mentor Graphics as your ECAD design tool, you must install BoardStation on client workstations. If you are going to perform viewable generation,you also must install Electronic Data Interchange Format (EDIF) SchematicWriter 200.

• Cadence Allegro SPB 15.5

If you use Cadence as your ECAD design tool, install Allegro Design Entry HDL210 15.5 and/or Allegro PCB Editor 15.5 on client workstations.

• Teamcenter Engineering 2005 SR1

Install a Teamcenter Engineering server and enable rich client and thin clientaccess. Teamcenter EDA is designed to work with both the rich client and thinclient user interfaces.

• Translation Solution Toolkit 3.0 (optional)

If you want to translate CAD design files into viewable files (.eda format), youmust install the Translation Solution Toolkit (TSTK) on a separate dedicatedmachine used only for translation. TSTK works with Engineering TranslationServices (ETS) on the Teamcenter Engineering to generate viewable files.

• InterComm 5.1 (optional)

InterComm is a tool you can use to view and mark up viewable files (.eda).Install InterComm on the workstations where your ECAD design tools areinstalled. You must also install InterComm on the TSTK server, becauseInterComm is used to translate CAD design files into .eda viewable files.InterComm is a licensed product, and a license server for InterComm is required.

• Perl 5.0 or later

You need a current Perl installation to be able to launch applications from therich client.

• Java™ 1.4.2 or later

You need Java Runtime Environment (JRE) installed on the TeamcenterEngineering server as well on Teamcenter EDA client workstations.

On HP-UX platforms use the Teamcenter Engineering installationsource (for example, CD-ROM) to install the JRE to the TeamcenterEngineering server.

To install these applications, see Installing Prerequisite Applications, next.



Installing Prerequisite ApplicationsFollow the directions in the subsequent sections to install prerequisite applications.

Installing CAD Design Tools

Install the CAD design tool of your choice:

• Mentor Graphics

Install Board Station and Design Manager.

• Cadence

Install Allegro Design Entry HDL and/or Allegro PCB Editor.

Refer to your design tool documentation for installation instructions. Installlicensing and verify proper operation of the tools prior to continuing with installation.

Installing Teamcenter Engineering

Because Teamcenter EDA runs on top of Teamcenter Engineering, you must ensurethat you have a Teamcenter Engineering server installed with the Server Managerfeature. Later you install the Teamcenter EDA server support (data model) on thisTeamcenter Engineering server (as described in Installing Teamcenter EDA ServerSupport, later in this chapter). You can also install the Teamcenter EDA serversupport at the same time that you install the Teamcenter Engineering server.

Also make sure you have the four-tier thin client (Web tier) installed for theTeamcenter Engineering server, and that you are running a tc.ear file deployed in aWeb application. Finally, ensure that the pool manager is running to manage thinclient connections to the server.

The Teamcenter EDA client uses the AIWS communications layer to connect toTeamcenter EDA. To test that the AIWS communications layer is working correctly,access the following URL in your thin client environment:

http://host:port/tc/aiws/aiwebservice

The message AIW Service is Alive displays if the AIWS communications layer isworking. In the example, replace host with the name of the Web application serverrunning in your thin client environment, and replace port with the port of that server.

You cannot install the Teamcenter Engineering server and the TeamcenterEDA client on the same machine.

For instructions about installing Teamcenter Engineering, see the Installation onUNIX and Linux Servers manual or the Installation on Windows Servers manual.



Installing the Translation Solution Toolkit (Optional)

If you want to translate CAD designs into viewable files (.eda format), installthe Translation Solution Toolkit (TSTK) on a dedicated machine only used fortranslation. Then, when you install the Teamcenter Engineering server, install theEngineering Translation Services (ETS) feature. TSTK works with ETS to generatethe viewable files from CAD designs.

For more information about installing the Translation Solution Toolkit, see theTranslation Solution Toolkit Installation Guide. For more information aboutinstalling and configuring ETS, see the Installation on Windows Servers manual orthe Installation on UNIX and Linux Servers manual.

Installing InterComm (Optional)

For design view and markup, Teamcenter EDA utilizes InterComm made by PTC.Installing InterComm is optional; if you do not want to use InterComm for designview and markup, you can still use Teamcenter EDA to check in and check outdesigns between your ECAD design tool and Teamcenter Engineering.

Teamcenter EDA is configured to use the InterComm application forvisualization activities. If you want to use another product, contactyour Teamcenter sales representative. InterComm is not provided by orsupported by UGS; contact PTC with issues related to InterComm.

If you install InterComm to Teamcenter EDA client machines, InterComm islaunched from the rich client when you select a viewable file. The rich client readsthe installed location of InterComm from the icmhome environment variable.

If you choose to generate viewable files from CAD designs, you must alsoinstall InterComm to the Translation Solution Toolkit server. InterCommis used in the translation process.

Perform the following steps to install InterComm:

1. Browse to the following PTC URL:

http://www.ptc.com/appserver/mkt/products/home.jsp?k=3110

2. Download the proper InterComm install file for your platform. You must createan account with PTC to download products.

For additional installation instructions, download the Acquiring and ConfiguringInterComm Products manual at the following URL:

http://www.ptc.com/appserver/wcms/standards/linkothumbredirect.jsp?&im_dbkey=35568&icg_dbkey=841

3. Run the installation file and follow the directions.

The installation process automatically sets the icmhome environment variablewith the installed location of InterComm.

If InterComm is running in client/server mode in a Windows environment, addthe ICMHOME environment variable to the client machine manually so thatit recognizes the installed location of InterComm.


http://www.ptc.com/appserver/mkt/products/home.jsp?k=3110





4. When you first run InterComm, you are prompted to request a license.

To obtain a license, follow the instructions in the InterComm Release and InstallNotes manual.

Installing Perl

You need Perl to be able to launch applications from the rich client. You must havePerl installed on each client host.

You can download Perl for client machines at the following URL:

www.activestate.com/Products/ActivePerl/

Perl can also be downloaded from other locations.

On Windows systems, the Nutcracker application used with MentorGraphics provides a version of Perl that is not compatible with TeamcenterEDA. Ensure that you download and install Perl 5.0 or later.

You must also have a registered MIME type for Perl (.pl) files defined in your Webbrowser to support application launching. Many browsers set the MIME typeautomatically. If you are using Netscape on UNIX, you must manually set theMIME type as follows:

Field ValueDescription Perl scriptMIME type application/x-perlSuffixes plApplication usr/bin/perl %S


http://www.activestate.com/Products/ActivePerl/


Installing and Configuring Teamcenter EDAWhen you install Teamcenter EDA, first install the Teamcenter EDA server support(data model) to the previously installed Teamcenter Engineering server machine.Then install the Teamcenter EDA client files to the client machines. Finally, enablethe Teamcenter menu in the CAD design tools (Mentor or Cadence) on the clientmachines.

Do not install the server and client on the same machine.

Installing Teamcenter EDA Server Support

Teamcenter EDA server support adds the Teamcenter EDA data model to theexisting Teamcenter Engineering data model. Before installing Teamcenter EDAserver support, you must have already installed the Teamcenter Engineering server.For more information, see Installing Teamcenter Engineering, earlier in this chapter.

You can also install Teamcenter EDA server support at the same time thatyou install the Teamcenter Engineering server. However, the directions thatfollow only describe installation of Teamcenter EDA server support andassume you have already installed the Teamcenter Engineering server.

Perform the following steps to install the Teamcenter EDA data model to theTeamcenter Engineering server:

1. Start the Teamcenter Environment Manager (TEM).

If you are adding Teamcenter EDA server support to an already-existingTeamcenter Engineering server, launch the Teamcenter Environment Managerfrom your Teamcenter Engineering environment.

If this is a first-time installation of a Teamcenter Engineering server and youwant to include Teamcenter EDA server support, run the TEM.js (Windows) orTEM.sh (UNIX) file from your install source, such as a CD-ROM.

For more information about launching the Teamcenter Environment Manager,see the Installation on UNIX and Linux Servers or the Installation on WindowsServers manual.

2. Proceed to the Select Features dialog window.

If you are adding Teamcenter EDA server support to an already-existingTeamcenter Engineering server, choose the Configuration Manager option toperform maintenance on an existing installation and click Next until you getto the Select Features dialog window.

If this is a first-time installation, in the Solutions dialog window of the of theTeamcenter Environment Manager, choose Corporate Server and choose Next.



3. In the Select Features dialog window, perform these steps:

a. Select the following options under the Teamcenter Corporate Server list:

• EDA Server Support

Installs the Teamcenter EDA server components. This option installsTeamcenter EDA dataset types and transfer modes.

• Cadence Translation Support (optional)

Configures Engineering Translation Services (ETS) so that viewable filesof Cadence CAD designs can be generated. Choose this option only if youuse Cadence as your design tool.

• Mentor Translation Support (optional)

Configures Engineering Translation Services (ETS) so that viewable filesof Mentor CAD designs can be generated. Choose this option only ifyou use Mentor as your design tool.

If this is a first-time installation of the Teamcenter Engineering server, youshould also choose the following options:

• Server Manager

Installs the pool manager. You must run the pool manager when usersconnect to the server using the thin client (Web tier).

• Engineering Translation Services (optional)

Also known as ETS, this option enables the translation of CAD designsto .eda file format for viewing. Users can view and mark up the designsusing a viewer such as InterComm.

b. In the Installation Directory field, enter the location where you want toinstall Teamcenter Engineering (the IMAN_ROOT). The Teamcenter EDAserver files are installed to an eda subdirectory.

c. Click Next.

4. Enter information as needed in subsequent dialog windows. For informationon standard Teamcenter Engineering installation dialog windows, see theInstallation on UNIX and Linux Servers or the Installation on Windows Serversmanual.

If you install Engineering Translation Services (ETS), on theinstallation dialog window, indicate that you want to use RMI as thetransfer protocol instead of HTTP.

5. In the Confirm Selections window, click Next. Teamcenter EDA servercomponents are installed.

The Add/Remove Components dialog window declares whether the installationwas successful. If the installation was unsuccessful, click Show Details andtake corrective action.



6. Obtain the license file that includes Teamcenter EDA licensing and install it onthe corporate server or license server.

7. Verify the addition of the Teamcenter EDA data types to the server:

a. Run the Teamcenter Engineering rich client.

b. In the Navigator application pull down the File menu and choose theNew→Item options. The New Item dialog window is displayed.

c. Verify that the EDA, EDAComp, and EDASchem item types are added tothe list of types you can create. Choose one of the Teamcenter EDA itemtypes and create an instance.

d. Verify that the item instance is created.

8. Before users can save BOM data to Teamcenter EDA, an administratormust first populate the database with components or change theEDA_CheckComponentExistence preference from 1 (true) to 0 (false). Formore information, see Populating the Database With Components in chapter 5,Customizing Teamcenter EDA.



Installing the Teamcenter EDA Client

To install the client, install the client files using the Teamcenter EnvironmentManager (TEM), enable the Teamcenter menu in the ECAD tool UI, and create thestaging and cache directories.

Installing the Client From TEM

Perform the following steps to install the Teamcenter EDA client files on clientcomputers running an ECAD design tool (Mentor Graphics or Cadence):

1. Start the Teamcenter Environment Manager for a client install by running theTEM.js (Windows) or TEM.sh (UNIX) file from your install source, such asa CD-ROM.

For more information about Teamcenter Engineering installation, see theInstallation on UNIX and Linux Servers or the Installation on Windows Serversmanual.

2. In the Solutions window of the Teamcenter Environment Manager, select EDAStandalone Client. Click Next.

3. Perform the following steps in the Select Features window of the TeamcenterEnvironment Manager:

a. The following options are selected in the Standalone Applications list.Deselect the features that do not apply for your situation:

• EDA Standalone Client

Installs the client for Teamcenter EDA.

• Markup Support

Installs support for using the view and markup tool with the TeamcenterEDA client.

• Cadence Support

Installs support for using Cadence Allegro with the Teamcenter EDAclient. Choose this option only if you use Cadence as your design tool.

• Mentor Support

Installs support for using the Mentor Graphics Board Station with theTeamcenter EDA client. Choose this option only if you use Mentor asyour design tool.

b. If you already have the rich client installed to your machine, under theTeamcenter Rich Client list, choose the EDA for Rich Client option. Thisfeature installs files to support launching an ECAD tool (such as Cadenceor Mentor) when you double-click a dataset in the Teamcenter Engineeringrich client UI.

c. In the Installation Directory field, choose a directory where you want toinstall the Teamcenter EDA client. For example, enter c:\teamcenter(Windows) or user-home/teamcenter (UNIX).



The client is installed to an eda subdirectory, for example,c:\teamcenter\eda (Windows) or user-home/teamcenter/eda (UNIX).This directory is known as TCEDAECAD_ROOT.

Do not use spaces in the path. Some Teamcenter EDA functions donot work if there are spaces in this path.

d. Click Next.

4. If you selected any features other than those used for Teamcenter EDA,enter information as needed in subsequent dialog windows. For informationabout standard Teamcenter Engineering installation dialog windows, see theInstallation on UNIX and Linux Servers or the Installation on Windows Serversmanual.

5. In the EDA Client dialog window, enter the following:

a. In the AIWS URL field, enter the address for the AIW Service running on theTeamcenter EDA Web server, for example:

http://host:port/tc/aiws/aiwebservice

Replace host with the name of the Web application server host running inyour thin client environment, and replace port with the server port.

b. The Cache Location field displays the full path to the directory wheretemporary data is to be stored. The default cache path is displayed. Changeif needed:

Windows systems:

c:\ecad\EdaCache\username

UNIX systems:

user-home/ecad/EdaCache/

c. The Staging Location field displays the full path to the directory whereyour ECAD designs are saved. This directory is the working directory forTeamcenter EDA. The default staging path is displayed. Change if needed:

Windows systems:

c:\ecad\EdaStaging\username

UNIX systems:

user-home/ecad/EdaStaging/

Do not use spaces in the cache or staging directory paths. SomeTeamcenter EDA functions do not work if there are spaces in thesepaths.

In these cache and staging directory examples, for Windowssystems, replace username with the name of the person usingTeamcenter EDA on this system. For UNIX systems, replaceuser-home with the home directory of the person using TeamcenterEDA on this system (set by the $HOME environment variable).



d. In the User Id field enter the Teamcenter Engineering ID for the user whologs in from this client. The default ID is the infodba administrator ID.

e. Click Next.

6. In the Confirm Selections window, click Next. Teamcenter EDA clientcomponents are installed.

The Add/Remove Components dialog window declares whether the installationwas successful. If the installation is successful, click Close. If the installation isunsuccessful, click Show Details and take corrective action.

7. FMS services are required to run the Teamcenter EDA client. The FMS servicesmust point to the Teamcenter Engineering server with Teamcenter EDA serversupport (which is defined in the fcc.xml file).

Typically, you install the FCC client if the thin client is the sole interface you useto access Teamcenter Engineering. If FMS services are not already on the clientmachine from a rich client installation, you must install the FCC client.

Perform the following steps to install the FCC client:

a. Access your Teamcenter Engineering software distribution image(for example, the installation CD-ROM) and browse to theadditional_applications\fcc_only directory (Windows) or theadditional_applications/fcc_only (UNIX).

b. Run the fcc_only executable file (fcc_only.exe for Windows systems andfcc_only.sh for UNIX systems). Follow the directions in the InstallShieldwizard to install the FCC client.

When you are prompted for the server to connect to, enter the name of theTeamcenter Engineering server. Also enter the FSC port on that server(for example, 4444).

The installation routine sets the FMS_HOME system environment variable.It also creates an fcc.xml file that points to the Teamcenter Engineeringserver.

If the server is moved to another machine, you must edit the fcc.xmlfile to point to that new machine. For more information, see Editing theTCEDAClient.properties File in chapter 5, Customizing TeamcenterEDA.

8. The Teamcenter EDA client sets an TCEDAECAD_ROOT userenvironment variable to point to the installed location of the TeamcenterEDA client (for example, c:\teamcenter\eda on Windows systems oruser-home/teamcenter/eda on UNIX systems).

Add the path for the installed location of the Teamcenter EDA client to thePATH environment variable. This allows access to the edacli batch file thatruns the Teamcenter EDA client.



9. Verify the client installation:

a. Verify that the FMS fcc.xml file points to your Teamcenter Engineeringserver.

b. Check that the FMS_HOME system environment variable is set and pointsto the location of the fcc.xml file.

c. Check that the TCEDAECAD_ROOT user environment variable is setto your Teamcenter EDA directory (for example, c:\teamcenter\eda onWindows systems or user-home/teamcenter/eda on UNIX systems).

Check that the path for TCEDAECAD_ROOT has been added to the PATHenvironment variable.

d. Verify that the directory defined by the TCEDAECAD_ROOT user variableexists and is populated with files.

e. If you are using Cadence, verify that the Cadence directory exists in theTCEDAECAD_ROOT directory. If you are using Mentor Graphics, verifythat the Mentor_BoardStation directory exists.

f. Verify that the TCEDAClient.properties file in the TCEDAECAD_ROOTdirectory contains the values you entered using the install routine, forexample:

URL=http://hostname:port/tc/aiws/aiwebserviceUser=user-nameCacheDir=cache-directory-locationStagingDir=staging-directory-location

The cache and staging directories paths contain a slash between directorieson UNIX systems. On Windows systems they contain double backslashes,for example:

CacheDir=C:\\ecad\\EdaCache\\usernameStagingDir=C:\\ecad\\EdaStaging\\username

When you first run Teamcenter EDA, the cache andstaging directories are created from the settings in theTCEDAClient.properties file. For more information, see Creatingthe Cache and Staging Directories, later in this chapter.

The TCEDAClient.properties file provides the login data,and points to a host, a user, a staging directory, and a cachedirectory. All four settings must be a unique combination.Therefore, administrators should never change settings in theTCEDAClient.properties file. Making changes to this fileinvalidates the user’s staging directory and cache.

The only supported circumstance for editing this file is if the servermoves to a new machine. For more information, see Editing theTCEDAClient.properties File in chapter 5, Customizing TeamcenterEDA.



Enabling the Teamcenter Menu

To use Teamcenter EDA, users choose the Teamcenter menu from their designtool (Mentor or Cadence). Perform the steps in the following sections to place theTeamcenter menu into the user interface.

Enabling the Teamcenter Menu in Mentor Graphics

Perform the following steps to enable the Teamcenter menu in Mentor Graphics:

1. Verify applications:

a. Confirm that the Mentor Graphics installation is complete and functional.

b. Verify that the Teamcenter Engineering server is operational.

c. Verify that the Teamcenter Engineering rich client and/or thin client isinstalled and functional.

2. Verify environment variables:

a. Verify that a TCEDAECAD_ROOT user environment variable was createdby the installer and that it points to the directory where Teamcenter EDAis installed.

b. Verify that the JAVA_HOME environment variable exists and points to aJava installation.

3. Verify that the Mentor_BoardStation directory exists in theTCEDAECAD_ROOT directory. This directory contains files that enable MentorGraphics to communicate with Teamcenter EDA.

4. Copy all the files in the following location:

Windows systems:

TCEDAECAD_ROOT\Mentor_BoardStation\platform-directory\bin

UNIX systems:

TCEDAECAD_ROOT/Mentor_BoardStation/platform-directory/bin

To the following location:

Windows systems:

MGC_HOME\bin

UNIX systems:

MGC_HOME/bin

Replace TCEDAECAD_ROOT with the installed location of Teamcenter EDA.Replace platform-directory with the directory for the computer platform for yourmachine, for example, wnti for Windows systems. Replace MGC_HOME withthe Mentor Graphics home directory location.

5. Open a Mentor Graphics korn shell window (Windows) or any shell (UNIX).



6. Enter the mti_dmgr command. This starts Mentor Graphics Design Managerwith the Teamcenter option added to the top menu bar and with TeamcenterEDA customizations.

After Mentor Graphics starts, verify that the Teamcenter menu displays inthe menu bar.

For an overview of the Teamcenter menu, see chapter 2, Getting Started WithTeamcenter EDA.

If you have any problems launching tasks from the Teamcenter menu, look at thesettings within the mti_dmgr file in the MGC_HOME directory. Also examinethe messages posted in the Design Manager log written to the open window. IfTeamcenter support help is required, submit the Design Manager log text tocustomer support.



Enabling the Teamcenter Menu in Cadence

To enable the Teamcenter menu in Cadence, you must follow the instructions in theREADME.txt files in the Cadence subdirectories under TCEDAECAD_ROOT.TCEDAECAD_ROOT represents the installed location of Teamcenter EDA. Copyand paste the text specified in the README.txt files into the appropriate Cadencefiles located in your Cadence installation directory (CDSROOT).

As a precaution, make backup copies of the Cadence files before pastingnew text into them.

Enabling the Menu in PCB

Follow the directions in the TCEDAECAD_ROOT\Cadence\pcb\README.txtfile (Windows) or TCEDAECAD_ROOT/Cadence/pcb/README.txt (UNIX).

1. Place the following text at the end of theCDSROOT\share\local\pcb\skill\allegro.ilinit file(Windows) or the CDSROOT/share/local/pcb/skill/allegro.ilinit file (UNIX):

let( ( TcEdaEcadSkill (tcEdaEcadRoot axlGetVariable("TCEDAECAD_ROOT")) )if(tcEdaEcadRoot then

TcEdaEcadSkill = simplifyFilename(strcat(tcEdaEcadRoot "/Cadence/skill"))setSkillPath( append( list("." TcEdaEcadSkill) getSkillPath() ) )load( "TcEdaPcbMenuCmds.il")

elseprintf("ERROR: TCEDAECAD_ROOT has not been set. TcEda could not been loaded\n")

)) ; let

If the allegro.ilinit file does not exist, copy theTCEDAECAD_ROOT\Cadence\pcb\allegro.ilinit file to theCDSROOT\share\local\pcb\skill directory (Windows),or TCEDAECAD_ROOT/Cadence/pcb/allegro.ilinit toCDSROOT/share/local/pcb/skill (UNIX).

2. Insert the following text into theCDSROOT\share\pcb\text\cuimenus\allegro.menfile (Windows) or CDSROOT/share/pcb/text/cuimenus/allegro.men (UNIX)before the POPUP "&Help" line:

POPUP "Team&center"BEGIN

MENUITEM "&Open...", "TcEda_open_pcb"MENUITEM SEPARATORMENUITEM "&Save...", "TcEda_save_pcb"MENUITEM "Save Secondary &Data...", "TcEda_save_data_pcb"MENUITEM "Save &As...", "TcEda_save_as_pcb"MENUITEM "Check-&In...", "TcEda_check_in_pcb"MENUITEM "Check-O&ut...", "TcEda_check_out_pcb"MENUITEM "&Cancel Checkout...", "TcEda_cancel_checkout_pcb"MENUITEM SEPARATORMENUITEM "&Refresh", "TcEda_refresh_pcb"MENUITEM SEPARATORMENUITEM "&Purge Cache...", "TcEda_purge_cache_pcb"MENUITEM "Ite&m Info", "TcEda_item_info_pcb"MENUITEM "Pre&ferences...", "TcEda_preferences_pcb"MENUITEM "&Logout.", "TcEda_logout_pcb"

END



Enabling the Menu in HDL

Open the TCEDAECAD_ROOT\Cadence\sch\README.txt file (Windows) orthe TCEDAECAD_ROOT/Cadence/sch/README.txt file (UNIX), and follow itsdirections:

1. Place the following text at the end of theCDSROOT\share\cdssetup\concept\concepthdl.scr file(Windows) or the CDSROOT/share/cdssetup/concept/concepthdl.scrfile (UNIX):

{TcEda client commands}script ($TCEDAECAD_ROOT)/Cadence/sch/TcEdaSchMenuCmds.scr;

2. Insert the following lines into theCDSROOT\share\cdssetup\concept\concepthdl_menu.txt file (Windows)or the CDSROOT/share/cdssetup/concept/concepthdl_menu.txt file(UNIX) before the "&Help" { line:

"Teamcente&r" {"&Open..." TcEda_open_sch;"Ite&m Info" TcEda_item_info_sch;SEPARATOR;"&Save..." TcEda_save_sch;"Save Secondary &Data..." TcEda_save_data_sch;"Save &As..." TcEda_save_as_sch;"Check-&In..." TcEda_check_in_sch;"Check-O&ut..." TcEda_check_out_sch;"&Cancel Check-Out..." TcEda_cancel_checkout_sch;SEPARATOR;"&Refresh" TcEda_refresh_sch;"&Purge Cache..." TcEda_purge_cache_sch;SEPARATOR;"Pre&ferences..." TcEda_preferences_sch;"&Logout" TcEda_logout_sch;

}

3. Open the TCEDAECAD_ROOT\Cadence\sch\concepthdl_cmd.txt file(Windows) or the TCEDAECAD_ROOT/Cadence/sch/concepthdl_cmd.txtfile (UNIX), and place its contents at the end of theCDSROOT\share\cdssetup\concept\concepthdl_cmd.txt file (Windows)CDSROOT/share/cdssetup/concept/concepthdl_cmd.txt file (UNIX).

If the concepthdl_cmd.txt file does not exist, copy theTCEDAECAD_ROOT\Cadence\sch\concepthdl_cmd.txt file tothe CDSROOT\share\cdssetup\concept directory (Windows), or copythe TCEDAECAD_ROOT/Cadence/sch\concepthdl_cmd.txt file to theCDSROOT/share/cdssetup/concept directory (UNIX).

Verifying the Teamcenter Menu Setup in Cadence

To verify that the Teamcenter menu displays, launch Allegro Design Entry HDLand/or PCB and verify that the Teamcenter menu displays on the top menu bar.

For an overview of the Teamcenter menu, see chapter 2, Getting Started WithTeamcenter EDA.

If you have any problems launching tasks from the Teamcenter menu, look atthe settings within the files you edited. Also examine the messages posted in thetcEdaCdsSkill.log Cadence log file. If Teamcenter support help is required, submitthe Cadence log file to support. The log file is located in a temporary system folder.



Creating the Cache and Staging Directories

The Teamcenter EDA staging directory holds designs for checkin and checkoutwith Teamcenter Engineering and the cache directory is where temporary datais stored. The first time you select a menu option on the Teamcenter menu, thecache and staging directories are created automatically using the settings in theTCEDAClient.properties file.

Perform the following steps:

1. Launch your design tool.

If you use Mentor Graphics, run the mti_dmgr file from a Korn shell window.

If you use Cadence, launch Allegro Design Entry HDL or PCB Editor.

2. Log in to Teamcenter Engineering:

a. Pull down the Teamcenter menu and choose the Open option. TheTeamcenter EDA login dialog window is displayed.

The login dialog window may be hidden behind your design tooldialog window. Minimize other dialog windows to reveal the logindialog window.

b. In the Teamcenter EDA login dialog window, enter your TeamcenterEngineering user name, password, and group (if applicable).

You must log in with the user ID presented. The staging and cachedirectories are created specifically for that person for use on thissystem.

c. Click Login.

The Open Dataset dialog window is displayed. When you log in for the firsttime, the cache and staging directories are created automatically.

d. Click Cancel on the Open Dataset dialog window.

e. In your design tool, pull down the Teamcenter menu and choose the Logoutoption. You are logged out of Teamcenter Engineering.

3. Verify that the cache and staging directories are created. The directories arecreated from the settings in the TCEDAClient.properties file.

4. If you use Mentor Graphics, create a location map for the staging directory,for example, $TcEda_Staging. Verify the location map settings by openinga navigator window and verifying that it opens to the staging directory. Formore information about location maps, see Location Map Usage in appendixB, Reference.

You must create and store your designs in the staging directory so that youcan check them in to Teamcenter Engineering and check them out fromTeamcenter Engineering. For more information, see Using the StagingDirectory in chapter 2, Getting Started With Teamcenter EDA.



Enabling Creation of Viewable Files (Optional)You can create .eda viewable files of ECAD designs. The designs can then be viewedusing InterComm or another viewer.

Perform the following steps to enable creation of viewable files:

1. Install and configure the Translation Solution Toolkit (TSTK) on a dedicatedmachine used only for translation. TSTK is required to translate native designfiles into viewable files. (Mentor and Cadence are not required on the translationmachine.)

For more information about installing and configuring TSTK, see the TranslationSolution Toolkit Installation Guide.

2. Ensure that you have installed Engineering Translation Services (ETS) on theTeamcenter Engineering server machine as described in Installing TeamcenterEDA Server Support, earlier in this chapter. Also ensure that you installedCadence Translation Support or Mentor Translation Support, depending onyour CAD design tool.

For more information about installing ETS, see the Installation on WindowsServers manual or the Installation on UNIX and Linux Servers manual.

3. Ensure that you have installed the InterComm viewer software on the TSTKserver. The InterComm.exe file is used by the translation process to generateviewable files.

For more information about installing InterComm, see Installing InterComm(Optional), earlier in this chapter.

4. Copy the translator.xml file in the IMAN_ROOT\eda directory (Windows)or the IMAN_ROOT/eda directory (UNIX). Use this file to replace thetranslator.xml file in on the TSTK sever in the TSTK\Module\conf directory(Windows) or the TSTK/Module/conf directory (UNIX). Make a backup of theoriginal file before replacing it with the Teamcenter EDA version.

Replace IMAN_ROOT with the installed location of Teamcenter Engineering.Replace TSTK with the location of the Translation Solution Toolkit on thetranslation server.

5. Edit the TSTK\Module\conf\transmodule.xml file (Windows) orTSTK/Module/conf/transmodule.xml file (UNIX) on the TSTK server to addthe Teamcenter EDA translations, for example:

<Translators><Translator name="&default;" tag="ToZipfile"/><Translator name="&default;" tag="CadenceToEda"/><Translator name="&default;" tag="CadenceSchToEda"/><Translator name="&default;" tag="CadenceToIff"/><Translator name="&default;" tag="MgcSchToEda"/><Translator name="&default;" tag="MgcPcbToEda"/><Translator name="&default;" tag="ToUnzipfile"/>

</Translators>

These translators correspond to the translator definitions in the translator.xmlfile.

6. Ensure that your Translation Solution Toolkit (TSTK) server is up and running.



7. On the Teamcenter Engineering server, run theIMAN_ROOT\ets\ets_create_rqst.exe file (Windows) orIMAN_ROOT/ets/ets_create_rqst.exe file (UNIX) to verify that you cantranslate Mentor and/or Cadence CAD designs.

Run ets_create_rqst.exe –h to obtain the command line arguments:

ets_create_rqst.exe-i=<item ID>-r=<revision ID>[-rn=<relation>]-dn=<dataset name>[-dv=<dataset version number>]-dt=<ds_type_name>-pr=<priority 1|2|3>-pn=<translator provider name>-tn=<translator name>-tr=<trigger string>[-ta1=<trans arg1> [-ta2=<trans arg2> [-ta3=<trans arg3>]]][-u=user ID] [-p=password] [-g=group][-verbose]

For example, you can run the following command line options to translatedifferent file types:

%IMAN_BIN%\ets_create_rqst.exe -i=<item ID> -r=<revision ID> -dn=<dataset name>-dt=EDADesCadBrd -pr=1 -pn=UGS -tn=CadenceToEda -tr=COMMAND_LINE

-u=infodba -p=infodba -g=dba

%IMAN_BIN%\ets_create_rqst.exe -i=<item ID> -r=<revision ID> -dn=<dataset name>-dt=EDADesCadSch -pr=1 -pn=UGS -tn=CadenceSchToEda -tr=COMMAND_LINE


%IMAN_BIN%\ets_create_rqst.exe -i=<item ID> -r=<revision ID> -dn=<dataset name>-dt=EDADesMentor -pr=1 -pn=UGS -tn=MgcPcbToEda -tr=COMMAND_LINE


%IMAN_BIN%\ets_create_rqst.exe -i=<item ID> -r=<revision ID> -dn=<dataset name>-dt=EDADesMentor -pr=1 -pn=UGS -tn=MgcSchToEda -tr=COMMAND_LINE


8. After you verify that you can translate Mentor or Cadence CAD designs, set upthe translation process for your site. For example, you can set up a script to runa nightly batch process to translate designs, or you could set up the TeamcenterEngineering server to trigger translation when CAD designs are checked in.

For more information about setting up translation processes, see the TranslationSolution Toolkit Installation Guide and the Engineering Translation ServicesCustomization manual.


Chapter

2 Getting Started WithTeamcenter EDA

Teamcenter EDA Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Teamcenter EDA Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Overview of the Teamcenter Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Performing a Typical Teamcenter EDA Workflow . . . . . . . . . . . . . . . . . . . . . . 2-5

Using the Staging Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6


Chapter

2 Getting Started With TeamcenterEDA

This chapter gives you an overview of Teamcenter EDA.

Teamcenter EDA integrates ECAD applications (such as Cadence and Mentor) withTeamcenter Engineering. Designers use Teamcenter EDA to move ECAD data intoand out of Teamcenter Engineering.

Teamcenter EDA supports Mentor Graphics and Cadence. You can accessTeamcenter EDA from the Mentor Graphics Design Manager and Cadence Allegroor Concept applications.


Chapter 2 Getting Started With Teamcenter EDA

Teamcenter EDA ComponentsA Teamcenter EDA installation is comprised of the following application components:

• ECAD design tool

The tools used to create designs. The supported electronic computer-aided(ECAD) design tools are Mentor Graphics and Cadence.

• Teamcenter EDA client

The client that moves designs between the ECAD design tool and TeamcenterEngineering. The Teamcenter EDA dialog windows are opened from options onthe Teamcenter menu in the ECAD design tool.

• Teamcenter Engineering server

A Teamcenter Engineering server with Teamcenter EDA support installed. Thesystem used to store and track the ECAD designs. The thin client and rich clientinterfaces are supported.

• InterComm viewer (optional)

A design view and markup tool developed by PTC. Open InterComm bydouble-clicking a viewable file (.eda) in the thin client or rich client interface.

• Translation server (optional)

A machine with the Translation Solution Toolkit installed that is dedicated totranslating CAD design files to viewable files (.eda). Engineering TranslationServices must be installed on the Teamcenter Engineering server to supporttranslation requests.

Figure 2-1 illustrates the components of Teamcenter EDA.

ECAD Design Tool(Mentor Graphics

or Cadence)

Teamcenter EDAClient

(client dialog windows)

Teamcenter EngineeringServer

with Teamcenter EDA Support

InterCommViewer

Save(Check In)

Open(Check Out)

TranslationRequests

TranslatedFiles

Translation Server(Translation

Solution Toolkit)

Figure 2-1. Teamcenter EDA Components


Getting Started With Teamcenter EDA

Teamcenter EDA ArchitectureTeamcenter EDA includes the following system architectural elements:

• ECAD design tool

Supported electronic computer-aided design tools (Mentor Graphics andCadence) provide scripting languages (Ample and Skil) to call the TeamcenterEDA client services.

• Client services

Eclipse RCP provides the framework for UI dialog windows, and providesextension points for communication with the ECAD design tool. The stagingdirectory is used to build archive files of designs and their BOMs. The local cacheholds Teamcenter Engineering item data.

• Teamcenter EDA

Communication from client services to Teamcenter Engineering is accomplishedvia PLM XML and AIWS (application independent Web services). TeamcenterEngineering utilizes a four-tier architecture to send design data to and fromthe database.

Figure 2-2 shows the system architecture of Teamcenter EDA.

ECAD Design Tool Client Services(C, C++, Java with

Eclipse UI)

Teamcenter Engineering

ResourceTier

PresentationTier

EnterpriseTier

Database

StagingDirectory

LocalCache

Figure 2-2. Teamcenter EDA Architecture



Overview of the Teamcenter MenuInstalling Teamcenter EDA places a Teamcenter menu on the menu bar in yourECAD design tool (Cadence or Mentor). For detailed instructions about using theoptions on the Teamcenter menu, see chapter 3, Using Teamcenter EDA.

The Teamcenter menu contains the following options:

• Open

Allows you to search for an ECAD design file in Teamcenter Engineering andopen it for reference (read-only) or modification (check it out).

• Item Info

Displays local Teamcenter Engineering information for the design.

• Save

Saves a new version of an opened and checked-out design, as well as a bill ofmaterials (BOM). The design remains in a checked-out state.

• Save Secondary Data

Saves a new dataset of secondary data (IDF, assembly, or fabrication) andassociates it with a design in Teamcenter Engineering.

• Save As

Performs a first-time save of a design to Teamcenter Engineering, makes a copyof an existing design with a new item ID, or saves a new revision of an existingdesign.

• Check-In

Checks in a design to Teamcenter Engineering and uploads Teamcenter EDAfiles and the BOM. (This is equivalent to saving the design and removing thecheckout lock.)

• Check-Out

Places a checkout lock on a currently opened design.

• Cancel Check-Out

Cancels the checkout lock on the design in Teamcenter Engineering and revertsthe opened design to the version prior to the checkout.

• Refresh

Updates the client cache with the latest version of the currently opened design.Checked out designs (that is, with the checkout lock applied) are not refreshed.

• Purge Cache

Clears the client cache of designs that are not checked out, and removesreferenced copies of these designs from the client staging directory. Checked-outdesigns are not affected (that is, designs with the checkout lock applied).


Getting Started With Teamcenter EDA

• Preferences

Sets preferences specific to Teamcenter EDA.

• Logout

Logs out of Teamcenter Engineering.

Performing a Typical Teamcenter EDA WorkflowPerform the following steps to perform a round-trip workflow from your ECADdesign tool to Teamcenter Engineering and back:

1. Create the design.

Create the design using your ECAD design tool (Cadence or Mentor) and saveit to a folder in the Teamcenter EDA staging directory that is named after thepart number (item ID).

You must create and store your designs in the staging directory sothat you can check them in to, and check them out from, TeamcenterEngineering. Create a folder with the same name as the part number ofthe design. This ensures data integrity because when you check out thedesign later from Teamcenter Engineering to make modifications, it issaved to a folder with the same name as the part number.

For more information, see Using the Staging Directory, later in thischapter.

2. Save the design to Teamcenter Engineering.

Pull down the Teamcenter menu and choose the Save As option. The design issaved and checked in to Teamcenter Engineering. The original design is still inyour staging directory.

3. Check out the design to make revisions.

Use your ECAD tool to open the design in your staging directory, then pull downthe Teamcenter and choose the Check-Out option. This places a checkout lock onthe corresponding design already checked in to Teamcenter Engineering, and theCO column in the Teamcenter Engineering interface displays a Y. This meansthat no one else can revise the design while you have it checked out.

If you want to revise a design that you have not worked on before, pulldown the Teamcenter menu and choose the Open option to search forthe design. To open the design for modification, click the Check Outcheckbox.

4. Check in the revised design to Teamcenter Engineering.

Pull down the Teamcenter menu and choose the Check-In option. You can alsochoose the Save As option to create a new revision and check it in.



Using the Staging DirectoryTeamcenter EDA requires that you create and work on designs in the stagingdirectory. If you have already created designs in another directory, copy them tothe staging directory, and from then on work on them exclusively from the stagingdirectory.

Before saving a design, you must create a separate folder in your staging directoryto hold each design, and this folder must be named identically to the part number(item ID) of the design (shown as part-number-folder in the following examples).This ensures that the file targets the correct location when being checked in andchecked out.

In the following examples, on Windows systems, replace username withthe name of the person using Teamcenter EDA on this system. On UNIXsystems, replace user-home with the home directory of the person usingTeamcenter EDA on this system (set by the $HOME environment variable).

Follow these conventions:

• Mentor Graphics

Save designs under a Mentor staging subdirectory, for example:

Windows systems:

c:\ecad\EDAStaging\username\Mentor\part-number-folder

UNIX systems:

user-home/ecad/EDAStaging/Mentor/part-number-folder

• Cadence

Save physical designs under a cadencePcb staging subdirectory, for example:

Windows systems:

c:\ecad\EDAStaging\username\cadencePcb\part-number-folder

UNIX systems:

user-home/ecad/EDAStaging/cadencePcb/part-number-folder

Save logical designs under a cadenceSchematic staging subdirectory, forexample:

Windows systems

c:\ecad\EDAStaging\username\cadenceSchematic\part-number-folder

UNIX systems:

user-home/ecad/EDAStaging/cadenceSchematic/part-number-folder

For more information about the staging directory, see About the Staging Directory inappendix B, Reference.


Chapter

3 Using Teamcenter EDA

Using the Teamcenter Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Saving Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Using the Save As Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Using the Save Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Using the Save Secondary Data Option . . . . . . . . . . . . . . . . . . . . . . . 3-5

Opening an Existing Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Checking Out Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Performing a Checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Canceling Checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Checking In Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Getting Design Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Working With Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Refreshing the Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Clearing the Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Setting Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12Logging Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Opening Viewable Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Starting Cadence Design Entry HDL With a Batch File . . . . . . . . . . . . . . . . . 3-13


Chapter

3 Using Teamcenter EDA

This chapter describes how to use Teamcenter EDA to move data between yourECAD design tool and Teamcenter Engineering.

Using the Teamcenter MenuThis topic describes how to use the options on the Teamcenter menu in your ECADdesign tool (Cadence or Mentor). For an overview of the options on the Teamcentermenu, see chapter 2, Getting Started With Teamcenter EDA.

Consider the following as you use options on the Teamcenter menu:

• Sometimes when you choose an option on the Teamcenter menu, a TeamcenterEDA dialog window does not display immediately because it is hidden behindyour design tool dialog window. Minimize or move other dialog windows to revealthe Teamcenter EDA dialog window.

• On Cadence, when you choose an option on the Teamcenter menu, your designtool dialog window may disappear from the window for a moment beforereappearing. Be patient and wait for your design tool to display again. This isthe normal process for refreshing the display.

• On Cadence, sometimes when you choose an option on the Teamcenter menu,you see the following status message in your design tool:

Warning: Current operation has not been finished.

This means that a Teamcenter EDA dialog window is still open and must beclosed.


Chapter 3 Using Teamcenter EDA

Logging In

Perform the following steps to log in to Teamcenter EDA:

1. Choose any option from the Teamcenter menu in your ECAD design tool. TheTeamcenter EDA login dialog window is displayed.

The login dialog window may be hidden behind your design tool dialogwindow. Minimize or move other dialog windows to reveal the logindialog window.

2. In the Teamcenter EDA login dialog window, enter your Teamcenter Engineeringuser name, password, and group (if applicable).

Do not log in as a different person than what is displayed in the logindialog window. Doing so invalidates the staging directory and the cache.The TCEDAClient.properties file provides the login data and pointsto a host, a user, a staging directory, and a cache directory. All foursettings must be a unique combination. For information about theTCEDAClient.properties file, see Editing the TCEDAClient.propertiesFile in chapter 5, Customizing Teamcenter EDA.

3. Click Login.

You only have to log in once per session because a cookie stores the sessioninformation. If there is no activity for a long period of time, the session times outand you are prompted to log in again.


Using Teamcenter EDA

Saving DesignsThere are several options for saving designs. Use the Save As option for a first-timesave of a design, to save a new revision of a design, or to make a copy of a design.Use the Save option to save changes to a design. Use Save Secondary Data to saveadditional files with a design.

Using the Save As Option

Perform the following steps to perform a first-time save of a design, to save a newrevision of a design, or to make a copy of a design:

1. In your ECAD design tool, create a new design in a folder in the staging location(as described in Using the Staging Directory in chapter 2), or open a designfor modification from Teamcenter Engineering and make desired changes tothe design.

2. In your ECAD design tool, pull down the Teamcenter menu and choose theSave As option. If prompted, log in.

If you use Mentor, and if the part number and nomenclature are savedas Mentor attributes, they are preloaded into the Save As dialog window.If values are changed, they are saved back into Mentor attributes. Ifattributes do not exist, new values are saved into Mentor attributes.

3. In the Select CCA dialog window, choose the CCA (circuit card assembly) file toassociate with the design, or click the Create CCA button.

4. If you create a CCA, perform the following steps in the Create CCA dialogwindow:

a. In the Select Folder panel, select the folder where you want to save thedesign.

You should have already created a folder in Teamcenter Engineering inwhich to save the design. You must do this to ensure successful checkin ofthe design and its associated components.

b. In the Item Information panel, enter the Teamcenter EDA item type as Item.

Enter the ID and revision, or click the Assign button to have themautomatically assigned. The item name defaults to the name given to theitem in the design tool.

c. Click the Create Secondary Items button if you want to create additionalitems related to the design, such as design documents. After you create thesecondary items, you can attach files to them in Teamcenter Engineering.

An additional dialog is displayed after you click the Create Secondary Itemsbutton. In the new dialog window, select the item type and enter the itemID, revision, and name. Click Add to add items, and click Assign to assignitem ID or revision. When you are done, click OK.

The Create Secondary Items button is enabled by theEDA_SecondaryItems preference. For more information, seeChanging System Preferences in chapter 5, Customizing TeamcenterEDA.



d. Click Next.

5. Enter the following information in the Schematic dialog window:

a. Ensure that the Selected Folder panel indicates the folder where you wantto save the design.

If you are saving a schematic using Cadence HDL, in the ItemInformation panel, the Type field defaults to EDASchem. Enterthe ID and revision, or click the Assign button to have themautomatically assigned. The item name defaults to the name givento the item in the design tool with _Schem added to the end ofthe name.

b. In the Dataset Information panel, enter a name and description for thedataset. The dataset name defaults to the name of the item with _DS addedto the end of the name.

Click the Check In checkbox if you want to check in the design to TeamcenterEngineering.

c. In the BOM options panel, indicate whether to save a BOM with the design:

• Cadence:

Select WithBOM or WithoutBOM.

• Mentor Graphics:

Select Board BOM, Schematic BOM, or No BOM.

The default choice is set by preferences.

d. Click Finish. The new revision is saved and checked in to TeamcenterEngineering.

A Save indicator displays showing that a save is in progress. Be patient. Itmay take several minutes for a save to complete.

The Save indicator may be hidden behind your design tool dialogwindow. Minimize other dialog windows to reveal the Saveindicator. In addition, your design tool dialog window may disappearfor a moment before reappearing on the screen.

e. Verify that the design is saved to Teamcenter Engineering by using the richclient or thin client to access Teamcenter Engineering.



Using the Save Option

Use the Save option to save a new version of an opened and checked-out designto Teamcenter Engineering. The design is left in a checked-out state for furthermodification. Perform the following steps:

1. In your ECAD design tool, open a design for modification from TeamcenterEngineering and make desired changes to the design.

2. Pull down the Teamcenter menu and choose the Save option.

In Cadence, if the design is new and has never been checked in, clickingthe Save option invokes the Save As operation.

3. In the BOM Option dialog window, click buttons to indicate whether to save aBOM with the design:

• Cadence:


• Mentor Graphics:


4. Click OK. The design is saved but remains in a checked out state. (To check inthe design you must use the Check-In option.)

Using the Save Secondary Data Option

Perform the following steps to save a new dataset of secondary data (IDF, assembly,or fabrication) with a design:

1. In your ECAD design tool, open a design.

2. Pull down the Teamcenter menu and choose the Save Secondary Data option.

3. Fill in the dialog window:

a. In the Type field, select the type of dataset to save: EDAAsm (assembly),EDAFab (fabrication), or EDAIdf (IDF).

b. In the Name field, enter the name you want to give the dataset. Do notinclude spaces.

c. Fill out the Description field, if desired.

d. In the File Explorer panel, select the files to include and click the + button.(Click the – button to remove files.)

e. Click OK. The new dataset files are saved and associated with the designin Teamcenter Engineering.

f. Verify that the new dataset files are saved with the design in TeamcenterEngineering by using the rich client or thin client to access Engineering.



Opening an Existing Design

If you want to open a design checked in to Teamcenter Engineering that you have notworked on before, pull down the Teamcenter menu in Cadence or Mentor Graphicsand choose the Open option. (To work on a design you already have in your stagingdirectory, use the Check Out option).

You can also open a design in the rich client My Navigator applicationby selecting the dataset and choosing File→Open or double-clicking thedataset file. This launches the ECAD tool and opens the file.

Perform the following steps to search for a design dataset file in TeamcenterEngineering and open it for reference (read-only) or modification (check it out):

1. In your ECAD design tool, pull down the Teamcenter menu and choose theOpen option. If prompted, log in.

2. In the Open DataSet dialog window browse to the design dataset you want toopen. By default design datasets are named with _DS at the end of the file.

You can also search for designs. Perform the following steps:

a. Click the dropdown arrow in the Search area and select the kind of searchyou want to perform (for example, Dataset...).

b. In the Criteria area, adjust your search as needed by entering text in theValue column. You can use an asterisk (*) for wildcard searching.

c. Click the magnifying glass icon to perform the search. Search results displayin the right panel.

d. In the right panel, select the dataset you want to open.

3. To open the dataset for reference only, do not check the Check out checkbox. Adesign opened for reference only is opened in your design tool for viewing only.You cannot revise it.

To open the dataset for modification, check the Check out checkbox, enter anID in the Change ID field, and enter any comments you want in the Commentsfield. A dataset that is opened for modification has a checkout lock applied to itin Teamcenter Engineering so that no one else can modify it.

The Check out checkbox is disabled if you already have a checked-outversion of the design in your staging directory, or if the dataset orrelated BVR is already checked out to you or someone else.

4. Click OK. The dataset is opened in your design tool.

The design is saved to a folder in the staging location with the samename as the part number (item ID). If the folder does not exist, the folderis created automatically and the checked out design is placed into it.

5. If you checked out the design, verify its checkout status in TeamcenterEngineering. When a design is checked out, the CO (checkout) column inTeamcenter Engineering displays a Y.



Checking Out Designs

Use the Check-Out option when you want to make revisions to a design in yourstaging directory, and it is a design you have already checked in to TeamcenterEngineering. When you check out the design, a checkout lock is placed on thecorresponding checked in design in Teamcenter Engineering so that no one else canopen it for modification.

If you want to revise a design that you have not worked on before, andtherefore the design is not in your staging directory, pull down theTeamcenter menu and choose the Open option to search for the design.Then to open the design for modification, click the Check Out checkbox.

Performing a Checkout

Perform the following steps to place a checkout lock on a design:

1. In your ECAD design tool, open a design in your staging directory that you havechecked in previously and that you now want to revise.

2. Pull down the Teamcenter menu and choose the Check-Out option.

If the item has not previously been checked in, you see a message thatstates:

Check out is not allowed because ofthe current item status.

3. In the Checkout dialog window, enter an identification number for the checkoutin the Change ID field and enter a description to the Comments field. (This isstandard for Teamcenter Engineering checkout).

Click OK.

A checkout lock is placed on the corresponding design in TeamcenterEngineering.

4. Verify the checkout status of the design in Teamcenter Engineering. When adesign is checked out, the CO (checkout) column for the design in TeamcenterEngineering displays a Y.



Canceling Checkout

Perform the following steps to cancel placing the checkout lock on the design inTeamcenter Engineering. This reverts the opened design to the version prior tothe checkout.

Canceling a checkout deletes the opened version of the design and deletesthe files in the local cache directory.

1. In your ECAD design tool, pull down the Teamcenter menu and choose theCancel Check-Out option.

The Cancel Checkout dialog window displays the following message:

Selecting OK will remove the check-out lockas well as all the changes since the check-out lockwas requested. The local cache will also be deleted.Do you still wish to proceed?

2. Click OK.

3. An Open DataSet dialog window displays the following message:

Directory directory-name already exists, do you want tooverwrite this directory?

Click OK if you want to replace the current version of the design with theprechecked out version.

The checkout lock is removed and the design is reverted to its prechecked outstate.



Checking In Designs

Use the Check-In option to remove the checkout lock on an opened and checkout-outdesign and save it back to Teamcenter Engineering.

You can also use the Save As to check in a design.

1. In your ECAD design tool, open a design and check it out from TeamcenterEngineering. When a design is checked out, the CO (checkout) column inTeamcenter Engineering displays a Y.

2. Make changes to the design.

3. Pull down the Teamcenter menu and choose the Check-In option.

If you see the message This item is not known to Teamcenterin your design tool, the design has not been previously saved inTeamcenter Engineering. To save the design, pull down the Teamcentermenu and choose the Save As option.

If you see the message The design has not been checked out forthis operation in your design tool, the design has not been checkedout from Teamcenter Engineering. Check out the design, makemodifications, and then choose the Check-In option.

4. In the Check-In dialog window, click buttons to indicate whether to save a BOMwith the design:

• Cadence


• Mentor Graphics


5. Click OK. The design is checked in to Teamcenter Engineering and replaces theprevious version. The Teamcenter EDA files are uploaded as well as a BOM (ifit was selected).

The checkout lock is also removed from the design. To verify, you can accessTeamcenter Engineering and see that the CO (checkout) column in TeamcenterEngineering no longer displays a Y by the design.



Getting Design Information

You can get information on a design in the staging location. This information onlyreflects the state of the designs in your staging location. For example, if you checkout a design for reference, the information says that the checkout flag is not set onthe design, even if someone else has checked out the same design for modification.

Perform the following steps to obtain Teamcenter Engineering-related informationabout a design:

1. In your ECAD design tool, open a design for reference or modification fromTeamcenter Engineering.

2. Pull down the Teamcenter menu and choose the Item Info option.

Teamcenter EDA displays a dialog window listing the design name, applicationreference number (to keep the local version and Teamcenter Engineering versionin sync), item ID, item revision, checkout status, working directory, and version.

3. Click OK to close the informational dialog window.



Working With Cache

The cache directory temporarily holds data as designs move between your designtool and Teamcenter Engineering. Occasionally, you may need to refresh or clear thecache so that it reflects the latest versions of your designs.

Refreshing the Cache

Refreshing the cache updates the client cache with the latest version of the currentlyopened design. No refresh is done if the design is checked out for modification andhas the checkout lock applied.

Perform the following steps to update the client cache with the latest modified design:

1. In your ECAD design tool, open a design that has already been checked in.

2. In your ECAD design tool, pull down the Teamcenter menu and choose theRefresh option.

3. If the design is the latest version available, a dialog window displays thefollowing message:

The dataset is up to date,no refresh is needed.

However, if there is a newer design found on Teamcenter Engineering, you arenotified that the older design is out of date and needs to be refreshed.

4. Click OK in the notification dialog window.

If the design was out of date the newer design replaces it in the cache andstaging directories.

Clearing the Cache

The Purge Cache option clears the client cache of nonchecked-out designs, andremoves copies of these designs from the client staging directory. Checked-outdesigns (that is, with the checkout lock applied) are not affected.

Do not make manual changes to the cache. If you manually delete the cachewithout using the Purge Cache option, you are blocked from making anyfurther changes to designs.

Perform the following steps to clear the client cache and remove copies of designsfrom the client staging directory:

1. In your ECAD design tool, pull down the Teamcenter menu and choose thePurge Cache option.

2. A dialog window displays the following message:

Selecting OK will cancel the sessionand remove all files from the local cache.Do you still want to proceed?

Click OK in the confirmation dialog window. All data is removed from the cacheand staging directories except for those designs with checkout locks and thosedesigns that have never been saved to Teamcenter Engineering.



Setting Preferences

To set default actions on Teamcenter EDA dialog windows, pull down the Teamcentermenu and choose the Preferences option.

You can set the following preferences:

• Common EDA tab

– Check-In Option Default

Selects the Check In box on the save dialog windows so that by defaultdesigns are checked in when you save them.

– Default Save As Folder

Sets the folder in Teamcenter Engineering where designs are saved.

• Mentor tab

Use the BOM Option Default field to select the default BOM option when savingdesigns. Select FromPCB to create the BOM from a PCB, select FromSchematicto create the BOM from the schematic, or select WithoutBOM to omit the BOMupon a save.

• Cadence tab

– BOM Option Default

Sets the default BOM creation option when you save a design. ChooseWithBOM to create a BOM upon save or WithoutBOM to omit the BOMupon a save.

– Schematic BOM Template

Sets the path of the template to use for the schematic BOM. TeamcenterEDA provides a tcEdaSchTemplate.bom template file that allows you tocustomize how schematic bill of materials (BOMs) are created. If you do notset the preference, the default Teamcenter EDA template is used.

For more information, see Customizing Cadence BOM Templates in chapter5, Customizing Teamcenter EDA.

– PCB BOM Template

Sets the path of the template to use for the PCB BOM. Teamcenter EDAprovides a tcEdaPcbTemplate.bom template file that allows you tocustomize how PCB bill of materials (BOMs) are created. If you do not setthe preference, the default Teamcenter EDA template is used.

For more information, see Customizing Cadence BOM Templates in chapter5, Customizing Teamcenter EDA.

There are additional preferences that can be set using the Navigator application inthe rich client. For more information, see Changing System Preferences in chapter 5,Customizing Teamcenter EDA.



Logging Out

To log out of Teamcenter EDA, pull down the Teamcenter menu and choose theLogout option.

The next time you choose an option on the Teamcenter menu you are promptedto log in.

You are logged out when you exit your ECAD design tool, although this maynot work consistently. It is always good practice to use the Logout optionwhen you are done working with Teamcenter EDA.

Opening Viewable FilesIf Teamcenter Engineering translation support is installed on your server, .edaviewable files can be generated from your CAD designs. You can then use theInterComm viewer to view and markup the designs. To create viewable files, yourenvironment must be set up as described in Enabling Creation of Viewable Files(Optional), in chapter 1, Installing Teamcenter EDA.

If you have installed InterComm and have enabled the Perl MIME type, whenyou open an .eda file in Teamcenter Engineering, the viewable file is opened withInterComm. For use of InterComm for viewing and markup, see the InterCommdocumentation.

Starting Cadence Design Entry HDL With a Batch FileIf you use Cadence as your design tool, you can start the Cadence Design EntryHDL application using the startCDSDesignEntryHdl.bat file located in theTCEDAECAD_ROOT directory. When you run the startCDSDesignEntryHdl.batfile, the Teamcenter EDA Open dialog window is displayed. Choose the design youwant to open, and the Cadence Design Entry HDL application runs and displaysyour design.

This is a useful tool if you have purged all your designs from the staging directoryand therefore cannot open the Cadence Design Entry HDL application withoutfirst creating a design.

You can also run the startCDSDesignEntryHdl.bat file from a prompt using the–projName option to specify a project file. Cadence opens that file directly.


Chapter

4 Troubleshooting

Empty Open Dialog Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Refresh Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Component Error When Saving Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

System Hangs When Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Packaging Error on Cadence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

BOM Template Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4


Chapter

4 Troubleshooting

This chapter describes how to troubleshoot problems using Teamcenter EDA.

Empty Open Dialog Window

Problem

When you pull down the Teamcenter menu and choose the Save As or Open options,the resulting dialog window does not display folders under your Home folder inTeamcenter Engineering.

Diagnosis

You are not connected to the Teamcenter Engineering server.

Solution

The problem may be caused by one of the following situations. Try each until youare able to again see folders under your Home folder:

• You have neglected to log out of Teamcenter Engineering after your last worksession.

1. Pull down the Teamcenter menu and choose the Logout option.

2. Pull down the Teamcenter menu and choose the Save As or Open option.You are prompted to log in again.

3. Log in.

After you log in, the Save As or Open dialog window displays folders underthe Home folder.

• Your connection to Teamcenter Engineering has been lost because the serveris down.

Check to ensure that the server is still running by logging in to TeamcenterEngineering on that server using the thin client or the rich client.


Chapter 4 Troubleshooting

• Your Teamcenter EDA client machine is not pointing to the server.

1. Open the fcc.xml file on your machine (found in your FMS_HOME directory)and make sure that the FSC master node points to the server.

2. If the fcc.xml file is not pointing to the server, reset the fcc.xml fileby reinstalling the FCC client. Run the fcc_only command from yourinstallation source (for example, CD-ROM).

• The server is not enabled for access by your client.

If this is the case, you see an error similar to the following when you accessthe Save As or Open dialog windows:

No route available for enterprise: ’417637057’,volume: ’1396441fff1a18e4a2c1’

Note: This is usually due to a configuration problem where theFMS master config has not been updated with the propervolume/accessor id (requires an FMS restart).

It can also indicate a multisite configurationthat is missing information about the given enterprise.

Ask the administrator of the server to modify theIMAN_ROOT\fms\fmsmaster_FSC*.xml file (Windows) orIMAN_ROOT/fms/fmsmaster_FSC*.xml (UNIX). Ask the administrator to findthe transient volume ID and change it to the ID from the error message.

For more information about resolving this kind of FMS master configurationproblem, see the Teamcenter Engineering Configuration Guide.

Refresh Failure

Problem

The latest version of the dataset is not loaded when you use the Refresh option. Or anew folder created using Teamcenter Engineering does not display in the Open orSave As dialog windows.

Diagnosis

A change occurred in the system since the last time the user logged in usingTeamcenter EDA. For example, a new version of the dataset was created or a newfolder was created.

Solution

Log out and log in again to get the latest information from the server.


Troubleshooting

Component Error When Saving Designs

Problem

When you attempt to save a design, a dialog window displays the following errormessage:

Save is not allowed.The following component(s) do not exist in Teamcenter.

Diagnosis

The EDA_CheckComponentExistence preference is set to 1 (true) on theTeamcenter Engineering server. The system is checking to see if prerequisitecomponents exist on the server.

Solution

An administrator must place components on the Teamcenter Engineering server,or set the EDA_CheckComponentExistence preference to 0 (false). Formore information, see Populating the Database With Components in chapter 5,Customizing Teamcenter EDA.

System Hangs When Saving

Problem

The system hangs when saving a design.

Diagnosis

There are potentially many causes for such a problem.

One possible cause may be if you create designs directly under the staging directoryinstead of in a staging directory subfolder named after the part name. If you createa design directly under the staging directory, working ZIP files at the root of thestaging directory are themselves placed into ZIP files when performing a save. Thisresults in a system hang.

Solution

Always create designs in staging directory subfolders named after the design partname. For more information, see Using the Staging Directory in chapter 2, UsingTeamcenter EDA.


Chapter 4 Troubleshooting

Packaging Error on Cadence

Problem

While using Cadence as the ECAD design tool to save a design with a BOM, thefollowing error displays:

Fatal errors in packaging.Operation will be aborted.

Diagnosis

Because the packaging function is called automatically, if any error occurs duringBOM packaging, the operation terminates.

Solution

Perform the following steps to resolve the problem:

1. In Cadence pull down the File menu and choose the Export Physical option torun manual packaging.

2. From the output list, find the cause of error and correct the error.

3. Resave the design with a BOM using Teamcenter EDA.

BOM Template Error

Problem

When you save a design with a BOM, a dialog window displays the following warning:

Found component(s) in the list without Part Number as Item ID.

Diagnosis

You are using a customized Cadence BOM template, and the components in thelist do not have the PART_NUMBER property specified. The PART_NUMBERproperty is required by Teamcenter EDA and is used as the item ID. The problem canbe caused by associating a nonexisting property to the required PART_NUMBERproperty in the BOM template.

Solution

Check the customized Cadence BOM template to see if a valid property is associatedwith the PART_NUMBER property.


Chapter

5 Customizing Teamcenter EDA

Populating the Database With Components . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Customizing Cadence BOM Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Printed Circuit Board BOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Schematic BOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Editing the TCEDAClient.properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Changing System Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4


Chapter

5 Customizing Teamcenter EDA

This chapter describes how to alter Teamcenter EDA for use at your company. Theprocedures in this chapter should only be performed by system administrators.

Populating the Database With ComponentsMany companies control the component library items that can be used to createBOMs by having an administrator check in to the database those componentsapproved for use. Thereafter, users can create BOMs that use those components.

As a way to manage this process, when Teamcenter EDA is first installed theEDA_CheckComponentExistence is set to 1 (true). With this setting, userscannot save design BOMs unless all the needed components are already placed inTeamcenter Engineering. They receive an error message upon save that statesthe following:

Save is not allowed.The following component(s) do not exist in Teamcenter.

Therefore, before users can begin using Teamcenter EDA to save designs with BOM,an administrator must first populate the database with components or change theEDA_CheckComponentExistence preference from 1 (true) to 0 (false).

An administrator must perform the following steps to populate the database withcomponents:

1. Ensure that users have not yet begun to use Teamcenter EDA. This process mustbe performed before users start saving designs and creating BOMs.

2. Set the EDA_CheckComponentExistence preference by performing thefollowing steps:

a. Run the rich client on the Teamcenter Engineering server and log in as anadministrator (for example, infodba).

b. In the Navigator application, pull down the Edit menu and choose theOptions option.

c. In the Options dialog window, click Index at the bottom of the window.

d. In the Preferences dialog window, search for theEDA_CheckComponentExistence preference and change its value from 1(true) to 0 (false).

e. Click the Modify button to save the preference.


Chapter 5 Customizing Teamcenter EDA

3. Locate or create designs that utilize the approved library components. Usethe Teamcenter EDA Save As option to save the designs to the TeamcenterEngineering server and create BOMs. When the BOMs are created, thecomponents are automatically placed in the database.

For directions about using the Save As option, see Saving Designs in chapter 3,Using Teamcenter EDA.

4. Reset the EDA_CheckComponentExistence preference to 1 (true) if you wantto restrict users to using only approved (and checked in) components.

If instead you want to allow new components to be automaticallyplaced in the database when users create BOMs, leave theEDA_CheckComponentExistence preference set to 0.

Customizing Cadence BOM TemplatesAdministrators can customize how bill of materials (BOMs) are created for Cadenceprinted circuit board (PCB) and schematic (SCH) designs. Administrators canuse the provided templates as references to create new templates, and then setpreferences to point to them. For more information about setting preferences, seeSetting Preferences in chapter Using Teamcenter EDA, Using Teamcenter EDA.

Printed Circuit Board BOM

Use the tcEdaPcbTemplate.bom as a starting point for customization. Whenediting the template file, keep the first four properties unchanged and in theircurrent order. The file header contains comments to assist you with customization.

For additional information, see the README.txt file in theTCEDAECAD_ROOT\Cadence\pcb directory (Windows) or theTCEDAECAD_ROOT/Cadence/pcb directory (UNIX). TCEDAECAD_ROOTrepresents the installed location of the Teamcenter EDA client.

Schematic BOM

The tcEdaSchTemplate.bom file is used to generate the BOM.xml file attachedto the dataset. You can replace the original Cadence template file with your ownversion of tcEdaSchTemplate.bom. Within Cadence, choose Tools→PackagerUtilities→Bill of Materials, open the tcEdaSchTemplate.bom template file, reviseit, and overwrite the original Cadence template file. (Create a backup copy of theoriginal Cadence file first.)

For additional information, see the README.txt file in theTCEDAECAD_ROOT\Cadence\sch directory (Windows) or theTCEDAECAD_ROOT/Cadence/sch directory (UNIX). TCEDAECAD_ROOTrepresents the installed location of the Teamcenter EDA client.


Customizing Teamcenter EDA

Editing the TCEDAClient.properties FileThe TCEDAECAD_ROOTTCEDAClient.properties file provides the login data,and points to a host, a user, a staging directory, and a cache directory. All foursettings must be a unique combination. Therefore, administrators should avoidchanging settings in the TCEDAClient.properties file. Making changes to thisfile invalidates the user’s staging directory and cache.

However, if the server is moved to a different machine, administrators can edit theTCEDAClient.properties file to point user workstations to the new server. (This isa one-time change. UGS does not recommended that you change settings to pointback to the original server.)

Perform the following steps:

1. Use the Teamcenter EDA client to check in all currently checked-out designs.

2. Use the Teamcenter EDA client to purge the cache.

3. Manually delete the cache and staging directories.

4. Edit the URL line in the TCEDAClient.properties file to point to the newserver.

The TCEDAClient.properties file is located in the in the TCEDAECAD_ROOTdirectory and contains the following information:

URL=http://hostname:port/tc/aiws/aiwebserviceUser=user-nameCacheDir=cache-directory-locationStagingDir=staging-directory-location

In the example, replace hostname with the name of the Web application server ofthe new server running in the thin client environment, and replace port withthe port of that server.

The cache and staging directories paths must contain doublebackslashes on Windows systems, for example:

CacheDir=C:\\ecad\\EdaCache\\usernameStagingDir=C:\\ecad\\EdaStaging\\username

5. Edit the fcc.xml file to point to the new server.

The fcc.xml file is discussed in step 7 of Installing the Teamcenter EDA Client inchapter 1, Installing Teamcenter EDA.

If for some reason the administrator needs to change the properties for theuser, the cache directory, or staging directory, this process can be followed.However, UGS does not recommend this as a way to switch back and forthbetween settings, but only has a one-time change that should be undertakenonly if absolutely necessary.


Chapter 5 Customizing Teamcenter EDA

Changing System PreferencesAdministrators can set system-wide preferences on the Teamcenter Engineeringserver that apply to all Teamcenter EDA users.

Users can set Teamcenter EDA preferences by pulling down the Teamcentermenu in their ECAD tool and choosing the Preferences option. For moreinformation, see Setting Preferences in chapter 3, Using Teamcenter EDA.

To change system-wide preferences, perform the following steps:

1. Run the rich client on the Teamcenter Engineering server and log in as anadministrator (for example, infodba).

2. In the Navigator application pull down the Edit menu and choose the Optionsoption.

3. In the Options dialog window, click Index at the bottom of the window.

4. In the Preferences dialog window, search for the preferences that begin withEDA_. The following preferences are displayed:

• EDA_CadenceBOMOptionDefault

Sets a default selection for the Cadence BOM option. The value can be eitherWithBOM or WithoutBOM.

• EDA_CheckComponentExistence

Defines whether to check for components in Teamcenter Engineeringbefore saving a design. Set to 1 to require that components already existin Teamcenter Engineering, or set to 0 if no check is required. For moreinformation, see Populating the Database With Components, earlier in thischapter.

• EDA_MentorBOMOptionDefault

Sets the default selection for the Mentor BOM option. The value can beFromPCB, FromSchematic, or WithoutBOM.

• EDA_SecondaryItems

Enables the Create Secondary Items button on the Create CCA dialogwindow. This lets users create secondary items under the top-level CCA.For more information, see Using the Save As Option in chapter 3, UsingTeamcenter EDA.

5. Change the preference value and click the Modify button to save the new value.


Appendix

A Glossary


Appendix

A Glossary

This appendix defines Teamcenter Engineering terms.

A

AssemblyCompound object that is assembled from other objects and may add additionalinformation to their interpretation. In the context of an assembly, other assembliesare called subassemblies, while noncompound objects are called components.

AttributeNamed storage variable that describes an object and is stored with the object. Userscan search the database for objects using the object’s attributes.

In an object, an attribute is a name/value pair; in the database, an attribute is a field.

B

BOM ViewTeamcenter Engineering object used to manage product structure information foran item.

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

C

Corporate ServerHost computer at the center of a Teamcenter Engineering network. This hostcontains the Teamcenter Engineering application root directory, TeamcenterEngineering data directory, licensing, file managers (Teamcenter File Services andFile Management System), and volumes. For installations that include the Webtier (four-tier architecture), the corporate server also contains the TeamcenterEngineering server manager. Multiple application clients can map to or mount thecorporate server.

ENG00041 A Teamcenter EDA User’s Guide A-1

Appendix A Glossary

D

DatasetTeamcenter Engineering workspace object used to manage data files created by othersoftware applications. Each dataset can manage multiple operating system files, andeach dataset references a dataset tool object and a dataset type object.

E

Engineering Translation Services (ETS)Integration of Translation Solution Toolkit (TSTK) and Teamcenter Engineering.ETS enables My Navigator users to translate CAD data files managed by TeamcenterEngineering to JT or CGM file format for viewing in either Teamcenter EngineeringVisualization or Teamcenter Visualization.

F

FolderGraphical representation of an aggregation of objects, such as a group, class, orsubclass. For easy distinction in the class hierarchy, each of these aggregations hasa different type of folder icon associated with it: a group folder icon, a class foldericon, or a subclass folder icon.

I

ItemWorkspace object generally used to represent a product, part, or component. Itemscan contain other workspace objects including other items and object folders.

Item RevisionWorkspace object generally used to manage revisions to items.

M

MetadataObject description in the Teamcenter Engineering database.

My NavigatorTeamcenter Engineering rich client application that is the main access point formanaging product information. My Navigator provides the functionality for creatingobjects in the Teamcenter Engineering database, querying the database for objects,checking in and checking out objects, and managing tasks. Users can also openobjects, automatically launching the related application.

Each user has a personal My Navigator window that displays product information asgraphical objects. Although users share product information across the enterprise,they organize this information individually in personal workspaces.

N

Naming RuleBusiness rule that defines the naming conventions for the string property value indifferent type objects. Naming rules can be attached to the following properties:

Item ID, item revision ID, and name in item types

A-2 Teamcenter EDA User’s Guide ENG00041 A

Glossary

Dataset name, ID, and revision number in dataset typesName form types

O

OwnerUser that owns an object, initially the user who created it. Ownership can betransferred from the owner to another user. An object owner usually has privilegesthat are not granted to other users (for example, the privilege to delete the object).

Owning GroupGroup that owns an object, usually the group of the user creating the object. Becauseusers commonly share data with other members of a group, additional privileges maybe granted to the owning group (for example, the privilege to write to the object).

P

PLM XMLUGS format for facilitating product life cycle interoperability using XML. PLM XMLis open and based on standard W3C XML schemas. Representing a variety of productdata both explicitly and via references, PLM XML provides a lightweight, extensible,and flexible mechanism for transporting high-content product data over the Internet.

PreferenceConfiguration variable stored in a Teamcenter Engineering database and read whena Teamcenter Engineering session is initiated. Preferences allow administrators andusers to configure many aspects of a session, such as user login names and thecolumns displayed by default in a properties table.

Product StructureHierarchy of assembly parts and component parts with a geometric relationshipbetween them, for example, a bill of materials (BOM). Variant and revision rulesdefine the generic BOM. This BOM can then be loaded to display the configuredvariant.

Product Structure EditorTeamcenter Engineering application that enables creation of generic productstructures that can be configured to show the product structure that is in production,effective on a certain date, used by a particular customer, and so forth. ProductStructure Editor enables creation and modification of a product structure and itsassociated occurrence data, display of a product structure in a multilevel indentedbill of materials (BOM) format, and viewing graphics tightly coupled to the structurefor easy identification of a component by location in the structure or in the graphicsviewer.

Product ViewSaved configuration of the assembly viewer, including the selection of objects, zoomfactor, rotation angle, and pan displacements.

R

RelationDescription of an association between a Teamcenter Engineering object and a pieceof information that describes or is related to the object.

ENG00041 A Teamcenter EDA User’s Guide A-3

Appendix A Glossary

Release StatusStatus associated with a workspace object when it is released through a workflowprocess.

Rich ClientJava-based user interface to Teamcenter Engineering installed on user workstations.The rich client accesses Teamcenter Engineering databases using a remote or localserver.

T

Teamcenter Engineering Application Root DirectoryDirectory location of the Teamcenter Engineering shared binary executables. TheIMAN_ROOT environment variable defines this location. Generally, the contents ofthis directory change only with a new version of Teamcenter Engineering.

Teamcenter Engineering Data DirectoryDirectory location of the Teamcenter Engineering shared data subdirectories andfiles. The IMAN_DATA environment variable defines this location. Each datadirectory is associated with a single database instance.

Thin ClientTeamcenter Engineering user interface that provides a streamlined browser-basedview of product information stored in a Teamcenter Engineering database. Thethin client is configured in the Web tier, which creates and serves its Web pagesto the client.

A-4 Teamcenter EDA User’s Guide ENG00041 A

Appendix

B Reference

Teamcenter EDA Data Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Teamcenter EDA Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

About the Staging Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

Mentor Graphics Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7Location Map Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7Released Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8Working Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9


Appendix

B Reference

This appendix provides background information about Teamcenter EDA.

Teamcenter EDA Data StructuresFigure B-1 illustrates the data structures utilized by Teamcenter EDA. The items inthe illustration represent physical files stored in EDA as well as nonphysical datastructures. The figure does not represent how ECAD tools store data.

BOM

EDA DesignArchive

PhysicalView

InterchangeView

SchematicView

FabricationPackage

BoardView

AssemblyPackage

Bare Board

Components

Schematic*.tar *.zip

Board*.tar *.zip

Combined*.tar *.zip

Physical*.prt

Physical*.jt

Transfer*.idf

Viewable*.eda Fabrication

Data

AssemblyData

Markup*.mrk

Markup*.mrk

Viewable*.eda

Circuit Board Assembly

Figure B-1. Overview of Teamcenter EDA Data Structures

ENG00041 A Teamcenter EDA User’s Guide B-1

Appendix B Reference

The design, or circuit card assembly, can be represented by the following datastructures:

• Bill of materials (BOM)

Includes the circuit board assembly, bare board, and related components. TheBOM is stored as relationships between objects.

• Teamcenter EDA design archive

Comprised of archive files in .tar or .zip format. The design archive containsnative ECAD data for the schematic, the board, or a combination of both. Thenative ECAD data is dependent on the ECAD tool used to create them.

• Physical and interchange views

Contain files that interface to tools. The .jt and .prt files are used forvisualization within the Teamcenter Engineering rich client. The .idf files areused for data transfer.

• Schematic and board views

Contain one or more viewable (.eda) or markup (.mrk) files that represent aschematic diagram or board view of the design.

• Fabrication and assembly packages

Contain data on the material used to fabricate the board, and instructions abouthow to assemble the board.

B-2 Teamcenter EDA User’s Guide ENG00041 A

Reference

Teamcenter EDA TypesIn the Teamcenter Engineering data model, types are the fundamental objects usedto model business data. Types are used to represent product parts, documents,change processes, and so on. The most commonly used type is the Item type, whichis often used to represent parts.

Table B-1 lists the types that Teamcenter EDA adds to the Teamcenter Engineeringdata model.

Table B-1. Types

Type Description Parent Type

EDA Represents an ECAD design. Item

EDAComp Represents a design component. EDA

EDASchem Represents a schematic drawing. EDA

In the Teamcenter Engineering data model, datasets are files. Dataset typesare different kinds of files, for example, text files, Word files, and so on. A tool(application) is associated with each file type.



Table B-2 lists the dataset types that Teamcenter EDA adds to the TeamcenterEngineering data model.

Table B-2. Dataset Types

Dataset Type Description Kind of File

EDAAsm Contains an assembly file thatdescribes how to assemble theboard.

ZIP file (*.zip)opened with UnZip.

EDACompCadBrd Contains a Cadence componentboard.


EDACompCadSch Contains a Cadence componentschematic.


EDACompMentor Contains a Mentor component. ZIP file (*.zip)opened with UnZip.

EDADesMentor Contains a Mentor design.Double-clicking this kind ofdataset file launches the MentorDesign Manager.


EDADesCadBrd Contains a Cadence boarddesign. Double-clicking this kindof dataset file launches CadenceAllegro PCB Design.


EDADesCadSch Contains a Cadence schematicdesign. Double-clicking this kindof dataset file launches CadenceAllegro Design Entry.


EDAIdf Includes an MCAD interchangefile that can be used for filetransfers between your ECADdesign tool and an MCADapplication. MCAD interchangefiles are in .idf format.


EDAView Contains a visualization file ofthe schematic.

Viewable file(*.eda) openedwith a viewer, likeInterComm.


Reference

About the Staging DirectoryTeamcenter EDA uses a staging directory for local storage of ECAD designs. Thissection explains why this staging directory exists.

Looking at staging directories in conjunction with how Teamcenter EDA performsa checkout action best describes the value of the staging directory. When a useraccesses a Teamcenter EDA browser, selects an ECAD object, and activates acheckout action, the Teamcenter EDA file services tools must know both a sourceand destination for the action. For the checkout, the source is where the data isstored within the Teamcenter EDA file system. This location is part of the metadatamaintained by Teamcenter Engineering. However, the destination is where the enduser wants the data dropped. Each user may want the destination to be in a differentphysical location. At a minimum, each workstation has a unique file system. For theTeamcenter EDA file system tools, the user must establish a fixed location knownto Teamcenter EDA for these files. This fixed location is defined at the time whenTeamcenter EDA is installed. The location is stored within a settings file that all ofthe Teamcenter EDA tools can access. Each user (each installation) specifies wherethe staging directory is defined for that user and host. The resulting action for acheckout from Teamcenter EDA is that the data source is a Teamcenter Engineeringserver, and the data destination is specified by the user’s staging directory setting ina Teamcenter EDA settings file. A different user can also checkout the same dataitems and the destination would be that user’s specified staging directory.

Alternatively, looking at how Teamcenter EDA performs a save action, the sourcecan be any location within the user’s file system and the destination would always bea Teamcenter EDA provided location within the Teamcenter Engineering server. Inpractice, this is not practical. A design may be contained within a single file for oneECAD product, while another ECAD product stores its design data within severalfiles. Many users want to have supplemental data included with the design files. Forexample, the user may want to add a readme file or add a specification documentto what Teamcenter EDA captures. To support this additional requirement,Teamcenter EDA is extended to expect that the design data that is to be managed isstored in an outer container. Any files or file objects that are in this container arecaptured when the ECAD tool executes a Teamcenter EDA Save or Save As action.Some ECAD products use hidden or invisible files to hold properties or metadatafor use by those ECAD products. Teamcenter EDA assumes that at a minimum,these hidden files are hidden within the directory that contains the design data.Additionally, Teamcenter EDA assumes that if multiple designs are all stored withincontainers inside of a common staging directory, there is the potential of namecollisions. To eliminate the potential of collisions, each directory that contains anECAD design is expected to be given a name that is unique. In fact, TeamcenterEDA requires the directory that contains the design to be given a name that isthe same as the design’s part number, or item ID in Teamcenter EDA terms. Therequirement to use this additional directory may seem unneeded at first, butprovides Teamcenter EDA with a reference point for all of its activities and providesa method for capturing supplemental or hidden ECAD files.



Any use of additional intermediary directories other than described here is notsupported and may cause broken Mentor references. For example, if a user wants togroup designs within project directories that are within the staging directory, the filesystem would see an arrangement such as this UNIX example:

/users/xyz/EDAStaging/mentor/projA/part123/designABC

This design would be checked in correctly, but would be checked out to the UNIXlocation:

/users/xyz/EDAStaging/mentor/part123/designABC

This path is where the data is checked out to, which is an unexpected location. Thereferences within the design would be expecting the location to be where it was whenchecked in. The checkout action always places the design directly at the location of:

/users/xyz/EDAStaging/mentor

rather than:

/users/xyz/EDAStaging/mentor/projA

The use of Mentor location map entries modifies this example.


Reference

Mentor Graphics ReferenceThis section contains Mentor Graphics reference information specific to the use ofTeamcenter EDA.

Location Map Usage

The Mentor Graphics Board Station products support a wide range of PCB designcreation and analysis. To support the many tools that Mentor offers and interfaceswith, the data files are very complex. Board Station alone support hundreds ofdifferent data types. To efficiently follow data files from one product to another,Mentor has chosen to embed references to supporting files within its data files.Rather than look up the destination of referenced data, full path information isincluded within various design files.

Having files containing path information is good for performance until a design getsmoved either intentionally or by accident. Moving data in a manner where thedestination of a reference is no longer valid leads to broken references and thereforebroken designs. Mentor incorporates in its Design Manager tool a set of functionsthat can search out broken references and repair them (with manual intervention).The Teamcenter EDA product must support Mentor data management in a way thatthese references are not broken when the designs are moved.

For its part, Mentor also wants its customers to be able to move or retarget designswithout breaking the references. To this end, the Mentor Graphics products containa provision for creating and maintaining paths and references by the use of symbolicnames instead of absolute file system paths. As long as the symbolic name canultimately be transformed into an absolute path, the design stays valid.

To support the use of symbolic paths, Mentor provides a location map facility. Inthe location map, each symbolic name is mapped to one or more file system paths.Nested symbolic values can be combined such that an absolute path is the finalresult. Location map mapping files can appear as user, workstation, project, andcorporate definitions, as well as others.

When a symbolic name is encountered during Mentor tool usage and a referenceneeds to be resolved, the available location maps are scanned to produce a finalpath value. When a physical path is encountered, it typically is converted to asymbolic value for convenience or for portability considerations. This again is donevia references to the available locations maps.

During the Teamcenter Engineering management of Teamcenter EDA design data,it is expected that all Teamcenter EDA data is staged into and out of the definedstaging folder. Because a user can check out a design that was created and saved ona different workstation and with a different physical location for the staging folder,Teamcenter EDA requires all users of Teamcenter EDA to define a common symbolicvalue for their staging folder. The name of the symbolic value is not critical, but toprovide a name that is common across all Teamcenter EDA users, it is proposed thatthe location map entry for the staging folder be named $TcEda_Staging.



A typical Mentor location map file from a Windows system looks similar to thefollowing:

MGC_LOCATION_MAP_2

#corp geoms$corp_geomsc:/users/abc/mti_data/approved/corp_geomsc:\users\abc\mti_data\approved\corp_geoms

# TcEng - TcEda Staging Directory$TcEda_Stagingc:/ecad/EDAStagingc:\ecad\EDAStagingc:/ecad/EDAStagingc:\ecad\EDAStagingc:\\ecad\\EDAStaging

A typical Mentor location map file from a UNIX system looks similar to the following:

MGC_LOCATION_MAP_2

#corp geoms$corp_geoms/users/abc/mti_data/approved/corp_geoms

# TcEng - TcEda Staging Directory$TcEda_Staging/ecad/EDAStaging

Released Attribute

Mentor Graphics tools support a Mentor defined attribute called Released. Thisattribute, in part, is used to signal to other Mentor tools that the target design hasbeen released. This is defined to be whatever the user intends it to be. When theReleased attribute is applied to a Mentor design object, that object and all containedobjects are blocked from future modification. The block is interpreted within the toolsand is not a file system attribute. The only way that the object can be modified is ifthe object is copied to a new location and given a new object name. Refer to MentorGraphics documentation for additional information about the Released attribute.

Teamcenter Engineering does not read the value of the Released attribute nor doesit take any actions based on the value of the attribute. If a Released design ischecked in to Teamcenter Engineering and then checked out for modification, theMentor tools are blocked from writing to the object, unless it is moved and renamed.


Reference

Working Directory

The Mentor Graphics Design Manager tool expects the user to set an environmentvariable (MGC_WD) to point to where the user’s Mentor design object browserstarting point is. In the case of Teamcenter Engineering and Teamcenter EDA,the variable points to:

staging-directory/mentor

To prevent the Mentor user from having to configure one more item during theTeamcenter EDA installation, the Teamcenter EDA provided launching scriptfor the Mentor Design Manager includes code that sets the environment variableMGC_WD to point to:

staging-directory/mentor


Index

A

Adobe Acrobat Reader . . . . . . . . . . . . . . . 9AIWS . . . . . . . . . . . . . . . . . . . . . . 1-4, 1-11allegro.ilinit file . . . . . . . . . . . . . . . . . 1-16allegro.men file . . . . . . . . . . . . . . . . . . 1-16Architecture of Teamcenter EDA . . . . . . 2-3Audience for the manual . . . . . . . . . . . . . 5

B

BOMCreation . . . . . . . . . . . . . . . 3-4–3-5, 3-9Templates . . . . . . . . . . . . . . . . . 3-12, 5-2

BOM Option Default preference . . . . . . 3-12

C

CacheDirectory . . . . . . . . . . . . . . . . . . . . . 1-18Location . . . . . . . . . . . . . . . . . . . . . 1-11Purging . . . . . . . . . . . . . . . . . . . . . . 3-11Refreshing . . . . . . . . . . . . . . . . . . . . 3-11

CadenceAllegro or Concept . . . . . . . . . . . . . . . 2-1Design Entry HDL . . . . . . . . . . . . . . 3-13README.txt files . . . . . . . . . . . . . . 1-16Teamcenter menu . . . . . . . . . . . . . . 1-16Version . . . . . . . . . . . . . . . . . . . . . . . 1-3

Cadence support feature . . . . . . . . . . . 1-10Cadence Translation Support feature . . . 1-8Cancel Check-Out menu option . . . . 2-4, 3-8Check-In menu option . . . . . . . . . . . 2-4, 3-9Check-In Option Default preference . . . 3-12Check-Out menu option . . . . . . . . . . 2-4, 3-7Code conventions . . . . . . . . . . . . . . . . . . 7Command line entry conventions . . . . . . . 7concepthdl_cmd.txt file . . . . . . . . . . . . 1-17concepthdl_menu.txt file . . . . . . . . . . . 1-17concepthdl.scr file . . . . . . . . . . . . . . . . 1-17Connection problems . . . . . . . . . . . . . . . 4-1Conventions

Caution icons . . . . . . . . . . . . . . . . . . . . 6Code . . . . . . . . . . . . . . . . . . . . . . . . . . 7Command line entries . . . . . . . . . . . . . 7

File contents . . . . . . . . . . . . . . . . . . . . 7Names . . . . . . . . . . . . . . . . . . . . . . . . 6Note icons . . . . . . . . . . . . . . . . . . . . . . 6Revisions . . . . . . . . . . . . . . . . . . . . . . 6Syntax definitions . . . . . . . . . . . . . . . . 8Values . . . . . . . . . . . . . . . . . . . . . . . . . 6Warning icons . . . . . . . . . . . . . . . . . . . 6

Customizing Teamcenter EDA . . . . . . . . 5-1

DDataset

Names . . . . . . . . . . . . . . . . . . . . . . . 3-6Types . . . . . . . . . . . . . . . . . . . . . . . B-4

Default Save As Folder preference . . . . 3-12Documentation . . . . . . . . . . . . . . . . . . . . 9

Online help . . . . . . . . . . . . . . . . . . . . . 9Organization . . . . . . . . . . . . . . . . . . . . 5Printable files . . . . . . . . . . . . . . . . . . . 9

E.eda files . . . . . . . . . . . . . . . . 1-5, 1-19, 3-13EDA Server Support feature . . . . . . . . . 1-8EDA Standalone Client feature . . . . . . 1-10EDAComp type . . . . . . . . . . . . . . . 1-9, B-3EDASchem type . . . . . . . . . . . . . . 1-9, B-3Engineering Translation Services (ETS)installation . . . . . . . . . . . . . . . . . . . . . 1-8

Environment variablesFMS_HOME . . . . . . . . . . . . . . . . . . 1-12icmhome . . . . . . . . . . . . . . . . . . . . . . 1-5JAVA_HOME . . . . . . . . . . . . . . . . . . 1-14TCEDAECAD_ROOT . . . . . . . . . . . . 1-12

Errors . . . . . . . . . . . . . . . . . . . . . . . . . 4-1ets_create_rqst.exe file . . . . . . . . . . . . 1-20

FFCC client . . . . . . . . . . . . . . . . . . . . . 1-12fcc_only file . . . . . . . . . . . . . . . . . . . . . 1-12fcc.xml file . . . . . . . . . . . . . . . . . . 1-12, 5-3File contents conventions . . . . . . . . . . . . . 7FMS services . . . . . . . . . . . . . . . . . . . 1-12FMS_HOME environment variable . . . . 1-12

ENG00041 A Teamcenter EDA User’s Guide Index-1

Index

Four-tier architecture . . . . . . . . . . . . . . 1-4

GGetting started with Teamcenter EDA . . 2-1

HHardware requirements . . . . . . . . . . . . . 1-2Home folder is empty . . . . . . . . . . . . . . . 4-1

Iicmhome environment variable . . . . . . . . 1-5Icon conventions . . . . . . . . . . . . . . . . . . . 6Installation directory . . . . . . . . . . . 1-8, 1-10Installing

Cadence support . . . . . . . . . . . . . . . 1-10Cadence translation support . . . . . . . . 1-8EDA server support . . . . . . . . . . . . . . 1-8EDA standalone client . . . . . . . . . . . 1-10Engineering Translation Services

(ETS) . . . . . . . . . . . . . . . . . . . . . . 1-8FCC client . . . . . . . . . . . . . . . . . . . . 1-12InterComm . . . . . . . . . . . . . . . . . . . . 1-5Markup support . . . . . . . . . . . . . . . . 1-10Mentor support . . . . . . . . . . . . . . . . 1-10Mentor translation support . . . . . . . . . 1-8Perl . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Server Manager . . . . . . . . . . . . . . . . . 1-8Teamcenter EDA . . . . . . . . . . . . . 1-1, 1-7Teamcenter EDA client . . . . . . . . . . . 1-10Teamcenter EDA server . . . . . . . . . . . 1-7Teamcenter Engineering . . . . . . . . . . . 1-4Translation Solution Toolkit . . . . . . . . 1-5

InterCommInstalling . . . . . . . . . . . . . . . . . . . . . 1-5Launching from Teamcenter

Engineering . . . . . . . . . . . . . . . . 3-13Licensing . . . . . . . . . . . . . . . . . . . . . 1-6Version . . . . . . . . . . . . . . . . . . . . . . . 1-3

Introduction to Teamcenter EDA . . . . . . 2-1Item Info menu option . . . . . . . . . . 2-4, 3-10

JJAVA_HOME environment variable . . . 1-14

LLicensing InterComm . . . . . . . . . . . . . . 1-6Location maps . . . . . . . . . . . . . . . . . . B-7Logging in to Teamcenter EDA . . . . . . . . 3-2Login menu option . . . . . . . . . . . . . . . . 3-2Logout menu option . . . . . . . . . . . . 2-5, 3-13

MManual organization . . . . . . . . . . . . . . . . 5Manual set . . . . . . . . . . . . . . . . . . . . . . . 9Markup Support feature . . . . . . . . . . . 1-10Mentor Graphics

Board Station . . . . . . . . . . . . . . . . . . 1-3Design Manager . . . . . . . . . . . . . . . . 2-1Teamcenter menu . . . . . . . . . . . . . . 1-14Version . . . . . . . . . . . . . . . . . . . . . . . 1-3

Mentor Support feature . . . . . . . . . . . . 1-10Mentor Translation Support . . . . . . . . . . 1-8MGC_WD environment variable . . . . . . B-9mti_dmgr command . . . . . . . . . . . . . . 1-15

NName conventions . . . . . . . . . . . . . . . . . . 6No route available for Enterprise error . . 4-2

OOnline help . . . . . . . . . . . . . . . . . . . . . . . 9Open menu option . . . . . . . . . . . . . . 2-4, 3-6Organization of the manual . . . . . . . . . . . 5Overview

Installation . . . . . . . . . . . . . . . . . . . . 1-1Teamcenter EDA . . . . . . . . . . . . . . . . 2-1

PPerl

Installing . . . . . . . . . . . . . . . . . . . . . 1-6Version . . . . . . . . . . . . . . . . . . . . . . . 1-3

Preferences . . . . . . . . . . . . . . . . . . . . . 3-12Menu option . . . . . . . . . . . . . . . . . . . 2-5Setting . . . . . . . . . . . . . . . . . . . . . . . 5-1

Prerequisite applications . . . . . . . . . . . . 1-4PTC . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Purge Cache menu option . . . . . . . 2-4, 3-11

RREADME.txt files for Cadence . . . . . . . 1-16Refresh menu option . . . . . . . . . . . 2-4, 3-11Released attribute . . . . . . . . . . . . . . . . B-8Requirements, system . . . . . . . . . . . . . . 1-2Revision conventions . . . . . . . . . . . . . . . . 6

SSave

Error . . . . . . . . . . . . . . . . . . . . . . . . 4-3Menu option . . . . . . . . . . . . . . . . . . . 2-4

Save As menu option . . . . . . . . . . . . 2-4, 3-3Save is not allowed error . . . . . . . . . . . . 4-3

Index-2 Teamcenter EDA User’s Guide ENG00041 A

Index

Save menu option . . . . . . . . . . . . . . . . . 3-5Save Secondary Data menu option . . 2-4, 3-5Saving designs . . . . . . . . . . . . . . . . . . . 3-3Schematic BOM Template preference . . 3-12Server installation . . . . . . . . . . . . . . . . 1-7Server Manager feature . . . . . . . . . . . . . 1-8Software requirements . . . . . . . . . . . . . 1-2Staging

Directory . . . . . . . . . . . . . . 1-18, 2-6, B-5Location . . . . . . . . . . . . . . . . . . . . . 1-11

startCDSDesignEntryHdl.bat file . . . . . 3-13Syntax definition conventions . . . . . . . . . . 8System requirements . . . . . . . . . . . . . . 1-2

Ttc.ear file . . . . . . . . . . . . . . . . . . . . . . . 1-4TCEDAClient.properties file . . 1-13, 3-2, 5-3TCEDAECAD_ROOT environmentvariable . . . . . . . . . . . . . . . . . . . . . . 1-12

tcEdaPcbTemplate.bom file . . . . . . . . . . 5-2tcEdaSchTemplate.bom file . . . . . . . . . . 5-2Teamcenter EDA

Architecture . . . . . . . . . . . . . . . . . . . 2-3Cache directory . . . . . . . . . . . . . . . . 1-18Client . . . . . . . . . . . . . . . . . . . . . . . 1-10Components . . . . . . . . . . . . . . . . . . . 2-2Customizing . . . . . . . . . . . . . . . . . . . 5-1Data structures . . . . . . . . . . . . . . . . B-1Getting started . . . . . . . . . . . . . . . . . 2-1Installing . . . . . . . . . . . . . . . . . . 1-1, 1-7Introduction . . . . . . . . . . . . . . . . . . . 2-1Logging in . . . . . . . . . . . . . . . . . . . . . 3-2

Preferences . . . . . . . . . . . . . . . . . . . 3-12Server . . . . . . . . . . . . . . . . . . . . . . . . 1-7Staging directory . . . . . . . . . . . . . . . 1-18Types . . . . . . . . . . . . . . . . . . . . . . . B-3Using . . . . . . . . . . . . . . . . . . . . . . . . 3-1Workflow . . . . . . . . . . . . . . . . . . . . . . 2-5

Teamcenter EngineeringInstalling . . . . . . . . . . . . . . . . . . . . . 1-4Version . . . . . . . . . . . . . . . . . . . . . . . 1-3

Teamcenter Environment Manager . . . . 1-7,1-10

Teamcenter menu . . . . . . . . . . 1-14, 2-4, 3-1TEM.js file . . . . . . . . . . . . . . . . . . 1-7, 1-10Templates, BOM . . . . . . . . . . . . . . 3-12, 5-2Translation Solution Toolkit

Installing . . . . . . . . . . . . . . . . . . . . . 1-5Version . . . . . . . . . . . . . . . . . . . . . . . 1-3

translator.xml file . . . . . . . . . . . . . . . . 1-19transmodule.xml file . . . . . . . . . . . . . . 1-19Troubleshooting . . . . . . . . . . . . . . . . . . 4-1Types for Teamcenter EDA . . . . . . . . . B-3

VValue conventions . . . . . . . . . . . . . . . . . . 6Viewable files . . . . . . . . . . . . 1-5, 1-19, 3-13Visualization

InterComm . . . . . . . . . . . . . . . . . 1-3, 1-5Translation Solution Toolkit . . . . . . . . 1-5

WWorkflow of Teamcenter EDA . . . . . . . . . 2-5

ENG00041 A Teamcenter EDA User’s Guide Index-3

ed a user guide

Documents