Pre-Update Actions
Before you update a PTC Arbortext Content Delivery release, you must perform the following tasks on the machine running the old PTC Arbortext Content Delivery release that has content loaded, such as product hierarchy, information structures, and so on.
 |
• You need to start the LDAP server before beginning to run update.
• To run update, ensure that you have the valid Java 11 JDK installed on your machine.
• During the installation process, the Installer has a new panel that takes the Java 11 JDK path. For convenience, it takes the old JDK path that was used in the earlier installation. If it is not JDK 11, update the path to JDK 11 using the new panel.
• You need a new license file for 7.2 version.
• You must perform the migration steps after an update or upgrade. Update or upgrade installation can be triggered with the existing WindchillDS. For more information see, Migrating from WindchillDS to OpenDJ or Another v3-compliant Directory Server
|
Stopping Servers
1. Stop Core server
2. Stop Core CMI servers
3. Stop JBoss Wildfly server
4. Stop the Performance Advisor service.
|
|
For Windows, after stopping the Performance Advisor agent (PA agent) service, update the PA agent service startup type from Automatic to Manual before you proceed to update PTC Arbortext Content Delivery.
|
5. For Windows operating system, update the code in the <InS_SW>\SW\stopServer.bat file mentioned in the below image:
6. Take backup of the existing PTC Arbortext Content Delivery installation folder on both the Publisher and Viewers.
7. If you have any previous customizations that you want to add to the updated release, see the Analyzing 7.1 Customization section.