Past three months our team was completely busy in implementing some essential features for Atomic Scope. We were mainly focusing on making product production ready covering important end to end monitoring use cases in hybrid integration scenarios. With all the arduous work of our team, we managed to release this version just before integrate-2018 and got positive reviews from potential customers and partners. In this blog, I am going to explain briefly all the features we released in version 2.0 of atomic scope.
Monitoring and Notification of Failures
Monitoring is an essential part of any integration project. When you use Atomic Scopes exception handling blocks, an immediate notification will be sent when there are errors in business transactions. AtomicScope uses SMTP server configuration to send alerts in a form of an email to people who need to know about transaction issues. Below is the sample notification email.
User Access Control
In version 2.0 we brought in windows authentication for the users to be able to log in to atomic scope portal. Once the user is authenticated, role based user access policy controls the level of access a user has got on the work space and business processes.
Roles at workspace level
- Workspace User – User can access the business processes within a workspace
- Workspace Owner – User can make changes to the workspace like adding users/ deleting workspace etc.
Roles at Business Process Level
- User (Business Process) – User can access the business process and edit the business process to which they have access to.
- Owner (Business Process) – User will be able to edit, delete and add users to the business process.
- Reader (Business Process) – User can view the business process but won’t be able to make any changes.
Purging Policy
This feature brings the capability to configure the number of days you want to retain the data in atomic scope database. By default it is 30 days. however, you can change it by modifying the application settings as shown below.
Provision for De- Batch Correlation
Message de-batching is very common in integration scenarios. When a batch message is received into BizTalk environment de-batching can happen in receive pipeline or in orchestration.
Version 2.0 brings following abilities.
- Log the batch message into main activity
- Archive the batch message
- Link all the de-batched messages to their parent batch
- Allow de-batched messages to progress with their individual journey.
Dynamic transaction resolution
In Atomic Scope, to track activities in BizTalk pipeline we will have to specify the transaction name at runtime as shown below.
Consider a scenario where a single receive location receives different message types and each message type corresponds to a completely different transaction in a business process. For example, you can receive Orders and Delivery confirmation on a single receive location. Consider another scenario where you receive a batch of different transactions from a trading partner through a single receive location. In both the scenarios, configuring transaction name during design time will not work. We should have an option to dynamically find out the transaction name based on BizTalk message type. Dynamic Resolution Of Transaction feature, supports above scenarios by allowing the users to map message types with transaction names.
UI improvements
We always care about user experience. In this release we improved various aspects of it. We are excited to introduce a brand-new Business Process configuration page, as well as a tabbed view for searching the tracking results. You can learn more about UI improvements in this blog UI improvements.
Configuration based Tracking with Logic Apps
This feature enables you to configure the tracked and search properties for stages executing at Logic Apps, similar to what we had for BizTalk in version 1.0.
Online Documentation
It is really important for an enterprise grade software product to have its documentation accessible to its users. We are proud to be able to move all our documentation online at http://docs.atomicscope.com. The documentation is powered by our in-house product document360.io.
Summary
We built these features based on the feedback that we received from our partners and potential customers. There will be series of articles published explaining each of these features in detail. For more information, you can visit our documentation http://docs.atomicscope.com. If you want to have a demo of the product please write to us at support@atomicscope.com or visit our website http://atomicscope.wpengine.com
