Upgrading a Standalone Operator Advisor System to 8.5.0
Upgrade to Operator Advisor 8.5.0 is supported from Operator Advisor 8.4.1 and 8.4.3 systems. If you are upgrading from an Operator Advisor system earlier than release 8.4.1, you must first upgrade to Operator Advisor 8.4.1 before upgrading to Operator Advisor 8.5.0.
To upgrade to Operator Advisor 8.5.0, complete the following instructions. Customers installing a fresh instance of Operator Advisor can proceed to Configuring Operator Advisor.
1. Upgrade your ThingWorx installation. For more information, see Upgrading to ThingWorx 8.5 in Reference Documents. For Product, select ThingWorx Platform.
2. Import the extension files as described in Importing the Extension.
3. Restart your ThingWorx server.
4. Update the database tables:
◦ For a Postgres database, run the following commands:
ALTER TABLE joborder ALTER COLUMN actualstarttime TYPE timestamptz;
ALTER TABLE joborder ALTER COLUMN actualendtime TYPE timestamptz;
ALTER TABLE joborder ALTER COLUMN plannedstarttime TYPE timestamptz;
ALTER TABLE joborder ALTER COLUMN plannedendtime TYPE timestamptz;
ALTER TABLE historicaldata ALTER COLUMN timestamp TYPE timestamptz;
ALTER TABLE joborder ALTER COLUMN actualendtime TYPE timestamptz;
ALTER TABLE joborder ALTER COLUMN plannedstarttime TYPE timestamptz;
ALTER TABLE joborder ALTER COLUMN plannedendtime TYPE timestamptz;
ALTER TABLE historicaldata ALTER COLUMN timestamp TYPE timestamptz;
◦ For a SQL Server database, run the following commands, replacing <schema> with twschema or the schema used for your database:
ALTER TABLE <schema>.joborder ALTER COLUMN actualstarttime DATETIMEOFFSET;
ALTER TABLE <schema>.joborder ALTER COLUMN actualendtime DATETIMEOFFSET;
ALTER TABLE <schema>.joborder ALTER COLUMN plannedstarttime DATETIMEOFFSET;
ALTER TABLE <schema>.joborder ALTER COLUMN plannedendtime DATETIMEOFFSET;
ALTER TABLE <schema>.historicaldata ALTER COLUMN timestamp DATETIMEOFFSET;
GO
ALTER TABLE <schema>.joborder ALTER COLUMN actualendtime DATETIMEOFFSET;
ALTER TABLE <schema>.joborder ALTER COLUMN plannedstarttime DATETIMEOFFSET;
ALTER TABLE <schema>.joborder ALTER COLUMN plannedendtime DATETIMEOFFSET;
ALTER TABLE <schema>.historicaldata ALTER COLUMN timestamp DATETIMEOFFSET;
GO
5. Navigate to the database thing corresponding to your database: PTC.SCA.SCO.PostgresDatabase or PTC.SCA.SCO.MSSQLDatabase.
6. Under Configuration, set the JDBC Settings appropriately for your database.
 |
Before configuring your database thing, ensure that the necessary JDBC drivers are present in ThingWorx. ThingWorx can use JDBC drivers to connect to any JDBC compatible database (such as SQL Server, MySQL, and so on). This can also be done using theThingWorx Edge MicroServer and the ThingWorx Host/Resource using OLEDB and ODBC if the database happens to be behind a firewall. If a JDBC extension does not exist in ThingWorx for your database, you can manually add the JDBC driver by downloading the driver and adding the files to the following location: /<Tomcat folder>/webapps/Thingworx/WEB-INF/lib. After copying the driver, you must restart your ThingWorx server. For more information, see JDBC Extensibility in the ThingWorx Help Center.
|
7. Click Save to save the database thing.
8. Navigate to the PTC.Factory.C_LaunchPointConfigurationThing_[ReleaseVersion] thing.
9. Under Configuration, in the DatabaseConfigurationSettings section, edit the DBConnection field to point to the database thing you configured in step 6.
10. Click Save to save the launch point configuration thing.
11. Navigate to the PTC.SCA.SCO.OAMigrator thing.
12. Under Services, execute the migration service appropriate for the release from which you are upgrading:
◦ If upgrading from 8.4.1, execute the MigrateFrom_8_4_1_To_8_5_0 service.
◦ If upgrading from 8.4.3, execute the MigrateFrom_8_4_3_To_8_5_0 service. (8.4.3 is a limited release, not available from the PTC Software Download page)
The service has completed successfully when "No results" displays in the service output pane.
13. If you had added pre-action and post-action services on the PTC.SCA.SCO.DefaultPreActionValidator or PTC.SCA.SCO.DefaultPostActionHandler things on your source system, follow the instructions in Pre- and Post-Action Event Dispatching and Validation to duplicate the new PTC.SCA.SCO.PreActionValidator and PTC.SCA.SCO.PostActionHandler things and add your services to the duplicates.
14. The MPMLink OData connector thing (PTC.SCA.SCO.MPMLink_ODataConnector) has been updated for 8.5. Make a duplicate of the updated thing and configure it following the instructions in Configuring the MPMLink OData Connector.
16. Update the database tables:
◦ For a Postgres database, run the following commands:
ALTER TABLE workdefinitionmaterialspecification ALTER COLUMN occurrencepath TYPE VARCHAR(4000);
ALTER TABLE historicaldata ALTER COLUMN value TYPE VARCHAR(4000);
ALTER TABLE historicaldata ALTER COLUMN value TYPE VARCHAR(4000);
◦ For a SQL Server database, run the following commands:
ALTER TABLE <schema>.workdefinitionmaterialspecification ALTER COLUMN occurrencepath NVARCHAR(4000);
ALTER TABLE <schema>.historicaldata ALTER COLUMN value NVARCHAR(4000);
ALTER TABLE <schema>.historicaldata ALTER COLUMN value NVARCHAR(4000);
17. If you are upgrading to an 8.5 service pack release, follow the instructions in Upgrading to an 8.5 Service Pack Release.
|
|
If you do not want to keep your data from the previous version of the Operator Advisor extension, execute the DropTables service, then execute the CreateTables service. Both services are found on the default production order manager thing (PTC.SCA.SCO.DefaultProductionOrderManager), under Services.
|