--- language: "en" --- # PowerConnect Documentation ## [Splunk](https://docs.rhondos.com/powerconnect-for-sap-solutions/splunk.md) ### [Dynatrace](https://docs.rhondos.com/powerconnect-for-sap-solutions/dynatrace.md) ### [ABAP](https://docs.rhondos.com/powerconnect-for-sap-solutions/abap.md) ### [Java](https://docs.rhondos.com/powerconnect-for-sap-solutions/java.md) ### [Cloud](https://docs.rhondos.com/powerconnect-for-sap-solutions/cloud-products.md) ### [Knowledge Base and Troubleshooting](https://docs.rhondos.com/powerconnect-for-sap-solutions/knowledge-base.md) * ### [Product Compatibility Matrix](https://docs.rhondos.com/powerconnect-for-sap-solutions/product-compatibility-matrix.md) ### [Customer Success](https://docs.rhondos.com/powerconnect-for-sap-solutions/customer-success.md) --- language: "en" --- # NIPING Utility Setup Guide - Splunk ## **INTRODUCTION** The NIPING utility is currently the best way to track SAP system availability. It does not rely directly on the PowerConnect tool and will continue to report system availability if the PowerConnect add-on is currently not sending data directly from your SAP system. ## **PREREQUISITES** Please note the following requirements for running the standalone NIPING utility: * A separate host system running Windows or Linux on the same internal network as your SAP deployment. * NOTE: Running this utility on a separate host system from your SAP deployment is not strictly a *requirement,* but as a best practice, it is *recommended*. Using an SAP host system to monitor SAP systems presents a potential issue if that host system becomes unavailable, defeating the purpose of running independent monitoring. * **Python 3.6+** with the **httplib2**library installed. ## INSTALLATION [niping_utility.zip](https://docs.rhondos.com/__attachments/a_369f9b0058ffb5f33cb84198c1e06513814d163fdf23c63735c0b517a69059e6/niping_utility.zip.md?cb=f31f2e18ac0c9d194b1149ed579f76c4) * Download the standalone NIPING utility on this page. * Extract the utility to the desired folder * Find the NIPING utility executable for your host's operating system in an SAP install directory (..\\usr\\sap\\\\\D\\\exe) * Copy the NIPING utility and associated library files to the utility's /lib/niping directory * Ensure that the host user has execute permissions for this directory * On Linux, you will need to run the command *chmod -R +x \* * On Windows, ensure the files are in a directory fully accessible to the user ![image-20220603-132748.png](https://docs.rhondos.com/__attachments/a_a92fb47b504e83b2ece06136ee0b7c6aac18b99eed450475f480ef88ccf37a5a/image-20220603-132748.png?cb=3818822432a508e417463312873988c6) * Configure the target_hosts.ini file using the instructions provided within the file * You will need the following for each target SAP host: * SID * host IP address * port (use 3200 as the default unless directed to use a different port by your BASIS team) ![image-20220603-131744.png](https://docs.rhondos.com/__attachments/a_94ee22f78bddc656a1e06038c4cfaff399390cafb7bad601402fa8ef0ace092d/image-20220603-131744.png?cb=6483be215202708553217ac4f7df553d) * Configure the target_endpoints.ini file using the instructions provided within the file * You will need the following for each target Splunk deployment: * URI (host address) * For Splunk Cloud, you will need the unique HEC endpoint address provided by Splunk support * For Splunk Enterprise, this will be in the form of `http://localsplunksystem.com:8088/services/collector` * Please double check if SSL is enabled for HEC data inputs. If enabled, use "https" in the URI * The default port is 8088. Please check with your Splunk administrator for any changes to this. * HEC token ![image-20240807-161247.png](https://docs.rhondos.com/__attachments/a_577b9affdd649d3511323335734a5271a1ccd8a36d4ba5372033303fef0761e0/image-20240807-161247.png?cb=07750fedd358281181e87b790539e003) * Schedule the script to run at desired intervals in the host system * On Windows, this will use the Task Scheduler utility * On Linux, use crontab ## Common Issues * Linux returns code 127 * See that the correct executable for your operating system has been installed in the niping utility directory. * Linux returns code 126 * Ensure that the user has permission to execute the niping executable file. --- language: "en" --- # 7.1.0 - Changes to Existing Dashboards * SAP Security Essentials * Updated the query of "Users with sensitive roles" single value panel. * Updated the query of "Users with sensitive auth object" single value panel. * Updated the query of "Users with admin profiles" single value panel. * SAP Security Scorecard * Updated the "Audit log deletion" single value panel. * Updated the "Users having excessive rights" single value panel. * Updated the "Users with sensitive authorization" single value panel. * Updated the "Users with sensitive roles" single value panel. * Audit Integrity Check * Removed the "Check Result" input filter. * Added four single value panel based on CHECK_RESULT field values * "Passed" single value panel * "Failed" single value panel * "Removed" single value panel * "Removed (OS Level)" single value panel * Work Processes Overview * Added new input filter "Type" * Updated the query of "Work process utilization %" chart panel * Renamed the title of "Work Process Runtime" to "Work Process Runtime (sec)" and updated the query. * STATS Details * Updated the query of "Overall Statistics" table. Changed the field HANA_PROCESSING_TIME to TOTAL_REQUEST_TIME * SAP Change Documents * Added a new table with fields Client, User, Object Class, Transaction Code * Renamed the existing table column names * SAP Directories * Added a new input checkbox "Last 30 Mins" * Added a new summary table, Details of directory table and History of file table * Removed earlier tables. * HANA: Alert Details (Historical) * Renamed the dashboard from "HANA: Alert Details" to " HANA: Alert Details (Historical)". * Removed the link list * Removed the "Count by Alert Name" and "Current Alert Details" tables * Fiori Statistics Details * Added new column "Response Time" in existing table Statistics record. * System Overview * Fixed the Availability panel query * System Overview (7.x) * Fixed the Availability panel query * Fixed a bug in the Work Processes panels to remove false null values * SuccessFactors Monitoring Dashboard * Fixed the title of the Dashboard * SM12 System Logs * Fixed the title of the Dashboard * Minor Improvements * SM51 - Request Queue Information * SM51 - RFC Communication Block * Work Process Detailed Analysis * Lookup changed in most of the dashboards --- language: "en" --- # ABAP --- language: "en" --- # ABAP Data Extraction User Guide ## Summary This user guide was prepared to ensure that customers understand what SAP data PowerConnect can send to Splunk, and how to optimize their environment's configuration to maximize business value. Please review the corresponding menu options on the left for a detailed summary of each of the data types available for extraction. ## View and Configure Data Extraction Events Events collected by PowerConnect typically correspond to an SAP transaction code (t-code) or table, and are represented in the EVENT_TYPE field in Splunk. The PowerConnect events for extraction are defined in the Group Def section of the PowerConnect administration console. The PowerConnect administration console can be accessed by using the /n/bnwvs/main t-code in the managed system. ![image-20210317-144809.png](https://docs.rhondos.com/__attachments/a_1d323249889eb58781c3c7f73c993287fcedcd9ab89b4142c844cae54f051374/image-20210317-144809.png?cb=157e354348f5f524e2e49b49bf43863a) After entering the PowerConnect administration console go to Administrator → Setup Group Def. **Important Note** : It is recommended that you stop all PowerConnnect batch jobs prior to making ++configuration changes++ to the Group Def. ![image-20210317-145151.png](https://docs.rhondos.com/__attachments/a_1d4bfe08197e5a246e9646a44dfe8973bb34472358b701a15e3a24659f9ebcc0/image-20210317-145151.png?cb=e981ff8095a3dab56c60bc1c6939b04f) The Group Def page defines what data will be collected in SAP and sent to Splunk. ![image-20210317-145356.png](https://docs.rhondos.com/__attachments/a_74a7395398a617215e58e036adf647ff705984816dc050a957bf76146db2e1fc/image-20210317-145356.png?cb=0e9d872ab13127ce50fccf68114c09da) Here are the field definitions from this configuration screen: | **Field Name** | **Definition** | **Field Type** | **Mandatory** | | Group Definition | This field corresponds to the EVENT_TYPE visible in Splunk and typically the transaction code or table from SAP | Text | Yes | | Suspend Interval | This field determines the frequency at which data is extracted in the SAP environment (collection interval) | Numeric | Yes | | Delay | This delays the extraction by this number in seconds. Some SAP databases delay writes from the application to the database, due to transactional consistency, reading back using a delay ensures all data is written to the database and readable so buffered data is not lost. | Numeric | No | | Mod. Max Interval | | Checkbox | No | | Maximum Last Interval | This controls how far back (maximum) the agent will look back in the past for data if the agent is not running. If the agent is stopped for an extended period (days or weeks) then getting all data could have a high impact on system resources and impact performance, to prevent this the agent will look back maximum 15x the collection interval | Numeric | Yes | | Use schedule | This checkbox enables or disables the scheduling feature, which is another method to define the data extraction interval | Checkbox | No | | Schedule | Another method to specify the frequency at which data is extracted, this allows data to be collected on a schedule using a mechanism similar to the SM37 batch job scheduling system | Prompt | No | | Job | Status indicator to show whether the job that is created when the **schedule** mechanism is used, is scheduled correctly (and operating correctly) | Icon | No | | AS Instance | Allows the collection of this EVENT_TYPE to be forced to be collected on a specific SAP instance (this should not be configured unless there is a reason to do so, generally this should normally be left blank) | Text | No | | Splunk Index | Specifies the index in which this data should be saved to in the Splunk indexer. You can direct each EVENT_TYPE to a different index, but they must all be send to the same group of indexers, you can no direct an EVENT_TYPE to a specific indexer, only to a specific index | Text | No | | Active | This checkbox activates and deactivates the data extraction for the particular event | Checkbox | Yes | | Category | This is a metadata tag, which is used to categorize the event and it's use i.e. Performance, Database, Security, ITSI | Text | No | |-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|---------------| ## Enable/Disable Data Extraction To enable data extraction for a particular event, ensure that the "Active" field is checked for the row corresponding to the Group Definition. To disable data extraction for a particular event, ensure that the "Active" field is unchecked for the row corresponding to the Group Definition. **Important Note** : It is recommended that you stop all PowerConnnect batch jobs prior to making ++configuration changes++ to the Group Def. ![image-20210317-154207.png](https://docs.rhondos.com/__attachments/a_23d5c88d74718ae6fcb6466af8fd5bd12051d1205373f46481dd6ac56e6e64a9/image-20210317-154207.png?cb=c2a2d10998236ae825e6e0b7d4635d17) ## Modify Data Extraction Interval To modify the data extraction interval for a particular event, change the value in the "Suspend Interval" field to correspond with the number of seconds at which you would like to extract data (e.g. 3600 would mean every hour). **Important Note** : It is recommended that you stop all PowerConnnect batch jobs prior to making ++configuration changes++ to the Group Def. ![image-20210317-155103.png](https://docs.rhondos.com/__attachments/a_92de0af341bfb1700ea22870851fccf59e8d71dbd1f9fd85b9cfdb355f4464ea/image-20210317-155103.png?cb=3ca68cd6f092838151d9d1c5a2ba5d87) --- language: "en" --- # ABAP Installation Guide Archive --- language: "en" --- # ABAP Release Notes --- language: "en" --- # ABAP Release Notes Archive --- language: "en" --- # ABAP Support Matrix The following versions of SAP ABAP NetWeaver products are supported, please pay attention to the combinations of BASIS version and ABA version. The notes will also identify restricted combinations and ACPs required for installation or upgrading to this target combination. NetWeaver stack table | **ABAP** | **BASIS** | **Product** | |--------------------|------------------------------|--------------------------| | **7.00/7.01/7.02** | **7.00/7.01/7.02** ^**(1)**^ | ECC 6.00 EHP0-EHP2 ^(1)^ | | **7.03** | **7.03** | ECC 6.00 EHP3 ^(3)^ | | **7.30** | **7.30** | NetWeaver 7.30 | | **7.31** | **7.31** | ECC 6.00 EHP6 ^(3)^ | | **7.40** | **7.40** | ECC 6.00 EHP7 ^(3)^ | | **7.50** | **7.50** | ECC 6.00 EHP8 ^(3)^ | | **7.51** | **7.51** ^**(2)**^ | NetWeaver 7.51 ^(15)^ | | **7.52** | **7.52** ^**(2)**^ | NetWeaver 7.52 ^(16)^ | NetWeaver stack matrix | **ABAP \\ BASIS** | **7.00** ^**(1)**^ | **7.01/7.02/7.03** | **7.30** | **7.31** | **7.40** | **7.50** | **7.51** ^**(2)**^ | **7.52** ^**(2)**^ | | **7.00/7.01/7.02** | ECC 6.00 EHP0-2 ^(1)^ | | | | | | | | | **7.03** | | ECC 6.00 EHP3 ^(3)^ | | | | | | | | **7.30** | | | NetWeaver 7.30 | | | | | | | **7.31** | | | | ECC 6.00 EHP6 ^(3)^ | | | | | | **7.40** | | | | | ECC 6.00 EHP7 ^(3)^ | | | | | **7.50** | | | | | | ECC 6.00 EHP8 ^(3)^ | | | | **7.51** | | | | | | | NetWeaver 7.51 ^(15)^ | | | **7.52** | | | | | | | | NetWeaver 7.52 ^(16)^ | |--------------------|-----------------------|---------------------|----------------|---------------------|---------------------|---------------------|-----------------------|-----------------------| S/4HANA stack table | **ABAP** | **BASIS** | **Product** | |----------|--------------|----------------------------------| | **75A** | **7.50** | BW4HANA 1.0 ^(4)^ S/4 1511 ^(5)^ | | **75B** | **7.51 (2)** | S/4 1610 ^(7)^ | | **75C** | **7.52 (2)** | S/4 1709 ^(9)^ | | **75D** | **7.53** | BW4HANA2.0 ^(8)^ S/4 1809 ^(11)^ | | **75E** | **7.54** | S/4 1909 ^(13)^ | | **75F** | **7.55** | S/4 2020 ^(14)^ | | **75G** | **7.56** | S/4 2021 ^(17)^ | | **75H** | **7.57** | S/4 2022 ^(18)^ | | **75I** | **758** | S/4 2023 ^(19)^ | | **816** | **816** | S/4 2025 ^(20)^ | S/4HANA stack matrix | **ABAP \\ BASIS** | **7.50** | **7.51** ^**(2)**^ | **7.52** ^**(2)**^ | **7.53** | **7.54** | **7.55** | **7.56** | **7.57** | **758** | **816** | | **75A** | BW4HANA 1.0 ^(4)^ S/4 1511 ^(5)^ | | | | | | | | | | | **75B** | | S/4 1610 ^(7)^ | | | | | | | | | | **75C** | | | S/4 1709 ^(9)^ | | | | | | | | | **75D** | | | | BW4HANA2.0 ^(8)^ S/4 1809 ^(11)^ | | | | | | | | **75E** | | | | | S/4 1909 ^(13)^ | | | | | | | **75F** | | | | | | S/4 2020 ^(14)^ | | | | | | **75G** | | | | | | | S/4 2021 ^(17)^ | | | | | **75H** | | | | | | | | S/4 2022 ^(18)^ | | | | **75I** | | | | | | | | | S/4 2023 ^(19)^ | | | **816** | | | | | | | | | | S/4 2025 ~(20)~ | |-------------------|----------------------------------|--------------------|--------------------|----------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| GREY = not valid SAP combination GREEN = valid SAP combination, and supported by PowerConnect (Supported by SAP) ORANGE = valid combination, but no longer supported by SAP | # | Note | PowerConnect version | ACP Required | ACP File to be Used | End of Support date | |----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|--------------|---------------------|----------------------------| | 1 | SAP NetWeaver 7.00, 7.01, 7.02 supported in mainstream maintenance to end of 2025. | 6.00 or higher | No | N/A | December, 2025 | | 2 | ABAP innovation pack | 6.00 or higher | No | N/A | | | 3 | Only supported when ECC is on top e.g. ECC 6.0 EHP 3, NW 7.00 on its own is not supported, NW 7.00 End Of Support expired in 2017. ECC on 6.0 EHP3 (on NetWeaver 7.0) supported until 2027. Manual TR of BC SET required. v6.00 and above supported. | 6.00 or higher | No | N/A | December, 2027 for ECC 6.0 | | 4 | BW4HANA | 6.00 or higher | Yes | See item B below | December, 2021 | | 5 | S/4 HANA 1511 | 6.00 or higher | Yes | | December, 2020 (expired) | | 6 | *Reserved* | 6.00 or higher | Yes | | December, 2021 | | 7 | S/4 HANA 1610 | 6.01 or higher | No | N/A | December, 2021 | | 8 | BW/4HANA 2.0 | 6.01 or higher | Yes | See item B below | December, 2022 | | 9 | S/4 HANA 1709 | 6.01 or higher | No | N/A | December, 2022 | | 10 | *Reserved* | | | | | | 11 | S/4 HANA 1809 | 6.02 or higher | No | N/A | December, 2023 | | 12 | *Reserved* | | | | | | 13 | S/4 HANA 1909 (also HEC certified) | 6.03 or higher | Yes | See item A below | December, 2024 | | 14 | S/4 HANA 2020 (also HEC certified) | 6.04 or higher | Yes | See item A below | December, 2025 | | 15 | NetWeaver 7.51 | 6.00 or higher | No | N/A | | | 16 | NetWeaver 7.52 | 6.00 or higher | No | N/A | | | 17 | S/4 HANA 2021 (also HEC certified) | 6.08 or higher | Yes | See item B below | | | 18 | S/4 HANA 2022 | 7.01 or higher | No | | | | 19 | S/4 HANA 2023 | 8.00 or higher | No | | | | 20 | S/4 HANA 2025 | 9.00 or higher | No | | | A. ACP for S/4 HANA 1909-2020 systems → [ACP_S42020_BNWVS600_700.SAR](https://docs.rhondos.com/__attachments/a_9a42ecfcf865d6ff70f7b4ca6e34ef218af508e7e08037c90b91be42e9a1c28e/ACP_S42020_BNWVS600_700.SAR.md?cb=0019b6d88b5ecb4f67e697ff47b13849) B. ACP for S/4 HANA 2021 systems → [ACP_S42021_BNWVS600_700.SAR](https://docs.rhondos.com/__attachments/a_758f41bea24a313bbf455bd75655776e24cbf193044c1562ba213f7b3d29883b/ACP_S42021_BNWVS600_700.SAR.md?cb=20176df2e0b041543dfc4e0b15eaa908) C. ACP for NW 7.10 / 7.11 → [ACP_711_BNWVS600_731.SAR](https://docs.rhondos.com/__attachments/a_2e1b7ace3a52662f224922142bf8565b99a21f2ee894e8669e8468cd0398aad5/ACP_711_BNWVS600_731.SAR.md?cb=b8a508003953c10576cbb8f4900673fb) D. ACP for NW 7.00/7.51/7.53 → [ACP_753_BNWVS600_700.SAR](https://docs.rhondos.com/__attachments/a_90f7867bc296e51402b232ba0405b35e117cfdb6b0dacf446a72155c4a266f38/ACP_753_BNWVS600_700.SAR.md?cb=b0af10cfde64812366209aebc7563c9d) --- language: "en" --- # ABAP Troubleshooting ## Summary Please consult the Knowledge Base to see if the problem you are encountering is documented with a resolution. The document below outlines key information required to troubleshoot potential problems associated with the PowerConnect ABAP application. Please acquire and attach the information below when submitting a support incident. Potential scenarios include: * Dumps associated with the PowerConnect application. * PowerConnect batch jobs failures. * PowerConnect metric uploader, check job, or data collector jobs are deactivated. * Expected data was not collected. * Errors in the PowerConnect administrative console. * Delays in data reaching Splunk. ## Mandatory Information for PowerConnect ABAP Support Incidents ### PowerConnect Troubleshooting Logs Starting from PowerConnect SP 6.00 it is possible to extract PowerConnect troubleshooting information to provide the support team with additional details and context. Please ensure these logs are sent as part of any PowerConnect support incident. To access the troubleshooting information, log into the managed system and execute the /n/bnwvs/main transaction. Then go to Goto → Troubleshooting → Download Information ![image-20210510-175057.png](https://docs.rhondos.com/__attachments/a_0155c597de6f6f212ac3755b141388f8213a86608d952d0a10c2a572ddf91e73/image-20210510-175057.png?cb=3f6d2b86d54a2e9dff8fd7c4ebd0c6f6) Once necessary options are confirmed (all options are selected by default), you will be given a file save dialog. The data is saved as compressed ZIP archive, which could be easily attached to the email/ticket. ![image-20210510-175146.png](https://docs.rhondos.com/__attachments/a_a86dd82fc0c603584efef582f809b4124332cf97f67f68fb53cef8612f1a9e7b/image-20210510-175146.png?cb=f4d70c00c911bf0e1fa9ef29e4ca76b7) ## Procedures - ABAP System ### No Data is Being Sent to Splunk Because PowerConnect Batch Jobs are Disabled If there is no data being sent to Splunk, the first item to check is to determine if PowerConnect batch jobs are disabled. To determine this, log into the managed system, and execute the /n/bnwvs/main transaction. Then confirm that all three jobs have a green check box next to their name. ![image-20210510-205329.png](https://docs.rhondos.com/__attachments/a_86e39eddd816dacd19a230301e216abe5ea94d8d086833039c6b1608140652a7/image-20210510-205329.png?cb=5f0106294f28e0a3c75a26b178e6954e) If one or more of the batch jobs are disabled, a red checkbox will be displayed: ![image-20210510-204402.png](https://docs.rhondos.com/__attachments/a_f24d1835339447df1b5ee943cf205869d67de993bbba18dfbe94d0f6067673ea/image-20210510-204402.png?cb=adf962bf1f6c45f1580034f8eac3c6a3) To restart the jobs, select the corresponding button to restart the job, and input the username responsible for executing the PowerConnect batch job. ![image-20210510-204821.png](https://docs.rhondos.com/__attachments/a_e122a2c599a0983141b0dfb8a18a0ac8cb9e8f20487a4be82891d96b4d8895d0/image-20210510-204821.png?cb=b7902dda99c8462f373113dc142c1a3e) Refresh the screen after several minutes and confirm that all the checkboxes are displaying green. Then check confirm data is visible in Splunk. ![image-20210510-205306.png](https://docs.rhondos.com/__attachments/a_35f17a0649cdb1e01ce28fcec48a7a4a86b829bff52422c489daff9f70b64b60/image-20210510-205306.png?cb=5f0106294f28e0a3c75a26b178e6954e) ### Data for Particular Extractor is Not Visible in Splunk The first step is to review the Group Definition configuration in the system where you cannot see the data to confirm it is active. Complete these steps by logging into the managed system in SAP, and executing the /n/bnwvs/main transaction. Confirm that the three batch jobs are activated (green check boxes). If the jobs are deactivated, reactivate them, and check in Splunk in accordance with the interval defined for the extractor (see below for how to obtain this information). ![image-20210510-191242.png](https://docs.rhondos.com/__attachments/a_9155141ccab40267819d97e58e9a2d7af9187780b4f81a948ae9a94cb9aab718/image-20210510-191242.png?cb=2f4c5e46dd8c2aa58d1a0033b7ce2b04) Then go to Administrator → Setup Group Def. ![image-20210510-191544.png](https://docs.rhondos.com/__attachments/a_aeac09198f4ca21fc54aae2adf35895368dd55f274a5e0596123efc66925757e/image-20210510-191544.png?cb=f49c3f3270218c9406a396043b431fc1) Confirm that the Active box is checked next to the extractor for which you are missing data, and that your Splunk search parameters align with the interval defined in the Group Def configuration. ![image-20210510-191636.png](https://docs.rhondos.com/__attachments/a_2e0f9fbc97321c55c028d6ae6127f22bc7c24f6f50a09e415249e5574ef8d3a7/image-20210510-191636.png?cb=9fb0032938a000b37bc9a7d0364f1cdb) ### Metric Errors in the PowerConnect Administrative Console If there are metric errors in the PowerConnect Administrative Console they will be visible by logging into the managed system and executing the /n/bnwvs/main transaction. If there are metric errors, there will be statistics visible in the following section of the administrative console. ![image-20210510-194402.png](https://docs.rhondos.com/__attachments/a_32fc3213daf795c6f67046a378696a4dd825f84c43c401260c415cf2fefc2ef1/image-20210510-194402.png?cb=f8a3829d7c82a500d1517a6912f1cc05) In case of metric errors, extract the PowerConnect Troubleshooting Logs (see "PowerConnect Troubleshooting Logs") and attach them to the support incident. ### PowerConnect ABAP Dumps If there are dumps associated with the PowerConnect application they will be visible in the ST22 transaction. Additionally, you can view if there are PowerConnect dumps in the PowerConnect Administrative Console by logging into the managed system and executing the /n/bnwvs/main transaction. Then click on the following icon in the top right side of the screen: ![image-20210510-195530.png](https://docs.rhondos.com/__attachments/a_c9f7db3414ede15dd51ed65f41328beb4820c5aacd84e43f13557946b3cbc894/image-20210510-195530.png?cb=2c90eaecca90966f796f675181a8a630) If there are dumps visible, the icon associated with Dumps will be red. If you wish to view the dumps, click on the Details icon. ![image-20210510-195624.png](https://docs.rhondos.com/__attachments/a_e143e8ebb566b2bcb83b894ac27cfd34b97256f3dd16d707dad53b3ea6c57716/image-20210510-195624.png?cb=9e92b6a00c04590a19ba7b5e7a20a4b9) If you find there are dumps associated with the PowerConnect application please extract the PowerConnect Troubleshooting Logs (see "PowerConnect Troubleshooting Logs") and attach them to the support incident. ### PowerConnect Batch Job Failures If there are batch job failures associated with the PowerConnect application they will be visible in the SM37 transaction. Additionally, you can view if there are PowerConnect batch job failures in the PowerConnect Administrative Console by logging into the managed system and executing the /n/bnwvs/main transaction. Then click on the following icon in the top right side of the screen: ![image-20210510-195530.png](https://docs.rhondos.com/__attachments/a_c9f7db3414ede15dd51ed65f41328beb4820c5aacd84e43f13557946b3cbc894/image-20210510-195530.png?cb=2c90eaecca90966f796f675181a8a630) If there are batch job failures, the icon associated with Jobs will be red. If you wish to view the batch job failures, click on the Details icon. ![image-20210510-203000.png](https://docs.rhondos.com/__attachments/a_af8654f001d035581d21f2f8e7be235f2af60908c593fa061b86600e94388a52/image-20210510-203000.png?cb=6058e306a530d7e351580a0e3067c10f) Highlight the batch job of interest, and then select the Job Log button. ![image-20210510-201106.png](https://docs.rhondos.com/__attachments/a_ebbb649c87e368a897ea5becf062e446d979fbc8e6247bee2afd3edfb435335d/image-20210510-201106.png?cb=d0b0b38491425704cc4f56400926d56a) In some instances you will see if the batch job failed because of a ST22 dump or because of another cause. If the job log references an ST22 dump please see the "PowerConnect ABAP Dumps" section mentioned above. If you see something similar to the screenshot below which references the system log, please continue onwards. Please take a screenshot for future reference. ![image-20210510-201322.png](https://docs.rhondos.com/__attachments/a_9e0a520040a58b22da2ea2241bc8feba1219901aba0d2c46fc90fa48c2223962/image-20210510-201322.png?cb=fa89352646003c1db03b4a8add42b31e) Go back to the SM37 summary screen, and select the Change Layout button. ![image-20210510-201438.png](https://docs.rhondos.com/__attachments/a_de78d4ed69bfa52121774919d7bc3efafed44da83138d145aa36886972a6a17e/image-20210510-201438.png?cb=33e727777d1ce5934991d434d2f94cc3) Add the Executing server, End date, End time, and Work process number to the layout. ![image-20210510-201604.png](https://docs.rhondos.com/__attachments/a_97fc913d9b3efb4e0d524fc4320485bf7fdc316e1dc6ef2ca40599b505c6b7e1/image-20210510-201604.png?cb=32a0955a4721be60c327986e09c956ad) Export the information displayed to be submitted with the support incident, and write down the Executing server, End date, End time, and Work process number for future reference. ![image-20210510-201910.png](https://docs.rhondos.com/__attachments/a_01a6e9eeb32b7a69c2676ac06173faf41db70d39e8dcb4c5638160f3ab6c40f5/image-20210510-201910.png?cb=d679216eaa434d59f21d18d1e861666f) Execute the SM51 transaction, and double-click on the server name referenced from the SM37 data. ![image-20210510-202030.png](https://docs.rhondos.com/__attachments/a_f62a9ce5aa6e08f4188a65afa6383dcfc792ae2bce73cad4c33285ec90dee734/image-20210510-202030.png?cb=a140c8a366d8ba5b5ee1e30418356937) Reference the work process number noted from the SM37 data and highlight the row associated with that number. Then from the top menu go to Administration → Trace → Display File → Current ![image-20210510-202241.png](https://docs.rhondos.com/__attachments/a_0513210ae58639d75d0adf9d4e0a5b1a4a5f53d0fed039b5a6e75fa7fdec5cbc/image-20210510-202241.png?cb=0b5ec8f439b6f02714c3e8a4456c0c77) Export the data referenced in the screen below in a .txt format, and attach it to the support incident along with the PowerConnect Troubleshooting Logs (see PowerConnect Troubleshooting Logs), the SM37 batch job view referenced earlier, and a screenshot of the SM37 job log. ![image-20210510-202527.png](https://docs.rhondos.com/__attachments/a_0c9daea671fa13617d05f60aaf04885bf5c4ba3fa3445b8320808aeb91e1074f/image-20210510-202527.png?cb=55b80b70cd04f69b078d27e23f46b8bb) ## Procedures - Splunk System ### Data for Particular Extractor is Not Visible in Splunk The first step in this case is to check with the SAP team to review the Group Definition configuration in the system where you cannot see the data to confirm it is active. Please review the section above titled "Data for Particular Extractor is Not Visible in Splunk" in the "Procedures - ABAP System" section. If for some reason, you do not have access to the SAP system, please access the Extractor Status dashboard, made available during the Splunkbase App 6.2 release. This dashboard can be accessed by going to the PowerConnect App in your Splunk instance. Then select PowerConnect → Extractor Status. ![image-20210510-190420.png](https://docs.rhondos.com/__attachments/a_72bd54d0f22a68041dd734651d35ba1780fe7e5305c535be21dc20e6d98537e4/image-20210510-190420.png?cb=dfbe1454c5f44853c970d9675f459e22) You will be brought to the dashboard below. Enter the time where the data was not collected and the system impacted in the user selection parameters. If the extractor is not activated, ask the team responsible for the administration of the PowerConnect admin tool in SAP to activate the extractor based on your requirements. Otherwise, export the information to Excel and attach it to the support incident. ![image-20210510-190614.png](https://docs.rhondos.com/__attachments/a_597a8dd07c9972967a4636a5a9f8ec804aeabda1b4ffa59cb2d56108a1159254/image-20210510-190614.png?cb=49e898b926d28b17975945b75bdae3e0) ### Delays in SAP Data Reaching Splunk If there are instances in which the data is not reaching Splunk at the interval defined in the Group Definition section of the PowerConnect administrative console please perform the following searches in your Splunk environment. Perform this search over the time period, during which the service was disrupted. Export these results in an Excel format and attach them to the support incident along with a screenshot of the graphs. #### Metrics in PowerConnect To Send Queue *index=* ***\*** *source=* ***\*** *EVENT_TYPE=PC_HEALTH* *\| timechart span=5m max(TOTAL_TO_SEND)* #### Count of PowerConect Errors Over Time *index=* ***\*** *source=* ***\*** *EVENT_TYPE=PC_HEALTH* *\| timechart span=5m max(IN_ERROR)* #### Delays in Data Reaching Splunk for a Specific Event Type *index=* ***\*** *source=* ***\*** *EVENT_TYPE=* ***\*** *\| fields _indextime CURRENT_TIMESTAMP* *\| eval indextime=_indextime* *\| eval indextime_human_readable=strftime(indextime,"%m/%d/%Y %H:%M:%S")* *\| eval Data_Extraction_Time_Epoch=strptime(CURRENT_TIMESTAMP,"%Y%m%d%H%M%S")* *\| eval Data_Extraction_Time=strftime(Data_Extraction_Time_Epoch,"%m/%d/%Y %H:%M:%S")* *\| eval difference=round(indextime-Data_Extraction_Time_Epoch,0)* *\| rename Data_Extraction_Time as "Time Data Extracted in PowerConect", indextime_human_readable as "Time Data Indexed by Splunk", difference as "Difference Between Index Time and Time Data Extracted in PowerConnect (s)"* *\| table "Time Data Indexed by Splunk" "Time Data Extracted in PowerConect" "Difference Between Index Time and Time Data Extracted in PowerConnect (s)"* --- language: "en" --- # Activate Business Configuration Set for Dynatrace (PowerConnect ABAP 9.X) → This action must be performed in your **productive client**as the Business Configuration (BC) Set contains client-dependent data. * Call transaction SCPR20. * In the field "BC Set" enter "/BNWVS/BCSET_DT" and press enter. ![image-20231107-134903.png](https://docs.rhondos.com/__attachments/a_5164f7caf350374f2faf62a3558ad66edea0b2518a98e0b25234371965cee483/image-20231107-134903.png?cb=d225a613dc0812529bd20db7633422bb) * Choose "**BC Set → Activate**" in the menu to process the activation. ![grafik-20210105-064639.png](https://docs.rhondos.com/__attachments/a_4992d3da0a2243187021cf6d2a688746379c1d21171f938a7a3e58225ca69c89/grafik-20210105-064639.png?cb=46882df33c7f61286f3d3b37e13fed38) * Create a customizing request to process the activation. → Caution: If the transport was not requested, check if settings in SCC4 allow this action. → Import the transport into DEV and in any subsequent system from there. ![grafik-20210105-064848.png](https://docs.rhondos.com/__attachments/a_060135d0eac675563bcca21a5fa261d4b3e72f6430eebc2638268d1b29107ba3/grafik-20210105-064848.png?cb=6f0da2c8774f85bd8287dbfd57f8cdae) Click on Save ![image-20231107-135000.png](https://docs.rhondos.com/__attachments/a_1ea173dcd72179bd1a9b7dc4d266c22ed746d2a1454650bd80c220b141f782d0/image-20231107-135000.png?cb=77e1aad0fcb4ce4ae08d0bc0f44fe875) Click on Continue ![image-20231107-135021.png](https://docs.rhondos.com/__attachments/a_0bdc88dba4e43ac0d94ef395ea421f4936a595878aae9e4018d7d70cd3346b13/image-20231107-135021.png?cb=3d96bc655f4dd215765f937f9c220bcf) Click on Continue Activation ![image-20231107-135045.png](https://docs.rhondos.com/__attachments/a_086cd6488047097725eda9e36e9fee3e89b3811431fa0fcdb557cf5c46e4658c/image-20231107-135045.png?cb=55ae16267ee5bb32daf7b9241d945c98) * Check the logs for successful execution by clicking on the **glasses**. ![image-20210105-071014.png](https://docs.rhondos.com/__attachments/a_c1346f8dc7393458e3a72fceefa177cf69a68af35f79880a4d613859bd33b1e3/image-20210105-071014.png?cb=0878768680b3e5757f4a26cd07ebdfdb) ![image-20231107-135152.png](https://docs.rhondos.com/__attachments/a_606355d8ff473ea2e100eea9c7ef1169f0dcf501ac0d506c5c81e14ce9d05d42/image-20231107-135152.png?cb=3c36984dc946fb509d076d74f465e0bd) If BC Set was not imported successfully, beside the logs, you will get a notice when starting the PowerConnect for SAP Solutions application using transaction "/BNWVS/MAIN". Next step is to[import the PowerConnect roles](https://docs.rhondos.com/powerconnect-for-sap-solutions/upload-powerconnect-roles-powerconnect-abap-9-x.md) to your productive client. --- language: "en" --- # Activate Business Configuration Set for Dynatrace (PowerConnect ABAP 8.X) → This action must be performed in your **productive client**as the Business Configuration (BC) Set contains client-dependent data. * Call transaction SCPR20. * In the field "BC Set" enter "/BNWVS/BCSET_DT" and press enter. ![image-20231107-134903.png](https://docs.rhondos.com/__attachments/a_eccff321dc8e5db550a75cb1059a0407aa55ca9f952151e001a58f209e6f1f08/image-20231107-134903.png?cb=d225a613dc0812529bd20db7633422bb) * Choose "**BC Set → Activate**" in the menu to process the activation. ![grafik-20210105-064639.png](https://docs.rhondos.com/__attachments/a_ae349da3e720fa9aa689cef6653468af6ff83c2b465aa96947bd7f70284b586c/grafik-20210105-064639.png?cb=46882df33c7f61286f3d3b37e13fed38) * Create a customizing request to process the activation. → Caution: If the transport was not requested, check if settings in SCC4 allow this action. → Import the transport into DEV and in any subsequent system from there. ![grafik-20210105-064848.png](https://docs.rhondos.com/__attachments/a_51cdd9fbd6250ce3456cfa5ccf993033032719a242276959d796d816f3b8090e/grafik-20210105-064848.png?cb=6f0da2c8774f85bd8287dbfd57f8cdae) Click on Save ![image-20231107-135000.png](https://docs.rhondos.com/__attachments/a_307f27ec001ec47407cf1d964483c1861eef3241ca5d31add71eb1e31cd6e885/image-20231107-135000.png?cb=77e1aad0fcb4ce4ae08d0bc0f44fe875) Click on Continue ![image-20231107-135021.png](https://docs.rhondos.com/__attachments/a_77bc2af6edf071cd3e2384e4c3bb7483ad7158fa3167b0da7670c1519485d12e/image-20231107-135021.png?cb=3d96bc655f4dd215765f937f9c220bcf) Click on Continue Activation ![image-20231107-135045.png](https://docs.rhondos.com/__attachments/a_41cbb5a8c57e0b5ccca139266e04c4c48af798583d540f85be6dcd584e115d79/image-20231107-135045.png?cb=55ae16267ee5bb32daf7b9241d945c98) * Check the logs for successful execution by clicking on the **glasses**. ![image-20210105-071014.png](https://docs.rhondos.com/__attachments/a_9c86ef6e295985d72ac758e0384d3110f5dd895075a548963827a2ef5922dd96/image-20210105-071014.png?cb=0878768680b3e5757f4a26cd07ebdfdb) ![image-20231107-135152.png](https://docs.rhondos.com/__attachments/a_9eb200056243595e9d6c7a43271274b0ecdd3128797c8fe4c1b9549a9cb55ae9/image-20231107-135152.png?cb=3c36984dc946fb509d076d74f465e0bd) If BC Set was not imported successfully, beside the logs, you will get a notice when starting the PowerConnect for SAP Solutions application using transaction "/BNWVS/MAIN". Next step is to[import the PowerConnect roles](https://docs.rhondos.com/powerconnect-for-sap-solutions/upload-powerconnect-roles-powerconnect-abap-8-x.md) to your productive client. --- language: "en" --- # Activate Business Configuration Set for Splunk (PowerConnect ABAP 9.X) → This action must be performed in your **productive client**as the Business Configuration (BC) Set contains client-dependent data. * Call transaction SCPR20. * In the field "BC Set" enter "/BNWVS/BCSET_SPLUNK" and press enter. ![image-20231120-135835.png](https://docs.rhondos.com/__attachments/a_be41964482bdfbeaf98bcddffdf0ddec3d371df99fc3c44679870d3e35fb08e4/image-20231120-135835.png?cb=759b902e843e46806b48057576844e4e) * Choose "**BC Set → Activate**" in the menu to process the activation. ![grafik-20210105-064639.png](https://docs.rhondos.com/__attachments/a_c34b1a013a434a24dd876eb46e920db8746fce235bd70aa0ec974d4d188e4810/grafik-20210105-064639.png?cb=46882df33c7f61286f3d3b37e13fed38) * Create a customizing request to process the activation. → Caution: If the transport was not requested, check if settings in SCC4 allow this action. → Import the transport into DEV and in any subsequent system from there. Click on Continue ![image-20231120-140027.png](https://docs.rhondos.com/__attachments/a_f35945cc8626b4abe8be00650ff66fa8bb51f65250a6cd98ec91bf051fe6746f/image-20231120-140027.png?cb=aa80873cefca1fd245b416e91ae55e6c) Click on Continue ![image-20231120-140055.png](https://docs.rhondos.com/__attachments/a_233a6caab96b36e896f7feae4a7e6d7126c6353854dbbe28276855ce4d2bca2f/image-20231120-140055.png?cb=e927a4fd9c30610246c680f3eb315aff) Click on Continue Activation ![image-20220720-225919.png](https://docs.rhondos.com/__attachments/a_6846de5132e0c8f0ba5a8d52956b2150730c50c4b75a81ad47211da270d6aac0/image-20220720-225919.png?cb=45077caf42503038b4a089b22e97903e) ![image-20210105-070854.png](https://docs.rhondos.com/__attachments/a_0c990c4868133a6eb88259b360946535f6b89adf76e48d1a4e95ca2499801274/image-20210105-070854.png?cb=880877aa553ccfbde80f4b00ea244a0c) * Check the logs for successful execution by clicking on the **glasses**. ![image-20210105-071014.png](https://docs.rhondos.com/__attachments/a_a97c7acf65b137d4a8c89fe839185548d645a153a80cf732a157c64f12d35996/image-20210105-071014.png?cb=0878768680b3e5757f4a26cd07ebdfdb) Confirm there are no errors or warnings. If there are errors or warnings, please contact PowerConnect support: [Raising a PowerConnect Support Request](https://docs.rhondos.com/powerconnect-for-sap-solutions/raising-a-powerconnect-support-request.md) ![image-20231120-140246.png](https://docs.rhondos.com/__attachments/a_b22d7225f6d7fe72e8da6da27baaa6db3afcd73b6b79a5a51d425658f89cefce/image-20231120-140246.png?cb=2691ef151cb7dcc73510538f8258db49) If BC Set was not imported successfully, beside the logs, you will get a notice when starting the PowerConnect for SAP Solutions application using transaction "/BNWVS/MAIN". Next step is to[import the PowerConnect roles](https://docs.rhondos.com/powerconnect-for-sap-solutions/upload-powerconnect-roles-powerconnect-abap-7-x.md) to your productive client. --- language: "en" --- # Activate Business Configuration Set for Splunk (PowerConnect ABAP 8.X) → This action must be performed in your **productive client**as the Business Configuration (BC) Set contains client-dependent data. * Call transaction SCPR20. * In the field "BC Set" enter "/BNWVS/BCSET_SPLUNK" and press enter. ![image-20231120-135835.png](https://docs.rhondos.com/__attachments/a_e27bcaaab56f51f1ea3eb1934272f944f8db0af07743e579bb26fc7cf4bcf7cb/image-20231120-135835.png?cb=759b902e843e46806b48057576844e4e) * Choose "**BC Set → Activate**" in the menu to process the activation. ![grafik-20210105-064639.png](https://docs.rhondos.com/__attachments/a_d5461a635a7a28bbaf65611f87acc1f7facd212097c28db4c3fd4da049ac6ae2/grafik-20210105-064639.png?cb=46882df33c7f61286f3d3b37e13fed38) * Create a customizing request to process the activation. → Caution: If the transport was not requested, check if settings in SCC4 allow this action. → Import the transport into DEV and in any subsequent system from there. Click on Continue ![image-20231120-140027.png](https://docs.rhondos.com/__attachments/a_58c0920386eee2ea8e6dd2e1e69fc9ca842a2b5403e170083eea2dcfe7612a5e/image-20231120-140027.png?cb=aa80873cefca1fd245b416e91ae55e6c) Click on Continue ![image-20231120-140055.png](https://docs.rhondos.com/__attachments/a_8c480df23595cf0075d0a55c2c88d111f87606ea4d39a72b70e61ccb213ea52f/image-20231120-140055.png?cb=e927a4fd9c30610246c680f3eb315aff) Click on Continue Activation ![image-20220720-225919.png](https://docs.rhondos.com/__attachments/a_bd1bba3d2d42cd3d9b41ec4abd8b30499d023888cd21b1961be0d5b86e6a92b6/image-20220720-225919.png?cb=45077caf42503038b4a089b22e97903e) ![image-20210105-070854.png](https://docs.rhondos.com/__attachments/a_0b7ade829e6c395145eb8ab480e80bc2e02a6994ab450ed04b739777eeb9a13d/image-20210105-070854.png?cb=880877aa553ccfbde80f4b00ea244a0c) * Check the logs for successful execution by clicking on the **glasses**. ![image-20210105-071014.png](https://docs.rhondos.com/__attachments/a_a54a80e77273d750ec943f9f2bc5beaf11fd605247c88927a0c302f8702778a5/image-20210105-071014.png?cb=0878768680b3e5757f4a26cd07ebdfdb) Confirm there are no errors or warnings. If there are errors or warnings, please contact PowerConnect support: [Raising a PowerConnect Support Request](https://docs.rhondos.com/powerconnect-for-sap-solutions/raising-a-powerconnect-support-request.md) ![image-20231120-140246.png](https://docs.rhondos.com/__attachments/a_d65ee08308a3db4395f588c91bd2c4c424508c96a38d4eab98ff2ddc839f36a0/image-20231120-140246.png?cb=2691ef151cb7dcc73510538f8258db49) If BC Set was not imported successfully, beside the logs, you will get a notice when starting the PowerConnect for SAP Solutions application using transaction "/BNWVS/MAIN". Next step is to[import the PowerConnect roles](https://docs.rhondos.com/powerconnect-for-sap-solutions/upload-powerconnect-roles-powerconnect-abap-7-x.md) to your productive client. --- language: "en" --- # Activate Business Configuration Sets (PowerConnect ABAP 8.X) BCSETs are platform specific, please use the appropriate guide following by one of links below: [Activate Business Configuration Set for Splunk](https://docs.rhondos.com/powerconnect-for-sap-solutions/activate-business-configuration-set-for-splunk-pow.md) [Activate Business Configuration Set for Dynatrace](https://docs.rhondos.com/powerconnect-for-sap-solutions/activate-business-configuration-set-for-dynatrace-.md) --- language: "en" --- # Activate Business Configuration Sets (PowerConnect ABAP 9.X) BCSETs are platform specific, please use the appropriate guide following by one of links below: [Activate Business Configuration Set for Splunk](https://docs.rhondos.com/powerconnect-for-sap-solutions/activate-business-configuration-set-for-splunk-p-1.md) [Activate Business Configuration Set for Dynatrace](https://docs.rhondos.com/powerconnect-for-sap-solutions/activate-business-configuration-set-for-dynatrac-1.md) --- language: "en" --- # Activate Business Configuration Sets (PowerConnect ABAP 7.X) → This action must be performed in your **productive client**as the Business Configuration (BC) Set contains client-dependent data. * Call transaction SCPR20. * In the field "BC Set" enter "/BNWVS/BCSET_500" and press enter. ![grafik-20210105-064613.png](https://docs.rhondos.com/__attachments/a_586b51115c15e1fbb735d8d933bc7f53b3fb863f21ef3786067decb4ae155f96/grafik-20210105-064613.png?cb=3bf180b91d38abd2951319febb37f3c9) * Choose "**BC Set → Activate**" in the menu to process the activation. ![grafik-20210105-064639.png](https://docs.rhondos.com/__attachments/a_21ee755b02899a036a2e0bf9e082fc97283649ec887bb736d1ecfdd856cc11b3/grafik-20210105-064639.png?cb=46882df33c7f61286f3d3b37e13fed38) * Create a customizing request to process the activation. → Caution: If the transport was not requested, check if settings in SCC4 allow this action. → Import the transport into DEV and in any subsequent system from there. ![grafik-20210105-064848.png](https://docs.rhondos.com/__attachments/a_c84b8eb4156f54740f69e0d79cbe0c765b5956b92d8818885a7c45ac5f309186/grafik-20210105-064848.png?cb=6f0da2c8774f85bd8287dbfd57f8cdae) Click on Save ![image-20220720-225800.png](https://docs.rhondos.com/__attachments/a_2e1d3a16ba4ab6f06ee86c954508bdf39086c7f2fe762a6ff04efd29bb7d95aa/image-20220720-225800.png?cb=0f111958d48dce4635c453c8cef2eccf) Click on Continue ![image-20220720-225828.png](https://docs.rhondos.com/__attachments/a_c486a8cb03a1bfebe8bea35c7053178d0c5175ae0bdd0aa4882d35983e8605fd/image-20220720-225828.png?cb=49c64a852cb1568971af9d9c847ba17c) Click on Continue Activation ![image-20220720-225919.png](https://docs.rhondos.com/__attachments/a_d1817ab63b3b7d2316e4fb3b5ed30d44b6b038807f568f31d45aba49e587d164/image-20220720-225919.png?cb=45077caf42503038b4a089b22e97903e) ![image-20210105-070854.png](https://docs.rhondos.com/__attachments/a_8b7ee14fedbbdfa3655a3ba87dacb05fd0ef81302a7c530e811869a18d35ef3c/image-20210105-070854.png?cb=880877aa553ccfbde80f4b00ea244a0c) * Check the logs for successful execution by clicking on the **glasses**. ![image-20210105-071014.png](https://docs.rhondos.com/__attachments/a_1541686ef0b23afbd3f5d9b049abd668c4c8c06a367e34143bb2c77edc85fb7c/image-20210105-071014.png?cb=0878768680b3e5757f4a26cd07ebdfdb) ![image-20210105-071047.png](https://docs.rhondos.com/__attachments/a_70d9fc6a8cea16ffbf383b9a3a4afe910a9baf6b0ade8e5865d0dfd7525e60cb/image-20210105-071047.png?cb=2ed85386c09d555dfab52af92570baef) If BC Set was not imported successfully, beside the logs, you will get a notice when starting the PowerConnect for Splunk application using transaction "/BNWVS/MAIN". Next step is to[import the PowerConnect roles](https://docs.rhondos.com/powerconnect-for-sap-solutions/upload-powerconnect-roles-powerconnect-abap-7-x.md) to your productive client. --- language: "en" --- # Additional Actions for Dual Stack Systems (PowerConnect Java - All Versions) The PowerConnect license is generated against the installation number in the SAP license key that is installed in to the system. In **Dual-Stack** systems like PI, SolMan there is no license installed in the JAVA side of the dual stack installation, instead Java relies on the ABAP license. In this case there is no functionality for PowerConnect agent to check the license key in the ABAP side of the dual stack installation and therefor the Java license key can not be validated. In order to allow the PowerConnect agent to validate the license, you need to install an SAP license in to the Java stack. In the /nwa application a valid license must be shown otherwise the PowerConnect agent will not startup. You can safely run a Java license in the Java side of a dual stack solution, even when there is a license in the ABAP solution. The /nwa must have a valid license installed, and there must be a valid installation # and SID shown. ![image-20201006-064020.png](https://docs.rhondos.com/__attachments/a_60f4377befe84f6d9e53a2dfcb044af4cd718815fd1f3f40576b96e96678414f/image-20201006-064020.png?cb=4fdb9c5d9850f19f34b7deb85961a7ec) ![image-20201006-064028.png](https://docs.rhondos.com/__attachments/a_071decacc29b0dd18adb193163f7ab72e3666f5a8cc37f878895f3dada23a579/image-20201006-064028.png?cb=90d295e37852582d9aab9273b837755c) --- language: "en" --- # ADS_CHECK - Adobe Document Service(ADS) availability check ## Data Description The ADS_CHECK event is used to determine the status of the Adobe Document Service(ADS) connection to SAP. ## Potential Use Cases This event could be used in the following scenarios: * Alert on instances where ADS connection goes down. * Visualize ADS connection failures over time. * Correlate ADS connection failures to other system activities. ## Metric Configuration Out of the Box, the 'ADS' destination name is used to check the connection. However, If customers have a different name for the ADS destination in their system, they can configure the destination in Metric configuration. To do this, log into the managed system and execute the /n/BNWVS/MAIN transaction. Then, go to Administrator → Setup Metric → Metric Configuration. ![image-20221027-020301.png](https://docs.rhondos.com/__attachments/a_74da2db5340ad3b9a7fbb7e28eb555f30e90aae4c2dfaf847d8988126e110633/image-20221027-020301.png?cb=5099640827e692c098a43b5eb91ceae0) Then Enter the Destination name in the 'Parameter Value' column for ADS_CHECK if it is different from ADS. ![image-20221027-022343.png](https://docs.rhondos.com/__attachments/a_a539f9976b25f99a77988c064ed65dc679f3935e65cffb5307d475dd47ca07b0/image-20221027-022343.png?cb=ba5cd954ff788f42c014698007c1d46d) ## Splunk Event The event will look like this in Splunk: ![image-20221027-022530.png](https://docs.rhondos.com/__attachments/a_da8146fa633f2333ed2b4b1f378287408025e7328fdff63fe28d810d898923f6/image-20221027-022530.png?cb=893db3a3d31da152f3a5ec6c250e885b) ## SAP Navigation Log into the managed system and execute the report FP_CHECK_DESTINATION_SERVICE to check the ADS connection. ![image-20221027-022726.png](https://docs.rhondos.com/__attachments/a_b4768dc12436b44a4e55a0d8abab1c237d27e68d67dfe57da7d569963c4fc92c/image-20221027-022726.png?cb=6c3618bebb6c8577e22495ad6483aed3) --- language: "en" --- # AL08 ## Data Description The AL08 event is used in SAP to show the list of all the users who are logged on to the system globally or for all the instances in the system which are active. ## Potential Use Cases This event could be used in the following scenarios: * View users that are logged in. * Alert on sensitive users logging into the system. * View log-in trends over time. ## Splunk Event The event will look like this in Splunk: ![image-20210401-222007.png](https://docs.rhondos.com/__attachments/a_59d14412027ddf34b1b07656de06589c12283562d218071af09452e3d631fef6/image-20210401-222007.png?cb=0e72a4ba62686b04ed4eacc876321582) ## SAP Navigation Log into SAP, and execute the AL08 transaction code. The data that is sent to Splunk will then be visible. ![image-20210401-222101.png](https://docs.rhondos.com/__attachments/a_773360577d2df7d61a5225f29e60cda2929d9be72cb5e69757ab083f74c006b1/image-20210401-222101.png?cb=334a6987d82e9030452aff93b0b7ca65) --- language: "en" --- # AL11 ## Data Description The AL11 event is used in SAP to display the SAP Directories and associated files. ## Potential Use Cases This event could be used in the following scenarios: * Monitoring to confirm that files are being added to the directory at the correct time. * Confirm that critical files are added to the SAP directories. * Monitor the size of certain SAP directories. ## Metric Filters The Metric Filter needs to be defined to extract data for this event. Log into the managed system and execute the /n/bnwvs/main transaction code. Then go to Administrator → Metric filters → AL11 filter. ![image-20210402-024015.png](https://docs.rhondos.com/__attachments/a_ad78100799d23306b32adef025e61490ac636deffeba9ad4dc37df56c593dc65/image-20210402-024015.png?cb=e27d724e09ea3c2e55dd3f5ae96d731d) Then fill out the configuration based on your needs, and save. Below is a summary of the fields and their associated function: * Directory Parameters - This field is mandatory, and is the SAP directory where the information is stored. * Context Path - This field is mandatory, and is the file path where the information is stored. * Collect names - This field is optional, and is a checkbox to activate or deactivate the collection of the file names stored within the file path (i.e. AL11 with EVENT_SUBTYPE="NAMES"). * Collect count - This field is optional, and is a checkbox used to activate or deactivate the collection of the summary level statistics associated with the directory (i.e. AL11 with EVENT_SUBTYPE="") * Collect Child Directories: This field is optional, and is a checkbox used to activate or deactivate the collection of the child directories present in the directory mentioned in the first column 'Directory Parameter'. Here is an example of what the AL11 metric filter looks like when it is filled out: ![image-20240324-040536.png](https://docs.rhondos.com/__attachments/a_c4713ccbb1895762c58ef9859e7199d8c0872ca6f1100b3eb5fdae112dccc006/image-20240324-040536.png?cb=10099ea73e8fb1d653f45a5aa8782405) ## Splunk Event ### **AL11 with EVENT_SUBTYPE=""** **Important Note:**The Metric Filter needs to be configured to enable data extraction for this event. The event will look like this in Splunk: ![image-20210402-020218.png](https://docs.rhondos.com/__attachments/a_9fd1e82daab1798f99c7a52782bd3a3bbda91da9a2d34d63d7a1db68c47c6920/image-20210402-020218.png?cb=28e99990c958eff90d26b004b32b5aa3) ### **AL11 with EVENT_SUBTYPE="NAMES"** **Important Note:**The Metric Filter needs to be configured to enable data extraction for this event. The event will look like this in Splunk: ![image-20210402-020243.png](https://docs.rhondos.com/__attachments/a_923cb2c0ba1fe34d357f273c6d6412b71c38cdfb0263c8ce893e3b23b95b8178/image-20210402-020243.png?cb=c6ba657c64e46654f750d729427ed41a) ## SAP Navigation ### **AL11 with EVENT_SUBTYPE=""** **Important Note:**The Metric Filter needs to be configured to enable data extraction for this event. Log into the managed system and execute the AL11 transaction code. You will then be brought to the Directory summary page, which will match the data in Splunk. ![image-20210402-020439.png](https://docs.rhondos.com/__attachments/a_e2f03ad1c40f3c42449ae46fc67246c9c819c2a7cf071d01cdfab9027651666f/image-20210402-020439.png?cb=7ad39a8825fc34bbaba8dcd55398feec) ### **AL11 with EVENT_SUBTYPE="NAMES"** **Important Note:**The Metric Filter needs to be configured to enable data extraction for this event. Log into the managed system and execute the AL11 transaction code. You will then be brought to the Directory summary page. ![image-20210402-020439.png](https://docs.rhondos.com/__attachments/a_e2f03ad1c40f3c42449ae46fc67246c9c819c2a7cf071d01cdfab9027651666f/image-20210402-020439.png?cb=7ad39a8825fc34bbaba8dcd55398feec) Double-click on the directory line of interest to go to the directory page where the file detail is shown. ![image-20210402-020538.png](https://docs.rhondos.com/__attachments/a_5b1d591ec168672bfe89b60cc4dda8325cf7b40bac3c2b2008545230cf2255fa/image-20210402-020538.png?cb=5a25ccc9661cd4eb634865c9e1e11b4f) --- language: "en" --- # Alert Notification Service ## **Overview** The SAP Alert Notification service for SAP BTP provides a central service for receiving, filtering, and delivering alerts and notifications from SAP BTP services, applications, and custom event providers. It can be used to monitor availability, performance, errors, and operational events across SAP BTP environments and route those notifications to external systems. The PowerConnect Cloud agent collects alert notification events from the SAP Alert Notification service and sends them to the target platform for monitoring, reporting, and alerting. ## **Data Collected** Alert severity Alert category Alert subject and body Alert source Resource and service information Event timestamps Event tags and properties Alert status and metadata ## **APIs Used** SAP Alert Notification service REST APIs Credential management / OAuth client credentials for API access ## **Status** Generally Available ## **Configuration** ### **Get API User Details** PowerConnect Cloud requires access to the SAP Alert Notification service API to extract alert notification data. The most secure way to do this is to create or use a service binding / service key for the SAP Alert Notification service instance in your SAP BTP tenancy. This provides OAuth client credentials that PowerConnect Cloud can use to authenticate against the service API. To do this, follow the steps below for your environment: 1. Login to the SAP BTP Cockpit. 2. Navigate to your subaccount. 3. Under **Services → Instances and Subscriptions** , find your **Alert Notification** service instance. 4. Open the service instance and create or view the service binding / service key credentials. 5. Note down the following values: * `url` * `clientid` * `clientsecret` * `identityzone` * `uaadomain` Depending on the SAP BTP cockpit version and service plan, these values may be shown under the service key, service binding, or credentials section. ## **Adding the Alert Notification Input to PowerConnect Cloud** 1. Login to the PowerConnect Cloud web UI. 2. Click on the **Inputs** link in the menu bar. 3. Click the **+** button to add a new Input. 4. Choose **alerts-cf** under **BTP Platform**. 5. Fill in the details on the form using the API authentication values from the step above. 6. Fill in the **System ID**. The System ID maps to the `source` field in Splunk/Dynatrace and is used by dashboards to group related events. 7. Choose the Splunk output you wish to send the Alert Notification data to. 8. Click **Save**. The Input is now created. ## **Configuration Options** | **Configuration** | **Description** | **Required** | **Default Value** | **Comments** | |------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|------------------------|---------------------------------------------------------------------------------| | How frequently to poll for new data in seconds | How often the input will check for new alert notification data | True | 60 seconds | | | Unique Identifier for the Input | A unique ID for the input | True | Spaces are not allowed | | | Friendly name for the Input | Friendly name for the input | True | | | | System ID | System ID or SID of the system. The value of this field will be mapped to the source field in Splunk and is used in dashboards for grouping related system events | True | | | | Lag in Seconds | How far behind the input will lag in seconds | True | 60 | This setting is to deal with SAP APIs that sometimes lag behind under high load | | Enable Data Collection | Enable / Disable the Input | True | True | | | SAP BTP platform host | SAP BTP platform host | True | | | | Identity zone | Identity zone | True | | | | Client Id | Client Id of the Alert Notification service API user | True | | | | Client Secret | Client Secret/password of the Alert Notification service API user | True | | | | Page Size | Number of records to return in a single API call | False | 100 | | | Filter by severity | | False | | | | Filter by category | | False | | | | Filter by event type | | False | | | | Filter by resource name | | False | | | --- language: "en" --- # ALV_REPORTS - ALV Reports data ## Data Description The ALV_REPORTS event is used to extract data of any SAP Standard/custom transaction/program displaying the data in ALV Report Format. This is a generic event that extracts data from any Report Transaction based on the configuration. ## Potential Use Cases This event could be used in the following scenarios: * To view \& analyze data of any SAP Report Transaction/Program displaying the data in ALV Reports format. * To view \& data of any Custom Report Transaction/Program displaying the data in ALV Reports format. ## Metric Filters To extract data from a report Transaction/Report, a user must configure the Transaction name and/or Report Name along with Report selection variant information. Only the active configurations are considered. The following steps need to be performed to set up the Filter configuration: * Open ALV_REPORTS filter using menu option below (Administrator-\>Metric filters-\>More-\>ALV Reports Filter) ![image-20230202-085126.png](https://docs.rhondos.com/__attachments/a_3a1d73c45125123c3d3cd0ea3471da8da9976277e7bf5c835acda54b3fcbef6b/image-20230202-085126.png?cb=d1d2687f3bef5f608e9b1de08bb92a9c) * Maintain the Transaction, Report Name along with Variant Name. The interval represents the extraction frequency in seconds for each record. As an example data from MB59 should be extracted every hour ( as the interval value is 3600 Sec). The configuration can be activated and deactivated using the checkbox. ![image-20230202-085252.png](https://docs.rhondos.com/__attachments/a_b9d7f18ab3cd77d989e5a6c01f0b9b916c802c8364ea95f1df47305546510cf5/image-20230202-085252.png?cb=068d72ce2d033c394edefba954293e40) ## SAP Navigation In SAP, Execute the the transaction with corresponding variants that you want to maintain in Filter Configuration to extract the data. For example, below is the output of transaction MB59 executed with the selection variant that is also used in the Filter configuration. This data will be extracted and send to the Splunk system ![image-20230202-090126.png](https://docs.rhondos.com/__attachments/a_f9229446cb0d9049c94c814980a00393b792ec23b96911af5af36787ef518706/image-20230202-090126.png?cb=3a15cece7a22472f3399b7f8608f9b0c) --- language: "en" --- # App Setup Page The setup page is used to configure the SAP PowerConnect App for Splunk. This is performed immediately after app installation. Navigate to Apps \> Manage Apps. Alternatively, find the gear icon in the Apps menu. ![image-20220404-215235.png](https://docs.rhondos.com/__attachments/a_e753aca599959438d206936a01923961508e7b646556b8142ea9b744a86848db/image-20220404-215235.png?cb=39698084135fa179dbd975d20e96c459) In the app listing, find the "SAP PowerConnect for Splunk" app and click the "Set UP" action. ![image-20220404-215350.png](https://docs.rhondos.com/__attachments/a_f188b6c2850d92be08d5b90cd81e2a2eba8eb420a07066037a52f311ab410c2f/image-20220404-215350.png?cb=c3b3f1b005755f7012b0dd84f11c115c) Please see the version-specific setup page guide below. Pre-v8.5.0 ![image-20241218-144919.png](https://docs.rhondos.com/__attachments/a_62595de2677ec803e4b3af655398094b1149944b3672bcbe54fcc484f00a17e9/image-20241218-144919.png?cb=d881d0ea879f918015b7942e3e4755db) Determine which of the options below should be selected: * Defaults Selection: Sets the following default options... * Default TimeRange: Select the time range that is used as the default for most dashboards in the app. * Default Span: Select the time span that is used as the default for span inputs across the app. * SAP Data Indexes: Indicate which indexes are used for SAP data. This populates one of the macros used for searches across the app. * SAP Metric Indexes: Indicate which indexes are used for SAP metrics. This populates another macro used for searches across the app. This feature is currently in limited implementation. * SAP Product Selection * Database Selection: Allows you to check the database types used by your SAP implementation. This will ensure that only the required database dashboards are visible in the app. * SAP Cloud Selection: Allows you to check the SAP Cloud products used by your SAP implementation. This will ensure that only the required SAP Cloud dashboards are visible in the app. * SAP Fiori Selection: Allows you to indicate whether your SAP implementation includes SAP Fiori. This will ensure that the SAP Fiori dashboards are visible in the app. * Application Setup Status: Please ensure this is checked in order to record the configuration status of the app. After configuration, click "Save" to apply the changes and the page will redirect to the next view where you can populate system lookups. v8.5.0+ ## Welcome ![image-20250630-190542.png](https://docs.rhondos.com/__attachments/a_8c689ffa61720fbed4a1ca7ea21dd8cf3cc812dc0047e919cee7241c5d4b18cb/image-20250630-190542.png?cb=ea766fba3c68aa9d69601375fe0cca62) The Welcome page introduces the setup process and performs preliminary checks to ensure that the current user has the capabilities necessary to run setup. If the conditions are met, the Next button will appear. ### Configure Data Ingest ![image-20250630-190525.png](https://docs.rhondos.com/__attachments/a_ce9c364abd1885ba7b901add125f018f83bbc9eafef6a41870775ec4684b0872/image-20250630-190525.png?cb=9847fa7c05f3f40f7b3a36e4ce120e59) As part of the Splunk app setup, users will need to create HTTP Endpoint Collectors and Indexes for SAP data. The Next button will appear when the user indicates that these requirements are met by checking the box. ### Select Indexes ![image-20250630-190425.png](https://docs.rhondos.com/__attachments/a_8b1302086ba10a553734c8804e416eee48451ee5f5648edbcf78930451f005c5/image-20250630-190425.png?cb=08c4543ae9c771e83719dcf7fa0c28a1) This page configures the base search macros for event and metric SAP data indexes. The user selects indexes from available lists. With each input, the following controls are present: * Scan for Data: Scan available indexes for existing SAP data. This is useful if your Splunk instance is already ingesting data from SAP systems. * Reset Selection: Removes current selections. ### Select SAP Products ![image-20250630-190333.png](https://docs.rhondos.com/__attachments/a_e6ca061839bfc18560115e2ad74550dfe9a0098e8690b8ffb1c79da058940817/image-20250630-190333.png?cb=bf9c9a62ceb0d53db274ce27f485e1ab) Configure the SAP products monitored by PowerConnect on this page. these selections will control what dashboards are visible in the navigation menu, including: * Database types * SAP Cloud Products * Other SAP Products ### Set Dashboard Defaults ![image-20250630-190227.png](https://docs.rhondos.com/__attachments/a_35575636927be517bf6c80617c5db90f631656f2f5f74aa8e44aa78dc0c17f04/image-20250630-190227.png?cb=9bdb91ad855a2e9493c00127992b3d4a) Set the default time range for Splunk dashboards as well as the default span for time-based charting in applicable Splunk dashboards. ### Confirm Setup ![image-20250630-190201.png](https://docs.rhondos.com/__attachments/a_ff63152979eaba615366d6bbd5a94883bedabadcabd817d4723092dc1d28efcd/image-20250630-190201.png?cb=f7acd94d5a35dba0300de23eb0de590e) Review the setup options before clicking "Finish" to save the app configuration. If the application saves successfully, you will be redirected to the next page for populating lookups used in the PowerConnect Splunk app. --- language: "en" --- # Apply PowerConnect License (PowerConnect Java) ## Adding License Key (PowerConnect Java 6.X) After the PowerConnect agent has the correct credentials and has been restarted a license must be installed. Obtain your license from your reseller and use the below steps to install the license. Open a browser and navigate to the PowerConnect admin page [http://\:\/webdynpro/resources/com.powerconnect5/spcj_wd/SapPowerConnectJava#](http://172.16.3.18:50000/webdynpro/resources/com.powerconnect5/spcj_wd/SapPowerConnectJava) ![image-20210219-062927.png](https://docs.rhondos.com/__attachments/a_6ce6968b7f3a080f10968bf392b3c0afb5831de87e960437e601ffe74b254f18/image-20210219-062927.png?cb=058196137a3ce04ae682f91b27f8fc48) Enter the license key in to the **License Key** field, and click **SAVE** ![image-20201006-064007.png](https://docs.rhondos.com/__attachments/a_f71346d4fde463540d57e3fd5b9b9bfd4eae7430bb3fb868289491fe44d123f2/image-20201006-064007.png?cb=ad1c688625daea3a0feec89e648b1d7c) If the license key validates then a message will be displayed confirming the license key is valid. If you receive an error that your license key is not vaild, then restart the agent using the steps below **Starting / Stopping Agent** and re-enter your license. If you continue to receive a message that your license key is not valid then collect the agent logs using the instructions in section **Troubleshooting → Collecting Logs** and send them to your reseller. After you install the new license restart the agent using [**Starting / Stopping Agent**](https://docs.rhondos.com/powerconnect-for-sap-solutions/start-stop-powerconnect-java-agent.md). ## Adding License Key (PowerConnect Java 7/8.X) After the PowerConnect agent has the correct credentials and has been restarted a license must be installed. Obtain your license from your reseller and use the below steps to install the license. Open a browser and navigate to the PowerConnect Administration → License page [http://\:\/](http://172.16.3.18:50000/webdynpro/resources/com.powerconnect5/spcj_wd/SapPowerConnectJava)powerconnect-java/index.html ![image-20240228-021256.png](https://docs.rhondos.com/__attachments/a_3aa49441edfab2605a710199b13e53d7daa4d5178c2ceb26c6150cd5ba09d340/image-20240228-021256.png?cb=3fd8bd41469c3a6b2e81b2f910094a17) Enter the license key in to the **License Key** field, and click **Save** The license details should be updated with the key information including the validity ![image-20240228-021510.png](https://docs.rhondos.com/__attachments/a_eeba7ef4d756fd6ca553c6e2b014fc627efff87a16d7d95ae3bff4aa9b3c9943/image-20240228-021510.png?cb=74220670d77cf04a1d595bb50fccc362) If you receive an error that your license key is not vaild, then restart the agent using the steps below **Starting / Stopping Agent** and re-enter your license. If you continue to receive a message that your license key is not valid then collect the agent logs using the instructions in section **Troubleshooting → Collecting Logs** and send them to your reseller. After you install the new license restart the agent using [**Starting / Stopping Agent**](https://docs.rhondos.com/powerconnect-for-sap-solutions/start-stop-powerconnect-java-agent.md). --- language: "en" --- # (Archived)PowerConnect SP 7.XX Release notes (ABAP) --- language: "en" --- # ASE_DBCC_DMPHIS ## Data Description The ASE_DBCC_DMPHIS event can be used to monitor SyBase database backup status, making it easy to confirm runs and catch failures. ## Potential Use Cases This event could be used in the following scenarios: * Alerting on failed or missing backups * Correlating long backup windows with heavy system load or storage issues * Supplying audit evidence of retention, location and compliance ## SAP Navigation Log into the managed SAP system and execute the transaction DBACOCKPIT. ![Pasted Graphic 3-20250618-055738.png](https://docs.rhondos.com/__attachments/a_456754920aa1623f7ec907725d30f856b37437ecd86d45f48d7d69e3317b03ed/Pasted%20Graphic%203-20250618-055738.png?cb=ffec2125014bc270f73ffbc8ca5e0efb) --- language: "en" --- # Assign PowerConnect Roles to Users (PowerConnect ABAP 8.X) After importing the PowerConnect roles into the system, the roles need to be assigned to different user accounts. There are two different kinds of users that will need to access the PowerConnect application: * Batch User - this user account will be used to execute the batch jobs that collect the data in the SAP environment and send the data. * Administrative User - this user account will be used to make configuration changes in the PowerConnect administrative console, which is accessed using the /n/bnwvs/main transaction. The roles that should be assigned to each type of user, are displayed in the table below: | **User** | **Role(s)** | **Role Description** | |---------------------|-----------------------|---------------------------------------------------------------------------------------------------| | Batch User | Z_BNWVS_BATCHUSER | Provides the user with the ability to execute the PowerConnect batch jobs. | | Administrative User | Z_BNWVS_ADMIN_DISPLAY | Only provides access to display configuration, but job control is not available. | | Administrative User | Z_BNWVS_ADMIN_CHANGE | Provides access to start/stop PowerConnect jobs and provides the ability to change configuration. | | Administrative User | Z_BNWVS_ADMIN_CONTROL | Can be used only to start/stop PowerConnect jobs, and includes configuration read access. | To assign the roles to each respective user, execute the SU01 transaction. Then enter the user ID, and select the change button. ![image-20210526-155509.png](https://docs.rhondos.com/__attachments/a_da9dca24e7efc8b7fddbecad80db34033fbe9cf221839bdbdc9e182f3d00ea0e/image-20210526-155509.png?cb=490189fec5630eaf24f75c4d7a87707f) Then click on Roles ![image-20210526-155543.png](https://docs.rhondos.com/__attachments/a_5e45a722ccac6eaf15a507bb1f1ec2664940d94ed487095d6d165d4796144a47/image-20210526-155543.png?cb=ad9785579c47d826f937638b19e813dc) Then add the roles according to the table above with the Start and End dates for when the roles will be assigned to the user and Save. ![image-20210526-160022.png](https://docs.rhondos.com/__attachments/a_b125f2dce05a95e98cc6c7059255ee31de2e7d467b474ef5534d51b356dbdfe5/image-20210526-160022.png?cb=6652a93a0c0d7d7de66b0ed13d25c232) You now can start the PowerConnect application by calling the transaction /n/BNWVS/MAIN. Doing so, first and mandatory step is to [configure the PowerConnect license](https://docs.rhondos.com/powerconnect-for-sap-solutions/configure-powerconnect-license-powerconnect-abap-7.md). --- language: "en" --- # Assign PowerConnect Roles to Users (PowerConnect ABAP 9.X) After importing the PowerConnect roles into the system, the roles need to be assigned to different user accounts. There are two different kinds of users that will need to access the PowerConnect application: * Batch User - this user account will be used to execute the batch jobs that collect the data in the SAP environment and send the data. * Administrative User - this user account will be used to make configuration changes in the PowerConnect administrative console, which is accessed using the /n/bnwvs/main transaction. The roles that should be assigned to each type of user, are displayed in the table below: | **User** | **Role(s)** | **Role Description** | |---------------------|-----------------------|---------------------------------------------------------------------------------------------------| | Batch User | Z_BNWVS_BATCHUSER | Provides the user with the ability to execute the PowerConnect batch jobs. | | Administrative User | Z_BNWVS_ADMIN_DISPLAY | Only provides access to display configuration, but job control is not available. | | Administrative User | Z_BNWVS_ADMIN_CHANGE | Provides access to start/stop PowerConnect jobs and provides the ability to change configuration. | | Administrative User | Z_BNWVS_ADMIN_CONTROL | Can be used only to start/stop PowerConnect jobs, and includes configuration read access. | To assign the roles to each respective user, execute the SU01 transaction. Then enter the user ID, and select the change button. ![image-20210526-155509.png](https://docs.rhondos.com/__attachments/a_6e84195afbb4b5773febfba3bc685d096e169c37c20c82408588941e0c05447e/image-20210526-155509.png?cb=490189fec5630eaf24f75c4d7a87707f) Then click on Roles ![image-20210526-155543.png](https://docs.rhondos.com/__attachments/a_fe25f18e6ab68575eb334f117c71acf208cd87cae2b1b23e503fe22ee51fc549/image-20210526-155543.png?cb=ad9785579c47d826f937638b19e813dc) Then add the roles according to the table above with the Start and End dates for when the roles will be assigned to the user and Save. ![image-20210526-160022.png](https://docs.rhondos.com/__attachments/a_41c3e9d8793996f60537032682f0cbcf86653beff1c1c0a0632f51bae36e59b8/image-20210526-160022.png?cb=6652a93a0c0d7d7de66b0ed13d25c232) You now can start the PowerConnect application by calling the transaction /n/BNWVS/MAIN. Doing so, first and mandatory step is to [configure the PowerConnect license](https://powerconnect.atlassian.net/wiki/x/Wge2_/). --- language: "en" --- # Assign PowerConnect Roles to Users (PowerConnect ABAP 7.X) After importing the PowerConnect roles into the system, the roles need to be assigned to different user accounts. There are two different kinds of users that will need to access the PowerConnect application: * Batch User - this user account will be used to execute the batch jobs that collect the data in the SAP environment and send the data to Splunk. * Administrative User - this user account will be used to make configuration changes in the PowerConnect administrative console, which is accessed using the /n/bnwvs/main transaction. The roles that should be assigned to each type of user, are displayed in the table below: | **User** | **Role(s)** | **Role Description** | |---------------------|-----------------------|---------------------------------------------------------------------------------------------------| | Batch User | Z_BNWVS_BATCHUSER | Provides the user with the ability to execute the PowerConnect batch jobs. | | Administrative User | Z_BNWVS_ADMIN_DISPLAY | Only provides access to display configuration, but job control is not available. | | Administrative User | Z_BNWVS_ADMIN_CHANGE | Provides access to start/stop PowerConnect jobs and provides the ability to change configuration. | | Administrative User | Z_BNWVS_ADMIN_CONTROL | Can be used only to start/stop PowerConnect jobs, and includes configuration read access. | To assign the roles to each respective user, execute the SU01 transaction. Then enter the user ID, and select the change button. ![image-20210526-155509.png](https://docs.rhondos.com/__attachments/a_e1abf75829597ac6fec1024de90c50b88b000d953a2b6eefea522134f5dded71/image-20210526-155509.png?cb=490189fec5630eaf24f75c4d7a87707f) Then click on Roles ![image-20210526-155543.png](https://docs.rhondos.com/__attachments/a_99003862b090cde496bd506953f4880a06239c1ebf09eaef7daf696870e4e459/image-20210526-155543.png?cb=ad9785579c47d826f937638b19e813dc) Then add the roles according to the table above with the Start and End dates for when the roles will be assigned to the user and Save. ![image-20210526-160022.png](https://docs.rhondos.com/__attachments/a_899742e922f75ae6ef6d7dd17b19fe61d5d8f8e648bfc1a4a614ef1585a86d21/image-20210526-160022.png?cb=6652a93a0c0d7d7de66b0ed13d25c232) You now can start the PowerConnect application by calling the transaction /n/BNWVS/MAIN. Doing so, first and mandatory step is to [configure the PowerConnect license](https://docs.rhondos.com/powerconnect-for-sap-solutions/configure-powerconnect-license-powerconnect-abap-7.md). --- language: "en" --- # ATC - ABAP Test Cockpit Results ## Data Description The ATC event (corresponding to SAP transaction 'ATC-\>(Manage) Results' functionality in SAP Business Suite systems) is used to obtain ATC check results. ## Potential Use Cases This event could be used in the following scenarios: * To display and analyze ATC findings and Identify the precise location of errors in source code * Determine ATC errors/findings trend over time * These help to improve code quality and develop security risk-free code ## Splunk Event ### **ATC with EVENT_SUBTYPE=" "** This event subtype contains the ATC run details. ![image-20221027-090713.png](https://docs.rhondos.com/__attachments/a_30218be7ac54cca37d751fa5538342f075db3602f7a2ee875bb40f0d335226a6/image-20221027-090713.png?cb=79d631b194c4cce381bc9095cde00bf8) The corresponding information on the SAP system can be found on the 'Manage Result' screen of the ATC transaction. ![image-20221027-091019.png](https://docs.rhondos.com/__attachments/a_8f9f180f3cc816c4d3928ed2e082dd0c7c6f4fb0787f40e2f9f44de19aad2d2d/image-20221027-091019.png?cb=64dae45a894696fff0a359e575e9216a) ### **ATC with EVENT_SUBTYPE= "CONTENTS"** This event subtype contains the details high-level details about the technical object having the error as well as the priority of the finding. ![image-20221027-091302.png](https://docs.rhondos.com/__attachments/a_5e46fb227129c6892a371fa118fd18f63180f8af0cf82fa8820003aa76064f82/image-20221027-091302.png?cb=81c36109541a9859c5a3eec2aa1863c9) ### **ATC with EVENT_SUBTYPE="CONTENTS_DETAIL"** This event subtype contains the exact code line number having the error. ![image-20221027-092222.png](https://docs.rhondos.com/__attachments/a_9058fbbcf5e90be76fb1ce14a4f137490750ac6cc471e16e896e49e29dcd42ed/image-20221027-092222.png?cb=bd8b5e5cabf97655ad59c3c7087b38c7) ### **ATC with EVENT_SUBTYPE="CONTENTS_TEXT"** This event subtype contains the description of the error and other related helpful information ![image-20221027-092551.png](https://docs.rhondos.com/__attachments/a_6c16fa065785f3a480f1e2d3fd8d07afc3980d2140f6f6e64a594492e1f30dd9/image-20221027-092551.png?cb=593789e2bafc09d86e2bc911a40227fb) ## SAP Navigation Log in to the SAP system and execute the ATC transaction code. Click on Manage Results to check the ATC results. ![image-20221027-092632.png](https://docs.rhondos.com/__attachments/a_d15cabf5b8657ca008effa333fb9ce139c5136e4731edda679c6e8379f8b83bd/image-20221027-092632.png?cb=1b4db676987fc2dac04d33e4887a7be5) ![image-20221027-091019.png](https://docs.rhondos.com/__attachments/a_8f9f180f3cc816c4d3928ed2e082dd0c7c6f4fb0787f40e2f9f44de19aad2d2d/image-20221027-091019.png?cb=64dae45a894696fff0a359e575e9216a) --- language: "en" --- # BD87_DYN ## Data Description The BD87_DYN event is used in SAP to view iDoc details including statuses, segments, and the data stored within the EDI container. ## Potential Use Cases This event could be used for the following scenarios: * Alert on iDoc failures. * Dashboard iDoc error distribution for a specific interface. * Correlate outbound iDoc data with tRFC failures. * End-to-end monitoring or dashboarding use cases when trying to track business process flows and failures across systems. ## Metric Filters **Important Note:**The metric filters need to be applied to extract data for the BD87_DYN event. To access the metric filters for the BD87_DYN event, execute the /n/bnwvs/main transaction in the managed system. Then go to Administrator → Metric Filters → IDOC Segment filter. ![image-20210329-170457.png](https://docs.rhondos.com/__attachments/a_b301d8f6a66eb9df1baa1c119fa3748863ac7a145c1c0682954019ce64bafdb2/image-20210329-170457.png?cb=ce5d89fa57df4b9a17764b1109e20f46) **Note: From PowerConnect 9.01 onwards, the Filter link is: /n/BNWVS/MAIN**→Administrator → Metric Filters → Interfaces→ BD87 IDOC Seg filter. ![image-20260401-071104.png](https://docs.rhondos.com/__attachments/a_1f1e0fb6b5a9ac62c61cc9635ac20f06c178d3e6787620b564bfb1555d6b8d03/image-20260401-071104.png?cb=d62c91ef7e6e8e9f4b9e69909b242b26) Then you will be brought to a page where the iDoc parameters can be input. Select the New Entries option. ![image-20210329-170638.png](https://docs.rhondos.com/__attachments/a_99cda4d295b411109ac98e21b7315add831e451820f613ef729b7566f07f6058/image-20210329-170638.png?cb=f69af5c4fbe572f9c7f4fb2cfadf00ba) Then input the desired values into the selection criteria fields. Here are the definitions for each of the fields, and how they can be leveraged: * Message Type - This field is mandatory, and is based on the Message Type associated with the iDoc desired for data extraction. * Basic Type - This field is mandatory, and is based on the Basic Type associated with the iDoc desired for data extraction. * Direction - This field is optional, but can be used to filter on inbound or outbound transactions. To filter on inbound transactions enter "Inbound", and to filter on outbound transactions enter "Outbound". If you would like to select all transactions regardless of direction, leave the field value empty. * RcvPartn.no. - This field is optional, but can be used to filter on a particular receiving partner number associated with an iDoc. If you could like to select all transactions regardless of the partner, leave the field value empty. * RcvPort - This field is optional, but can be used to filter on a particular receiving port associated with an iDoc. If you would like to select all transactions regardless of the port, leave the field value empty. * SndPartn.no. - This field is optional, but can be used to filter on a particular sending partner number associated with an iDoc. If you could like to select all transactions regardless of the partner, leave the field value empty. * SndPort - This field is optional, but can be used to filter on a particular receiving port associated with an iDoc. If you would like to select all transactions regardless of the port, leave the field value empty. * Active - This checkbox can be used to enable and disable the data extraction. To enable the data extraction ensure that the checkbox is selected. **Extract iDocs Accross Clients** If you would like to extract iDocs from multiple clients, select the row that you would like to extract the data from, and then double-click the IDOC Clients section on the left side of the screen. ![image-20210329-220115.png](https://docs.rhondos.com/__attachments/a_a9f76073c3a9022796fd5764dfc0191f626b7034c64e32e6b56247fd3b9b1c38/image-20210329-220115.png?cb=ba1bd9dd68321f604a7fa0186a601946) You will then be brought to a page where you can input the Clients from which you would like to extract the iDocs. Select the New Values button. ![image-20210329-220234.png](https://docs.rhondos.com/__attachments/a_6da1e392626925d9e9241a873e35d3e9683f98f4774b6d34e3fa1ea408ae007b/image-20210329-220234.png?cb=887cce83760553e959dadc7b568b51ab) Enter the Client(s) that you would like to extract the data from, and Save. ![image-20210329-220418.png](https://docs.rhondos.com/__attachments/a_4470970be6e852226dd09c140164b4528a35916c77fa208cbe6f8ea64347ca02/image-20210329-220418.png?cb=7716e14f58d08f3de2aeeb703b5fa96f) **Extract iDoc Segments** Once the values have been input as specified above, Save. Then select the row that you would like to extract the segment values for and and then double-click the IDOC Segments section on the left side of the screen. ![image-20210329-210651.png](https://docs.rhondos.com/__attachments/a_803e6339faeae22377d0c8e556eda70bba5424c17a392c660eefa4f71ece4928/image-20210329-210651.png?cb=c00b8a2b54cc076e76085acfdfed19cb) You will then be brought to a page where you can input which iDoc segment associated with the field values you would like to extract. Select the "New Entries" button. ![image-20210329-212116.png](https://docs.rhondos.com/__attachments/a_ac5d37b2593b490ef1fbaa9490481f05a09d58ae78085dd4dfabf18e653ceea2/image-20210329-212116.png?cb=c705385039a34780a1dbaa89add704d0) Then input the desired values into the selection criteria fields. Here are the definitions for each of the fields, and how they can be leveraged: * Segment Type - This field is mandatory and is used to input the segment associated with the fields and field values you would like to extract from within the iDoc container. * Status - This field is optional and is used if you would only like to extract the fields and field values from within the iDoc on specific statuses. * Active - This checkbox can be used to enable and disable the data extraction. To enable the data extraction ensure that the checkbox is selected. Once the values have been input, hit the Save button. Then select the row that you would like to extract the fields and field values for, and then double-click on the Segments Fields section on the left side of the screen. ![image-20210329-213747.png](https://docs.rhondos.com/__attachments/a_08eab8d9c824b55381e7842da8311618d35351bc5bc3b471deef2ca72bd63b0d/image-20210329-213747.png?cb=efaf4b660fd4da712372b0254437d8a4) You will then be brought to a page where you can input which iDoc segment fields that you would like to extract. Select the "New Entries" button. ![image-20210329-215128.png](https://docs.rhondos.com/__attachments/a_6607acb3cc3bdf2dae956845c5e819783e1c7d0be30d9aabf666ebc230a9736c/image-20210329-215128.png?cb=bec86f9c1953651a7fcdfde4eefbc9f7) Then input the field names associated with the iDoc segment you previously highlighted, and Save. ![image-20210329-215537.png](https://docs.rhondos.com/__attachments/a_6627bc30c0544b8532c0c08c6992a715566b8da39d7c4e2f7f0666629313600b/image-20210329-215537.png?cb=06b54c5e4fdcf584eac2faf96e1b5c4c) ## Splunk Event **Important Note:**The metric filters need to be applied to extract data for the BD87_DYN event. Please see the Metric Filters section above for how to apply the filters. **BD87_DYN with EVENT_SUBTYPE=""** The event will look like this in Splunk: ![image-20210329-173229.png](https://docs.rhondos.com/__attachments/a_4242d0b618ee749f09c78d4fec57c133bc06b85d6a11c20ed126f0fb930888e1/image-20210329-173229.png?cb=3cdc276c21f4239f4db2309689f2293d) **BD87_DYN with EVENT_SUBTYPE="SGFV"** This event subtype is customized based on the parameters input in the metric filters. The event will look somewhat like this in Splunk: ![image-20210329-173556.png](https://docs.rhondos.com/__attachments/a_9f906161fd81add093d83f7b2936d55c0f6dd97e3654e5e2851359556233b1bb/image-20210329-173556.png?cb=e5bfe1ef5fba68f3305a22fdf9d98fc1) **BD87_DYN with EVENT_SUBTYPE="SGLG"** The event will look like this in Splunk: ![image-20210329-173644.png](https://docs.rhondos.com/__attachments/a_36bd07d31477adced4c8a05eb05ef50783c09593f3363e46ad49fb5587733718/image-20210329-173644.png?cb=bd5c61736a6209ad745db0885724bb0c) ## SAP Navigation **Important Note:**The metric filters need to be applied to extract data for the BD87_DYN event. Please see the Metric Filters section above for how to apply the filters. Navigate to this data by using the WE02 t-code. The BD87 t-code can be leveraged, but the WE02 t-code provides more specific filter criteria. Enter the desired filter criteria from the entry page and select "Execute". ![image-20210329-174337.png](https://docs.rhondos.com/__attachments/a_4cc7f0b50e6add0b32266e8b60836e7a4fa46c5e6b49d81d5ae4c5b07d9b0c11/image-20210329-174337.png?cb=5cea8fd317fcb402876010b46aca8ecf) You will then be presented the list of iDocs that were specified in the filter criteria. Select one of the iDocs of interest by double-clicking the iDoc number: ![image-20210329-174827.png](https://docs.rhondos.com/__attachments/a_357bc71d4cf802be1d1ca5e927dc23f7b2e83eae30e4cd42af33f42913cc9293/image-20210329-174827.png?cb=479da58cb064d9f99b50fc3c4c785613) Each of the data types below is accessed using the entry point steps documented above. **BD87_DYN with EVENT_SUBTYPE=""** When viewing the iDoc selected from the steps above, double-click the Control Record option from the left side of the screen. ![image-20210329-193309.png](https://docs.rhondos.com/__attachments/a_f93624a6a6e5695783d1834315b2c0ac261ce9c1d587c9ed171e5f31d7f03039/image-20210329-193309.png?cb=0ea2f90f534d0d2a6068a3aecf0262d9) Each of the tabs are extracted as part of this event: **Type Information** ![image-20210329-193428.png](https://docs.rhondos.com/__attachments/a_ae00425246f846cd5a835eaa73acb78eb6b5a030d8e4f8756b1bfd6d3eb41205/image-20210329-193428.png?cb=6691217d10077a255a1adeb9b1fe4710) **Partner** ![image-20210329-193609.png](https://docs.rhondos.com/__attachments/a_dfdf50fedfa753c72ed9ae0f26bde9927666884300cf8c0835ee4f50e277d85f/image-20210329-193609.png?cb=e18f4a3b745ee492f9eb65f6e2af10e5) **Technical Information** ![image-20210329-193638.png](https://docs.rhondos.com/__attachments/a_0a0dbf62b0bea9fd66d3d13c1cb567fcfdcee72b15b2d6522a9aff59eeaf7300/image-20210329-193638.png?cb=d469c093f83bd3664a290d625a74903d) **Address Information** ![image-20210329-193724.png](https://docs.rhondos.com/__attachments/a_5f6487e411f3f32ad10dcbe55fc6e102c436996608377eaeb2b6704190816b4f/image-20210329-193724.png?cb=77feb7511ec3d868c6f95caeb03ae867) **Details** ![image-20210329-193749.png](https://docs.rhondos.com/__attachments/a_16798914d3e09c10467817bc0a5af9fdf95207c26d619be0c648d06f62ce161a/image-20210329-193749.png?cb=77feb7511ec3d868c6f95caeb03ae867) **BD87_DYN with EVENT_SUBTYPE="SGFV"** When viewing the iDoc selected expand the Data Records option from the left side of the screen. ![image-20210329-194134.png](https://docs.rhondos.com/__attachments/a_1b7667f1257fcdc8d5b5e9403a0722399b9044a9edfb4e2b58b6a501699d9a5e/image-20210329-194134.png?cb=029c93a7b39116dfea7ded6e2c59ba86) The fields that are extracted as part of this event are based on the customization of the Metric Filters defined above. Please see the Metric Filters section for how to customize what data is extracted from within the iDoc. **BD87_DYN with EVENT_SUBTYPE="SGLG"** When viewing the iDoc selected expand the Status Records option from the left side of the screen. ![image-20210329-194540.png](https://docs.rhondos.com/__attachments/a_481a05cad5b13f746e95bedaee16b360f61e309918713071135bd61638e746cb/image-20210329-194540.png?cb=074b779b89d1eff1d1fafaae57401808) Then double-click the status record value of interest, and you will be brought to the next screens, which are viewable within the Splunk event. **Technical Information** ![image-20210329-194820.png](https://docs.rhondos.com/__attachments/a_147cee6b75c3fe59bde30f0a7c7d58d910cf19498f35124d65ac1b7d5dcd8c03/image-20210329-194820.png?cb=924fa7c51c5fa91336afa69eda31c448) **Status Details** ![image-20210329-194855.png](https://docs.rhondos.com/__attachments/a_485d0c223438a8084cf859457d5f42cfa84632d930f9cca9be3e9ff924a6df7f/image-20210329-194855.png?cb=71e412d795def22efdf7624c19076249) **Logging** ![image-20210329-194906.png](https://docs.rhondos.com/__attachments/a_630780a4615a9939084b3fd1f056f1f7918d8a81b01ca3688e2871395e2e7481/image-20210329-194906.png?cb=709bf89966e7e7123610dc892aab0538) --- language: "en" --- # BGRFC_MON - Background RFC Monitor ## Data Description The BGRFC_MON event is used to display the recorded units of the background RFC(bgRFC). A unit consists of one or more function modules that need to be processed as an indivisible unit. The units are stored in the database until they are processed. The event can be used to trace the state of the unit, from when it is first recorded until it has been processed. ## Potential Use Cases This event could be used in the following scenarios: * To Analyse what kind of bgRFC units exist in the SAP system, based on destinations, queue names, program names, and transaction codes * To determine the status of Inbound and Outbound bgRFC destinations * To determine the status of Inbound and Outbound bgRFC destinations queues * To determine the status of Inbound and Outbound bgRFC destinations queues * To analyze the recorded units of the background RFC(bgRFC) * Identify and alert based on the status and properties of bgRFC destinations, queues, and units as per the requirements ## Metric Configuration Out of the box, the event's/metric configuration is set to get all the bgRFCs details irrespective of the destination status. Extraction records with only Locked and/or with Errors can be activated/deactivated using the Metric Configuration. To do this, log into the managed system and execute the /n/BNWVS/MAIN transaction. Then, go to Administrator → Setup Metric → Metric Configuration. ![image-20221027-020301.png](https://docs.rhondos.com/__attachments/a_0f063d145acb1477e8831ce293f5e4a5bf2d9c0b910a47ee9f00018edec06f7d/image-20221027-020301.png?cb=5099640827e692c098a43b5eb91ceae0) To get only error records set the Parameter Key value for ALL as blank and set it as 'X' for the Parameter Key 'ERROR' in the below screen. Similarly, only LOCKED records can be extracted by disabling other Parameter Key with blank value and setting LOCKED as 'X' ![image-20230202-050439.png](https://docs.rhondos.com/__attachments/a_7dd9f29f191a0ec03af3f8214760226fb857812a2e55490cc4259e440ebaf046/image-20230202-050439.png?cb=9df736cc510533725dcf428019884fd6) ## Metric Filters Metric Filter functionality for BGRFC_MON even is added in the release 8.01 to give users the options to get/exclude data for particular destination or queue. To maintain the configuration, log into the managed system and execute the /N/BNWVS/MAIN transaction code. Then go to Administrator → Metric filters → Interfaces → BgRFC Monitor Filter. Please note that starting from release 8.03, maintaining filter records is mandatory to retrieve data. If no filter records are maintained, the functionality will not work. ![image-20240324-033912.png](https://docs.rhondos.com/__attachments/a_777f59eacacee6d0906032613faf9d70b2d7f9daff40ebdb735a67b8dd0970ba/image-20240324-033912.png?cb=788e55cddbb2a5466cc8ad9e4f3b54a1) Then fill out the configuration based on your needs, and save. Below is a summary of the fields and their associated function: * BgRFC Destination Name - This field represents the Destination name which can be inbound or outbound destinations. If you would like to extract data from all objects, place a wildcard value in this field (not recommended based on potential data volume), or specify a destination name from the SBGFRCMONG transaction that you would like to extract. * Name of BgRFC Queue - This field represents the Queue name which should be associated with the destination maintained in above column. If you would like to extract data from all objects, place a wildcard value in this field (not recommended based on potential data volume), or specify a queue name from the SBGFRCMONG transaction that you would like to extract. * INCL/EXCL - This is an include/exclude flag. Use 'I' to include the objects. If you want to exclude certain destinations and queues from being selected input an 'E' * Active - Select this box to enable the configuration. If you would like to disable the configuration uncheck the box. Here is an example of what the BgRFC metric filter looks like when it is filled out: ![image-20240324-034330.png](https://docs.rhondos.com/__attachments/a_fbd2f2470bd40012f1f8793dec362cc0b8385122ce5a18e1300eb5ee75dffb58/image-20240324-034330.png?cb=be7a6cd9598e4a40c8d408fa6ddaf872) ## SAP Navigation Log into the managed SAP system and execute the transaction SBGRFCMON to display the recorded units of the bgRFC. ![image-20230202-051256.png](https://docs.rhondos.com/__attachments/a_85ac5335a192bf4a62fbf9abc1ec6140d8f57bd4b2b13f8fe3d04e87922cb26a/image-20230202-051256.png?cb=49cda8e441181bed857b9e698f88f4f8) --- language: "en" --- # BGRFC_PERFMON - Background RFC Performance Monitor ## Data Description The BGRFC_PERFMON event is used to analyze various pieces of data about the state of bgRFC runtime. These include the total number of units, the number of units with types Q and T, the number of units with the state SYSFAIL (system error), the number of executable units with the types Q and T, and the date and time of the longest running unit. ## Potential Use Cases This event could be used in the following scenarios: * To find \& analyze longest running units of bgRFC * Identify and alert about the units with the state SYSFAIL (system error) * To find and analyze the number of units with types Q and T ## SAP Navigation Log into the managed SAP system and execute the transaction SBGRFCPERFMON to display bgRFC performance data. ![image-20230202-053634.png](https://docs.rhondos.com/__attachments/a_4e931bac999f62dd28693ff1792a49239b2a7171886a6da19c884517145fc4f7/image-20230202-053634.png?cb=a0e147fefebf89e97a44634f39ffce8b) --- language: "en" --- # BNK_MONI - Bank and Payment Monitor ## Data Description The BNK_MONI event is used in SAP to monitor the processing of Bank and Payment messages, track messages status, and errors. ## Potential Use Cases This event could be used in the following scenarios: * To monitor Bank and Payment messages for integrations/financial monitoring use cases. * Identify actionable business errors associated with bank payment using the messages, and alert respective business process teams. * Review the status of each messages/batches for the payment ## SAP Navigation Log into the managed system and execute the BNK_MONI transaction, and select the "All" tab which is the default tab as well to display all the messages. ![image-20241103-144029.png](https://docs.rhondos.com/__attachments/a_adc23fc7e8ea7fa0e66ec6bf6903c0fa082a494fb387d6317491e2de7faff513/image-20241103-144029.png?cb=9add809a0d161ec524f89caa87b38114) ![image-20241103-144047.png](https://docs.rhondos.com/__attachments/a_e3b44f730bede9798669650c0f523e7631a6b1d72cce9e894233be81d16e7deb/image-20241103-144047.png?cb=f1cb614c2f78a791ae879df7e80db5c9) --- language: "en" --- # /BNWVS/COLLECT_HIST - Utility Transaction to Collect Historical data ## Data Description The /BNWVS/COLLECT_HIST transaction serves as a valuable tool for extracting historical or backdated data related to Event Types, facilitating its transmission to the Splunk system. This functionality proves especially useful following a fresh installation in a customer's environment, especially when historical data is required. This becomes particularly relevant if certain data wasn't initially selected by PowerConnect, possibly due to errors or system shutdowns. The configuration user (with role Z_BNWVS_ADMIN_CHANGE) has authorization to the transaction. ## Potential Use Cases This transaction could be used in the following scenarios: * Recover missing data that may not have been selected by PowerConnect, especially in cases of any errors. * To recover data that was not selected during a system shutdown, ensuring data integrity. * After a new installation to retrieve historical data for Event Types in a customer environment. ## SAP Navigation Log into the managed SAP system and execute the transaction /n//BNWVS/COLLECT_HIST to collect and send Historical data for an Event Type at a time. **Input fields:** * Metric Collector: Enter Event Type Here which is mandatory * Date \& Time input fields are mandatory \& self Explanatory * Extraction Frequency in Seconds: This parameter is optional and specifically designed for the batch extraction of data. In the absence of user input, the system defaults to either the extraction frequency defined in the Group Definition or a minimum interval of 300 seconds, whichever is shorter. It's essential to note that the potential abundance of historical data poses a risk of memory overflow. The inclusion of this batch extraction parameter optimizes the data retrieval process, mitigating the risk of memory overflow errors and ensuring a smoother extraction experience. ![image-20231127-044841.png](https://docs.rhondos.com/__attachments/a_0ba7bf2c801de9cf3fef958c831faf0083ab1bc9f4fe45b3eac7556f3b564680/image-20231127-044841.png?cb=8cda1e548f1d9fa53dda58b95dd03f79) Following the execution of the historical report, the extracted data is stored in metric tables for subsequent transmission to the Splunk system. To verify the accuracy of the extracted data, one can examine both the Splunk system and the SAP system. A convenient method for cross-verification is through the Metric search report, accessible via /n/BNWVS/MAIN-\>Goto-\> Test Metrics in the SAP system. Below is the output screen after execution of the historical report. ![image-20231127-045542.png](https://docs.rhondos.com/__attachments/a_7ab4cd11e6bfd412b17f377eca82fd22d717801eccec7f426e8cb0d63eea9ec0/image-20231127-045542.png?cb=a5b03b6ee7f38a6ad34b5bc3a29485a1) --- language: "en" --- # CCMS ## Data Description The CCMS event is used in SAP to monitor, control, and configure the SAP system. CCMS stands for Computing Center Management System, and contains a series of pre-packaged metrics which can be alerted on. ## Potential Use Cases This event could be used in the following scenarios: * Chart environment availability over time. * Alert on specific CCMS alert metric values. ## Splunk Event The event will look like this in Splunk: ![image-20220804-194908.png](https://docs.rhondos.com/__attachments/a_a5f38612b8221375ede25f57df093ebda566d95c36f334458cbc3a9e44740f08/image-20220804-194908.png?cb=4ef86b96777663ebdde82e83eda0c361) ## SAP Navigation Execute the RZ20 transaction in the SAP system, and double-click on the node of interest: ![image-20220804-195013.png](https://docs.rhondos.com/__attachments/a_8cfdb460a4095a1df4160f33b390249412667b03fd5e6fa2b2f91e161ad9a4c6/image-20220804-195013.png?cb=c991b69e077a4686d02e9c020104491c) Expand the folder path of interest. The metric and value displayed will match the data that is extracted and sent to Splunk. ![image-20220804-195122.png](https://docs.rhondos.com/__attachments/a_ffa36a9f544dfb12f2bed76d58c1d951a00735d1e595cc703ffe8458002b86bf/image-20220804-195122.png?cb=46e0142058a1a7f2d73b7a2793547b52) --- language: "en" --- # CDPOS ## Data Description The CDPOS event is used in SAP to view the change documents associated with changes to a business object in the SAP system. ## Potential Use Cases This event could be used in the following scenarios: * Identify and alert on changes, which could create compliance concerns * Dashboard and alert on total change volume for specific critical tables. ## Metric Filters **Important Note:**Data will not be extracted until the Metric Filter is configured. Log into the managed system, and execute the /n/bnwvs/main transaction. Then go to Administrator → Metric filters → Change doc. filter. ![image-20210503-175700.png](https://docs.rhondos.com/__attachments/a_a2a7249164075b4688e2356eb24878f33c64d30fd8f141bd00bb6949e859e17c/image-20210503-175700.png?cb=ed8cb17b0be35a1d8294218f612cde4e) Click on the New Entries button to add additional values. Define the filter header records by indicating Change document object, Transaction code, Description (wildcards are supported). Selection type should be "CDPOS table". Save. ![image-20210512-225052.png](https://docs.rhondos.com/__attachments/a_73980f7c0d4f2bc68df3cb81c0649482f32ef95267d78c854b6e6500f540bee4/image-20210512-225052.png?cb=ee7c169d2c9a0216490a97da0a53abde) **Note:**In version 7.03, a new configuration checkbox field 'Only Header' is added to select only Header log data from CDHDR table. ![image-20230626-071846.png](https://docs.rhondos.com/__attachments/a_351833aeabbdc9ec7d59f8d13fb42176526856459eff0e7863a3e4f547b6a431/image-20230626-071846.png?cb=e89ed26ca01d0e0ae5fcfad164f4556e) If the 'Only Header' option is chosen, no need to set configuration mentioned in the following steps: Then define the list of tables to select changes from by selecting filter header record and double-click on 'Tables to select from' node on the left panel. ![image-20210512-225230.png](https://docs.rhondos.com/__attachments/a_563fa3fba2958a92aac7f0144f925613da5d5dfaa571b28831359486ad0f29ac/image-20210512-225230.png?cb=c34c2e1294aa2facd37d441b18a6753e) Key field name and 'Is master' fields should be empty/ignored. Active flag should be set, otherwise table will be ignored at run time. ![image-20210512-225313.png](https://docs.rhondos.com/__attachments/a_69e0c50795b4082d3d116d317425e0ce8063cf8d47f724ed983e3aa7af2be746/image-20210512-225313.png?cb=6edcda19c58b26e567d390be12e82f6b) For each table it is possible to define list of fields to be extracted (wildcards are supported). Add the desired entries by selecting the New Entries button, and enter the desired parameters. Highlight the table of interest and double-click on the "Field values to get" option. ![image-20210512-225516.png](https://docs.rhondos.com/__attachments/a_94ffa9130ab751f51d8dd74f08a46674d10329586ce33e5c0b4b9766fac6f414/image-20210512-225516.png?cb=28edee80a9e5883be6b256a1499132bd) Click the New Entries button and add new field values. ![image-20210512-225601.png](https://docs.rhondos.com/__attachments/a_497d2b02f98c941c9c815a402e3b546718b333df78acc2deba186161c70e1c20/image-20210512-225601.png?cb=3e3e8e7d85158a76f9096d7301e328e1) Save all settings. ![image-20210512-225736.png](https://docs.rhondos.com/__attachments/a_f6fef699e5c0ddde912b902290f6975d9e0bfe6ba6280da96b114ef74a7e39fa/image-20210512-225736.png?cb=d32f12d213e6a0c5412a43bb73f5ce12) ## Splunk Event ### **CDPOS with EVENT_SUBTYPE=""** **Important Note:**Data will not be extracted until the Metric Filter is configured. The event will look like this in Splunk: ![image-20210503-174415.png](https://docs.rhondos.com/__attachments/a_6eaa821dede39363a9c6fe5d7dab770cefb2b959e3b93614423685266b3cf619/image-20210503-174415.png?cb=2615f7d6935ed46e302dade2f6171f12) ### **CDPOS with EVENT_SUBTYPE="CDPOS"** **Important Note:**Data will not be extracted until the Metric Filter is configured. The event will look like this in Splunk: ![image-20210503-174348.png](https://docs.rhondos.com/__attachments/a_37a8233aeff4c07598c343dd2fe00a194569181688e83220d84e2d46ea1f515a/image-20210503-174348.png?cb=32cfbbfa0f169b981b2c281acbfc8729) ## SAP Navigation ### **CDPOS with EVENT_SUBTYPE=""** **Important Note:**Data will not be extracted until the Metric Filter is configured. Log into the managed system, and execute the SE16 transaction code. Then enter CDPOS in the Table Name field, and hit the Enter key. ![image-20210503-181637.png](https://docs.rhondos.com/__attachments/a_74e84cb61dc743223bbaa1732e8ce701a4959618c87615d677d2d2786dd5c403/image-20210503-181637.png?cb=bf07e389dada1129ca7d2557f4fb261f) Then enter the desired user selection parameters, and hit the Execute button. ![image-20210503-181658.png](https://docs.rhondos.com/__attachments/a_057f098af15567a01d04c1fb37cb1e47dc8524ab15e464fe2d71a303eca5fa02/image-20210503-181658.png?cb=a5cef220634bc2e53325264f86d85fe4) The information displayed will match the data that is extracted and sent to Splunk. ![image-20210503-181733.png](https://docs.rhondos.com/__attachments/a_ccdcefecdd9c596c56be8bcf2fc3a7fe47e959a4cc2d727d52a8a4417581761e/image-20210503-181733.png?cb=1a0aa5c9a599d26ae1837a3f785e2a0a) ### **CDPOS with EVENT_SUBTYPE="CDPOS"** **Important Note:**Data will not be extracted until the Metric Filter is configured. Log into the managed system, and execute the SE16 transaction code. Then enter CDPOS in the Table Name field, and hit the Enter key. ![image-20210503-175143.png](https://docs.rhondos.com/__attachments/a_308945c2af211fe4510970854f7c399f9705007cc25fa06ffc9a1891711d34b2/image-20210503-175143.png?cb=6d70efb82983a72b2f17d5699793cc5f) Then enter the desired user selection parameters, and hit the Execute button. ![image-20210503-175359.png](https://docs.rhondos.com/__attachments/a_3103e2350669a4b2cba958f0d8cd381b1a27c65510ab0515c812e7f5b0aaf278/image-20210503-175359.png?cb=c6cca687cf5ba95c37003b71ab6a5596) The information displayed will match the data that is extracted and sent to Splunk. ![image-20210503-175518.png](https://docs.rhondos.com/__attachments/a_6c44858c39bf265cf943481b159439ccca1bcc22998c96820a6d0a825a90d141/image-20210503-175518.png?cb=40095ba415687c370bdfe39ccf4f93fd) --- language: "en" --- # Certificates ## Data Description The PowerConnect Java agent is able to extract certificate metadata from the SAP system. This data can be leveraged for SAP certificate monitoring use cases. ## Potential Use Cases This event could be used in the following scenarios: * Alert on expiry of certificates * Visualize all certificate information including root CA * Alert when a new certificate is added to the SAP system ## PowerConnect Administrative Console Configuration **Important:**None of the configurations below requires a restart of the PowerConnect agent. * Login to the PowerConnect administrative console via the following URL ([http://\:\](http://172.16.3.18:50000/webdynpro/resources/com.powerconnect5/spcj_wd/SapPowerConnectJava)/powerconnect-java/index.html). * Then click on the Overview tab on the left. The screen will look like the screenshot below. Ensure that Certificates is checked and click Save. ![image-20240315-212253.png](https://docs.rhondos.com/__attachments/a_8e05e9115cec9bd84806b0f9e9fbcf748c8c603f49facaf899fee9b1d7378dbb/image-20240315-212253.png?cb=55c3441ab7304f53b506298a2932727e) ## Certificate Permissions Configuration By default the powerconnect user will only have permissions to monitor the TrustedCAs keystore certificates. To add other keystores do the following: * Login to the NWA UME Console via the following URL ([http://\:\/useradmin](http://172.2.0.38:50000/useradmin) * Search for the powerconnect role you created when installing the agent (usually called powerconnect or JMXManageAll) ![image-20240315-212908.png](https://docs.rhondos.com/__attachments/a_efd1a71d5ad4a6f1e9faa20e99623d835fb5b6c2b2eb37a3eab52c90f7134d73/image-20240315-212908.png?cb=96abdcf468f5b1dc9f1055493867d1aa) * Click the Assigned Actions Tab then click Modify ![image-20240315-213134.png](https://docs.rhondos.com/__attachments/a_1744b00f6129c3ee96cd2f0047a3faa1d9558b2842b9198d6469682afd26e081/image-20240315-213134.png?cb=8a337b0dd93d891599fb64afd6aa1f53) * Search for each Keystore you would like to monitor, the actions permission format is keystore-view.\ for example: **keystore-view.WebServiceSecurity** ![image-20240315-213350.png](https://docs.rhondos.com/__attachments/a_351ce5d3aff07789fa8e3cb4f37bb5fc083c4bbdaf4bfca799f4dde10dfddaf3/image-20240315-213350.png?cb=967480017026af7328341f8d1489c64e) * Select the resulting actions and click Add ![image-20240315-213602.png](https://docs.rhondos.com/__attachments/a_48018da3bd465bd8b5991e747b4b550d860245db183a625711adcc0e94559130/image-20240315-213602.png?cb=59e30c142de9c55677213ccbf59726e9) * Repeat for each Keystore then click Save * To see a list of your Keystores go to the Certificates and Keys: Key Storage view in the NWA Console (http://\:\/webdynpro/resources/sap.com/tc\~lm\~itsam\~ui\~mainframe\~wd/FloorPlanApp?applicationID=com.sap.itsam.cfg.sec.keystore\&applicationViewID=key_storage) ![image-20240315-213843.png](https://docs.rhondos.com/__attachments/a_377a862e4a94e66b2310f2ac3721da46b4c12caaf93ca174069b03167df2e5f8/image-20240315-213843.png?cb=08ae7b76bbc95505f34bc43852b95f16) * The Name column contains the list of the Keystore names ## Event The event will look like this: ![image-20240315-214143.png](https://docs.rhondos.com/__attachments/a_17b3426a8733bd6efb7758bb7fbe3ccea7704a686bbf9c061334fb557b69fb6f/image-20240315-214143.png?cb=9d4a33f5f7c6ab1c6ed8690871377296) There is an out of the box Splunk Dashboard available in the PowerConnect Splunk app: * Open the PowerConnect Splunk app * In the navigation bar click Java → NW → Netweaver Java: Certificate Monitoring ![image-20240315-214300.png](https://docs.rhondos.com/__attachments/a_d5936910a77dcd1d1e85a5929b636675fc574c63685c135bd49adc5341899f74/image-20240315-214300.png?cb=89227592b07a8500d41d847509752871) * The dashboard will be displayed ![image-20240315-214453.png](https://docs.rhondos.com/__attachments/a_486d4520f2019e50edd2680c86837d3f619d897c2b056d104b93a4993a0fcc8c/image-20240315-214453.png?cb=02888f33d51a3f9e072ce76798fee734) --- language: "en" --- # Cloud Foundry Syslog ## Overview SAP Cloud Foundry is a cloud plaform that allows you to create polyglot cloud applications in Cloud Foundry. It contains the SAP BTP, Cloud Foundry runtime service, which is based on the open-source application platform managed by the Cloud Foundry Foundation. The Cloud Foundry environment enables you to develop new business applications and business services, supporting multiple runtimes, programming languages, libraries, and services. You can leverage a multitude of buildpacks, including community innovations and self-developed buildpacks. It also integrates with SAP HANA extended application services, advanced model (SAP HANA XSA). The PowerConnect Cloud SAP Cloud Foundry Syslog Input allows any application deployed in SAP Cloud Foundry to send it's logs to the PowerConnect Cloud agent. These logs are then normalized, transformed and pushed to the target platform. ## Data Collected Syslog log data including logged errors and opentracing traces ## Status Beta ## Configuration ### Sylog over HTTPs Cloud Foundry is able to send syslog over https. As a prerequisite this requires the PC Cloud agent to be configured with SSL by following these steps (if the PC Cloud agent is deployed in Cloud Foundry its already SSL enabled) - [Configuring the PowerConnect Agent UI to use SSL](https://docs.rhondos.com/powerconnect-for-sap-solutions/configuring-the-powerconnect-agent-ui-to-use-ssl.md) Then do the following: * Login to the PowerConnect Cloud UI * Click on the Inputs tab ![image-20230801-120308.png](https://docs.rhondos.com/__attachments/a_7b2cf6bf926dfd70cbd6cedcfbae790b123914f5fd7c42697f80428885fd47d3/image-20230801-120308.png?cb=60f95c4423798c15af394e53af8ba845) * Click Add New ![image-20230801-120346.png](https://docs.rhondos.com/__attachments/a_3a0311b6d0ee4ca13bcfc24960d3e277fcbd362ea203e17f8b03063c0070594c/image-20230801-120346.png?cb=940064ab0d6f1ca7b646847129e25643) * Under the Platform menu choose CF ![image-20230801-120705.png](https://docs.rhondos.com/__attachments/a_7f4da8c21fe70f6b46394af7cd010bef74026019c32f22729bc67550fd55fbc3/image-20230801-120705.png?cb=4a7c99c05c32a0fc8ee96e60f0f81d10) * Then under syslog select cf-syslog-http ![image-20230801-120935.png](https://docs.rhondos.com/__attachments/a_a1340468fb4f3d4299598373a802a09eb6ccdd5f7570141e6fdbd7becf0a107c/image-20230801-120935.png?cb=a7ba83a02531f150a28c56c5fc5e59db) * Fill in the details for the Syslog Input, the System ID is mapped to the source field in Splunk ![image-20230801-121232.png](https://docs.rhondos.com/__attachments/a_5632138286a44b39fd254d8f92f2188c9bc3e09713b503ad18094d7515d9420a/image-20230801-121232.png?cb=64386054bb2fe752a17ec30f647682f5) * Click Save * The Input should now be created and visible in the Inputs table * In the Inputs table, click the View button under the Actions column for the newly created Syslog input ![image-20230801-121441.png](https://docs.rhondos.com/__attachments/a_18e504f40d677def5fd404fed197f511d7d14443f2e3094722dfd2669f0e250a/image-20230801-121441.png?cb=38dfdf153d25d0cebc135cfd9af0449f) * Click the unhide button next to the Token and note down the value ![image-20230801-121657.png](https://docs.rhondos.com/__attachments/a_c953742855ca5431ec1ef49b84544fd12efbf2e63f58414aedaeeb506a5adba4/image-20230801-121657.png?cb=0bec3ade43ea003fc965e3bebc71c812) * The token value will be used to authenticate the syslog data coming from the SAP Cloud Foundry applications * The next step is to create the PowerConnect Cloud syslog service cf create-user-provided-service powerconnect-syslog -l https:///ingest/http// * \ is the url where the pc cloud agent is running * \ is the input id of the syslog input you just created * \ is the token belonging to the syslog input you just created * Then bind the new syslog service to the application you wish to send logs from cf bind-service powerconnect-syslog * \ is the name of the application you wish to monitor * The application will then need to be restaged cf restage ### **Syslog over TCP** hen do the following: * Login to the PowerConnect Cloud UI * Click on the Inputs tab ![image-20230801-120308.png](https://docs.rhondos.com/__attachments/a_7b2cf6bf926dfd70cbd6cedcfbae790b123914f5fd7c42697f80428885fd47d3/image-20230801-120308.png?cb=60f95c4423798c15af394e53af8ba845) * Click Add New ![image-20230801-120346.png](https://docs.rhondos.com/__attachments/a_3a0311b6d0ee4ca13bcfc24960d3e277fcbd362ea203e17f8b03063c0070594c/image-20230801-120346.png?cb=940064ab0d6f1ca7b646847129e25643) * Under the Platform menu choose CF ![image-20230801-120705.png](https://docs.rhondos.com/__attachments/a_7f4da8c21fe70f6b46394af7cd010bef74026019c32f22729bc67550fd55fbc3/image-20230801-120705.png?cb=4a7c99c05c32a0fc8ee96e60f0f81d10) * Then under syslog select cf-syslog-tcp ![image-20241112-031549.png](https://docs.rhondos.com/__attachments/a_266e2423572d808497832e8e1dd72805d0ba4a8d4e3fd917c532e46480e13109/image-20241112-031549.png?cb=e766977ebde98cc89ef51b532833076e) * Fill in the details for the Syslog Input, the System ID is mapped to the source field in Splunk. The port should be set to an available TCP port above 1024 ![image-20241112-031402.png](https://docs.rhondos.com/__attachments/a_26313ee832084323721222d3714acfc2a3726d929992b43d3e46335a67235f67/image-20241112-031402.png?cb=de9a5d563c94e030ac42623e4e3268f0) * Click Save * The next step is to create the PowerConnect Cloud syslog service cf create-user-provided-service powerconnect-syslog -l syslog://: * \ is the host where the pc cloud agent is running * \ is the port you configured for the syslog input * Then bind the new syslog service to the application you wish to send logs from cf bind-service powerconnect-syslog * \ is the name of the application you wish to monitor * The application will then need to be restaged cf restage --- language: "en" --- # Cloud --- language: "en" --- # PowerConnect Cloud Release Notes --- language: "en" --- # Cloud Release Notes Archive --- language: "en" --- # Cloud Troubleshooting ## Summary Please consult the Knowledge Base to see if the problem you are encountering is documented with a resolution. The document below outlines key information required to troubleshoot potential problems associated with the PowerConnect Cloud application. Please acquire and attach the information below when submitting a support incident. ## Mandatory Information for PowerConnect Cloud Support Incidents Collect the following logs from the PowerConnect Cloud servers: From: /opt/powerconnect/logs ▪ powerconnect.log\* /opt/powerconnect/bin * nohup.out For Cloud Foundry environments run the following command to get the logs: `cf logs powerconnect-cloud --recent` Where powerconnect-cloud is the name of the deployed app --- language: "en" --- # Configure PowerConnect Java Agent (PowerConnect Java 6.X) Now that PowerConnect agent is installed, security is setup and license is installed, we need to configure the agent. → Note: If you're using a [Dual Stack setup](https://docs.rhondos.com/powerconnect-for-sap-solutions/additional-actions-for-dual-stack-systems.md), please execute some additional actions, described [here](https://docs.rhondos.com/powerconnect-for-sap-solutions/additional-actions-for-dual-stack-systems.md). There are 8 tabs to configure the agent, there are only 3 (three) that need to be configured to ensure agent is operational: · User credentials in the **General** tab · Splunk URL and HEC token in the **Splunk** tab · License key **License**tab (which should already be installed) For a full reference of each field refer to the full configuration reference. ![image-20200929-082525.png](https://docs.rhondos.com/__attachments/a_964cc75b4824113f233603013bc6f5044ae7700ace1fca20d14956e581c04aa7/image-20200929-082525.png?cb=37aaf0802fff64a7ec8c1995ed4c667b) ## General In this tab you need to configure the PowerConnect user and credentials that you created above in **Creating security user and role** Enter the user *powerconnect* and the password you set. Keep the case the same as the user/password created in previous steps. |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| | ![image-20200929-091210.png](https://docs.rhondos.com/__attachments/a_7c8fcf6c786cfb4cff9488ad6fbcd9ebb342b358deeaeb433c311d2044166bd4/image-20200929-091210.png?cb=ca32cc477c7c3f6a0e6e81739cbb411c) | user: powerconnect password: as set when you created the user (above). Both these parameters are case sensitive. | ## Splunk |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ![image-20201001-000246.png](https://docs.rhondos.com/__attachments/a_4d436ee615710a7beba667f56a0970f0e73f7cb8b634f059f0ca6bcd89f36b18/image-20201001-000246.png?cb=5ebc3e65ddbe860bafd869514b308fb7) | **Splunk HEC Key**: This is the HEC token that can be found in Splunk Enterprise → Settings → Data Input → HTTP Event Collector - Enter the HEC token for the HEC endpoint you want to use. **Splunk HEC URL**: This is the URL of the Splunk · indexer · heavyforwarder That you are sending the data to. It must include http:// or https:// at the start and be a correct URL (example [http://server.domainname.com:8088](http://server.domainname.com:8088/) It also needs to include the HEC ports (default: 8088) and can be found in the HEC settings Splunk Enterprise → Settings → Data Input → HTTP Event Collector → Global Settings → HTTP Port Number. If you are using SSL to connect from SAP → Splunk, you ++*must*++ ensure that: · The URL you enter here matches the CN in the certificate loaded in to the HEC endpoint, by default this is not true, Splunk comes delivered with a self signed certificate with CN=SplunkDefaultCert. This will not pass validation inside SAP. · This URL must be contactable from the SAP application server. You can test this using curl (unix/linux), or Invoke-WebRequest (Windows/PowerShell) to ensure SAP and connect successfully to the HEC endpoint and ensure there are no port blocks in place. · Ensure the HEC endpoint certificate (if it is self-signed) or the intermediate \& root signed certificates in the HEC endpoint chain are loaded in to SAP. If you want to send the data to multiple Splunk HEC endpoints, you can specify them comma delimited, however: · there must be the same number of HEC endpoints configured as HEC tokens · They must all use the same index name, and sourcetype Example config for multiple HEC endpoints HEC Url: [http://server1.example.com:8088](http://server1.example.com:8088/),[http://server2.example.com:8088](http://server1.example.com:8088/),[http://server3.example.com:8088](http://server1.example.com:8088/); HEC Token:HEC-TOKEN1,HEC-TOKEN2,HECTOKEN3 This configuration will load balance the data across all 3 servers [server1.example.com](http://server1.example.com:8088/) [server2.example.com](http://server1.example.com:8088/) [server3.example.com](http://server1.example.com:8088/) **Splunk Index** This is the index in which the agent will store the data. You can specify only 1 (one) index, even if you have multiple HEC endpoints. **Splunk sourcetype** This is the sourcetype the data is tagged with when sent to Splunk, ++*do not change this value*++. | Configuration work is finished now, data should be arrive in Splunk. If this is not the case, please view our [PowerConnect Knowledge Base](https://docs.rhondos.com/powerconnect-for-sap-solutions/knowledge-base.md), the installation [troubleshooting page](https://docs.rhondos.com/powerconnect-for-sap-solutions/troubleshooting-on-powerconnect-java-agent.md) or contact [PowerConnect support](mailto:support@powerconnect.io). --- language: "en" --- # Configure PowerConnect License (PowerConnect ABAP 7.X) → If installation has been executed properly, PowerConnect starts without any error prompt but with a license request. Ensure to have a valid license. If not, or if the license key does not work correctly, please contact your business partner or PowerConnect support: [Raising a PowerConnect Support Request](https://docs.rhondos.com/powerconnect-for-sap-solutions/raising-a-powerconnect-support-request.md)[.](mailto:support@powerconnect.io) → Keep in mind that settings done in PowerConnect are persisted as client dependent. Means, if you have more than one productive client, settings must be done separately. * Start program **/n/BNWVS/MAIN**. * The license prompt starts automatically at first startup. ![image-20210107-172419.png](https://docs.rhondos.com/__attachments/a_ad226a6667596d797d7affaf9fb363771f995d9a12480a3ce488616dd0de9797/image-20210107-172419.png?cb=ab0593a1892aee0324bb22142734b7b5) * The easiest way to apply the license is to put it into your clipboard and select the most right button to paste it from the clipboard. * After applying it you see a dataset telling you type and validity of the license. * Please read and accept the EULA. ![image-20210107-172655.png](https://docs.rhondos.com/__attachments/a_3c26ddf0eb21a59829d80c892929864ca44a330f4cb56a425651c77880460c05/image-20210107-172655.png?cb=b1e907c4d567156f1f86c6d0a8acaee0) ![image-20210107-172618.png](https://docs.rhondos.com/__attachments/a_aa7c6c7714b86fa3cffe5240bd774216ecc53767e753e71f0ddd37c3030f0a4a/image-20210107-172618.png?cb=fc7e3d04aa501def7be47adf349ee7ff) ![image-20210107-172828.png](https://docs.rhondos.com/__attachments/a_27f00d45cccfd45c50b7efa52aa073f42d29e6feda948f142d81c8915c024741/image-20210107-172828.png?cb=454b909e5920a361d52147f5ba115bce) PowerConnect now is ready to be configured. Thus a wizard is started by default to support you with [creating the connection between the PowerConnect ABAP application and Splunk](https://docs.rhondos.com/powerconnect-for-sap-solutions/configuring-powerconnect-splunk-connection-in-sap-.md). If you, however, want to create an encrypted connection between SAP and Splunk, you must [configure SSL](https://docs.rhondos.com/powerconnect-for-sap-solutions/optional-using-ssl-encryption-between-sap-and-splu.md) first. --- language: "en" --- # Configure PowerConnect License (PowerConnect ABAP 8.X) → If installation has been executed properly, PowerConnect starts without any error prompt but with a license request. Ensure to have a valid license. If not, or if the license key does not work correctly, please contact your business partner or PowerConnect support: [Raising a PowerConnect Support Request](https://docs.rhondos.com/powerconnect-for-sap-solutions/raising-a-powerconnect-support-request.md)[.](mailto:support@powerconnect.io) → Keep in mind that settings done in PowerConnect are persisted as client dependent. Means, if you have more than one productive client, settings must be done separately. * Start program **/n/BNWVS/MAIN**. * The license prompt starts automatically at first startup. ![image-20210107-172419.png](https://docs.rhondos.com/__attachments/a_0f5cba09ded4f650560ba7be291d1dc302d2cd921e31695dcabd72a7093d9a3d/image-20210107-172419.png?cb=ab0593a1892aee0324bb22142734b7b5) * The easiest way to apply the license is to put it into your clipboard and select the most right button to paste it from the clipboard. * After applying it you see a dataset telling you type and validity of the license. * Please read and accept the EULA. ![image-20210107-172655.png](https://docs.rhondos.com/__attachments/a_5851d3d17cb8bacfea16875d8f1a42ab6d3ddf4f9cbff85bb2fcfb2df92c1f1b/image-20210107-172655.png?cb=b1e907c4d567156f1f86c6d0a8acaee0) ![image-20210107-172618.png](https://docs.rhondos.com/__attachments/a_18c19c49a4b5a92c22fb4b19569b01ec2b5bc8d89eff301dff5f3a1f359e3929/image-20210107-172618.png?cb=fc7e3d04aa501def7be47adf349ee7ff) ![image-20210107-172828.png](https://docs.rhondos.com/__attachments/a_ae5c955f6bcfa7e7028b5aa5f1334a32c4948fe1398ee1e3f416a6a1d43c2193/image-20210107-172828.png?cb=454b909e5920a361d52147f5ba115bce) PowerConnect now is ready to be configured. Thus a wizard is started by default to support you with [creating the outbound connection for the PowerConnect ABAP](https://docs.rhondos.com/powerconnect-for-sap-solutions/configuring-outbound-connection-in-powerconnect-po.md). If you, however, want to create an encrypted connection, you must [configure SSL](https://docs.rhondos.com/powerconnect-for-sap-solutions/optional-using-ssl-encryption-between-sap-and-targ.md) first. --- language: "en" --- # Configure PowerConnect License (PowerConnect ABAP 9.X) → If installation has been executed properly, PowerConnect starts without any error prompt but with a license request. Ensure to have a valid license. If not, or if the license key does not work correctly, please contact your business partner or PowerConnect support: [Raising a PowerConnect Support Request](https://docs.rhondos.com/powerconnect-for-sap-solutions/raising-a-powerconnect-support-request.md)[.](mailto:support@powerconnect.io) → Keep in mind that settings done in PowerConnect are persisted as client dependent. Means, if you have more than one productive client, settings must be done separately. * Start program **/n/BNWVS/MAIN**. * The license prompt starts automatically at first startup. ![image-20210107-172419.png](https://docs.rhondos.com/__attachments/a_cb98e6b0097b0d52b60f12a7a0f0588d2b16568aa3bf3c3f6a6c1de6f35a7cc3/image-20210107-172419.png?cb=ab0593a1892aee0324bb22142734b7b5) * The easiest way to apply the license is to put it into your clipboard and select the most right button to paste it from the clipboard. * After applying it you see a dataset telling you type and validity of the license. * Please read and accept the EULA. ![image-20210107-172655.png](https://docs.rhondos.com/__attachments/a_76808f2bd5581ca6ffd2d6c2d422aecf45723a8ff7557de8265388786123d779/image-20210107-172655.png?cb=b1e907c4d567156f1f86c6d0a8acaee0) ![image-20210107-172618.png](https://docs.rhondos.com/__attachments/a_6973347534a036d7b19c84b8382d7c16728ed7efbd8cae55f70345d7bad2fb4e/image-20210107-172618.png?cb=fc7e3d04aa501def7be47adf349ee7ff) ![image-20210107-172828.png](https://docs.rhondos.com/__attachments/a_1b6f13fc28eafb71c4ac5c5c3558a60bf918bd6042a6dab9c296c3568b1969f3/image-20210107-172828.png?cb=454b909e5920a361d52147f5ba115bce) PowerConnect now is ready to be configured. Thus a wizard is started by default to support you with [creating the outbound connection for the PowerConnect ABAP](https://docs.rhondos.com/powerconnect-for-sap-solutions/configuring-outbound-connection-in-powerconnect--1.md). If you, however, want to create an encrypted connection, you must [configure SSL](https://docs.rhondos.com/powerconnect-for-sap-solutions/recommended-using-ssl-encryption-between-sap-and-t.md) first. --- language: "en" --- # Configure SSL in Splunk (Recommended) Using an SSL connection with the Splunk application is optional for the PowerConnect application. If you do not wish to use SSL, proceed to [Create a Splunk Role](https://docs.rhondos.com/powerconnect-for-sap-solutions/create-a-splunk-role.md). SSL is enabled by default for Splunk Cloud deployments, but Splunk Enterprise may require additional setup as noted below. ## Setup for Splunk Enterprise * Click on "Global Settings" under Data Inputs --\>HTTP Event Collector in Splunk and click on Global Settings. Ensure the "Enable SSL" checkbox is selected if you want to use SSL connection in your environment. ![image-20210316-171337.png](https://docs.rhondos.com/__attachments/a_2994a78398cbdb9710902e945b01c9f6139c97e2cce1af787256555c8e1de1ac/image-20210316-171337.png?cb=36f9c7031fe333b7590dc5a4e4fdb9b9) ![image-20220315-183429.png](https://docs.rhondos.com/__attachments/a_ec9e5158f9a940710b08b74c0f43d7fdc28912747cb860b13582453d9d654758/image-20220315-183429.png?cb=37e54026c9076f17f7c52920fb5c394f) * If the Splunk host does not already have a valid certificate for web connections, obtain either a ROOT CA or self-signed certificate for your Splunk environment for configuration of SSL between Splunk and the source SAP system(s). Instructions for creating a self-signed certificate for the Splunk host are available here: [KB 95 - Splunk -- Create Self-signed SSL Certificate V2](https://docs.rhondos.com/powerconnect-for-sap-solutions/kb-95-splunk-create-self-signed-ssl-certificate-v2.md) or * If needed, you can obtain a copy of the certificate using the steps below. ## Export SSL Certificate * Start by connecting to your Splunk instance on port 8089 (Splunk Enterprise) or port 443 (Splunk Cloud) using HTTPS. this will show you the certificate in use. ![image-20210316-171806.png](https://docs.rhondos.com/__attachments/a_aa45ad06b219abd58f4b8e8dfe388e074cd537091cb7b771067c8b5c6eeabef0/image-20210316-171806.png?cb=85f6cbef7a1727182e41a4308d279958) * Open the certificate information ![image-20210316-171834.png](https://docs.rhondos.com/__attachments/a_cd29cedd837bfbf5548cea580b491d8662dc5cdfeb0b317cf3fd8aff834b7b3e/image-20210316-171834.png?cb=5b7e57452571672ecc12e4dcd125ad06) * Next, click "Copy to File" to export this certificate ![image-20210316-171913.png](https://docs.rhondos.com/__attachments/a_d98dbd111ae86ccdcbbbe5b95ca0e8a0679623864d7621e01756218a2daaeaf2/image-20210316-171913.png?cb=8ced3df0c1b1693b2795ffac81f006bb) ![image-20210316-171934.png](https://docs.rhondos.com/__attachments/a_6501375f295ff7f95c3b56f78843ffe084da3cc292d9ed34eef625036a711d4b/image-20210316-171934.png?cb=9216bb5f2d2e0d4ff538b65e821dadba) ![image-20210316-171948.png](https://docs.rhondos.com/__attachments/a_12d0a0da22643d6ed2264d4faee6279b04a8b6c14b00baa40ff8a984c4741e23/image-20210316-171948.png?cb=41625c034dfde4cbc136d50e9a18435f) ![image-20210316-172000.png](https://docs.rhondos.com/__attachments/a_79157ad968d7e8109b0c71b44072351369650fd6bede75a6b3193cdd33491024/image-20210316-172000.png?cb=ef837d5583eca56400d1c06ad86c8fb5) ![image-20210316-172012.png](https://docs.rhondos.com/__attachments/a_a64111661bce028cd075572b82bda013e73444023f3647e669a617cdc709b7e9/image-20210316-172012.png?cb=7430c2a6e586b5087c5a1c393b9ac41b) * When uploading the SSL certificate into the SAP system via STRUSTSSO2, please confirm the CN field matches the root domain of your Splunk instance. See the example below for Splunk Cloud. ![image-20220315-171301.png](https://docs.rhondos.com/__attachments/a_93f848013cfd71ca64b7aeb572d0eae79b5be053841ff66af207e26a9cb3e8cf/image-20220315-171301.png?cb=920c8aff2db0340d0705b951cdaefd23) SSL configuration is now complete. Next step would be to create an SAP-specific Splunk role: [Create a Splunk Role](https://docs.rhondos.com/powerconnect-for-sap-solutions/create-a-splunk-role.md). --- language: "en" --- # Configuring a Dynatrace Connection in PowerConnect for SAP Data Services ## Configuration Steps To create a connection to the Dynatrace Log Monitoring API do the following: * Open the PowerConnect Java UI - http(s)://\:\/powerconnect-java/index.html * On the menu on the left click **Dynatrace** under Outputs * Fill in the details of your Dynatrace Log Monitoring API endpoint: ![image-20240711-025607.png](https://docs.rhondos.com/__attachments/a_c84b81ee8a09ad8606cd91913ce4ce8b1502ae02c8f7cafa29200728138d47cd/image-20240711-025607.png?cb=c613d4ef73a9c2f3918589c2939d1fb9) | **Configuration** | **Description** | **Required** | **Default Value** | **Comments** | |------------------------------------|-------------------------------------------------------------------------------------|--------------|-------------------|------------------------------------------------------------------------------------------------------------------| | Dynatrace Log Monitoring API URL | Log Monitoring API url | Yes | | e.g. [https://xxx.live.dynatrace.com/api/v2/logs/ingest](https://wwp60164.live.dynatrace.com/api/v2/logs/ingest) | | Dynatrace Log Monitoring API Token | Log Monitoring API token | Yes | | | | Retry | Retry sending data if the Dynatrace endpoint is down | No | No | | | Max Retries | If retries are enabled defines how many times the Agent will retry before giving up | No | 3 | | | Retry Interval | Time in milliseconds the Agent will wait between retries | No | 10000 | | * Click **Save** * To test the connection click Administration in the menu on the left then click the Health tab ![image-20240711-025656.png](https://docs.rhondos.com/__attachments/a_1924573c211b618505609df7ebd8834f34eeebcf666fe69e86cfff246d85f022/image-20240711-025656.png?cb=7ec86d07bb98e23009b7070af35d0fd2) * Click the Dynatrace Log Monitoring API button and a message will be displayed showing the result ![image-20240227-215644.png](https://docs.rhondos.com/__attachments/a_d20c437f1fcfe5e9c5ef7f498328f6707ab3b1c6efbf84606e8ac3890e2425be/image-20240227-215644.png?cb=f2af1d464d4a5f70b575625b712a670a) [Next Page](https://docs.rhondos.com/llms-full.txt/1)