For up-to-date product documentation, see the IBM MobileFirst Foundation Developer Center.
Constraints on MobileFirst Server administration service, MobileFirst Server live update service and MobileFirst runtime
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.
We 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 we 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, we can install the runtimes on different application servers from the administration and the live update services.
- Symmetric deployment
- In symmetrical deployment, we 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, we 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.
- Stand-alone server topology
We can configure a stand-alone topology for WebSphere Application Server full profile, WebSphere Application Server Liberty profile, and Apache Tomcat.- Server farm topology
We can configure a farm of WebSphere Application Server full profile, WebSphere Application Server Liberty profile, or Apache Tomcat application servers.- Liberty collective topology
We can deploy the MobileFirst Server components in a Liberty collective topology.- WebSphere Application Server Network Deployment topologies
The administration components and the runtimes are deployed in servers or clusters of the WebSphere Application Server Network Deployment cell.- Using a reverse proxy with server farm and WebSphere Application Server Network Deployment topologies
We can use a reverse proxy with distributed topologies. If your topology uses a reverse proxy, configure the required JNDI properties for the administration service.
Parent topic: Constraints on the MobileFirst Server components and MobileFirst Analytics