New post
AllAccepted answers
Julian Matthews · May 29, 2018

The accepted answer would probably be your best shot.

Say for example you wanted a count of all messages that have come from a service called "TEST Inbound", you could use the SQL query option (System Explorer>SQL) to run the following:

SELECT count(*)
FROM Ens.MessageHeader WHERE SourceConfigName = 'TEST Inbound'

If you wanted to put a date range in as well (which is advisable if what you're searching is a high throughput system and your retention is large):

SELECT count(*) Total
FROM Ens.MessageHeader where SourceConfigName = 'TEST Inbound' AND TimeCreated >= '2018-04-30 00:00:00' AND TimeCreated <= '2018-04-30 23:59:59'
Julian Matthews · May 29, 2018

Hi Gadi.

Glad to hear you have something in place now.

I guess a task is better for specifying the exact time for the event to run rather than every x number of seconds, as the timing could go out of sync if the service was restarted at any point.

For the setup I have, because I want to check the status of the drive free space (and I also check a specific folders files to alert if any of them have existed for more than 5 minutes) it makes sense to just let the Call interval run every x seconds.

Julian Matthews · May 24, 2018

I use a similar approach to Edwards answer (using a BS that runs every x seconds), but for alerting when freespace on my drives fall below a specified value.

I'm not sure if my approach is the most efficient to your requirement, but I would do something like this in the Service:

  • Query the table and sort it so you get the most recent result at the top (I'm assuiming the dateTime field is suitable for this)
  • Take a Snapshot of the results, and and get the first datetime result.
  • Compare it to the system datetime
  • Send an alert to Ens.Alert if the difference is more than 24 hours
Julian Matthews · May 18, 2018

Thanks Joyce, I made contact with them instead of support, and after a webex the solution was found!

It turns out the performance issues I had been getting when adding the entire namespace was because I had included all of the system folders (ens, enslib, EnsPortal, etc). So on each launch, Eclipse was then reindexing the entirety of the core files in each namespace.

Julian Matthews · Apr 4, 2018

Hi Bob. Do you have KeepIntegrity selected?

I ask because the only thing I can see which might point in the right direction is that the selection of message headers when KeepIntegrity is selected does a "select top 100000000" and your Ens.MessageBodyS is a digit greater (10 digits vs 9), so it could be that the items are somehow being missed? If this is the case, running the purge without the Keep integrity selected might work?

Also, I assume you are getting a success status from the task running?

Julian Matthews · Apr 4, 2018

Hi Bob.

These will be picked up by either Purge running the all command, or by selecting "Messages" for TypesToPurge in either one.

The MessageBodyS should be purged when the "BodiesToo" tick box is selected in the task. The description for the BodiesToo  option is: "Delete message bodies whenever their message header is deleted. This is off by default because some Productions may use message objects that are part of a larger environment and not transitory." so it may be that your task was left with the defaults and this has built up.

Julian Matthews · Apr 4, 2018

Hi Bob.

I ran a comparison against the two Tasks to find the answer.

Basically they're almost identical, except that Ens.Util.Tasks.PurgeMessageBank includes the ability to purge "Message Bank Events" and "Message Bank Messages" using the "ALL" Parameter in TypesToPurge or by individually selecting them. So using Ens.Util.Tasks.Purge with all selected will not touch the Message Bank.

My guess would be that Intersystems either added Ens.Util.Tasks.PurgeMessageBank when the Message Bank functionality became available and didn't want to edit the Ens.Util.Tasks.Purge task so that ALL started to include purging the message bank, or Ens.Util.Tasks.Purge exists to be able to have a task which can purge all except the message bank so that customers that would like to purge all except the message bank can do so with one task rather than 7 separate tasks.

Julian Matthews · Mar 16, 2018

Hi Mark.

After throwing in an if statement for the Priority variation and some other local tweaks I have this working perfectly, so thank you for sharing.

I also added the Token and User Key as a setting to be set from the Operation within Ensemble.

It would be good to catch up outside of the Intersystems forums sometime soon.

Cheers!

For anyone interested in adding the Token and User Key

So I included before the method:

Property Token As %String;

Property User As %String;

Parameter SETTINGS = "Token, User";

And then the http request parameter became:

        Do httprequest.SetParam("token",..Token)
        
        Do httprequest.SetParam("user",..User)

This leaves the token and user key to be configured within Ensemble via the Management Portal:

Julian Matthews · Feb 9, 2018

Hi Lorraine.

I think the issue is that the Constraint is not set for the condition to be able to reference the filename. I see that you have added a comment to another post which explains how to do this, but it stops short in explaining fully. Fortunately, Joshua Goldman then links to another post where he goes in to more detail.

I'll copy and paste it here, and include the link.

https://community.intersystems.com/post/how-route-file-based-file-type

  1.  Define a business rule. Make it a General Message Routing Rule and have the assist class be EnsLib.MsgRouter.RuleAssist.
  2. Add a rule to the rule set and double-click Constraint. Specify the rule class Persistent > ENS > StreamContainer
    That's the message class used by the pass-through file service/operation. You can also specify the business service as the source.
  3. Double-click  condition, and in the expression editor specify Document.Type or Document.OriginalFilename, add an operation, and a  value.
  4. Send it to the correct operation.
  5. Define a router business process and specify the rule you just created.
  6. Connect the pass-through file service to the router.