Com Channels are the interface between N-OC and the outside world.
- You must create a Com Channel for each type of action.
- A Com Channel must be linked to an Event. Refer to: Automation Factory
- When the event is triggered, Sleipner will perform the actions specified in the COM Channel.
- The Com Channels should be configured by help of your IT Department and / or NAVBLUE Customer Support.
Example
Field | Description |
Name | Name is mandatory. |
In/Out | Select if Sleipner should send out or read incoming messages. This field is mandatory. |
Host | Specify host location. It can be a physical location or e.g. an Email host. Note: For SITA/AIRINC messages, the host must point to the location where Sleipner is running. |
Port | Port number e.g. for email |
Sender | A sender is optional. |
Folder | A folder is optional. |
Apart from "Active" and "Default", you will see different options depending on which communication type you select.
Other options:
- SSL: Secure Sockets layer (secure communication).
- Use 0Auth 2.0: Connects to local directory and provides security.
Note: User must always be Sleipner.
Optional: User Name and Password.
Communication Type
The communication type can be one of the below and is used when making Events.
File Type
Here you find a long list of file types. Select one that matches the Communication type.
Note: SITA is the old TypeB format, SITATEX is the "new" format.
Type B
- QU KIMOPOP
- .CPHOPOP
- MVT
- VH8113/23.HK4818.ADZ
- AD1650/1651 EA1859 BOG
- DL12/0011
SITATEX
- =PRIORITY
- QU
- =DESTINATION TYPE B
- STX,KIMOPOP
- =ORIGIN
- CPHOPOP
- =SMI
- MVT
- =TEXT
- MVT
- VH8113/23.HK4818.ADZ
- AD1650/1651 EA1859 BOG
- DL12/0011
Adapters
- Multi MVT
- LDM Cargo: this option will try to correct a LDM message into correct IATA format.
