#### Creo® Installation and Administration Guide 5

This guide describes how to generate and configure licenses, and how to install and maintain the Creo applications—Creo
Parametric, Creo Direct, Creo Layout, Creo Simulate, and Creo Options Modeler—using PTC Installation Assistant.

#### Share on Social Networks

Use permanent link to share in social media

#### Share with a friend

5. OpenT ype Font Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 UNICODE Font Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 A vailable System Fonts for Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Extended ASCII Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Displaying the T ext Symbol Palette in Creo Parametric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Exporting Special Symbols to IGES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Font Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 A VI Compression Codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Exporting Data to Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Meeting Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Opening a PDF File within the Creo Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Using Creo V iew Express to Open Creo Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Opening Creo Objects from Windows Explorer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 JavaScript Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Handling Incorrect Wra pper Files Stored in Windchill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Appendix D. Installing and Configuring Diagnostic T ools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Installing Diagnostic T ools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Configuring Diagnostic T ools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Using Diagnostic T ools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Uninstalling Diagnostic T ools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Appendix E. Installing MKS Platform Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Installing MKS Platform Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Appendix F. Installing the Creo Applications in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Guidelines and Advantages of a Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Strategies for the Mass Deployment of Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Wor kflow for a Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Command Syntax for a Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Locating the XML Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Editing the XML Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Uninstalling the Creo Applications in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Installing and Uninstalling Client-Side Components in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . 152 Installing Diagnostic T ools and MKS Platform Components in Silent Mode . . . . . . . . . . . . 154 Updating the Registry File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Appendix G. Port Usage by Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Using Communication Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Appendix H. Distributed Computing T echnology for Creo Parametric . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Overview of Distributed Computing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Supported Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Configuring Wo rkstations for Distributed Computing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Appendix I.T roubleshooting T ips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 General Debugging Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Online Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 T roubleshooting List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Contents 5

1. Creo ® Installation and Administration Guide 5.0.4.0 Creo Parametric Creo Direct Creo Layout Creo Simulate Creo Options Modeler Creo Render Studio

113. ASCII Font Definition Use the following parameters to define ASCII characters: • codeset: 0 • height: 16 • width: 16 • base_of fset: 4 • gap: 0 System Administration Information 1 13

115. Special Font Definition The following text parameters are used to define a special font: • codeset: 4 • height: 38 • width: 36 • xextent: 63 • spec_height: 24 • base_of fset: 8 • ascender: 6 • fixed_width: 1 • ics: 1 • gap: 4 In the special font, all characters are defined in 38 vertical grid spaces. Each character has an individual width declared in front of its definition. T o establish spacing between character boxes, the “gap” parameter is set to 4. The following figure illustrates the definition of the special font character . System Administration Information 1 15

11. 1 Preparing to Install Y our PTC Software What Y ou Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Generating Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Before Y ou Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Opening a PTC Online Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 About PTC Installation Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Wo rking with PTC Installation Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 PTC Software License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Authenticating Y our User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 This chapter describes the materials in your software shipment. It also provides an overview of how you can use PTC Installation Assistant for obtaining licenses and installing your software. 1 1

19. 2 Quick-Start Installation for Experienced Users Updating PTC License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Installing Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Where Y our Software Is Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 This chapter provides a quick-start approach for experienced users who have previously installed license management and product software on license server , license client, and node-locked machines. For step-by-step installation instructions on using PTC Installation Assistant, read the subsequent chapters in this guide. New users can refer to the section Installing the Creo Applications: Simple Installation Process on page 32 . 19

6. Appendix J. Workflow for Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Wor kflow for Generating Licenses for the Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Wor kflow for Installing the Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Wor kflow for Reconfiguring the Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 6 Cr eo ® Installation and Administration Guide

171. W orkflow for Generating Licenses for the Creo Applications W orkflow for Installation and Configuration 171

173. W orkflow for Reconfiguring the Creo Applications W orkflow for Installation and Configuration 173

47. 6 Completing the Installation and Starting the Creo Applications Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Installing and Uninstalling the Creo Applications in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Starting the Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Configuring the Creo Application Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Directory Permissions to Start Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Installing Creo Platform Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Configuring a Creo Parametric Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Uninstalling Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 This chapter explains how to complete an installation of a Creo application. This information is common to Creo Distributed Services Manager. Information on how to start the Creo applications and configure their startup is also given. Proceed to the end of the chapter for the procedure to uninstall the Creo applications. 47

112. character box, depending on how you decide to draw them. The following figure illustrates text justification. Y ou can change a font file to alter the appearance of any given font. Consider the ASCII font definition for the character “A”, both in the original and modified form. If you modify the text parameters without redefining the character parameters, the appearance of the fonts changes. For example, if you change the grid height from the default value of 16 to 20, the character appears smaller . Because the character was originally defined with a maximum grid value of 16, the original ratio was 16/ 16; after the change, the ratio is 16/20. Therefore, the new text height appears to be 80 percent of the original height. 1 12 Cr eo ® Installation and Administration Guide

137. E Installing MKS Platform Components Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Installing MKS Platform Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 This appendix contains information on how to install MKS platform components to work with CADDS 5 models. 137

139. F Installing the Creo Applications in Silent Mode Guidelines and Advantages of a Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Strategies for the Mass Deployment of Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Wo rkflow for a Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Command Syntax for a Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Locating the XML Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Editing the XML Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Editing the PROPER TY Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Editing the SHORT CUT Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Editing the PSF Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Editing the QUALITY_AGENT Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Editing the LANGUAGE Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Editing the P ACKAGE Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Editing the CDSECTION Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Uninstalling the Creo Applications in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Installing and Uninstalling Client-Side Components in Silent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Installing Diagnostic T ools and MKS Platform Components in Silent Mode . . . . . . . . . . . . . . . . . . . 154 Updating the Registry File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 This appendix for system administrators is applicable only for W indows. It provides information on how to perform a silent installation of the following Creo applications: Creo Parametric, Creo Direct, Creo Layout, Creo Simulate, and Creo Options Modeler. The instructions for using command-line arg uments are also common for Creo Distributed Services Manager. 139

59. 7 Installing and Accessing Creo Help Overview of the Help Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Browser Support for Creo Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Accessing Help from within a Creo Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Choosing a Location for the Help Center Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Installing the Help Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Enabling the Help Center from a Network Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Installing the Help Center on a Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 V iewing the Help Center Independent of a Creo Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Uninstalling the Help Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 This chapter provides an overview of the Help Center . It explains how to install and access Help for Creo Parametric, Creo Direct, Creo Layout, Creo Simulate, and Creo Options Modeler from a local host computer , a network drive, or a W eb server . 59

99. Starting a Creo Application through an External Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Opening a PDF File within the Creo Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Printing a PDF File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Using Creo V iew Express to Open Creo Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Opening Creo Objects from Windows Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 JavaScript Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Handling Incorrect Wr apper Files Stored in Windchill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 This appendix describes general system administration information, including system management utilities and machine configuration settings. System Administration Information 99

37. <Installdir>\DiagnosticTools Using Diagnostic T ools with Creo Applications Diagnostic T ools is a required utility that is installed by default when you install any of the Creo applications. Click or clear the check box at the bottom of the Application Selection screen to enable or disable diagnostic reporting. By default, diagnostic reporting is enabled. Diagnostic T ools helps you to collect information and send reports to PTC on the performance and usage of the Creo applications. Before clicking the check box, read the instructions in the data collection document. The link to the data collection document is at the bottom of the screen. See Installing and Configuring the Diagnostic T ools on page 130 for more information on the uses of Diagnostic T ools. Installing Creo Applications, PTC Mathcad, and other Utilities 37

67. 8 Updating an Installation Updating the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Updating Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Customizing an Existing Installation of a Creo Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Installing a Maintenance Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Upgrading an Existing V ersion of an Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 This chapter explains how to update the Creo applications installed on your system. Use the same procedure to update Creo Distributed Services Manager. Each time you update your software, you must update your license file. New license codes are not required if you are updating to a new build of Creo within the same release. In some cases you may have to update the current installation of PTC License Server . See the next section for details. 67

110. In addition to the width parameter , an individual width parameter can occur in each character definition. Use the individual width parameter to create a variable horizontal distance between the characters. In this case, if the ics parameter = 1, the individual width for each character overrides the width at the top of the file. If ics = 0, the system ignores individual width parameters. The following figure shows the ef fect of the ics parameter on the calculation of character width. The following figure shows the eff ect of the fixed_width parameter on the calculation of character width. 1 10 Cr eo ® Installation and Administration Guide

165. I T roubleshooting T ips General Debugging Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Online Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 T roubleshooting List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Failure to Start the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Xtop Icon Disappears from the T askbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Inaccurate Ptcstatus Command Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Invalid Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 FlexNet Publisher Fails to Start (T riad Configurations) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 ModelCHECK Metrics T ool Display Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 This appendix documents common problems that occur when you install PTC software and PTC License Server . This appendix also provides general debugging techniques and cites other sources of information available from the PTC W eb site. 165

46. Using this tabbed page you can configure licenses for Creo Simulate. A list of license types against the selected licenses appears on this tabbed page. T ype a value in the Selected License(s) text box to change the license for the selected license type. 46 Cr eo ® Installation and Administration Guide

116. LA TIN_1 Font Definition The following text parameters define the LA TIN_1 font: • codeset: 2 • height: 40 • width: 32 • xextent: 63 • spec_height: 24 • base_of fset: 8 • ascender: 8 • fixed_width: 0 • ics: 0 • gap: 0 The LA TIN_1 font is defined with a character box of 40x32 grid spaces. All characters have constant width and are centered in the character box. In the double quoted line above the character definition, the decimal and hexadecimal code representing the character is shown, as follows: code <decimal> <hex> The following figure illustrates how to map a LA TIN_1 character . 1 16 Cr eo ® Installation and Administration Guide

172. W orkflow for Installing the Creo Applications 172 Cr eo ® Installation and Administration Guide

38. 5 Customizing the Installation of the Creo Applications Customizing an Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Defining the Installation Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Installing Creo Mold Analysis (CMA) Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Modifying License Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Configuring Windows Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Setting Licenses for Creo Simulate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 This chapter explains how to customize an installation of the Creo applications. This information also applies to Creo Distributed Services Manager. Some of the application features in this chapter are specific to individual Creo applications. 38 Cr eo ® Installation and Administration Guide

109. • If you set it to 1, the font is independent of the text_width_factor option in the drawing setup file. • If you set it to 0, you can control the font width by using the text_width_ factor option or by modifying the text width manually . The following figure illustrates the text parameters that define a font. When you modify text parameters, consider how the font will appear in text with other fonts. Fonts used in the same text line (such as ASCII and LA TIN_1 for European languages, or ASCII and special) must be compatible. Altering one font might create inconsistency in appearance and placement. For example, changing the base_offset value at the top of the font file aff ects the positioning of all the font characters, relative to the text baseline, as shown in the following figure. System Administration Information 109

130. D Installing and Configuring Diagnostic T ools Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Installing Diagnostic T ools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Configuring Diagnostic T ools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Data Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Pending Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Last Sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Using Diagnostic T ools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Uninstalling Diagnostic T ools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 This appendix contains information on Diagnostic T ools utility . 130 Cr eo ® Installation and Administration Guide

111. Character Parameters Below the text parameters section, a font file contains an individual definition for each character . A character definition contains the following information: • First line—An ASCII character , in double quotes, that represents the character to be drawn. For ASCII and filled primary fonts, it is the character itself. Special characters also use ASCII characters to represent them. The LA TIN_1 fonts use the decimal and hexadecimal codes representing the character . • Second line (optional)—Individual width value (used only if ics is turned on). • The remainder of the file consists of drawing-definition commands, described in the next section. Definition Commands The drawing definition of characters and special symbols in the font files is done with the following commands (where <X> and <Y> are integers): • [m<X>, <Y>] —This command moves an imaginary pen to the grid point (X, Y). • [d<X>, <Y>] —This command draws a line from the current position to grid point (X, Y). • For each font, you can use 63 or fewer grid points to create characters and symbols. Creo provides optimum values, giving adequate character definition with a minimal grid. Enter characters centered or left-justified within a System Administration Information 1 1 1

114. The following figure illustrates how ASCII characters are mapped. Note that ASCII characters are defined in a character box consisting of 16x16 grid spaces. All characters have modifiable width and are centered within a character box. Filled Font Definition Use the following text parameters to define a filled font: • codeset: 0 • height: 63 • width: 48 • base_of fset: 16 • gap: 0 • polygons: 1 • ics: 1 In the filled font, characters are mapped within 63 vertical grid spaces. However , the width for each character is dif ferent. The ics parameter (set to 1) tells the system to ignore the global width parameter given at the top of the file. Instead, the system uses the individual character width, which precedes each character definition, to map a character . Define the outline of a filled character by drawing polygons (closed loops). When the polygons parameter at the top of a font file is set to 1, the Creo application fills with color any closed polygon drawn in a character definition. 1 14 Cr eo ® Installation and Administration Guide

