PDXpert PLM Software Installation Guide
Upgrading the PDXpert Application Server
If your current system is older than PDXpert 8.0, refer to Upgrade to PDXpert 7.5 or earlier .
All updates are cumulative and may be applied to any PDXpert system. No other updates are required to obtain the most current features.
If you have a large system or many custom services, consider validating your upgrade in a test environment prior to upgrading your production system.
A system upgrade is applied to your server computer. If you use more than one computer for your PDXpert system, upgrade the PDXpert system on your server computer before upgrading the PDXpert client application on each workstation computer.
Confirm that you have administrator rights to your server computer, and are the only logged-in Windows user.
Microsoft has stopped all support for SQL Server 2005. If you are using SQL Server 2005, upgrade to a supported version (SQL Server 2008 or higher).
In PDXpert release 9.2 or later, the PDXpert system installer will automatically upgrade a PDXPERT database instance from SQL Server 2005 Express to SQL Server 2008 Express. Other SQL Server editions must be upgraded manually.
Close all PDXpert client applications.
Stop access from any applications, utilities or services that rely on the PDXpert database (CAD part look-up, MRP transfers, database backup services, etc.).
Back up your data as described in the help file: Contents > PDXpert Application Server > How to... > Back up the database or in on-line help. If you have a large number of files, you may want to use the Database without Library (.bak) option. The upgrade will not affect any library files.
Download and save the new PDXpert Application Server installer.
Save the PDXpert system installer to your server computer. Do not run the installer directly from your browser. An interrupted connection may cause the installation process to fail.
Run the PDXpert Server installer on your current server computer. This also updates the PDXpert client on the same computer. If your computer does not already have the required Microsoft .NET Framework, it will be downloaded from the Microsoft website and installed for you.
During the upgrade, the database schema may require changes, and take up to 30 minutes. Some upgrades (for example, releases before 8.0) recalculate the library files' hash values at roughly 500 to 2000 files per minute.
Users may log in after the server displays the Database upgraded successfully status message.
Indexing may take significant time for a large database and library. While the database is being indexed, search results may be incomplete and server computer performance will be reduced. Server performance and search results will return to normal after the indexing is complete.
Validating your database & library upgrade—
Use the following steps to confirm that your database and library file pointers have been successfully updated, and that all database services are operational.
On the server computer:
Start the PDXpert client using an account with normal or analyst role permissions:
- Enter account name and password, and
- Click the OK button.
If you see the log in message The server could not be contacted, then the client communications service could not automatically restart after the upgrade. Restart the service by rebooting the computer. Or, to avoid rebooting, try using the tool to , then , the SQL Server (PDXPERT) and then the PDXpert Server services.
Search for a known part or document that has a file attachment. Open the item and confirm that the file attachment can be copied from PDXpert to your computer's Desktop. View the file to ensure the file appears as expected. You may want to test both recent and older items.
A large database may require significant time before all items are searchable. You can monitor indexing progress within the PDXpert client: Tools | Index Status...
Verify that each Data Transformations member (custom reports, imports and exports) performs as expected.
If you have defined any Views collection members for sharing data with CAD, MRP or similar applications, verify that each member contains expected data.
Restart/restore any custom applications, utilities or services that rely on the PDXpert database and verify proper operation.