This chapter provides an insight into the printing (Legacy) process of the WebOffice extensions.

 

The following graphic shows schematically the process of printing (Legacy) with WebOffice extensions:

 

Following steps are carried out here:

 

1.Client (user)
The user presses the Print button in the client > Print request will be send from client to WebOffice Application server (Tomcat).

2.WebOffice Application Server (Tomcat)
Assemble content. Tomcat sends a request via http / REST interface to the SynOutputService SOE.

3.ArcGIS Server
The SOE provides all layers which are involved in the plot. This is an internal request of SOE, since the information is stored in the SOE's cache. The SOE loads all involved MXDs (\arcgisserver\directories\arcgissystem\arcgisinput\<ordner>\<servicename>.MapServer\extracted\v101\<servicename>.mxd) into the cache. These MXDs are then listed here: https://<servername>:[Port]/arcgis/rest/services/SynOutputService/MapServer/exts/SynSOEGateway/soecomm_handler.
The cache is created either by Reload resources or at the latest during the first printout.

4.WebOffice Application Server (Tomcat)
OutputPrintExport: Tomcat sends a request via http / REST interface to the SynOutputService SOE. At this point the dynamic print field information, the north arrow, the scale and other layout information are passed.

5.ArcGIS Server
SerializeContent: Accumulated layers are inserted into the empty SynPlotService.mxd. The SOE copies the plot template MXD (\arcgisserver\directories\WebOfficePlotTemplates\SynPlotService.mxd) to \arcgisserver\directories\arcgisoutput\SynOutputService_MapServer.

6.WebOffice extensions
The provided MXD is printed by using ArcGIS Engine and the path returns to the SOE.

7.ArcGIS Server
The SOE receives the definitive plot path and passes it to WebOffice 10.9 R4.

8.Client (user)
The final printed result is displayed in the client as an iFrame.