Troubleshooting server farm configuration issues
When you start the Administration Services and the MobileFirst runtime environments, several exception types can be emitted in the application server logs if the configuration of the server farm is incorrect.
Server ID is not set
- MBeanRegistrationException "server id JNDI property is not set".
This is because in the application server configuration, the JNDI property ibm.worklight.admin.serverid is not set.
You must configure the property ibm.worklight.admin.serverid in the application server. Restart the application server. For more information, see JNDI environment entries for MobileFirst projects in production.
Administration Services MBean is already registered
- The Administration Services MBean <MBean name> is already registered on another node of the farm, which means that the JNDI property ibm.worklight.admin.serverid has the same value on other nodes.
This situation occurs because the Administration Services MBean is already registered under the same name on another server of the farm. The value of the JNDI property ibm.worklight.admin.serverid is the same as one defined in another server of the farm.
You must configure the property ibm.worklight.admin.serverid in the application server. This property must be unique among the servers of the farm. Restart the application server.
Use of a Derby database
- MBeanRegistrationException "Derby databases are not supported in a farm of servers".
You must use a DB2®, Oracle, or MySQL database for the runtime and Administration Services databases, because Derby is not supported in server farm topology.