Reverse proxy

Forward proxy sits near the user, best for managed corporate devices.

Reverse proxy sits near the cloud app, best for unmanaged personal devices.

API based connects directly to the provider.

It has no latency, but it isn't real time.

Those were just the deployment shut off to start the new deployment.

And then we changed the URL rewrite rule on the active, no, on the, Apache reverse proxy server to point to the new master node of the cluster.

So switching in between I-110 and I-70 is all controlled by the configuration of that reverse proxy server, what that URL rewrite was defined as.

So again, because we replaced the application servers, and kept the ActiveMQ and Apache Reverse Proxy servers as is.

That allowed for minimal changes to external interfaces like the Teamcenter and SAP interfaces because we did not change the IP address or host name of those servers.

And with the Reverse Proxy, The DNS that people were using to access, the URL that people were using to access the application did not change because DNS changes can take a while to propagate.