# Pandora FMS SAP Plugin # Introduction *Ver. 170522* The purpose of this document is to describe SAP system monitoring with Pandora FMS. **PandoraFMS\_SAP\_Plugin** allows remote monitoring of SAP systems and servers without the need to install anything on the computers that host SAP, making use of RFC (Remote Function Call) functions. This plugin can be used as a server plugin and as an agent plugin. # Compatibility matrix The following table shows the SAP system versions the plugin would support.
**Systems where it has been tested**SAP R/3 (ECC or ERP) SAP S/4 HANA
**Systems where it should work**SAP R/3 (ECC or ERP) SAP S/4 HANA
# Pre requirements In order to run PandoraFMS\_SAP\_Plugin it is necessary to meet a series of prerequisites. Although the plugin can be launched from any system that meets the requirements, we will use a Pandora FMS server built on Linux as an example. - **Java 16** The system that runs the plugin must have Java JDK installed at least in its version 16. To do this, you may access the Java JDK download page and obtain the corresponding "openjdk" package: [http://jdk.java.net/archive/](http://jdk.java.net/archive/) [![image-1652368429203.png](https://pandorafms.com/guides/public/uploads/images/gallery/2022-05/scaled-1680-/image-1652368429203.png)](https://pandorafms.com/guides/public/uploads/images/gallery/2022-05/image-1652368429203.png) Once the "**openjdk-16.0.2\_linux-x64\_bin.tar.gz**" package is downloaded into the system, unzip it and place it in the desired path. It is recommended to create a symbolic link to be able to execute the "java" command without the need to indicate the full path: ```bash tar zxvf openjdk-16.0.2_linux-x64_bin.tar.gz mv jdk-16.0.2 /opt ln -s /opt/jdk-16.0.2/bin/java /usr/bin/java ``` - **SAP JCO** To connect with the SAP systems to be monitored and make RFC calls, it is necessary to have the "sapjco3" library for Java. This library can be downloaded from the official SAP website: [https://support.sap.com/en/product/connectors/jco.html](https://support.sap.com/en/product/connectors/jco.html) [![image-1652369391415.png](https://pandorafms.com/guides/public/uploads/images/gallery/2022-05/scaled-1680-/image-1652369391415.png)](https://pandorafms.com/guides/public/uploads/images/gallery/2022-05/image-1652369391415.png) You will need 2 files, the compiled library and the JAR file: - - **libsapjco3.so** (Linux) or **sapjco3.dll** (Windows) - **sapjco3.jar** The compiled library can be placed in any directory you wish, for example: ```bash /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/libsapjco3.so ``` But the JAR file must be located in a directory called "PandoraFMS\_SAP\_Plugin\_lib" located next to the plugin "PandoraFMS\_SAP\_Plugin.jar". For example, if the plugin is located at: ```bash /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar ``` The JAR library will have to be located at: ```bash /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin_lib/sapjco3.jar ``` So the files would be organized like this: ```bash /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/libsapjco3.so /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin_lib/sapjco3.jar ``` - **SAP SNC** To connect to SAP systems using SNC you will need to obtain the official library for this, which is available for authorized customers on the SAP Service Marketplace at [service.sap.com/swdc](https://support.sap.com/en/my-support/software-downloads.html) under **Download → SAP Cryptographic Software**. The required file is: - - **libsapcrypto.so** This library must be located in the same directory where the plugin is located: ``` /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/libsapcrypto.so ``` - **Connectivity** Since monitoring is done from outside the SAP system, it is necessary to ensure communication with it. By making use of the RFC functions, connectivity is carried out from the device that runs the plugin (for example, Pandora FMS server) and the SAP system gateway through the **33XX TCP** port, where **XX** is the number of the SAP system it connects to (by default 3300 TCP). Therefore, the possible connection ports will range from 3300 to 3399. - **User** In order to execute the RFC functions of the SAP system, it will be necessary to have a username and password. This user must be “B-System” (System) in SAP ECC or S/4HANA versions, or “C-Communication / CPI-C/RFC” in previous SAP versions. It is recommended for the user to be "B-System" whenever possible, since for this type of users, passwords do not expire, which if it happened, it would force them to also be changed in the plugin configuration in Pandora FMS. For creating the user in the SAP system, it will be necessary to have the following authorization objects: - - Authorization object "**S\_RFC**": - Field "**ACTVT**" with value "**16 Ejecutar**". - Field "**RFC\_TYPE**" with value "**X FUGR**". - Field "**RFC\_NAME**" with values "**I\***", "**R\***", "**S\***", "**O\***", "**T\***". - Authorization object "**S\_TABU\_DIS**": - Field "**ACTVT**" with value "**03 Visualizar**". - Field "**DICBERCLS**" with value "**\***". - Authorization object "**S\_XMI\_LOG**": - **All its fields** with value "**\***". - Authorization object "**S\_XMI\_PROD**": - **All its fields** with value "**\***". - Authorization object "**S\_TCODE**": - Field "**TCD**" con valor "**SM50**". - **License** PandoraFMS\_SAP\_Plugin is exclusive for Pandora FMS Enterprise clients who have hired it. Therefore it is necessary to have a valid license key to run the plugin. To obtain a valid license, contact Pandora FMS team at: [https://pandorafms.com/es/](https://pandorafms.com/es/) - # Plugin parameters PandoraFMS\_SAP\_Plugin has the following parameters for its manual execution:
**Paramter****Description**
**-l "<license>"**It indicates the plugin the license it will use to run it. If the license is not valid, the plugin will display an error. For example: **-l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w"**
**-h "<sap\_host>"**It indicates the plugin the IP or DNS name of the SAP server to connect to. For example: **-h "10.5.6.30"**
**-c "<sap\_client>"**It indicates the plugin the SAP client (client) number for the connection. For example: **-c "001"**
**-s "<sap\_system>"**It indicates the plugin the SAP system number for the connection. This parameter will determine the port used in communication with SAP. For example: **-s "00"**
**-u "<sap\_user>"**It indicates the plugin the SAP user for the connection. For example: **-u "PANDORA01"**
**-p "<sap\_password>"** or **-x "<sap\_password\_encrypted>"** It indicates the plugin the password of the previous SAP user. For example: **-p "P45sw0rD."** or **-x "bSg8XKC63rhGfXHgjzSCMQ"**
**-X "<sap\_password>"**Instead of launching the plugin to monitor a SAP server, it produces the encrypted password as output, to launch the plugin with the parameter "**-x**" instead of "**-p**". For example: **-X "P45sw0rD."**
**-P "<sap\_snc\_partner\_name>"**A valid SAP server SNC name, which is equal to Distinguished Name(DN) of SAP server PSE. **-P "CN=SDD, OU=SAP Web AS, O=SAP Trust"**
**-Q "<sap\_snc\_qop>"**It is a parameter that defines the level of security applied in communication between SAP systems using Secure Network Communications (SNC). Valid values are: - **1**: Authentication only - **2**: Authentication and integrity protection - **3**: Authentication, integrity and privacy protection - **8**: Global default protection - **9**: Maximum protection **-Q "3"**
**-N "<sap\_snc\_client\_name>"**A valid client SNC name, which is equal to Distinguished Name(DN) of client PSE. **-N "CN=UDD, OU=SAP Web AS, O=SAP Trust"**
**-m "<plugin\_module>"**It indicates the plugin the ID of the module from which data is to be obtained (see table below) in an execution as a server plugin. For example: **-m "SYS\_INFO"**
**-M "<plugin\_module>"**It indicates the plugin the IDs of the modules from which data is to be obtained (see table below) in an execution as an agent plugin. Not all module IDs support this mode, and do not support custom filters or conditions. This parameter can be used multiple times in a single run to indicate multiple modules. For example: **-M "SYS\_INFO" -M "IDOC\_FAIL\_COUNT"**
**-R "<sap\_rfc\_function>"**In server plugin mode, for the module IDs that support it, it indicates the SAP RFC function to execute to obtain the data. For example: **-R "TH\_WPINFO"**
**-T "<sap\_rfc\_table>"**In server plugin mode, for the module IDs that support it, it indicates the name of the SAP table from which to obtain the data. For example: **-T "WPLIST"**
**-S "<sap\_rfc\_structure>"**In server plugin mode, for the module IDs that support it, it indicates the name of the SAP structure from which to obtain the data. For example: **-S "MSSDBLOGSIZE"**
**-F "<sap\_field\_1>,...,<sap\_field\_N>"**In server plugin mode, for the module IDs that support it, it indicates the fields of the previous table or structure separated by commas "," from which you want to obtain the data. For example: **-F "WP\_TYP,WP\_ISTATUS"**
**-W "<sap\_filter\_condition>"** or **-W "<plugin\_filter\_condition>"** or **-W "<ztransaction\_table\_input>"** In server plugin mode, for the module IDs that support it, it indicates filters for query conditions to SAP tables or filters for conditions in other types of plugin queries (depending on the module ID). This parameter can be specified multiple times for multiple conditions. The format for each of these conditions is described below. For example: **-W "STATUS EQ 'F'" -W "AND JOBNAME LIKE 'Z%'"** or **-W "WP\_ISTATUS,EQ,2" -W "WP\_ITYPE,EQ,1"** or **-W "TT\_OPTIONS,TEXT,STATUS EQ 'F'" -W "TT\_OPTIONS,TEXT,TT\_OPTIONS,TEXT,AND JOBNAME LIKE 'Z%'"**
**-I "<plugin\_rfc\_input>"** In server plugin mode, for the module IDs that support it, they indicate inputs for the execution of the RFC functions. This parameter can be specified multiple times for multiple inputs. The format for these inputs is described later. For example: **-I "TABLE\_NAME,USR04" -I "DBNAME,XYZ"**
**-L "<seconds>"**In server plugin mode, for the module IDs that support it, it indicates the number of seconds from the current moment backwards in which data will be searched. Its default value is "**86400**". For example: **-L "21600"**
**-C "<string>"**In server plugin mode, for the module IDs that support it, it indicates a text (as a filter) that the results of the RFC query must contain to be returned by the plugin. For example: **-C "USER01"**
**-Z "<sap\_z\_transaction\_function\_module>"**In server plugin mode, for the IDs of modules that allow it, indicate the number of the functional module that launches a transaction Z of SAP to obtain the data. For example: **-Z "Z\_CHECK\_STATUS"**
**-D "<delimiter>"**For the module IDs that support it, it indicates the field delimiter character for the outputs produced by the plugin that have a table format. Its default value is "**|**". For example: **-D ";"**
**-H "<1 | 0>"**For the module IDs that support it, it indicates whether you want to obtain the table header in the plugin output or not for all those outputs produced by the plugin that have a table format. It admits the values "0" (do not show the header) or "**1**" (show the header). Its default value is "**1**". For example: **-H "0"**
- **-W parameter format** The "-W" parameter can be used for different plugin modules, admitting 2 different formats in each case: - - Format for modules "**RFC\_READTABLE\_COUNT**", "**RFC\_READTABLE\_TABLE**" and "**RFC\_READTABLE\_GROUPTABLE**" (table queries): In the queries made to SAP tables, the conditions that must be indicated comply with the format expected by the "**RFC\_READ\_TABLE**" function, which would correspond to: `FIELD OPERATOR 'VALUE'` If multiple "-W" parameters are indicated, it may be necessary to indicate in the consecutive conditions whether they are joined by means of the "**AND**" or "**OR**" logical comparators. Note that SAP will evaluate the conditions in the order listed. For example: `-W "FIELD OPERATOR 'VALUE'" -W "AND FIELD OPERATOR 'VALUE'" -W "OR FIELD OPERATOR 'VALUE'"` It would be equivalent to a single condition: `-W "FIELD OPERATOR 'VALUE' AND FIELD OPERATOR 'VALUE' OR FIELD OPERATOR 'VALUE'"`

