The Navitas Hub has been developed as a direct replacement for the Amadeus SmartScripting Bridge which is being decommissioned by Amadeus on April 30th 2025.
The Navitas Hub is based on Microsoft SignalR technology, which has been employed to facilitate communication between Amadeus Selling Platform Connect and all applications and solutions provided by Navitas Solutions.
In developing the Navitas Hub, it has been designed to be extremely streamlined and simple, with only a few 'components' required - the below diagram outlines the system,
The key information for each component:
Amadeus Selling Platform Connect
This is the normal Amadeus environment used by agencies to book Travel for their clients and is run from within the users chosen browser.
Navitas Hub Connector SmartTool
The SmartTool is an add on, configured by Amadeus within your Office ID, and is set to start up each time a user signs into Amadeus Selling Platform Connect. The Navitas Hub Connector will look for the existence of the Navitas Hub being available by attempting to connect to the Navitas Hub 3 times using the JavaScript SignalR client library. There is no local installation required for the Navitas Hub Connector SmartTool, its all done by Amadeus and hosted online by Navitas Solutions.
Certificates
Navitas Solutions Ltd is added as a registered Trusted Root Certificate on each Windows Machine during the installation. This certificate is used to enable communications between the Navitas Hub Connector SmartTool and the Navitas Hub running locally. If the certificates have not been installed correctly, then communication is blocked by the browser. The Certificates are installed to the 'c:\navitas\sslcertificates' folder on each local machine.
Navitas Hub
This is a small Microsoft SignalR Hub written using .NET 8 and ASP.Net Core components. The Navitas Hub is responsible for passing messages (signals) from/to the Navitas Hub Connector SmartTool, for example when requesting the current PNR open in Amadeus Selling Platform Connect. The Navitas Hub is configured to be a Window Startup application during the installation to ensure it is always running and available when the user logs into the computer. The Navitas Hub should be started and up and running before the user logs into Amadeus each day, otherwise the connection may have failed. The connection can be reset using the NAVITAS:RESETHUB command in Amadeus.
The Navitas Hub itself is deployed as either a Microsoft ClickOnce application for standalone machines, or as a Windows Service when using a Terminal Services/Citrix Environment.
The main files are installed to the 'c:\navitas\navitas hub' folder, with the clickonce version also deploying to each users c:\users\{username}\AppData\Local\Apps\2.0 folder infrastructure.
Navitas Applications
Our normal suite of applications and bespoke solutions have been updated to use the Microsoft SignalR .net client to connect to the local instance of the Navitas Hub. This connection is then used to pass messages (signals) through the entire communications pipeline to interact with the Amadeus Selling Platform Connect website.
Comments
0 comments
Please sign in to leave a comment.