There is no way for setting Stopped and Disabled states – not for monitoring or auto-correct behavior.

The problem this is creating for me is that if someone inadvertently starts a secondary FTP Receive Host Instance (as someone did recently) I want BizTalk360 to:

1. alert me that this Host Instance is in an unexpected state
2. have auto-correct set it to the desired state – Disabled
3. and stop the running service – because it should never have been started and must be stopped:
a. Set to disabled and left running is not what I need
b. Setting ‘Desired State’ to Stopped and using auto-correct to stop it isn’t enough – it needs to be disabled to draw someone’s attention to the fact that this service should not be started if it is seen to be down. This is special behaviour required by the limitations of the FTP Receive Adapter where business needs don’t justify clustering costs and a ‘warm standby’ solution is sufficient.

So in summary, what I would like BizTalk360 to do is to:

· Allow me to set desired state monitoring to disabled (which it does)
· Allow Auto-Correct to set the status to disabled (which it does)
· To also stop the service if it is running before setting the state to disabled

- Idea shared by Simon Young

Our BizTalk runs on two application servers and two Db servers. We are facing one problem where we have now clustered our SQL server enterprise single sign on service, so if one of the sql server is down, the SSO sign on service will move to another node.

Earlier the monitoring setup in BizTalk360 was Ent SSO service on both the sql nodes were set as started. Now it is running on one node at a time and the second is inactive. There can be a condition where this node can be down, so other SSO service node will be started automatically. So how to set this monitoring in BizTalk360, so that it can check for active node only on which SSO is running.
Services that are clustered should also be monitored.

- Idea shared by Akash (TCS).

When creating a new Alarm you must enable one or more of the 3 independent alarm types:
- Threshold
- Health
- Data Monitoring

There does not seem to be any logical reason that when an alarm should monitor Thresholds that it shouldn't also be monitoring Data and vice versa.
We ran into an issue when we built some DB Query Monitors and attached them to Alarms that didn't have Threshold monitoring enabled, only Data Monitoring. We never received alerts when the DB Query was triggering a failure. Only upon detailed investigation when we noticed that we were in a failure condition but had never received an email did we track down that Threshold monitoring was not enabled and DB Queries are part of Threshold, not Data Monitoring.

Hello BizTalk360 team,

I am helping TF1 test your monitoring solution and after my first presentation to different users, I have some remarks from them which I think might interest you :
· User management : possibility to create management profiles, and attach those profiles to users. I am aware that we can achieve something similar through AD groups, but they don’t seem to be very enthusiastic about it – mainly because the process of requesting membership to a specific AD group is slow…
· Graphical flow tracking and Message Box Queries (In particular, but this suggestion may apply to all functionalities) : automatically filter the data according to the applications the user is allowed to monitor
· Graphical flow tracking and Message Box Queries saved queries : right now all saved queries are available to any user (provided this user is granted the right to access Message Box Queries or tracking data). It would be nice to be able to grant / deny access per query and per user (profile?)

By Simon Rivas

We have a need for functionality regarding the filtering by time range in Data Monitoring.
We have a case where we are moving data from customer’s ERP to their CRM daily using BizTalk.
And sometimes those transfers fail.
If the transfer is older than 24h it already obsolete and we would like to get rid of that kind of BizTalk instances using the Data Monitoring.
As far as I know there is no way to setup it a way where it would terminate the instance if the creation date is older than 24h from current time?
The closest we have setup is following task in Data Monitoring and in my understanding it terminates all the instances between 24h in past and current time and that’s not what we are looking for.

New Message Box data monitoring tool – This new feature to perform actions is great allowing automatically messages to be resumed or terminated. The only issues with that is the minimum frequency we can set is only to 15 minutes and it would be perfect if we are allowed to set lower values like seconds or 1 minute for example. Also the option to send or not a notification for that as sometimes we don’t need the email and the last suggestion is to add the port name as a filter for that as sometimes we only would like to perform an action if the suspended instance is related to a specific port.

By Daniel Schnabel de Barros

Process Monitor to handle acknowledgements.
For examle
- System sends an invoice to BizTalk
- BizTalk do a couple och mappings
- BizTalk sends Invoice to VAN och directly to customer
- VAN or Customer sends an xml-ACK to BizTalk with invoicenumber and status
- BizTalk360 triggers alarm if:
o No ACK received in x minutes
o If status in ACK is different from ”OK”
- View in BizTalk360 that shows
o What system did send the invoice and when
o For how long did we have to wait for ACK
o And more…..
o Of cource filter to be able to see what invoices does not have ACK yet.

-Idea shared by Daniel Wilen.