Object Providers define these RFC connections and therefore they must be configured for usage.Įvery Object Provider must be assigned to a System Group, therefore before you configure Object providers, you need to create System Groups. While ATC check runs in the central system, the ATC framework uses RFC connections to the remotely checked systems to extract a model from the custom code for analysis. Use transaction SM59 to create RFC destinations for each ABAP system, which will be checked in the current central ATC system. Define RFC destinations for checked systems This option defines that the current system takes the role of the ATC central check system and ATC is used to analyze development objects in remote systems.Ģ. Switch to change mode, choose ATC Checks by Object Providers Only option and click Save button. Under ATC Administration -> Setup double-click the Set System Role entry: Log on to the ATC central check system as ATC administrator and call transaction ATC. Setup System Roleīy setting up the system role you can specify the current system as a central check system for remote ATC checks. PLEASE NOTE: The ATC central check system can only analyze systems at the same or lower software levels. Please also assign your RFC user the corresponding roles as described in SAP Note 2672703 Authorization roles for remote check scenarios See Authorizations for the ABAP Test Cockpit. You would also need authorizations for administrative and quality assurance activities. If you intend to run ATC for the objects in your own custom namespaces (other as Z* or Y* namespaces), you will need to register custom namespaces of the checked systems at the central ATC system. The RFC destinations for all checked systems must be provided in the ATC central check system and RFC-stubs must be implemented in all checked systems.ĭepending on your support package level you need to apply the respective SAP Notes for using ATC to perform remote analysis. For supported SP levels see also the SAP Note 2385520. The systems, which you want to check in your landscape, must be on SAP_BASIS 7.00 (not before SP15), 7.01 (not before SP01), 7.02 (not before SP09), 7.31 (not before SP03), 7.40 (not before SP02) or 7.50 releases. Depending on how many custom objects you need to consider, SAP recommendation for system sizing is about 1 CPU and 4GB RAM per 16000 objects, for data volume on the DB about 400kB per object. To use Remote Code Analysis in ABAP Test Cockpit (ATC) you need to install and configure one ATC central check system SAP_BASIS 7.51 or >=SAP_BASIS 7.52. Remote Code Analysis in ATC – Maintain exemptions approvers according to their responsibilities Remote Code Analysis in ATC – Browse Central ATC Result in Developer Systems Remote Code Analysis in ATC – How to check Smart Forms and Adobe Forms Remote Code Analysis in ATC – How to write an ATC check Remote Code Analysis in ATC – Working efficiently with ATC Result List Remote Code Analysis in ATC – Scanning customer extensions Remote Code Analysis in ATC – Working with Exemptions Remote Code Analysis in ATC for Developers Remote Code Analysis in ATC– Working with Baseline to suppress findings in old legacy code Remote Code Analysis in ATC – One central check system for multiple systems on various releases.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |