Integration Landscape: Graphical views improves usability and information sharing

We are proud to present Integration Landscape, a new powerful feature that displays the Repository model as a graphical model.

 

This feature is available in the 4.3 release series.

This feature has been implemented using the open source library jsPlumb. Read more about jsPlumb here

Log tracked messages with ease from multiple BizTalk instances

 Integration Manager 4.2.0.9 has now support for harvesting logged tracking data from multiple BizTalk instances from one instance of Integration Manager. Since all your production environments are covered within our simple fixed price licensing model there is no additional licenses costs associated with adding more BizTalk Servers. This is not the case with competing tools where you have a plethora of licensing options and costs.

This is especially useful when introducing new version of BizTalk Server, since you may have multiple production environments up and running in parallel using only a single instance of Integration Manager. Data is separated by the use of unique id’s, read more here.

General Release Notes: http://support.integrationsoftware.se/support/discussions/forums/1000227207

 

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

 

Supervise the size of your SQL Databases in Azure

Make sure your SQL databases in the cloud stay performant and within the sizing thresholds your business requires. By monitoring the size, you gain awareness and can take actions to keep only the required amounts of data. This will save you money.

With the SQL monitor agent in Integration Manager it is easy to keep track of your SQL Databases in Azure. Today the there are two categories available for monitoring the SQL Databases.

  • Size check
  • Custom statements

This blog post describes how to monitor size checks using Integration Manager.

SQL Monitor Agent

With Integration Manager comes an agent for monitoring SQL Server instances and databases on premise and SQL Databases in the cloud. To read more about the agent and see all supported monitoring capabilities, please visit the Documentation site.

The Agent can be installed in multiple instances on premise or in the cloud/partner location on a virtual machine.

SQL Monitor Agent

 

Global Configuration

Using Remote Configuration the agent can be configured to monitor one or more databases

Size Check Category

Configure

Configure the thresholds for the size check category to get warnings and errors if the limits are reached. An error will also be raised if the resource is unavailable (network error, someone accidently removes the database, changes permissions and so on).

There are two options available for the size check evalution

  1. Percentage
  2. Size in Megabytes

Remote Configuration SQL Server

Read more about configuration in the Integration Manager Documentation, Azure – SQL Size Checks.

Monitor

When the configuration is done it is easy to add the resource to one or more Monitor Views. Within the monitor view you can configure whether an alert should be raised or not when an error or warning occurs. More about Monitor Views in Integration Manager can be found here.

Azure SQL Monitor

This screen shot shows a list of my Monitor Views.

The Azure SQL Monitor view, which supervise the size of the databases are currently OK in the example above. The other view, ‘Azure LogicApps Monitor’ indicates a problem with my Logic Apps (more about monitoring Logic Apps in a future blog post).

Detailed configuration

A specific resource can easily be reconfigured and information about limits are also showed. In the example below one can see that there was indeed a size limit on just 100 MB and percentage was the better monitoring configuration for this specific database.

Azure Database Size Check Configuration

Summary

With Integration Manager it is easy to monitor all your assets independent of where and what they are. This was a short blog post about how to monitor your Azure SQL Databases without logging in to the Azure portal and manually keep track of the size.  A database cannot grow beyond limits and your business critical applications will fail if there’s not enough free space to deal with your transaction needs. Stay proactive using Integration Manager

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 4.0 webinar available on YouTube

The webinar held on September 22nd, 2015 is now available on YouTube – click here.

We were showing some of the new features available in the new version of Integration Manager – version 4.0.

List of features seen in the video:

  • Actions
  • Expected State
  • Dynamic Data Custom Field plugin
  • User Interface
  • Search Field Expression tester
  • Source remote configuration
  • etc

[Webinar] Join the webinar and see Integration Manager 4.0 in action

On September 22nd (Duration: 1-hour) we will be showing the new features of Integration Manager in action.

It has been a busy year for us. We have been working hard on stabilizing and improving Integration Manager – and the result is amazing. Working with your integrations is becoming easier and easier, the insights and control given is helping not only you in your IT department, but also your business!

Our main focus on this version has been the monitoring engine of Integration Manager making it a lot easier to configure and to administrate the different resources / systems / applications you are monitoring. But not only the monitoring engine has been improved, a lot has happened and we would like you to join us at our webinar to see the improvements we did!

Feel free to join the webinar and learn more about the new version of Integration Manager, version 4.0.

Register here or contact us at info@integrationsoftware to book an online demo.

Integration Manager 4.0 – Webinar

Date: September 22, 2015 – 1:00 PM CET (Duration: 1 hour)

We are happy to announce the release of Integration Manager’s upcoming version – version 4.0.

We would like to invite you to our webinar giving you the opportunity to see all the new features / functions and changes. 

Feature Agenda:

New Changes
  • Actions / Control Center
  • Expected State
  • Custom Fields / Dynamic Data
  • End-To-End Monitoring Capabilities
  • UI Changes

Click here to see a full list of news and changes.

Want to know more? Contact us at info@integrationsoftware.se to book a private in depth meeting.

Azure App Services Series – Finding #7: Startpage widget for Logic Apps in preview portal not showing status

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

The new Azure portal is great when it comes to flexibility and customization support for the user interface or at least when it comes to the start page. You can add shortcuts to virtual machines, websites, etc. to your dashboard, as well as billing information, etc.  And this makes it interesting from a monitoring point of view, since you can add a shortcut to your virtual machine and the dashboard will then provide you with a shortcut link, as well as shows information about the state. This means that if the virtual machine is stopped – the dashboard/home page will tell you as shown below in Screenshot 1.

Screenshot 1 - Virtual Machine widget showing status.

Screenshot 1 – Virtual Machine widget showing status.

The Problem

I wanted to add my Logic Apps to my dashboard to simply provide myself with useful shortcuts as well as I thought that the widget on the dashboard would then show me the state of the application itself – but no (see Screenshot 2 below). Unfortunately the new widgets provided for the logic apps do not show the state yet.

Screenshot 2 - Status of logic app not showing on home.

Screenshot 2 – Status of logic app not showing on home.

Integration Manager – a tool for centralizing logging and monitoring of data and systems in your system integration provides you that shows all logic apps, not only the one in your Azure directory- but all directories you configure it to log from and to monitor.

The Solution (in my/our opinion)

Show the state of the logic apps (running/stopped), as well as the state of all API apps used in the logic apps, since they are important as well for the integrations you’ve build to work.

Azure App Services Series – Finding #6: No possibility to comment triggers and actions in Logic Apps

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

Working with Logic Apps is fun, but in the current version of it is kind of hard to keep track what all the different actions do. Let’s say you use the BizTalk XPath Extractor several times, because you need to extract several values from an XML file content. But take a look at Screenshot 1 below and see what it looks like.

xpath-extractor

Screenshot 1 – Several XPath Extractors

With the announcement that Integration Manager now fully supports logging in Logic Apps it becomes very easy to follow the chain of occurred events in your logic apps, enabling you to see the input and output of the different actions which helps you understanding the different logic apps better – read the announcement by clicking here.

The Problem

As you can see in Screenshot 1 above it is pretty hard to understand what the different extractor actions do, isn’t it? It will be a demanding task to learn and understand logic apps by just looking at them in they designer view if they will look like shown in Screenshot 1, since the information provided is not enough – making it hard to understand.

The Solution

What we would like to see is a way of commenting each action in the workflow for better understanding each action being executed. An example would be a comment field  enabling developers to explain what the action does.

Screenshot 2 - Comment Field

Screenshot 2 – Comment Field

Twitter
YouTube
LinkedIn