SAP IDM Monitor
Monitoring of SAP Identity Management dispatchers, job logs, provisioning queue, packages, identities
General
| Executable | SAP_IDM_Monitor.exe |
| Connection method | ODBC |
| Ports |
|
| Lookup files |
|
Default parameters
| Parameter name | Possible values | Default | Description |
|---|---|---|---|
| Host | <ip> | <hostname> | empty | Hostname or IP of the target system. If you use a virtual hostname on your SAP servers, please use also the virtual host to connect. |
| DBName | string | empty | Name of the database |
| DBUsername | string | empty | Database user |
| DBPassword | string | empty | Password of the database user |
Sensor-specific parameters
| Parameter name | Possible values | Default | Description |
|---|---|---|---|
| DBType | ASE | ORACLE | MSSQL | ASE | Defines which database type is used |
| DBSchemaPrefix | string | MXMC_db.dbo | Schema prefix of the IDM database
|
| Minutes | number | 60 | Count of past minutes to check for job logs |
| AdditionalQueries | <file1>,<file2>,<file3>,… | NONE | Additional queries to create custom channels. The queries have to be specified as .sql files in the folder SAP_IDM_Monitor. File syntax:
|
| CustomOnly | false | true | false | Defines wether only the queries from the AdditionalQueries parameter should be used. |
Channels
| Channel name | Description | Lookup file |
|---|---|---|
| Dispatcher <Name> state | Current state of the dispatcher <Name>. The state of a dispatchers where the LAST_VISITED timestamp is older than two minutes will be recognized as UNKNOWN. | itesys.sapidmmonitor.dispatcherstate.ovl |
| Dispatcher <Name> JRE log level | Current JRE log level of the dispatcher <Name> | itesys.sapidmmonitor.dispatcherloglevel.ovl |
| Log errors | Number of errors in the job log within the past <Minutes> | |
| Log warnings | Number of warnings in the job log within the past <Minutes> | |
| Checked-out packages | Number of checked-out packages. (The checked-out packages and the current developer are also shown in the sensor message.) | |
| Entries in provisioning queue | Number of entries in the provisioning queue | |
| ID Store <Name> active identities | Number of active identities per ID store | |
| Inactive Repositories | Number of inactive repositories | |
| Housekeeping status | Displays the status of enabled housekeeping jobs. A job with an empty schedule time will be recognized as failed. | |
| Jobs/Tasks in error state | Displays the count of jobs and tasks in status error. | |
| <AdditionalQuery> | Result of additional query defined in a .sql file for the parameter <AdditionalQueries> |
Lookup values
Values, states and texts defined in the lookup files of this sensor.
Lookup file: itesys.sapidmmonitor.dispatcherloglevel.ovl
| Value | State | Description |
|---|---|---|
0 | OK | None |
1 | OK | Error |
3 | OK | Info |
4 | OK | Extended |
7 | OK | Debug |
Lookup file: itesys.sapidmmonitor.dispatcherstate.ovl
| Value | State | Description |
|---|---|---|
0 | OK | Running |
1 | Error | Stopped |
2 | Warning | Suspending |
3 | Warning | Suspended |
4 | Warning | Resuming |
5 | Error | Unknown |
Lookup file: itesys.sapidmmonitor.housekeepingstate.ovl
| Value | State | Description |
|---|---|---|
0 | OK | OK |
1 | Error | Not OK |
Preparation
If you use a monitoring user which has no access to the Identity Management database schema, please use the following SQL commands to give the necessary access:
grant select on mc_dbschema to <user>
grant select on MC_Dispatcher to <user>
grant select on MC_LOGS to <user>
grant select on mc_jobs to <user>
grant select on mc_package to <user>
grant select on MXP_Provision to <user>
grant select on idmv_vallink_basic_active to <user>
grant select on MXI_IDStores to <user>
grant select on mc_proc to <user>
grant select on mc_sched_rule to <user>
grant select on mc_sched_item to <user>
grant select on MC_REPOSITORY to <user>
warning
Also check permissions for additional queries you defined in the parameter <AdditionalQueries>.
Important notes
warning
Please check the limits if they fit for your alerting.
Troubleshooting
| Error Code | Error Message | Possible Solution |
|---|---|---|
[SCN-068-000] | The following parameters has not been provided: <parameters> Please read the sensor documentation for further information! | Specify the listed parameters in the profile or in the sensor-specific parameters. |
[SCN-068-051] | Please define parameter DBType as 'ORACLE', 'ASE', 'MSSQL' | Set the parameter DBType to ORACLE, ASE or MSSQL. |
[SCN-068-052] | Parameter "Minutes" is not a correct integer value! | Specify a positive integer in the parameter Minutes. |
[SCN-068-053] | The additional query from file <file> doesn't return a valid integer value. Please make sure that the query returns an integer. | Change the query in the file so that it returns a single integer value. |
[SCN-068-054] | The additional query from file <file> returns more than one row. Please make sure that the query returns only a single row with a single column (integer or double). | Change the query in the file so that it returns a single row with a single column. |
[SCN-068-055] | The additional query from file <file> contains an illegal statement which is not a SELECT only. | Only SELECT statements are allowed in the query files in folder SAP_IDM_Monitor. |
[SCN-068-102] | Could not connect to Oracle database: <message> | Check the parameters Host, DBPort, DBName, DBUsername and DBPassword and that the database is reachable from the PRTG probe. |
[SCN-068-104] | Could not connect to ASE database: <message> | Check the parameters Host, DBPort, DBName, DBUsername and DBPassword and that the database is reachable from the PRTG probe. If the message is ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified, please install the correct 64-bit ASE ODBC driver on the PRTG probe. |
[SCN-068-107] | Could not connect to MSSQL database: <message> | Check the parameters Host, DBPort, DBName, DBUsername and DBPassword and that the database is reachable from the PRTG probe. |
Changelog
| Version | Changes |
|---|---|
| 2025.06 | Optimized check for failing housekeeping jobs |
| 2024.04 | Fixed bug during check of dispatcher state by LAST_VISITED date |
| 2024.01 |
|
| 2023.03 | Corrected selection of logs when using Oracle database. |
| 2022.08 |
|
| 2021.06 |
|
| 1.4.1.2 | First stable release. |