the owning organization. Therefore, any subtypes you create from within the initial organization context become site-level subtypes because the owning organization is the same.

To have subtypes created in an organization context that do not be come available as site-level subtypes, the context from which the subtypes are created cannot be the initial organization context created during the installation.

Note

With Windchill PDMLink, the installer can install demo data. As part of the demo data installation, the Demo organization context is created and the Demo user is created as the organization administrator. As is the case for all organization contexts, the Demo organization context inherits rules and data from the site context, but the Demo organization does not have the same owning organization as the site context or the initial organization context.

You can create additional organization contexts. PTC recommends that if you are considering using multiple organization contexts in the future, you should create at least one additional organization context in which to create your products, libraries, projects, or programs, rather than creating them within the initial organization context. This allows you to add additional organizations (participants and contexts) without having to restructure your administrative data so that members of one organization cannot see data from another organization.

Establishing Administrators

Before you attempt to use your Windchill solution, you should establish a minimum set of administrators for the solution. The types of administrators that are available are determined by the Windchill solutions that are installed.

The Administrators group is defined in every installed Windchill solution. Initially, the administrative user entered during installation (for example, wcadmin) is the only member. Out of the box, the members of the Administrators group have full control over all Windchill objects and are commonly called the system or site administrators.

Best Practice

If you want to use a site administrator to manage contexts or teams, you should create a second site administrator for these tasks to improve Windchill performance. For more information, see Establishing Site Administrators on page 133 .

The additional types of administrators available are:

•An organization administrator manages a specific organization.

•A product manager manages a specific product (for Windchill PDMLink, Arbortext Content Manager, Pro/INTRALINK).

•A library manager manages a specific library (for Windchill PDMLink, Arbortext Content Manager, Pro/INTRALINK).

•A project manager manages a specific project (for Windchill ProjectLink).

•A program manager manages a specific program (for Windchill ProjectLink).

•A shared team manager manages a specific shared team and has management privileges for any context using the shared team.

In the out-of-the-box configuration, there are two LDAP directory service nodes. Administrative users reside in the Administrative LDAP node. For more information about the LDAP services, see Working with LDAP Directory Services on page 255 .

Note

For notification email messages to be sent, some mail servers require that a valid email address be specified in the From header of the email message. Windchill solutions use the wt.mail.from and wt.notify. notificationSenderEmail properties in the wt.properties file to populate the From header when sending email messages. Setting these properties to a valid Windchill user should have been done as a manual step after installing your solution. If this was not done, see the PTC Windchill Installation and Configuration Guide for details on how to set these properties to the email address of the Windchill administrator or some other authorized user.

The site administrative user (as defined by the Administrators group) can use the links that are under Site and Organizations .

Selecting Site Administrators displays the Site Administrators table. From this table, you can add users to the Administrators group.