All
Accepted answers
Andreas Dieckow · Jan 20, 2023 go to post

Mark, you can try it out by joining the Early Access Program. The PWS was provided for convenience only and can always be removed or replaced with a different web server. In the future IRIS will check if a local web server is present and can configure the instance during the installation to use that web server (IIS on Windows, Apache everywhere else). I am going to augment the primary post to include removal information. Hope this helps.

Andreas Dieckow · Jan 9, 2023 go to post

Enrico and I talked about this last year and he was able to verify that InterSystems addressed the issue, which will be available once we release the NoPWS adjustment.

Andreas Dieckow · Dec 20, 2022 go to post

I think that installing a web server is not more complex than installing and configuring VSCode. If an Apache (or IIS on Windows) instance is installed prior to the installation of InterSystems IRIS the IRIS installer will offer to configure that web server. From here on forward it is the same as before. 

Andreas Dieckow · Dec 20, 2022 go to post

InterSystems intentionally continues to install a web server with the Community Edition. There are no plans to remove it.

Andreas Dieckow · Aug 9, 2022 go to post

About a method to determine connection use with the Community Edition: I am going to look into this, Dmitry. 

Andreas Dieckow · Aug 9, 2022 go to post

Community Edition: Connection and Core increase

 

The Community Edition is free, and the defined limits are making this possible. The community Edition is using the core-based license model (as opposed to a user-based license model). Core based licenses are not counting users and therefor do not enforce a maximum number of users. To maintain the free nature of the Community Edition InterSystems initially specified the following restrictions:

 

Max Number of concurrent connections:      5

Max Number of Cores:                                  8

Max Size of all databases:                            20GB (which includes system databases)

 

The Community Edition is a combination of a core-based and a single-user license. The single-user license is restricted to 5 concurrent connections.

 

InterSystems is in the process of increasing the limits to:

 

Max Number of concurrent connections:      8

Max Number of Cores:                                  20

Max Size of all databases:                            20GB (which includes system databases)

 

We will announce availability soon with 2022.2 as the target.

 

Community Edition: Licensing

 

InterSystems licenses are defined in the Terms and Conditions. The Terms and Conditions specify what the capabilities and the limitations for each license type are.

The license key applies limits of how the product can be used technically, but that is not the license (which is always defined by the Terms and Conditions). Not everything can be enforced as desired and sometimes historic reasons enforce higher values that today’s Terms and Conditions specify.

 

For regular user-based IRIS licenses, a license unit allows for multiple connections.  The technical maximum for concurrent connections per license unit is currently 25, but the Terms and Conditions set that limit to 12, which is the maximum number an application is allowed to use by default.

Andreas Dieckow · Oct 29, 2021 go to post

Standard kits have been posted on the WRC. Version 2021.1 Build 215.3 for all platforms that the Community Edition supports. These kits have a build-in key and will not require the keys we posted.

Andreas Dieckow · Oct 29, 2021 go to post

The new keys are in the process of getting posted on the WRC. I will update here once they are available.

Andreas Dieckow · Jun 23, 2021 go to post

The advisory will be updated shortly and no longer list Caché Server Pages. Caché Server Pages are fully supported on InterSystems IRIS and C/E.

Andreas Dieckow · Jun 17, 2021 go to post

InterSystems will provide a list for both categories in a couple of weeks. We wanted to get the advisory out first. 

Andreas Dieckow · Nov 1, 2019 go to post

I am confused. The link above is for the IRIS for Health Community Edition. I would expect you get the IRIS for Health image. Please elaborate

Andreas Dieckow · Oct 30, 2019 go to post

Community kits (preview) for InterSystems IRIS and InterSystems IRIS for Health are now available from the Docker hub.

docker pull store/intersystems/iris-community:2019.4.0.379.0

docker pull store/intersystems/irishealth-community:2019.4.0.379.0
Andreas Dieckow · Oct 15, 2019 go to post

We will post container kits here as well. Those are released versions and not previews, that can be used for Development, but not for deployments.

Andreas Dieckow · Jul 18, 2019 go to post

No, the focus of this conversion is to enable existing C/E customers to move to InterSystems IRIS.

Andreas Dieckow · Jul 1, 2019 go to post

I think the link is not wrong, but stops at the directory above the components folder. Your link if our course on click faster ;)

Andreas Dieckow · Mar 15, 2019 go to post

I updated the original statement to include that with Caché and Ensemble 2018.1.2 we added support for two new platforms:

Ubuntu 18.04

Windows Server 2019.1

Andreas Dieckow · Feb 26, 2019 go to post

InterSystems has completed the verification process for running our products on Windows Server 2019.

  • InterSystems IRIS is now supported with 2019.1 and later
  • Caché and Ensemble are now supported with version 2017.2 and later

InterSystems found no issues and existing kits are supported.

Andreas Dieckow · Feb 5, 2019 go to post

We currently anticipate that this version will be supported on Windows Server 2019, but we will have to wait for the conclusion of our verification process to be sure.

Andreas Dieckow · Jan 7, 2019 go to post

InterSystems is finishing up some additional tasks for InterSystems IRIS Studio. It will be available as a separate download and I will make an announcement here when it is available.

Andreas Dieckow · Jul 16, 2018 go to post

Thanks for all your questions and comments.    A bit more of an explanation:

 

    We’re reviewing our plans beyond Atelier 1.3 in order to radically improve the developer experience with InterSystems IRIS Data Platform. 

    We welcome your ideas and feedback, and invite private communication to ensure that our plans are sound.  

 

    In the meantime:

·        If you are using Studio and happy with it, keep using it.   We are maintaining it indefinitely and are happy that there are so many active developers and that the community has expert advice as well as add-on tools that work with Studio.

·        If you are using Atelier and happy with it, keep using it, and look forward to version 1.3.   We are also maintaining it indefinitely.  We've reached a milestone and have many users that are productive and effective with Atelier, including combining it with other Eclipse plug-ins.   

·        If you are starting work with a new development group, use Atelier.   Eclipse is familiar to millions of developers, and Atelier is more than sufficient to get the job done.  Consult with us on these projects as you get going, because there are some areas such as Ensemble productions where developers may want to use Studio or other tools along with Atelier.