Search

Red Hat Insights alerts now available for InterSystems IRIS InterSystems and Red Hat are working together to add IRIS-specific alerts to Red Hat Insights. Red Hat Insights is a service to predict and recommend remediations for system risks in Red Hat Enterprise Linux environments. Insights is free with nearly every RHEL, OpenShift, or Ansible subscription. You can learn more about Insights at Red Hat’s site. Swappiness Recommendation The first recommendation “Apply swappiness recommendation for better performance of InterSystems IRIS” has been activated. This recommendation checks the system memory and, if swap is used at a level above what we recommend, sends our recommendation for the ideal level of swappiness. Swappiness really only comes into play when under memory pressure. File buffer cache can be as large as it can fit in memory. Linux will only push out buffer cache when it needs to free pages for computation pages, so we recommend keeping swappiness at a low level. Upcoming Recommendations Red Hat is currently working on Insights recommendations for: Huge Pages settings Upgrading old installations Shmmax … and more If you have suggestions for further Red Hat Insights alerts for IRIS, please contact your account team or reach out to me directly. If you have questions or problems with Red Hat Insights, please contact Red Hat support. Hi Bob This is great! We already seeing some recommendations on redhat insight for one of our dev systems. The performance of InterSystems IRIS server may be impacted when Transparent Huge Pages is enabled Recommend running SystemPerformance 24-hour daily for InterSystems IRIS Map the Write Image Journaling (WIJ) disk for better performance of InterSystems IRIS Enable FreezeOnError for the integrity and recoverability of InterSystems IRIS database Apply swappiness recommendation for better performance of InterSystems IRIS Apply hugepages recommendation for better performance of InterSystems IRIS

Hello, I am quite new with InterSystems, SAM and Grafana. I am looking a way to get Log Files and Application Errors from InterSystems to SAM like in this post: https://community.intersystems.com/post/grafana-support-intersystems-iris. Is this plugin still under development or is there any other way to get those errors? By using SAM, I do not get those errors. Hi! May be with something like this https://community.intersystems.com/post/get-most-out-intersystems-sam-implement-your-own-alert-handler or with a custom setup of grafana/prometheus to send alert and not only visualize them. Be also advised that it's going to be deprecated https://community.intersystems.com/post/deprecation-intersystems-system-alerting-and-monitoring-sam Thank you! We heard about this that SAM is being deprecated and we were thinking of another solution.

In this article we are going to see how we can use the WhatsApp instant messaging service from InterSystems IRIS to send messages to different recipients. To do this we must create and configure an account in Meta and configure a Business Operation to send the messages we want. Let's look at each of these steps in more detail. Setting up an account on Meta This is possibly the most complicated point of the entire configuration, since we will have to configure a series of accounts until we can have the messaging functionality. Here you can read the official Meta documentation. First we will create a personal Meta account, thus giving our soul to Zuckerberg: The next step is the creation of a business account that will allow us to use WhatsApp services in our applications and that will be linked to our personal account: And then we have registered as developers from here. The next step was, once inside the developers account, to create an application: Following the instructions in the documentation, we select a type of application "Other": And a type of company application: In the last step we will assign the name of the application and link it with our business account to be able to use the WhatsApp functionalities. Finally, after this long and tedious process of creating several accounts, we will have our application ready to configure it with the WhatsApp functionality. You can see in the menu on the left that a new option called Whatsapp will be available once configured. By accessing the API Setup option you can see everything we need to connect to the messaging functionality. What we see on this screen: We have a test number from which the messages will be sent (From) to our recipients identified with an ID that we will later use to make calls to the API from our IRIS. We have defined a destination number (To) to which we will send our test messages (we must register it previously to accept receiving the messages). An Authentication Token has been generated with a validity of 24 hours. In our call we must send our data in JSON format as follows: { "messaging_product": "whatsapp", "to": "", "type": "template", "template": { "name": "hello_world", "language": { "code": "en_US" } } } For this example we are going to use a message template, although we could send any text. As you can also see, all we need is to make a POST HTTP call to the URL defined in the example: https://graph.facebook.com/{{Version}}/{PhoneID}/messages For our example we are going to create 3 different templates, so we can see how we could configure different messages. We have accessed this option from the link shown in step 2 of the API configuration. Well, now we have everything to start sending messages to our client. Let's proceed to configure our IRIS instance. Configuring IRIS For our example we are going to configure a small production that simulates the reception of HL7 ORU type messages with glucose level data for a certain patient. Depending on the level received, we will send the patient one message template or another. Business Service We will start by creating a Business Service to capture HL7 messaging from a file: And you will receive a message like this: MSH|^~\&|HIS|HULP|APP||20230330133551||ORU^R01|71186|P|2.5.1 PID|||1502935519^^^SERMAS^SN~184001^^^HULP^PI||CABEZUELA SANZ^PEDRO^^^||20160627|M|||PASEO JULIA ÁLVAREZ 395 3 E^^MADRID^MADRID^28909^SPAIN||6XXXXXXXX^PRN^^PEDRO.CABEZUELA@GMAIL.COM|||||||||||||||||N| PV1||O|||||0545128263Q^MARTÍNEZ FERNÁNDEZ^SUSANA^^MD^^^^|||||||1|||||173815|||||||||||||||||||||||||20230330133551|20230330133551 ORC|1|921099|131777||||^^^20231126133551||20230330133551|||0269410060K^URDANETA LÓPEZ^SUSANA^^MD^^^^|HULP||||||||HULP||||||||LAB OBR|1|921099|131777|LAB^LABORATORY^L||||||||||||0269410060K^URDANETA LÓPEZ^SUSANA^^MD^^^^|||||||||F OBX|1|NM|GLU^Glucosa|1|200|mg/dL|70-105|N|||F|||20231123124525||Lectura desde dispositivo de control|1| Business Process Once the message is received, we will send it to a Business Process that will transform the HL7 message into a type of message created by us and that will have the information that is relevant to us. As you can see it will be a very simple BPL: If we take a look at the transformation we will see how, depending on the glucose level data and the defined limits, we will indicate the type of message template that we are going to use: Business Operation This component will be responsible for sending the POST call to the WhatsApp server. To do this, we will define the EnsLib.HTTP.OutboundAdapter class as the component's adapter. Here you can see the class code: Class Whatsapp.BO.WhatsAppBO Extends Ens.BusinessOperation { Parameter ADAPTER = "EnsLib.HTTP.OutboundAdapter"; Parameter INVOCATION = "Queue"; Property Version As %String(MAXLEN = 5); Property PhoneNumberId As %String(MAXLEN = 15); Property Token As %String(MAXLEN = 1000); Parameter SETTINGS = "Version,PhoneNumberId,Token"; Method SendMessage(pRequest As Whatsapp.Message.WhatsAppRequest, Output pResponse As Whatsapp.Message.WhatsAppResponse) As %Status { set tSC=$$$OK set body = { "messaging_product": "whatsapp", "to": "", "type": "template", "template": { "name": "", "language": { "code": "en" } } } do body.%Set("to", pRequest.telephone) do body.template.%Set("name", pRequest.template) $$$TRACE(body.%ToJSON()) set request = ##class(%Net.HttpRequest).%New() set request.Authorization = "Bearer "_..Token set request.ContentType = "application/json" set request.Https = 1 set request.SSLConfiguration="default" set request.Location = "/"_..Version_"/"_..PhoneNumberId_"/messages" do request.EntityBody.Write(body.%ToJSON()) set status = ..Adapter.SendFormData(.response,"POST",request) $$$TRACE(response.StatusCode) set pResponse = ##class(Whatsapp.Message.WhatsAppResponse).%New() Quit tSC } XData MessageMap { <MapItems> <MapItem MessageType="Whatsapp.Message.WhatsAppRequest"> <Method>SendMessage</Method> </MapItem> </MapItems> } } We have defined 2 new parameters for the component in which we will indicate: The version of the API we will invoke. The identifier of the phone from which the message will be sent and which we have seen previously in the information of our Meta developers account application. The token that we will send in the header of our call (remember that it is valid for 24 hours). Since the required connection is HTTPS we have created a default SSL configuration: Well, we would have everything configured to launch our messaging tests. We will try sending 3 HL7 files, each one with a different glucose value for our patient: Value 80: which will generate a notification message indicating that our levels are normal. Value 110: in which it will warn us that we are exceeding the limit and will urge us to exercise to lower the levels. Value 200: in which it will alert us of our level and urge us to visit a medical center. Let's copy the messages to the defined folder: *Attention, if you want to test the example with the associated project you must configure the HL7 message with your phone number (search and replace the value 6XXXXXXXX in the example message) and modify the DTL to take into account the national prefix of your test phone . Let's see the result: Here we have our 3 messages received. Another new success from InterSystems IRIS! If you have any questions or comments, you can write them in the comments and I will be happy to answer you. 💡 This article is considered InterSystems Data Platform Best Practice.

Hi Developers, Watch the execution of a speed test for a heavy-ingestion use case on InterSystems IRIS: ⏯ InterSystems IRIS Speed Test: High-Volume Ingestion Try the full demo at https://github.com/intersystems-community/irisdemo-demo-htap Speakers: 🗣 @Amir.Samary, InterSystems Director, Solution Architecture 🗣 @Derek.Robinson, InterSystems Senior Online Course Developer, InterSystems Subscribe to InterSystems Developers YouTube and stay tuned!

Hey Developers, Learn about the use and design of the InterSystems FHIR Transformation Service and the InterSystems FHIR Server, and what to expect next: ⏯ FHIR in the Cloud: Understanding New InterSystems FHIR Server 🗣 @Mitchell.Tyson, Senior Cloud Engineer, InterSystems🗣 @Regilo.Souza, Product Owner - Cloud Strategy, InterSystems Subscribe to the InterSystems Developers YouTube channel and stay tuned!

Hi Community, Get a first look at InterSystems HealthShare's next-generation healthcare decision support and notification capabilities: ⏯ Introducing InterSystems HealthShare Extended Decision Support 🗣 Presenter: @Frank.Pandolfe, Clinical Product Specialist, InterSystems Subscribe to the InterSystems Developers YouTube channel and stay tuned!

