Search

Hi,this is a public announcement for the first release of Intersystems Cache Object-Relational Mapper in Python 3. Project's main repository is located at Github (healiseu/IntersystemsCacheORM).About the projectCacheORM module is an enhanced OOP porting of Intersystems Cache-Python binding. There are three classes implemented:CacheClient This is the super class of CachePython module. It wraps two functions from intersys.pythonbind module pythonbind3.connection() and pythonbind3.database().CacheQuery A subclass of CacheClient that wraps methods and adds extra functionality in intersys.pythonbind.databaseand intersys.pythonbind.query classesCacheClass A subclass of CacheClient, that wraps methods and adds extra functionality in intersys.pythonbind.databaseand intersys.pythonbind.object classesThe intersys.pythonbind package is a Python C extension that provides Python application with transparent connectivity to the objects stored in the Caché database.Source CodeThe project's code that is released to the public was originally written and used as a module of TRIADB project.Tests and DemosThere are two folders in this release:testCacheORM contains python jupyter notebook files that demonstrate CacheQuery and CacheClasstestCacheBinding are tests written for Intersystems Cache python bindingOne can simply compare tests with demos to appreciate the work in this project to leverage intersystems cache python binding. For example # Intersystems Cache Python binding for queries import intersys.pythonbind3 # Create a connection user="_SYSTEM"; password="123"; host = "localhost"; port = "1972"; url = host+"["+port+"]:SAMPLES" conn = intersys.pythonbind3.connection() # Connect Now to SAMPLES namespace conn.connect_now(url, user, password, None) # Create a database object samplesDB = intersys.pythonbind3.database(conn) # create a query object cq = intersys.pythonbind3.query(samplesDB) # prepare and execute query sql = "SELECT ID, Name, DOB, SSN FROM Sample.Person" cq.prepare(sql) cq.execute() # Fetch rows for x in range(0,10): print(cq.fetch([None])) Same code in only 4 lines using CacheORM python module from CacheORM import CacheQuery samples_query = CacheQuery(namespace='SAMPLES', username='_SYSTEM', password='SYS', dl=99) samples_query.execute_sql('SELECT ID, Name, DOB, SSN FROM Sample.Person') samples_query.print_records(10) You can view the output from this python Jupyter Notebook at my Microsoft Azure CacheORM library Another example, this time with Cache-Python Objects # Demo of Intersystems Cache Python binding with Samples namespace and Sample.Person class import intersys.pythonbind3 conn = intersys.pythonbind3.connection( ) conn.connect_now('localhost[1972]:SAMPLES', '_SYSTEM', '123', None) samplesDB = intersys.pythonbind3.database(conn) #%% Create a new instance of Sample.Person to be husband husband = samplesDB.create_new("Sample.Person", None) ssn1 = samplesDB.run_class_method("%Library.PopulateUtils","SSN",[]) dob1 = samplesDB.run_class_method("%Library.PopulateUtils","Date",[]) husband.set("Name","Hatzis, Athanassios I") husband.set("SSN",ssn1) husband.set("DOB",dob1) # Save husband husband.run_obj_method("%Save",[]) print ("Saved id: "+str(husband.run_obj_method("%Id",[]))) #%% Create a new instance of Sample.Person to be wife wife = samplesDB.create_new("Sample.Person", None); ssn2 = samplesDB.run_class_method("%Library.PopulateUtils","SSN",[]) dob2 = samplesDB.run_class_method("%Library.PopulateUtils","Date",[]) wife.set("Name","Kalamari, Panajota"); wife.set("SSN",ssn2) wife.set("DOB",dob2) # Save wife wife.set("Spouse",husband); wife.run_obj_method("%Save",[]); print ("Saved id: " + str(wife.run_obj_method("%Id",[]))) #%% Relate them husband.set("Spouse",wife); husband.run_obj_method("%Save",[]); wife.set("Spouse",husband); wife.run_obj_method("%Save",[]); # Open an instance of the Sample.Person object athanID=217 athanPerson = samplesDB.openid("Sample.Person",str(athanID),-1,-1) # Open another instance otherID=3 otherPerson = samplesDB.openid("Sample.Person",str(otherID),-1,-1) # Fetch some properties print ("ID: " + otherPerson.run_obj_method("%Id",[])) print ("Name: " + otherPerson.get("Name")) print ("SSN: " + otherPerson.get("SSN")) print ("DOB: " + str(otherPerson.get("DOB"))) print ("Age: " + str(othePerson.get("Age"))) Same code using CacheORM python module, i.e. object-relational mapping from CacheORM import CacheClass # Create an instance of PopulateUtils to call built-in CACHE class method populateUtils = CacheClass(namespace='%SYS', cachepackage='%Library', cacheclass='PopulateUtils', username='_SYSTEM', password='SYS') # Create CacheClass Instance husband = CacheClass(username='_SYSTEM', password='SYS', dl=99) # Create and populate a new CacheClass Object husband.new() husband.set_value("SSN",populateUtils.class_method("SSN")) husband.set_value("Name", "Hatzis, Athanassios I") husband.set_value("DOB", populateUtils.class_method("Date")) # Save husband husband.save() # Create another CacheClass object wife = CacheClass(username='_SYSTEM', password='SYS') wife.new() wife.set_value("SSN",populateUtils.class_method("SSN")) wife.set_value("Name", "Kalamari, Panajota") wife.set_value("DOB", populateUtils.class_method("Date")) wife.save() # Relate them wife.set_refobj("Spouse", person._cache_id) wife.save() husband.set_refobj("Spouse", female._cache_id) husband.save() # Get Object References person.get("Spouse").get("Name") female.get("Spouse").get("Name") # Open an existing object with id=3 and read cache properties person = CacheClass(username='_SYSTEM', password='SYS', objectID='3') print(f"ID:{person.id}\nSSN: {person.get('SSN')}\nName:{person.get('Name')}\nDateOfBirth:{person.get('DOB')}") You can view the output from this python Jupyter Notebook at my Microsoft Azure CacheORM library Cool staff, Athanassios!Caché queries demo doesn't work though: Thanks Evgeny, you cannot execute my jupyter notebooks on Azure cloud and I think you have to login first in order to view them. In any case my CacheORM module is dependent on intersys.pythonbind module. One has to install this first and verify that it works then start playing with my demos. I wrote guidelines about installation in Github README file.

BridgeWorks is pleased to announce a VDM, v9.1.0.1. This release includes the following updates: Updates Historical Linking is now based off connection profile name Saved Formatting is now based off connection profile name Tables and Fields column headers no longer hide based on connection type Bug Fixes Cross tab would not load data correctly in Finished Reports Viewer if it was in a report footer Fixed an issue where refreshing logs would not work correctly after viewing a SQL statement Views were not visible for available schemas on the connection wizard New Load Selected Connections Only load connections selected from a list

Hi Developers, The new video from Global summit 2019 is already on InterSystems Developers YouTube: ⏯ Intersystems IRIS Kubernetes Operator This video introduces the InterSystems IRIS Kubernetes operator, which enables InterSystems IRIS containers to function as "first-class citizens" of the Kubernetes ecosystem. We recommend that you be familiar with basic Kubernetes concepts: Introduction to Kubernetes Video Takeaway: You will understand and appreciate the value proposition of the InterSystems IRIS Kubernetes operator. Presenters: 🗣 @Luca.Ravazzolo, Product Manager, InterSystems🗣 @Steven.Lubars, InterSystems Software Developer Additional materials to this video you can find in this InterSystems Online Learning Course. Check out the Cloud Deployment Resource Guide. Enjoy watching this video! 👍🏼 HI Guys, Can you please post the link of prevision session that you mentioned in this video. I am still not sure how we will use Kubernetes with IRIS . It be great if you can put some light on that too ? Thanks Hi Neerav Adam, Are you looking for the Introduction to Kubernetes session? Does anyone know how to download this operator? I'm excited to start using it. Hi @Jonathan.Keam, I hope you found the answer back in Jan. If not head over to containers.intersystems.com HTH

