#Ensemble

InterSystems will support this Operating System version with Caché and Ensemble 2016.1.

In some project, I found the need to use SMIME format https://www.ietf.org/rfc/rfc3851.txt, basically is an standard used to wrap a message together with its signature using a certificate (usually X509). Ensemble don't have a single class to do that but inside the Ensemble installation we have the openssl utility, so in this example I use the "openssl smime" command to sign or verify a message.

The example has two Business Process that able to sign or verify and in order to test I made a simple production.

Hope this helps

So calling this lookup manually from the console works as expected:

However, calling it from a method with some concatination to build the key is giving me problems:

I have a routing rule that processes messages from multiple customers. I would like to create some sort of flag or setting that I can toggle to indicate if a given customer is allowed to pass messages through the router. Should I use a registry entry, lookup table or something else? Which can be accessed from a routing rule and how?

Hi,

Does someone have experience with ISO-8385 transactions and Ensemble?

ISO-8385 is used for credit card transactions: https://en.wikipedia.org/wiki/ISO_8583

Thanks

I have had a few questions about the number of HL7 messages Ensemble can handle lately, so i thought i would draw people's attention to the benchmark report

https://community.intersystems.com/documentation/ensemble-and-healthshare-hl7v2-message-throughput-0

It describes the throughput of HL7 messages with realistic messages and routing.

Dave

Are you new to Ensemble? InterSystems provides several tools to learn the basics of Ensemble and get on your way to becoming an expert in the technology. Before installing Ensemble, take a look at the Ensemble Technology Overview and Getting Started with Ensemble in documentation. Respectively, these documents explain features and major components of Ensemble as well as how to install the software.

The Business Processing Language - for orchestration and long-running business processes.

Ensemble can orchestrate calls to external systems. Very often this is done to implement or automate a long-running business process - that is, real business processes where people interact with a series of different systems to complete complex tasks. BPL (the Business Processing Language) provides a graphical way to create these orchestrations.

Ensemble is based on message flow, and a data transformation is a way to convert from one message type to another. DTL (Data Transformation Language) adds a layer to this - it provides a graphical way to do the conversion. This is really helpful because most of the time, people with domain-specific knowledge may not have extensive coding skills. However, you always have the ability to do some coding, so if you need or want to, this is available.

DTL has several components: the data transformation engine, the language itself, and the DTL editor.

Introduction

This paper describes how Ensemble behaves after a system crash or similar uncontrolled shutdown or failover. Ensemble is normally configured to start processing messages automatically when the operating system restarts or when the system has failed over to a cluster member or mirror member. No manual intervention is required. But, in order for your system to robustly handle system failure and restart, you must understand how Ensemble handles these conditions and develop your productions using the rules and guidelines in this document.

Introduction

HL7 V2 message routing solutions often have hundreds of business services, processes and operations. Inevitably things will go wrong and you have to monitor the production to be able to react quickly and resolve any problems before they can become serious issues.

Ensemble includes some powerful alerting capabilities that can help, but if you aren't careful you will be inundated with alerts and your inbox more or less becomes a copy of the event log defeating the object of the exercise.

Introduction

Application integration at its simplest is often just one application sending a message to another to notify it of some change. Perhaps when a patient arrives at a hospital, the registration system will send a message to clinical systems so they have all demographic data ready to use. Of perhaps it is just a nightly file transfer from the sales system to the accounting system.

But modern application integration platforms or suites can do a lot more than this to help applications work together and add real value to the enterprise.

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: