go to post Vic Sun · Sep 20, 2021 Sai, By folder, do you mean moving a class to a different package? It's okay if the class name overlaps, because the package will still differentiate the "full name" of the class. ex, the following can coexist. package1.class package2.class You could also use subpackages such as package1.subpackage.class. Some of the built in class divisions might be helpful for you to compare with - for example, on IRIS for Health, the following packages exist: EnsLib.HL7.Operation EnsLib.HL7.Service etc., for each type of business component. I certainly agree that having Git / source control set up is a good practice. You may also find the built-in production deployment functionality useful:https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=EGDV_deploying
go to post Vic Sun · Sep 20, 2021 Vivek, I looked at learning.intersystems.com and it looks like the FHIR tutorials make use of the new SMP features. For 2019.1, it seems the documentation I linked would be the best starting point. https://docs.intersystems.com/irisforhealth20191/csp/docbook/DocBook.UI.Page.cls?KEY=HXIHFHIR_fhir_productionconfigure#HXIHFHIR_fhir_productionconfigure_init
go to post Vic Sun · Sep 16, 2021 Hello Alicia, I would recommend you reach out to your Athena representative for guidance on what version of IRIS to migrate to. I anticipate you will also need them to distribute to you the appropriate kit. It also sounds like you are planning to go live with this change in the very near future. I would suggest testing this upgrade before attempting in your live environment. edit: I may have misinterpreted your org. If you are licensed directly with InterSystems, I'd recommend reaching out to your InterSystems account rep. If you are licensed through somebody else, they can help you with the migration to IRIS.
go to post Vic Sun · Sep 16, 2021 Sai, I'm not sure I understand your question, but it sounds like you are asking about code package conventions? Perhaps you can describe in more detail what you are trying to do, or give an example? Package Options
go to post Vic Sun · Sep 16, 2021 I'm not sure I understand what you want to do exactly. Presumably, there are at least a few namespaces where you want to access this code. You could test a few namespaces (not the %ALL "namespace", real namespaces) to confirm that you can access the code you have %ALL mapped.
go to post Vic Sun · Sep 16, 2021 That makes sense to me. As the docs explain, there is not really a "%ALL" namespace, it's more of an abstraction to represent a system-wide mapping. Once you have set up a %ALL mapping, I would just directly try to verify that the functionality works as you expect. For example, make a AllMapping package and put your test code in there, then make an AllMapping package mapping for %ALL, then confirm that you can access that code in any namespace.
go to post Vic Sun · Sep 16, 2021 Hello Muhammad, Where are you trying to select %ALL? https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GSA_config#GSA_config_namespace_addmap_all "%ALL is not visible except for the purposes of mapping data; that is, it is not a real namespace, but a mechanism for mapping data to all namespaces."
go to post Vic Sun · Sep 16, 2021 Vivek, Your version of IRIS for Health doesn't have the SMP UI to create a FHIR server. That was added in 2020.2. https://docs.intersystems.com/irisforhealthlatest/csp/docbook/DocBook.UI.Page.cls?KEY=HXIHRN_new#HXIHRN_new_serverui I'd suggest you look at the 2019.1 docs for your version's instructions. That being said, IRIS' FHIR support is being actively developed so it is changing frequently. If you can upgrade to the latest version of IRIS for Health, you will get access to the most functionality (and quality of life improvements like the SMP option!)
go to post Vic Sun · Sep 14, 2021 Hello Apoorva, I see you've already opened a WRC for this. I think it definitely makes more sense to look into this with InterSystems than on this forum. In general, my questions would be along the lines of why you needed to force the instance, and what other messages were logged. The OS logs will probably also be helpful.
go to post Vic Sun · Sep 13, 2021 Hey Cedric, Unattended installs don't have a parameter for journal directories, but you can configure the journal directory with an installation manifest and Config.Journal. This post might be helpful also: https://community.intersystems.com/post/how-use-unattended-install-perform-following-tasks
go to post Vic Sun · Sep 13, 2021 Gotcha. Then perhaps the following documentation would be helpful: Configuring and Using Push Notifications
go to post Vic Sun · Sep 10, 2021 Muhammad, What exactly do you mean by push alerts? Email alerts are quite straightforward to set up. The following resources from learning.intersystems.com might be helpful. Basic course here: Setting Up Alerts For more: Proactive Alerting: Advanced Approaches for Alerting Solutions: Webinar Recording
go to post Vic Sun · Sep 9, 2021 Hello Muhammad, Either documentation page explains the difference: Embedded Language Development > ObjectScript > ObjectScript Reference > ObjectScript Functions > $INCREMENT https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=RCOS_fincrement#RCOS_fincrement_seq "$SEQUENCE and $INCREMENT can be used as alternatives, or can be used in combination with each other. $SEQUENCE is intended specifically for integer increment operations involving multiple simultaneous processes. $INCREMENT is a more general increment/decrement function. $SEQUENCE increments global variables. $INCREMENT increments local variables, global variables, or process-private globals. $SEQUENCE increments an integer by 1. $INCREMENT increments or decrements any numeric value by any specified numeric value. $SEQUENCE can allocate a range of increments to a process. $INCREMENT allocates only a single increment. SET $SEQUENCE can be used to change or undefine (kill) a global. $INCREMENT cannot be used on the left side of the SET command." Hope that helps!
go to post Vic Sun · Sep 8, 2021 Note that copying the CACHESYS is not a general recommendation. You may choose to copy that database in specific situations if you are prepared to deal with potential consequences. In general, if you have problems with CACHESYS, using the installer would be the preferred option. https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GORIENT_ch_enviro This documentation states that "InterSystems does not support moving, replacing, or deleting this database."
go to post Vic Sun · Sep 7, 2021 Storage recommendations are covered on a separate page, here: Preparing to Install InterSystems IRIShttps://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GCI_prepare_install#GCI_storage
go to post Vic Sun · Sep 6, 2021 Virat, What exactly do you mean by database tuning? Robert and Vitaly mention how to tune a table for SQL optimization, but what exactly were you hoping to achieve? I wonder if you meant something like configuring the memory settings for an instance, for which I'd recommend starting by reviewing this page of documentation: Architecture > Scalability >Scalability Guide > Vertically Scaling InterSystems IRIS
go to post Vic Sun · Sep 3, 2021 Kevin, That's pretty worrisome. <DIRECTORY> is not a problem with the command - it means the instance can't locate that directory - this case, the CACHESYS directory. I would be surprised if there aren't errors elsewhere in the Caché logs. https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=RERR_system "There is no such directory on the target system, no Caché database, the Caché database is not mounted, or the database is locked by another configuration. For further details, refer to $ZERROR." This might be a configuration issue, permissions issue, etc. Definitely would recommend opening a WRC at this point, if you can't identify the problem.
go to post Vic Sun · Sep 3, 2021 Kevin, It sounds like your namespace prompt has been replaced with a directory path in the terminal. The /mgr path is for %SYS (or CACHESYS, technically), but the fact that it is displaying that way seems a little unusual. It sounds like you're entering the implied namespace for some reason. Nothing immediately comes to mind for what could be causing this. You said "at some point", do you recall when that was and if any changes have been made? I wonder if login auditing would give useful information on this. Does logging in as a different user or looking at the user you are using's security settings show anything? May be worth opening a WRC, as that might be easier than troubleshooting through this forum.
go to post Vic Sun · Sep 2, 2021 Hello Michael, John's suggestion might help. Alternatively, try "iris terminal" as I think that's the best practice. Interact Using the InterSystems Terminal
go to post Vic Sun · Aug 26, 2021 Hello Lewis, In my experience, aborting doesn't retry a message. I wonder if something in your production is resending the message? Do you see anything in the logs that speak to what is happening? This may be worth opening a WRC about - if you do, I would be interested in hearing what you end up finding out.
