Software deployment is all of the activities that make a software system available for use. The general deployment process consists of several interrelated activities with possible transitions between them.
We are seeing more and more customers being lured with latest infrastructure technologies, particularly Composable Infrastructure. Coming with all sorts of data center consolidations and costs savings.
Question is: are there any concerns for HealthShare/TrakCare being run on these platforms or things to look out for? Anyone out there, already on these platforms?
To be more specific this is HPe Synergy with 480 Compute blades booting as bare metal.
https://www.youtube.com/embed/-8XaMxsauio [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
I'm almost running out of disk space so I want to move 1 DB to a different hard drive. It's a rather simple but lengthy action during a shutdown of IRIS. But is this somehow possible under runtime in a stand-alone installation? I'm looking for kind of a "local drive failover"
ZPM-Registry – is the package registry for the ZPM package manager.
As you probably know, the ZPM package manager is configured by default to work with the public community registry https://pm.community.intersystems.com/, which currently has more than 150 packages published. You can install and configure your own registry for use in your organization.
Recently we released the updated version 0.1.3 of ObjectScript Package Manager (ZPM) which comes with the support of simplified ObjectScript sources folder structure.
What 'simplified' does mean?
Before 0.1.3 ZPM expected the following structure:
/src
---/cls - for ObjectScript classes
---/cls/package_name/class_name.cls
---/cls/package_name/class_name2.cls
---/mac - or Mac ObjectScript routines
---/mac/package_name/mac_routine.mac
---/mac/package_name/mac_routine2.mac
---/inc - for ObjectScript macro include files.
---/inc/package_name/include_file.inc
This small tutorial described how to „register“ the ADO.NET Database Provider (Driver) for InterSystems IRIS and InterSystems Caché on a Windows machine.
Before we start: Why need the ADO.NET Database Provider to be registered?
I have a need to create a custom deployment package for our production. I can't do a full deployment of the production so I need to create a custom deployment package that will add our new classes, business processes, rest end points and transforms. I would like for the production to add and configure the business services, process and operations as well.
Most CloudFormation articles are Linux-based (no wonder), but there seems to be a demand for automation for Windows as well. Based on this original article by Anton, I implemented an example of deploying a mirror cluster to Windows servers using CloudFormation.I also added a simple walk through.
The complete source code can be found here.
Update: 2021 March 1 I added a way to connect to Windows shell by public key authentication via a bastion host as a one-liner.
What do you think If I will say you, that very soon you will be able to connect to IRIS from the application written in Rust.
What is Rust
Rust is a multi-paradigm programming language designed for performance and safety, especially safe concurrency. Rust is syntactically similar to C++, but can guarantee memory safety by using a borrow checker to validate references. Rust achieves memory safety without garbage collection, and reference counting is optional. (c) Wikipedia
I am investigating creating builds from TravisCI, which will pull the source from github. This will also involve a code review process, pull request, etc.
It will be done in Multiple phases. The first one will not involve automated testing using TravisCI yet. It will only involve travisCI pulling the latest code from github and creating a release for testing(A deployment file in a format that can be loaded by Ensemble0)
Do you have a guide or tutorial with recommendations to configure IRIS to a production environment? The better strategies, recommended disk, memory and processing settings, etc?
I'm trying to build my project on a Linux machine using Docker.
In my development environment, I use Windows 10 Pro with Docker Desktop version 2.3.0.5. Everything works fine, and the docker-compose build runs flawlessly.
But, when I tried to run the same project in a Linux. Ubuntu 18.04.5 LTS (GNU/Linux 5.4.0-1025-azure x86_64), docker --version Docker version 19.03.6, build 369ce74a3c
I work on deploying IRIS inside Docker container. I really like %Installer class can automate many steps. I want to establish an ECP connection to a mirror database and then define a remote database on the application server. I have already seen we can create local database and namespace in %Installer. What code is needed to establish ECP connection?
The InterSystems IRIS offer many options to deploy digital services running in IRIS. Your option will depends if you use IaC (my preferred option) or no.
InterSystems supports use of the InterSystems IRIS Docker images it provides on Linux only. Rather than executing containers as native processes, as on Linux platforms, Docker for Windows creates a Linux VM running under Hyper-V, the Windows virtualizer, to host containers. These additional layers add complexity that prevents InterSystems from supporting Docker for Windows at this time.
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.
By update
Open Exchange app