I downloaded containers.intersystems.com/intersystems/healthshare_providerdirectory:2023.2 to evaluate, however when I try to run the container it keeps exiting. >docker run --name providerdirectory --user=irisowner --env=ISC_DATA_DIRECTORY=/intersystems/irisdata --runtime=runc -d containers.intersystems.com/intersystems/healthshare_providerdirectory:2023.2 I keep getting the following, and I am not sure why... 2024-01-17 20:36:20 [INFO] Executing command /home/irisowner/irissys/startISCAgent.sh 2188... 2024-01-17 20:36:20 [INFO] Writing status to file: /home/irisowner/irissys/iscagent.status 2024-01-17 20:36:20 Reading configuration from file: /home/irisowner/irissys/iscagent.conf 2024-01-17 20:36:20 ISCAgent[17]: Starting 2024-01-17 20:36:20 ISCAgent[18]: Starting ApplicationServer on *:2188 2024-01-17 20:36:20 [INFO] ...executed command /home/irisowner/irissys/startISCAgent.sh 2188 2024-01-17 20:36:20 [INFO] Starting InterSystems IRIS instance IRIS... 2024-01-17 20:36:20 [ERROR] iris: instance 'IRIS' not found 2024-01-17 20:36:20 [ERROR] Command "iris start IRIS quietly" exited with status 256 2024-01-17 20:36:20 [ERROR] See the above messages or /intersystems/irisdata/mgr/messages.log for more information 2024-01-17 20:36:20 [FATAL] Error starting InterSystems IRIS Can someone point me to the correct docker run command to get this to run? Thanks Scott Hi, I've got the same issue, I've started to container without running the IRIS on startup -u=false and found that there is only HSPD installed, so here is the command that worked for me: docker run -d --name providerdirectory -p 52773:52773 -p 1972:1972 -p 2187:2187 containers.intersystems.com/intersystems/healthshare_providerdirectory:2023.2 -i HSPD hth Eyal Thanks I got it running, but I am not sure what to do next. When I try to access HealthShare within the Management Portal, it is telling me the Service is Unavailable. I want to be able to see what the System can do.

Is there any chance to make available a arm64/aarch64 binary version for Caché ODBC Driver? Just like IRIS ftp://ftp.intersystems.com/pub/iris/odbc//2021/ODBC-2021.1.0.215.0-lnxrharm64.tar.gz As I am using docker, currently is not possible to build locally a new image using existing Caché ODBC Drivers on Mac M1. Do you still expect some echo?Or is the question meanwhile just out of date? @Robert.Cemper1003 I am waiting for that. Do you have any solution ? Caché will not get support for M1, and so, I think no reasons to wait for an ODBC driver for M1 too No, I have no solution.As all development on Caché (except serious bugfix) is frozen I wouldn't expect this to come.You may migrate your Caché to IRIS. Or use some other way (REST ?) for access.

Hey Developers, Are you joining us for the InterSystems Virtual Summit 2021? ⚡️ THE REGISTRATION IS NOW OPEN ⚡️ Innovations in Data - #VSummit21 At the second InterSystems Virtual Summit, learn how to make your organization thrive with healthy data, powerful analytics, and a smart data fabric powered by InterSystems technology. Hear from our experts, world-leading thought leaders, and InterSystems customers from around the globe. 🗓 Tuesday, October 26 - Friday, October 29 👉 Keynotes | Live Experience Labs | Focus Sessions On-demand | Free Registration Summit Schedule Day 1 (Tuesday, Oct.26)Keynote presentations by our InterSystems leadership team, thought leaders, and key customers. Day 2 (Wednesday, Oct. 27)Keynotes about Client Support and "What’s New and Next" presentations by product directors for InterSystems IRIS®, InterSystems IRIS for Health™, HealthShare®, and TrakCare®. Days 3 and 4 (Thursday, Oct. 28, and Friday, Oct. 29)Build your own schedule. Take this opportunity to view all the Focus Sessions on demand. You can also sign up for our Experience Labs. All on demand focus sessions are pre-recorded and will be available on day 2 starting at 2 PM ET. REGISTER FOR FREE TODAY. And see you at Virtual Summit 2021!

