PC SOFT

ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Home | Sign in | English EN
New WINDEV Mobile 26 feature!
  • Overview
  • Implementing an MDM solution for a mobile application
  • Step 1: HFSQL server and reserved server setup
  • Step 2: Enable the MDM system in your mobile project
  • Step 3: Generate and upload the application to the MDM (Android)
  • Step 3: Generate and upload the application to the MDM (iOS)
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
To distribute your applications, there are 2 possibilities:
  • use a public store such as App Store or Google Play.
  • directly distribute your applications.
The distribution of professional applications via a public store raises a number of concerns. And the distribution of applications by a direct method is not feasible on a large scale because everything has to be done manually: copy to each device, updates, authorizations.
WINDEV Mobile 26 offers an ideal solution for distributing your professional applications: WINDEV Mobile WINDEV Mobile 26 includes a ready-to-use Mobile Device Management system, which is equivalent to having a private app store.
It is very easy to implement and use:
  1. Install all the prerequisites for using the MDM.
  2. In the project, enable the "MDM" system and compile the applications (iOS and / or Android).
  3. Upload the applications to the MDM server.
  4. Define the authorized users.
  5. Share the URL or QRCode (automatically generated) with the users.
  6. Users will download the application, log in and start using the application.
  7. Then, you can publish new updates: users will be notified, and can accept and automatically download the update.
Caution: In iOS, you will need to enroll as an Organization.
Remark: This help page presents the implementation of the "MDM" system. To implement the User Groupware, see Mobile User Groupware (Android and iOS).
Implementing an MDM solution for a mobile application
To implement an MDM solution for a mobile application:
  1. Configure your server:
    • If you are using a PCSCloud platform, the required elements are installed by default on your platform.
    • If you are not using a PCSCloud platform, Install the following elements:
      • an HFSQL server,
      • the reserved server, requesting the installation of modules for the Mobile User Groupware (WDBaaS).
  2. Enable the MDM system in your mobile project and specify the various parameters requested.
  3. Generate and upload the application to the MDM:

Step 1: HFSQL server and reserved server setup

The following must be installed on a computer to use the mobile user groupware:
  • An HFSQL server.
  • A server reserved for the user groupware.
Remarks:
  • A Web server (IIS, Apache or other) must be installed on the computer on which the reserved server will be installed. The Web server must:
    • be accessible with basic authentication,
    • comply with the HTTPS protocol with a certificate issued by a recognized trust authority for iOS and Android mobile devices,
    • allow a maximum content size of HTTPS responses greater than the size of the installations (IPA & APK).
  • The HFSQL server and the reserved server can be installed on two different computers.
  • The reserved server can be installed on a Web server that also hosts a WEBDEV application server.
