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.
Does anyone have experience using SCCM or any other enterprise application management tool to deploy updates to a thick client (internally developed standalone app) across the enterprise? I have a client that is attempting to get this working for their customer and running into some trouble. If you have any knowledge or experience you can share it would be greatly appreciated.
I have read some MS Technet pages that appear to indicate this is possible
If you're deploying to more than one environment/region/cloud/customer, you will inevitably encounter the issue of configuration management.
While all (or just several) of your deployments can share the same source code, some parts, such as configuration (settings, passwords) differ from deployment to deployment and must be managed somehow.
In this article, I will try to offer several tips on that topic. This article talks mainly about container deployments.
For those that, at some point, need to test what means that of ECP for horizontal escalability (computing power and/or users and processes concurrency), but they're lazy o have no much time to build the environment, configure the server nodes, etc..., I've just published in Open Exchange the app/sample OPNEx-ECP Deployment .
I love the frequent mentions of versioning the CPF merge files in Source control. One thing that is not yet clear to me is how this would work for rolling back a change:
I'm deploying IRIS for Health on a Google Cloud VM, and I note that the SuperServer port is 1971, rather than good old 1972. Is this as it's supposed to be? I can't see that it's documented anywhere.
Deploying InterSystems HealthShare code, supporting lookups and artifacts like ssl certs, keys etc is relatively straight forward using Gitlab Runners. Not only does this approach enable managing the code base and deploying with git type workflows, but it also lends to a speedy recovery and repeatable environments for some implementations.
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.
So I've got the IRIS AMI spun up in AWS EC2; it seems to be running fine.
I've added an EBS volume to it for persistent storage, and now I'm pondering how to make it actually do something useful.
What's the best way to do deploy code to this instance? I can think of a few ways to do it, but what's the least painful way? Push my code to an S3 bucket and figure out how to load it at system start? Github project?
Writing a script for the application deployment can be very interesting to ensure rapid deployment without forgetting anything.
config-api is a library to help developers to write configuration scripts based on a JSON document.
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
By update
Open Exchange app