Hi, I'm a java developer,have integration package for springboot?(maven or gradle) This is also the question I want to submit. check https://openexchange.intersystems.com/package/springboot-iris-crud

Hello, I'm testing IRIS 2020.4 Preview with preview key. I've access to the management portal but I can't connect with Studio. This is my docker-command : docker run --name my-iris --detach --publish 9091:51773 --publish 9092:52773 --volume C:\Docker\iris_external:/external –-volume C:\Docker\iris_durable:/durable –-env ISC_DATA_DIRECTORY=/durable/irissys containers.intersystems.com/intersystems/iris:2020.4.0.524.0 --key /external/iris.key --password-file /external/password.txt I notice that Caché Direct is disabled by the license. Can someone help me out ? InterSystems have changed SuperServer port in a few latest builds, back to 1972. So, just replacing 51773 with 1972, should work. You can use docker inspect docker inspect containers.intersystems.com/intersystems/iris:2020.4.0.524.0 Will outputs something like this ..... "ExposedPorts": { "1972/tcp": {}, "2188/tcp": {}, "52773/tcp": {}, "53773/tcp": {}, "54773/tcp": {} }, ..... "Labels": { "com.intersystems.adhoc-info": "", "com.intersystems.platform-version": "2020.4.0.524.0", "com.intersystems.ports.default.arbiter": "2188", "com.intersystems.ports.default.license-server": "4002", "com.intersystems.ports.default.superserver": "1972", "com.intersystems.ports.default.webserver": "52773", "com.intersystems.ports.default.xdbc": "53773", "com.intersystems.product-name": "IRIS", "com.intersystems.product-platform": "dockerubuntux64", "com.intersystems.product-timestamp": "Thu Oct 22 2020 13:02:16 EDT", "com.intersystems.product-timestamp.iso8601": "2020-10-22T17:02:16Z", "maintainer": "InterSystems Worldwide Response Center <support@intersystems.com>", "org.opencontainers.image.created": "2020-10-22T19:32:32Z", "org.opencontainers.image.documentation": "https://docs.intersystems.com/", "org.opencontainers.image.title": "intersystems/iris", "org.opencontainers.image.vendor": "InterSystems", "org.opencontainers.image.version": "2020.4.0.524.0-0" } I've just left, only interesting lines in your case. Where you can find, which ports are declared as exposed in the image, and labels, which declares available ports in the image. Access directly to the label $ docker inspect containers.intersystems.com/intersystems/iris:2020.4.0.524.0 \ --format '{{ index .Config.Labels "com.intersystems.ports.default.superserver" }}' 1972 Thanks, I replaced 51773 with 1972 and now it works !

I am trying to install IAM in my local and I downloaded IAM-0.34-1-1.tar.gz and extracted. I went to the location where iam_image.tar is available and run below command in the command prompt. C:\ESB\HC\IAM-0.34-1-1.tar\IAM-0.34-1-1\IAM>docker load -i iam_image.tarunsupported os linux Getting unsupported os Linux issue. Kindly let me know if anyone had this issue. Thanks! On windows docker works in two different ways, as windows containers and linux containers. It looks like, you just should switch it to linux from Windows Thanks for reply @Dimtriy, I am new to Docker. I have below info on my machine about docker and looks it is using Windows container. Let me know if anything needs to be changed. C:\>docker versionClient: Docker Engine - Community Version: 19.03.8 API version: 1.40 Go version: go1.12.17 Git commit: afacb8b Built: Wed Mar 11 01:23:10 2020 OS/Arch: windows/amd64 Experimental: false Server: Docker Engine - Community Engine: Version: 19.03.8 API version: 1.40 (minimum version 1.24) Go version: go1.12.17 Git commit: afacb8b Built: Wed Mar 11 01:37:20 2020 OS/Arch: windows/amd64 Experimental: false As I said for server side it show linux for os/arch. You should find the switcher in context menu in tray on docker icon. Thank you, I am able to load the image after I switch to linux container in server-side. After I loaded the image, I am trying to do the next step of configuration. 2) Configure your InterSystems IRIS instance 2a) Enable the /api/IAM web application 2b) Enable the IAM user 2c) Change the password for the IAM user Do we need to change these settings in iris.cpf file? any inputs where we have to configure. I have IRIS 2019.1.1 installed in my machine.

I liked the transactional analytic DBMS and Advanced Analytics segmentation concept. The 1.0 version IRIS plug-in to VSCode is amazing. The partnership between community and InterSystems was very positive to it. However a low code option would do very well for IRIS in the near future. The Dynamic Gateways/Native API positions IRIS as the most advanced data platform for the main open languages in the market, but it is necessary use the public package managers from these languages, specially maven public repository. The API Manager is a good option but it is not available to the community IRIS version and can be used only with API created with IRIS. It is a critical point to resolve. OPC-UA adapter to IoT and Kakfa adapter to realtime events are great, I loved it. In the future, new adapters to the Salesforce, SAP, Office 365 and other most used platforms could be considered. Cloud support is perfect now, with ICM and IKO to deploy and manage and SAM to monitor. The FHIR accelerator is great option to FHIR projects, it's really very useful. IRIS really is getting faster and faster, impressive to be able to make something that is already very fast faster. The Adaptive Analytics was an impressive launch and very welcome, it has the ability to speed up and simplify the creation of analytical cubes (in a totally visual and intuitive way) and its exposure to excel and other data viewers in a wonderful way. In the future I would like to see InterSystems launching its own viewer, since IRIS Reports is for restricted use and is not available for community versions, making it impossible to popularize in the community. The IntegratedML was my favorite new IRIS feature. Very easy to use, any DBA can be use it. The AutoML is a fantastic technology and will be used a lot. Now, InterSystems needs to deliver a viewer of predictions and classifications to the end user, it could use the same technology as SAM, the Grafana. I agree with you in most cases. The most important announcement for me would be Embedded Python.This will bring to the community the power of python libraries, it's a giant step forward. Yes, the integration with python is very important.

The FHIR® SQL Builder, or Builder, is a component of InterSystems IRIS for Health. It is a sophisticated projection tool used to create custom SQL schemas using data in an InterSystems IRIS for Health FHIR repository without moving the data to a separate SQL repository. The Builder is designed specifically to work with FHIR repositories and multi-model databases in InterSystems IRIS for Health. The objective of the Builder is to enable data analysts and business intelligence developers to work with FHIR using familiar analytic tools, without having to learn a new query syntax. FHIR data is encoded in a complex directed graph and cannot be queried using standard SQL syntax. A graph-based query language, FHIRPath, is designed to query FHIR data, but it is non-relational. Enabling a data steward to create a customized SQL projection of their FHIR repository, using tables, columns, and indexes, the Builder makes it possible for data analysts to query FHIR data without the complexity of learning FHIRPath or the FHIR search syntax.The repository will load FHIR Resources, All you need is to configure FHIR SQL BUILDER.For configuration, Navigate to http://localhost:55037/csp/fhirsql/index.html#/ For more details about how to do configuration, please watch this Tutorial Video To view the configurations, Navigate to http://localhost:55037/csp/fhirsql/index.html#/spec/1 Now let us use irisChatGPT application, Connect to the terminal by using the below command docker-compose exec iris iris session iris Create a new instance of dc.irisChatGPT class and use SetApiKey method to set OpenAI API Key set chat = ##class(dc.irisChatGPT).%New() do chat.SetAPIKey("Enter your Open API Key here") Thanks Hi Muhammad, Thank you for putting this demo together. When I go to http://localhost:55037/csp/fhirsql/index.csp# to configure FHIR SQL BUILDER, I get the following:The IRIS instance is running and is healthy as seen: Please advice what the issue might be.Thank you. Hi @Piyush.Adhikari Thanks for highlighting the issue. Please modify index.csp to index.html as mentioned below:http://localhost:55037/csp/fhirsql/index.html#/RegardsMuhammad Waseem I bet that the issue is related to the fact that recently IRIS 2023.2 was released. This version removed this method `InstallFoundation` from this class `HS.HC.Util.Installer`. This was a private method and it was not documented. But it was widely used by the community to install FHIR server. TL;DR : Change : ``` do ##class(HS.HC.Util.Installer).InstallFoundation() ``` to ``` Do ##class(HS.Util.Installer.Foundation).Install(namespace) ``` cf : https://community.intersystems.com/post/installfoundation-method-missing-iris-20232 Thanks, @Guillaume.Rongier7183 for the suggested solution. Thank you @Muhammad.Waseem Just leaving the link to the documentation that mentions that link to access FHIR SQL Builder here.

