Find out the constraints and the deployment mode of the administration service, live
update service, and the runtime per server topology.
The live update service must be always installed with the administration service on the same
application server as explained in MobileFirst Server administration service to MobileFirst Server live update service. The context root of the live update service must define in this way:
/<adminContextRoot>config. For example, if the context
root of the administration service is /mfpadmin, then the context root of the
live update service must be /mfpadminconfig.
You can use the following topologies of application servers:
- Stand-alone server: WebSphere® Application Server Liberty
profile, Apache Tomcat, or WebSphere Application Server full
profile
- Server farm: WebSphere Application Server Liberty
profile, Apache Tomcat, or WebSphere Application Server full
profile
- WebSphere Application Server Network Deployment cell
- Liberty collective
Modes of deployment
Depending on the application server topology that you use, you have two modes of deployment
choice for deploying the administration service, the live update service and the runtime in the
application server infrastructure. In asymmetric deployment, you can install the runtimes on
different application servers from the administration and the live update services.
- Symmetric deployment
- In symmetrical deployment, you must install the MobileFirst
administration components (MobileFirst Operations Console, the
administration service, and the live update service applications) and the runtime on the same
application server.
- Asymmetric deployment
- In asymmetric deployment, you can install the runtimes on different application servers from the
MobileFirst
administration components.
Asymmetric deployment is only supported for WebSphere Application Server Network Deployment cell
topology and for Liberty collective topology.