(I wasn't able to find this in the docs or the Community, so feel free to point me to a reference that I missed) How can I determine the effective User and Group that will be used when an InterSystems IRIS process is doing file I/O on the file system for UNIX? Bonus points if you can tell me how to do it from within InterSystems IRIS as well as from the host OS. Thanks! From the OS side in AIX, I can see it in parameters.isc (example from a QA env I'm playing with) security_settings.iris_user: irisusr security_settings.iris_group: irisusr security_settings.manager_user: irisusr security_settings.manager_group: irisusr I do not recall how to see it in IRIS itself (or if it's even possible) but I remember wanting to figure out how to change the values after installation (due to someone goofing up an entry on a dev environment) and without a lot of effort, it is pretty difficult. Thank you @Craig.Regester for the response. Looking up that file in the docs (https://docs.intersystems.com/iris20201/csp/docbook/DocBook.UI.Page.cls?KEY=GCI_unixdist) it tells me that "For security reasons, the parameters.isc file is accessible only by the root user." I am pretty sure there is a way to tell what it is currently running as without needing that level of access. But it is good to know about this in the cases where root access is an option Interesting question. I didn't see anything for this in the class reference either. I'll be following this post. ##class(%SYS.ProcessQuery).GetOSUsername() You could try:ps -ax -o uname,cmd | grep "irisdb WD" | grep -v "grep"-ax will get all the running processes including ones that aren't running on a terminal, retrieve the username, and command that started the process. We then use grep to filter out the exact process we need. Thanks @Jean.Millette and @Timothy.Leavitt for the help with this! great way to do it within InterSystems IRIS - thanks Tim! Perfect!! Exactly what I was looking for - thank you @Sarmishta.Velury (and @Jean.Millette and @Timothy.Leavitt ) If you're doing file I/O, why not %File.GetOwnerGroup()? Or is this something you need to know before you open (or create) a file? @Jeffrey.Drumm - it is important to have this run from a process that is already running in the InterSystems IRIS instance (or something spun off from the SuperServer) so that it doesn't pick up your UNIX username if you enter via console. So being able to run an API like Tim's will work nicely as I can run it via the Output window from Studio: Understood ... but I'm curious as to how IRIS is getting my environment: w ##class(%SYSTEM.Util).GetEnviron("USER") jdrumm w ##class(%SYS.ProcessQuery).GetOSUsername() irisusr No idea, but I don't think it's tied to the IRIS name. When I am logged into Studio as bspead I see the following: [quote] w ##class(%SYSTEM.Util).GetEnviron("USER")rootw ##class(%SYS.ProcessQuery).GetOSUsername()cacheusr [/quote]

NOTE: we previously found an issue with the 2021.1.1.324.0 builds. The 2021.1.1 maintenance releases have been removed from the WRC and have been replaced with 2021.1.2.336.0 builds. 2021.1.2 containers will be available shortly. Two new sets of maintenance releases are now available: Caché 2018.1.6, Ensemble 2018.1.6, and HSAP 2018.1.6 InterSystems IRIS 2020.1.2, IRIS for Health 2020.1.2, and HealthShare Health Connect 2020.1.2 Installation kits and containers can be downloaded from the WRC Software Distribution site. Container images for the Enterprise Editions of InterSystems IRIS and IRIS for Health and all corresponding components are available from the InterSystems Container Registry. These are maintenance releases with many updates across a wide variety of areas. For information about the corrections in these releases, refer to the documentation for that version, which includes a Release Notes and Upgrade Checklist, and a Release Changes list, as well as the Class Reference and a full set of guides, references, tutorials, and articles. All documentation can be reached via docs.intersystems.com. Build numbers for these releases are shown in the table below: Version Product Build number 2018.1.6 Caché and Ensemble 2018.1.6.717.0 2018.1.6 Caché Evaluation 2018.1.6.717.0su 2018.1.6 HealthShare Health Connect (HSAP) 2018.1.6HS.9063.0 2020.1.2 InterSystems IRIS 2020.1.2.517.0 2020.1.2 IRIS for Health 2020.1.2.517.0 2020.1.2 HealthShare Health Connect 2020.1.2.517.0 2020.1.2 IRIS Studio 2021.1.2.517.0 2021.1.2 InterSystems IRIS 2021.1.2.336.0 2021.1.2 IRIS for Health 2021.1.2.336.0 2021.1.2 HealthShare Health Connect 2021.1.2.336.0 2021.1.2 IRIS Studio 2021.1.2.336.0 Container images InterSystems IRIS and IRIS for Health and all corresponding components are available from the InterSystems Container Registry using the following commands for the 2020.1.2 release: docker pull containers.intersystems.com/intersystems/iris:2020.1.2.517.0 docker pull containers.intersystems.com/intersystems/irishealth:2020.1.2.517.0 docker pull containers.intersystems.com/intersystems/iris-arm64:2020.1.2.517.0 docker pull containers.intersystems.com/intersystems/irishealth-arm64:2020.1.2.517.0 For a full list of the available images, please refer to the ICR documentation. Do I understand correctly that Caché Evaluation and IRIS Studio (full kit) are only available through WRC, which is not available to everyone, but only for supported customers? It seemed to me that these products are designed for everyone. By the way, the same goes for ODBC, JDBC and CSPGateway. @Vitaliy.Serdtsev - you could download the Community Edition of InterSystems IRIS from evaluation.InterSystems.com and just install Studio from that if you wish. Also, is there a reason you want the SingleUser version of Caché rather than the InterSystems IRIS Community Edition (which is freely available to everyone)? It's only 2 weeks ago when WRC said that 2018.1.5 will be last ever version of Cache and Ensemble! But it's really nice to have new version, hopefully it fixes known bugs. What you heard from the WRC was in error - 2018.1.6 has been planned for over a year. It definitely fixes known bugs (otherwise why release a maintenance release? ;) ) you could download the Community Edition of InterSystems IRIS and just install Studio from that if you wish That's exactly what I'm doing now. But agree, downloading hundreds of megabytes for the sake of Studio and drivers is inefficient. Also, is there a reason you want the SingleUser version of Caché rather than the InterSystems IRIS Community Edition IRIS does not interest me in this case. Over the years I have "tormented" WRC about the bugs I found in Caché (in some way I acted as a free beta tester), until the technical support ended. Some fixes at that time were included only in future versions of Caché , which I can no longer check. I would be interested to check out these fixes on the free version. Maybe there are other reasons why there is still a single-user version of Caché, especially only for those who already have a full-featured version, but for me they are not obvious. Hi Vitaliy - InterSystems IRIS has been on the market more than 3 years now and is the platform the general market is developing on. We've worked to make it easy to get InterSystems IRIS and the VS Code dev tooling, and are working to make independent components available easily as well. By far the vast majority of users that want Caché are existing customers - so you can get this easily through the WRC. @Vitaliy.Serdtsev - you make a fair point about downloading the full Eval kit just for a few pieces of it ... unfortunately that is the only distribution mechanism that I know of currently available for non-supported customers. Thank you for all the time you've spent over the years helping to find ways to make Caché more robust!! It sounds like you've been able to identify quite a few areas of improvement. There was significant effort put into streamlining things and solving known issues in the rebirth of Caché as InterSystems IRIS. You might find it interesting to download the Community Edition (IRIS version of the SU kit but much more powerful with fewer restrictions) and see if the bugs you reported are still present there or not. What do you think about that approach? I got clarification that we still create an SU version of Caché which is available in the WRC because some of our large partners/APs rely on it for people to learn on (which makes sense). Obviously we won't want new prospects playing with it, which is why it is no longer publicly available and instead we provide the InterSystems IRIS Community Edition. Hi Jeffrey. By far the vast majority of users that want Caché are existing customers - so you can get this easily through the WRC. I have indicated why I already can't get Caché now, even the SU version:<..>, until the technical support ended. <..> in future versions of Caché, which I can no longer check. You might find it interesting to download the Community Edition <..> and see if the bugs you reported are still present there or not. What do you think about that approach? <..> we still create an SU version of Caché <..> because some of our large partners/APs rely on it for people to learn on <..> I have already written that, as well as your large partners/APs who prefer to stay on Caché, IRIS does not interest me in this case. Why would I check something that I won't be using in the foreseeable future, even if there are fixes there? And yes, for the sake of hobby, I have been using IRIS CE for a long time.