# InterSystems Package Manager 0.9.0 Beta I am excited to announce the upcoming release of InterSystems® Package Manager (IPM) version 0.9.0. This has possible impact for all users of IPM and we would welcome the community’s feedback prior to release. ## How can I get involved? As an important note, this is a beta and not yet recommended for use in production. You can find the latest v0.9.0-beta.x release at https://github.com/intersystems/ipm/releases. Under assets, there’s a file named zpm-0.9.0-beta.x.xml. Download this and then load it with $System.OBJ.Load(filename,"c"). If you find any issues, please report them at https://github.com/intersystems/ipm/issues. ## When will version 0.9.0 be released on the Open Exchange? December 16, 2024 (ultimately; we slipped on this a bit due to holidays and some unexpected late-breaking issues) ## What has changed? The most significant change is the restructuring of the codebase and rename of all classes, from %ZPM to %IPM. This isn’t expected to impact most users of IPM but if you have packages that extend or reference package manager classes, they will need to be updated. The %IPM package is mapped to the namespace-default routine database on installation, with the option (but no longer the requirement) to make it available instance-wide; the latter is done automatically on upgrade from earlier IPM versions that were available instance-wide. There are several reasons for this change: * InterSystems is taking real ownership of this code, so the naming should move out of a space reserved for users. * Code living in IRISSYS – such as classes prefaced with %Z – gets some special security exceptions that we don’t want IPM to have. * A package mapping approach allows different versions of IPM to run in different namespaces on the same instance. This is helpful if multiple distinct applications are running on the same instance because they are now able to update IPM independently. * The original %ZPM package structure was based on some early design intent that is now outdated. Renaming was also an opportunity to make the class names and package structure more intuitive. We have added automation around testing of the most popular Open Exchange packages, which gives us confidence that the rename and numerous other changes do not have widespread functional impact. ## Why is this release important? It’s helpful to provide a bit of history here. From 2016-2018, I led a team building a package manager for use in development of InterSystems HealthShare® products and InterSystems IRIS® for Health. Our objective started out as revolutionizing the installation and upgrade process for HealthShare, but quickly shifted to taking an enormous, monolithic ObjectScript codebase and making it more modular; a package manager goes a long way to help with that. At the same time, Evgeny Shvarov saw a need for providing a standard way to define and distribute InterSystems ObjectScript-based projects from the open-source community. A package manager is the right tool for that job, too. So Evgeny and team forked the HealthShare package manager, and different teams continued to develop the two projects independently for many years. The community and Evgeny’s team made amazing contributions to ZPM, but most of InterSystems direct investment was in the HealthShare package manager, from within the HealthShare development team. Unsurprisingly, there was significant divergence between the two codebases due to differing needs and use cases, and each package manager was ahead of the other in different ways. We have finally finished reconciling the two, bringing together the best of both, and the release of InterSystems Package Manager 0.9.0 finally marks the point where we just have one package manager. Going forward, investment from InterSystems development in IPM will benefit the community (rather than just HealthShare development), and we are ready to reengage with the community that has driven so much innovation in the past. This work has been a long time coming and has gone through a few changes in ownership, but I am now the architect for IPM, with Bob Kuszewski serving as product manager. ## What’s coming next? We have a lot of big things we'd like to do. These include a focus on improved documentation, catching up with industry standards around software supply chain security, better support for publication and distribution of different artifact formats (such as deployed code targeting multiple versions), and eventually adding options to enable IPM at instance installation and namespace configuration time. We want to hear from you, too, whether that's here or through GitHub issues or discussions. ## Known Issues In general, you can see the latest known issues here: https://github.com/intersystems/ipm/projects/8 If any particularly notable new issues are discovered, I’ll update this post. @Timothy.Leavitt - great work on continuing to move this critical piece of our tech ecosystem forward!! well done Great news, @Timothy.Leavitt!How can I test the 9.0 beta IPM client? No problem found it https://github.com/intersystems/ipm/releases First I went to OEX and didn't find it there. Any updates when 0.9 will be released? Jani, thanks for asking - December 16 is the plan. Great! After I have upgraded it too we can have a session about my IPM usage scenario if you're still interested. I guess the session could take place on early January.

