Hi Theresa, you can of course access mashups remotely using correct URL pattern as to your all the following questions I would say it goes back to the discussion we had in your other thread Is it possible to send a PUT-Request to an remote localhost?
Do note that it also contains the link to the blog REST API Overview and Examples explaining URL pattern on accessing the mashups e.g. http://localhost/Thingworx/Mashups/BasicMashup?appKey=b101903d-af6f-43ae-9ad8-0e8c604141af&x-thingworx-session=true
As per my understanding; you can replace the localhost with your IP and access it on your local machine. And you can also access it on other remote machines which are in same network. But you will have to add exception in your Firewall to allow access to ThingWorx port outside your machine.
If you want to access the mashup on internet; you will have to host ThingWorx so that it is available for access on internet.
I assume by hosted Ankit Gupta meant getting ThingWorx as a service from PTC Cloud Service, which in other words would mean buying that service as you mentioned. To put it simply PTC Cloud Services will install and provide you the ThingWorx access i.e. access to the composer which you can open/access anywhere.
Otherwise you could leverage your IT support to help make your local server addressable over the Internet - which in other words mean your machine's name/IP will be addressable over Internet. Part of which we discussed in one of your old thread, which I referenced above.
Hope it helps!
By hosting I mean setup/install Thingworx on a server which has public IP (usually static) and is access over the internet. As Sushant mentioned you will have to reach out your IT team for that.
I hope it helps.
as basically said by Ankit, this is solved by replacing "localhost" in your URL's by the IP of the host (your PC), and allowing access to the port in the Firewall and/or NAT-router.
1) you construct a working URL like "http://localhost/Thingworx/Mashups/BasicMashup?appKey=b101903d-af6f-43ae-9ad8-0e8c604141af&x-thingworx-session=true" from Sushant
2) you replace "localhost" by "127.0.0.1", this is a technical IP equal to the string "localhost", the behavior should not change:
3) you find out the IP of Your PC using "Windows Control Panel\All Control Panel Items\Network and Sharing Center", or "ipconfig" or "ifconfig"
If you access this IP (which is 192.168.1.7 in the example below) from your PC or from a PC/Device connected to the same Router, the behaviour should not change. In case from a different PC/Device you experience difficulties, then (Windows) Firewall is blocking the connection, check it's settings.
Ports in question are, among others, 80, 8080, 8087, this you can find out by looking in your Thingworx settings or by trying, which of the links is working
4) You can find out the global IP of your PC by googling some "geolocation" site which will tell your apparent IP (example 204.142.02.223)
5) If you have a NAT-Router (most users have) This router needs to be set to forward incoming traffic to your PC-IP:Port like "192.168.1.7:8087" or to place Your PC in a DMZ. Refer to the manual of the router for this.
Alternative here is a direct access to the internet (either static IP or dynamic IP), in this case the IP from step4 and step3 would be identical in short terms (during a day).
6) Access from outside should work with:
Step 5 exposes your PC and/or Thingworx Port to incoming traffic (from anybody knowing on the internet) which means you should be sure one more time, that you have the appropriate level of security according to the value of your system.