127. If a Creo session is not running and you double-click an object in W indows Explorer , the Creo application startup configuration file dialog box opens. Y ou are prompted to select a file from the list of available configuration files. Upon selecting the required startup configuration file, a Creo session is started using the selected configuration file. The selected object is loaded in this Creo session. If multiple sessions of Creo applications are running, the selected object is loaded in the session that you started first. JavaScript Security In Creo, a JavaScript bridge is used so that the JavaScript code inside a displayed HTML page interacts with the Creo application. For example, Feature info reports, folder content listings, and new connection registrations all use the JavaScript bridge for security purposes. A Creo application automatically activates the JavaScript bridge only from pages generated by the application or W indchill Solutions. If a page generated from another source tries to access the Creo application through the JavaScript bridge, a warning message appears and the operation is stopped. T ake one of the following actions: • If the URL in the message is from an unreliable source, contact your system administrator and avoid accessing this page again. • If the URL in the message is from a reliable source, such as a PTC W indchill Solution, contact T echnical Support. Handling Incorrect W rapper Files Stored in Windchill When you use Creo Unite technology to open CA TIA, NX, and SolidW orks part and assembly models in Creo, the following occurs: • Creo data wraps around the non-Creo data. • Creo wrapper files are created. The wrapper files are stored internally and are not visible. System Administration Information 127

141. • Y ou can eff iciently mass-deploy Creo applications across a lar ge enterprise. • Y ou can source all the configuration settings, such as installation location, license source list, and startup commands, for installing a Creo application from an XML file. Strategies for the Mass Deployment of Creo Applications As an administrator you can adopt one of the following strategies to mass-deploy Creo applications and client-side components such as Creo V iew Express, Creo Thumbnail V iewer, and Creo Platform Services in a lar ge enterprise: • Perform a silent installation of Creo applications on all the client computers. See W orkflow for a Silent Installation on page 142 for details. Y ou can then choose to install the client-side components on each client computer . See Installing and Uninstalling Client-Side Components in Silent Mode on page 152 for details. • Provide the client computers access to the applications installed on a single network-accessible machine. Perform the following steps for the client-side configuration: 1. If required, install the client-side components on each client computer . See Installing and Uninstalling Client-Side Components in Silent Mode on page 152 for details. 2. Update the registry entry for each Creo application on each client computer using the created.reg file. See Updating the Registry File on page 154 for details. • Copy a single prototypical installation onto each client computer . Then perform the following steps for the client-side configuration: 1. If required, install the client-side components on each client computer . See Installing and Uninstalling Client-Side Components in Silent Mode on page 152 for details. 2. Update the registry entry for each Creo application on each client computer using the created.reg file. See Updating the Registry File on page 154 for details. Installing the Creo Applications in Silent Mode 141

133. Note Y ou cannot filter information that PTC considers mandatory . Those check boxes are unavailable. The customized preferences and data filters are stored at C:\Program Files\ PTC\DiagnosticTools\text\xml\ . Pending Data For each Creo application you have installed, you can view the collected product and system information on the Pending Data tab. Installing and Configuring Diagnostic T ools 133

156. G Port Usage by Creo Applications Using Communication Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Port Usage for PTC License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 This appendix provides information on the communication ports used by various Creo applications and the related client applications. 156 Cr eo ® Installation and Administration Guide

33. 3. Click Next . The Software License Agreement screen appears. 4. Accept the agreement and click the check box at the bottom of the screen to confirm that you are installing the software in compliance with the export agreement. 5. Click Next . The License Identification screen appears. Installing Creo Applications, PTC Mathcad, and other Utilities 33

98. C System Administration Information T emporary Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 System Management Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Creo Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 FlexNet Publisher Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Supported Graphics Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 General Plotter Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Using Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 OpenT ype Font Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 UNICODE Font Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 A vailable System Fonts for Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Extended ASCII Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Displaying the T ext Symbol Palette in Creo Parametric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Exporting Special Symbols to IGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Font Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 T ext Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Character Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 1 Definition Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 1 ASCII Font Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 13 Filled Font Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 14 Special Font Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 15 LA TIN_1 Font Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 16 How to Edit Fonts or Create New Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 17 How to Modify a Font File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 17 How to Create a User-Defined Font File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 18 How to Store a New Font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 18 How to Set Y our Font as the Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 18 How to Create or Customize a Font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 18 A VI Compression Codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Exporting Data to Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Meeting Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Browser Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 98 Cr eo ® Installation and Administration Guide

124. Exporting Data to Portable Document Format Y ou can use the Interface for PDF application through Creo Parametric to export model drawings to Portable Document Format. The Interface for PDF provides enhanced navigation, search, and presentation capabilities. The licenses for this application can be node-locked or floating. The Interface for PDF enables you to do the following tasks: • Insert the Creo Parametric parameter data as searchable metadata in the PDF file. • Modify the font types, color , style, and resolution of the PDF output. • Insert Creo Parametric drawing text and numerical values as searchable and selectable content in the PDF file. • Insert bookmarks for the various Creo Parametric layers, sheets, zones, flag notes, and revision tags. • Control the access and security rights of the PDF file. For more details, see the Interface Help available in the Creo Parametric Help Center . Meeting Browser Requirements This section describes the requirements for the Creo browser for all the Creo applications. For information on W eb browser support for the Creo applications, see http://www .ptc.com/WCMS/files/160242/en/PTC_Creo_Future_Platform_ Support_Summary .pdf . For information related to the Help Center , see Installing and Using Creo Help on page 59 . Browser Requirements Creo browser runs in the Creo agent and uses the engine of Internet Explorer (IE) by default. Creo uses a 64-bit browser processing support for IE and Chromium. The multi-process architecture of IE browser allows Creo to run the embedded browser in the out-of-process mode. That is, the IE browser runs as a separate process that is not within the Creo process. The Creo agent is the same across all Creo applications and as a result, the 64 bit embedded browser will also be the same across all Creo applications. When Creo applications are connected to the same Creo agent, you can only use a single browser type in a session of a Creo application. Y ou cannot change the browser type in the session. T o change the browser type, you must exit the current 124 Cr eo ® Installation and Administration Guide

162. H Distributed Computing T echnology for Creo Parametric Overview of Distributed Computing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Interactions between the Controller and the Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Supported Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Configuring Wor kstations for Distributed Computing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 This appendix contains information on the Distributed Computing technology that is used by Creo Parametric to augment your existing hardware. 162 Cr eo ® Installation and Administration Guide

170. J W orkflow for Installation and Configuration Wo rkflow for Generating Licenses for the Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Wo rkflow for Installing the Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Wo rkflow for Reconfiguring the Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 This chapter provides simple workflows for generating licenses and installing and reconfiguring the Creo applications. The workflow is presented as a flowchart for each of these processes. If you have received a license file via e-mail from PTC License Management, use that license file instead of the product codes for licensing. After the installation, you can configure the installation of applications like Creo Parametric for units of measurement or drawing standards. 170 Cr eo ® Installation and Administration Guide

90. Argument Description -d display Displays the system name. Required only if the displayed system name is dif ferent than the one used to initiate borrowing. feature Names the borrowed license feature to be returned early . Use the lmborrow -status command for a list of borrowed license features. 90 Cr eo ® Installation and Administration Guide

94. Reconfiguring the V endor Daemon A server administrator can use the V endor Daemon Configuration tab to verify whether the server is running and to reconfigure the vendor daemon. 94 Cr eo ® Installation and Administration Guide

45. Configuring Windows Shortcuts Using the Shortcut tabbed page, you can configure the W indows shortcut preferences for the Creo applications. Set the W indows shortcut settings that are shown in the following figure: Setting Licenses for Creo Simulate The Licenses tabbed page appears when you click Creo Simulate . Customizing the Installation of the Creo Applications 45

61. Choosing a Location for the Help Center Installation Using the Help DVD, you can install the Help Center for the Creo applications at one of the following locations: • A local host computer where the Creo applications are installed. • A network drive. This location is helpful for administering multiple clients on a network. • A W eb server . Installing the Help Center Using the Help DVD in your shipment, proceed with the installation as described. Y ou can also download the Help DVD from the Order or Download Software Updates page at PTC.com. If you have installed the Help Center on a network drive, perform the steps explained in Enabling the Help Center from a Network Drive on page 63 to access the Help Center from the Creo application. 1. Start W indows Explorer , browse to the DVD drive, and double-click setup.exe . Alternatively , download the DVD as described in the previous paragraph. The PTC Installation Assistant begins. 2. Perform steps 1 through 4 as described in Installing the Creo Applications: Simple Installation Process on page 32 . 3. Click Next . The Application Selection screen appears. Installing and Accessing Creo Help 61

72. 5. After you select all the options, click Install on the Application Selection screen. 6. Click Finish to complete the installation and close the Assistant. 72 Cr eo ® Installation and Administration Guide

163. Overview of Distributed Computing Creo Parametric uses Distributed Computing technology to perform computationally intensive tasks by augmenting your existing hardware. Distributed Computing technology includes the following elements: • A Creo Parametric session or the controller . • Participating networked workstations. • A daemon running on each participating workstation. • One or more agents running on the workstations. These agents could be the Creo Parametric sessions running as server processes. • A task or a collection of jobs. Note Distributed Computing is suitable only for multiobject design studies. Interactions between the Controller and the Agent W ith Creo Parametric you can optimize the distribution of tasks using Distributed Computing technology . The controller communicates with the daemon on each workstation and determines load averages. Agent sessions are automatically started depending on load averages and the number of processors. These agents are started only once for every distributed computing task and not for every job. Communication of data is also optimized. Data, that is, models, information, and instructions, are eff iciently streamed directly to each agent through the daemon. No files are copied to a workstation before a job is carried out. As subsequent jobs are dispatched to the same agent, only data that is dif ferent between the jobs is streamed. If the data involved is the same, it is not streamed again. Supported Functions Distributed Computing technology supports the following functions: • W orkstations with multiple CPUs are leveraged so that an agent process exists for every CPU (depending on the system load average). • W orkstations are engaged in distributed computing unless the load on a CPU exceeds 20 percent. • T asks are dispatched to workstations based on the following real-time conditions: ○ The workstations must be online. Distributed Computing T echnology for Creo Parametric 163

184. network connection failure, 85 ptcflush utility syntax, 85 software execution, 166 tips, 165 U uninstalling Creo applications, 57 update installation, 68 utilities Creo, 100 lmtools, 101 lmutil, 101 ptcflush, 85 ptcshutdown, 101 ptcstartserver, 101 system management, 100 W W eb browser requirements, 124 W indows browser requirements, 124 creating program shortcuts for Creo applications, 45 temporary directory, 100 workstations for distributed computing configuring, 164 X XML file editing, 146 locating, 145 Xtop icon, 166 184 Cr eo ® Installation and Administration Guide

43. Similarly , run the following command for a 64–bit system to uninstall the Creo Mold Analysis component: smpd-intel-4.0.3.009-x64.exe – uninstall Modifying License Configurations Using the Command Configuration tabbed page, you can add, edit, or delete a license configuration. The figures in this section show the default license configurations for Creo Parametric. Similar screens appear for the other Creo applications. Perform the following steps: 1. Click Add to add additional configurations. The Add configuration dialog box opens. Customizing the Installation of the Creo Applications 43

52. Directory Permissions to Start Creo Applications Y ou cannot start a Creo application from a directory without write permissions unless you specify an alternative directory to store the trail files. If you start a Creo application from a directory without write permissions, a dialog box opens as shown in the following example: Specify another directory with write permissions. The working directory remains the same, but the trail files are stored in the new working directory that you have specified. Installing Creo Platform Services Installation Path of Utilities Few of the required and optional utilities that you select to install with the Creo applications do not get installed at the default or custom installation path that you specify . The following are the required and optional utilities and their respective installation paths for the Creo Platform Services: W ith default location as C:\Program Files\ W ith custom path: <installdir>\Creo\ When you begin the installation of a Creo application, the latest version of the Creo Platform Services also gets installed. Older installed versions of Creo Platform Services are uninstalled, since the latest version works with older versions of Creo applications. 52 Cr eo ® Installation and Administration Guide

181. Index A ASCII font definition, 1 13 B borrowed licenses, 74 browser requirements PTC Creo, 124 W indows, 124 C CDSECTION nodes editing, 151 character box, 1 1 1 definitions, 1 1 1 modifying, 1 1 1 parameters, 1 1 1 client-side components installing and uninstalling silently, 152 commands PTC Installation Assistant, 69 ptcflush, 82, 85, 100 ptchostid, 100 ptcstatus, 100 communication ports usage, 157 compatibility file format, 32 Compression Codecs, 123 configuring workstations for distributed computing, 164 controller and agent interactions, 163 Creo browser requirements, 124 updating, 68-69 utilities, 100 Creo applications compatibility, 32 completing installation, 47 customizing, 38 removing installation, 57 specifying directory permissions, 52 starting, 47, 49 uninstalling, 151 Creo Unite wrapper files recreating when corrupt, 127 updating to synchronize with import profile, 127 Creo V iew Express, 125 D defining components, 40 Diagnostic T ools, 131 configuring, 131 session log, 135 setting filters, 132 setting preferences, 132 uninstalling, 136 uses, 135 viewing information, 133 viewing last sent information, 134 Distributed Computing technology, 162 E extended licenses, 74 181

