IoT Tips

This video is the 1st part of a series of two videos walking you through the configuration of Analysis Event which is applied for Real-Time Scoring. This 1st video demonstrate how to create a Template and Thing which allows the prediction model to score in real-time. Note that this video is just for demo purposes, customers who have ThingWorx, they of course already have their properties set-up. They just need to configure Analysis Event which is demonstrated in the part 2 video. Updated Link for access to this video: Analytics Manger 7.4: Create a Template & Thing for Real-Time Scoring Part 1 of 2

Mar 31, 2017

This video will walk you through the first steps of how to set-up Analytics Manager for Real-Time Scoring. More specifically this video demonstrates how to create an Analysis Provider and start ThingPredictor Agent. NOTE: For version 8.1 the startup command for the Agent has changed view the command in PTC Help center. Updated Link for access to this video: ThingWorx Analytics Manager: Create an Analysis Provider & Start the ThingPredictor Agent

Mar 31, 2017

Here is a sample to run ConvertJSON just for test 1. Create a DataShape 2. There are 4 input for service ConvertJSON fieldMap (The structure of infotable in the json row) json (json content) { "rows":[ { "email":"example1@ptc.com" }, { "name":"Lily", "email":"example2@ptc.com" } ] } rowPath (json rows that indicate table information) rows dataShape (infotable dataShape) UserEmail

Feb 17, 2017

There are some scenarios where you don't necessarily want to connect to your corporate mail server, or a public mail server like gmail - e.g. when testing a new function that possibly spams the official mail servers - or the mail server is not yet available. In such a scenario it might be a good idea to use a custom, private mail server to be able to send and receive emails locally on a test- or development-environment. In this post I will show how to use the hMailServer and setup the ThingWorx mail extension to send emails. This post will concentrate on installing and deploying within a Windows environment. More specifically on a Windows 2012 R2 server virtual machine. Installing hMailServer Download and install the .NET Framework 3.5 (includes .NET 2.0 and 3.0). In Windows Server 2012 R2 open the Server Manager and in the Configuration add roles and features. Click through the "Role-based or feature-based installation" steps and install the ".NET Framework 3.5 Features" in case they are not already installed. Download hMailServer via https://www.hmailserver.com/download As always: the latest version is more stable while the beta versions might provide more functionality and additional bug fixes. This post is based on version 5.6.6-B2383. Functionality and how-to-clicks might change in other versions. Note: The Microsoft .NET Framework is required for this installation. In case the .NET installation fails by installing it with the hMailServer framework, it's best to cancel the installation and install the required .NET Framework manually instead of the automatic download and installation offered by hMailServer. In case of such a failure it's best to play it safe and uninstall the mail server again, install the .NET framework manually and then re-install hMailServer. (Any left-over directories should be deleted before re-installing) For the installation, choose your path and a full installation. Use the built-in database engine, set a password for the administrative user and install. Configuring hMailServer The hMailServer Administrator opens automatically after the installation - if not you will find it in the Start menu. Connect to the default instance on the localhost. The password is the one set up during the installation process. Add a domain (e.g. mycompany.com) and save it. The domain will specify the domain of the mail-addresses e.g. user@domain (me@mycompany.com). In the domain add an account. Specify the address (e.g. noreply) and set a password (e.g. ts). Save the new account. The default port used for SMTP is 25. For POP3 it's 110. This is configured under Settings > Advanced > TCP/IP ports Ensure the ports for SMPT and POP3 are not blocked by a firewall in case you run into issues later on. This setup should *usually* work. However there might be hostname specific SMTP issues. In case something happens / or to avoid errors in the first place, go to Settings > Protocols > SMTP > Delivery of e-mail and specific the Local host name. This should be the fully qualified hostname of the server (e.g. myserver.this.company.com). Test hMailServer via telnet Note: telnet needs to be installed for this test - in case it's not installed, Google can help. Open a command line window and execute: telnet <yourhostname> 25 This will open a connection to the SMTP port of the hMailServer. Manual commands can be send to test if the basic send functions are working. The following structure can be used for testing - it holds manual input and responses. Username and password need to be Base64 encoded. See https://www.base64encode.org/ for Base64 conversions. (Tip: only text, don't add additional spaces or line breaks - otherwise the hash will be quite different!) Command / Response Description 220 <HOSTNAME> ESMTP Connected to host HELO mycompany.com Connect with domain as defined in hMailServer 250 Hello. Connected AUTH LOGIN Login as authenticated user 334 VXNlcm5hbWU6 Base64 for "Username:" bm9yZXBseUBteWNvbXBhbnkuY29t Base64 for "noreply@mycompany.com" 334 UGFzc3dvcmQ6 Base64 for "Password:" dHM= Base64 for "ts" 235 authenticated. Authentication successful MAIL FROM: noreply@mycompany.com Sender address 250 OK RCPT TO: <your real mail address> To address 250 OK DATA Body 354 OK, send. Subject: sending mail via telnet Subject line Blank line to indicate end of subject just a simple test! Content . . indicates the end of mail 250 Queued (10.969 seconds) Mail queued and sent with duration QUIT Log off telnet 221 goodbye Connection to host lost. Log off confirmed Configuring ThingWorx Download and configure the mail extension Download the MAIL EXTENSION from the ThingWorx Marketplace https://marketplace.thingworx.com/Items/mail-extension In ThingWorx, click Import / Export > Extensions > Import, choose the downloaded .zip file and import it. The Composer should be refreshed to reflect the changes introduced by the extension. The Extension created a new Thing Template: MailServer Create a new Thing based on the MailServer Template. In its configuration adjust the servername and port to match the hMailServer configuration, e.g. localhost and port 25. Change the Mail User Account and Password to the authentication user (e.g. noreply@mycompany.com / ts). Save the configuration to persist the changes. In any Thing, create a new Service to send mails and notifications. Insert a snippet based on Entities > <yourMailThing> > Send Message Call the service manually for an initial functional test. It should look similar to this... but parameters need to be adjusted to your environment: var params = { cc: undefined /* STRING */, bcc: undefined /* STRING */, subject: "sending email via ThingWorx" /* STRING */, from: "noreply@mycompany.com" /* STRING */, to: "<your real mail address>" /* STRING */, body: "just a simple test!" /* HTML */ }; // no return Things["<yourMailThing>"].SendMessage(params); Check your mailbox for incoming messages! What next? The mail server can also be used to receive emails. So instead of sending mails to your regular mail address and risking a ton of spam (depending on your services and frequency of sending automated emails), you could also configure a local Outlook / Thunderbird / etc. installation and send mails directly to the noreply@mycompany.com address. Those mails can then be downloaded from hMailServer via POP3. With this the whole send AND receive mechanism is contained within a single (virtual) machine.

Feb 2, 2017

