It feels really good as long as things going fine, what if something goes wrong? What if we did some bulk operations and then we realize that something works weird because of that? Do we need to search for what made something messed up? So, wait
Don’t you think it’s good to have a feature that Audits our activity and can look back anytime if needed just to figure out what we have done so far?
Here comes, Governance Audit Feature to audit both operations and configuration activities from Biztalk360.
Security is the major concern for any software product., – Sometimes there may be a huge disruption in business due to some major operations that have been performed by someone accidentally. It’s important to audit those operations which help us to take necessary steps and identify who has done what.
Governance and Audit have the auditing capability for various features across Biztalk360., – For instance, let’s take Operations Section. It has the auditing capability for Applications, Service instances, ESB, Business Rule Composer, and much more. Also, there are auditing features to capture the operations performed while configuration in BizTalk360 under configuration activities.
Take a scenario where there are a set of normal users in team management also configured User Access Policy for the individual users. Later, there is some need to check the user access policy that is configured for each user, Of course, it will be a tedious thing to check the user access policy for each user in team management.
Just to make the process simple, BizTalk360 has User Access Policy Activities under configuration activities, where all the operations performed in team management can be audited with all the details of user access policy configuration.
The Alarm activities, will capture all the operations performed in alarm along with its configuration details, the operations such as creating an alarm, update, delete and import and export of alarm will also be captured.
For instance, there are a set of alarms that have been deleted in the BizTalk360 by a user and want to know the reason why they have been deleted. In Alarm activities, where all the operations can be captured along with the configuration details and the reason for the operation that has been mentioned while performing those operations, the activities will be captured.
Similarly, Configuration activities have Artifact mapping activities, License activities, Secure SQL query activities, and much more that can be audited
Governance and Audit have consolidated activities for both operation and configuration activities to audit all the operations performed across all features. Want to know more about Governance and audit? We suggest following BizTalk360 Activity Auditing
In addition to these, in Biztalk360 Version 10.1, we have added the auditing capability for another two features in the Operations section based on the customer feedback and business needs
So now, any operations that are performed in Tracking Manager and Logic Apps can be tracked and captured in operation activities under Governance and Audit.
In addition to these auditing functionalities, there are filters to sort through the data and routing will be done to the respective feature while clicking each audit activity.
Tracking is one of the important and key capabilities in the Biztalk server. It’s really important to know how things work and getting them tracked especially when it comes to a middleware product like the BizTalk server.
In BizTalk, while sending a message from receive port to send port, tracking helps us to monitor the health of the BizTalk implementation and to identify any bottlenecks.
So often there is a need to manage tracking for all the artifacts. It would be really helpful to have a feature that audits all the activities performed in Tracking Manager Feature in Biztalk360.
Let’s take a scenario where a message that passes from receive port to send port will be gone through various processing., -If there is a need to track message body and property in various points of the journey then tracking for each artifact of the application or can enable overall tracking of all the artifacts., – These activities will be audited in tracking manager activities. Since enabling the tracking for the artifacts would cause a performance impact on the BizTalk server, it would be helpful to keep an eye on the activities for enabling/disabling the tracking and which user has performed the same.
The following activities will be captured and audited for the tracking:
Global Tracking – By enable/disable Global tracking we can manage tracking interceptors of the entire BizTalk Server group
Overall Tracking – By enable/disable overall tracking for each artifact we can manage tracking for the respective artifact for the entire BizTalk Server group
Artifact Tracking based on Applications– Can manage tracking of artifacts for the particular application
Artifact Tracking- In BizTalk, there were various tracking points for each artifact. We can manage tracking for each tracking point of the artifact
In BizTalk360, user can manage the tracking of the deployed Business Rules
Business Rules have the tracking options such as
Operations performed over these tracking options will be audited
Azure Logic Apps play a vital role in an integration platform, It helps to automate many of the workflows you have in place at easiest,
For example, To organize workflow or to manipulate data in an enterprise you can use built in triggers and actions in Azure Logic Apps
Let’s take a scenario,
In a Logic App, if the user has twitter trigger which has some action to perform when new tweet is posted based on the keyword or hashtag, so that user can take and analyze the sentiments expressed in the tweet data
If any user performs operations over the Logic App such as disabling the logic app which causes disruption in workflow leads some actions undone also the respective logic app won’t get triggered further when the new tweet is posted with the mentioned keywords which may cause business impact
So, it’s important to track all the operations that are performed over the Logic Apps
The following activities will be captured and audited under the logic apps activities
Enable-Enabling a logic app or multiple logic apps can initialize the workflow of the logic apps once the trigger occurred
Disable-Disabling a logic app or multiple logic apps can affect workflow instance which stops service to create or to run new service instance further
Run Trigger – Can also Run trigger a Logic Apps or multiple logic apps from BizTalk360
Delete – Deleting a logic app or set of logic apps can make all the in-progress and pending runs to get cancelled
We have added these Auditing features in BizTalk360 V10.1, Do you think it will make your work easy and more productive? Want to upgrade your current BizTalk360 to V10.1? or new to BizTalk360?
We have a free trial for you! Try it out!
BizTalk360 will make you more productive, happy monitoring!