Rehosting Servers for On-prem Environment with AI Assistant Plugin Installed
When you rehost a Windchill server that has the Windchill AI Assistant plugin installed, follow the steps in this topic to avoid configuration issues and index corruption.
1. Perform the source‑to‑target rehosting procedure as documented in the Windchill rehost documentation. This procedure includes running the Windchill rehost utility.
 |
Rehosting fails if the target system has an active AI Assistant plugin. Before you start the rehost, stop indexing and remove the plugin configuration on the target system.
|
2. After rehosting is complete, recreate the plugin configuration on the target system. Depending on the rehost scenario, different steps may be required:
◦ If the server was moved or renamed, you can use the original credentials.
◦ If the server is a clone, create new Azure resources and configure them in the plugin configuration window. In the configuration, update the following values to point to the new resources that are dedicated to the new target instance:
▪ Index Name in Azure AI Search
▪ Container Name in Azure Storage
Azure OpenAI resources can be shared between instances.
 |
If you do not update the index name and container name, the index can become corrupted.
|
3. Re‑enable indexing and synchronization on the target instance. You can start a manual bulk synchronization or wait for automatic synchronization to run.
|
|
For instructions on creating an index in Azure AI Search and a container in Azure Storage, see Step 7: Create Azure Resources.
|
If you are rehosting a Windchill 13.1.3.0 environment and the source system uses an indexing user that is different from the administrator, complete the following additional steps on the target system:
1. Recreate the plugin configuration using the original indexing user (User A) from the source system.
2. Save the configuration.
3. Update the indexing user to the new user (User B).
4. Save the configuration.
|
|
You must configure the original indexing user on the target system, at least momentarily, before changing it to another user. Otherwise, the event queue subscription remains in an unrecoverable state on the target system.
|