Run Visual Builder Applications On Other Servers

While it's possible to run Visual Builder web applications on other web servers, you do lose some functionality.

Specifically:

• Business objects won't run, because they require the Visual Builder back end.
• You can't use Identity Cloud Service to manage your users, roles, or authentication, so you'll have to manage these aspects of your app.
• The Visual Builder server authentication proxy manages connections to REST services, so you'll need to define your Visual Builder services to use a "Direct (Bypass Authentication Proxy)" connection. The calls are then made directly from the browser to the remote REST service. See How Does the Fixed Credentials Authentication Method Work? for more information.

If these limitations are acceptable, then you can host your Visual Builder app on another server.

To modify your app to do this:

• Use the direct access to your REST services, and switch the set of services that the app is accessing. One way is by doing a global search and replace, to update the address of the server hosting the REST services that provides data to the app. This will allow the back end to be on-premise.
• Ensure that you've allowed anonymous access to the app. Identity Cloud Service won't be available to manage authentication.
• Create a zip file that contains the app ready to be deployed. See Optimize Your Builds and Audit Your Code Using Grunt for information on how to do this.

You can take this optimized version of the app and host it as a regular collection of HTML/JavaScript resources on a web server.