10. Documentation Conventions PTC documentation uses the following conventions: Convention Item Example Bold Menu paths, dialog box options, buttons, and other selectable elements from the user interface Click File ▶ ▶ New . Click OK . Courier User input, system messages, directories, and file names Processing completed. Courier with less- than and greater - than symbols (< >) V ariables for which an appropriate value is substituted output= <LOADPOINT> 10 Cr eo ® Installation and Administration Guide

155. The default location of the registry file for some of the Creo applications is as shown: C:\Program Files\PTC\Creo <version number>\Parametric\bin\pim\xml\created.reg (Creo Parametric) C:\Program Files\PTC\Creo <version number>\Direct\bin\pim\xml\created.reg (Creo Direct) T o make configuration changes on the client computer , open the created.reg file stored on the computer where the Creo applications are installed. Then perform one of the following steps: • Mer ge the entries of this file with another file you are using on the client computer . • Open the Registry Editor dialog box and click File ▶ ▶ Import to import the entries of the file to the client computer . Installing the Creo Applications in Silent Mode 155

39. Customizing an Installation Y ou can customize the installation of a Creo application using the following procedure: 1. Perform steps 1 through 8 as described in the section Installing the Creo Applications: Simple Installation Process on page 32 . 2. Select the applications on the Application Selection screen and click Customize . The Application Custom Setting dialog box opens. The selected applications for customization appear on the left pane. The customization tabbed pages appear on the right pane as shown in the following figure. • T o install customized application features using the Application Features tabbed page, see Defining the Installation Components on page 40 . • T o modify license configurations using the Command Configuration tabbed page, see Modifying License Configurations on page 43 . • T o configure W indows shortcut preferences using the Shortcuts tabbed page, see Configuring W indows Shortcuts on page 45 . 3. Click an application on the left pane and then click a tabbed page on the right pane to proceed. 4. After selecting the options on all the tabbed pages, perform one of the following actions: Customizing the Installation of the Creo Applications 39

21. Where Y our Software Is Installed PTC Installation Assistant defines and installs software into a default installation directory that you can modify for your environment during installation. The default path is as follows: C:\Program Files\PTC\Creo <version number>\<app_name> where <version number > has the format V .R.M.C where: • V - indicates the main release number • R- indicates the point release number • M- indicates the maintenance release number • C-indicates the critical patch set number For example for the main Creo 5 release the value of V .R.M.C would be 5.0.0.0 and the software will be installed at the path C:\Program Files\PTC\Creo 5.0.0.0 hereafter referred to as <creo_loadpoint> PTC License Server , the Creo applications, and any related components are installed into separate subdirectories within the PTC directory . Note All the 32-bit applications are installed at C:\Program Files (X86) even if you have specified your installation path as C:\Program Files . Quick-Start Installation for Experienced Users 21

135. Click Send via e-mail to send an aggregated report in ASCII format. The report is sent as an e-mail attachment to a designated PTC T echnical Support Engineer or to your e-mail address. Using Diagnostic T ools The Diagnostic T ools utility automatically collects information related to the application and system information and transfers it to PTC. The information transfer is based on the filter settings in the Data Filters tab and the frequency settings in the Preferences tab. For each session, Diagnostic T ools checks for new data before the transfer . The information is automatically encrypted and transferred using the SSL methodology . As a user of a Creo application, you can open the Diagnostic T ools dialog box to view the pending data to be transferred to PTC on the Pending Data tab. Y ou can click the Send via e-mail button to send the Creo application-related and system information report in ASCII format as an e-mail attachment to a designated PTC T echnical Support Engineer and to your e-mail address. Both you and PTC T echnical Support can then review the information simultaneously . Installing and Configuring Diagnostic T ools 135

123. Examples of the T ext Symbol Palette Layout File • If you specify #1.15 in the first row of the text symbol palette layout file, Creo Parametric ignores the crosshatch ( # ) character . One column is displayed in the T ext Symbol palette. The decimal point (.) after 1 is ignored. The integer 15 is taken as the first ASCII code but is ignored. Only those ASCII codes from 32–255 are displayed in the T ext Symbol palette. • File 1 and File 2 represent the same T ext Symbol palette in Creo Parametric: File 1 File 2 3 60 61 62 35 37 68 65 66 70 75 3 60 61 62 35 37 68 65 66 70 75 A VI Compression Codecs Y ou can capture an A VI file using the third-party compression codecs installed on your system. PTC does not provide codecs that support A VI compression. A warning message appears when you try to capture an A VI file under the following conditions and the process aborts prematurely: • Y ou have not installed or licensed the compression codecs correctly on your windows system. • Y ou have installed a codec that is defective. • The codec does not work with specific compression settings. System Administration Information 123

134. On the active application tab, click a button to perform the following actions: • Send Now —Sends the product and system information to the database via an https secure communication protocol. For example, if the Creo Direct tab is active, the product and system information for Creo Direct is sent to the database. • Send via e-mail —Sends a report in ASCII format as an e-mail attachment to a designated PTC T echnical Support Engineer . For example, if the Creo Direct tab is active, you can send a report for Creo Direct to a PTC T echnical Support Engineer or to your e-mail address. Last Sent For each Creo application that you have installed, you can view the product and system information that was last collected and transferred to PTC on the Last Sent tab 134 Cr eo ® Installation and Administration Guide

58. Select one of the following Uninstall Options : • Uninstall only selected application • Uninstall all applications and Utilities in this version Click Uninstall to remove either the selected Creo application or all applications and utilities for the selected version. Note If you have installed more than one Creo application, make sure that the Common Files folder and its contents are still available in the Creo load point. 58 Cr eo ® Installation and Administration Guide

60. Overview of the Help Center The Help Center provides access to documentation and includes the following features: • Context-sensitive Help for Creo applications — Creo Parametric, Creo Direct, Creo Layout, Creo Simulate, and Creo Options Modeler. • A search facility and quick links to helpful information. Browser Support for Creo Help Creo Help supports following browsers: • Internet Explorer 9.0 and later • Mozilla Firefox 10.0.1 and later The Help Center for the Creo application opens in your default browser . Y ou can set one of these browsers as the default on your computer . Accessing Help from within a Creo Application Each Creo application launches its Help in a separate window of your default browser . The value of the PRO_LANG environment variable determines the language of the Help Center . Y ou can access Help topics in the following ways: • For context-sensitive Help, point to a user interface item and press F1. • T o browse the Help Center , click . The Help Center is accessed from the following locations: • support.ptc.com/apps/help_center—The default if you do not install the Help Center and set the PTC_<app_name>_HC_URL_5 environment variable. • Local host computer—The default if you install the Help Center but do not specify an alternate location, such as a network drive, for accessing Help. Note When you upgrade a Creo application, you must also upgrade the Help center to the corresponding datecode of the application. Otherwise, the Creo application accesses the corresponding Help Center from PTC.com. 60 Cr eo ® Installation and Administration Guide

107. Exporting Special Symbols to IGES Special symbols and their corresponding ASCII characters map to the IGES font table 1001. Only two symbols (T otal Runout and the Least Material Condition) do not map to the 1001 table. They are supported by the 1003 font table. The configuration file option use_iges_font_1003 determines which IGES font table outputs data to IGES.When you assign an ASCII character to a new symbol, select a character from either the 1001 or 1003 font table. Use 1001 or 1003 exclusively when you anticipate that a drawing will be exported in an IGES file. (Refer to your IGES documentation for more information on IGES font tables.) Font Definition Creo defines fonts using two sets of parameters: • T ext parameters—The settings of a character definition box and other parameters used by all characters. • Character parameters—The individual definition of each character (that is, how the character is drawn). Comment lines in font definition source files are preceded with the “#” character . These parameters do not define the actual size of characters. They establish relative coordinates for stroking the character in the graphics windows. Y ou control the actual size of text and symbols using the appropriate options in a Creo application. In case of Creo Parametric, you can change the actual size of text in drawings only . T ext Parameters T ext parameters for a given font are specified only once, at the head of the font file, and are used for every character definition in the file. Note The exception to this is the proportional fonts, such as Iso, Leroy , and Cal_ grek, which require you to specify a specific width for each character . The following parameters define a character box with a grid (where <n> is an integer): • height <n> —Defines the total number of grid spaces in the vertical direction. The maximum height is 63. • width <n> —Defines the total number of grid spaces in the horizontal direction. The maximum width is 63. • gap <n> —Defines the total number of grid spaces between character boxes. System Administration Information 107

169. Cause: The information specified in the Data Sources page of the T omcat W eb Server Administration T ool does not match the information specified in the new_ admin.xml configuration file. Solution: V erify if a mismatch of information occurred. In case of a mismatch, ensure that the information in both places matches. Cause: The location of the Image Directory specified in the new_admin.xml configuration file does not match the location specified in the DocumentRoot path of the Apache\conf\httpd.conf file. Solution: Ensure that the paths are same in both files. Cause: The parameters related to the display of graphics are not set in the new_ admin.xml configuration file. Solution: Check the new_admin.xml configuration file and set the following parameters and their corresponding values: • dbname—The name of the database • dbtype—The type of database used, such as Oracle or Microsoft Access • imagedir—The location or path of the Image Directory • imagedirLink—The link to the Image Directory that stores the images of the graphs and reports in the metrics tool. T roubleshooting T ips 169

31. 4 Installing Creo Applications, PTC Mathcad, and other Utilities Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 File Format Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Installing the Creo Applications: Simple Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Using Diagnostic T ools with Creo Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 This chapter provides information on how to install the following PTC products: • Creo applications: ○ Creo Parametric ○ Creo Direct ○ Creo Layout ○ Creo Simulate ○ Creo Options Modeler ○ Creo Render Studio ○ Creo Distributed Services Manager • PTC Mathcad • Utilities 31

102. Supported Graphics Modes For graphics support information, refer to the PTC Hardware Configuration Notes at PTC_Creo_Future_Platform_Support_Summary .pdf . General Plotter Information PTC supplies software that writes plot files in plotter format. Y ou can specify a plot command in the config.pro file. The physical connection, however , is the responsibility of the computer and plotter vendors, because they are hardware and system software experts. Depending on the hardware configuration, the system software may require a dif ferent setup. If you have dif ficulty in set up, contact the customer support department of your hardware vendor . Note Creo applications described in this guide do not support any HPIB interfacing. Using Fonts PTC provides 42 third-party T rueT ype fonts and the default PTC fonts with your software. In addition, you can also use any T rueT ype font available on W indows. The third-party T rueT ype fonts include 13 dif ferent font styles. If you are running a Creo application in Chinese T raditional or Chinese Simplified, you can use two additional T rueT ype fonts: • Chinese T raditional • Monotype Hei Medium • Monotype Sung Light • Chinese Simplified • Monotype HeiGB Medium • Monotype SungGB Light New fonts appear in the current font list in Detailed Drawings and Sketcher . PTC fonts are listed first, followed by the third-party fonts supplied by Agfa Corporation. T rueT ype fonts are stored in the <creo_loadpoint>\Common Files\ text\fonts folder . Y ou can change this default location by placing the fonts in another folder and setting the value of the pro_font_dir configuration option to this folder . Creo applications use the fonts in the folder specified by the pro_ font_dir configuration option. 102 Cr eo ® Installation and Administration Guide

119. cp /usr/pro/text/usascii/ascii.src custom.src (primary font with codeset 0) cp/usr/pro/text/usascii/special.src symbols.src (special symbols font with codeset 4) 2. Edit the source files to include all the required definitions and changes. vi custom.src vi symbols.src 3. Copy the compile_font script from the directory <creo_loadpoint>/ Common Files/<machine_type>/obj into the same local working directory . cp /usr/pro/i486_nt/obj/compile_font 4. Compile the font files. compile_font custom.src custom.fnt compile_font symbols.src symbols.fnt 5. Create a new index file to reference the compiled font files. Note that the index file name does not need to be the same as the primary font name. If the custom font created is not a primary font (codeset 0), be sure to include a font with a codeset of 0 in the index file. In this example, the new font index file references both customized font files (primary and special symbols). myfont.ndx (new customized .ndx file) custom (new custom primary font (codeset 0)) latin_1 (system extended ASCII font(codeset 2)) symbols (new special symbols font (codeset 4)) This font index file references the new customized special symbols font only . It uses the system default primary font. myfont2.ndx (new customized .ndx file) ascii (system default primary font (codeset 0)) latin_1 (system extended ASCII font (codeset 2)) symbols (new special symbols font (codeset 4)) Y ou can use the new font in the following ways: System Administration Information 1 19

28. 2. T ype your Sales Order Number or your product code in the corresponding text box. 3. Click Host ID Setup to open the Host ID Setup dialog box. The sales order number or the product code from the previous step appears in the dialog box. The Machine ID , Port , and the Host columns for the local computer is shown. a. T o change the default port for a single license, edit the number in the Port text box and click Install Licensing . Then skip to the last step in this section. 28 Cr eo ® Installation and Administration Guide

