Query on Installation of GRC AC 5.3 RAR component

Hi,
We are implementing SAP GRC 5.3 - RAR Component. Can the tool needs to be implemented in the SAP Server itself or can it be installed in a different server other than SAP.
Can GRC tool be installed in a different server but falling under the same system landscape directory?
In future we are also planning to go for the other components of GRC like CUP, SUPM & ERM. In that scenario, does these components also needs to be installed in SAP Server itself.
Please suggest the SAP best practice of installation of SAP GRC 5.3
Request the experts to reply at the earliest.
Thanks and Best Regards,
Srihari.K

Hi Srihari,
I agree with Frank and you need to go to SAP Service Market Place and check out the Installation and Configuration guides for SAP GRC 5.3 at https://service.sap.com/instguides.
I also recommend to go through these articles published on SDN.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/408bd039-d9c1-2a10-0fab-a92b97c7cd25
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a07b4cc8-1a57-2b10-1798-d2fec068473a
Hope this helps as a good starting point for learning about SAP GRC Installation reqs.
Regards,
Kiran Kandepalli.

Similar Messages

Running Analysis in GRC AC 5.3 - RAR

Hi,
Can anyone let me know how to resolve the issue.
When i run the Risk Analysis in GRC AC 5.3 - RAR
Informer>Risk Analysis> Role Analysis--> Execute
This is the error message it gives:-
*VIRSAHR_01: Cannot execute BAPI RoleList: Error connecting using JCO.Client: null: Could not create JCOClientConnection for logical System: VIRSAHR_01_MODEL - Model: class com.virsa.cc.modelvirsahr_01.BAPI_VIRSAHR_01. Please assure that you have configured the RFC connections and/or logical system name properly for this model!: Error while obtaining JCO connection.: Failed to resolve JCO destination name 'VIRSAHR_01_MODEL' in the SLD. No such JCO destination is defined in the SLD. *
Please indicate what could be the possible solution for it.
Thanks in advance.
Nazeer

HI ,
Why dont you check the SLD is running fine or not.These are the steps to be followed ,
Check out the URL : http:
<localhost>:50000/sld
When you enter the sld screen then click on administration and there you will see whether sld server is running or not.If it is stopped then start.
Then check whether in visual administrator check for sld data supplier under server node under services node.There on the top there will be a button as trigger sld data supplier .We should get a succesul message.
In the Jco connections click on test option one should get a test message succeful.To see the JCo connections path launch j2ee home page URL : http:
<localhost>:50000/.After that click on web dynpro then on content administrator and then maintain JCo connections.There check out the JCo connections.IF the JCo connections are not working fine then check out the RFC 'c configured in the backend system are testing successfully.
SLD_UC
SLD_NUC
LCRSAPRFC
SAPSLDAPI
If u still face any problem plz let me know.

GRC AC 5.3 - RAR Parameters

Hello,
I have the following 8 queries related to GRC AC 5.3 RAR parameters
When I go into RAR -> Configuration -> Miscellaneous, I see the following entries.
Maximum Display Lines For Print Preview
This parameter specifies the maximum number of lines to be displayed in print preview mode; the default value is 500
1- What is the Print Preview of the lines for? Can I make it 10000 instead of 500. Is there a performance impact?
Background Job Spool File Location
This parameter specifies the location where the background job spool files are stored Note: You need to restart the server
2- Why do I need the Background Job Spool File location? Is it when I use Default Logger parameter as SAP Logger? Currently we are using the Default Logger parameter as Java Logger
Alert Log File Name and Location
This parameter specifies the location where the action usage purged data files are stored
3- Whey do I need this Alert Log file parameter for? I mean how is the Alert Log file generated in RAR 5.3
SAP Application Server Location
Enter SAP application server location here
4- Why do I need SAP Application Server Location, when I have installed SAP GRC 5.3 on standalone SAP JAVA Stack?
FTP Site Location
Enter FTP site location here
5- What should the FTP site location be given as? Should I give a fully qualified domain for a particular host for the FTP of above RAR background job log files and RAR Alert log files?
6- Do we have the background job log files FTP into another host, if Default Logger parameter is chosen as SAP Logger?
FTP Site User Name
Enter FTP site User Name here
7- What is the best practice for specifying a FTP User? I mean what is the username normally given in RAR environment?
8- Is there any OSS Note, SAP Help URL which describes about RAR parameters in detail?
Thanks,
Haleem

