Product Lifecycle Management (PLM)PDMLink 8.0 M020 with Pro/ENGINEER Wildfire 2 M200 User GuideAuthor:PLM TeamRevision:AFile Ref:Status:Modified:Creation2010-02-25DOCUMENT FILE NAME: d:\data\personal\business\psion\plm\implentation scope\training\pdmlink proewildfire user guide.docPAGE: 1 OF 33

Table of ContentsPDMLINK 8.0 M020 WITH PRO/ENGINEER WILDFIRE 2 M200 USER GUIDE1TABLE OF CONTENTS214SOFTWARE CONFIGURATION1.1 Recommendations2CLIENT WORKSTATION CONFIGURATION2. X Security Options Enabled on a Windows Internet BrowserClearing Pro/ENGINEER Workspace Cache (workstation and client login dependent)Clearing JRE Cache (workstation and client login dependent)Product View Standalone ClientPRO/E WILDFIRE INTEGRATED WITH PDMLINK3. Registry ConfigurationCreate Workspace for Pro/E Wildfire ClientsUploading and Checking In Pro/E Wildfire Standard Library Model FilesDeletion of WorkspacePRO/E WILDFIRE CONFIGURATION58891111131418204.1 Cache4. LocationCache Size21224. to Last Workspace22Model Display in Pro/E Client22File Compression for Upload and Download22Default Web Page22PDMLink Registry Server Connection Retries22Concurrent Download Threads23Automatic Upload to the Primary PDMLink server User’s Personal Cabinet Workspace folder in theDatabase234.9 Automatic Upload to the other Secondary PDMLink servers User’s Personal Cabinet Workspace folderin the Database234.10 File Retrieval Options235CUSTOMIZATIONS TO PDMLINK SERVER5.1 Automated Part Creation25266ACCESS CONTROLS ON LIBRARY DOMAINS IN PDMLINK307BEST PRACTICES WITH THE CURRENT PDMLINK FUNCTIONALITY33PAGE: 2 OF 33

INTRODUCTIONWindchill PDMLink Pro/ENGINEER (Pro/E) Wildfire Extension is the ability to manage and control your data.PDMLink Pro/E Wildfire Extension delivers data management capabilities within the PDMLink environment. Itunderstands Pro/E files and all their detailed inter-relationships.Product Capabilities: Maintain and organize secure data through the use of ORACLE technology Access database tools for easily finding and re-using data, attributes, system-wide renames, lifecycletracking and release controls Integrate Pro/E designs, relationships and functionality with Windchill PDMLink Product Structure Work with specific product configurations and incorporate design changes and conflicts from manysources Communicate design status, release procedure status, activity and intent of other users to entire designteam, enabling rapid local changesCustomer Benefits: Increased efficiency through a common working environment for Pro/ENGINEER users Ensured data integrity through secure access to data and design history Quicker time to market through effectively managed design changes and avoidance of design conflicts Increased productivity of engineers through simplified information management Shared engineering data with enterprise systems through Web-based environmentPAGE: 3 OF 33

1 Software ConfigurationThe base PTC components of this entire configuration is:PDMLink Server Products Release 10GApacheTomcatAphelionJava(TM) 2 SDK, Enterprise Edition 1.4.2 10international versionJava 3D for 1.3.1PDMLink Foundation 8.0Windchill Visualization ServiceBoth Language Pack CDsService Pack M020RetrievalWareCAD WorkerPro/E Wildfire 2ProductView CAD Adapters M020 for Pro/E WildfireWindows File Transfer Protocol in Internet Information Services onlyPro/ENGINEER Wildfire ClientsInternet Explorer with all active X enabled in internet security optionsProductView Standard Edition M020 for Windchill PDMLinkJava(TM) 2, Runtime Environment 1.4.2Pro/ENGINEER Wildfire 2 M200NOTE: You will need at least one licenses of Pro/ENGINEER, for the CAD WorkerSince Apache Web Server, Tomcat Servlet Engine, Info*Engine, Excalibur RetrievalWare and PDMLink, are placed onthe same server, the recommended minimum amount of RAM is 2 GIGs for production.1.1 RecommendationsIt is best to have the CAD Worker on a separate machine because it requires a considerable amount of resources tocreate the ProductView viewables from Pro/E.PAGE: 4 OF 33

