For connecting the following Channel Managers, there are specific procedures that differ from the standard process:
Activation procedure:
Tour Operator contacts TravelClick to open the connection; normally, TravelClick will send the Tour Operator a connection questionnaire where the endpoint (URL provided by Netstorming) will also be requested
Tour Operator configures the contracts using the standard procedure, making sure to select "TRAVELCLICK API" in the "Channel Manager" field
Tour Operator opens a Redmine ticket with the credentials provided by TravelClick for bookings push (NOTE: the "company_name" in TravelClick must match the Tour Operator code in the Netstorming system, otherwise Netstorming development is required)
Tour Operator sends the mapping to TravelClick along with the credentials. TravelClick must combine them so that the Tour Operator's username matches the "actor.login" in Netstorming
Activation procedure:
Tour Operator must contact Phobs to open the connection
Tour Operator configures the contracts using the standard procedure; for a smoother connection, we recommend indicating the Phobs contract reference in the "contract name", using the same User and Password for all users under the contract
Tour Operator opens a Redmine ticket for each hotel that needs to receive updates from Phobs. The ticket must include the following details provided by Phobs:
◦ DestinationSystemCode
◦ Credentials provided by Phobs
◦ Phobs Hotel ID
◦ Netstroming Hotel ID
◦ Mapping information between Phobs contracts and Netstorming contracts (this is why we suggest including Phobs contract names in the Netstorming contract names)
Our technical team will use these details to download and update the contract mapping (on the Netstorming side)
Phobs sends the test updates
This process must be repeated for each hotel the Tour Operator wishes to connect
Activation procedure:
Tour Operator contacts Siteminder to open the connection. Siteminder may require certification. (Normally, Netstorming’s technical team interfaces directly with the channel manager to proceed to the pilot phase)
Tour Operator configures the contracts using the standard procedure with the following specifications:
◦ all contracts must share the same user credentials to be provided to the channel manager; Login and Password must be the same as those provided to Siteminder (the Actor can differ between providers)
◦ all contracts must have the correct channel manager configured: the channel manager set on each individual contract must be SITEMINDER EUROPE or SITEMINDER ASIA/AUSTRALIA, depending on the hotel’s location
◦ Tour Operator must open a Redmine ticket with push credentials that Siteminder should provide to you. At this point, our technical team will activate the connection ◦ Tour Operator will now be able to share the mapping with Siteminder and coordinate with cannel manager and the hotel for the "pilot phase"
◦ This activation needs to be done only once per Tour Operator, then they will be autonomous for the next hotels
Activation procedure:
Tour Operator will contact D-EDGE to open the connection
Tour Operator configures the contracts using the standard procedure, with these precautions:
◦ all contracts must have the same User credentials to share with the Channel Manager, Login and Password need to be the same to give to D-EDGE (the Actor can be different between the different suppliers)
◦ all contracts need to have the correct Channel Manager configured: D-EDGE API (NO D-EDGE)
Tour Operator will ask D-EDGE to compile the information needed to duplicate the Netstorming connector
Tour Operator opens a ticket to ask for the endpoint to be shared with D-EDGE
D-EDGE proceeds with the duplication of the connector. Once the connector has been deployed, D-EDGE shares the push booking information. The Tour Operator will include the credentials in the Redmine ticket (Login and Password)
D-EDGE can proceed to connect and test with the Tour Operator 3 pilot hotels live on their side. D-EDGE proceeds to map the 3 pilot hotels. The partner has to make test reservations in each pilot hotel
If everything works well, the project will be released