This document is a general reference/help with configuring and troubleshooting google email account with the ThingWorx mail extension. To start with the configuration: SMTP: smtp.gmail.com 587, TLS checked. If SSL is being used, the port should be 465. POP3: pop.gmail.com 995 To test, go to "Services" and click on "test" for the SendMessage service. Successful request will show an empty screen with green "result" at the top. Possible errors: Could not connect to SMTP host: smtp.gmail.com, port: 587 with nothing else in the logs. Check your Internet connection to ensure it's not being blocked. <hostname:port>/Thingworx/Common/locales/en-US/translation-login.json 404 (Not Found) Check your gmail folders for incoming messages regarding a sign-in from unknown device. The subject will be "Someone has your password", and the email content will include the device, location, and timestamp of when the incident occurred. Ensure to check the "this was me" option to prevent from further blocking. This may or may not be sufficient, sometimes this leads to another error - "Please log in via your web browser and 534-5.7.14 then try again. 534-5.7.14 Learn more at 534 5.7.14..." The error can be resolved by: Turning off “less secure” feature in your Gmail settings. You have to be logged in to your gmail account to follow the link: https://www.google.com/settings/security/lesssecureapps Changing your gmail password afterwards. I don't have a valid explanation as to why, but this is a required step, and the error doesn't clear without changing the password.

Dec 16, 2016

Since it's somewhat unclear on how to set up the reset password feature through the login form, these steps might be a little more helpful. Assuming the mail extension has already been imported into the Thingworx platform and properly configured - say, PassReset - (test with SendMessage service to verify), let's go ahead and create a new user - Blank, and a new organization that will have that user assigned as a member - Test. Let's open the configuration tab for the organization, assign the PassReset mail thing as the mail server, assign login image, style, prompt (optional), check the Allow Password Reset, then the rest looks like this: Onto the Email content part, it is not possible to save the organization as is at the moment: Clicking on the question mark for the Email content will provide the following requirements: Now this is when it might not be too clear. The tokens [[:user:]], [[:organization:]], [[:url:]] can be used in the email body and at the runtime will be replaced with the actual Usernames, organization, and the reset password url. Out of those fiels, only [[:url:]] token is required. So, it is sufficient to place only [[:url:]] in the body and save the organization: Then, when going to the FormLogin, at <your thingworx host:port>/Thingworx/FormLogin/<organization name>, a password reset button is available: Filling out the User information in the reset field, the email gets sent to the user address specified and the proper message appears: Since in this example only the [[:url:]] token has been used in the email content, the email received will look like this: To troubleshoot any errors that might be seen in the process of retrieving the password reset link, it's helpful to check your browser developer tools and Thingworx application log for details.

Dec 16, 2016

Dec 9, 2016

Nov 29, 2016

The term ‘Extension’ or ‘Plugin’ often has many different meanings. For example, from the point of view of a Product Manager it often means an ‘easy’ way to add additional functionality to an existing piece of software. In contrast, from the point of view of a Software Developer it often means new syntax to memorize, extensive amounts of API documentation to read and very often weeks or even months of trial and error to make this ‘easy’ addition of functionality. We at ThingWorx recognized that in order to be a true Platform we need to take action to make the creation of Extensions easier at all phases of the process. Our development team took on the challenge of understanding what it is that normally makes this such a difficult process, and try and find solutions. We took to the open source community looking for a Platform that could offer our Extension developers a wide array of functionality that was easily accessible and familiar. This is where the Eclipse IDE comes in. We were able to create a Plugin of our own for the Eclipse IDE that makes it easy for an Extension Developer to create an Extension Project, generate ThingWorx specific code, manage all the project configuration and build files and also package the Extension. We can do all of this without having a developer read any API documentation or manually write any code, leaving the Extension Developer to focus on what they are best at, which is adding that additional functionality we mentioned earlier. Extensibility and the true nature of a Platform Extensibility is a core aspect of any true Platform as it allows users to add functionality at any time to meet new and changing requirements. The capabilities of extensions are almost endless but here are a few examples: Adding new UI Widgets to be used to visualize data Adding any custom third party Libraries to be used seamlessly in ThingWorx Easily accessing REST APIs outside of ThingWorx Creating helper Resources to be used across the entire platform Add custom Entities easily to multiple ThingWorx instances Provide custom Authenticators and Directory Services As you can see, it is possible to do practically anything that you or our community might find useful for the Internet of Things. This is the nature of a true ‘Platform’. How do I get started developing an extension? There are three steps that will help you dive into Extension Development quickly. First, an instance of ThingWorx Foundation and the ability to navigate the UI, called Composer. Second, a basic understanding of the ThingWorx Model, or “Thing Model”, is necessary. Finally, you will need an installation of the Eclipse IDE with the ThingWorx Eclipse Plugin installed to get started developing your extension. 1) Getting familiar with ThingWorx Foundation The easiest way to get started playing with the ThingWorx platform is to head over to the Developer Portal and spin up a hosted ThingWorx Foundation server. This is as easy as clicking the ‘Create Foundation Server’ button and a 30-day hosted instance will be created for you to start using as your own personal development playground. If you prefer to set up and work in your own environment, you can also download a Developer Trial Edition to host on your own machine. In order to get familiar with ThingWorx Foundation, I recommend going through our ThingWorx Foundation Quickstart Guide that introduces you to the core building blocks of the platform as well as guide you through a typical scenario of creating a simple IoT application. 2) Understanding the Thing Model Basics If you are already familiar with the Thing Model and know the basics of using the ThingWorx Platform, then you can probably skip over this section. If you aren’t, or just want a refresher, I’ll go over the basics here. The Thing Model is a collection of Entities that define your solution or business model in ThingWorx. You need a Thing Model for a few reasons. For those in software development, the Thing Model and its benefits are very similar to those of the Object Oriented programming model. A good model allows you to maximize reusability, maintainability, and encapsulation. Having a sound Thing Model means that the future of your IIoT solution will be minimally affected by things like migration, iterative changes, permission changes and security vulnerabilities. The three most commonly used and most important Entities within your model are Things, Thing Templates, and Thing Shapes. These entity types will be the main building blocks for your Thing Model. These are only a few of the Entity Types provided by ThingWorx. It is not necessary but definitely recommended, to have a more comprehensive understanding of the Thing Model, and to work with the entire collection of Entity Types within the ThingWorx Platform by going through the ThingWorx Foundation Quickstart Guide on the Developer Portal. 3) Dive into the Eclipse Plugin and develop your own extension Lastly, if you don’t have Eclipse IDE installed, head over to the eclipse.org download page and get one installed on your machine. Once you have that, you can find the Eclipse Plugin on our Marketplace here. In a next step, you will want to create a new Extension Project. We added a ThingWorx Extension perspective that enables all of the custom functionality. Once in the correct perspective, we tried to make our plugin as intuitive as possible. We did this by following as many of the Eclipse usability standards as we could, which means that if you are familiar with the Eclipse IDE you should be able to find most of the ThingWorx functionality on your own. For Example, a simple ‘File’ >> ‘New’ will show you all the options for creating a Project. Creating a new ThingWorx Extension project requires a Name and a ThingWorx Extension SDK (found on the ThingWorx Marketplace) of the version of ThingWorx that you are building your extension for. By utilizing the capabilities of the Eclipse IDE, we were able to automate the creation of many of the artifacts that had slowed extension developers down. The wizard allows the plugin to handle creating and managing a build file and a metadata.xml as well as manage all of the project dependencies. Once you have an Extension Project, you can use the ThingWorx menus to create your Entities. These actions will create the necessary Java files and manage their applicable entry within the metadata.xml of your project. After creating your Entity, you can right click the applicable java file which will show you the ‘ThingWorx Source’ menu. This houses the options to generate the code for additional characteristics (Services, Properties, etc.) making the need to learn all of the custom annotations and method signatures a much less daunting process. Once you have generated some code with the Plugin, it is time to get started implementing your solution - This is the point where my expertise ends and yours begins! If you are interested in getting some more in-depth information on this topic, check out these additional resources: Tutorial: We have created a tutorial that guides you step-by-step through the entire process of developing a ThingWorx extension. Webcast: Watch this 60-minute, interactive deep-dive into IIoT development and learn how to use the Eclipse Plugin to rapidly create a custom ThingWorx extension. Head over to the Developer Portal and start bringing all of your great ideas to life!

