@prashanth ponugoti - a couple of things to look at:
1) When you open the first link in /csp/healthshare does it open for you after authenticating?
2) Is your /csp/test web application definition set to work in the same namespace as /csp/healthshare?
3) Is a copy of your person.csp file moved to the web application root that you defined for /csp/test?
Hope that helps get you started on finding a solution.
Note ... make sure you have downloaded the actual Community Edition kit (if you did not then it won't have a license embedded). Go to evaluation.intersystems.com and select the option for Community Edition to make sure you have the right kit.
really nice article @Eduard Lebedyuk - thank you for taking the time to write this up! I am going to add this reference to my team's debugging resources list!!
Thanks for the additional use-case :)
Good point Robert!
@Evgeny Shvarov - you cannot use "!<cmd line>" from the Output window of Studio. It is often very helpful to run a command from the context of a serverside Caché/InterSystems IRIS process which you can do via the Output Window with the above command, but not with "!":
!whoami
whoami - Error <SYNTAX>
Kill stream Set sc = ##class(%Studio.SourceControl.ISC).RunCmd("whoami",.stream,,1) w ! do stream.OutputToDevice() If 'sc { Write $System.Status.GetErrorText(sc) }
CMD: whoami
irisusrAgain, this is particularly useful when running server-side source control commands (if you need to debug or augment hooks)
@Sylvain Guilbaud - wow ... thanks for the interesting trivia :)
Thank you @Yuri Marx - great reference!
This is great, thank you Evgeny!! Here is another one that I use, often from the Output window in Studio in order to execute an OS-level command (I most frequently use this for p4 commands to interact with my Perforce server from my IRIS server). IIRC, original credit goes to @Timothy Leavitt
Kill stream Set sc = ##class(%Studio.SourceControl.ISC).RunCmd("<insert OS Command here>",.stream,,1) w ! do stream.OutputToDevice() If 'sc { Write $System.Status.GetErrorText(sc) }Nice application of our new Python support ... I especially love the the QR code feature!!
@Dan Pasco - I always appreciate it when you jump into these threads ... I learn so much!!
@Evgeny Shvarov - really good to know, thank you for clarifying!
@Paul Cranston - curious if you found anything that is helpful, and if not, what areas of automation within HS are you looking for?
This looks like a great opportunity for those in Eastern Europe!! I look forward to seeing the results coming out of this incubator program
@A.R.N. H Hafeel - are you specifically interested in Caché or are you looking for the latest and greatest and therefore interested in learning InterSystems IRIS?
Really glad to see this spelled out so clearly for our customers - thank you @Jeff Fried !!
Well deserved @prashanth ponugoti :) Keep up the excellent work in your contributions to our Community!
Congratulations everyone and thank you for your code contributions to the Community that everyone can leverage!
Congrats to the winners, especially @prashanth ponugoti who is on the winner's podium for the first time!!
Congratulations @Shane Nowack and team!
To our users of CCR in the field, thank you in advance for making time this month for participating as a Beta Tester of InterSystems' newest Certification Exam!
All - please note the new Practice Questions have been added to this post as an attachment, and that the opening up of the Beta Test has been announced:
https://community.intersystems.com/post/beta-test-intersystems-ccr-tech…
If anyone hasn't registered as a beta tester yet and would like to do so, please email certification@intersystems.com
Thanks Vic! Always great to have a documentation reference :)
In the \bin directory is the csystray.exe file. Run that to get the cube running. Alternatively, you can use the cube that you do see in your systray and select "Remote System Access" to get to Studio, SMP, etc of your second instance.
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")
root
w ##class(%SYS.ProcessQuery).GetOSUsername()
cacheusr
[/quote]
@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:.png)
Perfect!! Exactly what I was looking for - thank you @Sarmishta Velury (and @Jean Millette and @Timothy Leavitt )
great way to do it within InterSystems IRIS - thanks Tim!
Note - more details on this topic can be found here: https://community.intersystems.com/post/git-shared-development-environm…
NOTE - to see the presentation launching this at the 2021 Global Summit, see this article: https://community.intersystems.com/post/video-git-gitlab-shared-develop…
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…
) 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