Working with Containers
Your installed Windchill environment consists of a set of containers that hold all of the administrative areas (known as domains), rules, and data that make up the context from which Windchill users work. Throughout the user interface, Context is used to identify where specific rules, domains, and data reside in the framework. However, to create this environment, you load containers. Because container is the label you see in the code, this topic collection uses the term container (rather than context).
There are three levels of containers: site, organization, and application contexts. After installing Windchill, it is recommended that you load demo data to ensure that the system is working. The Windchill Loader is used to load this data.
For more information about the Windchill Loader, see the Windchill Installation and Configuration Guide (Windchill Installations- und Konfigurationshandbuch).
By default, the Windchill Loader creates the following containers:
• site container
• organization container
These containers are nested and create a hierarchy (that is, the organization container exists within the site container). The Windchill Loader only creates one of each container.
Containers in Your Windchill Solution
Depending on whether your solution includes projects or includes products and libraries, there are minor differences in how the hierarchy must look. To load data into the appropriate container, you must be aware of the differences in the hierarchy. Data files must be prepared to load into the appropriate container. A separate file for each container is required, and the container must be specified in the LoadFromFile command.
 |
Once all objects are loaded, you can load the structure separately using the AssemblyAddLoad tag.
|
Hierarchy that Includes Products and Libraries
Site container
• Organization container
◦ Product containers
◦ Library containers
▪ Documents
In the hierarchy, there is a single site container and a single organization container when the solution is installed. You may create additional organization containers.
Within each organization container, there may be product and library containers. Business-level objects such as parts, documents, and CAD documents can be loaded into the product or library containers.
Multiple product containers can exist in one load file. Product containers belong to an organization, so when calling the load utility, you must specify the proper organization.