Nov 17, 2016

Get MQTT (like mosquitto) operating with SSL - use http://rockingdlabs.dunmire.org/exercises-experiments/ssl-client-certs-to-secure-mqtt as your primary guide to building out your self-signed CA cert and your server cert and key. Simply follow their directions with the one caveat of setting IPLIST and HOSTLIST environment variables prior to executing the generate-CA.sh script. This will be necessary for hosted environments like AWS where the actual IP address of the system cannot be used to access the server from the internet. Put the external facing IP address in IPLIST and the external facing fully qualified domain name (FQDN) into HOSTLIST. If you have multiple usable ip addresses or hostname aliases, enclose them in quotes and separate them with spaces (export IPLIST="1.2.3.4 5.6.7.8") Complete steps 1-3 in the instructions above. This is sufficient to get the MQTT traffic encrypted and use it with Thingworx. Do not proceed until you can make a mosquitto_pub and mosquitto_sub pass data using the --cafile option and get an error if you do not supply the --cafile option. Make sure you have a copy of the ca.crt file generated by the script above to reference in the commands. Note that it may be necessary to use the ip address rather than the FQDN. mosquitto_sub --cafile path/to/ca.crt -h ipaddr -t topic mosquitto_pub --cafile path/to/ca.crt -h ipaddr -t topic -m message Create an MQTT Thing in Thingworx based on the MQTT ThingTemplate. Create a property in the new thing for sending messages to the MQTT broker. In the configuration page for the new MQTT Thing, set the serverName, serverPort and check the useSSL checkbox. In the Property to MQTT topic mappings, create a publish entry that points to the property you created in the thing and set the topic to the mqtt topic on which you want to publish . The ca.crt file created in the above script is the certificate for a new Certificate Authority (self-signed, so not really official). Clients may have to import this certificate into their trusted CA Root store in order to make the encryption work. Add the ca.crt file from the mqtt broker system to a keystore file that will become tomcat's truststore (the list of CAs trusted by the server). See the Tomcat documentation if you need to configure https on tomcat as well. Create a new keystore if one does not already exist as a truststore. keytool -import -trustcacerts -file /path/to/ca/ca.crt -alias CA_ALIAS -keystore path/to/TrustStore -storepass mypassword). Replace the CA_ALIAS with some identifying string like MyPrivateCertificateAuthority. It did not appear to care about the CA_ALIAS value used. Replace path/to/truststore to point to the file that already exists or you want to create. Add the following to the CATALINA_OPTS for starting tomcat -Djavax.net.ssl.trustStore=path/to/TrustStore" -Djavax.net.ssl.trustStorePassword=xxxx Replace path/to/TrustStore with the pathname of the file you created / updated with keytool above. Replace xxxx with whatever password you used in the keytool command above Restart tomcat. Check the mqtt Thing for its isConnected property. It should now be true. If it is not, then check the log files for mosquitto and for tomcat looking for SSL issues. Change the property value and see it appear in the output of a (properly constructed) mosquitto_sub --cafile path/to/TrustStore -t test somewhere.

Sep 15, 2016

Sep 13, 2016