2 Client Workstation ConfigurationTo perform administrative configuration on the PDMLink server and properly use the ProductView Express, StandardEdition and Lite versions via the web browser, ActiveX security controls must be configured on the clients InternetExplorer. To properly display PDMLink applets, a Java(TM) 2, Runtime Environment 1.4.2 10 software is be installedon each clients machine.2.1 Active X Security Options Enabled on a Windows Internet BrowserTo view thumbnails and ProductView viewables and thumbnails in various ProductView applications, the WindowsExplorer security options must be configured for ActiveX controls. The configurations are as follows:1. In the Menu Bar of the Windows Internet Explorer, select the Tools drop down list and select the Internet Options.2. In ther General Tab, delete all TemporaryInternet files and reset the settings.PAGE: 5 OF 33

3. In the Internet Options, select on CustomLevel button for the setting of Trusted Sitesand Local intranet.4. Enable the ActiveX controls according tobelow and select OK button:PAGE: 6 OF 33

PAGE: 7 OF 33

4. Disable Pop-up Blocker2.2 Clearing Pro/ENGINEER Workspace Cache (workstation and client login dependent)In your respective Application Data folder, delete the “.wf” directory:C:\Documents and Settings\ your user name \Application Data\PTC\ProENGINEER\Wildfire\.wf2.3 Clearing JRE Cache (workstation and client login dependent)PAGE: 8 OF 33

2.4 Product View Standalone ClientPAGE: 9 OF 33

PAGE: 10 OF 33

3 Pro/E Wildfire Integrated With PDMLinkPro/E Wildfire has an embedded web browser. Pro/E Wildfire’s embedded web browser allows the Pro/E user to use oneinterface to perform most of engineering functions. In order to have Pro/E drawings, assemblies and parts to be managedby PDMLink, each client of Pro/E must communicate to PDMLink via a registry server service in PDMLink. Currently,there is no functionality of renumbering. It is best practice to ensure that the Pro/E file has a correct part, assembly ordrawing number prior to uploading. It is best to work on the files locally. All required start files are managed in thePDMLink database.3.1 Server Registry ConfigurationPro/E Wildfire can connect to multiple PDMLink/Windchill servers. The Pro/E clients at Asahi Matsushita are onlyrequired to connect to one PDMLink server called The next steps will properly show how to connectto In the menu bar, select Tools then Server Registry.PAGE: 11 OF 33

2. A Server Registry applet will appear to connect to the PDMLink server. Select the Add button.3. In the Register new server applet, enter plm and plm/Windchill for values of Name and location respectively.Select the Check button and log in applet prompt an authentication.PAGE: 12 OF 33

4. If there are no workspaces in the user’s personal cabinet, the only selection is the default workspace. Select theOK button. To integrate the Pro/E client with the PDMLink server, select the Set button with alias highlighted.3.2 Create Workspace for Pro/E Wildfire ClientsFor every PDMLink user, there exist a hidden personal cabinet in the database. A workspace is a directory or folderwithin that user’s personal cabinet. There are many default functionality of Pro/E Wildfire integrated PDMLink. Theyare:a) Files can be uploaded into the workspace and the PDMLink number and name will be assigned the complete filename with the extension. In section 7, customizations are discussed to remove the extensions from thePDMLink number and name for WTParts.b) Cannot browse to CAD document templates via Pro/E Wildfire configuration tool.c) Cannot delete WTParts and CAD documents.d) Cannot renumber or rename parts.e) The name and description PDMLink system attribute is a non-versioned or iterative attribute.f) Because the workspaces are in the database, every object regardless of location has to be unique; therefore,objects can’t be located in multiple locations or workspaces. The methodology is to download.g) No Uploading in Default WSh) Cannot delete workspace if the workspace is still set or the PDMLink server is set on server registry.Because of default functionality, it is best to keep the workspaces of each user to a minimum.1. To create a workspace, select theWorkspace tab in the Server Registryapplet. Then select the New button.2. Enter Std Library for name of theworkspace and then select the OKbutton.PAGE: 13 OF 33

