Connecting the PULSE.Wemobile mobile application

Open Configurator and, from the main menu, go to:

Configuration → Configuration Extensions

Add a new extension using the following details:

• Name: PulseWemobile
• Prefix: PWM_
• Purpose: Add-on

Load the extension file (PulseWemobile.cfe) by clicking once on the row containing the newly added extension and, in the Configuration Extensions window, select:

Configuration → Load Configuration from File…

If compatibility errors occur between the extension and your configuration (compatibility mode, language, etc.), click Fix (on the right) and accept the recommended changes.

Clear the checkbox in the Safe Mode column, as the extension’s HTTP service must interact with network requests from the mobile application.

Update the database:

For users who will use the mobile application to connect to the database, add a new role from the extension:

1.  Open the Administration → Publish to Web Server…

2. In the settings window, clear all unnecessary checkboxes and:

• specify the publication name and the directory on the server;
• on the HTTP Services tab, enable “Publish extension HTTP services by default.”

It should look approximately like this:

3. Click the Publish button. The system will prompt you to restart the web server (IIS/Apache) — confirm the restart.

Important: Please note that this publication also makes your database available for standard access through the so-called Web Client. Therefore, this must be disabled at the web server level.

The example below is for the built-in Windows web server, IIS:

Go to the directory specified in the previous step (filled in automatically). Most likely, it will be:

C:\inetpub\wwwroot\pulse-wemobile

There you will find the default.vrd file. Open it in a text editor and add the attribute enable=”false” to the root <point> tag.

Example:

<?xml version=”1.0″ encoding=”UTF-8″?> 

<point xmlns=”http://v8.baf.com.ua/8.3/virtual-resource-system” 

xmlns:xs=”http://www.w3.org/2001/XMLSchema” 

xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” 

base=”/ім’я бази” 

ib=”File=&quot;шлях-до-бази&quot;;” 

enable=”false”> <!–Disables access for the web client and thin client. –> 

2. Click “Set Settings”:

3. Enter your server address (the full URI of the HTTP service added in Step 2) and generate an “Identifier”:

4.(Optional) Since each connection under a new user account, even if only temporary, will use one licence from your database, you can additionally specify a “technical user” in the Authorisation section of this form to conserve licences:

In this case, different users of the mobile application will still be able to sign in using their own usernames and passwords, but when connecting directly to BAF, the session will automatically be created under the specified technical user.

Also, to ensure that licences are actually conserved at the web server level, this must be specified in the publication file. An example for the built-in Windows web server, IIS, is shown below: Go to the directory specified in Step 2.2. Most likely, this is C:\inetpub\wwwroot\pulse-wemobile. There you will find the default.vrd file. Open it in a text editor and, within the <httpServices> block (most conveniently at the end of it, immediately before </httpServices>), add the following block:

<!– ADD!!! — Configure a pool for 1 persistent session so that licences are not consumed –>

<service name=”PulseWemobile:PWM_Mobile”

rootUrl=”pwm_mobile”

enable=”true”

reuseSessions=”autouse”

sessionMaxAge=”120″

poolSize=”1″

poolTimeout=”40″>

<accessTokenAuthentication> <issuers/>

<accessTokenRecepientName/>

</accessTokenAuthentication>

</service>

Also, since we have explicitly defined the HTTP service, it is advisable to additionally disable the default publication of HTTP services in this file so that, if the database contains HTTP services from other extensions, they are not published.

To do this, the publishByDefault and publishExtensionsByDefault attributes of the <httpServices> tag must be set to false:

Replace:
<httpServices publishByDefault=”true”

publishExtensionsByDefault=” true “> щадити ліце

На: <httpServices publishByDefault=”false” publishExtensionsByDefault=”false”>

5. After that, click “Save” on the settings form and then click “Send”. A QR code for quick authorisation in the mobile application will appear on the screen.

2. For its “Collect Events” and “Send Events” commands, set the required schedule.

3. Then save the changes.

1. How to log in:

   1. Open the application.
   2. Tap “Scan QR Code” and scan your QR code with the camera.
   3. Enter your username and password, then tap “Log In.”

4. Wait a moment. The first login may take up to a minute — this is normal, as the application is establishing a connection to your database.

5. From then on, you will be able to log in to the application using biometrics.

6. Done! The application’s home screen is now open — you can start working.