Per your second question, best practice is generally to use System Defaults which are set in your Namespace and store the production settings (rather than storing them in the Production class). This allows you to prevent having to have differences in the Production class between branches.
Steve - #2 is helpful if you want to leverage existing structures for authentication, auditing, transport or other functions that rely on CSP sessions . This can be used as part of a strategy of incrementally moving an application from a CSP-based architecture to Angular.
If your machine is virtualized, just clone the VM (that is what we do for all of our test upgrades). NOTE - make sure to stand it up on an isolated network segment so that it doesn't try to do any inbound file processing or other communication that it should not (especially if you clone LIVE).
Thanks again for sharing the start of your journey with the Community. I am curious if you are planning to provide another Update Article? I would love to hear about how your journey has progressed over the past year and what you have learned along the way which could help others!
Cheers,
Ben
Bouncing off of @Robert Cemper 's hints, if you are using a default SMP (system management portal) login you can just pass in the arguments for the username and password fields as follows:
https://mytest.myserver.com/csp/sys/UtilHome.csp?CacheUserName=tech&CachePassword=demo
I just tested this and it worked like a charm :) (use your own credentials of course)
Exactly! We are actively using it internally within InterSystems - both in internal application development, and in HealthShare product development. As discussed in the video we have found incredible value in this tool for decreasing technical debt (and making sure new changes don't add to it). We thought customers might find the value in it as well.
You are most welcome. In terms of why TestCoverage was released on OpenExchange, it is something we have been exploring internally last year and wanted to share with the Community in time for Global Summit 2018. In terms of whether or not it will actually make it into product, I can't speak to that but perhaps the author @Timothy Leavitt can comment on that (I believe there were at least exploratory discussions with Product Management on this topic).
The first half of that should be helpful. Code coverage may be helpful too if they are able to move into a CI type BUILD infrastructure (I don't know how well Test Coverage would work in a more dynamic Dev environment as longitudinal history might be harder to maintain ... haven't really thought about that too much before...)
Mike,
We're using UnitTesting for application validation for internal application development within InterSystems. If you have any specific questions, feel free to create new Questions in the D.C. and tag me, or if you would prefer a general discussion you can ask your Account Manager or Sales Engineer to set up a discussion with me.
There have also been several Global Summit presentations which have touched on the topic - not sure if you've seen these?
Best,
Ben Spead
Manager, AppServices, InterSystems
Sorry - I forgot that you first need to specify the source control class in the Management Portal. Put "Source Control" in the Search box on the SMP homepage, and then go to that page (e.g. http://localhost:57772/csp/sys/mgr/%25CSP.UI.Portal.SourceControl.zen). Select the Namespace in the left column and then "%Studio.SourceControl.ISC". Save the changes and try the BaselineExport() again. When you are done with the export, change the Source Control back to "None"
As a general tip, if you do enable and enforce source control, then you wouldn't need to be querying your class definitions to find variations between environments - you could see all of that (and so much more!) in your source control system ;)
I understand ... so you want to only export specific things which it has found to have differences in the code. That makes sense since you are trying to use it at the end of a piece of code already in place. I am afraid I don't know how to do that, but if you contact Support they may be able to suggest a trick or two.
Is there a reason that the use of a Virtual Namespace is a requirement? If not, you can use ##class(%Studio.SourceControl.ISC).BaselineExport() to export the entire contents of the Namespace to disk for file-based diffing (this is how I normally do it)
I can only comment on the original functionality in %Studio.SourceControl.ISC - if you're extending it you will need to do some debugging to see exactly why you are seeing the behavior that you are.
In the original %Studio.SourceControl.ISC class, when working in Connected mode (ie, Caché can issue p4 commands in real time to the Perforce server), the p4 command should take care of changing the file back to ReadOnly, which is what triggers GetStatus() to see it is uneditable and therefore not checked out. It may be that your GetStatus() isn't correctly interpretting the Reaonly state of the file, or if you are on UNIX, it may be that Caché doesn't see it properly as Readonly (this can happen if you are running your instance as Root). Note - I think there may be a bug where after checking the %Studio.SourceControl.Change table isn't updated appropriately, but the primary indicator of checked out/ checked in should be that Readonly bit on the file.
Hopefully this is enough to get you moving on this, and if not then I suggest you call Support to have them take a look with you and debug. If there are any other questions I can answer in this forum I am happy to try.
Best of luck!
Adrian - are you writing your own Perforce hooks or use the sample Perforce hooks that ship with Caché? (%Studio.SourceControl.ISC.cls).
In %Studio.SourceControl.ISC.cls it checks to see if the file in the local workspace is Readonly or ReadWrite. If Readonly it assumes it is not checked out and prompts the user to check out. If ReadWrite it will see if it is a multi-developer or single-developer instance. if single developer it can just edit it. If multi-developer it will check in %Studio.SourceControl.Change to see if the current user is the one who checked it out - if so they can edit, if not they can a message of who is editing it in the Output window and the item is treated as ReadOnly to them.
Eduard - I completely agree!
The nice (or annoying, depending on your perspective) thing about moving to the discipline of unit testing is that it forces you to write your code in a more modular (and therefore more testable) manner, and refactoring to meet these goals is a great byproduct of a testing focus :)
Alex - I think it isn't a smart idea to call into a specific line number of a routine since the contents will change. Instead you should call the line labels/functions called within the routine by outside of the routine and pass all appropriate variables, etc that way.
Trying to call a specific line number will certainly lead to faster than desired 'bit rot' in your unit test library.
Welcome to the the InterSystems Developer Community!!
1) ObjectScript is a (very, very large) superset of the M language (previously known as MUMPS)
2) InterSystems IRIS uses much of the core technology that was in Caché, but it is a break from the past in many ways and allows next-gen development tools, architectures, etc. InterSystems IRIS is an upgrade path which current Caché based applications should seriously consider. Zen is a legacy web development technology which runs on top of Caché (it ships with Caché and InterSystems IRIS)
3) The answer to this depends on whether you are taking straight globals, or persistent objects. Any data persisted via InterSystems Object or Relational structures can automatically be accessed via SQL. If you are just writing straight globals (e.g. set ^Patient(123)=foobar) then you can't query unless you set up an SQLStorage mapping to your globals
4) You can map your existing global structures to object definitions for OO/SQL access using SQLStorage (https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cl…). It looks like there isn't a lot in the docs on that so you should contact Support for more details on how to set it up to match your existing data to definitions which you can hit with traditional SQL.
Hope that helps!
Excellent article Michelle! Very well done :)
I absolutely concur that if a shared dev instance is going to be used along with client-side hooks then locking is a *must*! However, some may find that exclusive ownership on a single Shared dev instance is too restrictive, but find themselves still needing a Shared dev instance in the mix for certain reasons.
An alternative would be a Mixed mode of working with a Shared Dev and one or more Private Dev environment. We have found that this mode works really well for us in the case for large teams on active projects - locking across the board we've found to be too restrictive in how it blocks work. We have found this on a couple of our most active applications where we need shared development instance for a number of reasons. In order to make this work, you will need to move to using Server-Side Source Control hooks on the Shared dev instance, and then developers that don't require work on the shared dev instance can have a private instance which uses either Server-Side or Client-Side source control hooks (in our case we use server-side in Private dev instances to make it easier to support). This will work because the Server-Side Hooks on Shared should manage concurrency of any developers connected to that instance (they can't check out a file someone is already working on), while not locking the file in source control which would prevent other developers from touching it on their Private Dev instances.
Just throwing this out there as another option for those who find that they are tripping over exclusive locking, and are not comfortable running with unlocked files on the Shared Dev instance.
Also, a big thumbs up for including the suggestions of Jenkins - we have started using it this year to automate build/unit/code coverage testing on every check-in and are seeing some great results!
Make sure that you review all of the shortcuts outlined in the documentation (there are a LOT of useful ones there):
https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cl…
Also, check out one of my favorite things to do with Studio which isn't as widely known as it should be:
https://community.intersystems.com/post/studio-tip-running-cos-commands…
Hope that helps :)
Ben
It's deprecated but still available. Swapping it out for $zf(-100) for %Studio.SourceControl.ISC is on the TODO list...
check out the ##class(%Studio.SourceControl.ISC).RunCmd() method for an easy way to capture the OS output
You can use $version(1) to see if it is Windows (returns '2') or UNIX (returns '3'). If you want to get really fancy you can include %occOptions.inc and then use the $$$isUNIX and $$$isWINDOWS calls (which just check to see if $version(1) is 2 or 3).
Personally, I like using ##class(%Studio.SourceControl.ISC).RunCmd() as it wraps the capture of the output for parsing.
You can tie $version together the other answers into something that is platform independent (warning, I haven't tested this, but I believe the pieces work):
If ($version(1)=2) {
//Is Windows
set sc=##class(%Studio.SourceControl.ISC).RunCmd("Ver",.out,0)
set OS = out(1)
// exercise of parsing exact desired version piece from the string is an exercise left to the reader
} elseif ($version(1)=3) {
//Is UNIX
set sc=##class(%Studio.SourceControl.ISC).RunCmd("uname -a",.out,0)
set OS = out(1)
// exercise of parsing exact desired version piece from the string is an exercise left to the reader
}Hope that helps you Paul!
Mack- the %occLibrary calls are not documented for use by applications.
As your very interesting questions has proven the ease with which this is solved by:
$$CSVtoList^%occLibrary(csv)I suggest you contact the WRC to request an enhancement to have this wrapped in a supported (and documented!) API that may be more future-proof than this internal and undocumented call.
Nice work Gerd!
Daniel,
You are absolutely correct that using Client-Side source control hooks (ie the Eclipse Git hooks with Atelier) in a Shared development instance is a recipe for disaster and frustration. You options are moving to Private development environments (each developer gets their own Namespace, or instance, or VM or container), or move to Server-side source control hooks.
I did an in depth session on this at Global Summit 2017 which should be of interest to you. You can watch the recording and get the slides here:
https://learning.intersystems.com/course/view.php?id=713
HTH,
Ben
Akio,
First - welcome to the InterSystems Developer Community and to exploring InterSystems database technologies!
I see that you changed your original post and content and changed it to ask about the cube (original post was "question I want to use the database in the evaluation version"). I think it might be easier for you if I try to answer your first question ;)
My suggestion is that if you are new with InterSystems technologies that you start with InterSystems IRIS rather than Caché. There are some great cloud-based trials for exploring and learning about InterSystems IRIS and you don't have to install anything locally in order to play with it.
Please check out: https://www.intersystems.com/learn-play/
If you would prefer to play with Caché locally, then I am sure someone can answer your question about the cube (I am not on a Mac so I can't advise on that point).
All the best!
Ben
Unfortunately "ATL-3982" is not included. I don't know anything beyond that (in terms of plans for it in the future). You may want to grab a Product Manager to discuss if you're going to Global Summit in a couple of weeks.
Please contact InterSystems Support for assistance on this:
https://www.intersystems.com/support-learning/support/immediate-help/
Thank you,
Ben
Bravo!! I had never really seen a good 40,000 foot view of machine learning before, and this really suits the need!!
Thanks for your work on this Don!
Eduard - I think Arcady was asking from a purely data-processing perspective. I.e. if you are already have a bunch of in-memory data and need to process/iterate on it, is it better to stick it in traditional structures and use $Order, or is it equivalent to stick it into the new structures for iterating and processing? I think it's a good question and I would also like to hear what people think :)