Fiber Object Tables

Wavepoint ’s access to the underlying fiber data is only through the published service. This includes all the related fiber records stored in non-spatial, object tables. In a typical Fiber Manager implementation, these tables all start with the prefix F_ in your geodatabase.

The easiest way to verify is to switch to the List by Source pane in the Table of Contents.

• Ensure that all fiber object tables are included in the underlying map. This is particularly important if you are working in a Stored Display, as these tables are often not added. All populated fiber tables must be included in the map service, from circuits to patch panels all the way down to the front and back ports.

• Ensure all object tables that participate in fiber circuits are included in the published service. If circuit object tables are missing, there are error messages in Wavepoint when users attempt to run a trace.

If you do not see the fiber object tables in the List by Source pane, use the Add Data button to navigate to your geodatabase and add them.

It is OK to leave out empty tables. For example, the Fiber Manager sample data supports small form-factor pluggable (SFP) transceivers. If your fiber network does not incorporate those devices, it is OK to leave them out of your published map. On the other hand, adding empty tables does not harm the published service either, so leaving in empty tables does not negatively affect the application.