Due to socket limitations, a single condition indicated in a "**-W**" parameter cannot exceed **70 characters**. If you need to indicate longer conditions try concatenating them by using multiple "**-W**" parameters and using "**AND**" and "**OR**" logical comparators.

- Example of actual condition: `-W "SEQNO EQ '000'" -W "AND DATUM GE '_1_DAYSAGO_'"` - - Format for the "**RFC\_Z\_TRANS**" module: - - In Z transactions (SAP custom function modules) it may be necessary to send data to tables as input parameters, for which the following format must be used: - - `TABLE,FIELD,VALUE` - - In the case of indicating multiple "-W" parameters that refer to the same field of the same table, each of the values will be added to said field on a new line. - - Example of actual condition: - - `-W "TT_OPTIONS,TEXT,SEQNO EQ '000'" -W "TT_OPTIONS,TEXT,AND DATUM GE '_1_DAYSAGO_'"` - - Format for the rest of the modules: For modules that are not queries to SAP tables through the "**RFC\_READ\_TABLE**" function, the format of the filters must be: `FIELD,OPERATOR,VALUE` For these cases, if multiple "-W" parameters are indicated, it will be considered that all the conditions must be met at the same time (as if they were concatenated with logical "**AND**" operators). Example of actual condition: `-W "WP_ISTATUS,EQ,16" -W "WP_ITYPE,EQ,1"` The "**FIELD**" will depend on the SAP table or structure consulted, for example it could be the "**STATUS**" field of the "**TBTCO**" table. There are several pages where you can check the available fields of SAP tables, such as: [https://www.sapdatasheet.org/](https://www.sapdatasheet.org/) The "**OPERATOR**" determines the type of comparison to be made between the indicated "FIELD" and "VALUE". The possible operators are: 1. 1. **EQ**: The value of the field must be equal to the indicated value. 2. **NE**: The value of the field must be different from the indicated value. 3. **LT**: The value of the field must be less than the indicated value. In table queries using "RFC\_READ\_TABLE", if the field to be compares is a date or time, the oldest dates or times are lower than the most recent dates or times. 4. **LE**: The value of the field must be less than or equal to the indicated value. In table queries using "RFC\_READ\_TABLE", if the field to be compared is a date or time, the oldest dates or times are lower than the most recent dates or times. 5. **GT**: The value of the field must be greater than the indicated value. In table queries using "RFC\_READ\_TABLE", if the field to be compared is a date or time, the most recent dates or times are greater than the oldest dates or times. 6. **GE**: The value of the field must be greater than or equal to the indicated value. In table queries using "RFC\_READ\_TABLE", if the field to be compared is a date or time, the most recent dates or times are greater than the oldest dates or times. 7. **LIKE**: The value of the field must be adjusted to the expression of the indicated value. Only available for table queries (RFC\_READ\_TABLE). The indicated "**VALUE**" allows applying the filter (condition) of the query results according to its "OPERATOR". It is recommended to always encapsulate values in single quotes in SAP table queries with "RFC\_READ\_TABLE". With the "**LIKE**" "OPERATOR", the indicated expressions allow the use of the character "**%**" to determine that it can be any character from 0 to N times. For example: **Z%** : It allows indicating that the field with which it is compared must have a value that at least begins with the letter Z, and may or may not have more characters after it. For the "**DATS**" or "**TIMS**" "FIELDS" (SAP tables fields) macros can be used to be replaced by the corresponding date and time (according to the macro) regarding the date and time of the plugin execution time, which allow you to apply dynamic filters with the correct format for these types of SAP fields. 1. 1. Macros for "**DATS**" fields: 1. **\_N\_DAYSAGO\_**: N days ago date. 2. **\_N\_WEEKSAGO\_**: N weeks ago date. 2. Macros for "**TIMS**" fields: 1. **\_N\_SECSAGO\_**: N seconds ago time. 2. **\_N\_MINSAGO\_**: N minutes ago time. 3. **\_N\_HOURSAGO\_**: N hours ago time. For all macros, "**N**" can be replaced by a **positive integer** or 0. "**DATS**" fields have the format "**YYYYMMDD**", and therefore the macros for "DATS" fields will be replaced with values in that format, being: - - - **YYYY**: The year with 4 digits, for example "2022". - **MM**: The month with 2 digits, for example "05". - **DD**: The day of the month with 2 digits, for example "13". "**TIMS**" fields have the format "**hhmmss**", and therefore the macros for "TIMS" fields will be replaced with values in that format, being: - - - **hh**: The hour with 2 digits in 24-hour format, for example "13". - **mm**: The minutes with 2 digits, for example "08". - **ss**: The seconds with 2 digits, for example "51". - **-I parameter format** The format that the "-I" parameters must have is as follows: `INPUT,VALUE` The "**INPUT**" will depend on the SAP function queried, for example it could be the "**TABLE\_NAME**" input of the "**RFC\_GET\_TABLE\_ENTRIES**" function. There are several pages where you can check the available "input" entries of SAP functions, such as: [https://www.sapdatasheet.org/](https://www.sapdatasheet.org/) The "**VALUE**" indicated is the one that will be assigned to the "INPUT" when executing the corresponding RFC function. Actual "input" example: `-I "TABLE_NAME,USR04"`

The "-I" parameters also support the use of macros with the same format as those used for the "-W" parameters: "**\_N\_SECSAGO\_**", "**\_N\_MINSAGO\_**", "**\_N\_HOURSAGO\_**", "**\_N\_DAYSAGO\_**" and "**\_N\_WEEKSAGO\_**" (see point above for details).

# Manual execution For PandoraFMS\_SAP\_Plugin proper execution, it is necessary to indicate a series of minimum parameters for all cases. In addition to these minimum parameters, depending on whether the plugin is executed as an agent plugin or as a server plugin, a parameter must be indicated with the module(s) from which to obtain data, as the case may be. Lastly, and depending on the module, it is possible that it accepts additional parameters (see in following sections). That way, the minimum mandatory parameters for any execution are: ```bash -l "" -h "" -c "" -s "" -u "" -p "" ``` Or fi using an encrypted password: ```bash -l "" -h "" -c "" -s "" -u "" -x "" ``` For execution as a server plugin, you will also have to indicate: ```bash -m "" ``` While for an execution as an agent plugin, you will have to indicate: ```bash -M "" ``` It will also be necessary to indicate the location of the compiled "SAP JCO 3" library ("libsapjco3.so" for Linux and "sapjco3.dll" for Windows) through a Java parameter: ```bash -Djava.library.path= ``` Seeing it with a couple of examples, this would be a possible execution as a server plugin: ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "SYS_INFO" ``` Whose output would be: ```csv System hostname|System IP|System ID|System instance|System version|DB hostname|DBMS|OS server|10.5.6.30|XYZ|server_XYZ_00|46C|server|MSSQL|Windows NT ``` And this would be a possible execution as an agent plugin: ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -M "SYS_INFO" ``` Whose output would be: ```xml ``` In the case of the agent plugin, and as seen in previous sections, it is possible to indicate several modules to monitor in a single execution. For example: ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -M "SYS_INFO" -M "IDOC_FAIL_COUNT" -M "IDOC_OK_COUNT" ``` Whose output would be: ```xml ``` It is also possible to run the plugin just to encrypt a password and mask it during the final execution of the plugin. For example, with the following execution: ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -X "P45sw0rD." ``` The encrypted password would be obtained: ``` jc2hV8nK2NLtn5YvYNZzDQ ``` To run the plugin in this way, using the parameter "**-x**" instead of "**-p**" to indicate the password: ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -x "jc2hV8nK2NLtn5YvYNZzDQ" \ -m "SYS_INFO" ``` # Discovery This plugin can be integrated with Pandora FMS Discovery. To do so, you must load the ".disco" package that you can download from the Pandora FMS library: [https://pandorafms.com/library/](https://pandorafms.com/library/) [![sap1.png](https://pandorafms.com/guides/public/uploads/images/gallery/2024-10/scaled-1680-/xsrsap1.png)](https://pandorafms.com/guides/public/uploads/images/gallery/2024-10/xsrsap1.png) Once loaded, SAP environments can be monitored by creating Discovery tasks from the Management > Discovery > Applications section. [![sap2.png](https://pandorafms.com/guides/public/uploads/images/gallery/2024-10/scaled-1680-/ZgXsap2.png)](https://pandorafms.com/guides/public/uploads/images/gallery/2024-10/ZgXsap2.png) The following minimum data will be requested for each task: - **SAP Hostname**:IP or FQDN of the SAP environment to monitor. - **SAP Client**: SAP client/commander to monitor. - **SAP System Number**: Number of the SAP system to monitor. - **SAP Credentials**: SAP credentials to connect to the environment to monitor. These credentials will be created in the Pandora FMS console credentials store. - **SAP SNC Mode**: Enables connection via SNC. - **SAP SNC Partner name**: A valid SAP server SNC name, which is equal to Distinguished Name(DN) of SAP server PSE. - **SAP SNC QOP**: It is a parameter that defines the level of security applied in communication between SAP systems using Secure Network Communications (SNC). - **Client SNC name**: A valid client SNC name, which is equal to Distinguished Name(DN) of client PSE. [![sap3.png](https://pandorafms.com/guides/public/uploads/images/gallery/2024-10/scaled-1680-/yoYsap3.png)](https://pandorafms.com/guides/public/uploads/images/gallery/2024-10/yoYsap3.png) You can also adjust the task configuration to customize the desired monitoring: - **Max threads**: to optimize execution time, multiple threads may be configured to monitor the task modules. Keep in mind that configuring multiple threads may increase the task CPU usage. - **Target agent:** Name of the target agent in which the indicated modules will be created. If no agent name is specified, the SAP Hostname will be used instead. - **SAP modules**: From a list of predefined modules, the elements to be monitored in the SAP environment can be selected. - **Custom modules definitions**: Custom modules definition block. Each line of the block will be a module to monitor, indicating for each case name, data type and SAP plugin parameters to obtain the data. Each line must have the format: `;;` Example: `SAP info;generic_data_string;-m 120` [![sap4.png](https://pandorafms.com/guides/public/uploads/images/gallery/2024-10/scaled-1680-/xgrsap4.png)](https://pandorafms.com/guides/public/uploads/images/gallery/2024-10/xgrsap4.png) Tasks that are successfully completed will have an execution summary with the following information: - **SAP Target**: Monitored SAP target environment. - **SAP Client**: Monitored SAP client/commander. - **SAP System**: Number of monitored SAP system. - **Total modules**: Total modules generated for the target SAP environment. [![sap5.png](https://pandorafms.com/guides/public/uploads/images/gallery/2024-10/scaled-1680-/1Rcsap5.png)](https://pandorafms.com/guides/public/uploads/images/gallery/2024-10/1Rcsap5.png) Tasks that are not completed successfully will have an execution summary recording the errors that occurred. # Plugin modules The following table describes the modules available for the PandoraFMS\_SAP\_Plugin plugin:
**Module ID****Server plugin****Agent plugin****Module description (by default)**
**SYS\_INFO****YES****YES**Obtains information from the SAP system to which it is connected in table format.
**LOGIN\_TEXT****YES****NO**It checks if it is able to connect via RFC to the SAP system and generates an output indicating "Login OK" or a text with the error that occurs.
**LOGIN\_PROC****YES****NO**It checks if it is able to connect via RFC to the SAP system and generates an output of 1 in case of success or 0 in case of error.
**RFC\_FUNC\_COUNT****YES****NO**It allows executing an RFC function and obtaining as output the number of records obtained in the query.
**RFC\_FUNC\_TABLE****YES****NO**It allows executing an RFC function and obtaining as output a table with the records obtained in the query.
**RFC\_FUNC\_GROUPTABLE****YES****NO**It allows executing an RFC function and obtaining as output a table with the records obtained in the query and a counter of the number of different records.
**WP\_DIA\_FAIL\_COUNT****YES****YES**Counts the number of WP DIA in failed status on the SAP server.
**WP\_BGD\_FAIL\_COUNT****YES****YES**Counts the number of WP BGDs in failed status on the SAP server.
**WP\_UPD\_FAIL\_COUNT****YES****YES**Counts the number of WP UPDs in failed status on the SAP server.
**WP\_UP2\_FAIL\_COUNT****YES****YES**Counts the number of WP UP2 in failed status on the SAP server.
**WP\_SPO\_FAIL\_COUNT****YES****YES**Counts the number of WP SPOs in failed status on the SAP server.
**WP\_ENQ\_FAIL\_COUNT****YES****YES**Counts the number of WP ENQs in failed status on the SAP server.
**WP\_NOREST\_COUNT****YES****YES**Counts the number of WP without "restart" active on the SAP server.
**WP\_STOP\_COUNT****YES****YES**Counts the amount of WP stopped on the SAP server.
**WP\_DIA\_AVAIL\_COUNT****YES****YES**Counts the amount of WP DIA in available status on the SAP server.
**WP\_BGD\_AVAIL\_COUNT****YES****YES**Counts the number of WP BGDs in available status on the SAP server.
**WP\_UPD\_AVAIL\_COUNT****YES****YES**Counts the number of WP UPDs in available status on the SAP server.
**WP\_DIA\_AVAIL\_PERCENT****YES****YES**Gets the percentage of WP DIA available on the SAP server.
**WP\_BGD\_AVAIL\_PERCENT****YES****YES**Gets the percentage of WP BGDs available on the SAP server.
**WP\_UPD\_AVAIL\_PERCENT****YES****YES**Gets the percentage of WP UPDs available on the SAP server.
**IDOC\_FAIL\_COUNT****YES****YES**Posts the number of failed IDocs since yesterday in the SAP system.
**IDOC\_OK\_COUNT****YES****YES**Posts the number of successful IDocs since yesterday in the SAP system.
**DUMPS\_YEST\_TABLE****YES****YES**Obtains a table of the DUMPs generated since yesterday in the SAP system.
**DUMPS\_YEST\_COUNT****YES****YES**Posts the DUMPs generated since yesterday in the SAP system.
**JOBS\_CANCEL\_YEST\_TABLE****YES****YES**Obtains a table of JOBs canceled since yesterday in the SAP system.
**JOBS\_CANCEL\_YEST\_COUNT****YES****YES**Posts the JOBs canceled since yesterday in the SAP system.
**JOBS\_CANCEL\_YEST\_GROUPTABLE****YES****YES**Obtains a table where the JOBs canceled since yesterday in the SAP system are counted by name.
**BATCH\_INPUT\_FAIL\_COUNT****YES****YES**Posts the failed "Batch input" since yesterday in the SAP system.
**JOBS\_CANCEL\_TODAY\_TABLE****YES****YES**Gets a table of JOBs canceled today in the SAP system.
**JOBS\_CANCEL\_TODAY\_COUNT****YES****YES**Posts the JOBs canceled today in the SAP system.
**JOBS\_CANCEL\_TODAY\_GROUPTABLE****YES****YES**Obtains a table where the JOBs canceled today are counted by name in the SAP system.
**DUMPS\_TODAY\_GROUPTABLE****YES****YES**Obtains a table where the DUMPs generated today in the SAP system are counted by name.
**DUMPS\_TODAY\_COUNT****YES****YES**Posts the DUMPs generated today in the SAP system.
**SEND\_OP\_NOPROC\_COUNT****YES****YES**Accounts for external shipping operations not processed since yesterday.
**SEND\_OP\_PROC\_COUNT****YES****YES**Accounts for external shipping operations processed since yesterday.
**RFC\_READTABLE\_COUNT****YES****NO**It allows querying SAP system tables and obtaining as output the number of records obtained in the query.
**RFC\_READTABLE\_TABLE****YES****NO**It allows querying SAP system tables and obtaining as output a table with the records obtained in the query.
**RFC\_READTABLE\_GROUPTABLE****YES****NO**It allows querying SAP system tables and obtaining as output a table with the records obtained in the query and a counter for the number of different records.
**ORA\_TABLESPACES\_TABLE****YES****YES**Only available on SAP systems with Oracle database. Gets a table using Oracle's tablespaces.
**ORA\_TABLESPACES\_95\_COUNT****YES****YES**Only available on SAP systems with Oracle database. Counts the tablespaces with a usage greater than or equal to 95%.
**ORA\_TABLESPACES\_99\_COUNT****YES****YES**Only available on SAP systems with Oracle database. Counts the tablespaces with a usage greater than or equal to 99%.
**BLOCK\_ENTRIES\_TABLE****YES****YES**Gets a table with the SAP system lock entries.
**BLOCK\_ENTRIES\_COUNT****YES****YES**Posts the blocking entries of the SAP system.
**CUSTOMER\_OPEN\_ITEMS\_COUNT****YES****YES**Posts the open objects of customer accounts in the SAP system.
**CUSTOMER\_CLOSING\_BALANCE\_TABLE****YES****YES**Obtains a table of the closing balance of customer accounts from the SAP system.
**CUSTOMER\_CLEARING\_TRANS\_COUNT****YES****YES**Posts clearing transactions for customer accounts in the SAP system.
**PFL\_PARAM\_VALUES\_TABLE****YES****YES**Gets a table with PFL parameter values from the SAP system.
**PROFILES\_CHANGES\_COUNT****YES****YES**Posts changes to authorization profiles since yesterday in the SAP system.
**PROFILES\_CHANGES\_TABLE****YES****YES**Gets a table of changes to authorization profiles since yesterday in the SAP system.
**MSSQL\_LOG\_SIZE\_BYTES****YES****YES**Only available on SAP systems with MS SQL database. Gets the size in bytes of the MS SQL log.
**MSSQL\_LOG\_FREE\_BYTES****YES****YES**Only available on SAP systems with MS SQL database. Get the free bytes from the MS SQL log.
**MSSQL\_LOG\_FREE\_PERCENT****YES****YES**Only available on SAP systems with MS SQL database. Gets the free percentage of the MS SQL log.
**RFC\_QUEUE\_OUT\_COUNT****YES****YES**Posts the RFC output queue of the SAP system.
**RFC\_QUEUE\_IN\_COUNT****YES****YES**Posts the RFC input queue of the SAP system.
**RFC\_SEND\_FAIL\_COUNT****YES****YES**Accounts for failed delivery attempts in the SAP system.
**RFC\_SEND\_FAIL\_O\_COUNT****YES****YES**It counts the unsuccessful delivery attempts with an "O" output in the SAP system.
**RFC\_SEND\_FAIL\_I\_COUNT****YES****YES**Accounts for failed delivery attempts with "I" output in the SAP system.
**RFC\_ERROR\_QUEUE\_OUT\_FAIL\_COUNT****YES****YES**Posts the queue of RFC output errors from the SAP system.
**RFC\_ERROR\_QUEUE\_IN\_FAIL\_COUNT****YES****YES**Posts the RFC input error queue of the SAP system.
**RFC\_QUEUE\_OUT\_OLDER\_SECONDS****YES****YES**Gets the number of seconds since the oldest entry in the output queue was not processed.
**RFC\_QUEUE\_IN\_OLDER\_SECONDS****YES****YES**Gets the number of seconds since the oldest entry in the input queue was not processed.
**HANA\_FREE\_MEM\_BYTES****YES****YES**Only available on SAP systems with Hana database. Gets the bytes of free memory for the database.
**HANA\_USED\_MEM\_BYTES****YES****YES**Only available on SAP systems with Hana database. Gets the bytes of memory used from the database.
**RFC\_Z\_TRANS****YES****NO**It allows executing custom SAP function modules running SAP "Z" transactions and obtaining what is returned in output as a value.
The following table indicates the relevant information of the plugin modules for its execution:
**Module ID****XML name****Data type****Mandatory parameters****Optional parameters**
**SYS\_INFO**SAP System infogeneric\_data\_string **-F** **-H** **-D**
**LOGIN\_TEXT** generic\_data\_string
**LOGIN\_PROC** generic\_proc
**RFC\_FUNC\_COUNT** generic\_data**-R** **-T or -S** **-F** **-I** **-W**
**RFC\_FUNC\_TABLE** async\_string**-R** **-T or -S** **-F** **-I** **-W** **-H** **-D**
**RFC\_FUNC\_GROUPTABLE** async\_string**-R** **-T or -S** **-F** **-I** **-W** **-H** **-D**
**WP\_DIA\_FAIL\_COUNT**WP DIA failed - Countgeneric\_data
**WP\_BGD\_FAIL\_COUNT**WP BGD failed - Countgeneric\_data
**WP\_UPD\_FAIL\_COUNT**WP UPD failed - Countgeneric\_data
**WP\_UP2\_FAIL\_COUNT**WP UP2 failed - Countgeneric\_data
**WP\_SPO\_FAIL\_COUNT**WP SPO failed - Countgeneric\_data
**WP\_ENQ\_FAIL\_COUNT**WP ENQ failed - Countgeneric\_data
**WP\_NOREST\_COUNT**WP with restart not active - Countgeneric\_data
**WP\_STOP\_COUNT**WP stopped - Countgeneric\_data
**WP\_DIA\_AVAIL\_COUNT**WP DIA available - Countgeneric\_data
**WP\_BGD\_AVAIL\_COUNT**WP BGD available - Countgeneric\_data
**WP\_UPD\_AVAIL\_COUNT**WP UPD available - Countgeneric\_data
**WP\_DIA\_AVAIL\_PERCENT**WP DIA available - Percentgeneric\_data
**WP\_BGD\_AVAIL\_PERCENT**WP BGD available - Percentgeneric\_data
**WP\_UPD\_AVAIL\_PERCENT**WP UPD available - Percentgeneric\_data
**IDOC\_FAIL\_COUNT**IDOCs failed from yesterday - Countgeneric\_data
**IDOC\_OK\_COUNT**IDOCs ok from yesterday - Countgeneric\_data
**DUMPS\_YEST\_TABLE**Dumps from yesterday - Listasync\_string
**DUMPS\_YEST\_COUNT**Dumps from yesterday - Countgeneric\_data
**JOBS\_CANCEL\_YEST\_TABLE**Jobs canceled from yesterday - Listasync\_string **-H**
**JOBS\_CANCEL\_YEST\_COUNT**Jobs canceled from yesterday - Countgeneric\_data
**JOBS\_CANCEL\_YEST\_GROUPTABLE**Jobs canceled from yesterday - Grouped count listasync\_string **-H**
**BATCH\_INPUT\_FAIL\_COUNT**Batch input failed from yesterday - Countgeneric\_data
**JOBS\_CANCEL\_TODAY\_TABLE**Jobs canceled today - Listasync\_string **-H**
**JOBS\_CANCEL\_TODAY\_COUNT**Jobs canceled today - Countgeneric\_data
**JOBS\_CANCEL\_TODAY\_GROUPTABLE**Jobs canceled today - Grouped count listasync\_string **-H** **-D**
**DUMPS\_TODAY\_GROUPTABLE**Dumps today - Grouped count listasync\_string **-H** **-D**
**DUMPS\_TODAY\_COUNT**Dumps today - Countgeneric\_data
**SEND\_OP\_NOPROC\_COUNT**External send operations not processed from yesterday - Countgeneric\_data
**SEND\_OP\_PROC\_COUNT**External send operations processed from yesterday - Countgeneric\_data
**RFC\_READTABLE\_COUNT** generic\_data**-T** **-F** **-W**
**RFC\_READTABLE\_TABLE** async\_string**-T** **-F** **-W** **-H** **-D**
**RFC\_READTABLE\_GROUPTABLE** async\_string**-T** **-F** **-W** **-H** **-D**
**ORA\_TABLESPACES\_TABLE**Oracle tablespaces usage - Listgeneric\_data\_string **-H** **-D**
**ORA\_TABLESPACES\_95\_COUNT**Oracle tablespaces usage greater equal 95% - Countgeneric\_data
**ORA\_TABLESPACES\_99\_COUNT**Oracle tablespaces usage greater equal 99% - Countgeneric\_data
**BLOCK\_ENTRIES\_TABLE**System block entries - Listasync\_string **-H** **-D**
**BLOCK\_ENTRIES\_COUNT**System block entries - Countgeneric\_data
**CUSTOMER\_OPEN\_ITEMS\_COUNT**Customers accounts open items - Countgeneric\_data **-I**
**CUSTOMER\_CLOSING\_BALANCE\_TABLE**Closing balance of customers accounts - Listasync\_string **-I** **-H** **-D**
**CUSTOMER\_CLEARING\_TRANS\_COUNT**Customers accounts clearing transactions - Countgeneric\_data **-I**
**PFL\_PARAM\_VALUES\_TABLE**PFL parameters values - Listasync\_string **-W** **-H** **-D**
**PROFILES\_CHANGES\_COUNT**Changes on auth profiles from yesterday - Countgeneric\_data **-C** **-L**
**PROFILES\_CHANGES\_TABLE**Changes on auth profiles from yesterday - Listasync\_string **-C** **-L** **-H** **-D**
**MSSQL\_LOG\_SIZE\_BYTES**MS SQL log sizegeneric\_data
**MSSQL\_LOG\_FREE\_BYTES**MS SQL log freegeneric\_data
**MSSQL\_LOG\_FREE\_PERCENT**MS SQL log free %generic\_data
**RFC\_QUEUE\_OUT\_COUNT**RFC Queue OUT - Countgeneric\_data **-I**
**RFC\_QUEUE\_IN\_COUNT**RFC Queue IN - Countgeneric\_data **-I**
**RFC\_SEND\_FAIL\_COUNT**RFC send tries failed - Countgeneric\_data **-I**
**RFC\_SEND\_FAIL\_O\_COUNT**RFC send tries failed return O - Countgeneric\_data **-I**
**RFC\_SEND\_FAIL\_I\_COUNT**RFC send tries failed return I - Countgeneric\_data **-I**
**RFC\_ERROR\_QUEUE\_OUT\_FAIL\_COUNT**RFC Error queue OUT failed - Countgeneric\_data
**RFC\_ERROR\_QUEUE\_IN\_FAIL\_COUNT**RFC Error queue IN failed - Countgeneric\_data
**RFC\_QUEUE\_OUT\_OLDER\_SECONDS**RFC Queue OUT - Older entry seconds not processinggeneric\_data **-I**
**RFC\_QUEUE\_IN\_OLDER\_SECONDS**RFC Queue IN - Older entry seconds not processinggeneric\_data **-I**
**HANA\_FREE\_MEM\_BYTES**Hana free memory bytesgeneric\_data
**HANA\_USED\_MEM\_BYTES**Hana used memory bytesgeneric\_data
**RFC\_Z\_TRANS** **-F****-T** **-I** **-W**
# Examples - SAP system information: ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "SYS_INFO" ``` ```bash System hostname|System IP|System ID|System instance|System version|DB hostname|DBMS|OS server|10.5.6.30|XYZ|server_XYZ_00|46C|server|MSSQL|Windows NT ``` - Connection to the SAP system (Text): ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "LOGIN_TEXT" ``` ```bash Login OK ``` - Connection to the SAP system (Boolean): ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "LOGIN_PROC" ``` ``` 1 ``` - Work Process with "Waiting" status using RFC functions (Quantity): ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "RFC_FUNC_COUNT" \ -R "TH_WPINFO" -T "WPLIST" -F "WP_TYP,WP_ISTATUS" -W "WP_ISTATUS,EQ,2" ``` ``` 8 ``` - Work Process with "Waiting" status using RFC functions (Table): ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "RFC_FUNC_TABLE" \ -R "TH_WPINFO" -T "WPLIST" -F "WP_TYP,WP_ISTATUS" -W "WP_ISTATUS,EQ,2" ``` ```bash WP_TYP|WP_ISTATUS DIA|2 DIA|2 DIA|2 UPD|2 UPD|2 ENQ|2 BGD|2 SPO|2 ``` - Work Process with "Waiting" status using RFC functions (Quantity per distinct record): ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "RFC_FUNC_GROUPTABLE" \ -R "TH_WPINFO" -T "WPLIST" -F "WP_TYP,WP_ISTATUS" -W "WP_ISTATUS,EQ,2" ``` ```bash WP_TYP|WP_ISTATUS|count(WP_TYP|WP_ISTATUS) DIA|2|3 UPD|2|2 ENQ|2|1 BGD|2|1 SPO|2|1 ``` - Work Process DIA available (Quantity): ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "WP_DIA_AVAIL_COUNT" ``` ``` 3 ``` - Work Process DIA available (Percentage): ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "WP_DIA_AVAIL_PERCENT" ``` ``` 75.0 ``` - Correct IDocs since yesterday (Quantity): ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "IDOC_OK_COUNT" ``` ``` 0 ``` - Jobs in "Finished" status that start with the letter "Z" or in "Released" status using table queries (Quantity): ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "RFC_READTABLE_COUNT" \ -T "TBTCO" -F "JOBNAME,STATUS,STRTDATE" -W "STATUS EQ 'F' AND JOBNAME LIKE 'Z%'" -W "OR STATUS EQ 'S'" ``` ``` 21 ``` - Jobs in "Finished" status that start with the letter "Z" or in "Released" status using table queries (Table): ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "RFC_READTABLE_TABLE" \ -T "TBTCO" -F "JOBNAME,STATUS,STRTDATE" -W "STATUS EQ 'F' AND JOBNAME LIKE 'Z%'" -W "OR STATUS EQ 'S'" ``` ```bash JOBNAME|STATUS|STRTDATE ZADS_SCANPROG1|F|20100305 ZJOB1|F|20130714 ZJOB1|F|20130714 ZJOB1|F|20130714 ZJOB1|F|20130714 ZJOB1|F|20130714 ZJOB1|F|20130714 ZJOB1|F|20130714 RDDIMPDP|S| RDDIMPDP_CLIENT_001|S| SAP_APPLICATION_STAT_COLLECTOR|S| ZJOB1|F|20130714 ZJOB1|F|20130714 ZJOB1|F|20130714 ZJOB1|F|20130714 ZJOB1|F|20130725 ZJOB1|F|20130725 ZJOB1|F|20130725 ZJOB1|F|20130725 ZJOB1|F|20130725 ZJOB1|F|20130725 ``` - Jobs in "Finished" status that start with the letter "Z" or in "Released" status using table queries (Quantity per distinct record): ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "RFC_READTABLE_GROUPTABLE" \ -T "TBTCO" -F "JOBNAME,STATUS,STRTDATE" -W "STATUS EQ 'F' AND JOBNAME LIKE 'Z%'" -W "OR STATUS EQ 'S'" ``` ```bash JOBNAME|STATUS|STRTDATE|count(JOBNAME|STATUS|STRTDATE) ZADS_SCANPROG1|F|20100305|1 ZJOB1|F|20130714|11 RDDIMPDP|S||1 RDDIMPDP_CLIENT_001|S||1 SAP_APPLICATION_STAT_COLLECTOR|S||1 ZJOB1|F|20130725|6 ``` - Changes in authorization profiles in the last 24 hours that contain the word "USER": ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "PROFILES_CHANGES_TABLE" \ -L "86400" -C "USER" ``` ```bash USER|MOD|DATE USER1|M|2022-05-17 03:56:34 USER2|C|2022-05-17 03:39:02 USER3|M|2022-05-17 10:32:46 USER4|C|2022-05-16 07:57:27 USER5|M|2022-05-16 05:39:24 ``` - Output of the execution of a "Z" transaction: ```bash java \ -Djava.library.path=/usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/ \ -jar /usr/share/pandora_server/util/plugin/PandoraFMS_SAP_Plugin/PandoraFMS_SAP_Plugin.jar \ -l "f51a6712-a3fALLp4x0Af3vAfjr9II2f-bas1g74w" \ -h "10.5.6.30" \ -c "001" \ -s "00" \ -u "PANDORA01" \ -p "P45sw0rD." \ -m "RFC_Z_TRANS" \ -Z "Z_CHECK_STATUS" -F "OUTPUT,VALUE" ``` ``` OUTPUT|VALUE SUCCESS|1 ```