go to post Tani Frankel · Mar 1, 2024 Did you try accessing the terminal web app via port 52773, like your Mgmt. Portal? 52772 used to be the default port for the Private Web Server, but this could change per installation.
go to post Tani Frankel · Feb 22, 2024 Thanks @Ben Spead, note the link @Azezur Rahman provided above - https://download.intersystems.com/download/login.cspDoes not work (and is not redirected). Though as you mentioned the more basic - https://download.intersystems.com/ would redirect to the newer Evaluation page.It would be great if, as you suggested, the original article could be updated.
go to post Tani Frankel · Feb 20, 2024 These screenshots are useful! tx! Just updating the download link, nowadays this is: https://evaluation.intersystems.com/ (see also this post) And the download page for the Community Edition could look like this -
go to post Tani Frankel · Feb 13, 2024 Here's the recording of this session - https://www.youtube.com/embed/uT5sqSwtF0k?si=AiFyEe46jahRm7SH[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
go to post Tani Frankel · Jan 28, 2024 I recommend participants who are not currently using VS Code yet, at least review our previous Webinar on the topic.
go to post Tani Frankel · Jan 27, 2024 Theo, as you see it is described as "beta" therefore it is not currently publicly documented. Internally you can see IF-1930. It states: "This should only be used with guidance from InterSystems Support."
go to post Tani Frankel · Jan 10, 2024 See also this post https://community.intersystems.com/node/548491 by @Guillaume Rongier
go to post Tani Frankel · Dec 24, 2023 I believe you have stumbled across a known issue - that if you call the method you mentioned above HS.FHIRServer.Installer:InstallNamespace() in a container, more than once, the FHIR Config UI app breaks (due to the folder location you mentioned above). This was fixed since version 2023.2 (I see you are using 2023.1). If you want to upgrade to 2023.2/3 you will have the fix. (just note the differences between CD (Continuous Delivery) releases and EM (Extended Maintenance) ones (like 2023.2/3); see this article for more details). If you can't upgrade now I suggest you turn to your local InterSystems account team (@Anssi Kauppi / @Janne Korhonen) and/or InterSystems WRC (you can reference the internal fix IF-4531).
go to post Tani Frankel · Dec 14, 2023 Maybe using the Portal built-in "Test LDAP Authentication" can help. See Docs.
go to post Tani Frankel · Nov 23, 2023 Hi Yakov, You can see from the Docs here, for example re the Property ConnectAttrs (or later ConnectionAttributes): ConnectAttrs ... An optional set of SQL connection attribute options. For ODBC, they have the form: attr:val,attr:val For example, AutoCommit:1. ... Set this property in the OnInit() method of your business operation or business service to specify the options to use at connection time. For calling SetConnectAttr() see these Docs, for example: If the connection has already been established, call the SetConnectAttr() method of the adapter. This method takes two arguments (the attribute name and the desired value) and returns a status. For example: Set tout= ..Adapter.SetConnectAttr("querytimeout",10) As to the name of the attribute and the appropriate value you should consult the SQL Server documentation (for example this, but this will be up to you to verify). If you need more assistance than this please get in touch and we can work on this together.
go to post Tani Frankel · Nov 22, 2023 Hi Dmitrii,Thanks for this question.Programmatically you can use the method Security.Applications:Modify() (from within the %SYS namespace). Here's an example: set props("RedirectEmptyPath")=1 set status = ##class(Security.Applications).Modify("/myapp/name",.props) This article by @David Hockenbroch covers this Security Applications API (including reference to this setting) in general.
go to post Tani Frankel · Nov 20, 2023 By the way using Structured Logging might also be useful in this context.
go to post Tani Frankel · Nov 6, 2023 Sorry for the basic questions - Do you have data (Resources) in your FHIR Server? How many Resources do you see were processed in the Analysis?
go to post Tani Frankel · Nov 2, 2023 Maybe the problem with IIS has to do with Web Socket support. See for example from the Docs here: This extension uses WebSockets to communicate with the InterSystems server during debugging. If you are experiencing issues when trying to start a debugging session, check that the InterSystems server’s web server allows WebSocket connections. For example from the Windows Features - See also IIS Docs. If this is not the issue let us know if you are getting any error on the VS Code side and/or if you can turn on some logging on the Web Gateway or Server side.
go to post Tani Frankel · Oct 19, 2023 Until 2023.3 is GA, and you can upgrade to it, see also this related Global Summit 2023 session recording: https://www.intersystems.com/performing-advanced-fhir-validation-intersy... [Not sure I fully trust the presenter though 😉] And the related Open Exchange app (and GitHub repo): https://openexchange.intersystems.com/package/fhir-profile-validation
go to post Tani Frankel · Oct 3, 2023 See relevant values from the docs here: https://docs.intersystems.com/irisforhealthlatest/csp/documatic/%25CSP.D...
go to post Tani Frankel · Aug 24, 2023 Though this post does not address the question/issue raised directly it might help shed some light on some of the settings used.
go to post Tani Frankel · Jul 18, 2023 Now you can see also the latest related session from Global Summit 2023: https://www.intersystems.com/clinical-alerts-notifications-on-fhir-putti...
go to post Tani Frankel · Jul 16, 2023 See related Idea to allow the Web Gateway installer to map all requests from the Web Server to the Web Gateway.
go to post Tani Frankel · Jul 16, 2023 Thanks @Patrick Dunn this is indeed a common issue, so thanks for taking the time to post about it. I was thinking that this might become an even more common issue once we remove our Private Web Server (PWS) [related post for reference] so added this Idea to allow the Web Gateway installer to do this work for you in advance. @Andreas Dieckow please review (perhaps this was already taken into consideration).