IBMX Recommendations

IBMX is the AVEVA Batch Management application that provides I/O to AVEVA Batch Management from System Platform (SP). AVEVA Batch Management tags are linked to WAS using the AVEVA Batch Management TagLinker application. Tags can be linked to I/O through Device Integration (DI) objects or through Application Object attributes (which are then linked to I/O through DI objects).

This section discusses recommendations that need to be followed to get reliable I/O when using IBMX. If these recommendations are not followed, AVEVA Batch Management could get stale data causing batch execution problems and/or writing of old values to batch history.

If you are using WSP 2012 or greater, the "LMX Initializing Quality on Suspend Registry setting" is the recommended approach. It can influence other aspects of the system (i.e. Graphic updates may initially not show good quality), so that needs to be considered as well. For more information, refer to "Lmx Initializing Quality On Suspend Registry Setting".

Advise All

This applies to all versions of AVEVA Batch Management running with all versions of System Platform (SP). The "Advise All" option of IBMX causes all tags linked to System Platform (SP) to be "advised" at start up. Since all tags remain advised, the tag value updates to AVEVA Batch Management depend on the various scan groups where those tags originate. It is important to make sure your Phase Parameter scan groups will provide any final value changes before the Phase Status scan group sends the "Phase Done" status.

Prior to InBatch 9.5, IBMX operated in a "progressive advise all" manner, meaning as each phase is run, its tags remained on "advise". So, it was basically always running as if "Advise All" was set. In InBatch 9.5 (and later), tags are "Unadvised" when not in use, so "Advise All" needs to be specifically set.

NOTE: "Advise All" is only appropriate for smaller sets of tags. The appropriate number of tags depends on the design and capabilities of the overall system platform (I/O throughput capabilities).

Batch Management Specific DI Object

If you are using InBatch 9.5 (or greater) and an Application Server version prior to System Platform 2012, you will need to use "Advise All" as described above or link AVEVA Batch Management tags to point to their own DI object(s). This can include a set of Redundant DI Objects which point to other real DI Objects, but the path to the I/O should NOT be shared with other I/O clients (i.e. App Object attributes, scripting, graphics, etc.). The endpoint DA Servers or I/O Servers can be shared by multiple DI Objects, which keep the extra load off the DA Servers or I/O Servers themselves.

With this approach, it is still important to consider the Parameter and Phase tag scan groups to make sure Parameter value updates are sent out before the "Phase Done" status updates. However, because this approach typically gets "fresh" data when doing a "Read" at the end of a Phase, it is less of an issue.

Lmx Initializing Quality On Suspend Registry Setting

If you are using InBatch 9.5 (or greater) and System Platform 2012 (or greater), you can use either of the previous approaches. You also have the option of linking tags to Application Object attributes and/or DI Objects that are shared by other I/O clients (scripting, graphics, and so on). To do this, you will need to make a registry setting on every platform with which InBatch communicates (typically every platform in the Galaxy). This feature enables the system to set I/O quality to "Initializing" when going from the "suspended" state to the "activated" state and while waiting for the first data update. Without this set, InBatch will likely receive old data before receiving the first data update.

• The key for a 32-bit OS is: \HKEY_LOCAL_MACHINE\SOFTWARE\Archestra\ Framework\Platform

• The key for a 64-bit OS is: \HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Archestra\Framework\Platform

• The value under this key will be a DWORD type value named "InitializingQualityOnSuspend". The feature is enabled only if the value exists under the registry key and if the value of the DWORD is non-zero

• You should reboot after making this change

With this approach, it is still important to consider the Parameter and Phase tag scan groups to make sure Parameter value updates are sent out before the "Phase Done" status updates.