Here, the administrator can manage the cache keys and objects. Information on the current portfolio and objects can be derived. Debugging can be enabled to identify possible error sources.
Here, the administrator can see four tabs:
Tab |
Description |
Cache Object List |
Displays a list of xRPM objects that are cached in server memory. Cache keys can be generic or user-specific. |
Current Portfolio/Object |
Displays information on current xRPM portfolio and current object. |
RFC Debugging |
When activated, the RFC functions used by the system, since activation, are displayed along with an indication whether the result was successful. |
Live Logging |
Displays a log of the Methods used in the recent transactions, along with the path and a brief explanation. |
Cache Object List
Here, the administrator can identify the cache object that is loaded in memory. The cache object can be generic or user-specific. To make any backend configuration changes effective, the administrator can invalidate the corresponding cache key. The system then reloads the most current information from the configuration, for all objects connected with the invalidated cache key.
The table displays the following fields.
Field |
Explanation |
Cache Key |
This identifies the cache object that is loaded in memory. |
Cache Object |
Lists objects that are currently in the server memory. |
User ID |
Displays the used-id of user-specific objects or the generic object name for the generic objects. |
Refresh |
Refreshes the list to add objects that may have been added to the memory since the last display. |
Invalidate Selected Cache |
To remove the selected object(s) from server memory and re-fetch the latest configuration, select cache key and click this button |
Invalidate Entire Cache |
If this button is clicked, a Confirmation box opens: Are you sure you want to invalidate the entire cache objects? Click either: · Yes: invalidates the entire cache. · Cancel: cancels the command. Caution should be exercised in invalidating all cache because the entire cache will be deleted and the user may receive an error. However, it is a temporary state. As the application is used, the cache building is resumed. (Once you click on anything, the cache building resumes, thus the error state is resolved.) |
Navigation Menu icon (top right, above the list) |
To switch to another option under Cache Administration, click this icon and select the desired option from the drop down list. |
Scroll |
The triangles at the bottom of the displayed list facilitate scrolling. The three triangles pointing down help scroll down one row at a time, one page at a time and to the last page, respectively. The three triangles pointing up perform the same function for scrolling upwards. The triangles are inactive if all entries fit on a single pate. |
Click on any other option to move out of this option.
Current Portfolio/Object
Here information on the current portfolio and the current object is displayed in two boxes. The information displayed is useful in tracking and troubleshooting.
Type |
Field |
Explanation |
Current Portfolio |
Portfolio GUID |
This is the unique identifier for the current Portfolio. |
Portfolio Name |
Name of the current portfolio. |
|
Current Object |
GUID |
The unique identifier for the current object. |
ID |
Id of the current object. |
|
Name |
Name of the current object. |
|
Type |
Type of the current object. |
Click on any other option to move out of this option.
RFC Debugging
When activated, the remote function calls made since activation are displayed in tabular format. For each RFC, the corresponding input and output data is displayed in the boxes below the table
Checkbox |
Explanation |
Activate RFC debugging |
Check this box to activate the debugging. Click Apply to start the debugging. Uncheck this box followed by the Apply button to deactivate the debugging. |
Number of RFCs to log |
Enter the number of RFCs to be displayed at a time and click the Apply button next to it. The table below will be updated to reflect as many rows. If, the number of RFCs exceed the number specified, a scroll option shall automatically appear. |
The table displays the following information
Field |
Explanation |
Load |
This button adds to the list any new RFCs that may have been made since the last display. |
Clear List |
This button clears the RFCs from the list. |
Result |
Indicates, with a symbol, whether the remote function call was successful. |
Function |
The name of the remote function call. |
Runtime in ms |
The run time, in milliseconds, taken by the remote function call. |
Size in byte |
The memory size taken by the remote function call in the server. |
User |
User who initiated the remote function call. |
Time of Execution |
Time at which the remote function call was made. |
scroll |
The triangles at the bottom of the displayed list facilitate scrolling. The three triangles pointing down help scroll down one row at a time, one page at a time and to the last page, respectively. The three triangles pointing up perform the same function for scrolling upwards. |
Upon selecting a particular remote function from the table above, the boxes below display the corresponding information in xml format. Model is the data repository, and Context refers to the view of the current context.
Model Input |
Here you can see the information being updated to the model. |
Model Output |
This displays the information being fetched from the model. |
Context Input |
This displays the corresponding context specific information being saved to the back-end system. |
Context Output |
This displays the corresponding context specific information fetched from the back-end system. |
Download result |
This link displays the actual xml code used by the RFC. |
Click on any other option to move out of this option.
Live Logging
Activating this feature enables tracking of the methods being used by the system during the time this feature is activated. To use this feature:
Checkbox |
Explanation |
Live Logging |
Click ON to activate live logging. Click OFF to disable. |
The box that appears next, displays the full text description of the Method selected in the table below.
Once live logging is activated, the table displays information as follows:
Level |
Indicates the 5 levels of severity – Info, Warning, Error, Fatal, Java Exception. |
Method |
Name of the method being executed. |
Location |
Lists the path from where the above method was executed. |
Text |
Displays the first 40 characters of the message. To see the whole message, select the entry and the entire message is displayed in the box above the table. |
scroll |
The triangles at the bottom of the displayed list facilitate scrolling. The three triangles pointing down help scroll down one row at a time, one page at a time and to the last page, respectively. The three triangles pointing up perform the same function for scrolling upwards. The triangles are inactive if all entries fit on a single pate. |
Click on any other option to move out of this option.
The first column of each row has a checkbox which is used for selecting the cache key in that row.
· To select a single cache Key from the list, click on the corresponding checkbox.
· To select multiple cache keys, hold down the CTRL key and click the checkboxes corresponding to the cache key.
· To select a block of cache keys, hold down the SHIFT key and check the first and last cache key of the block.