Overview After having some discussions at Global Summit and using a lot of package managers in my day to day development (npm,nuget,Chocolatey, etc) in addition to recently using the InterSystems Package Manager for some CICD process I'm building using Intersystems IRIS and IRIS 4 Health, I wanted an easy and integrated way to search/view/install packages related to the Intersystems tech stack. I recently built a VSCode extension for IPM repositories that I will be open sourcing and publishing to the marketplace but wanted create this post to get some feedback from the community. Some features in the extension: VSCode setting for defining multiple repositories Activity Bar Icon/Explorer View List of packages in custom view List/Open github repository configured in package Details for package in a custom view Copy ZPM install command for use in IRIS terminal Setup/Settings: When you first start the extension, you will need to configure it. You can do this by accessing the settings.json file and adding something like the following. "ipm.repositories": [ { "name":"Public IPM", "url":"https://pm.community.intersystems.com" }, { "name":"Internal Packages", "url":"https://[insert private repo here]" }, { "name":"Test Packages", "url":"https://[insert private repo here]" } ] Screenshots: Ideas/Future After building this and working with the API, I'd like to propose a couple updates that potentially could be added to the manifest/API for packages to make integrations like this a little easier License field: (This will let the users know if the package license is compatable with their usage) Logo: encoded image for the package. Allow the developer of the package to specify an image Readme: Allow the developer of the package to include a readme markdown file in the package. This can then be displayed in the details section of the extension. Author: Include the author of the package (can be displayed the details view) Verified: Allow for an author to be verified. For example Intersystems could be a verified author Open Source: I will open sourcing this extension on my github page after running a few more tests. Comments/Suggestions Let me know what you think or if you have suggestions let me know. Would you be interested in using this? Sounds very promising and a big time saver! Very cool, @John.McBrideDev ! I think VSCode should have IPM extension. There is another helpful app I'm using for similar purposes which IMO has a better UI - ZPM-Explorer by @Henrique and @José.Pereira . Maybe you could borrow some functionality. Looks interesting, but that project still needs to be installed on the iris system. IMO I was something that is independent of the IRIS platform and is tightly integrated into a development environment. Which is why I built it into VSCode. I don't want to have to install and entire app on infrastructure to make it work. If that solution works for you workflow, its a great option as well Just my .02 nice extension app Another approach to this is the extension I wrote about here.

When I was searching for the ideas to migrate IRIS DB to Oracle, I could find a tool called "ESF Data Migration tools" over internet with easy steps. Can we use them to migrate? Link for your reference https://www.dbsofts.com/articles/cache_to_oracle/ Thanks in advance You probably should ask this in an Oracle forum.This is definitely not the best place to discuss such idea Help can be found here https://imgflip.com/i/8w3ot6 I like that response - also more money. I am working on an Oracle to MS-SQL migration now and really tried to get the vendor to support IRIS SQL but they won't consider. I find it particularly odd given at least a third of their customers already have an IRIS instance. Too bad Intersystems doesn't have a "MS-SQL" emulation mode. I would so love to speed test against MS-SQL directly. I know in generic SQL projects, IRIS easily beats both on the same hardware and at a fraction of the cost. probably the wrong direction ? How 'bout https://docs.intersystems.com/iris20241/csp/docbook/Doc.View.cls?KEY=GTSQ_intro I am wondering even if this is a right architecture decision to move from IRIS to RDS or find a nosql match?

Looking to download IRIS for health 2024.1 software Assuming you have access, you can download from the WRC application - wrc.intersystems.com. If you don't have access you should discuss with your account team. wrc.intersystems.com worked to download the required softwares. Thank you ! glad to hear it!