Verify a farm configuration

To verify a server farm configuration, start all the servers, deploy an application to one of the servers of the farm, and then check the log files of each server to confirm that all servers have been updated.

The purpose of this task is to verify that a farm is configured properly and that administration operations are propagated on all servers of a farm.

1. Start all the servers of the farm.

2. Deploy a MobileFirst application to one of the servers of the farm. Use the operations console or the wladm program with the deploy app command. For more information about the deploy app command, see Commands for apps.

3. Once the operation is completed, review the log file of the application server and search for the entries of class BaseTransaction. Verify that all servers have been updated.

   This is the example of a Liberty log file:

   $ grep BaseTransaction messages.log
          
   [9/22/14 1:03:17:032 CEST] 0000006d com.ibm.worklight.admin.actions.BaseTransaction              I Result: worklight: farm2///169.254.19.0: Preparation to deploy 'Hello' finished
   [9/22/14 1:03:17:251 CEST] 0000006e com.ibm.worklight.admin.actions.BaseTransaction              I Result: worklight: farm1///169.254.19.0: Preparation to deploy 'Hello' finished
   [9/22/14 1:03:19:123 CEST] 00000072 com.ibm.worklight.admin.actions.BaseTransaction              I Result: worklight: farm1///169.254.19.0: Commit
   [9/22/14 1:03:19:123 CEST] 00000072 com.ibm.worklight.admin.actions.BaseTransaction              I worklight: farm1///169.254.19.0: 2014-09-20T23:03:18.608Z: Application 'Hello' was updated
   [9/22/14 1:03:19:138 CEST] 00000071 com.ibm.worklight.admin.actions.BaseTransaction              I Result: worklight: farm2///169.254.19.0: Commit
   [9/22/14 1:03:19:138 CEST] 00000071 com.ibm.worklight.admin.actions.BaseTransaction              I worklight: farm2///169.254.19.0: 2014-09-20T23:03:18.608Z: Application 'Hello' was updated

   Troubleshooting

   • If we use an environment ID (see JNDI properties in server.xml and Configure a MobileFirst project in production using JNDI environment entries), for each server, verify that the environmentId value for the MobileFirst administration service is the same as the environmentId value for the runtime.

   • If we have several servers on the same computer, we must verify that all servers are using a different JMX port:

     • For WAS, the port used for JMX is the SOAP port.

     • For WAS Liberty, the port used for JMX is the HTTPS port.

     • For Apache Tomcat, the port used for JMX is the RMI port, which is specified in the Ant tasks or in the setenv file for a manual installation.

     If the JMX port is not available for a server, the MobileFirst runtime environment cannot start.

Parent topic: Install a server farm