Internationalization and Localization Internationalization (often abbreviated I18N – from "I" + 18 more letters + "n") is the process of developing software that supports many languages, including those with non-Latin character sets. Localization (L10N) refers to developing applications that can be delivered in many languages, relying on the underlying architecture of I18N. This how-to article focuses mostly on localization, since the infrastructure is in place and stable. Create a Localization Table You create a Localization Table entity when you need to add support for another language to the application you're developing. Someone from Sales has said "There's an opportunity if we can deliver the Spiffy application in Estonian." This suggests that an Estonian-speaking end user should be able to run Spiffy and see all of its labels, messages, prompts, dialogs, and so on in Estonian. Most of the cost of adding Estonian language support is in a (usually contracted) service that does the English-to-Estonian (or whatever target language) translations. Such services employ native speakers who can get the nuances of translation correct. See Tips for translators below for suggestions on improving the accuracy of the translation. In Composer, view the Localization Tables list. Begin by duplicating an existing table (e.g. check Default or another language and click Duplicate) or by clicking New. A new tab will open with a New Localization Table in edit mode. The fields shown are: Locale (required). This is the official language tag of the new language. Language tags are defined by an Internet standard, IETF BCP 47. Briefly, they consist of a standard abbreviation for a language (e.g. en for English, de for German), followed optionally by a script subtag (e.g. Cyrl for Cyrilic), followed optionally by a region code (a country code, such as CH for Switzerland or HK for Hong Kong, or a U.N. region number), followed optionally by other qualifiers such as dialect. A simple example is es, Spanish. A complex one is sl-Latn-IT-nedis, Slovenian rendered in Latin characters as spoken in Italy in the Natisone dialect. Software rarely needs such highly specific language tags; the most specific practical examples are the various scripts and regions for Chinese (e.g. zh-Hans-CN, zh-Hant-TW). Language Name (Native) (required). This is the name of the language as written in that language, such that it would be readable by a native speaker. For example, 日本語 for Japanese, ਪੰਜਾਬੀ ਦੇ for Punjabi, or Deutsche for German. Language Name (Common). This is the name of the language as written in a common administrative language. For an application delivered internationally, English is probably a safe choice. Administrators at a customer site might change these to be in the language of the headquarters country. Description. Free form text describing the language. This will appear to end-users as a tooltip as they hover over language choices. Tags. Standard ThingWorx entity tags. Home Mashup. Does not apply. Avatar. An icon for this language. The default is . No other icons are delivered as standard, but language selection interfaces in many products use national flags to help distinguish choices, and those could be supplied here. Avatars are 48x48px images. There may be political implications in choosing a flag or other symbol for a language; use caution. Note that subtags of a language tag are separated by a hyphen, as in zh-Hans-SG. Using underscore is a Java convention that does not conform to BCP 47.A complete properties definition for Czech might look like this: Once the table has been created and saved, you can edit the translated text in Composer. Under Entity Information, select Localization Tokens. A grid similar to this will appear: The columns shown are: Token Name. This is the symbol used by mashup developers to insert a localized string into a certain place in a widget. For example, no matter how the phrase "Add New Page" is rendered (Neue Seite hinzufügen, Adicionar nova página, 새 페이지 추가...) the application developer is only concerned that the token addNewPage appears on the proper widget. See How tokens are resolved below for more information. This Language. How the text is to be represented in this language, that is, the language of the Localization Table currently being viewed or edited. Language. How the text has already been represented in any other language currently defined on the system. This is simply for reference purposes, to compare one translation with another. Usage. Can be set to Label, Message, or left unspecified. This is a guide to translators, who have to be concerned about the size of translated text. Usage Label suggests that the text needs to fit in a confined space, such as in a column header or on the face of a button. Usage Message suggests that the text is meant for a popup, error message, help, or somewhere that full sentences can be accommodated. Context. This is a free-form text field to provide instructions, advice, context, or other explanatory material to the translator. For the token book, for example, the context field can distinguish between the senses of book (something to read), book a table, book a sale, or book a prisoner, which may all have different translations. Translations can be entered in Composer. However, it's also likely that a third-party translator will do the work without using this editor. See Tips for translators below. Define language preferences for a user The reason for localization is to present user interfaces in the best language for a given user. To support this, each ThingWorx user is associated with one or more languages – those that that user can read comfortably. Some applications might offer just one language or a few, some many, and the supported languages may or may not overlap. So each user defines an ordered preference list, saying in effect: my best language is Catalan, but I'm decent in Spanish, and if those aren't available I did spend a few years in Hungary, and as a last resort there was some French in school. This would be represented in ThingWorx as: ca,es,hu,fr. A user from Scotland might have language preference en-UK,en, meaning that English with United Kingdom spellings and vocabulary is best (tyre, windscreen), but if not available then any English will do (tire, windshield). (It is not necessary to spell out related preferences of this type – see How tokens are resolved.) Any application then interacts with a given user in the best language that the application and user have in common.To define the language preference(s) for a user, open the Users list in Composer: Then choose an existing user to edit, or click New to create a new account. The only localization related information here is the Languages field. An administrator who knows the names of available languages may edit or paste an ordered, comma-separated list into the Languages field (e.g. ca,es,hu,fr-CA). Clicking the Edit... button brings up a drag-and-drop preferences editor: The column on the left shows available (unselected) languages. The column on the right shows this user's languages, with the top entry being the most preferred language. Dragging a language from left to right adds it to the user's list; from right to left removes it; dragging rows up and down on the right changes the preference order. As language entries are dragged, a highlight appears to show where they might be dropped: A user with no language preference set will have all tokens resolved from the Default and System tables. Language Preferences can be set programmatically, as detailed in KCS Article CS243270. Localize Mashups The job of the application developer is to keep hard-coded natural language strings out of applications. To support this, widgets define an attribute isLocalizable: true for widget properties that can contain text. This shows up in the Mashup editor as a globe icon next to each localizable property. In this example, both the Text and ToolTipField properties are localizable: Clicking the globe icon changes the property from static to localized. The appearance in the Mashup editor changes accordingly: Clicking the magic wand icon opens the localization token picker: The list of tokens on the right corresponds to the Token Name column in the Localization Table editor. This is the key that is common to the meaning of a word or phrase, independent of its translation into natural languages. Select one from the list, or click to create a new one. Enter the token name and its Default (usually English) value: Note that, complying with best practices for extension developers, the token name has been namespaced: this token belongs to Acme Inc.'s Spiffy application. The rest of the name is descriptive and may reflect other development standards.When a new token is created, it becomes available to edit in every configured Localization Table. If these are not updated, then the default (English) value will be shown wherever the token occurs. How tokens are resolved What happens at run time when the UI needs to display the value of a localization token? The answer is determined by the current user's language preferences the set of Localization Tables configured on the system the presence or absence of a translation for a given token in a given table To visualize this, picture the user's language preferences as a stack, with the most preferred language on top and the least one sitting on the floor – where the floor consists of the Default and System Localization Tables: The user's language preference is fr,pt,ru,hi (French, Portuguese, Russian, Hindi, with French most preferred). The system is configured with Localization Tables, which have no order, for it (Italian), fr-CA (Canadian French), ru (Russian), pt-BR(Brazilian Portuguese), es (Spanish), and the default (likely Engish). Now the UI needs to present this user with the best value for the token com.acme.spiffy.labelAssembly. To resolve this, we start at the top of the stack. Is there a fr Localization Table? There is. Does it contain a translation for com.acme.spiffy.labelAssembly? For the sake of illustration, assume that it does not – perhaps other applications have French support, but the Spiffy application doesn't, so there aren't any com.acme.spiffy.* tokens in the French Localization Table. So we still need a value. Continuing down through the user's preferences, the next acceptable language is pt. Is there a pt localization table? No. There is a Brazilian Portuguese translation, but that won't help a user from Portugal. Still looking, we move to the next language, ru. Is there a ru Localization Table? There is. Does it contain a translation forcom.acme.spiffy.labelAssembly? It does: Ассамблея – so the token has a value, and that is what gets displayed in the UI. Suppose that the user's preferences were more specific, something like this: The users's language preference is fr-CA,pt-BR,ru-Cyrl-RU,sl-Latn-IT-nedis (Canadian French, Brazilian Portuguese, Russian in Cyrillic characters as used in Russia, Slovenian in Latin characters as used in Italy where the Natisone River dialect prevails). ThingWorx treats this by internally expanding the stack to include acceptable fall-back languages. In effect, it looks like: Of the four languages that the user can accept and that the system defines (fr-CA, fr, pt-BR, ru) the first one containing the desired token determines its value in the UI. Token and translation management for applications While it's possible to edit localized values using the Localization Table editor in Composer, translations are usually done in bulk by subject-matter experts. While workflow will vary among organizations and projects, the following example illustrates the basic process. ACME, Inc. is developing a ThingWorx application called Cambot for controlling security cameras. ACME's developer begins by constructing a mashup: This is the first draft. There is an area for the video widget, to be added later, and some button and label widgets for choosing and controlling a camera. The widgets have been given static labels: As shown here, the text for the pan left button has been entered simply as "Pan Left." But the Cambot app needs to be localized, and delivered in English, French, and Spanish. The next step for the developer is to replace all of the static text with localization tokens. Clicking the globe icon to the left of the label property changes the text from static to tokenized: and adds a magic picker for localization tokens. This is a new application, and will need its own set of localization tokens. To create the one for "Pan Left," click the magic wand to open the tokens picker: and then click "+ Localization Token" to add a new one. A dialog opens prompting for the token name and its default (English) value: Note that the token name has been namespaced for two reasons: to prevent conflicts with tokens from other sources, and to allow the developer and translators to work only with application-specific tokens. On clicking "Add Localization Token," the token is created and the default value saved. The mashup builder now shows: . After all of the tokens needed by the application have been defined, they and their values may be seen on the Localization Tokens editor for the Default Localization Table. By entering the namespace prefix in the filter textbox, the display can be restricted to the tokens for this application: As application development continues, and more tokens are required, this process is repeated. When tokens are defined, the developer should edit the Default Localization Table to supply Usage and Context information for each one: Finally, it's time to do the translations for French and Spanish. First, create the localization tables for those languages, as described above in "Create a Localization Table." From the Import/Export menu, select EXPORT / To File: Then, depending on the file format desired, choose either the Entities or Single Entity tab. For Entities, set the Collections value to Localization Tables, enter the namespace in the Token Prefix field, and choose XML as the Export Type: This will produce a single output file, containing a Localization Table element for every language defined on the system – in this example, English, French, and Spanish -- but including only the com.acme.cambot tokens. For Single Entity, choose the language to export, specify the prefix, and choose XML: This must be repeated, once for each language, and creates a separate XML file for each. In either case, the translator should be supplied with the Default XML and the file for the language to be added. (Or, the tokens and values may be converted to and from other formats, depending on the requirements of the translation service. In any case, the translated values must be in the same XML format before they can be imported.) The Default export file will contain a <Rows> element like this: < Rows > < Row > < usage > <![CDATA[label]]> </ usage > < name > <![CDATA[com.acme.cambot.buttonnext]]> </ name > < context > <![CDATA[Button to switch view to next camera]]> </ context > < value > <![CDATA[Next Camera]]> </ value > </ Row > < Row > < usage > <![CDATA[label]]> </ usage > < name > <![CDATA[com.acme.cambot.buttonpanleft]]> </ name > < context > <![CDATA[Button to pan view to the left]]> </ context > < value > <![CDATA[Pan Left]]> </ value > </ Row > < Row > < usage > <![CDATA[label]]> </ usage > < name > <![CDATA[com.acme.cambot.buttonpanright]]> </ name > < context > <![CDATA[Button to pan view to the right]]> </ context > < value > <![CDATA[Pan Right]]> </ value > </ Row > < Row > < usage > <![CDATA[label]]> </ usage > < name > <![CDATA[com.acme.cambot.buttonprev]]> </ name > < context > <![CDATA[Button to switch view to previous camera]]> </ context > < value > <![CDATA[Prev. Camera]]> </ value > </ Row > < Row > < usage > <![CDATA[label]]> </ usage > < name > <![CDATA[com.acme.cambot.buttontiltdown]]> </ name > < context > <![CDATA[Button to tilt view down]]> </ context > < value > <![CDATA[Tilt Down]]> </ value > </ Row > < Row > < usage > <![CDATA[label]]> </ usage > < name > <![CDATA[com.acme.cambot.buttontiltup]]> </ name > < context > <![CDATA[Button to tilt view up]]> </ context > < value > <![CDATA[Tilt Up]]> </ value > </ Row > < Row > < usage > <![CDATA[label]]> </ usage > < name > <![CDATA[com.acme.cambot.buttonzoomin]]> </ name > < context > <![CDATA[Button to view more detail]]> </ context > < value > <![CDATA[Zoom In]]> </ value > </ Row > < Row > < usage > <![CDATA[label]]> </ usage > < name > <![CDATA[com.acme.cambot.buttonzoomout]]> </ name > < context > <![CDATA[Button to expand view]]> </ context > < value > <![CDATA[Zoom Out]]> </ value > </ Row > < Row > < usage > <![CDATA[label]]> </ usage > < name > <![CDATA[com.acme.cambot.labelcamera]]> </ name > < context > <![CDATA[Label for current camera name]]> </ context > < value > <![CDATA[Camera:]]> </ value > </ Row > < Row > < usage > <![CDATA[label]]> </ usage > < name > <![CDATA[com.acme.cambot.labelrecording]]> </ name > < context > <![CDATA[Notice displayed when camera is recording]]> </ context > < value > <![CDATA[Recording]]> </ value > </ Row > </ Rows > Whereas the French and Spanish export files will contain an empty <Rows/> element. This is where the new translations should be added. When the translations are ready, check that the <LocalizationTable> attributes (name, description, languageCommon, languageNative) are correct. Then import the new languages and inspect the results using the Localization Table editor. Localization tables for an application may be bundled into an extension .zip file as other entities are handled; on import, the tokens for the application will be merged with existing localization tables for the same language. In the case that a brand new language is being introduced, note that many widgets use tokens from the System localization table. These will need to be translated as well – however, there is no easy way to restrict the set of tokens to those actually used. At present this is a manual filtering step. For existing languages, check to see if the System tokens have already been translated. Important note on character encoding In handling the export, transmission and editing of XML files, it's important to ensure that UTF-8 encoding is maintained throughout. Encoding problems can show up either as errors when the file is re-imported, or as localized strings with question marks or other unexpected characters in place of accented letters. ThingWorx must run with UTF-8 as the default file encoding. Specify the Java option -Dfile.encoding=UTF-8 on launch. Windows In %CATALINA_HOME%\bin\setenv.bat, include this command: set CATALINA_OPTS=-Dfile.encoding=UTF-8 Tips for translators Each token in an exported Localization Table XML file is defined by four fields: name, value, usage, and context. While name might be suggestive, it is actually arbitrary and should not be relied on. Value contains the natural language value for the token in another language (as agreed upon). Translating from this language into the target language is the object. Usage hints at constraints on the size of the translated text. ThingWorx widgets do not in general resize to fit contents; so a button label, column heading, field label, etc. may be more difficult to translate. Because the default language is likely to be English, and English is a particularly compact language, the application may have been designed with narrow constraints. Such tokens should be marked as tricky by having a usage value of Label. Tokens with a usage of Message are for strings in more adaptable spaces, such as a texarea, warning message, etc. Context allows the application developer to provide translation hints. This may disambiguate synonyms, explain usage, discuss space constraints, specify tone of voice, or anything else applicable. The interesting section of a language's XML representation is contained in the <Rows> element. For example: <Rows> example 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 < Rows > < Row > < usage /> < name > <![CDATA[com.acme.spiffy.labelPart]]> </ name > < context /> < value > <![CDATA[Part]]> </ value > </ Row > < Row > < usage > <![CDATA[Label]]> </ usage > < name > <![CDATA[com.acme.spiffy.labelAssembly]]> </ name > < context > <![CDATA[Label identifying the name of the assembly being edited, appears as Assembly: external_name]]> </ context > < value > <![CDATA[Assembly]]> </ value > </ Row > < Row > < usage > <![CDATA[Message]]> </ usage > < name > <![CDATA[com.acme.spiffy.warningIncomplete]]> </ name > < context > <![CDATA[Pop-up warning message on Save]]> </ context > < value > <![CDATA[A referenced part is missing, undefined, or not allowed in this assembly.]]> </ value > </ Row > </ Rows > In this example, the token defined in lines 2 through 7 is missing the translation cues usage and context. The translator's only option is to intuit the sense of "Part" – is it a noun or a verb? – and attempt a reasonable guess. Access to a running example of the application would clearly be helpful. Lines 8 through 13 identify a label and describe how it is used; lines 14 through 19 do the same for a message. The translator would know that space for the translation of "Assembly" might be limited but that the warning message can be expressed naturally. A translator working on French might then edit this file as follows (again, only the <Rows> element is illustrated): After translating 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 < Rows > < Row > < usage /> < name > <![CDATA[com.acme.spiffy.labelPart]]> </ name > < context /> < value > <![CDATA[Partie]]> </ value > </ Row > < Row > < usage > <![CDATA[Label]]> </ usage > < name > <![CDATA[com.acme.spiffy.labelAssembly]]> </ name > < context > <![CDATA[Label identifying the name of the assembly being edited, appears as Assembly: external_name]]> </ context > < value > <![CDATA[Assemblée]]> </ value > </ Row > < Row > < usage > <![CDATA[Message]]> </ usage > < name > <![CDATA[com.acme.spiffy.warningIncomplete]]> </ name > < context > <![CDATA[Pop-up warning message on Save]]> </ context > < value > <![CDATA[Une partie référencé est manquant, indéfini, ou non autorisés dans cette assemblée.]]> </ value > </ Row > </ Rows > Note that only the <value> elements need to be translated – the context and usage are hints for the translator. System tokens for international data formats There are several tokens used for formatting that are also subject to localization. Token Default value Notes datepickerDayNamesMin Su,Mo,Tu,We,Th,Fr,Sa Day-of-week abbreviations used in calendar heading. datepickerFirstDay 0 First day of the week, 0 for Sunday, 1 for Monday... datepickerMonthNames January,February,March,April,May,June,July,August,September,October,November,December Month names used in calendar heading. dateTimeFormat_Default yyyy-MM-dd HH:mm:ss Date and time format codes are defined by the moment.js library. dateTimeFormat_FullDateTime LLLL dateTimeFormat_LongDate LL dateTimeFormat_LongDateTime LLL dateTimeFormat_MediumDate ll dateTimeFormat_ShortDate l dateTimeFormat_TimeOnly LT shortDateFormat mm/DD/yyyy See also KCS Article CS241828 for details about numeric localization. Allowing users to set their own language preferences It may not be practical for the Administrator to set the language preferences for each user. An application may elect to expose the preferences editor to the end user, so that each user may select from the available languages those that are useful. To support this, ThingWorx Composer offers a Preferences widget in the Mashup builder. The widget may be inserted into any application wherever the designer chooses. It may be tied to a button or menu item, or simply appear in a layout with other widgets – perhaps along with application-specific preferences and other settings. To use the Preferences widget, design a mashup for it to appear in. The minimal case would be a responsive page mashup containing nothing but the preferences widget. Add the Preferences widget by dragging it into place: A placeholder for the widget appears in the mashup: The widget may be customized by setting various properties: These properties are specific to the Preferences widget: ShowClearRecent: Check this to include the option for the user to clear the Most Recently Used history. You may specify a localized tooltip. ShowRestoreTabs: Check this to include the option for the user to set tab restoration to ask, always, or never. You may specify a localized tooltip. ShowLanguages: Check this to include the option for the user to edit language preferences. You may specify a localized tooltip. ShowUserName: Check this to label the preferences widget with the user's name. ShowUserAvatar: Check this to label the preferences widget with the user's avatar, if one is defined. Style: Style the preferences widget itself. ButtonStyle: Style the Clear Recent and Edit buttons. These should probably be set to the application's primary button style. After adding the Preferences widget to a mashup, provide some way for the user to navigate to it, consistent with the application's UI design. The mashup may be tied to a menu entry, or assigned to a Navigation widget, or included in a page within the application's workflow – whatever suits the application design. Here is an example of providing access to preferences through a button in the application's title area: 1) The Navigation widget is placed in the page header. 2) The MashupName property is set to the mashup containing a Preferences widget. 3) The TargetWindow property is set to Modal Popup. 4) For a more interesting UI, the button label is bound from the user's name. At runtime, the example looks like this: Note that there is also a menu item leading to the mashup with the Preferences widget.

Aug 15, 2016

Part I – Securing connection from remote device to Thingworx platform The goal of this first part is to setup a certificate authority (CA) and sign the certificates to authenticate MQTT clients. At the end of this first part the MQTT broker will only accept clients with a valid certificate. A note on terminology: TLS (Transport Layer Security) is the new name for SSL (Secure Sockets Layer). Requirements The certificates will be generated with openssl (check if already installed by your distribution). Demonstrations will be done with the open source MQTT broker, mosquitto. To install, use the apt-get command: $ sudo apt-get install mosquitto $ sudo apt-get install mosquitto-clients Procedure NOTE: This procedure assumes all the steps will be performed on the same system. 1. Setup a protected workspace Warning: the keys for the certificates are not protected with a password. Create and use a directory that does not grant access to other users. $ mkdir myCA $ chmod 700 myCA $ cd myCA 2. Setup a CA and generate the server certificates Download and run the generate-CA.sh script to create the certificate authority (CA) files, generate server certificates and use the CA to sign the certificates. NOTE: Open the script to customize it at your convenience. $ wget https://github.com/owntracks/tools/raw/master/TLS/generate-CA.sh . $ bash ./generate-CA.sh The script produces six files: ca.crt, ca.key, ca.srl, myhost.crt, myhost.csr, and myhost.key. There are: certificates (.crt), keys (.key), a request (.csr a serial number record file (.slr) used in the signing process. Note that the myhost files will have different names on your system (ubuntu in my case) Three of them get copied to the /etc/mosquitto/ directories: $ sudo cp ca.crt /etc/mosquitto/ca_certificates/ $ sudo cp myhost.crt myhost.key /etc/mosquitto/certs/ They are referenced in the /etc/mosquitto/mosquitto.conf file like this: After copying the files and modifying the mosquitto.conf file, restart the server: $ sudo service mosquitto restart 3. Checkpoint To validate the setup at this point, use mosquitto_sub client: If not already installed please install it: Change folder to ca_certificates and run the command : The topics are updated every 10 seconds. If debugging is needed you can add the -d flag to mosquitto_sub and/or look at /var/logs/mosquitto/mosquitto.log. 4. Generate client certificates The following openssl commands would create the certificates: $ openssl genrsa -out client.key 2048 $ openssl req -new -out client.csr -key client.key -subj "/CN=client/O=example.com" $ openssl x509 -req -in client.csr -CA ca.crt -CAkey ca.key -CAserial ./ca.srl -out client.crt -days 3650 -addtrust clientAuth The argument -addtrust clientAuth makes the resulting signed certificate suitable for use with a client. 5. Reconfigure Change the mosquitto configuration file To add the require_certificate line to the end of the /etc/mosquitto/mosquitto.conf file so that it looks like this: Restart the server: $ sudo service mosquitto restart 6. Test The mosquitto_sub command we used above now fails: Adding the --cert and --key arguments satisfies the server: $ mosquitto_sub -t \$SYS/broker/bytes/\# -v --cafile ca.crt --cert client.crt --key client.key To be able to obtain the corresponding certificates and key for my server (named ubuntu), use the following syntax: And run the following command: Conclusion This first part permit to establish a secure connection from a remote thing to the MQTT broker. In the next part we will restrict this connection to TLS 1.2 clients only and allow the websocket connection.

Aug 8, 2016

The following videos are provided to help users get started with ThingWorx: ThingWorx Installation Installing ThingWorx (Neo4j) in Windows ThingWorx PostgreSQL Setup for Windows ThingWorx PostgreSQL for RHEL ThingWorx Data Storage Introduction to Streams Introduction to Value Streams Introduction to DataTables Introduction to InfoTables ThingWorx Concepts & Functionality Introduction to Media Entities Using State Formatting in a Mashup Configuring Properties ThingWorx REST API REST API (Part 1) REST API (Part 2) ThingWorx Edge SDK Configuring File Transfer with the .NET SDK ThingWorx Analytics *new* Getting Started with ThingWorx Analytics Part 1 Getting Started with ThingWorx Analytics Part 2 Installing ThingWorx Analytics Builder Part 1 of 3 Installing ThingWorx Analytics Builder Part 2 of 3 Installing ThingWorx Analytics Builder Part 3 of 3 Creating Signals in the Analytics Builder How to Access the ThingWorx Analytics Interactive API Guide ThingWorx Widgets How to Create and Configure the Auto Refresh Widget How to Create and Define a Blog Widget How to Create and Configure a Button Widget How to Use the Divider and Shape Widgets How to Create and Configure a Chart Widget How to Use a Contained Mashup How to Use the Data Filter Widget How to Use an Expression Widget How to Create and Configure a Gauge Widget How to Create and Configure a Checkbox Widget How to Use a Contained Mashup Widget How to Use a Data Export Widget How to Use the DateTime Picker Widget How to Use the Editable Grid Widget Using Fieldset and Panel Widgets How to Use the File Upload Widget How to Use the Folding Panel Widget How to Use the Google Location Picker How to Use the Google Map Widget How to Use a Grid Widget How to Use an HTML TextArea Widget How to Use the List Widget How to Use a Label Widget How to Use the Layout Widget How to Use the LED Display Widget How to Use the List Widget How to Use the Masked Textbox Widget Navigation in ThingWorx: Using Menus, the Navigation Widget, Link Widget, and Contained Mashups How to Use the Numeric Entry Widget How to Use the Pie Chart Widget How to Use the Property Display Widget How to Use the Radio Button Widget How to Use the Repeater Widget How to Use the Slider Widget How to Use the SQUEAL Search Widget How to Use the Responsive Tab Widget How to Use the Tag Cloud Widget How to Use the Tag Picker Widget How to Use the TextArea and TextBox Widgets How to Use the Time Selector Widget How to Use the Tree Widget How to Use the Value Display Widget How to Use the Web Frame Widget How to Create and Define a Wiki How to Use the XY Chart Quick note: Thread will be updated with more videos as they are added.

Jun 6, 2016

To setup the Single-Sign On with Windchill, we can just follow steps in Windchill extension guide. However, there is a huge problem to use "Websocket" for EMS or Edge SDKs from devices since Apache for Windchill blocks to pass "ws" or "wss" protocol. It's like a problem of a proxy server. There might be a couple of ways to avoid this issue, but I suggest to change filter-mappings for the SSO filter. When you look at the Windchill extension guide, it says that users set filters for all incoming URLs of ThingWorx by using "/*" filter mappings. Please use below settings for "web.xml" of ThingWorx server to avoid the problem that I stated above. It looks quite long and complicated, but basically the filter mappings from settings for "AuthenticationFilter" which are already defined by default except "Websocket" related urls.  <filter> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <filter-class>com.ptc.connected.plm.thingworx.wc.idp.client.filter.IdentityProviderAuthenticationFilter</filter-class> <init-param> <param-name>idpLoginUrl</param-name> <param-value>http(s)://<SERVERHOSTURL>/Windchill/wtcore/jsp/genIdKey.jsp</param-value> </init-param> </filter> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/extensions/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/action-authenticate/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/action-login/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/action-confirm-creds/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/action-change-password/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ThingworxMain.html</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ThingworxMain.html/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Server/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ApplicationKeys/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Networks/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Dashboards/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/DirectoryServices/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Authenticators/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/PersistenceProviderPackages/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/tunnel/wsadapter.jsp</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/tunnel/adapter.jsp</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Logs/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Resources/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Subsystems/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Users/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Home/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/StateDefinitions/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/StyleDefinitions/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ScriptFunctionLibraries/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/AtomFeedService/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/DataShapes/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Importer/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ImageEncoder/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Exporter/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ExportDatabase/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ExportTheme/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ExportDefaultEntities/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ImportDatabase/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/DataExporter/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/DataImporter/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Widgets/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Groups/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ThingPackages/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Things/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ThingTemplates/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ThingShapes/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/DataTags/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ModelTags/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Composer/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Squeal/index.html</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Runtime/index.html</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Mashups/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Menus/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/MediaEntities/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/loaders/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/demos/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ExtensionPackageUploader/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/ExtensionPackages/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/FileRepositoryUploader/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/FileRepositoryDownloader/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/FileRepositories/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/xmpp/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/LocalizationTables/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/Organizations/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/RemoteTunnel/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderAuthenticationFilter</filter-name> <url-pattern>/PersistenceProviders/*</url-pattern> </filter-mapping> <filter> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <filter-class>com.ptc.connected.plm.thingworx.wc.idp.client.filter.IdentityProviderKeyValidationFilter</filter-class> <init-param> <param-name>keyValidationUrl</param-name> <param-value>http(s)://<SERVERHOSTURL>/Windchill/login/validateIdKey.jsp</param-value> </init-param> </filter> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/extensions/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/action-authenticate/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/action-login/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/action-confirm-creds/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/action-change-password/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ThingworxMain.html</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ThingworxMain.html/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Server/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ApplicationKeys/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Networks/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Dashboards/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/DirectoryServices/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Authenticators/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/PersistenceProviderPackages/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/tunnel/wsadapter.jsp</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/tunnel/adapter.jsp</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Logs/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Resources/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Subsystems/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Users/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Home/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/StateDefinitions/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/StyleDefinitions/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ScriptFunctionLibraries/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/AtomFeedService/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/DataShapes/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Importer/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ImageEncoder/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Exporter/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ExportDatabase/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ExportTheme/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ExportDefaultEntities/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ImportDatabase/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/DataExporter/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/DataImporter/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Widgets/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Groups/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ThingPackages/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Things/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ThingTemplates/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ThingShapes/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/DataTags/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ModelTags/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Composer/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Squeal/index.html</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Runtime/index.html</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Mashups/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Menus/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/MediaEntities/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/loaders/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/demos/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ExtensionPackageUploader/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/ExtensionPackages/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/FileRepositoryUploader/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/FileRepositoryDownloader/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/FileRepositories/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/xmpp/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/LocalizationTables/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/Organizations/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/RemoteTunnel/*</url-pattern> </filter-mapping> <filter-mapping> <filter-name>IdentityProviderKeyValidationFilter</filter-name> <url-pattern>/PersistenceProviders/*</url-pattern> </filter-mapping>

Mar 31, 2016

