Dualog Fetch - Data Receiver Configuration

INTRODUCTION

This article provides information on how to configure Dualog Fetch via data receiver configurations.

2.1 - CREATE DATA RECEIVER CONFIGURATION

1. Under the Main page on Dualog Portal, click on Sub-menu (located on the top-left corner) > Fetch > Configuration tab > Under Date receiver configurations, create configuration.
2. Choose "All Ships" or "Specific Ships" (This can be edited at any point in time via the main configuration page)

AUTHENTICATION

Dualog Fetch supports two authentication methods:

• ID + certificate
• Username + password

The authentication method has to be selected during configuration.

Please note that you cannot edit the authentication type once the configuration has been created.

If Certificate is selected, ID will be auto-generated and you may choose to download the certificate now or at any later time.

If Username & password is selected, values will be auto-generated for both username and password.

• You may copy the values to the clipboard and save it for future
• Click on Continue to return back to the main configuration page.

• You can change the password at any point in time, which would generate a new password after.

2.2 - ASSIGNING INSTALLATION TO CONFIGURATION

You can choose to assign all vessels or specific vessels to a data receiver configuration by clicking on edit.

2.2 - DATA RECEIVER REQUIREMENTS

Dualog Fetch listens on the standard Syslog data port: 514. To make Dualog fetch receive syslog data from clients, there are two requirements:

• The devices must be configured to send this data. This is very device dependent. Please check the documentation of the device.
• An UDP/IP connection must be open between the device(s) and the computer running Dualog Fetch. This means that firewalls must allow this connection (from device to the Fetch computer) – on port 514.

An unlimited number of outbound message queues can be configured, depending on how and who to receive the SysLog messages. The Advanced Message Queuing Protocol (AMQP) is supported.

The receiving software must support AMQP and be configured to use one of the two authentication methods supported (ID/certificate or username/password).

Currently, the only outbound queue filtering is on ships to receive log data from.

WHAT IS AMQP?

AMQP is a messaging protocol on the application layer. It is designed to support a wide variety of messaging applications and communication patterns. Our implementation uses TLS for authentication and encryption.

2.3 CONFIGURE YOUR DATA RECEIVERS

The service reading from the message queue must support reading messages from the AMQP message queue.

End-point URL: fetch.dualog.com:11765

We are supplying two types of message queues:

• Raw data
  • Raw data delivers the syslog lines as created by the sending device. Message queue name: syslog
• JSON
  • Json contains ship name and the raw SysLog message Message queue name: syslog-json

JSON format:

{"Name":"ship name","LogMessage":"message"}

Name: ship name

LogMessage: the syslog message in raw format

For identification and authorisation, use the credentials created when configuring the data receiver on Dualog Portal.