Add a
ThingWorx
application

NOTE:
The
ThingWorx
application is supported by standalone version only.
For users that have IIoT (Industrial Internet of Things) applications or solutions using
PTC®
ThingWorx®
,
FactoryTalk Edge Gateway
provides a method to collect information from
Rockwell Automation
and third-party sources and send it to a
ThingWorx
Foundation server.
FactoryTalk Edge Gateway
supports
ThingWorx
version 8.5, 9.0 and 9.3.
FactoryTalk Edge Gateway
facilitates creating objects that are required in
ThingWorx
to represent the model, which reduces the time for deploying a
ThingWorx
application.
To communicate with the
ThingWorx
Foundation server, add a
ThingWorx
application in
FactoryTalk Edge Gateway
, and then configure and deploy the application. During configuration of a
ThingWorx
application, models selected from the
Models
dialog box appear in
Preview
as a hierarchical structure of
ThingWorx
Things.
To add a
ThingWorx
application
  1. In the top-right corner, select
    Online
    to go online with the gateway.
    FactoryTalk Edge Gateway
    displays a green banner:
    Gateway Connection: Online
    .
  2. Select
    Data Flow
    >
    Applications
    .
    • To add the first application, select
      Add Application
      .
    • To add a subsequent application, select
      Add
      .
  3. From
    Select Application
    , select an application
  4. Select
    Next.
  5. Set these parameters:
    • Application Name
      . Defines the application name.
    • ThingWorx Server Host Name
      . Defines the name or IP Address of the server host.
    • ThingWorx Server Port
      . Indicates the communication port between the <TXW> Foundation server and the gateway.
    • ThingWorx Server Application Key
      . Defines the security token used for authentication with the <TXW> Foundation server.
    • ThingWorx Logging Level
      . Set the logging level for the
      ThingWorx
      application to one of these options:
      • Info
        .This level logs important system information. Exceptions are not logged.
      • Trace
        . This level is used to help debug issues while developing an application. Trace logs provide detailed information to troubleshoot issues. This is the most detailed log.
      • Debug
        . This level is used to help debug issues. The log contains information about what the code is doing and the values of important variables.
      • Warn
        . This level logs unexpected exceptions that are acceptable or can be worked around. It includes problems that could become errors if left unattended.
      • Error
        . This level logs issues that affect the usage or performance of the system.
      • Force
        . This level logs issues that affect the usage or performance of the system. This option makes sure that all errors are logged.
      • Audit
        . This level logs messages in a separate audit file.
    • ThingWorx Logging Verbose
      . Select
      Logging Verbose
      to log every message sent between the application and the
      ThingWorx
      Foundation server. While valuable for debugging, this setting can significantly impact performance.
    • Store and Forward
      . This setting enables storing the data entering the application in a database on the gateway. This setting also functions as a buffer for data entering the store database at higher speeds than it is forwarding to the application.
      A maximum of 256 KB of data is fetched from the store database at each configured fetch interval.
      Select
      Store and Forward
      to enable the
      Maximum store size (bytes)
      and
      Fetch Interval (ms)
      settings. In case connectivity is lost to the external application, having
      Store and Forward
      enabled avoids periods of lost data to
      ThingWorx
      . Store and Forward keeps data stored in the database until the connection is restored.
    • Maximum store size (bytes)
      . This setting defines the maximum size of the store database on the gateway, in bytes. When the maximum store size is reached, the oldest data is deleted to make space for new application data. Select
      Store and Forward
      to enable this setting.
    • Maximum fetch size (bytes)
      . This setting defines the maximum size of data to fetch from the store database at each configured fetch interval.
      Select
      Store and Forward to enable
      this setting.
    • Fetch Interval (ms)
      . This setting defines the interval of time to egress (that is, forward) data from the store database, in milliseconds. Data continues to be egressed to the
      ThingWorx
      application until the store database is empty.
      When egress fails, the data remains in the store database. Select
      Store and Forward
      to enable this setting.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal