The EMS is now attempting to talk to the ThingWorx platform.
However, ThingWorx does not have detailed information about the Edge device that is attempting to connect to it, so it will show up in theUnboundcategory.
On the left, clickMonitoring.
ClickSTATUS > Remote Things.
Confirm that you see theEdgeThinglisted in the Unbound section.
NOTE: The nameEdgeThingcomes from the config.lua script. EdgeThing is simply the name that is in that script, hence the name that you see in ThingWorx. To change the name of the device, you could stop both wsems.exe and luaScriptResource.exe, edit config.lua to use a different Thing name other than EdgeThing, and then restart both of the WSEMS programs. At that point, the Thing showing up inRemote Things -> Unboundwould be whatever name you changed to in config.lua.
Create a Remote Thing
Now that the EMS is communicating with Foundation, let's create a Remote Thing to which Foundation can tie said connection.
Note that the namemustmatch the spelling and capitalization of the Thing's name that you entered in the EMS's config.lua for it to auto-connect.
If Project is not already set, search for and select PTCDefaultProject.
In theBase Thing Templatefield, search for and select RemoteThingWithTunnelsAndFileTransfer.
At the top, ClickSave.
Note the status-indication pop-up indicating that EdgeThing is now connected.
Use Services to Explore EMS Files
Now that your Remote Thing is Saved and Connected, we can use some of the built-in Services to explore the EMS folders and files which we previously created for testing purposes.
At the top ofEdgeThing, clickServices.
Under theExecutecolumn, click thePlay SymbolforBrowseDirectory.
In the top-leftpathfield, type/and click the bottom-rightExecutebutton.
Note theotherandtwfolders which we previously created for testing.
In the top-leftpathfield, type/twand click the bottom-rightExecutebutton.
Note thetw_test_01.txtfile which we previously created for testing.
As thetw_test_01.txtfile (and its parent folder) were items which we custom-created for this guide, you should now be 100% convinced that connectivity between Foundation and the EMS is dynamically working.
If so desired, you could explore into other folders (or even add additional files to these folders), run theBrowseDirectoryService again, and confirm that Foundation is now aware of the EMS and actively communicating.
Step 6: Next Steps
Congratulation! You've completed theInstall the Edge MicroServer (EMS)guide.