122. GTOL Symbol ANSI Code ISO Code Straight 33 133 Flat 99 136 Circular 101 138 Cylinder 103 140 Profile Line 107 146 Profile Surf 100 137 Angular 97 135 Perpendicular 108 147 Parallel 102 139 Position 106 145 Concentric 1 14 148 Runout Circular 104 141 T otal Runout 34 134 Symmetrical 105 144 In a Creo Parametric drawing, the GT OL symbols in the T ext Symbol palette change if you change the value of the gtol_symbol_same_size detailing setup option. Guidelines for Customizing the T ext Symbol Palette Layout File Administrators must verify that the text symbol palette layout file is customized correctly and all the entries in this file are valid. If the customization is incorrect, Creo Parametric uses the default settings to display the T ext Symbol palette without a warning message. Guidelines for customizing the text symbol palette layout file follow: • When creating images, ensure that the height and width of the images does not exceed 16 pixels and 24 pixels, respectively . • The file must contain only integers. All nonintegers are treated as spaces. • Specify ASCII codes from 32–255. • Do not duplicate ASCII codes. • Place the same number of ASCII codes on each row as the integer that you have specified in the first line of the file. This listing approximates the appearance of the customized T ext Symbol palette in Creo Parametric. • Use the ASCII codes for the dtl options carefully . The usage of these symbols in a drawing changes between ANSI and ISO according to the value that you set for the detailing setup option, gtol_symbols_same_size . 122 Cr eo ® Installation and Administration Guide

183. M mass-deployment installation strategy, 141 MKS Platform components installing, 138 overview, 138 modifying Creo, 69 N network connection troubleshooting, 85 node-locked license, 74 O Open T ype font, 104 P P ACKAGE node editing, 151 Portable Document Format, 124 exporting, 124 program shortcuts on W indows for Creo applications, 45 PROPER TY node editing, 146 PSF node editing, 148 PTC Installation Assistant, 16 PTC License Server overview, 81 PTC licensing overview, 74 ptcflush utility usage, 85 Q QUALITY_AGENT node editing, 149 R registry file updating, 154 requirements W indows, 23 restrictions FlexNet Publisher, 82 S SHOR TCUT node editing, 148 shortcuts creating for Creo applications, 45 silent installation command syntax, 144 guidelines and advantages, 140 workflow, 142 symbols special, 107 system management utilities, 100 T TCP/IP, 85 installation requirement, 23 text base of fset, 107 characters, 1 1 1 parameters, 107 modifying, 107 width, 107 text fonts ASCII definition, 1 13 creating, 107 definition, 107 LA TIN_1 definition, 1 16 text parameters, 107 traceback log generating, 55 troubleshooting invalid licenses, 167 Index 183

48. Completing the Installation After configuring your settings, follow these steps to complete the installation: 1. Click Back and review information to make sure that your settings are correct. 2. Click Install to begin the installation. The Installation Progress screen displays the status. Note Utilities that are required for applications that you select on the Application Selection screen, get installed prior to the installation of the selected applications. On this screen you can also perform the following operations using buttons to the right of the progress bars and below them: • Click to stop an installation. • Click to restart an installation. • Click Finish after the applications are installed to close the Assistant. Y ou can also click [X] at the top-right corner of the Assistant to exit the installer . 48 Cr eo ® Installation and Administration Guide

128. If you open the non-Creo part and assembly models in the W indchill connected mode of Creo, the wrapper files are created and stored in W indchill. The non-Creo models are checked in to the W indchill W orkspace as follows: • The non-Creo models are checked in as the primary content of CAD Documents. • The wrapper files are stored in W indchill as the secondary content of the CAD Documents. From Creo, you can retrieve the non-Creo part and assembly models from the W indchill W orkspace. Recreating W rapper Files While retrieving the non-Creo models checked in to the W indchill W orkspace, the wrapper files may be corrupt if: • Model regeneration fails. • The geometry of the retrieved models is incomplete. If wrapper files are corrupt and the non-Creo models and their wrapper files are not synchronized with the data of the latest import profiles, you can use Creo Distributed Batch to discard the corrupt wrapper files and recreate them. T o enable Creo Distributed Batch to discard the corrupt wrapper files and recreate them, set the configuration option, sync_data_import_profile , to recreate in the T ask T ype Definition (TTD) files. The value, recreate , is supported only in Creo Distributed Batch. Note Discarding the corrupt wrapper files and recreating them before they are uploaded to the W indchill W orkspace as the secondary content of the non- Creo models does not change the revision of the non-Creo models. The sync_data_import_profile Configuration Option Use the sync_data_import_profile configuration option to create new wrapper files when the existing wrapper files are corrupt or to update the existing wrapper files when they are not synchronized with the latest import profiles. V alues for the sync_data_import_profile configuration option are listed below: 128 Cr eo ® Installation and Administration Guide

117. How to Edit Fonts or Create New Fonts 1. Edit an existing or create a new .src file, which resides in <creo_ loadpoint>\Common Files\text\<language> . 2. Compile the font file by using the command compile_font . 3. Make the new font available locally or for all users. How to Modify a Font File 1. Copy the appropriate .src font file into your working directory . The .src files reside at <creo_loadpoint>\Common Files\text\ <language> . 2. Modify the font file. 3. From the <creo_loadpoint>\Common Files\text\<language> area, copy the appropriate index file to your working directory . 4. Copy the compile_font command to your working area. 5. T o compile the font, enter the following command for each font file you modify: compile_font fontfilename.src fontfilename.fnt System Administration Information 1 17

16. W orking with PTC Installation Assistant In addition to generating and updating licenses, you can install some of the Creo applications using PTC Installation Assistant. When you start the Assistant, the W elcome screen appears as shown below: On this screen select a task based on your installation requirements and click Next to proceed. • Install new software • Upgrade existing software • Reconfigure existing software • Setup license As you perform the various tasks, the processes involved are highlighted on the left pane. T ake one of the following actions to end the installation process: • Click Install and then click Finish to complete the installation and close the Assistant. • Click Finish to close the Assistant if you are only generating or updating licenses. • Click [X] at the top-right corner of the Assistant to stop the installation and exit the Assistant at any stage during the installation. 16 Cr eo ® Installation and Administration Guide

149. Subnode V alue LICENSE_IDENTIFIERS Provide a list of license sources separated by semicolons. The license sources can be node-locked license files or server -based port@host identifiers. FEATURE_NAME Provide a list of FLEXnet license-to-run features separated by spaces. The feature list is followed by a list of additional options within parentheses. Choose the options to acquire at startup. DESCRIPTION Identify the PSF run definition to be used by the software wrapper program (for example, parametric.exe ) in case multiple PSF run definitions exist. The software wrapper program then opens a dialog box with a list of descriptions for launching the startup definition profile. A sample PSF node and its subnodes in an XML file are as shown: <PSF dest="[LP]/bin/parametric.psf" id="parametric" installed="Y" name="parametric" source="psf_templates.xml> <EXE>parametric.exe</EXE> <LICTYPE name="CreoPma"><Creo Parametric</LICTYPE> <PREFIX>CREOPMA PROE</PREFIX> <DESCRIPTION>Creo Parametric (default)</DESCRIPTION> <LICENSE_IDENTIFIERS>7788@localhost</LICENSE_IDENTIFIERS> <FEATURE_NAME>CREOPMA_CUSTOMER ()</FEATURE_NAME> <DFOR_PATH>%PRO_DIRECTORY%\libs\dfor\lib</DFOR_PATH> <CV_ENV_HOME>%PRO_DIRECTORY%\%PRO_MACHINE_TYPE%\CV140</CV_ENV_HOME> </PSF> Editing the QUALITY_AGENT Node The QUALITY_AGENT node represents the Diagnostic T ools settings for an installed Creo application. Y ou can edit the following attribute of the QUALITY_ AGENT node: Installing the Creo Applications in Silent Mode 149

41. Component Application Description Note The ModuleW orks component is installed by default along with Creo Parametric. Additionally , starts the Intel MPI Service that enables parallel computing for Creo Mold Analysis. API T oolkits Creo applications and Creo Distributed Services Manager Installs the files necessary to run the Application Program Interface toolkits. Interfaces Creo Installs the external interfaces. Note T o install Creo Parametric Interface for CADDS 5 , you must also select MKS Platform Components 9.x for installation on the Application Selection screen. See Installing MKS Platform Components on page 137 for more information. Languages All the Creo applications and Creo Distributed Services Manager Selects the languages for the installation. The software is installed in English by default and cannot be disabled. Enable Diagnostic reporting All the Creo applications If enabled, collects information related to the Creo applications and other system-related information and sends it to PTC. See Installing and Configuring Diagnostic T ools on page 130 for more information on Diagnostic T ools. V erification Models Creo Simulate Installs the verification Customizing the Installation of the Creo Applications 41

40. • Click OK to finish the customization and return to the Application Selection screen. • Click Cancel . 5. Complete the installation of the Creo application. See Completing the Installation and Starting the Creo Applications on page 47 for details. Defining the Installation Components Using the Application Features tabbed page, you can define the following components for installation. Refer to the Application column for the application with which you can install the component. Component Application Description <application_name> All the Creo applications and Creo Distributed Services Manager Installs the Creo application and its components. By default, the components are installed at <creo_ loadpoint>\ <app_name> and the startup scripts are installed at <creo_loadpoint>\ <app_name>\bin . Options Creo Parametric Installs additional components such as Creo ModelCHECK, Mold Component Catalog, Creo Mold Analysis, NC-GPOST , Creo Parametric Distributed Computing Extension,and Creo Photo-Realistic Rendering with Creo Parametric, Creo Flow Analysis, and Creo T opology Optimization. See Installing Creo Mold Analysis (CMA) Component on page 42 for information on installing Creo Mold Analysis. 40 Cr eo ® Installation and Administration Guide

158. Application Environment V ariable Setting the port values. This application runs on the client workstation and uses the same host TCP/IP communication protocol for all the processes on that workstation. xtop.exe —Connects to creoagent , nmsd , and pro_ comm_msg to open a few dynamically allocated ports. This application uses the same host TCP/IP communication protocol for all the processes on a workstation. Not supported. creoagent.exe —Uses dynamically allocated ports to connect to all the Creo applications. This application uses the same host TCP/IP communication protocol for all the processes on a client workstation. Not supported. Async TK Apps—Use dynamically allocated ports to connect to pro_ comm_msg.exe on a client workstation. Not supported. Converters—Use dynamically allocated ports to connect to desktop-based Creo applications on a client workstation. Not supported. Creo V iew—Uses dynamically allocated ports to communicate with browser plugins, nmsd , and comm_brk_svc.exe on a client workstation. Not supported. 158 Cr eo ® Installation and Administration Guide

132. The tabs on the above dialog box show the configurable settings. Preferences If you have write permissions to the Diagnostic T ools installation folder and files, specify the frequency for the collection and transfer of the product and system information to PTC using the Preferences tab. Set the frequency to Daily , We ekly , Monthly , Quarterly , or Biannually . Note A user who does not have write permissions to the installation folder can view the preferences but cannot change the settings. Data Filters If you have write permissions to the Diagnostic T ools installation folder and files, click the Data Filters tab. Select specific information that you do not want to send to PTC. 132 Cr eo ® Installation and Administration Guide

53. Note The behaviour described above is new in Creo 4.0. In the previous releases older versions of Creo Platform Agent (which is now superseded by Creo Platform Services) were not automatically uninstalled or upgraded with a newer version of the same package. Creo Platform Services is a system level component which provides the following functionalities to Creo: • It acts as a broker connecting other independent Creo components. • Invokes the LearningConnector for Creo application. • Provides embedded browser infrastructure and HTTP streaming services. • Performs Creo monitoring for ExitLogger reporting. See Installing and Uninstalling Client-Side Components in Silent Mode on page 152 for instructions on performing a silent installation of Creo Platform Services. If you access Creo applications from a shared location across the network, you do not need to install Creo Platform Services on your client machine. If a Creo installation on a custom location (For Example, D:\PTC ), is relocated to a network drive (For Example, D:\PTC is exported as \\SERVER\CREO4_ Share\ ), then Creo automatically finds the creoagent executable file relative to the install location. Creo does not require the environmental variable CREO_AGENT_EXE_PATH to find the path of creoagent.exe . However , if the Creo installation structure in the network location is dif ferent from the default one, then the environmental variable CREO_AGENT_EXE_PATH must point to the file creoagent.exe . The environment variable, CREO_AGENT_LDP_LIST must also be set and must point to the manifests folder on the Platform location. (For Example, \\SERVER\CREO4_Share\Creo\Platform\4\manifests ). For local installation, the above environmental variables are not used. If Creo is started from a network install and Creo Platform Services package ( creoagent.exe and Creo platform) is installed locally and the environmental variables are not set, local installation takes precedence even if Creo finds the network installation. Using environmental variables, you can change the order of lookups. Completing the Installation and Starting the Creo Applications 53

