ThingWorx Extensibility > Integration Connectors > Upgrading Integration Connectors
  
Upgrading Integration Connectors
If you are upgrading from ThingWorx 7.4 to 8.0, choose one of the upgrade processes below to migrate your Integration Connectors. Then following the steps in the Special Instructions section.
Upgrade In Place
1. In ThingWorx 7.4, stop the Integration Runtime microservice and Tomcat.
2. Remove the validation.properties file from /ThingworxStorage/esapi.
3. Delete the thingworx.war file from your 7.4 Tomcat installation directory.
4. In ThingWorx 8.0, run thingworxPostgresSchemaUpdate7.4-to-8.0.bat.
5. Copy the thingworx.war file for 8.0 into the Tomcat installation directory.
6. Start Tomcat.
7. When you log into ThingWorx 8.0, the Integration Connectors, API maps and services are migrated from 7.4.
Upgrade Using Export/Import
1. In ThingWorx 7.4, ensure the Integration Runtime microservice is running.
2. Export the AllEntities file from 7.4.
a. In ThingWorx Composer, select Import/Export > Export > To File.
b. Under the Entities tab, confirm Binary is selected in the Export Type field, and click Export.
This exports all entities into the file AllEntities.xml.
3. In ThingWorx 8.0, the Integration Runtime microservice should not be running.
4. Import the AllEntities file to 8.0.
a. In ThingWorx Composer, select Import/Export > Import > From File.
b. Select the Entities button.
c. Under the Single File tab, browse to AllEntities.xml.
d. Ensure the Include Subsystems checkbox is checked so the Integration Subsystem and its data are imported.
e. Click Import.
Special Instructions
In ThingWorx 8.0, some services may have a new parameter type. If you create a new service in 8.0 with the same endpoint that was used in an existing service in 7.4 and observe that the services have different input parameters, use these special instructions to update the 7.4 service.
1. In ThingWorx 8.0, select the Integration Connector Thing using the service.
2. Select the service that was upgraded from 7.4.
3. Edit the service by temporarily changing the endpoint to a different option. Then change it back to the original endpoint.
4. Save the service.
5. Save the Thing.