Publishing Services and Web Client Binaries to the Server

After you have configured all the required services for an app, you need to publish the app. Publishing allows your app to start using the Quantum service in real-time. After an app is published, Quantum Fabric generates the code that you can integrate with platform SDKs.

NOTE: You can upload maximum up to 10 Web Client Binaries for an app.

IMPORTANT: When you publish an app to an environment, all the identity services associated with the app are published only to the selected run-time environment. The latest published Identity Services will affect any other apps in the same environment if they use these identity services.

The latest published identity services on the current environment will not affect any apps in different environments.

Based on environments created, Quantum Fabric Console allows you to publish apps to the environments.

Publishing services and Web client binaries of apps can be done in two ways:

NOTE: For On-premises only:

To skip a .war file if you have uploaded it for Web platform under the Manage Client App Assets tab, select the Allow Manual Publish Only check box in the Add a New Environment window.

IMPORTANT:  Make sure that your Quantum Fabric Console version used for creating apps is same as Quantum Fabric runtime components’ (Integration, Sync, and Messaging) versions. All the components of Quantum Fabric must be upgraded to same versions.

For example, if the Quantum Fabric Console installed version is V8 for creating your apps, you must use the same Quantum Fabric version for runtime components to publish your apps. If there is a version mismatch, Quantum Fabric’s Publish functionality and other runtime server components may not work as expected.