54. Note When conditions listed below exist, set the path for the Creo Platform Services executable as the value of the CREO_AGENT_EXE_PATH environment variable: • Y ou are working on a 64-bit platform. • Y ou access a Creo application that is installed at the default installation path and is shared across a network. This ensures all dependent add-ons of the Creo Platform Services work correctly . Configuring a Creo Parametric Installation After you have installed Creo Parametric, you can perform the following operations either by setting configuration options before starting Creo Parametric or by installing the necessary components at startup • Change the units of measure by setting configuration options in your config.pro file before Creo Parametric startup • Generate a traceback log file by setting a configuration option before or after starting Creo Parametric Changing the Units of Measure for Creo Parametric Y ou can change the units of measure for your Creo Parametric installation. Use the settings in the next table to update values for the configuration options in your config.pro file: Configuration Option English Metric drawing_setup_ file <creo_loadpoint>\ \Common Files\ text\prodetail.dtl <creo_loadpoint>\ \Common Files\ text\iso.dtl format_setup_ file <creo_loadpoint>\ \Common Files\ text\prodetail.dtl <creo_loadpoint>\ \Common Files\ text\iso.dtl pro_unit_ length unit_inch unit_mm pro_unit_mass unit_pound unit_kilogram 54 Cr eo ® Installation and Administration Guide

129. • never —Does not synchronize the non-Creo model to the latest import profile. This is the default. • update —Updates the wrapper data using the latest import profile. • recreate —Discards the existing wrapper files and recreates them. The value, recreate , is supported only in Creo Distributed Batch. Synchronizing Model and W rapper Data with Import Profiles If the latest format-specific import profiles saved to disk were not used when the non-Creo models were retrieved in Creo, then the non-Creo models and their wrapper files may not synchronize with the data settings of the latest import profiles. If they are not synchronized, set the sync_data_import_profile configuration option to update so that the wrapper files are updated and they synchronize with the latest import profiles. Optionally , if you do not want to use the default import profiles, you can set the following format-specific configuration options before retrieving the non-Creo models in Creo. The values for each of the configuration options is the full path of the corresponding import profiles, including the *.dip file extension. • import_profiles_catiav5 • import_profiles_solidworks • import_profiles_nx When the non-Creo models are subsequently retrieved in Creo, the wrapper files are updated so that the non-Creo models and their wrapper files synchronize with the import profiles in use. Note Updating the non-Creo models and their wrapper files to synchronize with the import profile data settings does not change the revision of the non-Creo models stored in W indchill. System Administration Information 129

106. Extended ASCII Set ASCII is the default font in all Creo applications. Y ou can modify ASCII characters. Y ou can also replace ASCII with your own font as the default. The extended ASCII character set used in the United States and W estern Europe is supplied by Creo through a combination of two font files, ascii.src and latin_1.src . Note Characters through 146 are defined in ascii.src . The remaining characters are defined in latin_1.src . T o use the European LA TIN_1 characters, use one of the following procedures: • Make sure your keyboard is set up for the appropriate language. A specific set of LA TIN_1 characters is available with each keyboard language setting. • Use a key sequence specific to your machine type to produce the desired character . If necessary , contact your hardware vendor for additional information. Displaying the T ext Symbol Palette in Creo Parametric T o display the T ext Symbol palette: 1. Open a drawing and click Insert ▶ ▶ Note to create a note. 2. Select a location on the drawing to place the note. The T ext Symbol palette appears. 3. Click on a symbol in the palette. Alternatively , you can create a new symbol. Creo Parametric represents special symbols with standard ASCII characters. T o use special symbols in drawing notes, follow these steps: 1. Enter the sequence CTRL+A. 2. Enter the ASCII character that represents the special symbol. 3. Enter the sequence CTRL+B. When you create a new symbol, you should either redefine an existing character to the new symbol or create a new special symbol font. Y ou can add new special symbols to the font file, special.src , by defining the graphic representation. 106 Cr eo ® Installation and Administration Guide

65. Alternatively , you can copy the Help Center of an application that is installed on the local host computer in the <DocumentRoot> directory of the servlet container . For example, if you have installed Creo Parametric Help Center on the local host computer at the default path, you can copy the Help Center directory C:\ Program Files\PTC\Creo <version number>\help\creo_help_ pma to the <DocumentRoot> directory . Specify the appropriate URL as the value for the PTC_PMA_HC_URL_5 variable to access the context-sensitive Help. Note If you specify <DocumentRoot> directory as the location for the installation of the Help Center , you can access the context-sensitive help directly from this directory . Set the Help Center URL as the value of the PTC_ <app_name>_HC_URL_5 environment variable to access the context- sensitive Help through the W eb server URL. V iewing the Help Center Independent of a Creo Application T o view the Help Center that is installed on a host computer independent of the corresponding Creo application, open the following page in a browser window: <creo_help_install_path>\help\creo_help_<app>\ <language>\index.html For example, to open the Help Center for Creo Parametric in English, open the following page in a browser window: <creo_help_install_path>\help\creo_help_pma\usascii\ index.html The Help Center opens in the browser window . T o view the Help Center that is installed on a W eb server independent of the Creo application, specify the following URL in a browser window: http://<server_name>:<port_number>/Creo <version number>/help/creo_help_<app_name>/<language>/index.html For example, to open the Help Center installed on a W eb server that has the T omcat servlet container configured on port number 8080 for Creo Parametric in English, open the following page in a browser window: Installing and Accessing Creo Help 65

36. Note Required utilities for applications that you select to install, are automatically marked for installation. Y ou can deselect the Creo Thumbnail V iewer, andCreo V iew Express for installation. The MKS Platform Components 9.x is not selected by default. Before selecting applications from the list, check if you are installing the correct version of the software and whether the disk space requirements are met. Perform one of the following steps: • Click Install to install the applications without any customization. • Select the applications and click Customize to customize their installation. The Application Custom Setting screen appears with the applications selected for customization on the left pane. Refer to the chapter Customizing the Installation of the Creo Applications on page 38 for more information. Note Some of the applications on the Application Selection screen cannot be customized. For such applications, the Customize button is not available. Installation Path of Utilities Few of the required and optional utilities that you select to install with the Creo applications do not get installed at the default or custom installation path that you specify . The following is the list of required and optional utilities and their respective installation paths: • Creo Thumbnail V iewer C:\Windows\System32\thumbplug.dll • Creo Platform Services W ith default location as C:\Program Files\ W ith custom path — <installdir>\Creo\Platform • Creo V iew Express C:\Program Files\PTC\Creo <version number>\View Express • Diagnostic T ools 36 Cr eo ® Installation and Administration Guide

136. Session Log When a session of an installed Creo application ends, a session log for that application is created. Click the Pending Data or Last Sent tab on the Diagnostic T ools dialog box, and select an application tab to view the session log for that application. A session log is a list of entries that provide information about a specific session. The session log lists information related to the session ID, start and end time of the session, idle time within that session, exit type, locale, license server used, browser information, Java version, and so on for a session. Uninstalling Diagnostic T ools Y ou can remove Diagnostic T ools independent of a Creo application using the following steps: 1. Click Start ▶ ▶ Control Panel ▶ ▶ Programs and Features . The Uninstall or change a program screen appears. 2. In the application list, click Diagnostic T ools . 3. Click Uninstall . A confirmation dialog box opens. 4. Click Y es to remove Diagnostic T ools. 136 Cr eo ® Installation and Administration Guide

55. Configuration Option English Metric template_ designasm <creo_loadpoint>\ \Common Files\ templates\ inlbs_asm_design.asm <creo_loadpoint>\ \Common Files\ \templates\mmks_asm_design.asm template_ drawing <creo_loadpoint>\ \Common Files\ templates\c_drawing.drw <creo_loadpoint>\ \Common Files\ templates\a3_drawing.drw template_ sheetmetalpart <creo_loadpoint>\ \Common Files\ templates\ inlbs_part_sheetmetal. prt <creo_loadpoint>\ \Common Files\ templates\ mmks_part_sheetmetal.prt template_ solidpart <creo_loadpoint>\ \Common Files\ templates\ inlbs_part_solid.prt <creo_loadpoint>\ \Common Files\ templates\ mmks_part_solid.prt todays_date_ note_format %Mmm-%dd-%yy %dd-%Mmm-%yy tolerance_ standard ansi iso tol_mode nominal nominal weld_ui_ standard ansi iso Generating a T raceback Log File for Creo Parametric In the event of a premature exit, Creo Parametric can output a stack trace of your last operations if you set the auto_traceback configuration option to yes . The default value is no . By default, this information is stored in the traceback.log file in the startup directory . The following message appears to indicate the premature exit of Creo Parametric: Completing the Installation and Starting the Creo Applications 55

138. Overview Y ou must install MKS Platform Components 9.x along with the Creo Parametric Interface for CADDS 5 component during Creo Parametric installation to work with CADDS 5 parts and assemblies within Creo Parametric. MKS Platform Components 9.x is a third-party application that supports the following functions: • Simulates a UNIX environment on the 64-bit W indows operating systems. • Emulates UNIX commands on the W indows operating systems. • Installs the Portmapper service for interoperability between CADDS 5 and Creo Parametric. • Copies the necessary startup files and libraries required to work with CADDS 5 files into a separate installation directory . Installing MKS Platform Components Install MKS Platform components using the following instructions: 1. Perform steps 1 through 7 as described in the section Installing the Creo Applications: Simple Installation Process on page 32 . 2. Click the MKS Platform Components 9.x check box on the Application Selection screen. 3. Click Install . The Installation Progress screen indicates the progress of the installation. 4. Click Finish to complete the installation and close the Assistant. After the installation is complete, see W orking with CADDS 5 Models in Creo Parametric on page 56 before you start. Note If you want to install updated packages of MKS Platform components, you must first uninstall its existing instance. Follow the steps below to uninstall MKS Platform components: Navigate to the /cadds5_mks folder of the DVD image and run the following command: For a 64–bit system — msiexec /X cadds5_mks_for_ windows64.msi /q 138 Cr eo ® Installation and Administration Guide

42. Component Application Description models as described in the Simulation V erification Guide Help. Creo Parametric Distributed Computing Extension Creo Simulate Installs this component to run distributed computing tasks that include import/export, printing operations, and studies in case of Creo Simulate. Direct Modeling Converter Creo Parametric, Creo Simulate, Creo Direct Installs files that are required to convert and open Creo Elements/Direct files. Note Some Creo applications require the latest version of Java 8 installed on your machine. For optimal performance of Creo, install the latest version of Java 8 before you start installation. Installing Creo Mold Analysis (CMA) Component Creo Mold Analysis (CMA) is an injection molding simulation application. Y ou can use CMA to verify the part design for manufacturing to avoid the molding defects. CMA uses the IntelMPI process to launch parallel computing. The smpd-intel-4.0.3.009 – x64 or smpd-intel-4.0.3.009 – x86 process on your system verifies whether the IntelMPI is installed or not. Y ou can install IntelMPI using following procedure: 1. Open a command window as an administrator . 2. Browse to the location of the smpd-intel-4.0.3.009 – x64.exe file, for a 64–bit system. If you install the Creo Mold Analysis component with the default installation path for the Creo Parametric application, the path is C:\ Program Files\PTC\Creo <version number>\Common Files\ x86e_win64\cma\Bin\IntelMPI\ . 3. Run the executable file to start the installation process. For example, run the following command for a 64–bit system: smpd-intel-4.0.3.009-x64.exe – install 42 Cr eo ® Installation and Administration Guide

66. http://<server_name>:8080/Creo version/help/creo_help_ pma/usascii/index.html A Help Center opens in the browser window . Note Context-sensitive Help is not supported when you view the Help Center independent of a Creo application. Uninstalling the Help Center Y ou can remove the Help Center from the local host computer independent of a Creo application using the following steps: 1. Click Start ▶ ▶ Control Panel ▶ ▶ Programs and Features . The Uninstall or change a program screen appears. 2. In the application list, click Creo Help <release><date_code> for any of the Creo applications. 3. Click Uninstall . A confirmation dialog box opens. 4. Click Y es to uninstall the Help Center for the application. Note If you have uninstalled the Help Center on the host computer or have not set the PTC_<app_name>_HC_URL_5 environment variable, you can access the Help Center from PTC.com from within a Creo application. Additionally , if you uninstall or remove the Help Center from the W eb server , you must remove or unset the PTC_<app_name>_HC_URL_5 environment variable. 66 Cr eo ® Installation and Administration Guide

