The Obix Client Manager is the default view of the ObixNetwork.

You access these properties by right-clicking the Obix Network in the Nav tree followed by clicking .
| Property | Value | Description |
|---|---|---|
| Status | read-only |
Reports the condition of the entity or process at last polling.
|
| Enabled | true (default) or false |
Activates (
true) and deactivates (false) use of the object (network, device, point, component, table, schedule, descriptor, etc.).
If If NOTE: If enabled, but not licensed for obixDriver export (status is fault), the server returns HTTP error code 500 to all oBIX client requests.
|
| Fault Cause | read-only |
Indicates the reason why a system object (network, device, component, extension, etc.) is not working (in fault). This property
is empty unless a fault exists.
|
| Monitor | additional properties |
Configures a network's ping mechanism, which verifies network health. This includes verifying the health of all connected
objects (typically, devices) by pinging each device at a repeated interval.
The Niagara Drivers Guide documents these properties. The ObixNetwork’s monitor properties verify child client component(s), which are the devices in the oBIX driver that are able to receive a ping. |
| Thread Pool | additional property | Serves as a container for the Max Threads property.
|
| Server | additional properties | Identifies a frozen container slot under the ObixNetwork. |
| Exports | no properties | Serves as a folder for data exports. |
| History Policies | additional properties | This extension serves as a container for the poll scheduler and default configuration rules. |
| Obix Client | additional properties | Represents client access to an Obix Network(server) device. |