Hi,
> Maximum Display Lines For Print Preview
> This parameter specifies the maximum number of lines to be displayed in print preview mode; the default value is 500
>
> 1- What is the Print Preview of the lines for? Can I make it 10000 instead of 500. Is there a performance impact?
>
You should used 500 only.
> Background Job Spool File Location
> This parameter specifies the location where the background job spool files are stored Note: You need to restart the server
>
> 2- Why do I need the Background Job Spool File location? Is it when I use Default Logger parameter as SAP Logger? >Currently we are using the Default Logger parameter as Java Logger
>
No, background job spool file location is something different from logger. Background spool file location is the location where
spool file of your background job will be generated.
Diferent between Java Logger and SAP Logger is that if you choose SAP Logger then log file of your RAR will be generated in NWA. But if you will choose as Java Logger then log file will be generated as separate file as ccappcomp.<n>.log which you will see in CC debugger.
> Alert Log File Name and Location
> This parameter specifies the location where the action usage purged data files are stored
>
> 3- Whey do I need this Alert Log file parameter for? I mean how is the Alert Log file generated in RAR 5.3
>
check below link:
Compliance Calibrator Alert Generation Issue
> SAP Application Server Location
> Enter SAP application server location here
>
> 4- Why do I need SAP Application Server Location, when I have installed SAP GRC 5.3 on standalone SAP JAVA Stack?
>
> FTP Site Location
> Enter FTP site location here
>
> 5- What should the FTP site location be given as? Should I give a fully qualified domain for a particular host for the FTP of above RAR background job log files and RAR Alert log files?
> 6- Do we have the background job log files FTP into another host, if Default Logger parameter is chosen as SAP Logger?
>
> FTP Site User Name
> Enter FTP site User Name here
>
> 7- What is the best practice for specifying a FTP User? I mean what is the username normally given in RAR environment?
The following new reports can have long runtimes:
- User Authorization Count
- Role Authorization Count
- List Expired and Expiring Roles for Users
- For that reason These jobs run on ABAP side and produce a spool file. An icon is displayed on the front-end for the jobs that complete. (If you run jobs on all systems and it finishes on one system before another the icon will display for the finished system first)
- The report directory on the SAP Enterprise Resource Planning (ERP) application servers. This is the temporary storage location for spool files generated by these background jobs.
- The same directory name is used for all SAP backend systems.
- The location, user name, and password for FTP of security reports generated by backend SAP ERP systems.
> 8- Is there any OSS Note, SAP Help URL which describes about RAR parameters in detail?
Note 1121978 - Recommended settings to improve peformance risk analysis
Check below link for performance optimization of RAR:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90aa3190-8386-2b10-c4ba-ced67322ea6d?quicklink=index&overridelayout=true
Thanks
Sunny

SAP GRC AC 5.3 RAR Background jobs are cancelled

Hi Experts,
we have newly implemented theS AP GRC AC 5.3 RAR Help me in troubleshooting the Background jobs cancellation in SAP GRC AC5.3 RAR.. we have reported this issue to customersupport they asked us to upgrade the front end patch level to Sp15, even we upgraded still i have the same problem.. later we upgraded the backend patch according to the SAP Note. still the problem is not resolved.
Latest recommendation they are asking us to uninstall the SMD agent.. and also my java control.exe is showing yellow color
help me how to resolve the issue.??
Edited by: n.s.k mohan on May 10, 2011 6:21 AM

Hi,
Could you please first change RAR log settings to Java logger then take a restart of the system. After that log for your background will start coming in RAR. Then schedule the job if it fails then paste background job log here.
Also, in future, please raise GRC related issue in GRC forum so that you can get more replies.
Thanks
Sunny

Query builder installation

