Pre-integration R2 station changes

Before beginning an oBIX integration, consider R2 station changes that can improve performance. The following changes apply:

Reducing R2 station resource count

Typically, the reason for integrating an R2 JACE in an Supervisor is to provide access to it via AX PxPages on the Supervisor. With this goal in mind, in many cases the R2 station’s resource count can be reduced by removing its GxPages and associated Gx objects. For a heavily loaded R2 station, reducing its station size may be the only way of accommodating the R2 oBIX server.

Reducing R2 swid lengths

The depth of the R2 tree is of importance in relation to the performance of the Ax Client. Obviously, more data being transmitted from the R2 Server to the Ax Client increases the time between updates. Application developers typically would like to keep re-engineering of the R2 station database to a minimum. However, simple name changes to shorten R2 swids (system wide identifiers) can result in a large benefit.

Example 1. Example

Original swid:

/AcmeBuildingOneFirstFloor/LonTrunk/AirHandlingUnit1/VariableAirVolumeUnits/Boxes/Room101/Room101VA

Shortened swid:

/Acme1stFlr/LT/AHU1/VAVs/Boxes/Rm101/Rm101

In addition to increasing the performance of the data transfer, reducing the length of a swid reduces the amount of memory required to serve up the data. This topic reflects a tendency to sometimes “over-engineer” a station database by creating unnecessarily deep hierarchies. Of course some hierarchy is necessary, but more is not necessarily better...