by Lex Hegt | Jan 9, 2020 | BizTalk Community Blogs via Syndication
In 2019, we released multiple major versions of BizTalk360. We have always believed that listening to the requests of our customers and partners is the right way to evolve the product. Many of the new features and improvements in the most actual version of the product have been suggested by our customers. So, we decided to organize a webinar to showcase the most appealing new features and improvements in the product.
Date: Wednesday 22nd of January
Time: 10 AM to 11 AM GMT (London)
Overview of some of the most important updates in BizTalk360 v9.x
It is interesting to see, that although over the last 8 years, we have brought over 60 releases, there are still areas where we can improve in the product. When looking at the v9.X updates we have released in 2019, the most recent version of the product contains 11 new features, 25 improvements, and 30 bug fixes. During the webinar, we will show the most interesting of these features in detail. Some of the features we brought are in the following areas:
- Monitoring and notification – SQL Server cluster monitoring, database size monitoring, a new BizTalk Group dashboard, configurable polling intervals, a new Notification Channel
- Operations – Querying Subscriptions, Send Port Group operations
- Analytics – APM integrations (AppDynamics, Dynatrace), Reporting improvements, data collection optimization
Does this sound interesting? It doesn’t stop here! Join the webinar to learn about other new capabilities in BizTalk360!
How does BizTalk360 help our customers?
Meanwhile, we have around 600 customers all over the world and we believe that we are doing a good job in helping them efficiently manage their BizTalk environments. But why should you just take our word for it?
That’s why we have invited representatives from a BizTalk360 customer and a partner to be a part of our webinar.
During the webinar, we will interview them, enabling them to share their experiences with BizTalk360. Please find a short introduction about both below.
The customer, UWV (Netherlands), is an organization around social security. They might just have the largest BizTalk Server platform in The Netherlands. UWV is using BizTalk360 for a few years now. We have invited Hans Knaap, a senior administrator at UWV, to share his experiences with the product.
The partner, Integration.Team, is one of the major Belgian consultancy companies in the area of Microsoft integration. During the webinar, we will talk to Jordy Maes, who is a BizTalk360 Product Specialist for multiple years meanwhile. He has done multiple implementations of BizTalk360 at his customers.
Join us at the Webinar!
The webinar will be hosted by two of our senior Product Consultants, who have years of experience in the area of BizTalk Server and BizTalk360. This tandem will be able not just to show how the new capabilities look like, they will also share how they can be used in day-to-day practice.
Do you want to join us at the webinar on January 22nd? Why wait! Registration is simple, just click the below banner and leave your details. We are looking forward to welcoming you during the webinar.
The post Webinar Spoiler: BizTalk360 v9. X Product Walkthrough appeared first on BizTalk360.
by Saranya Ramakrishnan | Jan 6, 2020 | BizTalk Community Blogs via Syndication
In BizTalk360, we have a practice of releasing new versions with significant features in every quarter. In 2019, we have released 4 major versions. In this blog, you can get to know about the top 10 stimulating features we have shipped in 2019.
1. Send Port Group Operations and Monitoring
You can completely manage and monitor your Send Port Groups from BizTalk360.
Operations – Send Port Groups can be Start/Stop/Enlist/Unenlist from BizTalk360. With this capability, it is possible to manage the operation of BizTalk applications (Start & Stop) for all the artifacts of each application in BizTalk360.
Monitoring – Create an alarm, map the Send Port Groups for monitoring by setting up the expected state. If any threshold violation occurs, you will be notified. You can also setup auto-healing for this monitoring; once the Send Port Group goes down, then BizTalk360 will try to auto-heal it to the expected state.
This implementation makes life easier for the BizTalk support engineers without context switching between the BizTalk admin console and BizTalk360.
2. Database Size Monitoring
Database Size monitoring helps to monitor the Data and log file size of the BizTalk and BizTalk360 databases, by simply configuring the error and warning threshold values for the database and log file sizes.
Below are the BizTalk databases that can be monitor using BizTalk360:
- BizTalkDTADb
- BizTalkMgmtDb
- BizTalkMsgBoxDb
- BizTalkRuleEngineDb
- BAM databases (BAMPrimaryImport, BAMAlertsApplication, BAMArchive, BAMStarSchema)
- SSODB
3. SQL Server Cluster Monitoring
Cluster SQL Server can be monitored by configuring the SQL Server Network name. BizTalk360 will start monitoring the currently active node. In case of a failover, BizTalk360 will automatically take the active server for monitoring.
The following resources can be monitored by configuring the SQL Server:
- CPU & Memory
- NT Services
- Disks (available disk space)
- Event Logs
4. Host Instance Monitoring
BizTalk Host Instances(clustered/non clustered ) can be monitored by setting the Expected State as started/stopped/AtleastoneActive. An alert will get triggered if there is a mismatch between the expected and current state of the host instance.
The state AtleastOneActive will guarantee that at least one host instance is running and no downtime happened for that host/server.
You can also enable AutoCorrect for Clustered and Non-Clustered host instances monitoring.
5. Configurable Polling Interval for Monitoring
By default, the BizTalk360 monitoring service checks the status of all configured artifacts every 1 min. However, BizTalk360 provides an option for the user to configure the polling interval. Based on the configured polling interval, the monitoring service will determine the monitor status of the endpoints.
6. SMTP Notification Channel
The SMTP Notification Channel provides an ability to create email distribution lists by grouping email ids based on the business needs.
Easily using the same email recipients for multiple alarms was not possible in earlier versions; the recipient’s details need to be entered for each alarm. To overcome this, we have introduced the SMTP Notification channel, through which the user can configure email distribution lists under one channel and can be mapped to multiple alarms. In addition to this, we have added email grouping for Up Alert and AutoCorrect Alert. With this, the user can configure different email ids to receive Up and AutoCorrect alerts.
7. BizTalk Group Dashboard
In BizTalk360’s Monitoring dashboard it was not possible to view the status of all the mapped artifacts in a single view; the user needed to change the alarm each and every time to view the status of the mapped artifacts of each alarm.
To overcome this challenge, we have introduced the BizTalk Group Dashboard which gives a consolidated view of the status of all the artifacts which are mapped to all the alarms in an environment.
The “BizTalk Group Dashboard” will automatically pick up all the artifacts (which are mapped to any of the BizTalk360 alarms) and displays the status of the artifacts in a graphical manner. Also, the error/warning details of the displayed artifacts are shown in a grid view.
8. Subscriptions (Message Box)
In addition, to retrieve the service instance and message details, BizTalk360 allows users to execute queries to retrieve the details of the subscription from the message box database. The subscription details such as Name, Service Name, state, subscription type, service instance id will be retrieved on message box query execution.
9. APM Integration
BizTalk360 is a one-stop tool for operations, monitoring and application performance management (APM) of BizTalk environments.
We get to see a few of our customers utilizing modern SaaS-based Application Monitoring/Analytics platforms like New Relic, AppDynamics, Dynatrace, etc., for their global enterprise analytics/monitoring requirements.
To support that we have integrated the following tools in BizTalk360.
- NewRelic
- AppDynamic (new)
- Dynatrace (new)
BizTalk360 Analytics service will start pushing the BizTalk performance data to your environment. With this, you can see the BizTalk server related performance metrics such as BizTalk/SQL Server health, Host Performance, BizTalk Messaging Performance, Throttling Performance, etc., in AppDynamics and DynaTrace environment.
10. Analytics Data Collection Optimization
We have fine-tuned the performance in analytics data collection. To improve the performance and tracking data collection we are providing an option for the user to select the required performance counters on each type. This way, BizTalk360 will start collecting data only for the selected counters.
Reporting Improvements
BizTalk360 provides the option for users to be able to generate PDF documents of critical performance metrics at specific time periods depending on the business.
In BizTalk Reporting, we have introduced an additive widget called Custom SQL Query widget through which SQL queries can be mapped to get the top 100 query result as a report based on the scheduled configuration.
In addition to this, we have extended our support for Analytics custom widget. With this, you can retrieve performance metrics of the BizTalk environment such as Messaging Performance, Message Transmission failure rate, Server performance, etc., and the SQL Query results as a report. Based on the configured schedule you can receive that report in your email box.
Conclusion
Considering the feedback from our customers, BizTalk360 will continue to provide more useful features. Why not give BizTalk360 a try! It takes about 10 minutes to install on your BizTalk environments and you can witness and check the security and productivity of your own BizTalk Environments.
The post Top 10 Features of BizTalk360 Released in 2019 appeared first on BizTalk360.
by Saranya Ramakrishnan | Oct 3, 2019 | BizTalk Community Blogs via Syndication
We are super excited to share the list of features that are planned for our upcoming BizTalk360 release 9.0 Phase 3. We always aim to constantly improve our product in every release, based on customer feedback and their business needs. Generally, we release a new version each quarter. In August 2019, we released Version 9.0 Phase 2. Now Version 9.0 Phase 3 is planned for late November and our team is energetically working towards it.
Reporting for Analytics custom widget
The BizTalk360 Reporting feature offers out of the box capabilities that allow users to create schedules and generate PDF documents of critical performance metrics at specific time periods.
From v9.0 phase 3 on, you can configure analytics custom widgets with the performance metrics of your BizTalk environment such as Messaging Performance, Message Transmission failure rate, Server performance, etc . and get that as a report, based on the schedule configuration.
For example, you can get a report by the end of the day with the number of messages processed for a particular schema or a particular send port.
Database Size Monitoring
This feature will be helpful for BizTalk administrators who frequently check the database growth to ensure the health of the BizTalk databases.
Some of the BizTalk databases can grow extremely big; it’s not uncommon to have over 1 million records in certain tables (ex: MessageInOutEvents table in Tracking Database). As the database size grows, the SQL server will need more memory and CPU to read data from the tables, and when the size of each table increases, it slows down the DB operations and affects the BizTalk operation.
With Database Size Monitoring, you can monitor the database and log file size of below BizTalk and BizTalk360 databases, by simply configuring the error and warning threshold values for the database and log file sizes.
- BizTalkDTADb
- BizTalkMgmtDb
- BizTalkMsgBoxDb
- BizTalkRuleEngineDb
- BAM Db’s
- SSODB
- BizTalk360
For example, If the size of the BizTalkDTADb is greater than a threshold value configured, then you will get notified.
Configurable polling interval for monitoring
The BizTalk360 Monitoring Service usually runs every 60 seconds and checks for the status of the artifacts which are mapped for monitoring, which include Application artifacts, File/FTP/SFTP, Queues, web endpoints, etc. We got requests from a few of our customers that they have configured multiple endpoints for monitoring and the BizTalk360 monitoring service calls the endpoint for every 60 secs to check the status, but they don’t want to call the endpoints frequently i.e. every 60 secs. So, to improve this, we are providing an option to configure the polling interval for monitoring; depending on the configurated time, only then the monitoring service calls the endpoint.
SQL Server Cluster Monitoring
In BizTalk360, we have a BizTalk and SQL Server Monitoring which allows you to monitor the Disks, System Resources, Event Log, and NT Services. From this version on, we extend our support to monitor the SQL Server cluster. By configuring the SQL Server network name for monitoring, BizTalk360 will start monitoring the current active node and in case of failover scenario, BizTalk360 will automatically take the active server for monitoring.
Support SQL Authentication SQL Query
The standard BizTalk Admin Console does not come with any capabilities related to accessing SQL Server data. This leaves the support people to rely on external SQL tools like SQL Server Management Studio (SSMS). Tools like SSMS are designed for DBA’s and Developers, and it’s not particularly friendly when it comes to pure support and management; a level of technical expertise is required to be able to use SSMS. We understood the practical challenges of not having an integrated SQL data access tool along with the BizTalk Administration and the challenges it exposes.
That’s why we have already built the “Secure SQL Queries” feature in BizTalk360.
Using Database Query monitoring, you can set up thresholds that are limited to database scalar values. For every BizTalk360 Monitoring cycle, the monitoring service will validate the results of the SQL query against the configured threshold values. If any violation happens, it will trigger a notification to the configured emails in the alarms.
However, since BizTalk360 does not support SQL authentication, currently you cannot access Azure databases from Secure SQL query and in Database Query monitoring. From this version on, the product supports SQL authentication for database access. You can query your Azure databases from the BizTalk360 Database query monitoring and Secure SQL Query sections.
Logic Apps Improvements
From this version on, you can provide access restrictions for logic apps. Based on the role, you can define which user can manage (enable, disable, delete, trigger) the Logic Apps.
Additional details such as Version, Last Run Time and Last Run Status of the logic app will get listed in the grid.
Copy Alarm along with artifact mapping
The first step in monitoring by using BizTalk360 is to create Alarms. Alarms in BizTalk360 act like a package to associate things together. We already have an option to copy the alarm which will copy only the alarm configuration. Now we are extending this to copy the alarm along with the artifact mapping configuration.
Alarm and Monitoring Dashboard Improvements
Below are some of the improvements, we have planned for this release in the Monitoring section:
- Indication of alarm status (Enabled/Disabled)
- Last Execution Time of the alarm
- Number of Alerts Notified (2/3)
- Indication whether Auto Correct is enabled or not
- The artifacts from the collapsed view will be made clickable to route to the respective configuration
Performance data collection improvement for DTA
We already optimized performance data collection in the last release. in this release, we are improving on DTA performance data collection. With this, we allow users to choose the relevant DTA metrics, which will reduce the number of calls to the DTA database.
Conclusion
Considering the feedback from our customers, BizTalk360 will continue to provide more useful features on every release.
Why not give BizTalk360 a try! It takes about 10 minutes to install on your BizTalk environments and you can witness and check the security and productivity of your own BizTalk Environments.
The post What is coming in BizTalk360 Version 9.0 Phase 3? appeared first on BizTalk360.
by Praveena Jayanarayanan | Aug 8, 2019 | BizTalk Community Blogs via Syndication
BizTalk360 is one-stop monitoring tool for monitoring your BizTalk environment. The BizTalk360 installation is a very quick process and does not take much time when all the prerequisites are met. For any software product, there would be some basic requirements that should be satisfied for its successful installation. BizTalk360 also has its own hardware and software requirements. In addition to these requirements, there are also some permissions and rules that need to be provided.
We have different documents that contain this information. But I thought it would be even more helpful for our customers if we have all this information in a single place. In this blog article, I would like to give a consolidation of all the requirements that one should make sure of before installing BizTalk360.
There are many considerations that need to be taken care of before installing BizTalk360, like where do you want to install BizTalk360, the service account permissions, the database creation, etc. Let’s look at each of them.
Installing guide for BizTalk360
BizTalk360, being a separate integration tool, always arises a query from the customers as to where we must install it. What is the best practice to install BizTalk360? It can be either installed on the same server where BizTalk is installed or in a standalone server.
The recommendation would be to install BizTalk360 on a separate server, rather than in the BizTalk server.
This will be useful in the performance perspective. The BizTalk server performance would not be hindered and BizTalk360 will notify the users when the BizTalk server is down. The important prerequisite for installing in a standalone server is that the BizTalk Admin Components must be installed beforehand in the standalone server.
If these components are not installed, then the BizTalk360 installer will fail with the following error.
The role of the service account in BizTalk360
One of the most important prerequisites for BizTalk360 is to configure a separate service account. The service account will be one that is used for the IIS App pool that will be created during the installation and also for running the BizTalk360 Monitor and Analytics service.
The recommendation is to create a dedicated service account, the reason being there are some permissions that need to be provided for this account.
The permissions would be:
- Local administrator permission in the BizTalk360 server for starting the Monitor and Analytics service
- Local administrator in the BizTalk and SQL server(s) for collecting the event log data and for disk and system resource monitoring
- Sysadmin permission to the SQL Server for creating and updating the BizTalk360 database
- Sysadmin permission for the BizTalk databases for monitoring and autocorrecting the SQL jobs. In case if you do not prefer to provide Sysadmin permission, you can provide SQLAgentOperator role for the service account for monitoring the SQL jobs and performing the autocorrect functionality
- Member of all the BizTalk groups
Once you have created the service account, you will have to log in to the BizTalk360 server with this service account to install BizTalk360. Logging in with other users may result in other permissions related to the database as other users may not have the expected permissions as the service account.
Firewall ports and protocols to be checked
When you plan to install BizTalk360 in a separate standalone server, there are some configurations that need to be taken care in the security perspective. For example, there may be firewall rules that may restrict access to the server. For BizTalk 360 to be able to contact BizTalk Server, the MSDTC connection needs to be enabled in all the servers. BizTalk360 should be enabled with certain ports/protocols for communicating with the external servers.
Next, make sure the below services are running in the server:
Also, make sure if custom ports are utilized for any service, unblock them as well from the firewall for the seamless working.
Ready to install BizTalk360
Once all the prerequisites are in place, you are now ready to install BizTalk360. The installation is a seamless process which would roughly take about 10-15 minutes when all permissions are in place.
You will have to make sure that you have logged into the server with the BizTalk360 service account. The reason for this is that when BizTalk360 is installed, the logged-in user will be created as a Super User in BizTalk360.
This Super User permission is required for the service account to perform certain automated processes like terminating/resuming service instances through Data Monitoring alarms and also for Analytics operations.
If for some reason, the installation fails, the first thing to be looked for the error, would be the installation logs.
Important configurations for BizTalk360
For BizTalk360 to be up and running, there are some configurations that need to be done. For example, the SMTP setting would be required for triggering the alert emails. You will need to create different users for accessing BizTalk360.
You can refer to the implementation of best practices here.
Best practices on a performance perspective
For any software product, the performance would be the foremost priority. Some of the performance measures that can be taken up for enhancing BizTalk360 would be:
- Configuring only the required sources in the Advanced Event Viewer so that the database growth is controlled
- Maintaining the appropriate purge duration to remove the historical data based on the business needs
- Enabling only the relevant performance counters for Analytics performance data collection
Upgrade and Migration Scenarios
- What happens when you upgrade BizTalk360 to a new version?
- What happens when you migrate your BizTalk server?
- Let’s have a look!
Upgrading BizTalk360
A new version of BizTalk360 is released every quarter with new features and enhancements picked up based on customer feedback. The release would also include certain bug fixes as well.
It is important that customers upgrade their BizTalk360 to the latest version to be in line with the release and enjoy the new features.
Things to be taken care while upgrading BizTalk360:
- You should log in with the BizTalk360 service account to the BizTalk360 server
- The license needs to be deactivated
- The database should be backed up so that in case of any errors, the old database can be restored
- Once after the successful upgrade, it is important to clear the browser cache and then launch BizTalk360
In a scenario where there might be some problems during the upgrade, the customer could have uninstalled and reinstalled BizTalk360. In this case, they would have restored the old database and the following error would occur.
Here, we can see that the application has been upgraded but not the database since the old version of the database has been restored. The suggestion here would be to run the SQL scripts from the next version seen in the error from C:Program Files (x86)Kovai LtdBizTalk360ServiceSQL folder. Please note, if there is more than one script that needs to be executed, then they should be run in the same sequence.
Upgrading BizTalk Server
Customers might migrate from a lower version of BizTalk Server to a higher version, say for example from BizTalk Server 2013 to BizTalk Server 2016. There are some configuration changes that need to be done at the BizTalk360 side as well to point to the new BizTalk environment. The below steps need to be followed in the BizTalk360 box when you migrate the BizTalk server.
- Deactivate the license in BizTalk360 first before migration
- Install the new version of BizTalk admin components in BizTalk360 server
- After migration, update the environment details to point to the SQL instance which contains the BizTalk databases
- The below tables need to have the BizTalk version changed appropriately and the MS_BizTalk_install_location should be updated
b360_admin_BizTalkEnvironment -> BizTalk Version
b360_admin_GlobalProperties -> MS_BIZTALK_VERSION & MS_BIZTALK_INSTALL_LOCATION
You can export the alarms from the old BizTalk360 environment and import them to the new environment. The mappings will also get imported to the new environment. If you are using BizTalk360 v8.8 or later, then you can export the user settings as well.
- Modify the alarm mapping to point to the artifacts in the new environment
Migrating BizTalk360 database and application
When the BizTalk360 database is moved to a new server, the connection string needs to be modified in the following config files:
- Web.config
- BizTalk360.Monitor.exe.config
- BizTalk360.Analytics.exe.config
For more details, refer to the article.
BizTalk360 additional details
The integrated Troubleshooter in the BizTalk360 UI will provide you with the complete details of BizTalk360 like the connection string, installation location, and the database.
Conclusion
Once all the setup and configurations are in place, it is a quick and seamless task to install/upgrade BizTalk360. The customer suggestion and feedback are always heard and addressed, which helps us to improve the product and provide better service.
Happy monitoring with BizTalk360! 
The post BizTalk360 – Ready to function appeared first on BizTalk360.
by Raja Sreenivasan | Jul 4, 2019 | BizTalk Community Blogs via Syndication
Introduction
BizTalk users who use BizTalk360 can manage their BizTalk environment in a more efficient way. Monitoring and Notification is amongst the most important features in BizTalk360, The first and foremost step for monitoring is mapping the artifacts to an alarm. In which user can use this on a daily basis to monitor their BizTalk environment and get notified if any violation occurs.
The Monitoring Dashboard is the one stop point for users to view the status of the artifacts which are mapped to an alarm. Typically a customer displays the monitoring dashboard in big screens and looks for the health of their BizTalk environment visually. The monitoring dashboard is structured at alarm level, which lists the status of all the artifacts mapped to the respective alarm. However, you cannot see all the alarms and their mapped artifacts status in a single view, which was a usability problem persist from our side. To overcome these we are implementing the “BizTalk Group Dashboard” for the v9.0 (phase 2). With this dashboard you can view the status of all the artifacts mapped to any number of alarm in a single view and you can easily customize it using the rich filter option provided
Let’s deep dive into BizTalk Group Dashboard and see how it solves the problem.
BizTalk Group Dashboard
The BizTalk Group Dashboard is designed to monitor all the artifacts (and view all errors) which are mapped to all the configured alarms in BizTalk360, in a single view. The BizTalk Group Dashboard can be found under the Home of Monitoring section. The “BizTalk Group Dashboard” will automatically pick up all the artifacts (which are mapped to any of the BizTalk360 alarms) and displays the status of the artifacts in a graphical manner . Also the error details of the displayed artifacts are shown in a grid view . The BizTalk Group dashboard checks the status of the artifacts in every 60 seconds .
For better usability, BizTalk Group Dashboard splits the windows in two sections:
- Displays the mapped artifacts in a graph
- Show the Error/Warning details in an artifact level segregation
The dashboard has a draggable separator so that the user can adjust the width of the graphical window and the error/warning pane, based on their resolution. They can even minimize or maximize the error/warning pane to the leftmost section.
There is a chance of mapping the same artifact to multiple alarms. In such cases, the BizTalk Group Dashboard picks only the positive state of artifacts for monitoring. For instance, a Receive Location is mapped to an alarm1 with the expected state as Enabled and the same receive location is mapped to another alarm, say alarm2, with the expected state as Disabled; in this scenario, the BizTalk Group dashboard will only consider the positive state mapping such as expecting state as Enabled for monitoring.
Note: BizTalk group Dashboard is only designed for visual monitoring of the BizTalk environment and artifacts. It will not trigger any alert notifications.
Advantages of BizTalk Group Dashboard
Comparing to the already existing Monitoring Dashboard, the BizTalk Group dashboard has quite some advantages. Some of the main advantages of the BizTalk Group Dashboard are:
- It consolidates the status of all the artifacts which are mapped to any alarm and there is no need to switch alarms for viewing the status of any other artifact
- The BizTalk Group Dashboard can be split into two windows; one for the artifact graph and the other for viewing the Error/Warning pane. For usability, the split windows can be adjusted based on the monitor resolution
- For better monitoring, the user can apply filters (at the top of the graph) based on the artifact and/or based on the event type filter option
- The user can view the Error/Warning details along with the graph
Scenarios
Many organizations use different alarm configurations and patterns for their processes. Some of the commonly used alarm configuration patterns are:
- Integration-based alarm configuration
- Role-based alarm configuration
- Entity-based alarm configuration
Integration-based alarm configuration means configuring BizTalk artifacts, File location, Queues, Web endpoints, etc. in an alarm, which all belong to the same integration.
Role-based alarm configuration is configuring alarms for people in different roles. For example, a platform administrator will be interested in infrastructure settings like Disk, system resources, host instances in an alarm.A Database Administrator (DBA), on the other hand, will be more interested in the SQL Server instances and the jobs which have been deployed in it.
Entity-based alarm configuration is configuring similar components in the same alarm. For instance, putting all the queues like IBM Queue, Azure service bus queue, MSMQ in one alarm.
Irrespective of the alarm configuration/pattern, now the user can customise the BizTalk group dashboard using the filter capablity .Say Administrator can monitor the infrastructure components which are mapped to all the alarm .) and queues in a single dashboard window by filtering only the Infrastructure components.
Conclusion
With this feature, users are able to visually monitor all the artifacts and view error/warning details in a single dashboard with a much more comprehensive view. If you have any feedback or suggestions, please write to us at [email protected]. You can get started with monitoring your BizTalk environment via the BizTalk Group Dashboard by downloading the 30-day free trial of BizTalk360.
The post Consolidated monitoring with the new BizTalk Group Dashboard appeared first on BizTalk360.
by Saranya Ramakrishnan | Mar 20, 2019 | BizTalk Community Blogs via Syndication
BizTalk360 enhances the complex administrative tasks into a modern easier task. We always aim to constantly improve our product based on our customer’s feedback and their business needs. We have recently released V8.9.5. The upcoming version 9.0 features are typically chosen from our customer feedback based on the impact and the number of requests.
You asked and we are implementing the below features for v9.0.
Alarm Auditing
When we work on cutting edge technology, security is one of the important factors we always need to consider. Keeping that in mind, earlier we implemented Governance and Auditing which actually audits BizTalk level activities from BizTalk360. You can think of actions on BizTalk Applications, Service Instances, Host Instances, BizTalk and SQL Servers, ESB Messages and Business Rules.
Many customers requested us that it could be great if Biztalk360 activities such as Alarms, User access policy activities also audited. So, for this release we have implemented Alarm activities. Alarm operations such as new alarm creation, deleting an alarm, changing the alarm status (Enable/Disable), editing alarm details will be audited with the existing and new values, along with the user details. With this, the administrator will get clear picture of all the alarm activities.
Also, we have taken Secure SQL Query auditing. If any query has been created or modified this will be audited. We also implemented auditing of the ‘Execute’ operation. So, with this administrator can easily look for, who has executed which query and which parameter value are passed for the query execution in detail.
SMTP Notification Channel
In BizTalk360 version 8.0, we introduced Notification Channels. With this , it’s easy to send alerts to any external systems like your ticketing system, internal databases, calling REST endpoints or executing PowerShell scripts.
To add more value to this, we are bringing the SMTP Notification Channel which provides an ability to create an email distribution lists by grouping email ids based on the business needs. The monitoring service will generate a notification to a group of people by simply configuring the recipient address (To, CC) in the channel. Once the SMTP notification channel is configured it can be used in all the alarms just, by enabling the channel. This will prevent the user to type email ids over and over again.
UnMapped Artifacts List
When the artifacts are mapped for monitoring, BizTalk360 will take care of it and intimates users when any violation occurs. But, what happens if you missed to map some artifacts for monitoring? You will not get any notification for this, right?! Of course, we don’t want you to miss artifacts for monitoring.
This problem will be solved in v9.0, you will get a summarized list in the Monitoring Dashboard. This list contains the status of the artifacts which has been mapped for monitoring and also the unmapped artifacts list. For instance, if any new artifacts have been added in your BizTalk environment, we will bring that to your notice and you can easily map the artifacts for monitoring. Also, we will forward the list of unmapped artifacts to the system administrator based on the configured interval time.
Switch User Roles
As of now in BizTalk360, once a user profile is created, the user roles (Super, Normal) cannot be modified at any point. To change the user roles, the profile needs to be deleted and recreated again which is a time-consuming process. This will be solved just by editing and changing the user roles. So Super Users can quickly be converted to Normal users and vice versa in a single step.
Copy to Clipboard
Our business data is highly valuable. The information uses contains decision-making and problem-solving. From v9.0 we are providing an option to copy your information’s in a single click from the BizTalk360 UI to the Windows Clipboard.
Apart from these new features, we are working on improvements in the following sections.
Monitoring Dashboard
The BizTalk360 ‘Monitoring Dashboard‘ becomes the one-stop point for support people to view the health status of BizTalk environment. We have planned to do some changes on monitoring dashboard UI which helps you to see the summarized dashboard in much enriched view.
AutoCorrect reset
In BizTalk360 we have the Auto Healing functionality with which, if your artifacts go down, the system will try to auto heal the violation. The system will retry the auto healing process for a configured number of times. Once retry limit is reached the auto healing process will be stopped.
In v8.9.5 we introduced the auto reset option for the auto healing process, in which, after the configured interval time, the retry count will be reset to 0 and starting the auto healing process again. We kept the “interval time to reset the retry count” to 0. This means that the retry limit will never reset, unless the user goes and manually change the interval time. This is quite a tedious process when you have huge number of artifacts mapped for auto healing.
This problem will be solved as we will provide an option to define the default interval time globally. So once you update the interval time it will be used for all the artifacts.
Conclusion
Considering the feedback from our customers, BizTalk360 will continues to provide more useful features. Now we would like you to hear from you, so please take some time to fill this questionnaire to help us prioritize the next upcoming feature tasks. Stay tuned for next version v9.0.
Why not give BizTalk360 a try! It takes about 10 minutes to install on your BizTalk environments and you can witness and check the security and productivity of your own BizTalk Environments. Get started with the
The post What is coming in v9.0 appeared first on BizTalk360.
by Senthil Kumar Palanisamy | Mar 7, 2019 | BizTalk Community Blogs via Syndication
BizTalk360 Monitoring
BizTalk360 comes with out of box capabilities to monitor BizTalk Artifacts, BizTalk Environment, Queues (IBM, Azure Service Bus and MSMQ), File Location (File, FTP and SFTP) and so on. The Monitoring Dashboard represents the Monitoring Status in a nice graphical chart view. Different set of users like BizTalk Administrators, Operators, Technical members and Business users are using the monitoring features for their day to day activities. Users create multiple alarms to suffice their needs to monitor the health of their BizTalk environment.
While users are monitoring the multiple alarms, they must keep an eye on multiple dashboards. It is a cumbersome task if a user takes care of more than two Alarms. Based on this requirement, few customers have requested for consolidate view of alarms. In this article, we are going through the process of how you can create a consolidated view of multiple alarms using Custom Widgets.
Scenarios
BizTalk360 users are configuring the alarms based on their business vertical or alignment to their process. There have been different patterns in alarm configurations. We can see some of the commonly used patterns;
- Integration-based alarm configuration
Configuring BizTalk Artifacts, Web Endpoints, Queues, File Location etc. of integration in an alarm.
- Role-based alarm configuration
BizTalk Administrators will look after infrastructure settings like Disk, System Resources, Host Instances and configure in an alarm BizTalk Operators can configure BizTalk Artifacts and other entities in a single alarm
- Entity-based alarm configuration
For instance, users can configure all their Queues (IBM/Azure Service Bus) in an alarm. Similarly, they can configure Web Endpoints, Infrastructure (Disks, System Resources) in separate alarms.
Based on the above patterns, Role-based and Entity-based alarms can have a single view of multiple alarms in which you can monitor all the entities. When you follow the Integration-based alarm pattern, then entities like Application Artifacts, Azure Service Queues and BizTalk Server health activities are in different alarms.
Many organizations follow the Integration pattern by grouping all the related artefacts in an alarm. In this scenario, users (BizTalk Operators/BizTalk Technician) must monitor multiple alarms. For Instance, BizTalk Operators looking after BizTalk Artifacts or Developers responsible to monitor Azure Service Bus Queues will have to monitor the multiple alarms. Let’s see how to overcome this challenge by using custom widgets to group multiple alarms.
Consolidated Dashboard
The Monitoring Dashboard is one of the most used features among the users to monitor BizTalk Environments and Artifacts in BizTalk360. An enriched monitoring capability while using Custom widgets to group the multiple alarms to get a single view based on business or team members role.
Custom Widgets are a powerful feature in BizTalk360, as such widgets will provide the opportunity to meet their business scenarios. Many customers adopted Custom Widgets to provide solutions to end users.
Following are a few illustrated scenarios of grouping alarms when it is configured based on integrations
- Azure Service Bus Queues
- BizTalk Application Artifacts
- BizTalk Environment Health
In this article we take one of these scenarios, to show how users can achieve the grouping alarms using Custom Widgets
Azure Service Bus Queues
Custom Widgets used BizTalk360 Secure SQL Query API’s to fetch all Azure Service Bus Queues Monitoring Status from BizTalk360 Database. A user can select the filter with different alarms they want to group.
By default, the user can see only the unhealthy queues in an environment. If they set the Enable Healthy Queue option, they will be able to view all queues in the tree nodes. The Azure Service Bus Queues Custom Widget will fetch the information from Secure SQL Query with a refresh interval which is configured in the script of the custom widget.
Follow the below steps to achieve the Custom Widget’s script;
1. Secure SQL Query
Create the Secure SQL Query to fetch the monitoring status of Azure Service Bus Queues in the environment. To know more about how you can execute Secure SQL Queries using custom widgets, refer to this article.
2. Custom Widget Script
Create the initial variables, Place holders and SQL Query to call the BizTalk360 API method in the Custom Widget’s script
// BEGIN User variables
azureQueueRefresh = 20;
username = "`username_812414`";
password = "`password_701422`";
environmentId = "`productionenvid_189308`";
queryId = "8eea2771-10a7-44c6-8709-a597687434cf";
queryName = "Azure ServiceBus Queues";
sqlInstance = "kovai-bts";
database = "BizTalk360";
sqlQueryForAzureGraph = "Select AA.Id,AA.[Name],AME.MonitorStatus,AME.ExecutionResult from [dbo].[b360_alert_MonitorExecution] AME Inner Join[dbo].[b360_alert_Alarm] AA ON AME.AlarmId = AA.Id and AME.MonitorGroupType = 'Queues' WHERE AME.LastExecutionTime = (SELECT MAX(LastExecutionTime) from [dbo].[b360_alert_MonitorExecution] WHERE MonitorGroupType = 'Queues' and AA.IsAlertDisabled='false' and AlarmId = AA.Id and LastExecutionTime >= DATEADD(MINUTE,-60,GETUTCDATE())) AND AME.EnvironmentId ='`productionenvid_189308`'"; // The SQL Query which needs to be executed from the custom Widget
bt360server = "biztalk360.westus.cloudapp.azure.com"; // Name of the BizTalk360 server (needed to do an API call to execute the SQL query
//Mention the created alarm details and the respective partner name to display in the graph.
AlarmDetails = [
{ AlarmName: "Threshold-1", PartnerName: "Air India" },
{ AlarmName: "Threshold-2", PartnerName: "British Airways" },
{ AlarmName: "Threshold-3", PartnerName: "DHL" },
{ AlarmName: "BizTalk360 Default Alarm1", PartnerName: "Jet Airways" }
];
// END User variables
3. GO JS Framework
BizTalk360 uses the GO JS Framework- Organization chart to represent the monitoring hierarchical view in the UI. It will display the organization chart structure as Azure Service Bus Queue node as a root node, Integration friendly name as second level node and Queue threshold violation details as a child node. You can control the nodes expand/collapse capability of through the custom widget code.
4. Filter Options
Users can able to filter the data based on the selected alarms or the option to show healthy queues. By default, users can see only unhealthy Azure Service Bus Queues. Similarly, other scenarios are implemented through custom widgets. To get the full source code of the Custom widgets you can download it from our GitHub Project.
Summary
We hope this article is useful in grouping the multiple alarms into a single view in an environment. This will bring you more control over the custom development you may want to achieve.
Get started with the free 30 days trial. For any queries/feedback please write to us [email protected].
The post Achieving a Consolidated Monitoring View Using Custom Widgets appeared first on BizTalk360.
by Praveena Jayanarayanan | Jan 21, 2019 | BizTalk Community Blogs via Syndication
A few more days to go for the release of our new version, BizTalk360 v8.9.5. Release by release, we aim at improving the user experience by adding new features and enhancing the existing features as per the suggestions and feedback received from our customers. The feedback can be posted in our User Voice portal http://feedback.biztalk360.com. There, customers can vote for the posted suggestions if they feel that the ideas also fit into their business requirements. These suggestions will be taken up for development based on the priority of voting.
There have been quite a few features and enhancements added in this release. Let’s look at one of the features which got the attention of many customers and that we thought it would ease the users in their business operations while using BizTalk360. So come on, lets jump in!
User Access Policies
After the installation of BizTalk360 and activation of the license, the next thing the user would do is to create the users, groups and provide access to the BizTalk360 features in the User Access Policy section. This is available only for providing access to the features in BizTalk360 and not for BizTalk level access. The importance of this feature can be known from the article User Access Policy.
In our previous version, BizTalk360 v8.9, this feature was enhanced to configure different rules for providing access to the existing as well as newly created BizTalk applications for the users. Get to know about the different rules here “User Access Policy – The New Look for Application Access”.
As part of this enhancement, we have introduced the concept of the Application groups for grouping the applications of similar category and provide users the access to the Application groups. So, any new application created, when added to such an Application Group will be automatically given access to the users.
Now there is an additional feature of managing custom User Access templates, which is described in the later part of this article.
As part of this enhancement, the user management, application groups and the custom templates must be managed in different sections. This has been done to avoid confusion to the users. Hence, the existing look of the User Access Policy section has been modified as below.
Manage Application groups
The application groups can now be managed in a separate section. Here, the application groups can be created, modified or deleted. Now it would be easy for customers to create application groups and manage them from a single section rather than moving between the screens.
Manage Users
This section remains the same as in previous versions, where the users and NT groups can be created, modified or deleted. Modification has been done in the Add permissions section for the normal users to include the custom profile templates newly created.
The Profile Templates
Keeping in mind the level of security needed for accessing the features and performing the operations with the BizTalk environment, we have the fine-grained authorization within BizTalk360. When a new user is created, the permissions to the BizTalk360 features can be selected from the list of features under each section and saved to the user profile. When the new user logs in to BizTalk360, he can only use the features which are added to his profile.
In the earlier versions, the features were selected from the list available or from the predefined templates available. These predefined templates come as part of the installation. There are three predefined templates available:
- View only modules – Choosing this template will provide read-only access to few features in BizTalk360. This will be helpful for the Level 1 support team
- Limited operation access – This provides access for the users to operate on Host Instance, applications and service instances
- Full access to all modules – As the name implies, the user will have access to all the features when this template is chosen
As per the feedback received from the customer, we have added the new capability to create custom templates and select them for providing access to the users.
How do the custom templates help?
Consider a scenario, where the customer would need to provide similar permissions to multiple users. This can be done by creating a group and applying the profile to the group account. But what if we need to make some minor changes to some of the users. It would be very difficult to make changes for some users within the group.
With the help of a custom profile template, this can be made in a single click. You can create a custom template with the desired features selected and choose the template while creating the users. Won’t this be an easy and quick way of configuring permissions to the users? Yes, of course!
The creation of custom templates is also done very quickly. The custom template can be created by providing a name to the template and selecting the features to be added to the template. With this feature, for each custom template, you can select permissions and store them as a custom template.
This would be similar to the Add permissions section in the user creation, but the only difference being the selected features can be saved to a template and used later in creating different users. The predefined templates would be suffixed with System Predefined in the name.
With the custom profile templates, the user creation is made much easier. The customer need not scroll through the entire list of features while creating users.
Conclusion
We always monitor the feedback portal and take up the suggestions and feedback. Now we would like to request you, our customers, to please take the time to fill this questionnaire to help us prioritize the next upcoming feature tasks, to let us know what are your main pain points and help us to further improve the product.
Why not give BizTalk360 a try! It takes about 10 minutes to install on your BizTalk environments and you can witness and check the security and productivity of your own BizTalk Environments. Get started with the free 30 days trial. Happy monitoring with BizTalk360!
Author: Praveena Jayanarayanan
I am working as Senior Support Engineer at BizTalk360. I always believe in team work leading to success because “We all cannot do everything or solve every issue. ‘It’s impossible’. However, if we each simply do our part, make our own contribution, regardless of how small we may think it is…. together it adds up and great things get accomplished.” View all posts by Praveena Jayanarayanan
by Mekala Ramesh | Jan 3, 2019 | BizTalk Community Blogs via Syndication
BizTalk360 team Wishes you all a Happy and Prosperous New Year!
In 2018, we have released 3 major versions of BizTalk360 with various new capabilities, enhancements and bug fixes. In this blog post, we wanted to summarize the best 10 features released.
1. Import & Export
All the newly created BizTalk Server applications are being tested first in the preproduction or UAT and shadow environments to avoid business consequences. Likewise, customers would prefer to test all the functionalities of their BizTalk360 configuration in their non-production environments. Further, they populate necessary data to operate, monitor and find analytical information of their environment. Admins don’t need to recreate their BizTalk360 configuration again in their production environment as in these situations, our import and export capability plays a major role. We have enhanced the existing functionality for users to be able to export:
1. User Access Policies
2. Saved queries
3. Secure SQL queries (along with their configurations)
4. Knowledge Base articles
5. BizTalk reports
6. Dashboards and Custom Widgets (along with their configurations)
from one environment (QA/Development/UAT) and import them as is into another environment (i.e., Production). Users can also change the configurations while importing into the destination environment.
2. Advanced web endpoint monitoring
In a BizTalk environment, the health of Web Endpoints is vital to be able to process the data between multiple applications/partners. BizTalk Administrators might manually monitor the health and results of web endpoints in every execution, but this is a cumbersome process. BizTalk360 provides the capability to monitor such Web Endpoints. This monitoring capability is extended to support other different authentications.
Basic
In the context of the HTTP transaction, there might be a scenario to authenticate the web endpoint using the Basic Authentication method (User Name, Password). BizTalk360 has this capability to monitor the Web endpoints using Basic Authentication.
Certificate Authentication
As like basic authentication, some HTTP web endpoints require a SSL certificate for the communication. To support this kind of scenarios, we have introduced a new option to provide client certificate thumbprint in the web endpoint monitoring section.
Azure Services Authentication
To provide extended support to monitor Azure services web endpoints, we have enabled the Azure services authentication mechanism in Web endpoint monitoring section. Once the Azure service principal is configured in Azure, information like Tenant Id, Client Id and Secret key need to be provided for monitoring.
3. Business Holiday Calendar
BizTalk360 provides this new capability to configure the business holidays in a calendar. These business holiday calendars can be mapped during maintenance window setup. This new configuration section is introduced in the Monitoring Notification settings section as “Configure Business Holidays”.
Using this intuitive UI, users can configure the business holidays in a calendar and save it for further mapping during the maintenance setup process.
4. User Access Policy – Multiple options for providing access to BizTalk applications
In earlier versions, it was a simple grid displaying all the available applications in a BizTalk environment, and you can select the applications to provide access to Normal Users/Groups. But now we have modified this, to provide multiple options for providing access to the applications. This would surely be more user-friendly and of course, meet the requirements. The different options include:
Grant Access by Applications
By enabling this option, the user has access to all the currently configured applications. Once this option is enabled for any profiles, that user doesn’t have access to the newly integrated applications in your BizTalk Server.
Grant Access to all Applications
As the name denotes, enabling this rule will provide access to all the available applications for the Normal Users/Groups. This will be similar to the permissions of the Super User who will have access to all currently deployed and newly added applications.
Wildcard Search
The user can select the required option and provide the search value. Once this rule has been configured, the user will have access to all the applications matching this wildcard. Also, the user will automatically be given access to the newly created applications that match the wildcard.
Grant Access to Application Groups
With this new capability, you can create Application Groups and map BizTalk applications to that group. Once the user is given access to the Application group, he/she can access all the applications mapped to that group.
5. PowerShell Notification Channel
Besides the already available notification channel features, BizTalk360 supports integration with PowerShell scripts. This new capability enables the user to perform some tasks via a PowerShell script, each time the alarm was triggered.
It only takes a few steps to use the PowerShell Notification channel:
– Create the PowerShell script
– Configuring the PowerShell Notification Channel in BizTalk360
6. Grid Column customization
Grid columns can be dynamically removed or added based on the user preference. As per the settings in the configuration section, columns will be aligned and displayed in the grid view. These customized column settings can be saved for future reference as well. We are sure this capability will add more value when the administrator is looking for the instances/messages based on various conditions.
As an initial phase, this implementation has been done in the following areas in BizTalk360:
1. Message Box Queries
2. Graphical Flow (Tracking)
3. Electronic Data Interchange
7. Pagination for improved performance
We have optimized the grids by providing you the power of pagination. We have implemented pagination for each grid available in BizTalk360. It is an easy and standard practice that prevents you from having to load the entire result set all at once. The grid supports both preloaded and dynamically loaded data. By using pagination, the rows in the grid gets dynamically separated into pages. The grid will automatically display default rows in each page. The user can increase the maximum number of result rows by selecting the Max Match size in the drop down.
8. Grid Column Filtering
All the grid columns in BizTalk360 have got a new makeover. In a high-volume data store scenario, there will always be challenges to quickly filter and retrieve the desired data. To simplify the data retrieval process, we have implemented 4 types of filters in BizTalk360.
Text Filter
Text filter is the default filter. Using a text filter, you can filter the text input. The text filter is already implemented in BizTalk360 in various sections. The user should enter the text in the filter text box to retrieve the desired data set.
Checklist Filter
Using this filtering type, the grid shows a checkbox list with the set of predefined values. The user can select one or more of the values and apply the filtering. The types are status, Boolean & Date Time filter.
Status Filter
A Status filter allows filtering the different status in the column. For some filter conditions, some predefined values will be shown in the drop down for the data retrieval. The user can retrieve the data based on the available status. For example, a BizTalk application has different statuses, like Started, Stopped and Partially started.
Boolean Filter
This kind of filter is used to fetch the value based on true or false conditions. Say for example, in the Search Artifacts section we have a checkbox column to check for the receive port, if it’s a two-way port or not. Using the Boolean filter for this column, the user can filter for the two-way receive location.
9. Stop Alerts for maintenance Improvements
During a maintenance window, no notification was shown in the UI. This is enhanced now, and a notification will be shown in the Operations dashboard and Alert Maintenance section. We have added the capability to allow the users to set up multiple (future) maintenance windows. Additional to this, historical maintenance schedules are preserved for auditing purposes along with periodic purging capability.
10. Triggering alert emails to admin users
Alert Notification will be sent to the admin users in case there is some monitor error. Admin users can be configured in the system alert settings section.
Installer Improvements
Installer Logging capability
We have enabled a logging capability in the installer. This will help the users and support engineers to identify the root cause in case of any issues during the installation process.
Installer One Password Capability
We have enhanced the BizTalk360 installer, where only one set of credentials (UserName, Password) will be asked during the upgrade process, in case the same credentials have been used for all the installed components.
Installer SQL Upgrade
There was no support for the SQL authentication upgrade. We have enhanced the installer logic to support SQL Authentication upgrade.
Persist Web.config file changes during the upgrade
To access BizTalk360 via the HTTPS protocol, few configurations need to be done in the web.config file. In earlier versions, during the upgrade process, this configuration is overridden, and the user needs to do the configuration every time. This has been enhanced, and changes which are made in the config file are persisted during the upgrade process.
Conclusion
I must say 2018 was a fantastic year for us, where we focused on improving the product with exciting new features, enhancements and fixing support cases. Along with the above new capabilities, we have provided a fix for 209 support cases and enhanced 24 existing features.
We are looking forward, 2019 would be another great successful year for us with more exciting new features added to the product.
Author: Mekala Ramesh
Lead QA & Product Support at BizTalk360 – Having around 8 years of experience in software testing & customer support field with the strong knowledge in SDLC and STLC phases. Specialized in various types of testing methodologies. Passionate tester, who always want to deliver the software product with the best quality to the end customers. Possess strong knowledge, to establish the testing process from scratch. Playing a pivotal role in BizTalk360 is making me deliver the product to every customer in a delicious way. View all posts by Mekala Ramesh
by Rochelle Saldanha | Nov 6, 2018 | BizTalk Community Blogs via Syndication
Continuing in our series of blogs, Customer feedback getting Answered, where we will be trying to address and answer some of the issues, where a workaround is possible, rather than awaiting a new feature release.
Today we will address an issue relating to BizTalk Health Monitor (BHM) integration in BizTalk360.
Issue at hand
One of our existing customers posted the following feedback request: http://feedback.biztalk360.com/forums/331695-biztalk360-operations/suggestions/20567692-bhm-bt360-profile-use-monitoring-profile
He wanted to specify or change the BHM Monitoring Profile that BizTalk360 should use.
Monitoring Profile in BHM
The BizTalk snap-in, “BizTalk Health Monitor” (aka “BHM”), has so been created to help you easily monitor the health of your BizTalk environment. BHM is based on the same engine as MBV. This snap-in can be added to the existing BizTalk Administration Console or can be run individually in its own MMC window.
A Monitoring profile is in fact a BHM profile, but configured specifically to execute a short selection of critical BHM queries/rules and custom rules checking the state of given ports, orchestrations, host instances, queues and BizTalk databases sizes and raise critical warnings detected in a log.
Current Working of BizTalk360 integrated BHM
The BizTalk360 product integrates with BHM, but currently has the limitation that you cannot specify a profile, that is stored in BHM, which should be scheduled and run at those specific times.
Solution Workaround
If you wish for BizTalk360 to run a certain BHM profile – Follow the below workaround.
- Save the Profile. This will automatically save a copy in the folder – C:ProgramDataMicrosoftBizTalkHealthMonitor with the name MBVSETTINGS_.xml
- Now you need to copy this XML file and paste it in the BizTalk360 folder – C:Program Files (x86)Kovai LtdBizTalk360Service.
- Delete the existing MBVSETTINGS.xml and rename the copied file to MBVSETTINGS.xml
Now BizTalk360 has been setup to pick that Profile to execute in it’s scheduled runs. Then, the next time you hit -> ‘Run BHM now‘, or BizTalk360 scheduled runs for BHM start, BizTalk360 will pick that profile and run the rules for it.
Hope you found this workaround helpful.
Thanks to our customer Joost for his help in the investigation.
Author: Rochelle Saldanha
Rochelle Saldanha is currently working in the Customer Support & Client Relationship Teams at BizTalk360. She loves travelling and watching movies. View all posts by Rochelle Saldanha
