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.
I'm exploring using installation manifests to deploy Ensemble configuration changes. I noticed that the documentation uses a macro within an "Error" tag.
<Error Status="$$$NamespaceDoesNotExist">
So I thought this would also be possible with "Var" tags, "If" tags, etc. For example:
I just deployed my production from test to acceptance but I found that the deployment misses some Soap Webclient classes which are used by my business operation components. I have used the management portal to create the deployment (i.e. production settings -> Export) and I expected that all classes used by the production were automatically included. Apparantly, that is not the case. Is this default behaviour for Ensemble? And can I somehow force Ensemble to automatically include these classes?
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.
The Idea is to have 1 file that customer can download and run. For now I realize that whole intersysytems developer kit that includes Studio, terminal acts as runtime environment (Like Java has JDK).
Is it possible to wrap my project to 1 archive (Back to Java example .war or .jar) and run it on some application server (like Tomcat) without Studio etc..?
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.
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"
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)
I am running into an error trying to send an Alert Email to test the functionality of IRIS HealthShare Health Connect 2022.1 compared to Cache HealthShare Health Connect 2018.1.3. I was trying to send an Alert email, when I am getting the following error on my EMailAlert operation which is using EnsLib.EMail.OutboundAdpater.
ERROR <Ens>ErrException: <UNDEFINED>FText+4 ^%occMessages *msg -- logged as '-' number - @''
Looking for advice on best practise (or at least reasonable approaches) for handling the Production class when utilising source control. (And perhaps wider advice around deployment.)
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?
Hello! I just had a quick question for anyone out there with more experience on deploying Ensemble productions.
I'm currently trying to export my Ensemble production WITH the Business Partners so I don't have to rebuild or add to that table after I import my Ensemble Production. I know that this is a small thing and doesn't actually affect anything in the production in terms of performance, but I like to have it for better documentation.
In the settings of the IRIS web application configuration page there is an option "Redirect empty path" which allows a user to access REST endpoint URL without trailing slash, eg. /csp/api/rest instead of /csp/api/rest/. How could I change this option declaratively in my ZPM manifest?
We have some custom tools that do project based deployment from environment to environment. In VS Code, we're struggling to find the best way to export PRJ files that contain the contents of a project the way we were able to in Studio. We can edit existing projects, and in server side editing we can create projects, but we can't seem to extract the project files (Not the classes, the wrapper) to store in our source control solution for deployment purposes.