3. Finally, highlight the Std Library workspace and select the Set button and then Close tocomplete the integration.3.3 Uploading and Checking In Pro/E Wildfire Standard Library Model FilesWhen implementing Pro/E with a PDM system, it is best practice to manage Pro/E model files in the PDM database. Asa result, history and control of all Pro/E model based files in a database would be part of the methodology. It is bestpractice to store the Pro/E modeled standard library files in a library container that will be shared by all end users. Also,all the configurations are stored Pro/E standard library model files in CAD documents objects in PDMLink. These filesmust be uploaded and checked into the ProE Std Library library container. The following steps will describe how tocomplete this task with the template solid model startwildfire.prt.1. Open the startwildfire.prt where it resides on the Std Library server in the directory and select the save option.Delete any Pro/E user defined parameters that are redundant to the PDMLink’s Pro/E controlled parameters.Also, it is best practice to rename any parameters that are spelled the same as the PDMLink system attributes.PAGE: 14 OF 33

2. In the menu bar under File, select the Save and Upload. The upload function will save the file into a CADdocument with the PDMLink number and name with the file name startpartwildfire.prt. Uploading it to thedatabase will also assign a PDMLink revision/version and iteration value.PAGE: 15 OF 33

3. A new CAD Document startpartwildfire.prt is now present in the Std Library workspace. This CAD documentobject will be checked into the library container called ProE Std Library. Select the startpartwildfire.prt bychecking the check box then select the check in iconin either the workspace menu or in the Actionsoptions.4. A check in window will appear in the embedded browser. Update the location for object to check.PAGE: 16 OF 33

5. Browse to the through the PDMLink repositories and select the ProE Std Library library container.PAGE: 17 OF 33

6. Finally select OK after highlighting the ProE Std Library.The check in page will refresh with the new location and then select OK.It is best practice to check in all Pro/E model files in the ProE Std Library in the PDMLink database that are locatedin the following local directories: ProE Std Wildfire \formats ProE Std Wildfire \library ProE Std Wildfire \start filesThe remaining files are only for the Pro/E software application. These files are to be stored in the shared local harddrive H:\.3.4 Deletion of WorkspaceTo keep Workspaces to a minimum, it is advisable to delete workspaces. To properly delete workspaces, there are 2prerequisites:a) The workspace to be deleted is not set.b) If it is the only workspace, the PDMLink registry server alias is not set.c) The workspace has to be empty of objects.In the Home tab of the Windchill-PDMLink page and check the workspace to be deleted then select the DeleteWorkspace icon.PAGE: 18 OF 33

PAGE: 19 OF 33

4 Pro/E Wildfire ConfigurationThe standard Pro/E Wildfire configuration file,, which is located in ProE Std Wildfire \configsis copied to all local clients installations of Pro/E. This must be modified to incorporate a PDMLink databasemanagement methodology. All configurations will be performed through the Pro/E interface.PAGE: 20 OF 33

4.1 CacheCache is used for temporary storage for the Pro/E Workspaces. This increases the performance of retrieving data in youPro/E session rather than searching it elsewhere.4.1.1Cache LocationCache directory is a fixed directory where there is large local shared space for all users. All users will require fullaccess to this directory. It is recommended place cache on local disk where there are no OS and other applicationsinstalled. This will avoid OS or application failure. It is recommended to create a system environment variable called:TMP directory location (not a network directory for better performance)PROE CACHE directory location (if possible another local drive)The following lines must be added to the to enable the cache locations.PTC WF ROOT TMPPTC WF CACHE PROE CACHEPAGE: 21 OF 33

4.1.2Cache SizeThe default cache size is 400 MEG per workspace. If you would like to state another value to be tailored to the limitsof you machine and the number of workspaces created by all users. Administrators should allocate disk space by thisformula# of Pro/E users per workstation X average number of workspaces X cache size X 2 total cache spacedm cache size 400 (set at 400 MEG for each workspace)4.2 Reset to Last WorkspaceWhen exiting and opening Pro/E, a configuration option can be set to his last accessed workspace. The default is set totrue (YES). The other option is NO. The configuration property is:dm remember server YES4.3 Model Display in Pro/E ClientSet the following for the thumbnail view for the ProductView Express functionality in the embedded model display shading lodboth4.4 File Compression for Upload and DownloadInteger, from 0 (no compression) to 9 (maximum compression) [default 0] Sets the level of compression for dataupload and download. Although compression speeds up transfer over the network, it uses server CPU and client CPU toperform the compress and decompress operations. In a local area network, where network transfers are rapid,compressing and decompressing data can result in lesser throughput. On wide area network with lower bandwidthcompression can lead to higher throughput. Since this is set per client, PTC recommends that clients in a LAN use avalue of 0 (the default) and clients in a WAN use a value of 2 or 3.There is a balance between Pro/E Client performance and network throughput and data storage. Pro/E Client bestperformance is at no compression while the best performance in a network and database file throughput and retrievalrespectively is at maximum compression. At , the configuration option was set to http compression level 54.5 Default Web PageThe default web page can be set by this property:web browser homepage http:// PDMLink Registry Server Connection RetriesThe default number of attempts to connect to the PDMLink Registry connections after a failure is 10 times. Thisconfiguration sets the number of attempts to connect to a PDMLink server before the connection is considered broken.PAGE: 22 OF 33

