Install MobileFirst Server administration with the Server Configuration Tool

Use the Server Configuration Tool to install and configure MobileFirst Server administration.

Verify that the user who runs the Server Configuration Tool has the privileges described in File system access rights.

Restriction:

• Does not support server farms. Therefore, we cannot use this tool to install, upgrade, or configure a server farm.

• MobileFirst Server is not supported for production use on Mac OS X.

1. Start the Server Configuration Tool.

   • On Linux: In the desktop menu, click IBM MobileFirst Platform Server > Server Configuration Tool.

   • On Windows: In the Start menu, click IBM MobileFirst Platform Server > Server Configuration Tool.

   • On Mac OS X: In the Finder, double-click the file MF_INSTALL/shortcuts/configuration-tool.sh.

     The MF_INSTALL placeholder represents the directory where you install MobileFirst Server. mf_server is the shortcut for MobileFirst Server.

2. Select Create a MobileFirst Server Configuration.

3. Name the configuration.

4. In the Configuration Description window:

   1. Enter the context root of the MobileFirst Administration REST service.

      The context root is used to create the URL to the MobileFirst REST Administration service. This URL is typically in the form <host:httpsport>/contextroot or <host:httpport>/contextroot.

   2. Enter an environmentId.

      This ID is optional and is used to distinguish between different deployments of the MobileFirst Server administration components in the same application server environment, for example in the same cell of WAS ND.

      Important: Review carefully this environment ID. It must match the environment ID of all the runtime environments managed by this MobileFirst Server administration component. If we install or upgrade MobileFirst runtime environments with separate Ant files, this verification is particularly important because the environmentId attribute must match. For a server farm, all installations must also have the same environmentId attribute.

      The environmentId attribute is an attribute of the following Ant tasks:

      • installworklightadmin, updateworklightadmin, and uninstallworklightadmin, which are documented at Ant tasks for installation of operations console and administration services.

      • configureapplicationserver, updateapplicationserver, unconfigureapplicationserver, which are documented at Ant tasks for installation of MobileFirst runtime environments.

5. In the Console Settings window, enter the context root of the operations console.

6. In the Database Properties window:

   1. Select the database type: IBM DB2 , MySQL, or Oracle.

   2. In the next window, enter the details to connect to the database instance.

   3. In the Database Additional properties window, enter the parameters to connect to the administration database.

   4. If the database administrator did not create the databases in step Create administration database (Optional), enter database administration credentials in the database creation request window.

      For IBM DB2 and for Oracle, we must have an SSH access to the host where the database management system (DBMS) is installed.

      The Server Configuration Tool creates the database for you.

7. In the Application Server Choice window:

   1. Select the application server type: WebSphere Application Server, WAS Liberty profile, or Apache Tomcat.

   2. In the Application Server window, enter the data so we can deploy IBM MobileFirst Platform Foundation to that application server.

   3. Depending on the application server...

      • If the application server is WAS Liberty profile, or Apache Tomcat, select Create a default user to declare a user who can log in to the console as administrator to the operations console

      • If the application server is WebSphere Application Server, select Declare the WebSphere Administrator as an administrator of IBM MobileFirst Platform operations console to allow the WebSphere administrator to log in to the operations console.

      For more information about further configuration of security roles, see Assign administration roles to users and groups.

8. When all the data is entered, click Deploy.

   The following effects take place.

   1. If the database administrator did not complete step Create administration database (Optional), the database for the MobileFirst Server administration is created and access rights are granted to the user specified in the database additional properties window.

   2. If the tables for MobileFirst administration do not exist in the database, they are created.

   3. The MobileFirst administration components are installed in the application server and are connected to the database.

9. Restart the application server

10. If we are in an environment where protect the password of the user who can log in to the console as administrator to the operations console, follow the steps in Secure the MobileFirst Server administration.

11. Open the console.

    If the context root of the console was not changed in the Console Settings window, you find it at <host:httpsport>/worklightconsole, or if HTTPS is not supported in the application server, at the unsecured URL <host:httpport>/worklightconsole.

What to do next

Install a MobileFirst runtime environment. See Deploy MobileFirst Server using the Server Configuration Tool.

Parent topic: Install administration services and the operations console