
In July, the release of the integration platform InterSystems Ensemble 2015.2. In this article, an overview of the major improvements 2015.2 and 2015.1.
The main thing: support of push-notifications for iOS and Google-devices, optimization of the database architecture for Ensemble products, optimization of "pass-through" (pass-through inproc) operations.
Ensemble 2015.1 supports push notifications for mobile devices. This allows Ensemble products to send iOS and Android device notifications. When developing an Ensemble solution, you do not have to worry about how many devices will receive notifications and what OS they have. Implemented support for the following protocols:
- iOS Push Notifications (APNS)
- Google Cloud Messaging (GCM).
To use will need:
')
- EnsLib.PushNotifications.AppService is a business service that receives notifications from Caché code executed outside of Ensemble products. Usually this service sends all notifications to Identity Manager.
- EnsLib.PushNotifications.IdentityManager is an Ensemble business process package that supports a table of user, application, and associated device mappings . Identity Manager allows you to send a message to the user without worrying about the number and types of user devices. Identity Manager receives messages from other components of Ensemble products and, in typical scenarios, sends them to the router for further parsing and sending to business recipients via GCM and APNS. These business transactions are configured appropriately to work with the required SSL certificates.
- EnsLib.PushNotifications.APNS.Operation is a business operation that sends a notification to the iOS Push Notifications server. For a business operation to work, you need to write an implementation of the% Net.PushNotifications.APNS class. For each iOS application, a special SSL certificate is required. A business transaction supports connecting to this server using this certificate.
- EnsLib.PushNotifications.GCM.Operation is a business operation for sending push notifications to the Google Cloud Messaging server. To run a business transaction, you need to write an implementation of% Net.PushNotifications.GCM.
Details how everything works can be read
here .
Improved data storage for Ensemble areas
In this release, there are some changes in the database architecture for the Ensemble product area.
First, separate databases for code and data appeared: for the code, a special PRODUCTION_SECONDARY database appears. This simplifies upgrading versions and makes it more logical to deliver and support Ensemble solutions. Of course, in the past it was possible to divide the database into a code and data base, but now this is done automatically and is the preferred scenario.
Secondly, each product now has its own temporary database PRODUCTION_TEMP - an analogue of CACHETEMP. This simplifies the management with temporary bases “if something went wrong” - for example, you can delete the temporary production base and not worry and not bother all other products that used to use the same CACHETEMP together. When upgrading Ensemble products will automatically begin to use their own temporary base instead of CACHETEMP.
Details
Optimization of "pass-through" (Pass-through) operations
Pass-through operations (Generic InProc Operations) are those that do not need additional processing logic and can be immediately redirected from inbound business services to outgoing business operations. In the new version for such "through" calls you can not generate stored messages, which significantly improves performance (as well as complicates debugging). End-to-end operations are implemented using the following classes: EnsLib.HTTP.GenericOperationInProc, EnsLib.REST.GenericOperationInProc, EnsLib.SOAP.GenericOperationInProc.
More details .
Java stateless calls
Ensemble 2015.1 supports stateless calls to Java, which helps reduce losses on connection creation and support.
More details .
Ensemble monitoring enhancements
In 2015.1, there were improvements in Enteriprise product monitoring and monitoring. Enterprise monitoring now shows the status of products executed in different areas and different Ensemble servers. You can watch:
- processing status of message queues relative to specified criteria;
- status histograms;
- Additional Information.
Read more here .
Filtering and sorting of product components appeared in the
monitoring of products. About these and other improvements read the full version of Ensemble Release Notes
2015.1 and
2015.2 .
Thank you for your attention, we are ready to answer your questions.