HFSQL Server setup:
The HFSQL server setup program is available in the WINDEV or WINDEV Mobile setup package. If you do not own this setup package, the HFSQL server setup can also be found in our site (http://www.windev.com).
To install the HFSQL server from the WINDEV/WINDEV Mobile setup package:
  1. Start the WINDEV/WINDEV Mobile setup program.
  2. Select "HFSQL server setup".
  3. Then, select "Install or update an HFSQL server".
  4. Accept the license agreement.
  5. Choose the platform ("For Windows on this computer").
  6. If HFSQL servers are already installed on the current computer, select "Install a new server".
  7. Select the setup directory and specify the server name and port. The port 4900 will be used by default.
  8. Specify the name and password of the user with management that will be created by default on the HFSQL server. By default, this user is "Admin" and has no password.
  9. Install (if necessary) the HFSQL Control Center if this one is not found or accessible from your computer.
  10. The wizard proposes to configure the sending of notifications in order to identify the server dysfunctions in real time. Select the desired option.
  11. The wizard proposes to enable the authentication via Active Directory. Enable this option if necessary.
  12. Validate (or not) the participation in product improvement by allowing us to collect information regarding the use of our products. This optional and anonymous collect allows PC SOFT to improve the product features.
  13. The setup is performed. By default (if you have not changed the administrator settings), to connect to the server in administrator mode, you must use the "Admin" user without a password.
    Note: For security reasons, don't forget to change the administrator password.
Reserved server setup (WDBaaS)
The MDM server is a WEBDEV application server reserved for the user groupware and the MDM.
To install the reserved MDM server:
  1. Launch the reserved server setup package (WX260PACKRSRV.exe file in the "Install\WDServerR" subdirectory of the WINDEV Mobile setup directory).
  2. Validate the license.
  3. Select the module to install: "Install BaaS modules for the mobile user groupware and Mobile Device Management". Go to the next step.
  4. Select (if necessary) the version of the reserved application server to install (32 or 64-bit). Go to the next step.
  5. Select the setup directory. Go to the next step.
  6. Specify the characteristics of the HFSQL server used for the user groupware/MDM (previously installed):
    • Name of the HFSQL server,
    • Port.
    • Name and password of administrator of HFSQL server. This information is necessary to automatically configure the user groupware/MDM database and the associated user.
  7. Test the connection to check your parameters.
  8. Specify the parameters specific to the database used by the user groupware/MDM:
    • the name of the database dedicated to the user groupware ("GPU", by default).
    • the user name and password of the user groupware administrator.
  9. This database and its user will be automatically created.
  10. Go to the next step.
  11. The wizard checks if there is a Web server on the setup computer.
    • If no Web server is installed on the setup computer, the wizard proposes to install one and to configure it in order to use the server reserved for the user groupware.
    • If there is a web server on the setup computer, the wizard proposes to configure it to use the server reserved for the user groupware/MDM.
  12. At the end of the setup, the wizard displays a summary:
    To connect to the mobile user groupware server,
    use the following parameters:
    - Username: xxx
    - Password: xxxxx

    The parameters HFSQL connection used are as follows:
    - Server: xxx
    - Database: xxxx
    - User: xxx - Password: xxx

    The password for the user groupware files is: xxxx
    Copy and store this information. This username and password for the mobile user groupware server must be used in the user groupware/MDM configuration window in your WINDEV Mobile project.
    Important: The reserved server settings are stored in the following file: "C:\ProgramData\WDBaaS\GPUConnection.default.xml"
    This file must be added to the server backup plan. This file will have to be restored if the server is reinstalled or duplicated on a new physical or virtual machine with the same settings.
  13. Finish the wizard.
Remark: If the database name is incorrect, you can restart the setup of the server reserved to specify the correct database name while keeping the identifiers.

Step 2: Enable the MDM system in your mobile project

To enable the MDM system in your WINDEV Mobile project:
  1. Open your project in WINDEV Mobile.
  2. On the "Project" tab, in the "Project" group, click "GPU / MDM".
  3. In the window that appears, in the "General" tab:
    • Enable MBaaS: click "Enabled".
    • Select the desired feature: "MDM: Management of application versions and updates (private store)".
    • In "GPU and MDM application server (webservice and administration site)", specify the server to use. In the case of a new server, select the type of server to use:
      • PCSCloud platform. In this case, specify the characteristics of your PCSCloud platform.
        Reminder: This option allows you to use a Web server, a dedicated server and an HFSQL Client/Server engine already installed and configured.
      • Network or Internet server with the protocol used. Enter the server name, user and password. This information was provided to you during the setup of the server reserved for the user groupware/MDM.
    • Specify the type of user accounts managed:
      • Accounts shared between applications: This option is used to deploy the application with other applications that will be accessible to the same users. This option is recommended for deployments in different companies.
      • Application-specific accounts: This option is used to store the application with its user database.
        This option is recommended for deploying applications on a store.
    • The URLs of administration sites are automatically filled in with the information previously specified.
      CAUTION: The specified URLs will only work when the user groupware configuration window is validated. Indeed, when this window is validated, the modules installed with the reserved application server are automatically configured.
  4. In the "Connection" tab, specify:
    • how users log in to the application: Two possibilities:
      • Display login window only at first start. The login window will only be displayed at the first start. The information entered for the first connection will be automatically reused for future connections.
      • Authentication at each start. The login window appears at each start. Biometric authentication can be enabled in this case.
    • If offline mode is allowed: The "Offline" mode is implemented when the user cannot use the authentication webservice. In this mode, users who were previously connected to the application can still use the application. Indeed, a file with the user's characteristics and rights is copied locally at each connection with authentication. You can define the number of days allowed in offline mode (0 by default).
    • If users are allowed to create an account: You can allow new users to create an account (not allowed by default).
    • If Sign in with Apple is enabled (iOS application only): This option requires an App Store certificate and is not available if the "MDM" feature has been selected.
  5. In the "Email" tab, specify:
    • The settings of the email sending server: To manage user registration and forgotten passwords, an email is sent to users. To do this, it is necessary to specify the parameters of the SMTP server used.
    • The texts used in the emails sent to users to validate their registration, manage forgotten passwords and install the application.
  6. In the "Advanced" tab, specify:
    • The user groupware customization mode:
      • "Default login window (recommended)": WINDEV Mobile takes care of everything. Simply start the application to use the user groupware.
      • "Customize login window": All elements of user groupware are included in your project via an internal component. You can customize the different elements of the user groupware. However, the evolutions of the product will not be integrated.
    • The user groupware start mode:
      • Automatic start: The user groupware login window is started before any other window of the application. The project initialization code is executed once the login window is opened and validated.
      • Manual start: The login window will only be opened if gpwOpen is used. This option can be used to execute the project initialization code before opening the login window. This option is useful for a multilingual application for example: a window can be displayed to ask for the application runtime language.
    • The file language: By default, data files specific to the user groupware are in English, but you can use data files in French.
  7. In the "MDM" tab, specify:
    • How the updates will be downloaded (Android only):
      • Over Wi-Fi only: users will be able to download updates only if they have Wi-Fi access.
      • Over Wi-Fi and mobile data: users will be able to dowload updates as soon as access is available.
      In iOS, these settings must be defined in the application console.
    • How to notify the user about optional updates. You can notify the user of an optional update by using one of the following methods:
      • Display a window in the application: in this case, an update prompt window will be automatically displayed.
      • Send a notification: in this case, a notification will let the user know there is an available update (notifications must be enabled for the application).
    • The options:
      • Enable automatic check for updates: This option makes it possible to automatically check for available updates. If this option is not selected, this check can be performed by programming using AppUPDAvailable.
      • Display a message if a problem occurs when checking for updates: This option is used to notify the user if an update check could not be performed.
    • Based on the information entered in the MDM settings window, you will get the URL used to install the application on mobile devices. It is also possible to get the corresponding QR Code.
  8. Validate the MDM management window.
Caution: When the user groupware/MDM settings window is validated, the following actions are performed:
  • Addition of the internal component with the user groupware windows (login window customization).
  • Declaration of the current application in the application server reserved for the user groupware/MDM.
  • Activation of user and rights management sites.
  • Update of the XML file that contains the description of the application windows on the server.
  • Definition of a default user, with "supervisor" as username and password.

Step 3: Generate and upload the application to the MDM (Android)

To generate your Android application:
  1. On the "Project" pane, in the "Generation" group, click "Generate".
  2. In the generation wizard, in the "Generation mode" step, select "Generate for free deployment (MDM, corporate fleet, private store, etc.)".
  3. Validate the different steps of the wizard with the desired options.
  4. The apk file of the application is generated in the "Exe" subdirectory of the project directory.
Caution: the Android application version number specified in the generation wizard must be standard, not custom.
To upload the application:
  1. Start an administration site via one of the links in the "General" tab of the user groupware/MDM management window:
    • URL that corresponds to the deployed application. The users and passwords defined will be used when the application is deployed.
    • URL that corresponds to the test mode. The users and passwords defined will be used during a test on the phone ("Go").
  2. Log in to the administration site. Enter "supervisor" both as username and password.
  3. For Android applications, the WDBaaS site allows you to upload versions of the application via its APK. A bar code can be generated to make setup easier on Android devices.

Step 3: Generate and upload the application to the MDM (iOS)

Before generating an iOS application, make sure that you have a certificate that allows you to perform an "In-House" deployment (see In-House deployment)..
To generate your iOS application:
  1. On the "Project" pane, in the "Generation" group, click "Generate".
  2. In the generation wizard, in "Signature", provide the required "Provisioning profile" files.
  3. Validate the different steps of the wizard with the desired options.
  4. The xxx.xcode.gen file of the application is generated in the "Exe" subdirectory of the project directory.
  5. Copy the entire folder generated in the EXE directory to an external media (USB key, external hard disk, shared directory with MAC on network). The name of this directory is <Project name>.xcode.gen.
  6. Paste this folder on the MAC that will compile the application.
  7. Open the folder on MAC and open the file named "Project_name.xcodeproj".
  8. The project is opened in Xcode.
In Xcode (caution: the operations described below are valid as of the date of writing of this document and may be subject to change):
  1. In the "Signing & capabilities" tab, check that you have a valid signing certificate.
  2. Select the compilation options from the drop-down list in the upper-left corner. Select the "Any iOS device" scheme.
    Caution: the "info.plist" file must be in XML format and not in binary format.
  3. To start the compilation, select "Product .. Archive".
  4. Once the process has been completed, a window shows the IPA archive. Click "Distribute App".
    The wizard starts.
  5. In the wizard:
    • Select "Enterprise".
    • Click "Next" twice.
    • The wizard requests the URLs with the application details. Use "https" URLs (simply type "https" in the fields).
    • Click "Next".
    • This step allows you to select the distribution certificate. It is selected by default. Select the corresponding "InHouse" profile.
    • Click "Next".
    • The files are generated. At the end of the generation, click the export button and specify where the ".ipa" and ".manifest" files should be copied.
To upload the application:
  1. Start an administration site via one of the links in the "General" tab of the user groupware/MDM management window:
    • URL that corresponds to the deployed application. The users and passwords defined will be used when the application is deployed.
    • URL that corresponds to the test mode. The users and passwords defined will be used during a test on the phone ("Go").
  2. Log in to the administration site. Enter "supervisor" both as username and password.
  3. The WDBaaS site allows you to upload versions of the application via its archive (".ipa" file and ".manifest" file).
  4. When the app is uploaded, a bar code is generated to easily install the app on iOS devices. Simply share this bar code and users will be able to scan it with their devices. Each user must have been described and activated in the MDM administrator for the production database.
Special case: 1st setup on an iOS device using the bar code
  • When users scan the bar code of the application, they must first accept the application developer's certificate. This must be done only once.
  • iOS downloads the application via HTTPS. If the certificate of the web server that hosts the WDBaaS site was not issued by a trusted authority recognized by iOS, you will need to add the certificate to iOS. The procedure is as follows (checked at the time of writing this document):
    • on the iOS device, click the .cer (received by email, etc.),
    • select the device,
    • a message indicates that the profile has been downloaded ("Profile Downloaded"): click "Close".
    • go to "Settings",
    • select "General",
    • select "Profiles & Device Management",
    • select the profile that was just installed,
    • click "install" and confirm.
    • go back to the "General" menu,
    • select "About",
    • select "Certificate Trust Settings",
    • select the certificate previously added to the profile,
    • activate the certificate,
    • accept the confirmation of addition to the root certificates.
Special case: Application update on iOS devices
If there are changes in the application, users must be able to update. The procedure in Xcode remains the same, you need to create a new archive. Upload the new version (IPA and manifest.plist).
The new version will be available in the MDM administrator. The next time the application is started, the update prompt will appear automatically.
Remarks:
  • Only the "Supervisor" can access the application management site.
  • A specific banner lets you know if the application management site is used in test mode.
Minimum version required
  • Version 26
Comments
Click [Add] to post a comment