-u wcadmin -p wcadmin

To import the exported table views, use the Import/Export Management utility. For more information, see Working with the Import/Export Management Utility in the PTC Windchill Help Center.

Managing Arbortext Editor Installation Bundles

Before Arbortext Editor can be downloaded by users from the PTC server, Arbortext Editor installation bundles must be made available from the user’s Software Downloads page. To accomplish this, an Arbortext section must be added to the Software Downloads page, and Arbortext Editor installation bundles be made available for download. Available installation bundles can later be updated or removed from the Software Downloads page. Only site administrators can perform these tasks.

An installation bundle is an executable file (.exe) approximately 60 MB in size that is created using the Arbortext Editor Deployment Kit. For more information, see the Arbortext Editor Deployment Kit Guide, available from your Arbortext Editor Help Center.

Adding the Arbortext Section to the Software Downloads Page

To add the Arbortext section to the user’s Software Downloads page, use the following procedure:

1.Open a windchill shell.

2.Run the following command:

cd bin

3. Run the following command:

ant -f setupAE.xml enableSoftwareDownloads

4.When prompted to authenticate, provide the username and password of a user with site administration privileges.

When any user now views their Software Downloads page, an Arbortext section appears. A message displays indicating that no downloads are available at this time.

Running this command also creates the Arbortext Downloads folder in the Site

Folders table.

Making Arbortext Editor Installation Bundles Available For Download

To make an Arbortext Editor installation bundle available for download, use the following procedure:

1.Navigate to Site Folders.

2.From the Folders table, select the Arbortext Downloads folder and click New Document to upload the installation bundle as a Windchill document. (The

Arbortext Downloads folder is automatically created when the command in the previous section is run.)

3.On the New Document window, specify the following information in the appropriate fields:

• Name—Enter the text that you want displayed to users on their Software

Downloads page. As a best practice, include the Arbortext Editor version (including the datecode) and indicate whether the bundle is targeted for a specific user community. For example: “Arbortext Editor 5.4 M020 for the Engineering Group”.

•Local File Path—use the exact file name of the installation bundle as

provided by Arbortext information architect.

•Location—ensure that the location is the Arbortext Downloads folder.

Accept the defaults or follow your company’s best practices to fill in the other fields.

4. Click OK.

After a short delay, the installation bundle will appear as a hyperlink under the

Arbortext section on the user's Software Downloads page.

More than one installation bundle can be available for download.

Updating Arbortext Editor Installation Bundles

When an update to an installation bundle is received from the Arbortext information architect, a site administrator can update the installation bundle using either the Replace Content or the Check Out and Edit action for the document. Only the latest iteration of the document is displayed on the Software Downloads page, along with the last updated date.

Note

If the document containing the installation bundle is checked out, the installation bundle does not display on the Software Downloads page.

Keep in mind the following best practices when updating installation bundles:

•Use the check-in comments to indicate who provided the new installation bundle iteration, when it was received, and so on. These comments are visible on the information page for the document, where they provide useful information for the administrator. The comments are not visible on the user's

Software Downloads page.

•If the disk space used by each iteration of an installation bundle (approximately 60MB) is a concern, use the Delete Non-latest Iterations action to remove previous iterations.

Removing an Installation Bundle From the Software Downloads Page

To remove an installation bundle from the Software Downloads page, making it unavailable to users, use one of the following options:

•Use the Delete action on the document containing the installation bundle. The document is deleted from the Arbortext Downloads folder, and is no longer available to users.

•Revert to a previous version of the document by downloading the desired iteration, and checking it in as the new latest iteration.

•Change the lifecycle state of the document to Canceled. The document remains in the Arbortext Downloads folder, but is no longer displayed on the user's Software Downloads page. This option is useful for retaining a record of installation bundles used, or for retaining the installation bundle for future use.

Managing Overall System Configuration

There are many system configuration settings you can view, set, and update remotely using the system configuration utilities. Use these utilities to view and set system properties, view and manage queues, and view server status and logs.

For more information, see the PTC Windchill Specialized Administration Guide and the PTC Windchill Enterprise Administration Guide.

Making Program Contexts Visible

By default, programs are hidden. To make programs visible and available for use in your Windchill solution, a you can set the value of the

preference to “No”. This preference is available from the

utility on Site Utilities. For more information on managing preferences, see the help available from the Preference Management utility.

Administering the Windchill Mobile App

Note

The Windchill mobile app requires a separate license. Ensure that your site has purchased this license before continuing.

A site administrator must configure the Windchill mobile app to connect it to the site's Windchill data. The configuration steps are described in the following topic in the Windchill Help Center: Administrator Actions for Windchill Mobile App. Once the mobile app has been configured, you can configure attribute layouts and set preferences related to the mobile app. For information on how users will download the app and connect to Windchill, see Connecting to Windchill from Your Mobile Device in the Windchill Help Center: .

Business Object Uniqueness

Considerations

When your Windchill solution was installed and configured, choices were made regarding the uniqueness of business objects, such as parts and documents. If your site has multiple organization contexts, decisions were also made about whether business objects must be unique across all organizations, or whether they can be unique within each organization.

In a default configuration with multiple organizations, business objects such as parts and documents must be unique across all organizations within the site, as shown in the diagram below. The colored area indicates the space within which each business object must be unique, also called the namespace.

Since each business object must be unique across all organizations within the site, there cannot be a Part1 or Part2 created in Org2, because Part1 and Part2 already exist within Org1; similarly, since Part3 and Part4 already exist in Org2, a user could not create a Part3 or a Part4 in Org1, as shown in the diagram below.

Note

CAD document file names must be unique across all organizations within the site, regardless of the business object uniqueness configuration. For example, if CADDoc1 exists within Org1, there can not be a CADDoc1 in any other organization within your site. For more information, see the Using PTC Creo Parametric with PTC Windchill guide.

If your system was configured to allow business objects uniqueness by organization, however, the organization becomes part of the uniqueness constraint for each business object. As a result, the uniqueness of a business object is constrained within each organization, rather than within the entire site. This allows

for a Part1 to be created in Org2, regardless of whether a Part1 exists in Org1. In the following diagram, the colored areas again indicate the space within which business objects must be unique.

Note

An organization's uniqueness is set within the organization template. Once an organization context is created, the business object uniqueness scope cannot be changed for that organization.

A part named Part1 can exist within both Org1 and Org2 because it is unique within each organization. Within Org1, however, a Part1 cannot be created in Product2 because there is already a Part1 in Product1, as shown in the diagram below.

Note

Regardless of whether business object uniqueness is configured for the site or organization level, the uniqueness of objects within projects and programs is not affected. Objects created within a project or program context are always unique within that project or program.

Users can search for all objects across all organizations in the site, regardless of the configuration. They are limited only by their access control permissions and other site configurations. If your site is configured for business object uniqueness within each organization, however, business objects from one organization cannot be selected from the search results and used within a different organization.

If you do not know whether your site was configured with business object uniqueness by organization, do one of the following:

•Check with the person who installed your Windchill system.

•See the PTC Windchill Installation and Configuration Guide for the business object uniqueness configuration details, and determine if they have been implemented.