7.1.x.x to 7.2.x.x Update Checklist
To update the 7.1.x.x version of PTC Arbortext Content Delivery installation to version 7.2.x.x, read the following checklist.
Step 1: Before you begin
Ensure you read the following to plan for your PTC Arbortext Content Delivery deployment:
Step 2: Install PTC Arbortext Content Delivery
To install PTC Arbortext Content Delivery, see the following sections:
| See all topics under this section. |
| See all topics under the section. |
4. LDAP Configuration
Step 3: Customization Upgrade
If existing customization is available, before updating, see
Analyzing 7.1 CustomizationStep 4: Validate your deployment
Validate and make sure all the configurations are correct using the deployment
Configurator.
Step 5: Pre-update actions
Before you update a
PTC Arbortext Content Delivery release, you must perform some tasks on the machine running the old
PTC Arbortext Content Delivery version. See the
Pre-Update Actions section in
Updating to a New Release.
Step 6: Split or Cluster Update
See
Updating from 7.x Release to update to the latest version of
PTC Arbortext Content Delivery.
Step 7: Configure the required security configurations
Step 8: Customize the application
See the following sections to customize PTC Arbortext Content Delivery and apply according to your requirements.
• Customizing the Login Page for PTC Arbortext Content Delivery
| See all topics under this section. |
| See all topics under this section. |
Step 9: Publish and load data
Step 10: Set the administration utilities
See the
Administration section to use the ACD administration utilities.
Step 11: Before Using the Application
Before you start using PTC Arbortext Content Delivery, see the following:
• See the following for custom applications to interact with PTC Arbortext Content Delivery.
Step 12: Review the ACD Application Status
For optimal performance, PTC recommends that you restart the PTC Arbortext Content Delivery application biweekly and do the following:
1. Check for RAM and disk consumption.
2. Check for CPU consumption.
3. Check the MongoDB size.