The Amazon Web Services (AWS) Cloud provides a broad set of infrastructure services, such as compute resources, storage options, and networking that are delivered as a utility: on-demand, available in seconds, with pay-as-you-go pricing. New services can be provisioned quickly, without upfront capital expense. This allows enterprises, start-ups, small and medium-sized businesses, and customers in the public sector to access the building blocks they need to respond quickly to changing business requirements.
This post provides useful links and an overview of best practice configuration for low latency storage IO by creating LVM Physical Extent (PE) stripes for database disks on InterSystems Data Platforms; InterSystems IRIS, Caché, and Ensemble.
Google Cloud Platform (GCP) provides a feature rich environment for Infrastructure-as-a-Service (IaaS) as a cloud offering fully capable of supporting all of InterSystems products including the latest InterSystems IRIS Data Platform. Care must be taken, as with any platform or deployment model, to ensure all aspects of an environment are considered such as performance, availability, operations, and management procedures. Specifics of each of those areas will be covered in this article.
InterSystems is pleased to announce a new Developer Download site providing full kit versions of InterSystems IRIS Community Edition and InterSystems IRIS for Health Community Edition. These are available free of charge for application development use.
InterSystems is currently verifying InterSystems IRIS 2019.1 with Windows Server 2019. This work is scheduled to complete by the end of January 2019. In the second half of this month InterSystems will add Caché/Ensemble 2018.1.2 to be verified on this platform.
As we get closer to the completion of those tasks, I will update this post with information on release dates, and which products and version will support Windows Server 2019.
Starting with 2017.1, InterSystems is adding Ubuntu (64-bit) as a third linux server platform. Prior to 2017.1 Ubuntu was already available as a development platform and customers could use InterSystems distributions build for SUSE to run on Ubuntu. As a result there are a few license key implications for 64-bit linux versions starting with Caché and Ensemble 2017.1:
a) Customers using RedHat will observe no changes
b) Customers using InterSystems products(1) for SUSE on SUSE will need new license keys (no charge)
Welcome to the very first Supported Platforms Update! We often get questions about recent and upcoming changes to the list of platforms and frameworks that are supported by the InterSystems IRIS data platform. This update aims to share recent changes as well as our best current knowledge on upcoming changes, but predicting the future is tricky business and this shouldn’t be considered a committed roadmap.
We’re planning to publish this kind of update approximately every 3 months and then re-evaluate in a year. If you find this update useful, let us know! We’d also appreciate suggestions for how to make it better.
AWS has officially released their second-generation Arm-based Graviton2 processors and associated Amazon EC2 M6g instance type, which boasts up to 40% better price performance over current generation Intel Xeon based M5 instances.
A few months ago, InterSystems participated in the M6g preview program, and we ran a few benchmarks with InterSystems IRIS that showed compelling results. This led us to support ARM64 architectures for the first time.
InterSystems has performed various system and application benchmarks to determine the potential performance impact after the corrections for Meltdown have been applied.
I try to open an existing log file and append to it. In Windows I use Open file:(NRW):1. I would expect it to append to the file, but each time I execute the code I get only the new entries, the prior file content is lost.
What is the proper syntax top open a file in "Append" mode?
I will deploy this code in Linux. Is there a different syntax to open a file in Linux versus Windows?
As previously announced, 2017.1 on VSI OpenVMS 8.4-1H1 is the final major version of Caché and Ensemble. 2017.1 will not be available for VSI OpenVMS versions beyond 8.4-1H1.
Project related quality assurance efforts have revealed a number of concerns for the current release of 2017.1.0 and 2017.1.1 on all OpenVMS platforms. In certain situations, the impact can be severe.
We will start from the examples that we faced as Data Science practice at InterSystems:
A “high-load” customer portal is integrated with an online recommendation system. The plan is to reconfigure promo campaigns at the level of the entire retail network (we will assume that instead of a “flat” promo campaign master there will be used a “segment-tactic” matrix). What will happen to the recommender mechanisms? What will happen to data feeds and updates into the recommender mechanisms (the volume of input data having increased 25000 times)? What will happen to recommendation rule generation setup (the need to reduce 1000 times the recommendation rule filtering threshold due to a thousandfold increase of the volume and “assortment” of the rules generated)?
An equipment health monitoring system uses “manual” data sample feeds. Now it is connected to a SCADA system that transmits thousands of process parameter readings each second. What will happen to the monitoring system (will it be able to handle equipment health monitoring on a second-by-second basis)? What will happen once the input data receives a new bloc of several hundreds of columns with data sensor readings recently implemented in the SCADA system (will it be necessary, and for how long, to shut down the monitoring system to integrate the new sensor data in the analysis)?
A complex of AI/ML mechanisms (recommendation, monitoring, forecasting) depend on each other’s results. How many man-hours will it take every month to adapt those AI/ML mechanisms’ functioning to changes in the input data? What is the overall “delay” in supporting business decision making by the AI/ML mechanisms (the refresh frequency of supporting information against the feed frequency of new input data)?
We are in the process of using Ensemble for HL7 translations, and wanted to know is it better to use it on Linux Server or Windows Server? We are mostly a Windows shop but just wanted to make sure there is nothing we will be missing out using the Windows application.
What are the best steps for troubleshooting printing to a Windows printer from Cache. The printer has been configured in the Windows Printer Manager and has been able to print a test page (from the windows print manager).
The device has been configured in Cache -> Sys Admin -> Config -> Device Settings -> Devices with properly formatted |PRN|printer device name and "W" for open parameters and 101 for Alias.
Starting with 2017.1, InterSystems has moved macOS from being a server platform to a development platform. 2017.1 will only support macOS 10.12 and will no longer be available as dmg kits.
Verification of macOS 10.12 has not been completed at this time and Field Test kits for this platform are not yet available.
Is there a recommended way to deal with the unattended reboot that happens when Windows Updates are applied? These reboots cause issues with running Ensemble produtions.
Beginning with the next release after 2017.1, InterSystems products will no longer be offered on macOS (OS X) as a Server platform. This platform has been re-classified and will be available as a Development platform in future releases.
Products: Caché, Ensemble
Expected Availability: next major release after 2017.1
With the recent release of macOS 10.15, Apple has tightened its control mechanism, called Gatekeeper, so that it now requires executables to be notarized. InterSystems products are not currently supported for use on macOS 10.15 and the executables have not been notarized. (As a reminder, InterSystems products are supported on macOS as a development platform only.)
By views
