Navigation:  How To > How to Configure... > Printing >

Put Markup Feature Classes into SDE

Previous pageReturn to chapter overviewNext page

When having issues with the markup file-geodatabases, move the markup feature classes used by the SynOutputService into an eGDB (SDE).

Note: For demo and test purposes, the markup feature classes of the SynOutputService can be left in the fGDB, but for productive use, i. e. as soon as there is a load on the server, they must always be transferred to an SDE database.

 

Perform the following steps:

1) Open the SynOutputService.mxd in ArcMap and remove the three layers from file-geodatabases syn_markup_02, syn_markup_03 and syn_markup_04.

Note: VertiGIS recommends the usage of the SynOutputService.mxd from the DVD, because this MXD has been prepared in a respective format.

 

Remove layers from fgdb syn_markup_02, syn_markup_03 and syn_markup_04 in SynOutputService.mxd

Remove layers from fgdb syn_markup_02, syn_markup_03 and syn_markup_04 in SynOutputService.mxd

 

2) Add a connection to the SDE and create a new feature dataset.

Create a new feature dataset in SDE

Create a new feature dataset in SDE

 

3) For the new feature dataset choose as coordinate system WGS_1984_Web_Mercator_Auxiliary_Sphere.

Choose coordinate system for the new feature dataset

Choose coordinate system for the new feature dataset

 

4) Copy the four feature classes from the file geodatabase syn_markup_01.gdb (by default in C:\arcgisserver\directories\ServiceDocuments\SynOutputService\syn_markup_01.gdb) to the new feature dataset.

Note: Do not use the import function in that case, because the field values will not be correctly transferred. Use instead copy/paste.

 

Copy feature classes to new feature dataset in SDE

Copy feature classes to new feature dataset in SDE

 

5) Adjust the data sources for each feature class from layer syn_markup_01 by pointing to the new feature classes in SDE.

Adjust data sources of each feature class of layer "syn_markup_01"

Adjust data sources of each feature class of layer "syn_markup_01"

 

Adjust data sources of each feature class of layer "syn_markup_01"

Adjust data sources of each feature class of layer "syn_markup_01"

 

6) Finally overwrite the existing map service SynOutputService.

Note: If you get troubles while overwriting the SynOutputService please delete the existing SynOutputService from ArcGIS Server and publish a new one. In that case please consider the settings from Publish the SynOutputServiceAdd Dynamic Workspaces to SynOutputService and Activate SOE on a Map Service.

Overwrite the existing SynOutputService

Overwrite the existing SynOutputService

 

Assure having performed all steps correctly by calling the REST interface of the SynOutputService in the browser: http://<server>:6080/arcgis/rest/services/SynOutputService/MapServer

If the structure under "Layers" looks like in the screenshot, the steps have been performed correctly and the markup feature classes have been shifted to the SDE.

Note: Please consider the correct order of the layers from the screenshot.

If this order does not match the order from the screenshot, please republish the SynOutputService from step 1.

If the order still is not correct, try the following workaround:

- 'Save A Copy' from the SynOutputService.mxd as 'ArcMap 10.1 and 10.2 Documents (*.mxd)'

- Open the Copy

- Overwrite the existing service based on the copy

- Check the order of the layers again

 

CORRECT: REST interface of SynOutputService

CORRECT: REST interface of SynOutputService

CORRUPTED: SynOutputService in der REST-Schnittstelle

CORRUPTED: SynOutputService in der REST-Schnittstelle

 

For every output the markups will be managed in the SDE.

 

Note: Please consider, that you only have to put the Markup-Feature Classes into SDE and not also the Upload-Feature Classes. Putting the Upload-Feature Classes into SDE could affect the WebOffice upload-functionality in a negative way!

Note: If the credentials for the sde connection have been changed, the output mxd might not be able to read out the connection correctly. In that case please republish the SynOutputService.mxd