The following section contains an overview of the Xtract Universal server.

The server performs two main tasks:

  • Run extractions stored in the Config directory.
  • Make extractions stored in the Config directory available to the Designer.

Run Extraction on the Server #

Execution is triggered by an HTTP request. The HTTP request can be triggered from the target environment for pull destinations or from the xu command line tool (xu.exe /xu.elf), see Execute and Automate Extractions.
The process can be traced in the Extraction Log.

  1. Theobald.Xu.Web.Worker.exe checks the authentication and authorization of the request.
  2. The target environment is prepared for writing the extracted data (e.g. establish database connection, create file).
  3. The license is checked.
  4. A connection to the SAP system defined in the source is established.
  5. The data of the defined extraction type is requested.
  6. Each extracted data package is written to the target environment.
  7. After all packages are received, Theobald.Xu.Web.Worker.exe terminates the connection to the SAP system and informs the target environment that the extraction is complete.

Tip: The Theobald.Xu.Web.Worker.exe logs its actions in log files. The log files are located in the logs subdirectory of the program directory:C:ProgramFiles\XtractUniversal\logs\servers\web\worker (default) The logs can also be displayed in the Designer under [Server]>[Logs (Web Worker)].

Access the Settings using the Designer #

  1. Theobald.Xu.Rpc.Worker.exe checks the authentication and authorization of the request.
  2. Designer requests a certain setting, e.g., list of all extractions.
  3. Theobald.Xu.Rpc.Worker.exe reads the requested settings from the Config directory and sends these settings to the Designer.
  4. The user changes the settings in the Designer (e.g., destination settings).
  5. Designer sends the changed settings back to Theobald.Xu.Rpc.Worker.exe. Theobald.Xu.Rpc.Worker.exe saves the changed settings in the Config directory.

Tip: The Theobald.Xu.Rpc.Worker.exe logs its actions in log files. The log files are located in the logs subdirectory of the program directory: C:\Program Files\XtractUniversal\logs\server\rpc\worker (default).

Server Architecture #

The server runs as a Windows Service and the main process of the XU Service is XtractService.exe. The Windows Service can be managed via the Windows Services administration or the Task Manager.

XtractService.exe starts two listener processes:

  • Theobald.Xu.Web.Listener.exe
  • Theobald.Xu.Rpc.Listener.exe

The both listener processes listen on the Ports defined in the Server Settings.

Tip: The XtractService.exe logs its actions in ServiceLog.txt The log file is located in the logs subdirectory of the program directory: C:ProgramFiles\XtractUniversal\logs (default).

Theobald.Xu.Rpc.Listener.exe

Theobald.Xu.Rpc.Listener.exe waits for new connection requests from the Designer.
For each TCP connection the Theobald.Xu.Rpc.Listener.exe starts a new instance of Theobald.Xu.Rpc.Worker.exe, which processes all Designer requests coming in over the particular TCP connection, see Access the Settings using the Designer.

Tip: The Theobald.Xu.Rpc.Listener.exe logs its actions in log files. The log files are located in the logs subdirectory of the program directory: C:\ProgramFiles\XtractUniversal\logs\server\rpc\listener (default).

Theobald.Xu.Web.Listener.exe

Theobald.Xu.Web.Listener.exe waits for HTTP requests.
For each TCP connection the Theobald.Xu.Web.Listener.exe starts a new instance of Theobald.Xu.Web.Worker.exe, which processes all HTTP requests coming in over the particular TCP connection, see Run Extraction on the Server.

The following HTTP requests are possible:

  • running an extraction
  • Emptying the result cache of an extraction
  • Canceling all runs of an extraction
  • Web API requests

Tip: The Theobald.Xu.Web.Listener.exe logs its actions in log files. The log files are located in the logs subdirectory of the program directory: C:ProgramFiles\XtractUniversal\logs\server\web (default).

More information about the server can be found in the following sections:

Start Server

Ports

Server Settings