152. <creo_loadpoint>\<app_name>\bin\uninstall.lnk -quiet For example, to uninstall Creo Parametric in silent mode, enter the following command: C:\>"C:\Program Files\PTC\Creo <version number>Parametric\bin\uninstall.lnk" -quiet Y ou must navigate to the installation directory of each Creo application to silently uninstall it. In case the Common Files folder is installed, uninstalling the last Creo application referencing the Common Files folder removes this folder automatically . Uninstalling All Creo Applications Y ou can uninstall all the installed Creo applications and utilities of a release as a group in silent mode by running the batch file silent_Group_ Uninstall.bat from a command shell: <creo_loadpoint>\InstallManager\silent_Group_Uninstall.bat The group of all the installed Creo applications of the same release or datecode are uninstalled. This command does not impact other installed applications or utilities. Uninstalling All Utilities Y ou can uninstall all the installed utilities of a release as a group in silent mode by running the batch file Uninstall_all_utilities.bat from a command shell: <creo_loadpoint>\InstallManager\Uninstall_all_utilities.bat The group of all the installed utilities of the same release or version are uninstalled. Installing and Uninstalling Client-Side Components in Silent Mode The installers (MSIs) of the following client-side components reside on the DVD media, at path <dvd>:\install\addon\ : • Creo Platform Services • Creo Thumbnail V iewer • Creo V iew Express Only the Creo Platform Services component get installed when you perform installation of any of the Creo applications on a client computer . Refer to the following sections for the command-line syntax to run the installers for each of these components. Creo Platform Services Open a command shell and enter a command to install or uninstall Creo Platform Services in silent mode: 152 Cr eo ® Installation and Administration Guide

154. Note Running the CreoV iew_Express_32_64.msi file alone does not completely install Creo V iew Express unless certain software prerequisites are met. Microsoft C++ Runtimes, OpenGL 1.1 or later , and Arbortext IsoV iew (optional) are required for installing and running Creo V iew Express directly using the MSI file. For more information on installing and uninstalling Creo V iew Express in silent mode, see Chapter 7, Deploying Creo V iew and Customizing the Installation, in Installing Creo V iew . Installing Diagnostic T ools and MKS Platform Components in Silent Mode T o silently install Diagnostic T ools and MKS Platform Components, you must copy the qualityagent.xml and the mkscomponents.xml files found at <dvd>:\pim\xml\ to your local computer . Edit the "install=" attribute of the MSI entry to be "Y" and then perform the silent installation at the command prompt. Updating the Registry File A list of registry changes made by PTC Installation Assistant during the prototypical installation is recorded on the computer where the Creo applications are installed. The file resides at the following location: <creo_loadpoint>\<app_name>\bin\pim\xml\created.reg The created.reg file enables the seamless opening of the appropriate Creo application when you click a Creo part, assembly , or drawing file. When you upgrade the version of the Creo application or make a copy of the installation of the Creo application, you must rerun created.reg file to update the registry with the latest settings. Note If you are using W indchill and do not have Creo files outside of that network, you do not need to run the created.reg file. Use this file to perform client configuration changes (registry edits) on a client computer on which you did not run the silent installation process. For example, the client computer can be the one that runs the software from a network installation. It can also be the one that received a copy of the installation. 154 Cr eo ® Installation and Administration Guide

49. Installing and Uninstalling the Creo Applications in Silent Mode Y ou can install and uninstall all the Creo applications included in this guide in silent mode using command-line ar guments. See Installing the Creo Applications in Silent Mode on page 139 for details. Starting the Creo Applications After your license management and product software have been installed, start the Creo applications. Y ou can run the applications using the shortcut defined on your desktop or using the Start menu. Click All Programs ▶ ▶ PTC Creo and select the Creo 5.0 application that you want to start. Configuring the Creo Application Startup When you configure the startup of a Creo application, an executable file named <app>.exe , for example, parametric.exe and one or more configuration files ( .psf ) are created for each startup configuration. The configuration file contains an area where you can specify and set user -defined environment variables. This user -defined information is preserved during reconfiguration and update installations of the Creo applications. A configuration file is created when you complete the installation of a Creo application. The configuration file is created in the <creo_loadpoint>\<app_name>\ bin\ directory . Y ou can run <creo_loadpoint>\\<app_name>\bin\<app_ name>.exe to display a list of the available startup configurations. The startup command is a combination of the startup executable and the configuration file. For example, parametric.exe <filename>.psf In this case, <filename> is the name of the configuration file. A sample configuration file follows. The text is the default information that is used when you start Creo Parametric. The bold text following the // USER - PSF section is the user -defined information for starting Creo Parametric. Note Modify only the last text line of this sample configuration file. // PTC - PSF file: parametric // Completing the Installation and Starting the Creo Applications 49

131. Overview The Diagnostic T ools combines the Quality Agent and the Session Logger utilities. This tool collects information and sends reports to PTC on the performance and usage of Creo applications. It also reports the system information of a user . It serves as a medium to help PTC improve the quality of its products. Installing Diagnostic T ools The Diagnostic T ools utility is installed by default when you install any of the Creo applications. The diagnostic reporting is enabled by default for all the Creo applications. Clear the check box at the bottom of the Application Selection screen to disable this process. A single installation of Diagnostic T ools can be used with all the Creo applications for which you have enabled diagnostic reporting. Note When customizing a Creo application, if you clear the Enable PTC Diagnostic reporting check box on the Application Custom Setting screen , this selection supersedes the selection that you made on the Application Selection screen. As a result, the diagnostic reporting is not enabled in this case. Y ou can install Diagnostic T ools utility on a host computer or a network location depending on where you are installing your Creo application. If you are running a Creo application from a remote host computer or a network location, set the quality_agent_path configuration option in your config.pro to access Diagnostic T ools. Specify the complete installation path of Diagnostic T ools as the value of the configuration option. For example, C:\Program Files\PTC\ DiagnosticTools\%PRO_MACHINE_TYPE%\obj\qualityagent.exe Note Note that setting the quality_agent_path configuration option supersedes any setting that you made during installation—Diagnostic reporting is enabled regardless of the setting on the Application Selection and Application Custom Setting screens. Configuring Diagnostic T ools After installing Diagnostic T ools, you can configure it as per your company’ s requirements. T o open the Diagnostic T ools dialog box, browse to the installation path or use a previously created shortcut. Installing and Configuring Diagnostic T ools 131

62. 4. Select one or more Help Centers from the list of Help Centers. 5. Retain the default folder , for example, C:\Program Files\PTC , or click and specify the full path of an alternative folder . 6. Click Install to install the Help Center without any customization. Alternatively , click Customize to open the Application Custom Setting dialog box and customize the installation as follows: a. On the Application Features tab, select the Help Center languages to install. b. On the Shortcuts tab, specify the shortcut preferences for the Creo Help startup commands and other W indows preferences. See Configuring W indows Shortcuts on page 45 for information on how to perform these operations. 7. Click OK . 8. Click Install on the Application Selection screen. The Installation Progress screen shows the status of the installation. Y ou can click Cancel at any time to cancel the installation. 9. Click Finish . The Help Center is installed in the <help_install_path>\ PTC\Creo verion\help\creo_help_<app_name> directory . 62 Cr eo ® Installation and Administration Guide

157. Using Communication Ports Many of the Creo applications communicate with one another and with the other client applications through a TCP/IP communication protocol. Such applications must be registered in the firewall. The TCP/IP protocol uses a port as a communication endpoint in the operating system of the host computer . A port is associated with the IP address of the host computer . It is identified for each IP address and protocol by a 16-bit number commonly known as the port number . The port number for a TCP/IP communication can be allocated by a Creo application. In such cases you can configure the port number using an environment variable. If a port number is allocated dynamically by the operating system on the host computer , you cannot change the value. The port allocation for various Creo and client applications follow: Application Environment V ariable Setting Nmsd —PTC name service used by asynchronous Pro/T OOLKIT applications and Creo Distributed Services Manager to connect to Creo Parametric. This application runs on the client workstation and uses the same host TCP/IP communication protocol for all the processes on that workstation. The default port number is 1239. Set PTCNMSPORT using Control Panel ▶ ▶ System ▶ ▶ Advanced system settings ▶ ▶ Environment V ariables . Note Y ou cannot set this environment variable in your .psf file. pro_comm_msg.exe —Facilitates communication between the executable xtop.exe and asynchronous Pro/ TO OLKIT applications. Note The executable xtop.exe refers to all the desktop-based Creo applications. A port number can be allocated by a Creo application or it can be set dynamically . • 6000–Change this value by specifying a value to the PRO_COMM_ MSG_COMPAT_PORT environment variable. Either the first unused port starting with the value of PRO_COMM_ MSG_COMPAT_ PORT or of 6001, whichever is bigger , is allocated. • 2 dynamic ports—Cannot configure assigned port values after their allocation. PTC Portmapper—If installed, communicates port information between Pro/TOOLK IT and a Creo application. If it is not installed, W indows registry is used to store Not supported. Port Usage by Creo Applications 157

108. • xextent <n> —Defines the maximum number of grid spaces in the horizontal direction. • ascender <n> —Defines the number of grid spaces above the character designated for placing special characters such as accent acute and accent grave. • base_of fset <n> —Enables character alignment. The base of fset positions the text box relative to a common baseline, so the drawn character definitions appear correct relative to each other . • spec_height <n> —Defines the height of a character without the ascender above the baseline. • ics (intercharacter spacing)—T urns on and of f the ef fect of individual character width on horizontal spacing. • If you set ics to 1, each character definition must contain an individual width setting to determine the placement of the next character . • If you do not specify ics , the system assumes it is 0, and the system ignores individual width settings. • If ics = 0, the system uses fixed width character spacing. • If ics = 1, the system uses proportional width character spacing. • codeset—Identifies a font type. Codesets have the following meanings: • 0—Primary alphanumeric font set (such as ascii.src , filled.src , or leroy.src ). • 2—Extended font set (such as latin_1.src ). • 4—Special character font set or palette (such as special.src ). Note The filled font has the same codeset as ASCII. Therefore, only one or the other can exist in the font.ndx file. • polygons—T urns on character filling. • If you set it to 1, all closed polygons in the character definitions are filled (refer to the section Filled Font Definition on page 1 14 ). • If you do not specify this parameter , the system uses the default value 0. • fixed_width<n>—Can be 0 or 1. 108 Cr eo ® Installation and Administration Guide

57. Check the config_cadds.pro file for the above configuration options. If required, copy the configuration options to your local config.pro file and update their values. • Check whether the components listed below are installed: ○ Creo Parametric Interface for CADDS 5 ○ MKS platform components. See Installing MKS Platform Components on page 137 for installation instructions. ○ Portmapper that is installed as a part of the MKS platform components. Click Start ▶ ▶ Control Panel ▶ ▶ Programs and Features to open the Uninstall or change a program screen. Y ou must see PTC Portmapper as an installed program. Uninstalling Creo Applications Y ou can remove an installation of a Creo application through the Control Panel as follows: 1. Click Start ▶ ▶ Control Panel ▶ ▶ Programs and Features . The Uninstall or change a program screen appears. 2. In the application list, click the specific version of the application you want to remove. 3. Right-click Uninstall . A confirmation dialog box opens as shown in the figure below : . Completing the Installation and Starting the Creo Applications 57

118. Note If you modify the ASCII font definitions, it alters the appearance of the default font in every Creo application. How to Create a User-Defined Font File 1. Define a new font in a file with the extension .src . Store the new font in your working directory . 2. Create an index file that includes the new font file. Make sure the index file contains fonts with unique codesets. 3. Copy the compile_font command to your working area. 4. Enter the following command for each font file you create: compile_font fontfilename.src fontfilename.fnt 5. Recompile user -defined fonts whenever you install a new major release of Creo. Y ou can include user -defined fonts as default or auxiliary fonts in drawings. How to Store a New Font 1. Store the updated index file with the .src and .fnt files in your local directory if the new font is for your personal use. 2. T o make a new font available to all users, reference the font in the index and store the index and source files in the directory <creo_loadpoint>\ Common Files\text\<language> . Store the .fnt file in the following directory: <creo_loadpoint>/Common Files/<machine_type>/ text/<language> How to Set Y our Font as the Default 1. Rename your file to ascii.src . 2. Recompile the ascii.src file using the compile_font command to produce a local ascii.fnt file. How to Create or Customize a Font 1. Copy or create font source files in the local working directory . In this example, the default primary ASCII and special symbol fonts are copied and renamed. 1 18 Cr eo ® Installation and Administration Guide

