eMagiz Mendix Connector

Content Type: Service
Categories: Import/Export,Data,Communication

Overview

The eMagiz Mendix Connector is a Mendix module that is developed and maintained by eMagiz that simplifies the connection between a Mendix application and an eMagiz integration model for data traffic in an application landscape. The objective of the module is to simplify the connection between Mendix and eMagiz and therefore enhance the speed of development and reduce the risks of problems. The Mendix module is developed and maintained by eMagiz. The eMagiz Mendix Connector makes use of Java Actions.

Documentation

Description

This module will allow to make quick and easy connection from a Mendix application to the eMagiz integration model and vice versa. The modules holds all the Mendix component to write message to and read message from the AMQP queues in eMagiz.

Typical usage scenario

This modules is most often used to handle scenario’s where the Mendix application needs to interact with various data sources that are exposed via the eMagiz iPaaS platform.

Features and limitations

Features:

  • Java actions that interact with AMQP queues
  • Admin screens to download the latest release content from eMagiz to Mendix and manage these exit and entry queues

Limitations

  • No support yet for multi-instance Mendix setups

Dependencies

  • There are no dependencies

Installation

Please refer to the microlearnings available at: https://docs.emagiz.com/bin/view/Main/eMagiz%20Academy/Microlearnings/Novice/Mendix%20Connectivity/ 

Configuration

Apply this user guide if you are using the eMagiz Mendix connector to add a new exit integration to a Mendix app. This provides a short summary. Please refer to the microlearnings for this module at: https://docs.emagiz.com/bin/view/Main/eMagiz%20Academy/Microlearnings/Novice/Mendix%20Connectivity/ for a complete explanation

Step 1. eMagiz capture and design phase

  1. Create integrations
  2. Create message definitions (xsd)
  3. Give message definitions to the Mendix developer

Step 2. Mendix model phase

  1. Import message definitions
  2. Create import mapping and/or import microflow
  3. Create export mapping (sync only)
  4. Download the eMagiz connector from the App store
  5. Add the XML Configuration_Overview snippet to the app
  6. Configure the constants
  7. Give mapping and microflow names to eMagiz developer.

Step 3. eMagiz create and deploy phase

  1. Update create phase with Mendix configuration
  2. Create release with updated Mendix packages
  3. Activate release

Step 4. Mendix runtime phase

  1. Run the Mendix project
  2. Click the download button on the page with the snippet.
  3. Configure which flow should be auto started
  4. Start the flows that should be started

Bugs

None reported so far. Please contact productmanagement@emagiz.com or use the feedback button in the eMagiz iPaaS Portal.

Releases

Version: 6.0.2
Framework Version: 8.18.2
Release Notes: The 6.0.2 release of the eMagiz Mendix connector (EMC) has one small bug fix on the metrics distribution. Bug fixes We have fixed an incorrect number of metrics collected by the connector
Version: 6.0.1
Framework Version: 8.18.2
Release Notes: The 6.0.1 release of the eMagiz Mendix connector (EMC) has one small bug fix on the reported CPU metric. Bug fixes We have fixed how we report the CPU metrics to the user.
Version: 6.0.0
Framework Version: 8.12.7
Release Notes: Version emc 6.0.0, released 2022-11-09. These are the release notes - please note that this version is compatible with Mendix 8 and 9 (whereby the version indicated is the minimal version required). - Next Generation runtime compatible. This version will work for both the current and the new runtime architecture of eMagiz - Stopping and starting exit configurations or (de)registering listeners triggers eMagiz model log entries in this release - Most of the userlib libraries were updated to include the latest security fixes - The Joda-Time userlib library is no longer used and will be deleted by the clean-up tool - We addded ‘RequiredLib’ files for all required userlib libraries.