New post

Find

Article
· Oct 21, 2015 1m read

Strategies For Rapid Development of New Applications

InterSystems encourages the adoption of a flexible, practical approach to application development, rather than strict adherence to one of the prevalent development theories. This paper offers advice based upon our experience. However needs, attitudes, and styles vary; we recommend that each programmer choose the development approach that works best for them. Caché supports a wide range of development methodologies, not just those recommended here.

Discussion (0)0
Log in or sign up to continue
Article
· Oct 21, 2015 2m read

Advancing SOA with an Event-Driven Architecture

Executive Overview

In most organizations, events drive action. In financial services, for example, a stock dipping below a threshold price may trigger a sell order. In manufacturing, production may start when an order is received. In healthcare, an unusual increase in the number of patients registering in an emergency room could signal the start of a disease outbreak, calling for action on the part of medical staff and public health officials.

In all of these cases, a business process is started, stopped, or modified based on an event or series of events. The ability to realistically model event processing in software is a crucial capability for organizations that want to become more responsive to their customers and partners, and for achieving greater operational efficiency.

Service-oriented architecture (SOA) is a start in this direction. SOA delivers greater speed and flexibility for IT organizations that need to respond to changing business requirements. It also enables easier reuse of applications and data in multiple business processes, and greater accessibility to this information for users. And through reuse SOA helps free developers to complete more projects, reduce IT backlogs, and deliver additional value to the business. But without event-processing capabilities, an organization with service-oriented systems remains bound by the same limits as before - it can respond to a business event only as fast as its employees can discover the event, determine a course of action, and allocate resources to respond.

Adding event processing to an SOA, through an event-driven architecture (EDA), can take your organization beyond these limits. It will give your information systems the ability to sense and respond to events rapidly, either through an automated process or human interaction.

This white paper explains how InterSystems Ensemble enables you to create advanced SOA systems that include EDA, making it easier to respond quickly to significant business events, and giving you a competitive advantage.

1 Comment
Discussion (1)0
Log in or sign up to continue
Article
· Oct 21, 2015 2m read

Healthcare IT Breakthrough: Evolving to Advanced Integration Technology

A business case for the transition from eGate to InterSystems EnsembleÆ From interface engine to integration platform Healthcare IT is evolving so rapidly that the term "HL7 interface engine" may soon become extinct. Forces driving this evolution include:

  • Government and markets pushing hospitals and integrated delivery networks (IDNs) toward broad-based health information sharing, within and between organizations
  • Clinical and administrative staffs needing more information, faster, to improve patient care and control costs
  • The need for real-time business intelligence capability to measure progress toward goals, whether Meaningful Use objectives or the organization's own patient care, safety, and profitability targets

Legacy interface engines, such as eGate, simply do not have the architecture or capabilities needed to adapt to these forces. Instead, healthcare IT organizations are turning to a new type of integration and development platform. The platform must be a world-class HL7 interface engine. But it also must support a range of other data interchange and messaging standards (such as XML, X12, and SOAP) and provide rapid development of connections to data sources and applications that don't "speak" HL7. The integration platform should be a central resource that stores all the messages that pass through it for concurrent or later analysis by business intelligence applications. And it must be ready to support new types of integration and process automation as you bring them into your IT infrastructure. This includes service- oriented architecture (SOA), event-driven architecture (EDA), business process management, and adaptable workflow. The limitations of legacy interface engines in meeting these new requirements make the need to replace them increasingly urgent. Using examples from six healthcare organizations, this document presents a business case for replacing interface engines, like eGate, with the advanced capabilities of the InterSystems Ensemble rapid integration and development platform.

Discussion (0)0
Log in or sign up to continue
Article
· Oct 21, 2015 2m read

InterSystems Caché: Database Mirroring: A Technical Overview

Providing a reliable infrastructure for rapid, unattended, automated failover

Technology Overview

Traditional availability and replication solutions often require substantial capital investments in infrastructure, deployment, configuration, software licensing, and planning. Caché Database Mirroring (Mirroring) is designed to provide an economical solution for rapid, reliable, robust, automatic failover between two Caché systems, making mirroring the ideal automatic failover high-availability solution for the enterprise.

