This manual describes backup and recovery features of Teamcenter® Engineering.
Teamcenter Engineering belongs to the UGS® portfolio of digital product lifecycle
management software and services.
This manual contains the following chapters:
Chapter 1 Integrated Backup describes Teamcenter Engineering integrated
backup and recovery.
Chapter 2 Single File Recovery (SFR) describes Teamcenter Engineering
single file recovery.
Chapter 3 Recovery Management Backup Recommendation describes
recommendations for recovery backup management.
Chapter 4 Installing and Using the Cold Backup and Restore Utility
describes the planning, installation, and usage of the Teamcenter
Engineering Backup and Restore Utility.
Chapter 5 Using the Teamcenter Hot Backup and Recovery Utility describes
the planning, installation, and usage of the Teamcenter
Engineering Backup and Recovery Utility.
10/15/2009
Teamcenter AutoCAD Integration
http://www.cadfamily.com/downinfo/292148.html
Managing your files with Teamcenter Engineering ensures that data can only be
modified by one user at a time. Write access is gained by checking the file out of the
Teamcenter Engineering database. To relinquish access, you must either cancel the
checkout and lose any modifications you have made to the file, or check the file
back in to the database.
The standard AutoCAD file commands are also available in Teamcenter 2005
Integration for AutoCAD. These commands store files locally, rather than in the
Teamcenter Engineering database; however, there are no restrictions preventing you
from using both AutoCAD and Teamcenter 2005 Integration for AutoCAD commands.
When you save an AutoCAD file in Teamcenter Engineering, Teamcenter 2005
Integration for AutoCAD automatically saves any files that are dependent on
the saved file. For example, if you save an AutoCAD assembly in Teamcenter
Engineering, Teamcenter 2005 Integration for AutoCAD automatically saves all
component parts and subassemblies before saving the assembly file.
Teamcenter 2005 Integration for AutoCAD Help illustrates the use of the Teamcenter
2005 Integration for AutoCAD and assumes that you are familiar with AutoCAD
concepts and usage.
Managing your files with Teamcenter Engineering ensures that data can only be
modified by one user at a time. Write access is gained by checking the file out of the
Teamcenter Engineering database. To relinquish access, you must either cancel the
checkout and lose any modifications you have made to the file, or check the file
back in to the database.
The standard AutoCAD file commands are also available in Teamcenter 2005
Integration for AutoCAD. These commands store files locally, rather than in the
Teamcenter Engineering database; however, there are no restrictions preventing you
from using both AutoCAD and Teamcenter 2005 Integration for AutoCAD commands.
When you save an AutoCAD file in Teamcenter Engineering, Teamcenter 2005
Integration for AutoCAD automatically saves any files that are dependent on
the saved file. For example, if you save an AutoCAD assembly in Teamcenter
Engineering, Teamcenter 2005 Integration for AutoCAD automatically saves all
component parts and subassemblies before saving the assembly file.
Teamcenter 2005 Integration for AutoCAD Help illustrates the use of the Teamcenter
2005 Integration for AutoCAD and assumes that you are familiar with AutoCAD
concepts and usage.
Application Integration Environment engineering process management
http://www.cadfamily.com/downinfo/292147.html
The Application Integration Environment (AIE) provides the framework and
common functions required to integrate applications with Teamcenter. This
framework consists of three components: Encapsulation Manager, Remote Manager,
and Supplier Manager.
Encapsulation Manager enables a multiple push-and-pull environment for
encapsulated applications. Remote Manager enables users to work offline and then
synchronize data with the Teamcenter database. Supplier Manager enables users to
manage data sharing between their enterprise and its suppliers.
The Application Integration Environment (AIE) provides the framework and
common functions required to integrate applications with Teamcenter. This
framework consists of three components: Encapsulation Manager, Remote Manager,
and Supplier Manager.
Encapsulation Manager enables a multiple push-and-pull environment for
encapsulated applications. Remote Manager enables users to work offline and then
synchronize data with the Teamcenter database. Supplier Manager enables users to
manage data sharing between their enterprise and its suppliers.
Security Services Release Notes in Teamcenter
http://www.cadfamily.com/downinfo/292237.html
UGS encourages customers to stay reasonably current with new releases of
Teamcenter products. This upgrade strategy ensures that users obtain the most
current announcements and information about new features in a timely manner. It
also allows UGS’s support of its products to be consistent with that of our dependent
technology partners (that is, operating systems, databases, and embedded software
products).
For a list of supported Teamcenter releases, search GTAC for the Product Support
Periods document.
UGS encourages customers to stay reasonably current with new releases of
Teamcenter products. This upgrade strategy ensures that users obtain the most
current announcements and information about new features in a timely manner. It
also allows UGS’s support of its products to be consistent with that of our dependent
technology partners (that is, operating systems, databases, and embedded software
products).
For a list of supported Teamcenter releases, search GTAC for the Product Support
Periods document.
Rich Client Framework in Teamcenter
http://www.cadfamily.com/downinfo/292236.html
This chapter describes the following topics:
• Establishing Teamcenter sessions
• Launching applications
• Using the Teamcenter rich client windows
• Using dialog window elements
• Using shortcut menus
• Expanding application groups
• Setting information center options
• Opening new default application windows
• Viewing help
• Closing applications
• Exiting Teamcenter sessions
This chapter describes the following topics:
• Establishing Teamcenter sessions
• Launching applications
• Using the Teamcenter rich client windows
• Using dialog window elements
• Using shortcut menus
• Expanding application groups
• Setting information center options
• Opening new default application windows
• Viewing help
• Closing applications
• Exiting Teamcenter sessions
Rich Client Customization Programmer Guide
http://www.cadfamily.com/downinfo/292235.html
UGS is committed to maintaining compatibility between Teamcenter
product releases. If you customize functions and methods using published
APIs and documented extension points, be assured that the next successive
release will honor these interfaces. On occasion, it may become necessary to
make behaviors more usable or to provide better integrity. Our policy is to
notify customers at the time of the release prior to the one that contains a
published interface behavior change.
UGS does not support code extensions that use unpublished and
undocumented APIs or extension points. All APIs and other extension
points are unpublished unless documented in the official set of technical
manuals and help files issued by UGS Technical Communications.
The Teamcenter license agreements prohibit reverse engineering, including:
decompiling Teamcenter object code or bytecode to derive any form of the
original source code; the inspection of header files; and the examination of
configuration files, database tables, or other artifacts of implementation.
UGS does not support code extensions made using source code created from
such reverse engineering.
If you have a comment or would like to request additional extensibility,
contact the UGS customer support representatives at GTAC for further
assistance.
UGS is committed to maintaining compatibility between Teamcenter
product releases. If you customize functions and methods using published
APIs and documented extension points, be assured that the next successive
release will honor these interfaces. On occasion, it may become necessary to
make behaviors more usable or to provide better integrity. Our policy is to
notify customers at the time of the release prior to the one that contains a
published interface behavior change.
UGS does not support code extensions that use unpublished and
undocumented APIs or extension points. All APIs and other extension
points are unpublished unless documented in the official set of technical
manuals and help files issued by UGS Technical Communications.
The Teamcenter license agreements prohibit reverse engineering, including:
decompiling Teamcenter object code or bytecode to derive any form of the
original source code; the inspection of header files; and the examination of
configuration files, database tables, or other artifacts of implementation.
UGS does not support code extensions made using source code created from
such reverse engineering.
If you have a comment or would like to request additional extensibility,
contact the UGS customer support representatives at GTAC for further
assistance.
Installation On UNIX and Linux Clients
http://www.cadfamily.com/downinfo/292234.html
Teamcenter Engineering 2005 SR1 supports the rich client on the following
operating systems:
• Hewlett-Packard HP-UX 11.0 and 11.i (11.11)
PA-RISC 1.1 is not supported.
• IBM AIX 5.1, 5.2, and 5.3
On IBM AIX hosts only, run the rootpre.sh script on the CD-ROM mount point,
as root user in a shell window.
$ /cdrom_mount_point_directory/rootpre.sh
This script configures the AIX Asynchronous I/O and Oracle Post-Wait Kernel
Extension.
• Sun Solaris 8 12/02, 9, and 10
• Novell Linux Desktop 9.0 SP2 and SUSE Linux Enterprise Server 9.0 SP1
The listed operating system versions are the minimum versions required to run
the software. Consult with the Global Technical Access Center (GTAC) regarding
compatibility with other operating system versions.
Teamcenter Engineering 2005 SR1 supports the rich client on the following
operating systems:
• Hewlett-Packard HP-UX 11.0 and 11.i (11.11)
PA-RISC 1.1 is not supported.
• IBM AIX 5.1, 5.2, and 5.3
On IBM AIX hosts only, run the rootpre.sh script on the CD-ROM mount point,
as root user in a shell window.
$ /cdrom_mount_point_directory/rootpre.sh
This script configures the AIX Asynchronous I/O and Oracle Post-Wait Kernel
Extension.
• Sun Solaris 8 12/02, 9, and 10
• Novell Linux Desktop 9.0 SP2 and SUSE Linux Enterprise Server 9.0 SP1
The listed operating system versions are the minimum versions required to run
the software. Consult with the Global Technical Access Center (GTAC) regarding
compatibility with other operating system versions.
Subscribe to:
Posts (Atom)