An open source project by

| 

  • More products

    Products

    i4FSMarketplace

    +

    i4Apps

    A marketplace for factory Apps. Designed to connect industry and developers.

    For Industry

    i4Support

    A support team of 4.0 industry professionals.

    i4Integration
    4.0 industry project integrators.
    i4Customisations

    A dedicated team of customisers for your own project.

    For Developers

    i4Platform

    A containerised environment to manage 4.0 industry apps.

    i4Assets

    Components that make part of 4.0 industry apps.

    i4Tools
    A set of developer tools to build 4.0 industry apps.
Components
Sign up
Sign up
Home
>
>
>
>
Messaging

Messaging

The Messaging component is part of the Data Infrastructure Middleware and the main functionality is to send messages for all i4FS components of the platform, through their unique identification.

All messages use the AMQP (Advanced Message Queuing Protocol) protocol. This protocol is an Open Standard for Messaging Middleware that provides reliable solutions for systems-interconnection based on messages exchange, using a combination of point-to-point messages and supports TLS/SSL encrypted and authenticated channels.

The Messaging component uses a message broker (RabbitMQ) to handle the communication between producers and recipients, reducing loads and delivery times for web applications by delegating to the message broker those tasks. The broker also uses the Security component to verify the authentication and authorisation of the asset that is using the messaging service.

The Messaging component is part of the Data Infrastructure Middleware and the main functionality is to send messages for all i4FS components of the platform, through their unique identification. All messages use the AMQP (Advanced Message Queuing Protocol) protocol. This protocol is an Open Standard for Messaging Middleware that provides reliable solutions for systems-interconnection based on messages exchange, using a combination of point-to-point messages and supports TLS/SSL encrypted and authenticated channels. The Messaging component uses a message broker (RabbitMQ) to handle the communication between producers and recipients, reducing loads and delivery times for web applications by delegating to the message broker those tasks. The broker also uses the Security component to verify the authentication and authorisation of the asset that is using the messaging service. To facilitate the usage of this component, there are available libraries in JavaScript and Java languages that allow the components to asynchronously send and receive messages. If the recipient is offline, the message will be stored in the broker until it is back online again, serving the message then.

Play Video

Send Message

Sends a private message to a component.

Receive Message

Receives a private message.

Message Content

The received messages will contain the following elements to be used for improving the message analysis: message content, timestamp, length, sender identification and routing key

Blob Data

The user can send binary data, such as files or images, embedded on the message content to ease the message receiver.

Additional ressources

Learn more about i4FS by visting the project website for general information, the wiki for information about the core components, the Technical Manual for API documentation, and downloading the repository’s source code.

Wiki

Get a better understanding of the global architecture and information flow.
Learn more

Source code

Our source code is opensource and available on our Gitlab repository.
Learn more

API endpoints

Let your infrastructure communicate with the i4 Platform.
Learn more