You are on page 1of 22

Pro/E Wildfire Connectivity Architecture

PDMLink Integration

Pro/E Wildfire Connectivity Architecture
Major Components of the Architecture
– User Model – File Management – Communications Architecture

Architecture Goals

© 2006 PTC

Major Components Of The Architecture The next few slides will cover the following major Architectural components in more detail: User Model The Console Pro/E Menus Navigator Model Tree Html UI Windchill Server File Management File Abstraction Location Cache http Cache storage Communications SOAP Services Data storage Workstation Disk Pro/ENGINEER Session © 2006 PTC .

User Model – PDMLink Access Points PDMLink Access points Pro/E Menus The Navigator The Model Tree The Browser © 2006 PTC .

Status and Debug level information © 2006 PTC . Information. a console is required.TheConsole Because many operations occur asynchronously. The console… Provides progress for and logs output from asynchronous activities for later review by the user Identifies any conflicts with suggested resolutions and tasks to be resubmitted Is accessed from the Pro/E UI – Tools->Console Menu – Console icon ( ) in Pro/E status bar Shows in the browser One for each registered server Can be configured to show Errors.User Model . Warnings.

“Component>Assemble”) to be extended to Internet locations – Pro/E requests a file from a “location” & the driver implements the logic to get the file for Pro/E PFA Pro/ENGINEER application layer Location independent abstract file management layer Location specific driver Disk FTP HTTP Windchill Existing file system driver New drivers added with Pro/E Wildfire © 2006 PTC . “. http.File Management Architecture File Abstraction Pro/E uses file system files to persist model data (e.g. “.prt”.g. Windchill) – Allows existing Pro/E functionality (e.asm”) Pro/E Wildfire added “location” drivers for Internet Locations (ftp.

File Management Architecture – Location Drivers Declaring a New Location Location drivers get initialized by Pro/E when a user adds a new “Location” 1. Select “Tools-> Server Registry” 2. Component->Assemble etc. Select “Add” 3. making the nature of the location transparent to the Pro/E user. File->Save. Enter an alias And the server URL The new location now appears to Pro/E as a new “disk” and is accessible through File->Open. ProjectLink Project PDMLink Server Second PDMLink Server Windchill Foundation Server FTP Site Hard Disk © 2006 PTC .

User can continue to work in Pro/E http 2. Results of the transaction are written to the Pro/E console Data storage Workstation Disk © 2006 PTC . Pro/E writes the data to the cache 4.Caching Pro/E Wildfire utilizes a cache to: Improve system responsiveness Optimize data upload/download Ensue data integrity Windchill Server 1. Pro/E uploads the data in a background thread(s) Cache storage Pro/ENGINEER Session 5. User chooses File->Checkin from Pro/E menu 3.File Management Architecture .

File Management Architecture .Caching Windchill Server Cache storage Pro/ENGINEER Session Workstation Disk Private Folder Shared Folder Save Upload Checkin Save & Upload Download Checkout © 2006 PTC .

Architecture: Runtime View (Open in Pro/E) Client (Pro/Engineer) Pro/ENGINEER Session Pro/ENGINEER Opens from cache PDMLink Server Workspace In Cache? N Retrieve from Workspace In Workspace? Y Retrieve from Workspace Y Retrieve from cache Windchill Public Folder Cache storage N Add to workspace from Public Folder © 2006 PTC .

OpenModel (http://URL) PDMLink Server Download Service Metadata and URL for content URL Client Connector CAD files Replica Site © 2006 PTC .Architecture: Runtime View (Open from html page) Client (Pro/Engineer) Java Script Bridge Open in Pro/Engineer Download JScript.

Communications Architecture Communications to the server use the built-in browser All communications to the server use the browser’s TCP/IP connection Only http (or https) is used (no Java RMI*) Pro/E can call the browser programmatically The browser can load pages that call Pro/E programmatically Authentication is through the browser Remote calls are made to the server using (SOAP) SOAP = “Simple Object Access Protocol” XML over http allows structured data to be sent to the server… *Except if required by Windchill applets © 2006 PTC .

P Example User Opens the “File Open” dialog In Pro/E to find a model In Windchill SOAP Services on the server receive the request. deserialize it and execute the appropriate Java Methods To get the contents of the folder. Pro/E writes out a SOAP request and sends it to the browser The browser forwards the request to the server <SOAP-> <> <get-contents…> </get-contents> <…> </SOAP> http Java Classes query the database and return the results Results are serialized into SOAP and returned to the client <SOAP-> <> <…> <> </SOAP> http Pro/E deserializes the SOAP message into C++ Classes and displays the result into the File->Open dialog box © 2006 PTC .O.Communications Architecture .A.S.

Respect customer’s security models Component technology Make use of existing component technology where possible – IE.Architecture Goals Internet/Intranet Enabled Firewall safe – Use only standard protocols (http & https) on standard ports – Server cannot initiate a call to client – Eliminate RMI (use SOAP for complex data operations) – Use the browser’s API for all network communications – Work with proxies and reverse proxies Loosely coupled client & server Use http requests not “hard” API calls – Server functionality injected into Pro/E via downloaded pages – Pro/E can connect to different Windchill solutions (PDMLInk.g. ProjectLink etc) and utilize the existing UI – Enables version interoperability with one version of Pro/E able to work with different versions of Windchill Familiar user model Make use of familiar user interactions – Bookmarks. if your browser can’t then Pro/E shouldn’t” © 2006 PTC . history. back etc. hyperlinks. forward. Pro/E can do it. Tools->Internet options in IE) Rule of thumb: “If your browser can do it. Mozilla – Inherit security settings from user’s existing browser (e.

pro file © 2006 PTC .Business Configuration Flowchart Start Add Prinicipals (Users and Groups) Register Server within Pro/ ENGINEER Setup External Vaulting for CAD Documents Add Creators within Organization Update Pro/ ENGINEER Start Parts with defined Parameters Enable CAD Document Autonumbering Create Product(s) and Libraries Update Pro/ ENGINEER Formats with titleblock attributes Enable Parameter to IBA Publication End Add Teams to Products and Libraries Update Pro/ ENGINEER config.

) include defining a standard set of designated parameters to enable bi-directional attribute modification with the Windchill application and to provide a valuable. searchable field within the Windchill application. etc.Pro/ENGINEER Start Part Modifications The primary modifications typically necessary to a Pro/ENGINEER start part (and start assembly. © 2006 PTC .

Some of the system attributes that can be added to the drawing format may include those listed in Table 1. it is important to update the drawing formats that are in use.Pro/ENGINEER Drawing Format Modifications To ensure that the Pro/ENGINEER drawing formats reference the accurate value of attributes stored by the Windchill PDMLink system. © 2006 PTC .

” Lifecycle State as identified by the Windchill system Lifecycle as identified by the Windchill system (as assigned by the OIR) Context and Folder as identified by the Windchill system Windchill Lifecycle State Windchill Lifecycle &ptc_wm_lifecycle_state &ptc_wm_lifecycle Windchill Location &ptc_wm_location Created By Created On Modified By Modified On &ptc_wm_created_by &ptc_wm_created_on &ptc_wm_modified_by &ptc_wm_modified_on Username of the initial creator Date of initial creation Username of the creator of the current iteration Date of creation of the current iteration © 2006 PTC .Type Drawing Name Model Name Sheet Scale Current Sheet Number Number of Total Sheets Windchill Revision Windchill Iteration Windchill Version Parameter Name &dwg_name &model_name &scale &current_sheet &total_sheets &ptc_wm_revision &ptc_wm_iteration &ptc_wm_version Description Name of the drawing file Name of the model used to build the drawing views Scale of the drawing Current sheet number Total number of sheets in the drawing Revision as identified by the Windchill system Iteration as identified by the Windchill system Concatenation of the Revision and Iteration separated by a “.

This process involves retrieving the drawing into session and updating the format with the newly created format (in Pro/ENGINEER Wildfire.Update Active Drawings with New Formats The process of updating drawings that are currently in work with the newly modified formats can be a tedious one and should typically be left up to the customer’s design engineers. Obviously. this is done through the Drawing’s File>Page Setup… dialog). for many released drawings. this modification may require a change request and is probably best left to the customer to be performed on an as-needed basis. © 2006 PTC .

Pro/ENGINEER automatically attempts to reconnect to the primary server at startup. Use cautiously as higher compression levels will put more burden on client and server CPU. depending upon the location of the config. © 2006 PTC . to all users as an initial default.Pro/ENGINEER config. Automatic will perform an automatic upload of content to server upon file>save within Wildfire.pro Modifications Pro/ENGINEER allows the usage of standard configuration settings through a config.pro file.pro file. or based upon their specific working directory and current working session.pro options in Table 2 relate specifically to the management of Pro/ENGINEER data within the Windchill PDMLink or Pro/INTRALINK system and should be considered for implementation. Explicit is the default. As a rule. the following settings should be assessed by the implementation team and the customer to determine to what extent this standard should be rolled out to the user base. For an extensive list of all of the Data Management-specific config. The config.sup).pro options Configuration Option dm_remember_server •=yes •=no dm_http_compression_level •=0 for LAN clients •>0 (up to 10) for WAN clients dm_upload_objects •=Explicit •=Automatic Description If yes. Enables compression of data for upload and download. These configurations can be applied to all users all the time (via config.

These template files should be created and maintained by a Librarian within a Library inside of Windchill. and recommended. The options in Table 3 specify the various template file settings. the end user will need to use the Pro/ENGINEER Copy From Source functionality instead of the new part dialog © 2006 PTC .Pro/ENGINEER config.pro Modifications Contd… It is possible. that to store template start parts within Windchill. Note: If multiple start parts of the same type are used. This provides revision and access authorization control over these standard documents.

template_designasm template_drawing template_ecadasm template_ecadpart template_mfgcast template_mfgcmm template_mfgemo template_mfgmold template_mfgnc template_mold_layout template_sheetmetalpart force_new_file_options_dialog Specify the assembly to use as the default assembly template. Specify the model to use as the default manufacturing assembly template. Specify the model to use as the default ECAD assembly template. Specify the model to use as the default manufacturing cmm template. Set this to “yes” to automatically point the user to the template start parts © 2006 PTC . Specify the model to use as the default sheetmetal part template.Configuration Option start_model_dir Sample syntax: start_model_dir wtpub://<server>/Libraries/Pro Standards/Start Parts Description Specify the complete path to a folder containing start parts and assemblies. Specify the model to use as the default mold layout template. where <server> is the name as configured through the server registry. where <server> is the name as configured through the server registry.prt Specify the model to use as the default part template. Template_solidpart Sample syntax: template_solidpart wtpub://<server>/Libraries/Pro Standards/Start Parts/START_PART. Specify the model to use as the default manufacturing expert machinist template. Specify the model to use as the default ECAD part template. Specify the drawing to use as the default drawing template. Specify the model to use as the default manufacturing cast template. Specify the model to use as the default manufacturing mold template.