The ArchestrAnaut

In my last article, I discussed a more reliable way of writing DataChange scripts. We often write scripts that are intended to be executed if one of multiple values change state or if a certain set of conditions occur. For the latter of the two scenarios, we write a simulated OnTrue / OnFalse script in the method described by the previous article.  Both scenarios require a composite value to execute a data comparison on.

Read the rest of this entry »

In my last article, I laid out the basics on the inner workings of IAS objects and pointed out a few basic pitfalls.  The most important of these is the reliability of DataChange, OnTrue, and OnFalse scripts.  In a heavily loaded system, the AppEngine can spend too much time doing housekeeping work (i.e. checkpointing or communication with its redundant partner engine).  This leads to scan overruns which can be monitored (via object viewer or historizing) the AppEngine’s Scheduler.ScanOverrunCnt variable.

Read the rest of this entry »

In implementing the latest project, we have discovered many tips & tricks to improving reliability of ArchestrA objects.  In this series of blogs, I am going to shed a little light on some potential pitfalls in ArchestrA scripting and some useful workarounds.

Read the rest of this entry »

If you read my last entry, I got a little salty complaining about the lack of progress in System Platform releases.  Complaining without proposing solutions is not very constructive so I’d like to spend some time proposing some upgrades I’d like to see with the next release of System Platform.

Read the rest of this entry »