153. • Install Creo Platform Services at the default location, in silent mode using the following command: "<dvd>:\install\addon\creosvcs_64.exe" /quiet • Uninstall Creo Platform Services installed at the default location, in silent mode using the following command: <dvd>:\install\addon\creosvcs_64.exe" /quiet /uninstall Creo Thumbnail Vi ewer Open a command shell and enter a command to install or uninstall Creo Thumbnail V iewer in silent mode: • Install Creo Thumbnail V iewer using the following command: "<dvd>:\install\addon\Thumbviewer_32_64.msi" /passive • Uninstall Creo Thumbnail V iewer using the following command: msiexec /uninstall "<dvd>:\install\addon\Thumbviewer_32_64.msi" /passive Creo V iew Express T o perform a silent installation of Creo V iew Express, follow these steps: 1. Deploy the application using the Creo V iew Express executable as shown in the following example: start /w <dvd>:\install\addon\pvx32_64\CreoSetup.exe /vADDLOCAL="ALL" /qn In the previous example: • /qn installs the application in silent mode • start /w starts the application from the command prompt and waits for the application to terminate If you have not specified the APPLICATIONFOLDER property , the default installation path is used. T o override this path, specify the APPLICATIONFOLDER property at the command prompt as shown in the following example: “ start /w <dvd>:\install\addon\pvx32_64\CreoSetup.exe /vADDLOCAL= ” ALL ” APPLICATIONFOLDER= ” c:\ptc\CreoViewExpress ” /qn ” T o uninstall Creo V iew Express in silent mode, enter the following command in a command shell: msiexec.exe /x <dvd>:\install\addon\pvx32_64\pvexpress\ CreoView_Express_32_64.msi /qn Installing the Creo Applications in Silent Mode 153

35. Selecting Application for Installation Select one or more applications from the list: • Creo: ○ Creo Direct ○ Creo Distributed Services Manager ○ Creo Layout ○ Creo Options Modeler ○ Creo Parametric ○ Creo Simulate ○ Creo Render Studio • PTC Mathcad: ○ PTC Mathcad Prime. ○ PTC Mathcad V iewable Support — Enables PTC Mathcad Prime when integrated with W indchill to generate PDF rendering of the worksheet. This component is required when using W indchill integration. For information on installation of standalone PTC Mathcad Prime, refer to the PTC Mathcad Prime 3.1 Installation and Administration Guide here . Note T o enable the integration of PTC Mathcad Prime with any of the Creo applications, ensure that you have installed both, the PTC Mathcad Prime and the corresponding Creo application. • Utilities: ○ Microsoft .NET Framework 4.5.1 Setup ○ Creo Platform Services ○ Creo Thumbnail V iewer ○ Creo V iew Express ○ Diagnostic T ools ○ MKS Platform Components 9.x Installing Creo Applications, PTC Mathcad, and other Utilities 35

100. T emporary Directories Creo applications use a temporary directory as defined by your system environment to store parts. Y ou can modify the location of the temporary directory by setting the temporary directory environment variable in the Creo application startup window before you run the application. This environment variable is TMP . System Management Utilities This section briefly describes the utilities for the Creo applications and FlexNet Publisher . The files listed in the next two tables are installed into the bin directory of your installation directory . Further information can be found in the FlexNet Publisher License Administration Guide . Creo Utilities Y ou can execute the Creo commands listed next, from the \<creo_ loadpoint>\<app_name>\bin directory when the license server is running. The load point is the directory where the software is installed. Command Function ptchostid Returns the PTC Host ID with required formatting used for FlexNet Publisher license codes. parametric Runs Creo Parametric. Can be user -defined. direct Runs Creo Direct. Can be user -defined. simulate Runs Creo Simulate. Can be user-defined. layout Runs Creo Layout. Can be user -defined. optionsmodeler Runs Creo Options Modeler. Can be user -defined. photorender Runs Creo Render Studio. Can be user -defined. ptcflush Releases licenses. This may be necessary if there are network problems. Formerly called proflush. 100 Cr eo ® Installation and Administration Guide

126. File Extension File T ype .pic Picture file .prt Part file .rep Report file .mfg Manufacturing file .sec Sketcher Section file On W indows, double-click a file with a registered PVX extension to open the file in Internet Explorer . Opening Creo Objects from Windows Explorer If you have not installed Creo V iew Express, you can open a Creo object directly from W indows Explorer in a Creo session. Creo objects typically appear with a PTC icon in W indows Explorer . Double-click an object in W indows Explorer to open it in a Creo session. If you have installed Creo V iew Express, a Creo object is opened in Internet Explorer only for viewing when you double-click the object in W indows Explorer . Right-click on the object and choose the Creo application in which to open the object. Y ou can open objects with the following file types: File Extension File T ype .asm Assembly file .dgm Diagram file .drw Drawing file .frm Format file .cem Layout file .mfg Manufacturing file .mrk Markup file .prt Part file .sec Sketcher Section file If a Creo session is already running and you double-click an object in W indows Explorer , the object is automatically loaded within the same Creo session in a new window . This new window becomes the active window . 126 Cr eo ® Installation and Administration Guide

121. 5. Store all the image files in the <creo_loadpoint>/Common Files/ text/resource directory . 6. Define a text symbol palette layout file and save this file in your working directory . See the next section, How to Create a T ext Symbol Palette Layout File on page 121 , for details. 7. In your config.pro file, set the value of the configuration option custom_text_symbol_palette_file to point to the full path of the customized text symbol palette layout file. For example, for a file named my_ custom_palette.txt and saved in the D:\my_parametric\my_ custom_palette.txt directory , set the configuration option as follows: custom_text_symbol_palette_file D:\my_parametric\my_ custom_palette.txt This path enables Creo Parametric to display the T ext Symbol palette according to the settings in the customized layout file. 8. Create or modify a drawing in a new session of Creo Parametric, and verify the presence of the customized T ext Symbol palette. How to Create a T ext Symbol Palette Layout File After you have created images files for the symbols that you have defined in the special font file, create a text symbol palette layout file using this procedure: 1. Create a file with .txt extension in your working directory , for example, my_custom_palette.txt . 2. Specify an integer in the first line of the file. This integer represents the number of columns in the T ext Symbol palette in Creo Parametric. 3. Specify integers on all other lines of the file. These integers must represent the ASCII codes of the symbols for the T ext Symbol palette. The integers must lie from 32–255. On every line separate each of the ASCII codes with one space. The order of the ASCII codes in the file represents the order of the symbols in the T ext Symbol palette. For additional information, see Examples of the T ext Symbol Palette Layout File on page 123 . ASCII Codes for GTOL Symbols ASCII codes for GT OL symbols are based on the setting for the gtol_ symbols_same_size detailing setup option. If you set the value to no , the ANSI codes are used to identify the special fonts to be used. If it is set to yes , the ISO codes are used to identify the special font in the T ext Symbol palette. Refer to the next table for the ANSI and ISO codes for GT OL symbols. System Administration Information 121

146. Application Files File Name File Location Creo application files <app_name>.p.xml <creo_loadpoint>\ <app_name>\bin\ pim\xml Common Files folder creobase.p.xml <creo_loadpoint>\ Common Files\ bin\pim\xml For example, if you have installed Creo Parametric, the XML file pma.p.xml is stored at <creo_loadpoint>\Parametric\bin\pim\xml . The XML file for the Common Files folder is stored at <creo_loadpoint>\Common Files\bin\pim\xml\creobase.p.xml . Editing the XML Files Y ou can edit and customize only those XML files listed in the table in the previous section with the settings required for future installations. In such cases, copy the XML files to a temporary location and edit the nodes in the XML files using a text editor or an XML editor . The following sections describe the various nodes in the XML file that can be edited. Note • PTC recommends you not to edit the XML files unless there is a specific need to do so. • Y ou can edit only those nodes that are documented in the subsequent sections. • The nodes in the XML file may dif fer for various Creo applications. Editing the PROPERTY Node Y ou can edit the following name attributes of the PROPERTY node: INST ALLBASE Use the INSTALLBASE name attribute to change the root path for installing the Creo applications in the current session. Y ou can change the INSTALLBASE name attribute in the Creo applications ( <app_name>.p.xml ) and Common Files ( creobase.p.xml ) XML files. The default value is usually the PTC folder under the Program Files folder . 146 Cr eo ® Installation and Administration Guide

104. Font Name File Name Supports Kerning Grotesque MT Bold grotesqb.ttf No Microstyle Extended microex.ttf Y es Microstyle Extended Bold microexb.ttf Y es Neographik MT neograph.ttf Y es SackersEnglishScript sackengs.ttf No Shannon shanno.ttf Y es Shannon Bold shannob.ttf Y es Shannon Extra Bold shannoeb.ttf Y es Shannon Oblique shannoo.ttf Y es Spartan Four MT sparton4.ttf Y es Spartan One T wo MT sparton12.ttf Y es Spartan One T wo MT Bold sparton12b.ttf Y es Symbol symbol.ttf No CG T riumvirate Inserat triin.ttf No If required, you can purchase additional T rueT ype and OpenT ype fonts. For information, contact Monotype Imaging at www .fonts.com . When you work with Creo applications, you use two categories of fonts: • Fonts specific to Creo applications—These fonts appear in the graphics windows of Creo applications. They define alphanumeric characters and special symbols in text files. Y ou can edit these files by: ○ Modifying the look of existing characters and symbols ○ Adding new symbols to the files ○ Creating new fonts ○ Hardware fonts—These fonts appear in the application window headers. They are machine- and language-specific. OpenT ype Font Support Creo applications provide additional support for OpenT ype fonts. These fonts are based on Unicode for multilanguage support. OpenT ype fonts of fer an expanded character set and layout features. In Creo Parametric, you can use these fonts in Sketcher to define geometry from sketched text and in Detailed Drawings to place drawing notes. OpenT ype fonts contain kerning information. Y ou can enable or disable it to adjust the spacing between letters. 104 Cr eo ® Installation and Administration Guide

145. Command Syntax Description [-translate_lp_ path_space <character>] in the installation path in the XML file. setup.exe – xml <file1> [-licfeat_regen] [Optional] Overrides the license feature list specified in the XML file. The default list is regenerated by checking the license source list as it is originally generated from an initial installation. W ithout this ar gument, the default license feature list is taken from the XML file. setup.exe – xml <file1> [-licfeat_preference <string>] [Optional] Prepends the preferred license feature names to the default license feature list. Specify the preferred names within quotes or as a space-separated list without parentheses. W ithout this arg ument, the default license feature list is used as is. setup.exe – progressbar – xml <file1> [Optional] Displays the indicative progress bar during the installation using the XML file. Consider the example of performing a silent installation of Creo Parametric with Common Files, and a required component Diagnostic T ools. Open a command shell and enter the following command: E:\setup.exe – xml “ D:\temp\ptc\pma.p.xml ” — xml “ D:\temp\ ptc\creobase.p.xml ” • E —The DVD drive letter • D:\temp\ptc\pma.p.xml —The location for the <app_name>.p.xml file. • D:\temp\ptc\creobase.p.xml —The location of the XML file for the Common Files folder . • D:\temp\ptc\qualityagent.xml —The location of the XML file for the required component Diagnostic T ools. Locating the XML Files On a successful installation of the Creo applications, XML files for each of the installed Creo applications are created. The file location and file name is as shown: Installing the Creo Applications in Silent Mode 145

120. • T o use the font as a global auxiliary font, place the .src and .ndx files in the <creo_loadpoint>\Common Files\text\<language> directory . • Then put the compiled .fnt files in the directory <creo_loadpoint>/ Common Files/<machine_type>/text/<language> . mv custom.src symbols.src myfont.ndx /usr/pro/text/ usascii mv custom.fnt symbols.fnt /usr/pro/i486_nt/text/ usascii • T o set the new font as the system default, rename the primary source and compiled font (codeset of 0) files to ascii.src and ascii.fnt , respectively . The system font.ndx file already references the ASCII font file and, therefore, does not need to be modified. Locate the new ascii.src and ascii.fnt files in the appropriate directories (see the previous section that describes how to use the font as a global auxiliary font). Note that the system overrides the original ascii.src and ascii.fnt files, unless you first rename them. The next time you start a Creo application, it uses the new custom font as the system default font. mv custom.src /usr/pro/text/usascii/ascii.src mv custom.fnt /usr/pro/i486_nt/text/usascii/ascii.fnt Customizing the T ext Symbol Palette for Creo Parametric Y ou can customize fonts and add symbols and characters to the T ext Symbol palette in Creo Parametric from the special font file. Y ou can also replace, reorder , or remove symbols using the text symbol palette layout file. How to Add New Symbols to the T ext Symbol Palette 1. Customize the special font file, special.src , using the method described in the section Using Fonts on page 102 . 2. Add a definition for each of the new symbols that you want to insert in the T ext Symbol palette and associate an ASCII code to the symbol. 3. Create new images for each of the symbols that you have defined in the customized special font file. 4. Save the images as sp_#.gif where # is the ASCII code of the image defined in the special font file. For example, you can save an image as sp_ 133.gif , where 133 is the ASCII code that is associated with the image. 120 Cr eo ® Installation and Administration Guide

