Mobile Center - Linux Installation

This section describes how to install the server on a Linux machine. For information about installing the server on a Windows machine, see Mobile Center - Windows Installation.

Before you start

Before installing Mobile Center, make sure that:

  • Your server machine meets the system requirements.
  • You have root or sudo permissions.
  • The host name of the server machine is accessible. Check this by running the following command:
    ping -c 1 "hostname"

Install Mobile Center as a new installation

Follow these steps to install Mobile Center as a full installation where no previous version is installed:

  1. Download the Linux server zip file.

  2. Log in as root on your Linux machine, or as a user in the Linux sudoers file.
  3. Copy the zip file to /root, your home directory.
  4. Extract the server installation files:
    unzip <name of Linux server file>.zip –d <Target directory Name>
  5. Change directory to the SERVER directory in the Target directory:
    cd <Target directory Name>/SERVER
  6. Run the installer:

    As root user:
    ./<install_server-x64 file name>.bin

    As a user in the Linux sudoers file:
    sudo ./<install_server-x64 file name>.bin

    The installation wizard displays the Introduction page. Read the contents and press Enter.

  7. The installation wizard displays the License agreement. Press Enter to move through the pages and press Y to accept the agreement.
  8. If you are doing an upgrade, the wizard warns you that you may lose existing applications during the upgrade. Press Y to accept this warning.
  9. Choose an installation folder. The default is /opt/mc/.


  10. Configure the Linux OS user:
  11. To use an existing Linux OS user, select Y and provide the user name.

    Caution: Do not use root or a user from the sudoers file as the name for this user.

    If you select n, Mobile Center creates a default Linux OS user mc. Provide a new password for this user.

  12. Configure the Mobile Center server according to the following guidelines:

    FQDN or IP address

    The fully qualified domain name (FQDN) consists of the host name and the domain name. For example, myhost.microfocus.com. The FQDN must begin with an English alphabetical character. FQDNs beginning with numbers are not supported.

    SSL connection

    Specify if the connection to the server should be over SSL only.

    The default is Y (secure connection only.) Note: If you choose the SSL option, all connections to the server from connectors and testing tool machines will need to be secure.

    Note:  

    • The SSL setting affects all connectors and testing tools that integrate with the server. When configuring the Mobile Center settings in connectors and tools, make sure that your selection matches that of the server.
    • When you specify an SSL connection, the setup installs a self-signed certificate. To use a CA certificate, import it after the installation. For details, see Using SSL certificates issued by a Certification Authority (CA).
    Server port

    By default, the installation is set to SSL on port 8443. The default non-SSL uses port 8080.

    Free port to be used internally by Mobile CenterDefault: 8081
    admin@default.com userThe installation creates a default administrator user, admin@default.com, for accessing the Mobile Center Lab Management console. Specify a password for this user.
  1. At the PostgreSQL Configuration stage, the installation prompts you to indicate whether to use an external PostgreSQL database. If you want to use the PostgreSQL version embedded with Mobile Center, skip to the next step. Note that Mobile Center 2.80 supports PostgreSQL version 9.60.

    Using an external database lets your organization utilize existing database resources and manage them with all of their other systems. When prompted Do you want to use an external PostgreSQL database, type "y".

    Enter the port, schema, admin user name and password of the external database. After you enter the password, the installation will attempt to connect to the database with the provided credentials.

  2. When using an embedded version of the PostgreSQL database, configure PostgreSQL according to the following guidelines.
  3. Database server port Default: 5432
    PostgreSQL superuser password

    When the PostgreSQL server is first installed, a superuser account postgres is created automatically. The superuser is needed to create the Mobile Center database schema, and to add a user for administering the database. The superuser can override all access restrictions within the database, so it is best to carry out most operations using a non-superuser role.

    You need to provide a password for the superuser:

    • The password must be between 6-20 English characters long (any alphabetical character, numbers, and the special characters "@" and "_" are permitted) 
    • Contains at least one digit, one uppercase and one lowercase English character.
    PostgreSQL database administrator username

    The installation creates an additional user for administering the database. This user is not a superuser and has permissions to perform operations only on the Mobile Center database.

    You need to provide a username for the database administrator (Default: MCadmin). The user name may consist of any lowercase English alphabetical characters, numbers, and the special character "_".

    Do not use postgres as the name for this user.

    PostgreSQL database administrator password

    You need to provide a password for the database administrator.
    The password must contain at least one digit, one uppercase and one lowercase English character, and must be between 6-20 English characters long. Any alphabetical character, numbers, and the special characters "@" and "_" are permitted.
  4. Review the pre-installation summary and press Enter to continue with the installation.
  5. The installation takes several minutes to complete. When the installation is complete, a message is displayed that the server was installed and provides options to:
    • Allow collection of anonymous data for the improvement of the product. You can modify your selection for this option after installation, in the Administration Settings.
    • Start the service. Unless specified otherwise during the installation process, by default, the server starts on port 8443 (HTTPS).

Caution: To insure integrity and confidentiality of the information stored with Mobile Center, we strongly recommend that you incorporate filesystem monitoring on the Mobile Center installation and temporary folders.

Back to top

Upgrade the Mobile Center server

Mobile Center 2.80 can be installed as an upgrade to Mobile Center 2.70. If you are using an earlier version of Mobile Center, first upgrade to version 2.70.

To ensure a smooth upgrade see Best practices for upgrades.

Packaged apps: 
To run the app packager upgrader on iOS apps, you must have already set up your Mac machine as described in Set up automatic app packaging and signing services

If your apps were packaged manually from the command line and then uploaded to Mobile Center, the upgrader will not be able to upgrade the apps. You will need to repackage your apps using the latest version of the MC Enabler (iOS) or the Android Enabler, before uploading them to Mobile Center.