In addition to providing an availability solution for unplanned downtime, mirroring offers the flexibility to incorporate certain planned downtimes on a particular Caché system while minimizing the overall SLA's for the organization. Combining InterSystems Enterprise Cache Protocol (ECP) application servers with mirroring provides an additional level of availability. Application servers allow processing to seamlessly continue on the new system once the failover is complete, thus greatly minimizing workflow and user disruption. Configuring the two mirror members in separate data centers offers additional redundancy and protection from catastrophic events.

Key Features and Benefits

  • Economical high availability solution with automatic failover for database systems
  • Redundant components minimize shared-resource related risks
  • Logical data replication minimizes risks of carry-forward physical corruption
  • Provides a solution for both planned and unplanned downtime
  • Provides business continuity benefits via a geographically dispersed disaster recovery configuration

Traditional availability solutions that rely on shared resources (such as shared disk) are often susceptible to a single point of failure with respect to that shared resource. Mirroring reduces that risk by maintaining independent components on the primary and backup mirror systems. Further, by utilizing logical data replication, mirroring reduces the potential risks associated with physical replication, such as out-of-order updates and carry-forward corruption, which are possible with other replication technologies such as SAN-based replication.

Finally, mirroring allows for a special Async Member, which can be configured to receive updates from multiple mirrors across the enterprise. This allows a single system to act as a comprehensive enterprise data store, enabling - through the use of InterSystems DeepSee - real-time business intelligence that uses enterprise-wide data. The async member can also be deployed in a Disaster Recovery model in which a single mirror can update up to six geographically-dispersed async members; this model provides a robust framework for distributed data replication, thus ensuring business continuity benefits to the organization. The async member can also be configured as a traditional reporting system so that application reporting can be offloaded from the main production system.

Discussion (0)0
Log in or sign up to continue
Article
· Oct 21, 2015 3m read

InterSystems Caché: Database Mirroring: An Executive Overview

Providing a reliable infrastructure for rapid, unattended, automated failover

Technology Overview

Traditional availability and replication solutions often require substantial capital investments in infrastructure, deployment, configuration, software licensing, and planning. Caché Database Mirroring (Mirroring) is designed to provide an economical solution for rapid, reliable, robust, automatic failover between two Caché systems, making mirroring the ideal automatic failover high-availability solution for the enterprise.

In addition to providing an availability solution for unplanned downtime, mirroring offers the flexibility to incorporate certain planned downtimes on a particular Caché system while minimizing the overall SLA's for the organization. Combining InterSystems Enterprise Cache Protocol (ECP) application servers with mirroring provides an additional level of availability. Application servers allow processing to seamlessly continue on the new system once the failover is complete, thus greatly minimizing workflow and user disruption. Configuring the two mirror members in separate data centers offers additional redundancy and protection from catastrophic events.

Key Features and Benefits

  • Economical high availability database solution with automatic failover
  • Redundant components minimize shared-resource related risks
  • Logical data replication minimizes risks of carry-forward physical corruption
  • Provides a solution for both planned and unplanned downtime
  • Provides business continuity benefits via a geographically dispersed disaster recovery configuration
  • Provides Business Intelligence and reporting benefits via a centralized Enterprise Data Warehouse configuration

Traditional availability solutions that rely on shared resources (such as shared disk) are often susceptible to a single point of failure with respect to that shared resource. Mirroring reduces that risk by maintaining independent components on the primary and backup mirror systems. Further, by utilizing logical data replication, mirroring reduces the potential risks associated with physical replication, such as out-of-order updates and carry-forward corruption, which are possible with other replication technologies such as SAN-based replication.

Finally, mirroring allows for a special Async Member, which can be configured to receive updates from multiple mirrors across the enterprise. This allows a single system to act as a comprehensive enterprise data store, enabling - through the use of InterSystems DeepSee - real-time business intelligence that uses enterprise-wide data. The async member can also be deployed in a Disaster Recovery model in which a single mirror can update up to six geographically-dispersed async members; this model provides a robust framework for distributed data replication, thus ensuring business continuity benefits to the organization. The async member can also be configured as a traditional reporting system so that application reporting can be offloaded from the main production system.

Discussion (0)0
Log in or sign up to continue