Basic architecture
The NETx BMS Server provides the opportunity to integrate hotel room status information from an Infor Hotel Management System (HMS). The following figure shows how the integration has to be done.
...
The Infor HMS provides a standardized interface based on the SOAP protocol to establish a two-way communication between the NETx BMS Server and the Infor HMS to synchronize the status of hotel rooms and receive updates such as check in, check out, and room move.
On NETx BMS Server server startup, the current status of all configured rooms is synchronized to the NETx BMS Server. Once the Infor plugin has been started, the Infor HMS notifies our system when one of the following actions occur:
- Room Check In
- Room Check Out
- Room Move
The NETx BMS Server keeps track of the room status within the item tree.
...
The driver is implemented as a plugin for the NETx BMS Server. Therefore, it has to be installed via the Extension Manager. To do so, stop the NETx BMS Server server and open the Extension Manager via the BMS Studio studio using the menu "Extensions". Select the "Infor" interface and press install as shown in the following screenshot:
...
After having installed the interface, restart the NETx BMS Studiostudio.
Integration steps
Determine local IP address to connect to the NETx Infor Endpoint
To determine the local IP address of the NETx Infor Endpoint, open a command prompt in Windows and enter "ipconfig".
To do so, press the Windows key and enter "cmd". Click the suggested Command Prompt app.
Once the command prompt has been opened, type "ipconfig" and hit enter.
...
| Parameter | Description | Example | Note |
|---|---|---|---|
| NETx Infor endpoint | The NETx BMS Server endpoint to listen for incoming requests from the Infor HMS | http://192.168.0.5/infor | Please see the "Determine local IP address" section below to see how you can determine the endpoint |
| Infor HMS endpoint | The Infor HMS endpoint to send outgoing requests from the NETx BMS Server. | http://192.168.0.6/netx | Please request this parameter from the Infor HMS operator and enter it accordingly |
| Infor HMS Hotel Code | The identifier of the controlled hotel | HMS01 | Please request this parameter from the Infor HMS operator and enter it accordingly |
| Request timeout | The request timeout in seconds | 60 | Optional |
Rooms
For the NETx BMS Server In order to know which rooms need be tracked, you have to provide some information regarding the room definitions.
You should be able to export this information from the Infor HMS and import it to the NETx BMS Studio studio so that you don't have to enter it manually.
Please talk to the Infor HMS operator to learn how to get the required room information.
...
Each definition line corresponds to one hotel room within the Infor HMS. The first column "ID" represents the unique room ID (for example 101), the second column "Path" represents the path that is used to define the structure within the item tree (usually grouped at floor level).
The remaining fields "Persistent", "Historical" (for NETx BMS server 2.0 only) and "Synchronize" have the same functionality as for all other interfaces within the NETx BMS Server.
The following figure shows an example of a set of configured rooms which should be tracked.
...
After having defined all rooms, the NETx BMS Server server has to be restarted. Afterwards, the configured rooms are shown within the item tree under the sub tree "NETx\XIO\Infor".
...
The retrieved information for each room from the Infor HMS is stored as a server item "RoomChecked" within the configured path.
Connecting to the NETx
...
Infor endpoint from an external network
Please keep in mind, that the NETx BMS Server Infor endpoint only listens to the specified IP address in the LOCAL network and is NOT publicly exposed to the internet.
If the Infor HMS is running in a seperate separate network, you will need to set up some kind of Port Forwardingof port forwarding in the network where the NETx BMS Server is running, so that the endpoint can be reached from other networks.
...
The Public NETx endpoint needs to be properly configured within the network where the NETx BMS Server is running.
The public endpoint will then redirect the traffic to the local IP address of the NETx BMS Server.
Sample configuration:
Article applies to the following products:
- NETx BMS Platform
- NETx Multi Protocol Server
- NETx BMS Server 2.0