Rehosting Servers for On-prem Environment with AI Assistant Plugin Installed
When rehosting servers with the AI Assistant plugin installed, complete the following steps:
1. Perform the source‑to‑target rehosting procedure as documented in the Windchill rehost documentation. This procedure includes running the Windchill rehost utility.
|
|
In rehost scenarios where the target system has an installed and active AI Assistant plugin, rehosting will fail. To rehost successfully, stop indexing and remove the plugin configuration on the target system before executing the rehost steps.
|
2. After the rehosting process is complete, recreate the configuration in the plugin configuration window on the target system. Depending on the rehost scenario, different steps may be required:
◦ If the server was moved or renamed, the original credentials may be used.
◦ If the server is a clone, new Azure resources must be created and configured using the plugin configuration window. Update the index name in Azure AI Search and the container name in Azure Storage to reference the newly created resources that are dedicated exclusively to the new target instance in the plugin configuration. Azure OpenAI resources can be shared between instances. Failure to update these values can result in index corruption.
3. Re‑enable indexing and synchronization, or start a manual bulk or automatic synchronization, on the target instance.
For Windchill 13.1.3.0 environments, if the source system uses an indexing user that is different from the administrator, perform the following 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 User B.
4. Save the configuration.
The original indexing user must be configured on the target system at least momentarily before it can be changed to another user. Otherwise, the event queue subscription remains in an unrecoverable state on the target system.