Requirements

Each R2 host (JACE, Web Supervisor) should be running Niagara 2.301.522 or later, have the obix module 2.301.527c.beta or later installed, and has its license enabled for the “obix” feature. Your JDE (WorkPlace Pro) should also be at 2.301.522 or later.

Optionally, each R2 host can also have an “obixInternal.properties” file in its nre\lib folder. This helps when doing Obix proxy point discovers from the AX client side, in coordination with an AX feature to hide rarely accessed (internal) properties. See About Discover “Include” options for related details.
The Supervisor host must be running NiagaraAX 3.1.31 or later, have the installed modules:
- obix 3.3.22 or later
- obixDriver 3.3.28.2 or later
The Supervisor also requires the “obixDriver” feature in its license. Any AX JACE that needs direct Obix client access to any R2 JACE also has the same requirements.

Loading effects of oBIX integration

Please be aware that oBIX creates an additional load on R2 stations. Tests indicate the following:

A VxWorks (JACE) R2 station with 40 percent idle time and 500,000 resources consumed can accommodate 1000 AX Obix proxies in a watch.
A VxWorks (JACE) R2 station with 30 percent idle time and 500,000 resources consumed can accommodate 500 AX Obix proxies in a watch.

Inspect idle time by pointing a browser to: http://ipAddress:3011/system/spy

Determine resource count by pointing a browser to: http://ipAddress/prism/resources

Please note that the above results depend on how the AX client is reading the values, that is, is it polling all of the points all of the time, or only some, etc. “Your results may vary.” In addition, the watch interval (adjusted on the AX client side) plays a role in the loading of an R2 station.

For related details, see Pre-integration R2 station changes, and Client polling timing.