Yet another Integration platform supported! Now supports Mule ESB

We are proud to announce that Integration Manager now supports Mule ESB. With future releases it will be possible to monitor applications and endpoints in Mule. It will also be possible to track messages and context within Mule applications.

Monitor Mule applications and endpoints

The next two pictures show an example of a monitor view of Mule. In the first one everything is working as expected but in the second one an application is indicating an error. In this case the application has been stopped.

Integration-Manager-Monitoring-Mule

Integration-Manager-Monitoring-Mule-Application-Stopped

Start and Stop actions

If the monitor view is configured to allow actions it will be possible to start and stop the monitored Mule applications and endpoints. Just click on the action button and select start or stop.

Integration-Manager-Monitoring-Mule-Actions

Tracked message events in Mule

Integration Manager receives the tracked messages (body and context) by using the Log component in Mule.

Integration-Manager-Mule-Logger

It is also possible to use the Mule Custom Business Events to retrieve the necessary information. Custom Business Events are only available in the Enterprise Edition.

 

After the messages has been processed by Integration Manager the will be shown in the web client.

Integration-Manager-Tracked-Messages-Events-Mule

 

The context of the received message.

Integration-Manager-Tracked-Messages-Events-Mule-Context

 

More from Integration Software:

Videos on  YouTube
Information on  Twitter
Contact on  LinkedIn

Online documentation: Latest version
Latest release notes: Release Notes
Support site: Support Site

 

Monitor Microsoft Azure services with Integration Manager

The number of monitor agents is getting bigger and bigger enabling you to monitor even more systems, services, platforms and applications. Not only are we working on supporting even more integration platforms, such as Mule or iCore, … we also work on integrating more with the Microsoft Azure platform, enabling you to monitor your cloud-based & hybrid integrations with ease – centralizing message logging and monitoring into your Integration Manager platform and having it all in one place.

We are currently supporting the following Microsoft Azure services:

  1. Cloud Services
  2. App Services (Logic & API Apps)
  3. Web Jobs
  4. Service Bus

Integration Manager fully supports Microsoft Azure Logic Apps

Guru Venkataraman and Mark Mortimore from Microsoft held a presentation about the critical mission to use cloud capabilities on Microsoft Azure for building system integrations during the Microsoft Ignite event in Chicago. We have been chosen to be one of the partners for showing the audience the capabilities Microsoft offers its partners and customers in the new service – App Services. In one of their demos they decided to show how you can extend your Logic Apps with monitoring and logging capabilities by using one of our products – Integration Manager. See the whole recorded session by clicking here.

We are proud to announce that Integration Manager now fully supports logging all events/messages and monitoring Microsoft Azure Logic Apps.

These new capabilities enables you to simply log all messages as well as to monitor all Logic Apps in your Microsoft Azure subscription. Simply install our all new log and monitor agent for Microsoft Azure Logic Apps, let it connect to Microsoft Azure and fetch all messages and monitor all parts of your Logic Apps.

Logging

Integration Manager’s Log and Monitor Agent for Microsoft Azure Logic Apps will log not only that an operation has been executed, it will also log the input and output data of all actions being executed within the different Logic Apps. All events being logged contain a correlation id as a contextual value which easily can be used as a Search Field to group the different events, enabling you to see the whole chain of events and get it all in one place.

Monitoring

The new agent for logging and monitoring for Microsoft Azure Logic Apps automatically keeps track of all Logic Apps published in your Azure subscription. Not only are the statuses of your Logic Apps being monitored, even the different connectors are being monitored – giving you the insight and control you need in order for you to know that everything is in place and running according for your business to work.


Want to see a demo and want to learn more? Please contact us at info@integrationsoftware.se and we will set up an online meeting and show you how easy you can get in control and retrieve the insight you need!

Azure App Services Series – Finding #4: Hybrid Connections – Could not load file or assembly Newtonsoft.Json

This blog post is one of many of a series we have about Microsoft Azure App Services. See a list of all our findings here.

Introduction

Azure BizTalk Services – Hybrid Connections allow you to access on-premise resources, such as SQL instances, files, etc from Azure app services – web, API, mobile and logic apps.

By enabling your app services to use on-premise resources you can together with Integration Manager monitor even more!

Microsoft created and released e.g. a protocol connector enabling you to access on-premise files – the File connector. This connector uses Hybrid Connections to access files located on your on-premise file system.

The Problem

If you follow tutorials / documentations on how to get started with Hybrid Connections you learn that you have to have a BizTalk Services instance in Azure, this instance can have one or several hybrid connections (see pricing of BizTalk Services to learn more about limitations). While setting up and configuring your hybrid connection, it requires you to install a service/agent on your on-premise machine called the Hybrid Connection Manager. Installing the agent sometimes works and sometimes not.

We came across a file not found error during installation. Newtonsoft.Json file could not be found and therefore the installer throws an exception stating “Could not load file or assembly Newtonsoft.json…”.