A user can make a direct REST call to Thingworx platform, but when it comes to a website trying to make a REST call. The platform server blocks the request as it is a Cross-Origin request. To enable this feature, the platform server needs to allow Cross-Origin request from all/specific websites. Enabling Cross-Origin request can be done by adding CORS filter to the server. CORS (Cross-Origin Resource Sharing) specification enables the cross-origin requests from other websites deployed in a different server. By enabling CORS filter, a 3rd party tool or a website can retrieve the data from Thingworx instance. Follow the below steps inorder to update the CORS filter: Update web.xml file (located in $CATALINA_HOME/conf/web.xml) For Minimal Configurations, add the below code: <filter> <filter-name>CorsFilter</filter-name> <filter-class>org.apache.catalina.filters.CorsFilter</filter-class> </filter> <filter-mapping> <filter-name>CorsFilter</filter-name> <url-pattern>/*</url-pattern> // "*" opens platform to all URL patterns, recommended to use limited patterns. </filter-mapping> NOTE: the url-pattern - /* opens the Thingworx application to every domain. For advanced configuration, follow the below code: <filter> <filter-name>CorsFilter</filter-name> <filter-class>org.apache.catalina.filters.CorsFilter</filter-class> <init-param> <param-name>cors.allowed.origins</param-name> <param-value> http://www.customerwebaddress.com </param-value> </init-param> <init-param> <param-name>cors.allowed.methods</param-name> <param-value>GET,POST,HEAD,OPTIONS,PUT</param-value> </init-param> <init-param> <param-name>cors.allowed.headers</param-name> <param-value>Content-Type,X-Requested-With,accept,Origin,Access-Control-Request-Method,Access-Control-Request-Headers</param-value> </init-param> <init-param> <param-name>cors.exposed.headers</param-name> <param-value>Access-Control-Allow-Origin,Access-Control-Allow-Credentials</param-value> </init-param> <init-param> <param-name>cors.support.credentials</param-name> <param-value>true</param-value> </init-param> <init-param> <param-name>cors.preflight.maxage</param-name> <param-value>10</param-value> </init-param> </filter> <filter-mapping> <filter-name>CorsFilter</filter-name> <url-pattern>/* </url-pattern> // "*" opens platform to all URL patterns, recommended to use limited patterns. </filter-mapping> NOTE: update the cors.allowed.origin parameter with the desired web address Save web.xml file Restart tomcat For additional information, please follow the official tomcat reference document: http://tomcat.apache.org/tomcat-7.0-doc/config/filter.html#CORS_Filter Tested this using an online Javascript editor (jsfiddle) and executing the below script <script> var data = null; var xhr = new XMLHttpRequest(); xhr.open("GET", "http://localhost:8080/Thingworx/Things", true); xhr.withCredentials = true; xhr.send(); </script> The request was successful and list of things are returned.

Feb 25, 2016

This project is developed out of curiosity of how ThingWorx communicates with sensors and vice versa. Immediately a Smart Parking system idea struck to our mind and I started working on it. While heading from home to office I always worry about car parking space in office especially in rainy season. This project will help user in getting parking space. This project has 4 sections as follows, 1) Smart Parking system: A system application developed in ThingWorx guides user to find empty car parking space. Sensors placed at each car parking slot senses the presence of car. A program running on Raspberry Pi board collects sensor information and sends that information to the Smart Car Parking System application in ThingWorx. The data received through sensor is displayed on ThingWorx dashboard/mashup. 2) Live Traffic: This inherits a Google Map and shows the traffic around user's current location. 3) Traffic Blog: If user is visiting a place and have questions regarding parking, traffic condition etc., then user can post their questions here and people around that area can answer it. Questions are not restricted for parking related questions but like best places to visit in areas, restaurant, shops etc. 4) Automobile Wiki: This page provides an documented help regarding anything related to automobile e.g. how to change car tyres?, how to change car wipers? etc.

Jan 31, 2016

Hello community, I'm happy to announce that I released GitBackup Extension 4.1.0 with some nice help from the community (special thanks to Tanguy Parmentier who provided all the localization export functionality). Many thanks for the people who provided feedback allowing this features to be prioritized. Version 4.1.0 brings several new features to the table: (Finally) Allows the user to specify a subset of Entities for Export Allows importing a single Entity from the Workspace, so it’s easier now to checkout a specific commit in the past and import that file version for testing. Adds the capability to Export localization tokens filtered by a specific prefix - overridable by you at export time. Adds a Log screen that contains log entries for some of the most used methods that caused silent fails. Closed remote branches are auto-pruned. Further cleans the ThingWorx XML source files, by removing the ModelPersistenceProviderPackage. The Main Mashup UI is slightly redesigned: there's a new Manage tab which holds the Settings, Delete Git Thing and more. The Export Mashup UX is improved: export buttons are no longer visible if you don't select a project. Supports ThingWorx 9.0 Two separate releases: one for 8.4&8.5 and one for 9.0 The documentation was updated and I suggest further reading the release notes and specifically the ones regarding the new Log and prune capabilities. In addition, the mechanism that cleans the source code is extensible, and most of the entities are editable, allowing you to tweak it to your own usecase. The Extesion source code is available here: https://github.com/PTCInc/thingworx-gitbackup-extension The importable Extension zip files are available here: https://github.com/PTCInc/thingworx-gitbackup-extension/releases Special note for people using ThingWorx 9.0: in this version some internal ThingWorx SDK Java methods changed their signature, and this required me to build a special releases for 9.0. The extension I built for 9.0 won't run correctly in 8.4/8.5 and also the reverse. As such, you will always see two releases for each GitBackup version: one for 9.0 and one for the 8.4/8.5. My ask for you is the following: don't click on the latest release Github shows - that will always send you to the latest release, which might not be compatible with the ThingWorx version you are using always use the link above to choose the Extension compatible with your ThingWorx version read carefully which release you download. The title contains the ThingWorx version compatible with that release. This Extension is licensed under the MIT Licence and is provided as-is and without warranty or support. It is not part of the PTC product suite. Taking into consideration the statement above: please read first the documentation if you encounter any problems, search first for closed issues, and if none is found for your problem, raise a new issue in GitHub's issue system: https://github.com/PTCInc/thingworx-gitbackup-extension/issues do not open PTC Tech Support tickets for this Extension For OOTB Git support in the ThingWorx platform, please raise a ThingWorx Idea in the PTC Community here https://community.ptc.com/t5/ThingWorx-Ideas/idb-p/thingworxideas Thank you!

Oct 7, 2020

Applicable Releases: ThingWorx Platform 7.0 to 8.5 Description: Introduction to ThingWorx Extension Development, with the following topics: What is an Extension Why building an Extension Prerequisites Installing Eclipse plugin and features Creating entities with the plugin and including exported Entities in an Extension Project Upgrading or Updating and Existing extension in ThingWorx Building with Gradle and Ant ThingWorx Extension Development Guide

Jul 23, 2020

The App URI in the ThingWorx Remote Thing Tunnel configuration specifies the endpoint of the specified tunnel. The default value (/Thingworx/tunnel/vnc.jsp) will point to the built in ThingWorx VNC client that can be downloaded through the Remote Access Widget in a Mashup to provide VNC remote desktop access. Leaving the App URI blank will result in the Tunnel being connected to the listen port on the users machine as specified in the Remote Access Widget. In this case the user must supply the application client (e.g. an ssh client) in order to connect to the tunnel endpoint.

Oct 23, 2015

Good evening and Happy New Year! I launched version 2.3.0 of the GitBackup Extension. The release is available here https://github.com/vrosu/thingworx-gitbackup-extension/releases/tag/V2.3.0 It adds the capability to push commits using User specific Committer Name and Email. This is an optional feature, which allows multiple developers to push commits under their own credentials. The documentation was updated with more details about this. This release certifies the Extension to work for ThingWorx 8.5.x. (Previous ThingWorx versions have not been tested and the documentation was updated accordingly). As always, this extension is not a PTC supported product, so in case you have issues with it, please do not open a PTC Tech Support ticket and instead use GitHub's issue system or the PTC Community. Please feel free to fork and improve it.

Dec 31, 2019

IoT Tips

Analytics Manger 7.4: Part 1 of 2. Create Template And Thing For Real-Time Scoring

Analytics Manager Create Analysis Provider And Start ThingPredictor Agent

How to run service "ConvertJSON" in Universal Converter extension in ThingWorx

How to install hMailServer to send emails via Mail Extensions in ThingWorx

Google e-mail and mail extension: set up and troubleshooting

How to set up the Reset Password feature in the Form login

ThingWorx Analytics Builder - Upload Data

Create Signals In ThingWorx Analytics Builder

How to Rapidly Develop ThingWorx IIoT Extensions with the Eclipse Plugin

Securing the Mosquitto MQTT Broker

Installing Thingworx Analytics Builder part 1 of 3

Managing and using Localization in ThingWorx

Securing MQTT connection to Thingworx platform

ThingWorx Video Tutorials

Setting SSO with Windchill

Make a REST call from a website to Thingworx platform

Smart Parking and Traffic Solution

GitBackup Extension 4.1.0 for ThingWorx 8.4, 8.5 and 9.0

Expert Session: ThingWorx Extension Development

ThingWorx Tunneling App URI's

ThingWorx GitBackup Extension version 2.3.0

ThingWorx Learning Paths

Getting Started on the ThingWorx Platform Learning Path