What Is Required For Events Portal?

This outlines What Is Required by Venues when considering implementing Events Portal.

The content is targeted at Resellers and swiftpos Venue Administrators who have a sound knowledge of and experience with swiftpos. For further information or assistance, please contact your swiftpos Reseller or swiftpos Support.

Web Server ▲ ▼

A Web server (for example, IIS) must exist and have the swiftpos API installed. For more information refer to the Reseller Help - Web Server (IIS) Installation.

Email ▲ ▼

Access to the Customer's email inbox that was used when registering SwiftPOS. This is required in order to retrieve the one-time code which is sent to the same email address when Cloud Onboarding. A copy of the same email is also sent to the Venue's SwiftPOS Reseller.)

swiftpos ▲ ▼

Version - swiftpos v10.49+

Server - Access to the swiftpos server, with ability to run Back Office as the swiftpos Administrator. The swiftpos server will need to be able to connect outbound to the following endpoints:
- mslmqprod.mslsolutions.com (TCP 443)
- venuemanager.micropower.com.au (TCP 443)
- manager.swiftpos.com.au (TCP 443)
- onboarding.micropower.com.au (TCP 443)

Back Office
- Clerk Security - The appropriate permissions are granted to the Clerk Security Group configured here:
  - Administration
    - Services (only found on the swiftpos server where services are installed)
    - OrderAway
  - Touch Settings
    - Keyboards
  - Products
    - Product Records
  - Members
    - Member Classifications
    - Member Records
  - Clerks
    - Clerk Groups
    - Clerk Security Groups
    - Clerks
  - Web
    - Web Api
- Guest/Non-Member Orders - Refer to Support Guest /Non-Member Orders for more information.
- Services - The following swiftpos Services need to be installed and running:
  - Connect
  - Gateway Client – This new service needs to be installed and will only start when an OrderAway Location is Activated. Once activated, the Gateway Client Service will be manually started. It facilitates the communication from the Venue’s swiftpos server to the swiftpos Cloud Server. This will be an outbound secure AMQP internet connection to the Cloud.
  - NetPOS
  - Orders Processing
  - Service Monitor
- Cloud Connectivity
  - SwiftAPI URL - Ensure the the SwiftAPI URL is set to the Venue's Web Server.
  - Locations - Venues will need to add each Location that is going to be making use of Events Portal.
  - Activating A Location - Each Location that is going to be making use of Events Portal will need to be Activated.

Notes...

It is recommended that the Submit orders directly to POS Terminal option is selected and a designated Orders Terminal is configured when activating a Location for Events Portal.

Touch
- Orders - Ensure that for each Location, listed in the OrderAway Locations, a single swiftpos Touch Terminal is designated as the Orders Master Terminal and has the Orders > Enabled option selected.
  - The swiftpos Master Order Terminal will need outbound connectivity to:
    - mslmqprod.mslsolutions.com (TCP 443)
  - Also, consideration may need to be given to the Finalise Remote/Web Order options available within the Table Tracking > Orders tab. Specifically the With no balance and Not Delayed option.
    - If SELECTED, Orders submitted via the Events Portal device will be sent straight through to the swiftpos Back Office.
    - If NOT SELECTED, Orders submitted by the Events Portal device will be sent to the Orders Master Terminal, where they can be processed further as required via the Orders Pending button.

Microsoft.Net Framework ▲ ▼

Ensure version 4.7.2 or higher is installed on the swiftpos server. Download

End of article. ▲