Hey Community, Enjoy watching the new video on InterSystems Developers YouTube channel: ⏯ Creating Virtual Models with InterSystems IRIS Adaptive Analytics See how InterSystems IRIS Adaptive Analytics lets you quickly and easily create virtual data models, helping you make better business decisions. Adaptive Analytics includes built-in AI to improve query speed based on common requests by automatically creating data aggregates. Business users and analysts can access data using their business intelligence tool of choice. Stay tuned!

Hey Developers, New video is already on InterSystems Developers YouTube channel: ⏯ Creating Pivot Tables with InterSystems IRIS Business Intelligence Learn how to use the Analyzer tool from InterSystems IRIS Business Intelligence to create pivot tables for display on a dashboard. This video shows the central components of the Analyzer tool and demonstrates how to construct a pivot table. Enjoy and stay tuned!

Hey Community, New video is already on InterSystems Developers YouTube channel: ⏯ Embed Business Intelligence into your Applications with InterSystems IRIS Learn how InterSystems IRIS Business Intelligence works, and get an introduction to commonly used dashboards and user interfaces. InterSystems IRIS® Business Intelligence offers a complete set of tools for embedding business intelligence into your applications, making it easier to get insights into your data. Enjoy and stay tuned!

Hi Developers! Here're the technology bonuses for the InterSystems "Sustainability" Interoperability Contest 2022 that will give you extra points in the voting: Sustainability Topic Sustainability Dataset Business Process BPL or Business Rule DTL Usage Custom Interoperability Adapter Production EXtension(PEX) Python, Java, or .NET usage Embedded Python usage Docker container usage ZPM Package Deployment Online Demo Code Quality pass Article on Developer Community The second article on Developer Community Video on YouTube See the details below. Sustainability Solution - 5 points Collect the bonus of 5 points if your solution is related to solving the global challenge of Sustainability. Check the contest announcement for more details on the problem. Sustainability Dataset - 3 points each Get 3 bonus points per each sustainability dataset (for the first 3 datasets) submitted to Open Exchange and used in a solution. Dataset should be published as a ZPM package, check Datasets Contest for dataset publishing examples. Business Process BPL or Business Rules Usage - 3 points One of the key features of IRIS Interoperability Productions are business processes, which could be described by BPL (Business Process Language). Learn more about Business Processes in the documentation. Business Rules it's a no-code/low-code approach to manage the processing logic of the interoperability production. In InterSystems IRIS you can create a business rule which you can create visually or via the ObjectScript representation. You can collect the Business Process/Business Rule bonus if you create and use the business process or business rule in your interoperability production. Business Rule Example Learn more about Business Rules in the documentation. Custom Interoperability Adapter Usage - 2 points InterSystems Interoperability production can contain inbound or Outbound adapters which are being used to communicate with external systems by business services and operations of the production. You can use out-of-the-box adapters (like File, or Email) or develop your own. You get the bonus if you develop your own custom inbound or outbound adapter and use it in your production. Example of an adapter. Learn more on adapters. Production EXtension (PEX) Usage - 3 points PEX is a Python, Java, or .NET extension of Interoperability productions - see the documentation. You get this bonus if you use PEX with JAVA or .NET in your interoperability production. PEX Demo. Learn more on PEX in Documentation. Embedded Python - 3 points Use Embedded Python in your application and collect 3 extra points. You'll need at least InterSystems IRIS 2021.2 for it. Docker container usage - 2 points The application gets a 'Docker container' bonus if it uses InterSystems IRIS running in a docker container. Here is the simplest template to start from. ZPM Package deployment - 2 points You can collect the bonus if you build and publish the ZPM(ObjectScript Package Manager) package for your Full-Stack application so it could be deployed with: zpm "install your-multi-model-solution" command on IRIS with ZPM client installed. ZPM client. Documentation. Online Demo of your project - 2 pointsCollect 3 more bonus points if you provision your project to the cloud as an online demo. You can do it on your own or you can use this template - here is an Example. Here is the video on how to use it. Code quality pass with zero bugs - 1 point Include the code quality Github action for code static control and make it show 0 bugs for ObjectScript. Article on Developer Community - 2 points Post an article on Developer Community that describes the features of your project. Collect 2 points for each article. Translations to different languages work too. The Second article on Developer Community - 1 point You can collect one more bonus point for the second article or the translation regarding the application. The 3rd and more will not bring more points but the attention will all be yours. Video on YouTube - 3 points Make the Youtube video that demonstrates your product in action and collect 3 bonus points per each. Example. The list of bonuses is subject to change. Stay tuned! Good luck with the competition! Sustainability Datasets bonus is introduced - 3 points for a dataset, up to 3 datasets per project.