Unfortunately there is no post from Microsoft about it, there are some forum posts regarding this error message, but we could not find a proper blog post about how to resolve the problem.

The Solution

We solved the issue by installing the proper version of the Newtonsoft.Json.dll into the Global Assembly Cache (GAC). The error message of the installer tells you which version you need, which in our case was version 4.5.x.x. We downloaded the dll with version 4.5.11 from the Newtonsoft.json Github project downloads and installed it into the GAC. Installing the DLL into the GAC can be done by using the Developer Command Prompt for Visual Studio and executing the gacutil.exe with the proper parameters.

The command prompt will show a message that the assembly has successfully been added to the GAC (see screenshot 1).

Screenshot 1 - Gacutil added assembly

Screenshot 1 – Gacutil added assembly

When you are done, restart the installer of the Hybrid Connection Manager and you should be good to go (if there is not another bug hidden somewhere along the installation!).

 

We hope this helps you solving issues during the installation of the Hybrid Connection Manager!

Azure App Services Series – Finding #2: Logic App Workflow API documentation is incomplete

This blog post is one of many of a series we have about Microsoft Azure App Services. See a list of all our findings here.

Introduction

With the release of Logic Apps, Microsoft also releases the Workflow Management API. An API to use for getting access to the workflow of your logic apps allowing you to easily enable, disable workflows, get the status, etc.

Microsoft’s documentation of the API is incomplete and not clear which of the API calls are working in the current release of the API.

This API is allowing you to monitor Logic Apps with Integration Manager’s monitoring feature!

The Problem

Problem #1: Incomplete documentation

According to the documentation the URI to the calls is:

https:///subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logic/workflows/{workflowName}?api-version=2015-02-01-preview

This is wrong of course, you can clearly see that something is missing in the beginning of the URI.

It’s the URI to the region of the Logic App. For example: northeurope.logic.azure.com. The URI to call the API should look like this (example below):

https://northeurope.logic.azure.com/subscriptions/72bad97c-b0ce-40a3-a300-d36e50de34fe/resourceGroups/Default-Web-NorthEurope/providers/Microsoft.Logic/workflows/FTP2BTnoIM?api-version=2015-02-01-preview
Problem #2: Not all of the API calls documented are working (yet)

We did not manage to get many of the API calls to work. In fact, we only did manage to get one call to work – triggering the action by calling the /run method of the API. Most of the others (we did not test all) return 404 not found when calling the API.

Problem #3: There is no documentation about authenticating against the API

The documentation says nothing about how the authentication looks like, which makes the documentation somewhat useless!

For your interest, the authentication type supported is Basic. A username is created on logic app create which is ‘default‘ and the password to use is the primary key (not sure if the secondary works as well) which you can find in the logic apps properties blade of the Azure portal (see screenshot 1).

Screenshot 1 - Primary Access Key

Screenshot 1 – Primary Access Key

So the proper way of authenticating against the API is to send the Authorization header with your Basic username/password value – see example below:

Authorization: Basic YOURENCRYPTED(default:primaryAccessKey)

Monitor Web Services and SQL Server with Integration Manager

We are proud to announce the release of two new monitor agents for Integration Manager giving you even more control and insights – Microsoft SQL Server and Web Services.

SQL Server Agent

Integration Manager’s agent for Microsoft SQL Server allows you to monitor:

  • SQL statements
  • SQL jobs
  • Backups
  • Size checks (data and log separately).

It is crucial to know when backups are not taken, jobs are not running and statements are not returning the expected result, due to the fact that this might cause business critical errors.

With this agent you can configure Integration Manager to monitor all imaginable SQL statements and their result.

Monitor SQL jobs on all configured SQL server instances.

Control that backups have been taken from all monitored databases. Displays the time and state of the last backup (if any).

Check the size of the files for data and log, supports warning and error threshold values.

  • Any number of SQL Instances can be monitored from a single agent
  • Multiple agents can be deployed

Web Services Agent

Many systems and integrations are depending on web services, monitoring them is important! With Integration Manager’s agent for web services you can easily monitor web API’s, SOAP services and even web sites.

You monitor them by simply providing all required HTTP headers, client certificates as well as the services’ address and let the agent do its job – connecting to the service, check if the response’s HTTP status is one of the expected ones and evaluate the result of the request by using a regular expression or an XPath.

Not only can you check if the HTTP status is one of the expected ones, and not only evaluate the result by using a regular expression or an XPath, you can even monitor the response time of the request.

  • Any http endpoint can be monitored
  • Any number of web endpoints can be monitored from a single agent
  • Multiple agents can be deployed

Technical Features

  • SOAP
  • Web Api
  • Web Applications
  • Body from file
  • All HTTP operations are supported
  • All HTTP Headers are supported
  • Validate Response body using RegEx or XPath
  • Validate HTTP response status code
  • Authentication support
    • Client Cert
    • Impersonation
    • Basic auth
    • Api Key
Twitter
YouTube
LinkedIn