Bridging Data Points
The Bridging point manager exposes its runtime state as ordinary GENESIS data points under the bwx: prefix and can be found in the data browser under Bridging, so any client that can read a point can read Bridging status, and any client that can write a point can start a transaction.
For what they mean and how to use them, see Bridging Logs and Statistics; to display them, see Monitoring Bridging Activities as a Client.
All the points below are browsable in Data Browser and Data Explorer under Bridging, so you rarely need to type a point name in full.
Server Statistics
These counters describe the transaction engine as a whole and are addressed relative to the point manager—for example: bwx:@@RunningTransactionCount.
|
Point |
Description |
|---|---|
|
|
Number of transaction requests that the engine has received. |
|
|
Number of transactions executing now. |
|
|
Number of transactions that completed with a success result. |
|
|
Number of transactions that completed with a failure result. |
|
|
Number of transactions that were canceled before completing. |
|
|
Number of requests that the engine declined, for example because a similar transaction was already running or the queue was full. |
|
|
Number of transactions currently hibernating. |
|
|
Number of requests waiting in the queue. |
|
|
Current load level of the engine, as reported to a distributed scheduler. |
|
|
Indicator of whether the point manager is online. |
Per-Transaction Points
These points are exposed beneath each transaction—for example, bwx:MyFolder/LogTankValues.@@LastExecutedStatus.
|
Point |
Description |
|---|---|
|
|
Writable. Writing a non-zero value submits the transaction for execution. Bind it to a button or a data entry object with DataEntry enabled to give an operator a manual start. |
|
|
Indicator of whether the transaction is currently executing. |
|
|
Local time at which the transaction last executed. |
|
|
UTC time at which the transaction last executed. |
|
|
Result of the most recent execution. |
|
|
How long the most recent execution took. |
|
|
Last error text reported by the transaction. |
|
|
Log record of the most recent execution. |
|
|
Log records of the recent executions. |
|
|
Scheduling state of the transaction. |
@@LastExecutedStatus Values
The @@LastExecutedStatus tag is a system status tag provided by Bridging for each transaction. It indicates the execution result or state of the most recent transaction run.
The following status codes are available:
|
Status Code |
Status |
Description |
|---|---|---|
|
0 |
In queue |
The transaction is queued or waiting for execution. |
|
1 |
Running |
The transaction is currently executing. |
|
2 |
Cancelled |
The transaction execution was canceled or aborted before completion. |
|
3 |
Executed successfully |
The transaction completed successfully without errors. |
|
4 |
Executed and failed |
The transaction completed but failed due to an error. |
Variable Points
Global and local variables are addressed as datasets, one cell at a time. Rows and columns are zero-based, and a column may be given by index or by name. Learn more
|
Point |
Description |
|---|---|
|
|
A cell of a global variable. Readable and writable. |
|
|
A cell of a local variable, in the context of the running transaction. |
Example: read the first cell of a global variable named Debug.
An Automatic Variable recalculates its value when read and cannot be written. An attempt to write one is refused and recorded in the trace log.
The .Query Dataset Point
bwx:.Query is a dataset point that returns transaction log details for a Table control or any other dataset consumer. Select the query table you want, choose the fields to return as columns, and filter on the execution you are interested in. Learn more
|
Query table |
Description |
|---|---|
|
|
One row per activity execution within a transaction instance. |
|
|
One row per data step recorded within an activity. Available only when Execution Log includes data step tracing. |
ActivityTraces returns the following fields.
|
Field |
Description |
|---|---|
|
|
Identifier of the transaction instance. Filter on this field to scope the result to one execution. |
|
|
Identifier of the activity entry within the instance. |
|
|
Time at which the entry was written. |
|
|
Name given to the activity in the diagram. |
|
|
Type of the activity. |
|
|
State of the activity execution. |
|
|
Time at which the activity started. |
|
|
Time at which the activity ended. |
|
|
How long the activity ran. |
|
|
Error reported by the activity, if any. |
|
|
Entry identifier of the activity that ran next. |
DataStepTraces returns the following fields.
|
Field |
Description |
|---|---|
|
|
Identifier of the transaction instance. |
|
|
Entry identifier of the activity that produced the step. Filter on this field together with |
|
|
Identifier of the data step entry. |
|
|
Time at which the step was recorded. |
|
|
The step the activity performed, such as a parameter or expression evaluation. |
|
|
The value or message the step produced. |
Performance Counters
The Bridging point manager also publishes Windows performance counters, which report the same engine measurements to system monitoring tools.
|
Counter |
Description |
|---|---|
|
|
Transaction requests received. |
|
|
Transaction requests processed. |
|
|
Transaction requests currently queued. |
|
|
Transactions currently executing. |
|
|
Transactions currently hibernating. |
|
|
Size of the engine's transaction queue. |
|
|
Size of the scheduler queue. |