159. Application Environment V ariable Setting comm_brk_svc.exe —Uses dynamically allocated ports to support communication between xtop.exe , third-party CAD software, and Creo V iew sessions. Not supported. Creo Distributed Services Manager—Uses the TCP/IP communication protocols between multiple workstations. • The executable dbatchc.exe is the dbatch client interface that runs on a client workstation. This interface communicates with the Service Manager dsq.exe located on a dif ferent workstation. • The dbatch service executable dbatchs.exe runs on a service workstation. • The executable dsq.exe uses a dynamic port to communicate with dbatchc.exe and multiple dbatchs.exe processes. Each service workstation runs nmsd.exe . Set PTCNMSPORT using Control Panel ▶ ▶ System ▶ ▶ Advanced system settings ▶ ▶ Environment V ariables to configure the default port number . Make sure that you set the same port number value on all the service workstations. Port Usage for PTC License Server PTC License Server runs on a designated server and requires a two-way TCP/IP communication between the client workstation and the server . The default port 7788 is used by the lmgrd and the lmadamin license server managers. The vendor daemon ptc_d dynamically selects an available port. Y ou can designate a port value other than the default value for lmgrd , lmadamin , and ptc_d using the procedures given in the subsequent sections. After designating appropriate port values for these applications, you must register the values in the firewall. Otherwise license transactions will not happen. Port Usage by Creo Applications 159

150. Attribute V alue enable Enables or disables the diagnostic reporting for a Creo application. For example, if this attribute is set to Y , diagnostic reporting is enabled. Note If the required attribute is set to Y , you must not change the value of the enable attribute to N . If you do so, the Creo application will not run because of conflicting settings. A sample QUALITY_AGENT node in an XML file is as shown: <QUALITY_AGENT enable="Y" keyname="QualityAgentOptIn" required="N"/> Editing the LANGUAGE Node Note Editing the LANGUAGE , PLATFORM , and PACKAGE nodes is not trivial. For editing these nodes you must manually edit the CDSECTION nodes. Instead, PTC recommends that you perform a template-based installation graphically with the required language, platform, and package settings. A LANGUAGE node represents the languages supported on the DVD media for the installation of a Creo application. Individual LANGUAGE nodes are created in the XML file for each of the supported languages. Y ou can edit the following attribute of the LANGUAGE node: Attribute V alue install Set this attribute to Y or N depending on whether you want to install the Creo application in that language. If the required attribute is set to Y do not change the install attribute. A sample LANGUAGE node in an XML file follows: <LANGUAGE install="Y" installed="N" name="usascii" required="Y">English</LANGUAGE> <LANGUAGE install="N" installed="N" name="japanese">Japanese</LANGUAGE> 150 Cr eo ® Installation and Administration Guide

103. The following table lists the T rueT ype fonts, their corresponding file names, and whether the font supports kerning. Kerning controls the space between certain pairs of characters, improving the appearance of the text string. Kerning is a characteristic of the particular font. Font Name File Name Supports Kerning Blueprint MT bluprnt.ttf No Blueprint MT Bold bluprntb.ttf No CG Century Schoolbook schlbk.ttf Y es CG Century Schoolbook Bold schlbkb.ttf Y es CG Century Schoolbook Bold Italic schlbkbi.ttf Y es CG Century Schoolbook Italic schlbki.ttf Y es CG Omega cgomg.ttf No CG Omega Bold cgomgb.ttf No CG Omega Bold Italic cgomgbi.ttf No CG Omega Italic cgomgbit.ttf No CG T imes cgtime.ttf No CG T imes Bold cgtimebd.ttf No CG T imes Bold Italic cgtimebi.ttf No CG T imes Italic cgtimeit.ttf No CG T riumvirate trium.ttf Y es CG T riumvirate Bold triumb.ttf Y es CG T riumvirate Bold Italic triumbi.ttf Y es CG T riumvirate Condensed Bold triumcb.ttf Y es CG T riumvirate Italic triumi.ttf Y es Garamond Kursiv garamdi.ttf No Garamond Halbfett garamdb.ttf No Garamond Antiqua garamd.ttf No Garamond Kursiv Halbfett garamdbi.ttf No Garth Graphic gargra.ttf Y es Garth Graphic Black gargrabl.ttf Y es Garth Graphic Bold Italic gargrabi.ttf Y es Garth Graphic Italic gargrai.ttf Y es Grotesque MT grotesq.ttf No System Administration Information 103

151. Editing the P ACKAGE Node PACKAGE nodes in an XML file represent the required and the optional packages selected for a Creo application on the Customize dialog box of the Assistant. There may be many PACKAGE nodes in an XML file. Y ou can edit the following attribute of the PACKAGE node: Attribute V alue install For a specific PACKAGE node, set this attribute to Y or N depending on whether you want to install the package with the Creo application. For a parent package with multiple child packages, set the install attribute of the parent package to Y to install any of its child packages. A sample PACKAGE node in an XML file follows: <PACKAGE hidden="N" install="Y" label="ModelCHECK name="modelcheck" parent="creooptions" required="N"> </PACKAGE> Editing the CDSECTION Nodes Edit the CDSECTION node only if you want to edit the LANGUAGE , PLATFORM , or the PACKAGE nodes. Check for the following attributes before you edit the CDSECTION nodes: • For each LANGUAGE node, locate the CDSECTION nodes with the language attribute reflecting the appropriate language. • Then locate the CDSECTION nodes with the platform attribute reflecting the appropriate operating system. • Finally locate the CDSECTION nodes with the name attribute reflecting the package to be installed with the Creo application. If all the attributes for the above nodes are to be considered for the installation, set the install attribute of the CDSECTION node to Y . Otherwise, set the attribute to N . A sample CDSECTION node in an XML file follows: <CDSECTION install="Y" installed="Y" location="[CREOCOMMONFILES]/[SHIPCODE]" name="ModelCHECK" size="7126314> Uninstalling the Creo Applications in Silent Mode Y ou can uninstall the Creo applications in silent mode by entering the following command for each of the applications in a command shell: Installing the Creo Applications in Silent Mode 151

63. For example, if you specify the default path, the Help Center is installed in the C:\Program Files\PTC\Creo version\help\creo_help_ <app_name> directory . Enabling the Help Center from a Network Drive T o enable the Help Center that is installed on a network drive, you must configure the Creo application as explained in the following example: 1. If you have installed the Help Center on computer machine03d at C:\ Program Files\PTC\<Creo 5.0.0.0\help , share the folder C:\ Program Files\PTC\Creo 5.0.0.0 as: \\machine03d\Creo 5.0.0.0 . 2. On a client computer where you want to access the Help Center , map the shared folder to a local drive, say Q . After mapping, the folder with the Help installation files appears as Q:\Help\help\creo_help_<app_name> . 3. Set the PTC_<app_name>_HC_URL_5 environment variable for the Creo applications as listed: • Creo Parametric— PTC_PMA_HC_URL_5 • Creo Direct— PTC_DMA_HC_URL_5 • Creo Layout— PTC_LCD_HC_URL_5 • Creo Simulate— PTC_SIM_HC_URL_5 • Creo Options Modeler— PTC_OPTM_HC_URL_5 • Creo Render Studio— PTC_RENDER_HC_URL_5 a. Click Start ▶ ▶ Control Panel ▶ ▶ System ▶ ▶ Advanced system settings . The System Properties dialog box opens. b. Click the Advanced tab and then click Environment V ariables . c. Click New under the User variables area. The New User V ariable dialog box opens. d. Specify the environment variable and its value in the boxes listed below . For example, for Creo Parametric Help, set the environment variable as follows: • V ariable name — PTC_PMA_HC_URL_5 • V ariable value — Q:\Help\help\creo_help_pma e. Click OK and again click OK on the System Properties dialog box. 4. Start the Creo application and access Help. Installing and Accessing Creo Help 63

144. edit it as required. See Editing the XML Files on page 146 for information on how to edit the various nodes of an XML file. 3. Perform a silent installation of the desired Creo applications using the command syntax as described in the next section. 4. Perform a silent installation of the required client-side components. See Installing and Uninstalling Client-Side Components in Silent Mode on page 152 for information on how to install Client-side components. Command Syntax for a Silent Installation T o perform a silent installation of a Creo application, open a command shell, and run setup.exe from the root directory of the DVD as follows: <dvd>:\setup.exe – xml “ <path to the .xml file stored in a temporary location> ” Where dvd is the DVD drive letter or the location of the downloaded DVD image. The arg uments you can use with setup.exe during a silent installation follow: Command Syntax Description setup.exe <no arg uments> Runs the installer interactively . setup.exe – help Displays all the arg uments to use with the installer . setup.exe – v Displays the version of the installer . setup.exe – xml <file1> – xml <file2>.... Performs a silent installation as per the directives in the specified XML files. setup.exe – upgrade – xml <file1> – xml <file2>.... Performs a silent installation with the removal of the highest version that already exists, and installs the current version of a release, according to the instructions in the specified XML files. setup.exe – xmlall “ <path to the.xml files stored in a common temporary location> ” Performs a silent installation of all the applications as per the directives specified in the XML files that are all stored in a common folder . setup.exe – xml <file1> [ – destination <directory>] [Optional] Overrides the destination specified in the XML file. setup.exe – xml <file1> [-licensesource <string>] [Optional] Overrides the license source specified in the XML file. setup.exe – xml <file1> [Optional] Replaces the whitespace characters 144 Cr eo ® Installation and Administration Guide

64. Installing the Help Center on a W eb Server Y ou can install the Help Center on any W eb server . If you are using Apache, install the Help Center in the Document Root directory as follows: 1. Perform steps 1 through 4 as described in Installing the Help Center on page 61 . 2. Specify <DocumentRoot> as the installation path. 3. Click OK and click Install on the Application Selection screen. The selected application help is installed in the <DocumentRoot>\Creo <version number>\help\creo_help_<app_name> directory . 4. T o distribute the Help Center files from the <DocumentRoot>\Creo <version number>\help\creo_help_<app_name> directory for context sensitive Help access, set the PTC_<app_name>_HC_URL_5 environment variable for the Creo applications as listed: • Creo Parametric— PTC_PMA_HC_URL_5 • Creo Direct— PTC_DMA_HC_URL_5 • Creo Layout— PTC_LCD_HC_URL_5 • Creo Simulate— PTC_SIM_HC_URL_5 • Creo Options Modeler— PTC_OPTM_HC_URL_5 • Creo Render Studio— PTC_RENDER_HC_URL_5 a. Click Start ▶ ▶ Control Panel ▶ ▶ System ▶ ▶ Advanced system settings . The System Properties dialog box opens. b. Click the Advanced tab and then click Environment V ariables . c. Click New under the User variables area. The New User V ariable dialog box opens. d. Specify the environment variable and its value in the boxes listed below . For example, for Creo Parametric Help, set the environment variable as follows: • V ariable name — PTC_<app_name>_HC_URL_5 • V ariable value — <Help_Center URL> For example, for a Help Center installed on Apache server configured on port number 8080 , the Help Center URL is http://<server_ name>:8080/Creo <version number>/help/creo_help_ <app_name> . e. Click OK and again click OK on the System Properties dialog box. 64 Cr eo ® Installation and Administration Guide

147. Note Ensure that you specify same root path in the Creo applications ( <app_ name>.p.xml ) and Common Files ( creobase.p.xml ) XML files. • Before editing the INSTALLBASE name attribute, the PROPERTY node appears as shown: <PROPERTY name="[INSTALLBASE]">"F:Program Files\PTC"</PROPERTY> • After editing the INSTALLBASE name attribute, the PROPERTY node appears as shown: <PROPERTY name="[INSTALLBASE]">"[PROGRAMFILES]\PTC"</PROPERTY> The [PROGRAMFILES] variable in the above example represents the default program location on a local computer . Y ou can use this variable instead of the absolute path F:\Program Files to make the default program location accessible on all the computers. For a 32-bit application running on a 64-bit computer , you can also use the [PROGRAMFILESx86] variable as shown in the following example: <PROPERTY name="[INSTALLBASE]">"[PROGRAMFILESx86]\PTC"</PROPERTY> The [PROGRAMFILESx86 variable represents the default program location for a 32-bit application on a 64-bit computer . NoRegistryActions Y ou can add the NoRegistryActions name attribute to skip processing of the REGISTRY nodes. REGISTRY nodes define file associations. <PROPERTY name="NoRegistryActions"</PROPERTY> LP and CREOCOMMONFILES The permitted editing of the LP and CREOCOMMONFILES property values is limited to changing or removing the whitespace characters. For example, you can change Creo [VERSION] to Creo_[VERSION] . Similarly , you can change Common Files to Common_Files or CommonFiles . Y ou must not modify any other aspects of the LP or CREOCOMMONFILES paths. Before editing these property values, the PROPERTY node appears as shown: <PROPERTY name="[CREOCOMMONFILES]"[INSTALLBASE]/Creo [VERSION]/[COMMONFILESNAME]</PROPERTY> <PROPERTY name="[LP]">[CREOCOMMONFILES]</PROPERTY> After editing the LP and CREOCOMMONFILES property values, the PROPERTY node appears as shown: <PROPERTY name="[CREOCOMMONFILES]"[INSTALLBASE]/Creo_[VERSION]/[COMMONFILESNAME]</PROPERTY> <PROPERTY name="[LP]">[CREOCOMMONFILES]</PROPERTY> Installing the Creo Applications in Silent Mode 147

#### Views

• 1159 Total Views
• 929 Website Views
• 230 Embedded Views

#### Actions

• 0 Social Shares
• 0 Likes
• 0 Dislikes