![]() ![]() Also the number of ABAP dialog work processes that can be used by the EFWK is subject to the resource cap. You can set resource caps for each READ RFC destination to a managed system and local RFC destinations. But if the managed system is very busy or huge and a lot of data has to be collected and if RCA and E2E Monitoring and Alerting is both active, it can be necessary to adjust the resource cap. Sometimes it can be necessary to adjust the resource cap. If an extractor hits a timeout 3 times, it is banned from further execution. There is also a timeout in EFWK, after which a resource is released no matter if the extractor finished or not. Additionally an enqueued lock is set per extractor to make sure it cannot be started several time at once in SAP Solution Manager. ![]() Usually a resource is blocked as long as the extractor is running. The resource cap applies to all extractors for a system, RCA as well as E2E Monitoring and Alerting and other use cases. This resource cap makes sure that the Resource Manager doesn't open too many RFC destinations to a managed system and might overload the managed system. The EFWK is controlled by the Resource Manager and is subject to the so called resource cap. In case of an error you will an error message in the column Message.Ĭhanging the Resource Cap for RFC Resources Which phases an extractor has, depends on the extractor. When you select a run you find details on the selected extractor run in the table below. When you select an extractor in a table below you find the status of the last N runs (per default N would be 20). However, before the collected data is written to the BW, that data is converted into the time zone of SAP Solution Manager. The extractor makes sure the data is delivered in UTC time zone. The Required Record algorithm and the Logging are also in UTC. Please note that all data transported in the Extractor Framework is always in UTC time zone. A timeout can occur if the extractor runs too long and is blocking a resource (i.e. An extractor gets banned if he causes 3 timeouts in the EFWK. Banned means the extractor is not executed anymore, due to previous problems it was causing. if the technical configuration of the system is changed. Setup for Benchmark Project (Massman Data)Īn Extractor can become inconsistent, e.g. IT Management Reporting – BI Self Service Monitoring and Alerting relevant Extractors Statistical Records (Mainextractor = E2E*SSR*)Įnd User Experience Monitoring (Technical Scenario)Įnd User Experience Monitoring (SolMan System only) Root Cause Analysis (Mainextractor E2E*SSR*) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |