(DI-2208) Collector for cross-system RFC locks
This collector collects information about cross-system RFC locks. It extracts information the same way as transaction code SMCL. It can be parametrized and it is using input table, which has the same select options as SMCL transaction. Additionally, the collector has implemented an enhancement spot, which could be used to automatically release these locks.
The technical name of the collector is /DVD/MON_CL_COL_RFC_LOCKS.
Default KPIs delivered with this collector
The following default KPIs are delivered with this collector:
KPI name | Description | Unit | Detail table |
---|---|---|---|
RFC_LOCK_ALL | All cross-system RFC locks | Count | Yes |
RFC_LOCK_LONG | Cross-system RFC locks running longer than 5 minutes (by default) | Count | Yes |
Input table
Collector uses input table /DVD/MON_LCK_RFC where user can specify what details will be extracted into detail table /DVD/MON_S_RFC_LOCKS.
When content for Input table /DVD/MON_LCK_RFC is not defined, default token manager is loaded using function module ‘CSLTM_GETTOKENMANAGER’ and all existing locks that are no more than day old (by default) or all locks since last run are reported.
Wildcards are supported for detail table /DVD/MON_LCK_RFC for fields TOKEN_HOME_SYTEM, OBJECT_TYPE, USERNAME to reflect functionality of SMCL T-Code. MSY and MNU must be specified.
MSY | Remote system of token manager |
MNU | Number of token manager |
TOKEN_HOME_SYTEM | Home system of token manager |
OBJECT_TYPE | Key for lock object type |
USERNAME | User who initiated token lock |
Parameters
The following parameters are used for this collector:
Parameter name | Description |
---|---|
RFC_LOCK_LONG_THRESHOLD | Used for KPI RFC_LOCK_LONG. Specifies how many seconds must lock exist to be reported as long running. Default 300 seconds (5 min) |
RFC_LOCK_DAY_THRESHOLD | Specifies how many days should collector look back to collect lock details. By default, when collector runs for first time or last run timestamp is not defined, this threshold is used. Otherwise all locks are collected since last run. |
Detail table
The collector provides a detailed table of RFC Cross System Lock Details. The technical name of the detail table is /DVD/MON_S_RFC_LOCKS
RFC Cross System Lock Details reports all cross-system RFC locks currently in place created in the last 24 hours.
Technical name | Description |
---|---|
TOKEN | Token |
TOKEN_MANAGER | System of Token Manager |
TOKEN_MANAGER_NUM | Number of Token Manager |
STATUS | Status of Assignment Token Manager to Token |
USERNAME | User Who Initiated Token Lock |
LAST_TIME_ACCESS | Last access timestamp for RFC lock formatted |
AGE | Amount of minutes lock was not accessed |
EVENT_TIMESTAMP | Same as field LAST_TIME_ACCCES - only used for overriding AppDynamics analytics timestamp |
Enhancement Spot
You can use collector run to automatically release all locks collected over the past 24 hours. There is an enhancement spot with BAdI /DVD/MON_BAD_RFC_LOCKS, with an interface that contains the method RELEASE_LOCKS.
In created implementation call function module CSLAR_TKCHANGE with parameters already provided through the interface:
FM Parameter | Variable |
---|---|
PCOMM_ROUTING_INFO | IS_ROUTING_INFO |
BNAME | SY_UNAME (or any name you wish to release locks under) |
PUCOMM | ‘DELE’ |
PCOMM_CALLED_CPPS | IT_CALLED_CPPS |
TO_CHANGE_TOKEN | IT_TOKENS |
This function module will automatically release all RFC locks collected by the collector. If you wish, you can also implement additional functionality in this implementation (logging, another action that needs to be done after lock release, etc.).
Example Code for releasing all collected locks:
CALL FUNCTION 'CSLAR_TKCHANGE'
EXPORTING
pcomm_routing_info = is_routing_info
bname = sy-uname
pucomm = 'DELE'
TABLES
pcomm_called_cpps = it_called_cpps
to_change_token = it_tokens
EXCEPTIONS
no_connection = 1
no_alobject = 2
internal_error = 3
OTHERS = 4.
IF sy-subrc <> 0.
/dvd/cx_mon_exception=>raise_from_system_message( ).
ENDIF.