Verify Map Service in Wavepoint XI

Results listed on this page are mainly driven by model names that Wavepoint XI looks for in the published map service. The list of tables below might not exactly match the list of tables that exist in your published service. The names in the Fields section only list the required model name tables so they may not match the list in your published service.

To see the verify list:

1. Open Wavepoint using the URL https://servername.domain.com:6443/wavepoint/verify.

2. Use the Results table to understand whether the validation was successful or needs more work.

Examine the verification results.

The verification sections only show results for configured feature and object classes included in the published map service. After compiling the list of feature and object classes, the application then checks for the appropriate fields, relationships, and Global IDs. For example, if your company has not configured small form-factor pluggable (SFP) transceivers, then they do not display in any of the verification results.

Here is an example of condensed portions of the validation output:

The number in parentheses refer to the layer number in the published service. It does not refer to the number of records or features.

The quickest way to see the layers in the published service is to view the REST URL. To do so:

1. In ArcGIS Server Manager, click Services.

2. Locate your published service, then click the name of the service.

3. Click Capabilities, then click the REST URL.

4. Notice all the layers and tables are displayed in the service. The published order comes from the Table of Contents in the underlying map document used.

For Wavepoint XI to function properly, all red Xs must be corrected. Re-run the verification process to ensure issues have been resolved. Once all the Tables and Fields sections have green checkmarks, you may proceed with the next steps in the configuration.

What Might be Wrong?

Based on the location of any red Xs you see, one of the following situations is occurring:

• Tables

  • The table is published but is not assigned the necessary class model name.

  • The same class model name is assigned to more than one of the tables (or, more likely, multiple layers possessing the same model name were published in the map service).

• Fields

  • The field does not exist on the table.

  • The same field model name is assigned to more than one field.

• Relationships

  • Usually problems in this portion of the test results are resolved by fixing problems that appear in the Tables portion of the report.

• Global IDs

  • The GlobalID field for certain tables is not published.

  • The GLOBALID field model name is missing.