In the monitor for real-time data acquisition (transaction RSRDA), the daemons currently available in the system are displayed in a tree structure along with the objects assigned to them.
The monitor displays the status of the daemons and the assigned objects. This enables you to monitor the daemon and the progress of the data update into the PSA and the InfoProviders. You can perform various functions on an object in the context menu for the node.
You access the monitor by choosing Monitors under Administration in the Data Warehousing Workbench.
Overview of Daemons
The system displays the DataSource that you have assigned to each daemon. For each DataSource, the system displays the relevant InfoPackage for real-time data acquisition that contains the parameters for the data transfer. Under Unassigned Objects, the system displays any DataSources to which you have not yet assigned daemons. If you have assigned a data transfer process to the DataSource, the system displays this on the same level as the InfoPackage. Under an InfoPackage or data transfer process, the system displays the open request that posts data to the PSA table or InfoProvider. The system only displays the DTP request if the PSA contains data. If you have used the data transfer process to assign a subsequent process chain to a daemon, the system displays the process chain under the data transfer process.
For information about the navigation options in the daemon overview and the icons for the various overview levels, choose Legend.
You can trigger the system to check the background jobs and refresh the object display by choosing Goto → Refresh.
Functions on All Display Levels in the Monitor
The following functions are available on all display levels in the monitor:
This function is not available for subsequent process chains.
More information:Troubleshooting Real-Time Data Acquisition
More information:Troubleshooting Real-Time Data Acquisition
Unlike the Display Error function, which only displays the errors until they are reset, this function provides you with the application log history.
Using the application log (transaction SLG1), you can restrict the number of logs displayed to display those for a specific time period only. This makes the display easier to use.
In the application log (transaction SLG1), choose RSAP as the object and REALTIME as the subobject. Enter your user name and restrict the time period to the period for which you want to display logs.
Daemon Functions
Function | Context Menu | Menu Path | Description/More Information |
---|---|---|---|
Create daemon |
- |
Daemon → Create |
Enter an ID for the daemon. There can be up to 99 daemons assigned the numbers 01 to 99. Enter a description for the daemon. Specify the intervals (in minutes) that you want the daemon to access the data in the source and in the PSA at. |
Start data transfer for the daemon |
Context menu for an inactive daemon: Start Daemon |
Daemon → Start |
For daemons with status inactive or terminated and have objects assigned to them, you can start data transfer. If the daemon is terminated, remove the cause of the error first. Select a server or a server group. The daemon is scheduled on this server or on a server in the server group. If you do not specify a server, the system selects one for you. The daemon waits for a free background job. If the background job for the daemon is running, the daemon starts the data transfer for the InfoPackages and data transfer processes assigned to it according to the settings. |
Stop data transfer for the daemon |
Stop daemon |
Daemon →Stop |
The data transfer for the InfoPackages and DTPs that are assigned to the daemon is completed. The system then closes the requests (PSA, DTP and activation requests). The daemon displays (Stop) as the status if there are still open requests. The status of the daemon only changes to (inactive) when all requests are closed and the daemon can be stopped. If the daemon cannot be stopped, for example if you reach the maximum number of attempts to close the requests, the status of the daemon changes to (terminated). |
Display runtime information for daemon |
Runtime Information |
Daemon → Runtime Information |
For active and terminated daemons, or inactive daemons that are not assigned to an object, the following information is displayed (in addition to the daemon ID and description):
|
Display and change daemon settings |
Daemon Settings or double-click on the daemon |
Daemon → Display Daemon → Change |
The system displays the daemon ID, the description of the daemon, and the interval (in minutes) at which the daemon accesses the data in the source and PSA. You can change the description and the time (in minutes) here. |
Delete Daemon |
Delete Daemon |
Daemon →Delete |
When you delete an inactive daemon, the objects assigned to this daemon are moved to Unassigned Nodes. |
Assign data transfer processes to the DataSources that are assigned to this daemon. |
Assign DTP |
Edit → Assign DTPs |
A list of DTPs is displayed. The list is organized by DataSources that are assigned to this daemon and that are the source for a DTP. You can select the DTPs by choosing Assign. |
Define job class to define the job priority |
- |
Daemon → Settings → Job Class |
The job priority defines how the daemon jobs are distributed over the available background work processes. |
Define users for RDA Execution |
- |
Daemon → Settings → Execution Users |
Here you define which users can execute the daemon job. |
DataSource Functions
Function | Context Menu | Menu Path | Description/More Information |
---|---|---|---|
Start data transfer for the DataSource |
Start Load Process |
Edit → Start Load Process. |
The daemon executes the InfoPackage and the data transfer process for this DataSource during the next load process. Start the data transfer process in this way:
|
Stop data transfer for the DataSource |
Stop Load Process |
Edit → Stop Load Process. |
The data transfer for this DataSource is closed, and the requests (PSA, DTP and activation request) are closed. This allows you to interrupt the data transfer if, for example, you need to adjust the data flow to reflect changed requirements. |
Call DataSource maintenance |
DataSource Maintenance or double-click on the DataSource |
Edit → Maintain |
You are now in display mode for the DataSource. |
Assign DataSource to a (different) daemon |
Assign Daemon |
Edit → Assign Daemon |
Enter the daemon ID. The DataSource and the corresponding InfoPackage as well as possibly the relevant data transfer processes are assigned to the selected daemon. If the DataSource is assigned to a new daemon, it is included in the processing if the next daemon job is running. |
Delete assignment of DataSource to a daemon |
Delete Assignment |
- |
The DataSource and its related InfoPackages and data transfer processes are moved to Unassigned Objects. |
Assign data transfer processes to the DataSource |
Assign DTP |
Edit → Assign DTPs |
A list of DTPs that have this DataSource as source is displayed. You can select the DTPs by choosing Assign. If there is only one DTP, the system makes the assignment automatically when you execute this function. |
InfoPackage Functions
Function | Context Menu | Menu Path | Description/More Information |
---|---|---|---|
Call InfoPackage maintenance |
Display InfoPackage Or double-click |
Edit → Maintain |
- |
Assign DataSource for the InfoPackage to a (different) daemon |
Assign Daemon |
Edit → Assign Daemon |
Enter the daemon ID. The InfoPackage, the DataSource and any relevant data transfer processes are assigned to the selected daemon. If the DataSource for this InfoPackage is assigned to a new daemon, it is included in the processing if the next daemon job is running. |
Assign data transfer processes to the DataSource for this InfoPackage |
Assign DTP |
Edit → Assign DTPs |
A list of DTPs that have the DataSource of this InfoPackage as source is displayed. You can select the DTPs by choosing Assign. If there is only one DTP, the system makes the assignment automatically when you execute this function. |
Functions of the PSA Request
Function | Context Menu | Menu Path | Description/More Information |
---|---|---|---|
Close Request |
Close Request |
- |
You can close a request if the daemon is terminated or has status active. SeeClosing Requests in the Monitor for Real-Time Data Acquisition. |
Display conditions for automatically closing the request |
Request Conditions |
- |
For open requests, the system displays header information and the threshold values set in the InfoPackage for automatically closing the request. |
Call request monitor |
Monitor |
Goto → Monitor |
The system displays the monitor for the selected request. |
Data Transfer Process Functions
Function | Context Menu | Menu Path | Description/More Information |
---|---|---|---|
Call data transfer process maintenance |
Display DTP |
Edit → Maintain |
DTP maintenance display mode appears. |
Assign DataSource for the data transfer process to a (different) daemon |
Assign Daemon |
Edit → Assign Daemon |
Enter the daemon ID. The data transfer process and the corresponding DataSource as well as the InfoPackage and possibly further related data transfer processes are assigned to the selected daemon. |
Delete assignment of the data transfer process to a DataSource |
Delete Assignment |
- |
The system no longer displays the data transfer process in the monitor for real-time data acquisition. |
Call InfoProvider administration |
Manage InfoProviders or double-click on the Data Target column |
- |
- |
Assign process chains that follow the data transfer process to the daemon |
Assign Subsequent Process Chain |
- |
In the dialog box, select a suitable process chain. You can only select active process chains. Note that the subsequent process chain has to include a start process with scheduling option Start Using API. The process chain starts when the daemon closes a request. This allows you to link further processing and update processes to real-time data acquisition. You can assign more than one subsequent process chain to a data transfer process. |
Generate a process chain for repairing the data transfer from the PSA to the InfoProvider |
Generate Repair Process Chain |
Edit → Repair Chain → Generate |
If the daemon terminated the data transfer due to an error in the transformation, for example, and you have corrected the error, you can generate a repair process chain. The repair process chain consists of a start process, a standard data transfer process, and possibly activation of data in the DataStore object and in the subsequent process chains. |
Execute Repair Process Chain |
Execute Repair Process Chain |
Edit → Repair Chain → Execute |
Information about using the repair process chain:Troubleshooting Real-Time Data Acquisition |
If you generated a repair process chain: Display repair process chain |
Display repair process chain |
Edit → Repair Chain → Display |
The maintenance display mode for this process chain appears. |
If you generated a repair process chain: Delete Repair Process Chain |
Delete Repair Process Chain |
Edit → Repair Chain → Delete |
- |
DTP Request Functions
Function | Context Menu | Menu Path | Description/More Information |
---|---|---|---|
Close Request |
Close Request |
- |
You can close a request if the daemon is terminated or has status active. SeeClosing Requests in the Monitor for Real-Time Data Acquisition. |
Display conditions for automatically closing the request |
Request Conditions |
- |
For open requests, the system displays header information and the threshold values set in the InfoPackage for automatically closing the request. |
Call InfoProvider administration |
Manage InfoProviders or double-click on the Data Target column |
- |
- |
Call monitor for DTP request |
Monitor |
- |
The system displays the monitor for the selected request. |
Subsequent Process Chain Functions
Function | Context Menu | Menu Path | Description/More Information |
---|---|---|---|
Call process chain maintenance |
Maintain Subsequent Process Chain |
- |
More information:Process Chain |
Delete assignment of process chain to daemon |
Delete Assignment |
- |
If you delete the assignment, the daemon does not control the process chain processing anymore. |