Prepare the Source System for Upgrade
Perform the following steps in setting up your production source database for upgrade:
Shut down Replica Servers
If your site uses replication, this section describes the steps specific to your site for that process.
If you do not use a replicated vault configuration, skip this section.
1. On the main site, perform the following:
a. Navigate to > > > . You can either delete or disable the schedules:
▪ Delete the schedules—Note the frequency and target vault for all of the replication schedules except the ones starting with PCS_. Schedule names starting with PCS_ are predictive caching schedules and are automatically created. Then, delete all content replication schedules, except the ones which are currently in the running/executing state.
▪ Disabling the schedules—Delete all one-time, immediate replication schedules and schedules starting with PCS_. Disable all remaining scheduled content replication schedules, except the ones which are currently in the running/execution state.
b. Wait for the running schedules to complete and then disable or delete them according to the guidelines in the previous step. Check the following queues (if they exist) and make sure there are no objects:
▪ replQueue
▪ wt.router.1.*, wt.router.2.*, wt.router.3.*, wt.router.4.*, wt.router.5.*, wt.router.6.*, wt.router.7.*
▪ RevaultingQueue
▪ ReplicationTaskQueue
2. Shut down all of the file server sites.
Shut Down the Windchill System
1. Configure the system to prevent access to the Windchill system by users. After the configuration, restart the method server so that all active sessions are terminated and no new authenticated client connections can be established. To restart the method server, run the following from a Windchill shell:
a. windchill stop
b. windchill start
2. Allow executing queue entries to be processed.
To monitor the state of the queues, use the Queue Manager on the source system’s Site Utilities page.
Select each queue and check to see that no entries have a status of Executing.
 |
Windchill solutions have the capability of scheduling work to be performed in the future. No action is required for the scheduled jobs that appear in the Ready state in Queue Manager. Therefore, the presence of these should not prevent you from starting an upgrade.
|
3. For Windchill Visualization Services, wait for any executing publish jobs to finish, then immediately use the CAD Agent Administrator to take the workers offline so that new jobs are not executed before you shut down the server.
4. Stop your Windchill solution. In a Windchill shell, enter the following command for either UNIX or Windows systems:
windchill stop
5. Shut down your web server and servlet engine.