Hi Murillo,
I replied to your similar comment on this discussion thread. In fact I referenced this discussion there as well...
So you'll find a more detailed answer there.
In any case - using both utilities could be helpful for your scenario going ahead - the DeleteHelper to hopefully avoid these kinds of cases, and this utility to validate you indeed don't have any "Purge leaks".
Hi Murillo,
Happy you found interest in this utility.
The situation you described is in fact the classic scenario I had in mind when I built this utility, so it could definitely help.
Here are a few clarifications though –
As I mentioned in my original post above, in “relatively” newer versions of Ensemble (since 2017.1), and definitely in InterSystems IRIS, within the SOAP Wizard there is a checkbox that if you check, the auto-generated classes will include a similar %OnDelete method to the one generated by my utility. And therefore the built-in Purge Task will take care of deleting this data (going ahead that is… see more about this in the next comment).
So in these versions, for this specific scenario (SOAP Wizard generated classes, as well the XML Schema Wizard) you don’t have to use my utility. For other cases, where you have custom Persistent classes with inter-relations, my utility would still be helpful.
This %OnDelete method (generated by my utility, or by checking the checkbox in the Wizard mentioned above) takes care of deleting these objects when the Message Body is deleted. But if the Message Body has already been deleted (which seems like your case), this would not help (directly) retroactively.
It would still be recommended to add it, for Purges happening going ahead (and for another consideration mentioned soon), but just by adding this, the old data accumulated will not get auto-magically deleted.
If indeed you have this old data (of objects pointed to by older, previously purged Message Bodies) accumulated then you’ll have to take care of deleting it programmatically.
I won’t get into too many details about how to do this, but here are a few general words of background –
The general structure of Ensemble Messages (in this context) is:
Message Header -> Message Body [ -> Possible other Persistent objects referenced at; and potentially other levels of more object hierarchy]
The built-in Purge Task will delete the Message Header along with the Message Bodies (assuming you checked the “Include Bodies” checkbox in the Purge Task definition, which in 99.99% cases I’ve seen should be checked). But it will not delete other Persistent objects the Message Body was referencing, at least not just “out-of-the-box” (that’s where the %OnDelete method comes into play).
So if your Message Headers and Bodies referring to the “other objects” were already deleted, in order to delete the “not referenced anymore” objects, you’d need to find the last ID of these objects (at the top most level of the object hierarchy) that still has a reference, and delete those under that ID (assuming an accumulative running integer ID for these objects).
I believe the WRC (InterSystems Support – Worldwide Response Center) have a utility built for these kinds of cases (at least scenarios), so I recommend reaching out to the WRC for their assistance, if this is your situation.
Note that if you added my %OnDelete to your classes, then finding just the top-level object in the hierarchy, the one(s) that the Message Body referenced, would be enough to delete, since the %OnDelete will take care of deleting the rest of “the tree” of objects. That’s why I said above that it won’t help the situation of this “lingering” data all by itself, but it could help.
As you can see finding yourself in the situation of having accumulated old data that is not too straightforward to delete, is something you’d very much want to avoid. That is why I also built another utility that helps in validating, during development/testing stages, that there are no such “Purge leaks” in your interfaces.
In addition this tool also helps at providing an estimate as to how much diskspace (for database growth and journaling) your interface will require.
You can check this out here.
Hope this helps.
Thanks Evgeny, understood.
So you're saying: "InterSystems spec-first /api/mgmnt/ service generates such an endpoint." - that means that if I used the spec-first approach (which I did, I used ^%REST) I should have this /_spec endpoint? Because that didn't seem to happen...
Thanks for this tip Evgeny.
Indeed this /_spec convention pointing to the Swagger spec does seem convenient, I wasn't aware this was part of the Open API Specification (in fact I didn't find this mentioned in the Spec...).
I actually saw the method you mentioned when I was looking at the rest template provided as part of the previous contest, and thought of using it, but eventually since I used the spec-first approach, and this method you mentioned is currently (at least as-is) implemented assuming you use a code-first approach, I opted not to, and to have the same functionality (a REST API end-point providing the Swagger spec) via our already built-in API Mgmt. REST API (which I mentioned above).
I could of course consider adding something similar in the future.
Thanks Evegny.
Well no error info is a little hard to work with...
But (un)fortunately I was able to reproduce this (though earlier on in the process I tested with the test ZPM registry and it seemed to work fine...).
In any case I see (as I mentioned in my previous reply, it was worth looking there) that the UI Web Application was defined with an unauthenticated authentication method, only.
Even though the Module.xml file (link from previous version) defines it with Authentication...
Indeed when I look at the -verbose output of the ZPM install I see different behavior in each of the two CSP Apps being installed.
Even though both define this -
PasswordAuthEnabled="1"
UnauthenticatedEnabled="0"For the REST app I see this:
Creating Web Application /pbuttons
AutheEnabled: 32
AuthenticationMethods:Which is correct.
But for the 2nd app I see this:
Creating Web Application /pButtonsUI
AuthenticationMethods:Note no "AutheEnabled: 32" which it should have.
I edited some of the code within the ZPM class (%ZPM.PackageManager.Developer.Processor.CSPApplication) and saw that indeed the related properties (PasswordAuthEnabled & UnauthenticatedEnabled) where empty...
Playing around and comparing with some other module.xml's I found that perhaps the order of the values make a difference, so I changed:
<CSPApplication
Url="/pButtonsUI"
Path="/src/pButtonsAppCSP"
Directory="{$cspdir}/pButtonsUI"
PasswordAuthEnabled="1"
UnauthenticatedEnabled="0"
ServeFiles="1"
Recurse="1"
CookiePath="/pButtonsUI"
/>to be:
<CSPApplication
Url="/pButtonsUI"
ServeFiles="1"
Recurse="1"
CookiePath="/pButtonsUI"
UseCookies="2"
PasswordAuthEnabled="1"
UnauthenticatedEnabled="0"
Path="/src/pButtonsAppCSP"
Directory="{$cspdir}/pButtonsUI"
/>And now when I run the zpm install I see thsi:
Creating Web Application /pButtonsUI
AutheEnabled: 32
AuthenticationMethods:As expected.
So I pushed this update to github and hopefully this should work for you now.
In any case -
(a) I would recommend investigating why this was behavior - is this by design that the order of these attributes matter - if not - we should fix it, and if yes - we should document it.
(b) and regarding documentation - I would recommend to document the actual attributes of this CSPApplication tag. In the current documentation there is a simple reference to the %Installer tags, but in reality though they are similar they are still different in some cases... so we should either indeed adhere to those, or document the ones that Module.xml actually uses.
For example, for relevance to the current discussion - the CSPApplication tag in our docs (referred to by the ZPM Module.xml docs) has an AuthenticationMethods attribute while the Module.xml has a combination of others instead.
Another example - Module.xml has a Path attribute and %Installer does not.
Let me know if this now works, and what you think about what I observed.
FYI
The latest version available in the Open Exchange supports now also ZPM (Package Mapper) installation.
Thanks for trying Evgeny,
Regarding the error page you are getting in the UI I believe it's pointing you to the Application Error Log in the System Mgmt. Portal (right? the screenshot above is cut...), so try and look there and let me know what you find.
One place to verify things are generally setup ok for the web side, is to see the Web Application was created and defined correctly (including authentication, pointing to the correct physical folder, etc.).
Let me know what you find.
Regarding the Swagger/Open API spec - you find it in any of these -
1. A json file under the /swagger folder (as mentioned towards the end of the Readme). I used this for easier editing of the spec within VSCode with the relevant plugin.
2. The .spec class /src/zpButtons/REST/spec.cls
3. Using our built-in API Mgmt. REST API, in this case the URL would be, for example:
http://localhost:52773/api/mgmnt/v2/%25SYS/zpButtons.API.REST
With either of these you can take the JSON and view it via the Swagger Editor - https://editor.swagger.io/
Let me know if this is what you meant.
Note for more information about the pButtons/SystemPerformance utility see -
From Documentation:
https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GCM_systemperf
From the Developer Community (mostly by @Murray Oldfield):
https://community.intersystems.com/post/intersystems-data-platforms-and-performance-%E2%80%93-part-1
https://community.intersystems.com/post/intersystems-data-platforms-and-performance-%E2%80%93-how-update-pbuttons
https://community.intersystems.com/post/extracting-pbuttons-data-csv-file-easy-charting
https://community.intersystems.com/post/yape-yet-another-pbuttons-extractor-and-automatically-create-charts
https://community.intersystems.com/post/extracting-pbuttons-data-csv-file-windows
Hi Michel,
Are you using DICOM interfaces?
I believe the proper way to do this is not by editing the Production class XData, but rather by using the icon/button you can see in the image above, with the small light-blue arrow:
When hovering over this icon you can see the text: "Select settings defaults".
See details of how to use this here from the Docs.
In your case you would there check the checkbox fro the "try" setting, press the "Restore Defaults" button on the bottom of the dialog, and then press Apply on the Settings tab.
If, as you mention the purpose of this logging is debugging, then I would recommend going with $$$TRACE vs. $$$LOGINFO. This will allow you to turn on and off tracing without making code changes. Whereas if you go with $$$LOGINFO it's always there unless you remove it (or comment it out), then you need to compile, and then if you need it once more...
See also this related article.
Regarding your question on the *.impl generated class -
if you already added code to this class and later update the swagger and consume it again - indeed the code you added will remain.
If you review the video recording of the Global Summit Solution Developer Conference session I mentioned above - you can see a live demonstration of this specific case. [I recommend you see all of it, but this particular part starts at about 33:30]
Looks great David! 
I think for the "background" part this Global Summit presentation - "API Design for REST" (by @Michael Smart) could be helpful.
See also using the ^SECURITY utility (for manual export vs. programmatic which is possible via the Security package classes API).
For example:
%SYS>do ^SECURITY 1) User setup 2) Role setup 3) Service setup 4) Resource setup 5) Application setup 6) Auditing setup 7) Domain setup 8) SSL configuration setup 9) Mobile phone service provider setup 10) OpenAM Identity Services setup 11) Encryption key setup 12) System parameter setup 13) X509 User setup 15) Exit Option? 2 1) Create role 2) Edit role 3) List roles 4) Detailed list roles 5) Delete role 6) Export roles 7) Import roles 8) Exit Option? 6 Export which roles? * =>
If I understood the question correctly I think there might be some confusion...
Indeed internally Ensemble stores the Message Header times (TimeCreated & TimeProcessed) in a UTC time (per the considerations Robert mentioned) but when these times are displayed in the Message Viewer they go through conversion and are displayed in local time.
So if you would open the object via code, or run an SQL query directly, you would be dependent on running the relevant LogicalToDisplay() or LogicalToOdbc() methods for objects, or using the ODBC or Display runtime modes, but on the default Message Viewer web page these times should appear local.
You can examine this by doing a simple select on the Message Header table and you can see the difference between the Logical and Display modes.
For example, for a certain message, the Logical (internal UTC) time is 10:42 -
And now the same time using Display mode, the time is 13:42 -
And compare this with what you see in the Message Viewer, you see 13:42 -
and -
Note if you take a look at the Ens.DataType.UTC data-type class you can see it's conversion methods.
For example the LogicalToDisplay() method.
Here's an example of what it looks like when it's code runs.
In the following code I show my current local time (using $H, taking into account Time Zone and Daylight Saving), then I show the current general time (using $ZTS, per GMT and no Daylight Saving), and then applying the code run by the method, calling the method, and explicitly.
TEST>set currentLocalTime = $ZDateTime($Horolog,3,,3) TEST>set currentGeneralTime = $ZDateTime($ZTimeStamp,3,,3) TEST>write currentLocalTime 2018-09-20 10:46:07.000 TEST>write currentGeneralTime 2018-09-20 07:46:15.107 TEST>write $zdatetime($zdTH($zdatetimeh(currentGeneralTime,3,,,,,,,,0),-3),3,,3) 2018-09-20 10:46:15.107 TEST>write ##class(Ens.DataType.UTC).LogicalToDisplay(currentGeneralTime) 2018-09-20 10:46:15.107
See the -3 argument in the $ZDTH function call, from the docs this does the following -
$ZDATETIMEH takes a datetime value specified in $ZTIMESTAMP internal format, converts that value from UTC Universal time to local time, and returns the resulting value in the same internal format
Hi Dmitry,
Recommending your very cool and useful utility to someone I realized I did not find installation instructions, not here in this article, nor in the GitHub readme.
Could you please point me to them, or in case they indeed do not exist currently can you please provide them, for the benefit not only of the person I'm sharing this with, but with other Community members who will want to use this in the future.
Tx!
What is the class name of your Web Service?
Is it also a Business Service? If so - what is the name of the BS component in the Production?
What URL are you using to access this WebService?
I have encountered this error when trying to call the WebService in a way that did not allow Ensemble to understand what is the name of the business service class it needs to use (for example by using the CfgItem URL parameter).
Happy this helped.
In general (you might be aware of this, but for the benefit of the Community) a good resource about searching Messages (including Search Tables and SQL, and other options), is this Online Course.
The issue of indexing data previously processed (before the Search Table was defined for the Business Service/Operation) is addressable by calling the BuildIndex() method of the relevant SearchTable class.
For example:
Set sc=##class(YourPackage.YourSearchTableClass).BuildIndex()If I understand your question correctly then I think you'd benefit from defining and using a Search Table.
See from the Documentation -
If you need to query specifically via SQL (and not using the Message Viewer) then see also this answer (though relating to HL7, but relevant in the same way to the XML case) regarding using the Search Table within a query.
Please note that by default when a Persistent instance is %Saved()'d it gets done inside a Transaction, and therefore, even if the Database the Class' storage globals' are in, is not journaled, these SETs (and KILLs) will get journaled (for supporting rollback).
See this article for more details regarding avoiding journaling data. Specifically - the options of using CACHETEMP or turning off transactions for object filing.
Note if you are concerned with the audit logs generated for every turning off and on the journal for your process - you could simply turn off that System Audit event - %System/%System/JournalChange. Taking of course into consideration the drawback of not logging these kind of events outside the context of this specific scenario.
Hi Wolf,
I am using v2017.2.1 and Atelier 1.2.118 and I'm not experiencing this.
What I have encountered with regard to license consumption and Atelier (also with version 1.1 of Atelier) was that if I did not define a proper user for the server login (i.e. UnknownUser) then multiple users where consumed (per CSP session of the REST calls). So the recommendation is (also regardless of this licensing aspect) to define a real User for login. Note the phenomena I saw was that of multiple Users, not multiple connections of the same User (if that was what you were seeing).
I suggest that if, also when you define a proper User for login, the issue persists (and you don't get any other swift answer from the Community), you should work with the WRC to resolve this (and then hopefully post the answer back here on the Community).
Regarding Samples see also from the InterSystems IRIS documentation:
Thanks Michelle.
When I tried to use the Tools menu I was in an "Atelier element" (e.g. an Ensemble class) so I don't think that was the cause.
Just in case, I double-checked now again - I'm editing an Ensemble class and the items in the Tools menu are disabled... (in the workspace that originally gave the problem; in the newer workspace this does not happen)
Thanks Alexander.
Indeed I had the Error Log view open and saw various errors - but those were to some projects I had in my workspace that connected to servers that were offline. So I ignored them.
But now you confirmed it should work on this version - I kicked off a new workspace, defined just one project to an online server, and I got to see my Add-Ins... 
So unfortunately I don't know exactly what the problem was... but a new workspace solved it...
John,
It seems the link to the documentation you provided above is now broken (and yields an error page; it possibly worked in a previous version's docs).
I assume you meant this page:
http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GCNV_C176399
Note that apart from Export and Import options -
If you are using a %Installer Manifest for your deployment (for any environment - test or prod) - you can include in that manifest also the creation of Security elements such as Resources and Roles, etc.
For example:
<Resource
Name="%accounting_user"
Description="Accounting"
Permission="RW"/>And:
<Role
Name="%DB_USER"
Description="Database user"
Resources="MyResource:RW,MyResource1:RWU"
RolesGranted= />See more information here (in the docs).
[Defining a Role as part of a manifest is also included in an example in [@Eduard Lebedyuk]'s post here]
Hi Tom,
What is the Type of the classes that you are creating - are they Serial?
If so, this could explain the error as Serial classes cannot embed themselves (directly or indirectly).
If you can try creating Persistent classes instead of Serial let us know how that works for you.
Note - with Persistent classes, as I understand this is Ensemble, you will need to take care of deleting the various instances generated, once you purge the messages. See this Post for further details if relevant.
Hope this helps.