Execute Steps for Windchill Index Search and Windchill PartsLink
 |
While the procedure outlined below is for upgrading, the same steps can be performed while performing an update.
• If you are updating from Windchill 11.1 F000, see the section: Updating from Windchill 11.1 F000.
|
The objects that were indexed in your source release must be re-indexed on the target system. This section describes how to re-index the objects that belong in the Windchill Index Search libraries.
You should have already installed the Windchill Index Search client and server when you installed your target system using the steps in the section Install the Target System.
Running the Bulk Index Tool each time you perform a rehearsal upgrade considerably improves the performance of the re-indexing process for Windchill Index Search during the production upgrade.
The following is a high-level overview of this process:
1. After the first rehearsal upgrade, execute the Bulk Index Tool.
2. The IndexStatus table is exported and saved.
3. After each subsequent rehearsal upgrade, the following steps are completed:
a. The IndexStatus table is imported into the upgraded database.
b. The Bulk Index Tool is executed.
c. The IndexStatus table is exported and saved.
4. After the production upgrade, the following steps are completed:
a. The IndexStatus table is imported into the upgraded database.
b. The Bulk Index Tool is executed.
|
|
This process is not mandatory. You can choose to run the Bulk Index Tool on the upgraded production server only, but this process helps bring down the time required for final bulk indexing. Availability of index search functionality depends on the time required for bulk indexing.
|
Steps for First Rehearsal Upgrade
Complete the following steps for the first rehearsal upgrade:
1. After completing a rehearsal upgrade on a snapshot of the production system, make a note of the date when the snapshot was taken (for example, BIT_START_DATE).
2. Verify that the collection name configured in the indexing policy rule in the Windchill Policy Administration utility is the same as in the Solr data folder (both should be “wblib”).
Perform the following steps:
a. Log in to Windchill as the site administrator.
b. Navigate to > > .
c. Click the domain name of the root (/) domain where the indexing policy is defined.
d. Navigate to the Indexing Rules tab and edit the existing rule.
e. Remove the existing collections from Selected Collections and add the necessary collections from the Available Collections depending on your indexing policies. See the Windchill Customization Guide for information on configuring multiple collections (cores).
3. Run the Bulk Index Tool. This is accomplished by performing the following steps:
a. Start your Windchill solution.
b. Open a Windchill shell.
c. Run windchill wt.index.BulkIndexTool.
d. Log in to the Bulk Index Tool.
e. Delete the bulk indexing list of objects.
f. Start the bulk indexing process.
For more information on installing Windchill Index Search or the Bulk Index Tool, see the Windchill Installation and Configuration Guide.
4. Export and save the IndexStatus table from the rehearsal Windchill target database. This table includes all of the necessary re-indexing information.
5. Copy and save the index data folders related to wblib.
Refer to the wt.index.server.datadir property value in the Index Search Server for the data directory path.
Steps for Each Subsequent Rehearsal Upgrade
Complete the following steps for each subsequent rehearsal upgrade:
1. After completing a rehearsal upgrade on a snapshot of the production system, make a note of the date when the snapshot was taken (for example, BIT_START_DATE).
2. Verify that the collection name configured in the indexing policy rule in the Windchill Policy Administration utility is the same as in the Solr data folder (both should be “wblib”).
Perform the following steps:
a. Log in to Windchill as the site administrator.
b. Navigate to > > .
c. Click the domain name of the root (/) domain where the indexing policy is defined.
d. Navigate to the Indexing Rules tab and edit the existing rule.
e. Remove the existing collections from Selected Collections and add the necessary collections from the Available Collections depending on your indexing policies. See the Windchill Customization Guide for information on configuring multiple collections (cores).
|
|
If there are any changes in the policy rules, the index data from earlier rehearsals should not be used.
|
3. Copy the index data folder from the previous rehearsal and paste it in the appropriate location during the current rehearsal:
a. Stop Windchill.
b. Copy index data directory as per collections configured.
Refer to the wt.index.server.datadir property value in the Index Search Server for the data directory path.
c. Paste the directory to the current rehearsal server file system.
4. Import the IndexStatus table into the upgraded rehearsal Windchill target database.
5. Execute the following SQL command:
update IndexStatus set modifyStampA2='BIT_START_DATE', createStampA2='BIT_START_DATE'; commit;
(where BIT_START_DATE is the date of the last rehearsal snapshot on which the Bulk Index Tool was executed).
6. Re-index the upgraded rehearsal system by running Bulk Indexing Tool to catchup with the modified data since the snapshot for the production system was taken. This is accomplished by performing the following steps:
a. Start your Windchill solution.
b. Open a Windchill shell.
c. Run windchill wt.index.BulkIndexTool.
d. Log in to the Bulk Index Tool.
e. Delete the bulk indexing list of objects.
f. Start the bulk indexing process.
For more information on installing Windchill Index Search or the Bulk Index Tool, see the Windchill Installation and Configuration Guide.
7. Export and save the IndexStatus table from the upgraded rehearsal Windchill target database. This table includes all of the necessary re-indexing information.
8. Copy and save the index data folders related to wblib.
Refer to the wt.index.server.datadir property value in the Index Search Server for the data directory path.
Steps for the Production Upgrade
Complete the following steps for the production upgrade:
1. Verify that the collection name configured in the indexing policy rule in the Windchill Policy Administration utility is the same as in the Solr data folder (both should be “wblib”).
Perform the following steps:
a. Log in to Windchill as the site administrator.
b. Navigate to > > .
c. Click the domain name of the appropriate domain root where the indexing policy is to be defined.
d. Navigate to the Indexing Rules tab and edit the existing rule.
e. Remove the existing collections from Selected Collections and add the necessary collections from the Available Collections depending on your indexing policies. See the Windchill Customization Guide for information on configuring multiple collections (cores).
|
|
If there are any changes in the policy rules, the index data from earlier rehearsals should not be used.
|
2. Copy the index data folder from the previous rehearsal and paste it in the appropriate location during the current production upgrade:
a. Stop Windchill
b. Copy index data directory as per collections configured.
Refer to the wt.index.server.datadir property value in the Index Search Server for the data directory path.
c. Paste the directory to the current server file system.
3. Import theIndexStatus table into the upgraded production Windchill target database.
4. Execute the following SQL command:
update IndexStatus set modifyStampA2='BIT_START_DATE', createStampA2='BIT_START_DATE'; commit;
(where BIT_START_DATE is the date of the last rehearsal snapshot on which the Bulk Index Tool was executed).
5. Re-index the upgraded production system by running Bulk Indexing Tool to catchup with the modified data since the snapshot for the production system was taken. This is accomplished by performing the following steps:
a. Start your Windchill solution.
b. Open a Windchill shell.
c. Run windchill wt.index.BulkIndexTool.
d. Log in to the Bulk Index Tool.
e. Delete the bulk indexing list of objects.
f. Start the bulk indexing process.
For more information on installing Windchill Index Search or the Bulk Index Tool, see the Windchill Installation and Configuration Guide.
Windchill PartsLink and Classification Structure
Re-index the Classification Structure on upgraded production system by running the utility to catchup with the modified data since the snapshot for the production system was taken.
• windchill com.ptc.windchill.csm.struct.UpdateClassificationStructure -u adminUsername -p adminPassword -v
Updating from Windchill 11.1 F000
For information on installing and configuring the Windchill Index Search server and client, see Windchill Index Search Installation and Post-Installation Configuration.
When updating from Windchill, you must set the following properties for the Windchill Index Search client in wt.properties:
• wt.index.enableIndexSearchHighAvailability
• wt.index.solrHost (set this only if the index search server is installed in standalone mode)
• wt.index.solrPort (set this only if the index search server is installed in standalone mode)
• wt.index.zookeeperHosts (set this only if using index search in high availability/cloud mode)
• wt.index.indexingLanguage
• wt.index.indexingLanguageList
• wt.index.solrEffectiveUid
• wt.auth.trustedHosts
The following properties are set in codebase/WEB-INF/conf/index.solrAuth.properties:
• wt.index.solrAdminUser
• wt.index.solrAdminPassword
For more information about these properties, see Windchill Search Properties.
Because the update operation should remove the Solr web application from Windchill, verify that the following files have been removed:
• Windows:
<Windchill>/Apache/app-Windchill-Solr.properties
<Windchill>/Apache/app-Windchill-Solr-AuthProvider.xml
<Windchill>/Apache/app-Windchill-Solr-AuthRes.xml
• Unix:
<Windchill>/HTTPServer/app-Windchill-Solr.properties
<Windchill>/HTTPServer/app-Windchill-Solr-AuthProvider.xml
<Windchill>/HTTPServer/app-Windchill-Solr-AuthRes.xml
If these files are still present, execute the following script to uninstall the Solr web application from Windchill:
1. Open a Windchill shell.
2. Navigate to one of the following locations:
◦ Windows:
<Windchill>/Apache
◦ Unix:
<Windchill>/HTTPServer
3. Execute the following command:
ant -f webAppConfig.xml uninstallWebApp -DappToUninstall=<Solr_WebApp_Name>
For example:
ant -f webAppConfig.xml uninstallWebApp -DappToUninstall=Windchill-Solr
You should also verify that the following file has been removed:
<Windchill>/tomcat/conf/Catalina/localhost/Windchill-Solr.xml
If it is still present, create a backup of it and then delete it.
Updating from Windchill 11.1 F000 and Later
The Windchill PSI has a limited ability to update installations that are located outside the Windchill load point. In subsequent update operations, you must perform a fresh installation of the Windchill Index Search server. For information on installing and configuring the Windchill Index Search server and client, see Windchill Index Search Installation and Post-Installation Configuration.
As part of this process, you will need to manually delete or archive old installations. You can also manually copy any configurations from your earlier installation to your new installation.
|
|
This applies to all Solr server installations. For example, if you are using a Solr cloud configuration (Solr cluster setup), you must perform a fresh installation of all Solr and Zookeeper nodes.
|