Custom Channel Manager

For connecting the following Channel Managers, there are specific procedures that differ from the standard process:

Travelclick (Amadeus)

• 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

  • Tour Operator must coordinate with the hotel to manage testing in the live environment

Phobs

• 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

  • The 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)

  • Netstorming’s technical team will create the mapping
  • Tour Operator sends the mapping to Phobs in a PDF file provided by our technical team

  • Phobs sends the test updates

    This process must be repeated for each hotel the Tour Operator wishes to connect

Siteminder

• Activation procedure:

  • The 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 the credentials for data push that Siteminder will provide. At this point, our technical team will coordinate with Siteminder for the pilot phase