Hi Community! Are you in Dubai on October 10-13? Join us at the Global DevSlam conference for developers with 15,000 participants expected in person!📍Let's meet here: Hall 9, Stand № H9-E30🌟 We will host the event: "The hands-on workshop on InterSystems IRIS Data Platform"Speaker: @Guillaume.Rongier7183, Sales Engineer at InterSystemsOctober 10, 2pm - 3:30pm Register here ❕We have free promo passes for our Community Members, partners, and customers. Please drop me a line if you are willing to attend! I will be there! Looking forward to meeting everyone! me too! ;) I'll be there! Thanks all, now I'm feeling pressured ;)

Hey Developers, Join us as we share lessons learned from standing up the initial InterSystems cloud offerings. We'll cover the challenges of standing up a SaaS and how to meet them: ⏯ Running InterSystems IRIS Workloads in the Cloud: Lessons Learned 🗣 Presenter: @Eduard.Lebedyuk, Sales Engineer, InterSystems Stay tuned for the latest videos on InterSystems Developer YouTube!

Hi Community, We're pleased to invite you to the upcoming webinar in Spanish called "SAM: Monitoring InterSystems IRIS with Grafana and Prometheus". Date & Time: June 15, 4:00 PM CEST Speaker: @Pierre-Yves.Duquesnoy, Sales Engineer, InterSystems Iberia The webinar is aimed at system administrators who want to monitor one or some InterSystems IRIS platforms and its applications at a glance. It is also aimed at DevOps who have to add application or interoperability metrics to the monitoring. SAM (System Alerting & Monitoring) is the perfect tool to monitor InterSystems IRIS data platforms. It offers an overall picture of the systems to be monitored, and facilitates alert management in any monitored systems. During the webinar, we'll show SAM architecture and its installation; and we'll start to monitor different InterSystems IRIS clusters. We'll also extend the existing metrics to monitor other application metrics. ➡️ Register today and enjoy!