(This is a hidden config option that was introduced in Pro/ENGINEER Wildfire date code 2003210.) The recommendedsetting is the default. If the http connection is unstable, a setting less than the default could increase failures, while asetting greater than the default causes delays if a failure occurs. In , the configuration value was set to network retries 54.7 Concurrent Download ThreadsThe default value for this configuration option is 3. This option sets the number of concurrent threads Pro/ENGINEERuses for downloading data from a PDMLink server. In most cases, increasing the number of threads in a LANenvironment will not improve performance, as the disk will then become the bottleneck. Even in a WAN environment,settings greater than the default are unlikely to improve throughput significantly. (This is a hidden config option that wasintroduced in Pro/ENGINEER Wildfire date code 2003210.) PTC recommends this option to be network threads 34.8 Automatic Upload to the Primary PDMLink server User’s Personal Cabinet Workspace folder in theDatabaseThis configuration option defines the behavior of the Save command in Pro/ENGINEER. If this option is set to explicit,the Pro/ENGINEER File Save command will write data to the local disk space and cache. The user must thenexplicitly upload/send that data to the PDMLink server (using either File Save and Upload, File Upload, or File Checkin). If this option is set to automatic, File Save in Pro/ENGINEER will also upload the Pro/ENGINEER filesto the PDMLink User’s Personal Cabinet Workspace folder. For best practices, PTC recommends that this value is setto automatic when connected to a PDMLink server. Files will be both saved on the database and locally on upload objects automatic4.9 Automatic Upload to the other Secondary PDMLink servers User’s Personal Cabinet Workspace folder inthe DatabasePro/E Wildfire can connect to multiple PDMLink servers, this option defines the behavior of saving to a secondaryserver (See also dm upload objects).dm secondary upload automatic4.10 File Retrieval OptionsTo ensure that the setting files are securely located and readily available, it is recommended to store setting files in thePDMLink Oracle database. Thus, history in changes will be maintained and proper security controls are placed for CADadministration methodology. The setting files are checkin to a read accessible Pro/E standards Library container inPDMLink. The options that specify storage and retrieval directories, including such options as the following: start model dir pro library dir pro format dircan be set to point to Windchill cabinets. For example, the value of start model dir is set to point to a WindchillPDMLink library container cabinet using the following syntax:start model dir wtpub:// server alias /Library/ library container name PAGE: 23 OF 33

Since all the files were stored in a single library container, the configuration is as follows:start model dir wtpub:// Stds Libraryfor all the directories as stated above.Note: If you retrieve an object from any location other than the primary server, it will be treated as if it were newlycreated in the Pro/ENGINEER session. This means that actions on the object (for example, save or requesting checkout)are done in the context of the primary server, not the location from which the object was options that point to a specific file, including such options as the following: intf in use template models template designasm template mold layout template ecadprt template solidpartcan be set to point to Windchill file locations using a string of the proper syntax and the name of the CAD document thatmanages the file, as in the following example:template solidpart wtpub:// server alias /Repositories/Templates/template solid inlbs.prtIn , the configuration is as follows for the template solidpart:template solidpart wtpub:// Stds Library/startpartwildfire.prtThe other templates configurations have been modified to their respective CAD documents:template sheetmetalpart wtpub:// Stds Library/ startpartsheet wildfire.prttemplate designasm wtpub:// Stds Library/ startasmwildfire.asmPAGE: 24 OF 33

5 Customizations to PDMLink ServerCurrently by default, PDMLink assigns the PDMLink number and name system attributes of the WTPart and CADdocument to the Pro/E file name with the extension.As a result, the product structure or bill of material will be displayed in the WTPart assembly as shown below:PAGE: 25 OF 33

To avoid this default behaviour, small customizations are added to the PDMLink codebase. To ensure Pro/E standardlibrary repositories, products and templates have to be created in PDMLink. Some ‘ini’ files are modified to ensure th