Host System Types

Overview

In the Chain.io portal we provide customers the ability to connect to multiple host systems. Some of these Host Systems can be used to send data to the Chain.io system and some of these Host Systems can be used to receive data. The flow types of send and receive are used many times and so it is important to understand the concept which can be found under the Send Flow Type and Receive Flow Type section found here.

Below is a list of Host System types available in the Chain.io portal

• API Client
  • Initiate a send flow by sending a request to a Chain.io hosted API endpoint. At this moment, there are no configuration options except for naming the API client. When creating a flow and using this option as a source system, you will be prompted to further define the API endpoint and API key. This Host system type will not be used as a destination system when configuring a flow.
• API Server
  • Configure an API endpoint to where you want data to be sent to your host system. This allows you to define an HTTPs endpoint and authentication method that will be used when your host system is receiving data. This host system type will be used as a destination system when configuring  a receive flow. This option is not used in a send flow.
• CargoWise Rest
  • Configure the CargoWise eAdaptor settings in order to use their RESTful web service interface. For more information on how to set this up please see the following article. This host system type will be the Source System in a send flow type and a Destination System in a receive flow type. For more details about CargoWise eAdaptor and their REST API vs SOAP please see the eAdaptor Developers Guide published by Cargowise in their account portal.
• CargoWise SOAP
  • This configuration option is primarily only used to route data to Chain.io AND to another company such as another middleware. To learn more about why you may need to set up this option, please review the following article.
• CargoWise Send Only
  • For our SEDNA users only
• Custom
  • If your application requires very unique and custom configurations that are not found in any of our other standard host types, then the Chain.io support team can help accommodate with a custom configuration to meet your needs.
• Send Email
  • This is the Destination System in select receive flow types. At this moment, there are no configuration options except for naming of this email host type. This name will show up as an option as a destination system in select receive flow types. From there, you will be able to define email recipient(s) along with a subject and body.
• Receive Email
  • Definition for if we were to implement: This allows you to define a Chain.io hosted email address to receive attachments. When configured as a Source System for a send flow type, any valid attachments to this email address will initiate the flow process.
• Magaya
  • This configuration is used to connect to your Magaya system so that data can be sent to the Magaya TMS. When configuring a flow, this host system will show up as a destination system for select receive flow types.
• file.chain.io(SFTP)
  • This is a legacy host system that has been replaced by the functionality of our SFTP Launcher. For more information please refer to our support article on SFTP Launcher
• Rollmaster

  • This configuration is used to connect to your Rollmaster system and send data out of it. When configuring a flow, this host system will show up as a source system for select send flow types.

• Remote SFTP Server
  • Configure an SFTP endpoint that flows can retrieve data or send data to. In the host system configuration, you can define the url and username and password details along with a few other protocols. Later on when you configure a flow that will leverage this host system, you will be able to define the directory and a few other configuration options that are applicable to that integration.
• Webhook.site
  • Configure this to connect to a webhook.site. The site UUID is the only configuration needed.
• S3
  • Configure Amazon Web Service(AWS) S3 buckets as a host system so that it can be used as the receiving system in a workflow.