...
The NETx Server provides an interface which can be used to integrate information from the hotel management system RMS CloudMews. Using this interface, information about the check-in/check-out procedure , the hotel guests and the hotel room states can be retrieved.
The communication is based on a REST full HTTP web service protocol that is using JSON objects as data payload . The RMS Cloud software and a websocket to retrieve events like check-in / check-out or changing room status. The Mews cloud service is the web API client server and our the NETx Server server is the web API serverclient.
Integration steps
To start, open the menu Modules > RMS Cloud > Mews > Configuration.... . With the dialog, specify at least the Client ID, the Client Password and the RMS Url.
...
Then, the used properties and areas (hotel rooms) have to be defined. This is done within the menu Modules > RMS Cloud > Property definitions. Each definition line corresponds to one property/area (room).
...
After having defined all rooms, the configured rooms are shown within the item tree. You will find the items under the sub tree NETx\XIO\RMS.
...
The retrieved information from the RMS Cloud is stored as Server Items. Here all available Server Items that are available for each room are listed (including their access rights)the Access Token and the User TokenID must be specified. This information can be retrieved from your Mews cloud account.
For a production environment, the Platform and Websocket URL can be kept at their default values. If other environments (e.g. the demo environment) are used, the corresponding URLs have to be entered too.
Afterwards, the Core Server can be started. During startup, the Core Server connects to the Mews cloud service and tries to fetch the available hotel rooms.
To check that the connection was successful, open the item tree and navigate to NETx > XIO > Mews and verify that the GATEWAY item is set to true.
...
| Note |
|---|
If the connection is not successful, please search server system logs for warning and error messages. |
The retrieved hotel rooms are shown in the sub item tree Rooms.
...
For room, the following items are available:
Item name | Data type | Access | Notes |
|---|---|---|---|
DescriptionId | String | read only | Specified within room Definitions within NETx ServerShows the resource ID within the Mews system. |
RoomChecked | Boolean | read only | True if at least 1 guest is check in this room – false if all guests are checked out. |
RoomCheckedForecast | Boolean | read only | True if there is a forecast check in for this room – false if all guests are checked out. |
RoomStatus | String | read and write | Room status |
GuestName | String | read only | Guest name that is received from RMSCloud. |
GuestTitle | String | read only | Guest title that is received from RMSCloud. |
GuestLanguage | String | read only | Language code that is received from RMSCloud. E.g. EN, DE, ... |
GuestArrivalDate | DateTime | read only | Arrival data and time of guest. Normally, this is equal to the check-in data and time. |
GuestDepartureDate | DateTime | read only | Scheduled departure data and time of guest.the room is currently booked (Mews reservation state Started) – false otherwise. |
RoomStatus | int | read only | Mews status of the hotel room. The following states are available:
|
RoomStatusText | String | read only | Text representation of the room status |
During the first startup, all available hotel rooms are fetched from the Mews cloud service and stored within the Room Definitions. This definition can be found in the Core Studio in the menu Modules > Mews > Room definitions.
If you would like to use not all available rooms, you can selected the corresponding rooms and convert them to comments. After having saved the definition file, the commented rooms will be deleted from the server item tree.
| Note |
|---|
Do not delete unnecessary rooms from the room definition. If rooms are deleted, they will be added again at the next server startup. |
...
Article applies to the following products:
...