
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Capability | Function | Use Case | Example |
Instance Data Replication (HLA) | Allows for the replication of data across multiple ServiceNow instances. | Used for high availability and disaster recovery scenarios, ensuring data consistency across geographically distributed instances. | A multinational corporation synchronizes critical incident data across its instances in different regions to maintain business continuity in case one instance fails. |
MetricBase | A time-series database within ServiceNow that stores and manages large volumes of numerical data points over time. | Ideal for tracking and analyzing trends, performance metrics, and operational statistics over time. | An IT team tracks the response times of their web services every minute to analyze trends and performance degradation over time. |
MID Server | Acts as a go-between for the ServiceNow instance and external systems, databases, or applications that are behind firewalls. | Enables secure data integration, orchestration, and discovery operations between ServiceNow and external resources. | A company uses a MID Server to securely connect its ServiceNow instance to an on-premises database for automated data retrieval and updates. |
Remote Tables | Allows ServiceNow to present data from an external source as if it were part of the local instance. | Useful for accessing and manipulating data from external databases without the need to import it into ServiceNow. | A business unit accesses real-time inventory data from a remote supplier's database directly within their ServiceNow instance using Remote Tables. |
Entity View Action Mapper | Provides a mapping interface for entity views, allowing users to define actions on those views. | Facilitates the creation of custom actions on entity views, such as creating, updating, or deleting records based on user interactions. | A service desk creates custom buttons on an entity view to allow technicians to quickly close or escalate tickets directly from a dashboard without navigating away. |
I have provided some more insights on how manageable and scalable these features are that can help us plan the implementations better. [1 (Low) to 5 (High)]
Capability | Manageability Rating | Scalability Rating | Notes |
Instance Data Replication (HLA) | 3 | 5 | Manageability can be complex due to the need for synchronization and conflict resolution across instances. However, it offers high scalability for disaster recovery and high availability. |
MetricBase | 4 | 5 | MetricBase is designed to handle large volumes of data with relative ease of management, and it scales well for time-series data analysis. |
MID Server | 4 | 4 | MID Servers are generally straightforward to set up and manage. They can be scaled by deploying additional MID Servers for load distribution and redundancy. |
Remote Tables | 3 | 4 | Remote Tables are easy to set up but can become complex depending on the external data source's schema. They scale well as they do not store data within ServiceNow. |
Entity View Action Mapper | 4 | 3 | This feature is user-friendly for defining actions on entity views, but scalability might be limited by the complexity of custom actions and the volume of data being manipulated. |
Additional information -
Manage instance data sources (servicenow.com)
- 855 Views
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.