The follwing 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).
Tip: The process can be traced in the Extraction Log.
- Server checks the authentication and authorization of the request.
- The target environment is prepared for writing the extracted data (e.g. establish database connection, create file).
- The license is checked.
- A connection to the SAP system defined in the source is established.
- The data of the defined extraction type is requested.
- Each extracted data package is written to the target environment.
- After all packages are received, the connection to the SAP system is terminated and the target environment is informed that the extraction is complete.
Access the Settings using the Designer #
- XtractConfigServer.exe checks the authentication and authorization of the request.
- Designer requests a certain setting, e.g., list of all extractions.
- XtractConfigServer.exe reads the requested settings from the Config directory and sends these settings to the Designer.
- The user changes the settings in the Designer (e.g., destination settings).
- Designer sends the changed settings back to XtractConfigServer.exe. XtractConfigServer.exe saves the changed settings in the Config directory.
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:
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).
XtractConfigServer.exe waits for new connection requests from the designer.
Tip: The XtractConfigServer.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\config’ (default).
XtractWebServer.exe waits for HTTP requests.
For each TCP connection the XtractWebServer.exe starts a new instance of XtractRun.exe, which processes all HTTP requests coming in over the particular TCP connection.
Tip: The XtractRun.exe logs its actions in the log subdirectory.
The log files are located in the logs subdirectory of the program directory:
These are also the logs that can be displayed in the Designer under [Server]>[Logs (Run)].
The following HTTP requests are possible:
- Executing an extraction
- Emptying the result cache of an extraction
- Canceling all runs of an extraction
- REST API requests e.g., Logs, Metadata etc.
Tip: The XtractWebServer.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: