04.12.2012 Views

Windchill System Administrator's Guide

Windchill System Administrator's Guide

Windchill System Administrator's Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

• It has the same name or the name is mapped to a local name, as well as<br />

mapped to the same parent type, unless this type is a root-level type. The<br />

names of hard types cannot be changed.<br />

• It has the same values for the following attributes: instantiable,<br />

userAttributeable, deleted.<br />

• The two types have the same number of attribute.<br />

• The two types have the same set of soft attributes. Two soft attributes are<br />

considered the same if they are of the same IBA type have the same value.<br />

• The two types have the same set of constraints on their attributes as well as<br />

the same set of constraints on the soft type itself.<br />

If a Type matching the above criteria is found in the system, it must be visible to<br />

the context into which the import is being performed.<br />

Organization Level Container Availability<br />

The import action is available to the Organization or Site administrator. Folder<br />

contents can be imported into an organization context. Type Definitions can be<br />

mapped to locally defined type definitions.<br />

Site Level Container Availability<br />

The import action is available to the Site administrator. Folder contents can be<br />

imported into a Site context. Type Definitions can be mapped to locally defined<br />

type definitions.<br />

Controlling the Destinations of Imported Objects with Context Mapping Files<br />

The preceding sections discussed working contexts, which correspond to logical<br />

entities called containers, within which the software organizes objects. The<br />

containers separate objects in different working contexts. The following are<br />

examples of containers:<br />

• Each installation of <strong>Windchill</strong> PDM has a different context from others, so<br />

each <strong>Windchill</strong> Foundation installation has its own ClassicContainer.<br />

• In <strong>Windchill</strong> ProjectLink, each project has a different context from other<br />

projects, so each project is its own Project Context.<br />

• Each organization has a different context from others, so each organization<br />

has its own OrgContainer. For <strong>Windchill</strong> PDMLink the namespace that is<br />

used is the Site level, and for <strong>Windchill</strong> ProjectLink the namespace that is<br />

used is the Organization level.<br />

In light of the preceding examples, you can expect objects exported from the<br />

context of a system, project, or organization to be present after import in new<br />

contexts within the system to which they were imported.<br />

6-6 <strong>Windchill</strong> <strong>System</strong> Administrator’s <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!