Hi,
please excuse my english.
I have a 9.2.0.1.0 installed database
I would like to use Query Builder and schema Builder from Oracle 6i
(Oracle Designer 6i Release 4.4 - a full, patch release for Designer 6i Release 4
(Includes the Designer 6i Release 4, R1.3.2 to R6.0 Upgrade)
The installation work fine but when I connect I have the messages
OBE-15952 Privilege table not loaded and
OBE-15950 no query builder table, Open and Savin deactivated.
In fact the repository is missing
I've tried to run BRWIN60 in <OracleHome>\BROWSE\SQL to create the desired tables but I've got the message : These scripts lets you install the Oracle Query Builder system tables.
*** Error: File system is not writable. ***
Installation has failed. Please make the file system writable and
restart installation.
can anyone explain what does it means ?
thank you for help.
Marc

The scripts is what you need to run.
Check out that the directory you run them from is writeable.

Unable to see installation files (GRC) at service market place

I am not able to see the files of GRC installation at the service market place by going through the menu.
Navigate Installation and Upgrades -
> Entry by Application Group -
>SAP
Solutions for GRC -
> SAP GRC Access Control.
Can anyone provide the installation files( .CAR , .SAR ) for the same.
Regards

Your organization needs to hold a valid license for SAP GRC Access Control. If that is the case your S-user ID that is linked to your organization's customer number at SAP will have access to the software download page on the [software download section of the SAP Service Marketplace|http://service.sap.com/swdc].
Please allow me to point out that this forum's participants use their real name when posting questions or comments on the BPX forum. Would you mind following that practice?
My apologies if my assumption is wrong and your name is indeed Indian Tiger.

Power Query SCCM Installation

I have been trying to create a SCCM application which will install Power Query after installing MSOffice Pro Plus 2013. On a machine which has the Office, I can manually install Power Query, however, silent and administrative installs do not work.
Has anyone successfully install Power Query through System Center as a system application (no user interaction)? If so, what am I missing.
Steps taking so far:
Downloaded latest Power Query Software: "PowerQuery_2.13.3688.242 (32-bit) [en-US].msi"
Created a new application from the MSI.
Created a deployment.
Tested deployment on Windows 8.1 Machine. Failed to install.
Tested deployment on Windows 7 Machine. Failed to install.
Tried on both Windows 7 and 8.1 Machines to install by command line (admin command prompt) with /a or /I with /qn and will not install.
In event viewer return code is installation success or error status: 0.
Verified com add-in is not present.
Tried on Windows 7 and 8.1 machines installing with no flags and installs successfully.

Hi,
I've tried to install PQ through SCCM it failed. I'm using command: msiexec /i "PowerQuery_2.16.3785.242
(64-bit) [en-us].msi" /q ACCEPT_EULA=1
This command works when I run cmd as Administrator on local machine (non-domain joined). But when cmd runs as a regular user (this user is local admin) it fails. SCCM tries to run it as local admin.
SCCM gives following error: 0x643 (1603).
Google says that it is related with elevation. Note: Run as Administrator feature blocked on client machines through GPO.
Could someone help me?

Add on installation (SAP GRC compliance calib) - Post installation question

Hi,
I have installed Virsa RTA 5.1 on ECC 6.0. This is a brand new system and I have followed all the steps recommended by SAP. And after installation and activating the BC-sets, I was able to execute transactions for Role Expert and Compliance Calibrator in my 000 client. But when I logged onto a different client (let's say client 226.) I was able to execute transaction for role expert, and when I execute Compliance calibrator (/virsa/zvrat) nothing happens (the status bar says starting application Virsa CC and stops). It dosent even show any error. But as I said all the transactions are working fine in my 000 client. So am I missing any step here. Please help me in solving this issue.
Thanks,
Naveen

Juan,
Thanks for your suggestion... but I already tried it and actually I figured it out by myself... it was the type of userID. I was using a service user to access CC in the other client i.e 226. This sounds wiered but when I changed the user type to Dialog it worked... Anyways thanks for taking your time on this..

Query View Installation

Hai Friends..,
Is in BI 7.0 any possibilities to install the BI content without install the root Query..,
Please advise me..,
Thanks

Root is the Base...,
The query which will use to create the View is called "Root"
Thanks

Query regarding installation of SOA Suite on Windows Vista 64 Bit

Hi,
I would like to setup a development enviroment having Oracle SOA Suite 10g and Oracle Database Server 10g on my laptop. Please can anyone clarify whether these softwares are compatible with a laptop of below mentioned configuration:
===========================================================HP Pavilion dv9700t Notebook PC
Windows Vista Home Premium with Service Pack 1 (64-bit)
Intel(R) Core(TM) 2 Duo Processor T5750 (2.0 GHz)
17.0" diagonal WSXGA+ High-Definition HP BrightView Widescreen Display (1680 x 1050)
3GB DDR2 System Memory (2 Dimm)
256MB NVIDIA GeForce 8400M GS
320GB 5400RPM SATA Hard Drive
===========================================================
I have gone through the compatibility matrix. However, the compatibility matrix mentions that Oracle software is compatible with EM64T processor.
Request clarification on whether an Intel(R) Core(TM) 2 Duo Processor T5750
(2.0 GHz) belongs to EM64T family or not.
Thank you.
Regards,
Balu

Didn't you read the posts in your other thread? Several people told you what needed to be done.

WAAS Default Group query - New Installation

Hi All,
This may be a very quick and easy to answer question so here goes.....
I have a WAAS estate of "X" amount of devices from day one initially the default application acceleration options were fine so all devices as default out of the box join the "AllDevicesGroup". This for the main is absolutely fine.
I have recently been asked to look at an application for acceleration and am in the process of creating the policy etc to apply, creating new classifiers etc for this.
My question mainly relates to why i can not see any applications defined when i navigate via:-
My WAN/Device Group/AllDeviceGroup then Configure/Acceleration/Policy Definitions on the Central Manager
HOWEVER
when i navigate directly on to a particular WAE device and go through the same steps above i see a list of applications as you would expect and it then states "inherited from AllDevicesGroup" so i know this is gathering the information regarding config/classifiers etc from the CM AllDevicesGroup.
i just wonder in this scenario how would i edit an existing default classifier for example wanting to add TCP pport 8082 to HTTP as an example would this mean changing it on every endpoint which to me defeats the object in having a alldevicesgroup?
any thoughts on this would be appreciated as usual.
thanks
craig

Hello Craig,
What you are seeing is correct, at least it was also on our lab device.
You can click on "Restore Predefined Policies and Classifiers" on the My WAN -> Device Group -> AllDeviceGroup -> Configure -> Acceleration -> Policy Definitions page.
This will populate the page with the default rules, you can then add your custom application to this.
I hope this helps, Peter

Query on SoD matrix for CRM-Webshop applications - RAR 5.3

Hi,
We are implementing RAR 5.3 for CRM system. We observed that GRC has standard SoD matrix for CRM application. But there is no SOD matrix available for the Webshop (B2B/B2C/BOB) where access will be provided to the external users
We are of the opinion that there will be no SoD conflicts for the Roles/Users created for the webshop applications as the webshops are used by the external users i.e. customers.
Is there any standard SoD matrix available for the authorization objects of the webshop application with SAP? Has anybody configured SoD rules for the webshop application roles? If yes, please provide us the link of the information where we will get this rule matrix
Thanks in advance.
Srihari.K

Hi Sri,
The standard rule for CRM is available in the marketplace.
But I don't think SAP has created standard rule for webshop.
Thanks,
Sudip.
Edited by: Sudip Saha on May 18, 2009 4:05 PM

GRC-AC 5.3 RAR Management view error - Expired users not cleaned-up.

Hello Gurus,
I have a problem in RAR Management View: Users who was valid have been analyzed and their conflicts considered in statistics, but when they become expired, their conflicts remain in the statistics forever, because they are not re-analyzed neither in Full nor in Incremental sync. Even if all roles are removed from the user in backend, the conflicts remain in Management View.
I think the Full Batch Risk Analysis should clean-up all users violations from current period statistics before recording the new analysis results.
Did you have this problem too? Am I missing something?
I appreciate your thoughts about it.
Vaner

Hello Nuno,
Thanks for your comments.
My release is 5.3 SP 16.2.
I also think the full sync should be enough but I already find about 20 users with problems, in 4 different backend and in 2 GRC (Tests and Production)
I think that depending on some procedures done in the back-end the full sync do neither re-analyze the user nor clean-up previuos statistics, for example:
1. A user was delete and recreated again with option to maintain old data, and he already had expiration date.
2. A sand-box environment was created as copy of production, users were created valid but already with expiration date.
I observed that for these scenarios, there was no Change Document for field "valid to", my guess is that Full Sync process relies on Change Documents to do its job.
I already opened a message in SAP for this, first level could not solve it, It is in Development Team now.
Vaner

Moving connections of GRC AC 5.3 RAR with R/3 ABAP Client (same SID)

Dear All,
Please can someone assist me with the documentation for the movement of the connection of AC 5.3 RAR based on Java, from one client in R/3 ABAP to another.
For e.g. if GRC AC 5.3 is connected to QAS Client 101 on ABAP side, how to move the connection to Client 102 on the same system (SID).Also, mention please, if there are any specific steps to carried out for removal of existing connection.
Regards,
Prashant

Usually you don't move a connection, as the analysis results and the naming reflect the target system.
I don't know your specific context, but let's asusme you're finished working with the test system and want to add the production system.
From SP10, RAR has a feature to delete a connector and all related data (Careful! Be sure to back up your rule set before you do that!).
You would then create the new connector, add it to the logical system, create the rules, plan the sync and analysis jobs and you're good to go.
If that's not what you're looking for, please tell us a few nmore details.
Frank.

GRC AC 5.3 RAR: Change system connector entry

Just a tip:
I had a problem after upgrading from RAR 5.2 where the previous connector entry wasn't named the same as it is in the SLD, so I had to change the connector. We have a lot of information in our RAR system, so I didn't want to clean the database and start over, I just wanted to change the name of the connector. Therefore, I used the following SQL query to rename it across the whole application. You can input the RENAMED SYSTEM to whatever you want your rename to be, and of course input the SID of the system for the database schema. This is for SQL Server 2005, but you can adapt it to your flavor.
update SAP<SID>DB.VIRSA_CC_ACTRULE set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ACTUSAGE set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ACTVL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ALLASTRUN set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ALLISTDTL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ALTCDLOG set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ANLACT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ANLPRM set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_AUTHMAP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRACT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRACTT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRACTVL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRPRM set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRPRMVL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRPROF set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRPROFT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRROLE set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRROLET set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRROLEVL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_DATAEXD set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_EXLOBJ set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_FLDMAP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_FUNCACT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_FUNCPRM set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_FUNCSYS set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_GENACT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_GENOBJ set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_GENOBJT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_GENPRM set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_GENUSR set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_GPRMLIST set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_LASTRUN set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_LSYSGRP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_LSYSGRP set LVSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MGALERTS set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MGCRTR set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MGMTBU set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MGMTTOT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MGRISKD set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MGRISKS set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MITRPT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MTGENOBJ set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MTGENOBJH set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ORAEXT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ORGUSERS set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_PRMRULE set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_PRMVL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ROLEVL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SCHEDFORK set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SUPP_DET set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SUPP_HDR set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SUPP_TEXT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSCRACT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSCRACT set PVSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSHMAP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSRULE set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSSAPOBJ set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSTEM set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSTEMC set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSTEMT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSUSR set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_TEXTKEY set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_USRMAP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_XSRULEMAP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_XSRULEMAP set PVSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_XSRULEMAP set LVSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_XSYSGRP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_XSYSGRP set XVSYSKEY = 'RENAMED SYSTEM'

Just a tip:
I had a problem after upgrading from RAR 5.2 where the previous connector entry wasn't named the same as it is in the SLD, so I had to change the connector. We have a lot of information in our RAR system, so I didn't want to clean the database and start over, I just wanted to change the name of the connector. Therefore, I used the following SQL query to rename it across the whole application. You can input the RENAMED SYSTEM to whatever you want your rename to be, and of course input the SID of the system for the database schema. This is for SQL Server 2005, but you can adapt it to your flavor.
update SAP<SID>DB.VIRSA_CC_ACTRULE set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ACTUSAGE set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ACTVL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ALLASTRUN set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ALLISTDTL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ALTCDLOG set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ANLACT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ANLPRM set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_AUTHMAP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRACT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRACTT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRACTVL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRPRM set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRPRMVL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRPROF set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRPROFT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRROLE set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRROLET set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_CRROLEVL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_DATAEXD set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_EXLOBJ set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_FLDMAP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_FUNCACT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_FUNCPRM set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_FUNCSYS set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_GENACT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_GENOBJ set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_GENOBJT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_GENPRM set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_GENUSR set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_GPRMLIST set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_LASTRUN set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_LSYSGRP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_LSYSGRP set LVSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MGALERTS set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MGCRTR set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MGMTBU set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MGMTTOT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MGRISKD set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MGRISKS set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MITRPT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MTGENOBJ set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_MTGENOBJH set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ORAEXT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ORGUSERS set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_PRMRULE set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_PRMVL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_ROLEVL set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SCHEDFORK set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SUPP_DET set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SUPP_HDR set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SUPP_TEXT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSCRACT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSCRACT set PVSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSHMAP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSRULE set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSSAPOBJ set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSTEM set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSTEMC set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSTEMT set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_SYSUSR set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_TEXTKEY set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_USRMAP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_XSRULEMAP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_XSRULEMAP set PVSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_XSRULEMAP set LVSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_XSYSGRP set VSYSKEY = 'RENAMED SYSTEM'
update SAP<SID>DB.VIRSA_CC_XSYSGRP set XVSYSKEY = 'RENAMED SYSTEM'

Query on Installation of GRC AC 5.3 RAR component

Similar Messages

Maybe you are looking for