For up-to-date product documentation, see the IBM MobileFirst Foundation Developer Center.


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.

In this topology, all the administration components and the runtimes are deployed in a single Java™ Virtual Machine (JVM).

Figure 1. Topology of a stand-alone server

Architecture of a stand-alone server topology with MobileFirst Operations Console, the administration service, and the live update service with its corresponding database and three runtimes, each with its own database.

With one JVM, only symmetric deployment is possible with the following characteristics:


Configuration of JNDI properties

Some JNDI properties are required to enable Java Management Extensions (JMX) communication between the administration service and the runtime, and to define the administration service that manages a runtime. For details about these properties, see List of JNDI properties for MobileFirst Server administration service and List of JNDI properties for MobileFirst runtime

Stand-alone WebSphere Application Server Liberty profile server

The following global JNDI properties are required for the administration services and the runtimes.

Table 1. Global JNDI properties for administration services and runtimes in WebSphere Application Server Liberty stand-alone topology
JNDI properties Values
mfp.topology.platform Liberty
mfp.topology.clustermode Standalone
mfp.admin.jmx.host The host name of the WebSphere Application Server Liberty profile server.
mfp.admin.jmx.port The port of the REST connector that is the port of the httpsPort attribute declared in the <httpEndpoint> element of the server.xml file of WebSphere Application Server Liberty profile server. This property has no default value.
mfp.admin.jmx.user The user name of the WebSphere Application Server Liberty administrator, which must be identical to the name defined in the <administrator-role> element of the server.xml file of the WebSphere Application Server Liberty profile server.
mfp.admin.jmx.pwd The password of the WebSphere Application Server Liberty administrator user.

Several administration components can be deployed to enable the same JVM to run on separate administration components that manage different runtimes.

When we deploy several administration components, we must specify:

  • On each administration service, a unique value for the local mfp.admin.environmentid JNDI property.
  • On each runtime, the same value for the local mfp.admin.environmentid JNDI property as the value defined for the administration service that manages the runtime.
Stand-alone Apache Tomcat server

The following local JNDI properties are required for the administration services and the runtimes.

Table 2. Local JNDI properties for administration services and runtimes in Apache Tomcat stand-alone topology
JNDI properties Values
mfp.topology.platform Tomcat
mfp.topology.clustermode Standalone

JVM properties are also required to define Java Management Extensions (JMX) Remote Method Invocation (RMI). For more information, see Configuring JMX connection for Apache Tomcat.

If the Apache Tomcat server is running behind a firewall, the mfp.admin.rmi.registryPort and mfp.admin.rmi.serverPort JNDI properties are required for the administration service. See Configuring JMX connection for Apache Tomcat.

Several administration components can be deployed to enable the same JVM to run on separate administration components that manage different runtimes.

When you deploy several administration components, we must specify:

  • On each administration service, a unique value for the local mfp.admin.environmentid JNDI property.
  • On each runtime, the same value for the local mfp.admin.environmentid JNDI property as the value defined for the administration service that manages the runtime.
Stand-alone WebSphere Application Server

The following local JNDI properties are required for the administration services and the runtimes.

Table 3. Local JNDI properties for administration services and runtimes in WebSphere Application Server stand-alone topology
JNDI properties Values
mfp.topology.platform WAS
mfp.topology.clustermode Standalone
mfp.admin.jmx.connector The JMX connector type; the value can be SOAP or RMI.

Several administration components can be deployed to enable the same JVM to run on separate administration components that manage different runtimes.

When we deploy several administration components, we must specify:

  • On each administration service, a unique value for the local mfp.admin.environmentid JNDI property.
  • On each runtime, the same value for the local mfp.admin.environmentid JNDI property as the value defined for the administration service that manages the runtime.

Parent topic: Constraints on MobileFirst Server administration service, MobileFirst Server live update service and MobileFirst runtime