Administrators of Business Activity Monitoring (BAM) definitions use the out-of-the-box BAM Management utility tool (BM.exe) to manage and maintain all aspects of the BAM infrastructure.
You can use the BAM utility to perform the following tasks:
- Consume BAM definition and BAM configuration XML as input. The BAM definition XML or XLS files define the data to track and aggregate and the business end user’s view on the tracking data. The BAM configuration XML mandates where to deploy the infrastructure, such as the server name, database name, and other database settings.
- Deploy the run-time infrastructure on the server, including the BAM Primary Import database, BAM Star Schema database, BAM Analysis database, and corresponding Data Transformation Services (DTS) packages. The following items are created during this step:
- BAM Primary Import database
- BAM Star Schema database
- BAM Archive database
- BAM Analysis database
You can learn more about this command-line tool in one of my previous posts: BAM Management Utility Commands – bm.exe. Nevertheless, despite being a powerful tool that works well, it is still an old command-line tool.
BizTalk Business Activity Monitoring Management Utility Tool is a Windows Application tool that works on top of the BM.exe to modernize and simplify its use. It is the equivalent of the BAM Management utility (BM.exe) tool with a GUI.
In this new version we:
- Tried to modernize the layout of the tool by adding a picture and some other minor adjustments.
- Fix some minor issues getting the correct version of the product – we removed the drop-down box, and now we are getting this info directly from the environment itself.
- Tested in BizTalk Server 2020.
- Rikard Alard, was the original creator of this tool.
- Diogo Formosinho | Linkedin | Member of my team, and that help me migrate this tool and add a more modern look.
THIS TOOL IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND.
You can download the BizTalk Business Activity Monitoring Management Utility Tool from GitHub here:
The post BizTalk Business Activity Monitoring Management Utility Tool appeared first on SANDRO PEREIRA BIZTALK BLOG.
While organizing my vast resources in my hard drive, I recently found out, polished, and improved two SQL Server queries that allow us to check the users and groups with access to BAM resources.
These are simple SQL Queries, but they are essential for maintaining your environment under control, security, and privacy standards compliance.
Generally, BizTalk Server is compatible with all the privacy standards-compliant like GDPR or FIPS. BizTalk Server is a messaging broker that doesn’t capture or store any data on its system other than for the time needed to complete business processes and connect and route messages to their target systems. However, because you can process messages and/or communicate with systems that contain sensitive data (personal data), you must have some good practices in BizTalk Server Applications to comply with privacy standards.
Business Activity Monitoring (BAM) is a collection of tools that allow you to manage aggregations, alerts, and profiles to monitor relevant business metrics (called Key Performance Indicators, or KPIs). It gives you end-to-end visibility into your business processes, providing accurate information about the status and results of various operations, processes, and transactions so you can address problem areas and resolve issues within your business. But it is also a component that can capture data from the messages passing by the systems, and some of these data can be sensitive – that shouldn’t happen, but it can happen.
So, it is always good in terms of security, control, documentation, and in some cases, privacy to know which users can access BAM data.
BizTalk Server: SQL Query to list all Users with access to BAMPrimaryImport database
This is a simple SQL Server Query that provides a list of all users that has access to the BAMPrimaryImport database.
THIS SQL SCRIPT IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND.
BizTalk Server: SQL Query to list all Users with access to BAM Views
This is a simple SQL Server Query that provides a list of all users access to a specific or to all BAM Views
THIS SQL SCRIPT IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND.
The post BizTalk Server BAM SQL Queries: Checking who has permission appeared first on SANDRO PEREIRA BIZTALK BLOG.
Do you feel difficult to keep up to date on all the frequent updates and announcements in the Microsoft Integration platform?
Integration weekly update can be your solution. It’s a weekly update on the topics related to Integration – enterprise integration, robust & scalable messaging capabilities and Citizen Integration capabilities empowered by Microsoft platform to deliver value to the business.
If you want to receive these updates weekly, then don’t forget to Subscribe!
Hope this would be helpful. Please feel free to let me know your feedback on the Integration weekly series
When you create a Web API you can use it for your own applications but maybe you also want to expose it to the outside world. In that case you probably want to change the behavior of the Web API. For example add security or hide properties. You can use BizTalk to create a virtual service in front of your Web API to modify the behavior but is that the smartest choice? Because BizTalk writes every message that it receives a couple of times to the MessageBox database. This increases heavily the execution time and especially with Web APIs it’s important to have a really low execution time!
Another option is to use Sentinet from Nevatech to create a virtual service in front of your Web API.
The virtual service runtime in Sentinet can also be extended with custom messages processing. Sentinet provides a number of build-in message processing components but it is also possible to create custom message processing components.
Let’s have a look at the following example where an Order Web API is used inside an organization to process orders. This Web API must also be exposed to external customers to show the status of an order but if an error occurs in the Web API or in a background process, the OrderStatus property must be modified that the order is still in progress and the ErrorMessage property with the error must not be shown to the customers. Furthermore the output of the Web API must be in XML instead of JSON.
The following steps in Sentinet are necessary to make it work:
- Add the REST service (or API) to the the Sentinet Repository
- Create a Virtual Service
- Add custom Pipeline Processing
- Test the Virtual REST Service
Sentinet makes it really easy to modify the response of a Web API. You only have to create a Virtual Service in front of it and add custom Pipeline Processing! Especially if you are already familiar with XPATH and XSLT, the example above doesn’t take long to implement.
Sentinet version 4.5