Follow these steps to upgrade the Mobile Center server:

  1. Download the MC Linux Server zip file.

  2. Log in as root on your Linux machine, or as a user in the Linux sudoers file.
  3. Copy the zip file to /root, your home directory.
  4. Extract the server installation files:
    unzip <name of Linux server file>.zip –d <Target directory Name>
  5. Change directory to the SERVER directory in the Target directory:
    cd <Target directory Name>/SERVER
  6. Run the installer:
    As root user:
    ./<install_server-x64 file name>.bin

    As a user in the Linux sudoers file:
    sudo ./<install_server-x64 file name>.bin

    The installation wizard displays the Introduction page. Read the contents and press Enter.
  7. Read the License Agreement, and select y to accept the terms and proceed with the installation.
  8. The installer detects that this is an upgrade and warns you accordingly. When you upgrade from 2.70, all existing apps remain associated with their corresponding workspaces.
  9. Enter the PostgreSQL superuser password.
  10. In the Packaging Upgrade Configuration screen, indicate whether you want to automatically run the app packager upgrader at the end of the setup (Default. y). The upgrader enables you to upgrade your packaged apps in one operation, instead of having to upload each app again to Mobile Center. Note that if you choose not to run the upgrader, you can run can run it manually at the end of the setup. For details, see Upgrade packaged apps with the app upgrader.

  11. If you choose to upgrade the packaged apps, the next screen prompts you to specify the credentials for the Mobile Center user, and to select the operating systems of the apps you want to upgrade.
  12. If you are upgrading from 2.70 and you want to use an external postgreSQL database in the 2.80 installation:

    1. Create a backup of the original database in the form of a hp4m.bin file. For details, see Export the original database.
    2. Create the following roles in the external database: mc_sa, mc_security, and MCadmin.
    3. Restore the database on the machine, specifying the external database location. For details, see Prepare your new server.
  13. When the installation is complete, a message is displayed that the server was installed, and provides an option to allow collection of anonymous data for the improvement of the product. You can modify your selection for this option after installation, in the Administration Settings.
  14. Exit the installer.
  15. After upgrade:
    • Clear the browser cache before logging into the Lab Management console. Testing engineers should clear the browser cache on their testing tool machines before connecting to Mobile Center.
    • iOS: Re-sign the Agent and Launcher apps with your Developer certificate. For details, see Connect iOS mobile devices.

    Caution: To insure integrity and confidentiality of the information stored with Mobile Center, we strongly recommend that you incorporate filesystem monitoring on the Mobile Center installation and temporary folders.

Back to top

Stop, start, or restart the server

You can stop and start the Mobile Center server with the following commands:

  • To start the server: service mc start
  • To stop the server:  service mc stop
  • To restart the server: service mc restart

Back to top

Best practices for upgrades

To ensure a smooth upgrade and prevent the loss of data, we highly recommend first performing an upgrade on a test machine, with the same operating system as your production machine. If the upgrade succeeds on the test machine, you can then proceed to upgrade your production server.

Prepare for the upgrade

Before you start the upgrade process, do the following:

  1. If you are using the iOS packager service, upgrade it to the new version before you run the upgrade process. For details, see Set up automatic app packaging and signing services.
  2. Decide if you would like to upgrade your applications during the upgrade process, as you will be prompted during the setup.

    • If you upgrade your apps, take into consideration that it may add more time to the upgrade process.
    • If you do not want to upgrade your apps, to reduce the downtime of Mobile Center for your users, you can update the apps after the upgrade. For details, see Upgrade packaged apps with the app upgrader.
  3. Back up your existing Mobile Center database. For details, see Export the original database.
  4. Prepare a testing machine with the same operating system as your production environment. Other hardware parameters such as CPU and RAM can be different. This machine will serve as a test environment for the upgrade.

Perform the upgrade

To ensure a successful upgrade, we recommend that you perform an upgrade on the test machine that you prepared above. Follow these steps:

  1. Install your current Mobile Center server version on the test machine with the same operating system as your production environment.
  2. Import the original database to the test machine. For details, see Prepare your new server.
  3. Verify that the import was successful by logging into Mobile Center on the testing machine and verifying the apps, devices, settings, and so forth as indicated in the Upgrade checklist. Note that you will not be able to communicate with those connectors, since they were configured to work with the production machine—not the test machine.

  4. Locate the server installation file for the Mobile Center version to which you want to upgrade.
  5. Extract its contents and run the file on the test machine as described in Upgrade the Mobile Center server. If you encounter any difficulties during the upgrade, contact Support.
  6. Verify that the import was successful by logging into Mobile Center on the test machine and verifying the apps, devices, settings, and so forth as indicated in the Upgrade checklist.
  7. Optional: Install a new connector on the upgraded test machine and attempt to run a test through one of the integrated testing tools.
  8. If all of the above information is correct on the test machine, proceed to Upgrade the Mobile Center server on your production machine.

Upgrade checklist

After the upgrade process has completed on the test machine, check the following items to ensure that the upgrade succeeded:

  • Login. Log in to Mobile Center as an admin user.
  • Users. Check that all the users were migrated to Mobile Center in the ADMINISTRATION > Users page.
  • Settings. Check that all the Administration Settings were migrated from the production environment.
  • Apps. If you chose to upgrade your applications during the upgrade process, make sure that all of your apps are visible in the APPS screen.
  • Connectors. Verify that all the connectors are visible in the DEVICES > Connectors page. Note that you will not be able to communicate with those connectors, since they were configured to work with the production machine—not the test machine.
  • Devices. Make sure that you see all of the production environment's devices.

If there are any missing items or if you encounter any other issues, contact Support.

Back to top