Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

This integration was added in v1.4, check out the full release notes for this version here v1.4, v1.4HF1 - July 2019.

...

  • EMS Platform Services API version 44.1.19000.180 or higher. To check your version navigate to your Platform Services status URL e.g. http(s)://<servername>/EmsPlatform/status

  • An EMS Platform Services Integration Account, see the below Integration Account Configuration section for the account requirements

  • Access to the EMS Desktop Client and EMS SQL database

...

Expand
titleIntegration Account Configuration

An integration account is required to enable authentication and two-way communication between ResourceXpress and EMS Platform Services. To create the integration account:

  • Log in to the Platform Services admin page e.g. http(s)://<servername>/EmsPlatform/admin

  • Click Integrations from the left pane.

  • Click New Integration Client

  • Populate the required fields per the below

Name

<Enter a suitable name>

Type

Partner

Role

All Routes

Audience

Client Audience

Active

Yes

Enable Logging

No

Allow this client to book without Everyday User Templates and Ignore Booking Rules

Yes

Everyday User Authentication Required

No

User Authentication is Persistent

No

Everyday User Authentication Method

EMS Native

  • Click Save Changes

A client secret will now be generated and shown at the top of the page. Copy the newly created Client ID and Client Secret for later use.

Note

Once you close this page the client secret will not be viewable and cannot be retrieved.

...

Expand
titleResourceXpress System Settings

Once the Platform Services Integration Account has been created you can configure the integration details in ResourceXpress.

  • Navigate to Administration Settings - System Settings - Resource Server and populate the fields per the below

Server Host Name

Note

The URL entered here is case sensitive and should be entered in the exact format shown on the right including the last '/'

Enter your Platform Services URL in the format

http(s)://<servername>/EmsPlatform/api/v1/

Server Port

80 or 443

Resource Login User ID

Enter the Integration Account Client ID

Resource Login Password

Enter the Integration Account Client Secret

Resource Login Domain

Enter your company domain

  • Click Save

...

Expand
titleEMS SQL IDs

When a booking is initiated using ResourceXpress via a Room Screen, Qubi, Kiosk or Map the booking is created based on specific parameters defined in EMS. To enable RX to use the correct options various SQL IDs need to be retrieved and defined in the application.

Info

Currently the only way to define these values is in the backend configuration of ResourceXpress, please contact helpdesk@qedas.com for assistance setting these up.

SQL IDs for the following options in EMS will be required to complete the configuration:

EMS Option

Description

EMS Database Table

Setup Type

This defines the booking setup type as specified in the EMS Desktop Client Configuration - Facilities - Setup Types

dbo.tblSetupType

Event Type

The defines the booking event type as specified in the EMS Desktop Client Configuration - Other - Event Types

dbo.tblEventType

Status

The defines the booking event type as specified in the EMS Desktop Client Configuration - Administration - Statuses

dbo.tblStatus

Group

This defines the EMS Group account to use for non authenticated device bookings and will be shown as the booking organiser.

dbo.tblGroup

Example

Running the below query in SQL Server Management Studio against the EMS database

Code Block
languagesql
select ID, Description, Active, AllowWebRequest from dbo.tblsetuptype

yields the following results

Image RemovedImage Added

To enable ResourceXpress to create bookings using the Conference setup type the ID 1 would be defined in the application.

Note

The ID specified must be Active (1) and must be set to AllowWebRequest (1)

SQL IDs for the remaining 3 options can be obtained the same way by querying the relevant table in the EMS database

...