Performing the Import
To perform the import, complete the following steps.
1. On the system where ThingWorx is installed, add the import bundle to a ThingWorx file repository in the following directory: <install_location>/ThingworxStorage/repository. Import bundles must be in a ThingWorx file repository in order to be imported.
You can use the PTC.SCA.SCO.DefaultOperatorAdvisorFileRepository, which is the same file repository used when converting process plans from Windchill MPMLink. If that directory does not already exist, you can either add it manually, or prompt the system to add it by clicking Manage (
) in ThingWorx Composer, and selecting the repository from the Repositories list.
) in ThingWorx Composer, and selecting the repository from the Repositories list.You can also choose to create a custom file repository for importing bundles. For more information, see Managing File Repositories in the ThingWorx Help Center.
2. In ThingWorx Composer, navigate to the PTC.SCA.SCO.DataImportManager Thing.
3. Under Services, execute the ImportFromBundle service.
4. As service inputs, enter the following:
◦ sourceFileRepository—Select the Thing for the file repository where you added your import bundle, for example PTC.SCA.SCO.DefaultOperatorAdvisorFileRepository or your custom file repository.
◦ destinationFileRepository—Select the PTC.SCA.SCO.DefaultOperatorAdvisorFileRepository Thing. This is the location where the binary files will be located and referenced by Operator Advisor after importing.
◦ bundleZipPath—The path to the import bundle, relative to the source file repository. For example, /bundle-001.zip.
5. Click Execute. When the import completes successfully, the service output displays the path of the directory in the file repository that was created for the imported data, relative to the destination file repository. The data is now present in Operator Advisor and in the database.
Troubleshooting the Import
When an import fails, the import is automatically rolled back. Any data that was added is removed from both the Operator Advisor database and the ThingWorx file repository. Review the ApplicationLog and ScriptLog in ThingWorx, and the database logs for more information on what caused the failure.
Data integrity violations are the most common causes of import failures. For example, the name for a site (PTC.SCA.SCO.Site) must be unique. Attempting to import a site with the same name as an existing site causes the import to fail.