What is the most secure way to communicate with the Application Workspace SaaS server?
A satellite server allows a cloud zone to communicate with on-premise resources as well as can act as a “content distribution point”. The satellite server, when started, reaches out to your zone and opens a web socket to it and keeps the socket open, which allows the zone to send content and access resources when it needs to.
The Application Workspace Servers needs to connect to the Satellite server over port 443. When the Application Workspace server is a SaaS in the cloud, the satellite server needs to be accessable from the internet on port 443. Is this correct?
Actually, satellite servers use web sockets. In theory, you don’t have to open up the ports, when the satellite server starts, it should establish a connection to the cloud environment and keep the connection open… So shouldn’t need to open up the ports.
That would be great. The documentation is not that clear: Firewall settings . I only use the Satellite server for a connector, so there are no URI’s in User Portal > Device > Content Access. Unfortunately, I am not able to test this right now.
Once the satellite server is connected, you can add it as a content source under Content Access. Once you add it there, it will show up in that location. You can also add it on a Context directly as well if you don’t want it as a global setting.
You can see that it is connected via the Servers section as well… And then you can use it where you want it. But if you want to use it as a content server, you need to go into the settings on the Satellite server and make sure content is enabled. And then in Servers, you can specify to use it for Content Distribution.