Risk Analysis in AE 5.2

hi,
Here is an other issue we have implementing AE:
When you create a request, if you add a role to the request and proceed to a risk analysis, we have an error message:
Failed to perform Risk Analysis. Reason: Service call exception; nested exception is: java.net.SocketTimeoutException: Read timed out
But if you do not add a role creating your request it s ok.
Just for info, we have exactly the same problem in RE.
About configuration
we created a "virsa" user with cc admin role and url is http: //server:50000/VirsaCCRiskAnalysisService/Config1?wsdl&style=document
Do we miss something?Thank you for your help!
Julien
Edited by: Julien LE GAL on Feb 29, 2008 11:31 AM

it is on the same host. how can we test access cc from ae?
no firewall, connection between re and ae is ok
about log i Don't really know which part to copy:
so here is the AE one:
2008-02-29 12:17:46,796 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :Please correct the following errors:paramNames :paramsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,797 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : INTO the method : 9601~en
2008-02-29 12:17:46,797 [SAPEngine_Application_Thread[impl:3]_18] INFO pStrKey :9601~en
2008-02-29 12:17:46,797 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : OUT of the method com.virsa.ae.dao.dto.MessageDTO@7f0b7f0b[code=9601,locale=en,type=error,desc=Please enter a valid value for,imgPath=images/messaging/error.gif,cssClassName=msg_error,paramNames=[]]
2008-02-29 12:17:46,798 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :Please enter a valid value forparamNames :paramsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,798 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : INTO the method : 9602~en
2008-02-29 12:17:46,799 [SAPEngine_Application_Thread[impl:3]_18] INFO pStrKey :9602~en
2008-02-29 12:17:46,799 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : OUT of the method com.virsa.ae.dao.dto.MessageDTO@7f977f97[code=9602,locale=en,type=error,desc=Please select a valid option for,imgPath=images/messaging/error.gif,cssClassName=msg_error,paramNames=[]]
2008-02-29 12:17:46,800 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :Please select a valid option forparamNames :paramsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,800 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : INTO the method : 9624~en
2008-02-29 12:17:46,800 [SAPEngine_Application_Thread[impl:3]_18] INFO pStrKey :9624~en
2008-02-29 12:17:46,800 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : OUT of the method com.virsa.ae.dao.dto.MessageDTO@b940b94[code=9624,locale=en,type=error,desc=Please enter a valid \"#_!FIELD_NAME#_!\".,imgPath=images/messaging/error.gif,cssClassName=msg_error,paramNames=[FIELD_NAME]]
2008-02-29 12:17:46,801 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :Please enter a valid \"#_!FIELD_NAME#_!\".paramNames :FIELD_NAMEparamsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,801 [SAPEngine_Application_Thread[impl:3]_18] INFO desc isPlease enter a valid \"#_!FIELD_NAME#_!\".
2008-02-29 12:17:46,801 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : INTO the method : 9625~en
2008-02-29 12:17:46,801 [SAPEngine_Application_Thread[impl:3]_18] INFO pStrKey :9625~en
2008-02-29 12:17:46,802 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : OUT of the method com.virsa.ae.dao.dto.MessageDTO@c290c29[code=9625,locale=en,type=error,desc=Please enter a valid \"#_!FIELD_NAME#_!\". Only digits are allowed.,imgPath=images/messaging/error.gif,cssClassName=msg_error,paramNames=[FIELD_NAME]]
2008-02-29 12:17:46,802 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :Please enter a valid \"#_!FIELD_NAME#_!\". Only digits are allowed.paramNames :FIELD_NAMEparamsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,802 [SAPEngine_Application_Thread[impl:3]_18] INFO desc isPlease enter a valid \"#_!FIELD_NAME#_!\". Only digits are allowed.
2008-02-29 12:17:46,803 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : INTO the method : 9626~en
2008-02-29 12:17:46,803 [SAPEngine_Application_Thread[impl:3]_18] INFO pStrKey :9626~en
2008-02-29 12:17:46,803 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : OUT of the method com.virsa.ae.dao.dto.MessageDTO@cc40cc4[code=9626,locale=en,type=error,desc=Please enter a valid \"#_!FIELD_NAME#_!\".,imgPath=images/messaging/error.gif,cssClassName=msg_error,paramNames=[FIELD_NAME]]
2008-02-29 12:17:46,804 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :Please enter a valid \"#_!FIELD_NAME#_!\".paramNames :FIELD_NAMEparamsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,804 [SAPEngine_Application_Thread[impl:3]_18] INFO desc isPlease enter a valid \"#_!FIELD_NAME#_!\".
2008-02-29 12:17:46,804 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : INTO the method : 9627~en
2008-02-29 12:17:46,804 [SAPEngine_Application_Thread[impl:3]_18] INFO pStrKey :9627~en
2008-02-29 12:17:46,805 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : OUT of the method com.virsa.ae.dao.dto.MessageDTO@d590d59[code=9627,locale=en,type=error,desc=Please enter a valid \"#_!FIELD_NAME#_!\".,imgPath=images/messaging/error.gif,cssClassName=msg_error,paramNames=[FIELD_NAME]]
2008-02-29 12:17:46,805 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :Please enter a valid \"#_!FIELD_NAME#_!\".paramNames :FIELD_NAMEparamsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,805 [SAPEngine_Application_Thread[impl:3]_18] INFO desc isPlease enter a valid \"#_!FIELD_NAME#_!\".
2008-02-29 12:17:46,806 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : INTO the method : 9628~en
2008-02-29 12:17:46,806 [SAPEngine_Application_Thread[impl:3]_18] INFO pStrKey :9628~en
2008-02-29 12:17:46,806 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : OUT of the method com.virsa.ae.dao.dto.MessageDTO@dee0dee[code=9628,locale=en,type=error,desc=Please enter a valid \"#_!FIELD_NAME#_!\".,imgPath=images/messaging/error.gif,cssClassName=msg_error,paramNames=[FIELD_NAME]]
2008-02-29 12:17:46,807 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :Please enter a valid \"#_!FIELD_NAME#_!\".paramNames :FIELD_NAMEparamsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,807 [SAPEngine_Application_Thread[impl:3]_18] INFO desc isPlease enter a valid \"#_!FIELD_NAME#_!\".
2008-02-29 12:17:46,807 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : INTO the method : 9628~en
2008-02-29 12:17:46,807 [SAPEngine_Application_Thread[impl:3]_18] INFO pStrKey :9628~en
2008-02-29 12:17:46,807 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : OUT of the method com.virsa.ae.dao.dto.MessageDTO@dee0dee[code=9628,locale=en,type=error,desc=Please enter a valid \"#_!FIELD_NAME#_!\".,imgPath=images/messaging/error.gif,cssClassName=msg_error,paramNames=[FIELD_NAME]]
2008-02-29 12:17:46,808 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :Please enter a valid \"#_!FIELD_NAME#_!\".paramNames :FIELD_NAMEparamsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,808 [SAPEngine_Application_Thread[impl:3]_18] INFO desc isPlease enter a valid \"#_!FIELD_NAME#_!\".
2008-02-29 12:17:46,808 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : INTO the method : 9623~en
2008-02-29 12:17:46,808 [SAPEngine_Application_Thread[impl:3]_18] INFO pStrKey :9623~en
2008-02-29 12:17:46,809 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : OUT of the method com.virsa.ae.dao.dto.MessageDTO@aef0aef[code=9623,locale=en,type=error,desc=Please enter a valid \"#_!FIELD_NAME#_!\". Only Alpha-numeric, Space or Underscore characters are allowed.,imgPath=images/messaging/error.gif,cssClassName=msg_error,paramNames=[FIELD_NAME]]
2008-02-29 12:17:46,810 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :Please enter a valid \"#_!FIELD_NAME#_!\". Only Alpha-numeric, Space or Underscore characters are allowed.paramNames :FIELD_NAMEparamsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,810 [SAPEngine_Application_Thread[impl:3]_18] INFO desc isPlease enter a valid \"#_!FIELD_NAME#_!\". Only Alpha-numeric, Space or Underscore characters are allowed.
2008-02-29 12:17:46,810 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : INTO the method : 9622~en
2008-02-29 12:17:46,810 [SAPEngine_Application_Thread[impl:3]_18] INFO pStrKey :9622~en
2008-02-29 12:17:46,811 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : OUT of the method com.virsa.ae.dao.dto.MessageDTO@a540a54[code=9622,locale=en,type=error,desc=Please enter a valid name \"#_!FIELD_NAME#_!\" (Firstname Lastname).,imgPath=images/messaging/error.gif,cssClassName=msg_error,paramNames=[FIELD_NAME]]
2008-02-29 12:17:46,811 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :Please enter a valid name \"#_!FIELD_NAME#_!\" (Firstname Lastname).paramNames :FIELD_NAMEparamsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,811 [SAPEngine_Application_Thread[impl:3]_18] INFO desc isPlease enter a valid name \"#_!FIELD_NAME#_!\" (Firstname Lastname).
2008-02-29 12:17:46,812 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : INTO the method : 9630~en
2008-02-29 12:17:46,812 [SAPEngine_Application_Thread[impl:3]_18] INFO pStrKey :9630~en
2008-02-29 12:17:46,812 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : OUT of the method com.virsa.ae.dao.dto.MessageDTO@f220f22[code=9630,locale=en,type=error,desc=One AND ONLY one ROW must be selected,imgPath=images/messaging/error.gif,cssClassName=msg_error,paramNames=[]]
2008-02-29 12:17:46,813 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :One AND ONLY one ROW must be selectedparamNames :paramsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,813 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : INTO the method : 9629~en
2008-02-29 12:17:46,813 [SAPEngine_Application_Thread[impl:3]_18] INFO pStrKey :9629~en
2008-02-29 12:17:46,814 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : OUT of the method com.virsa.ae.dao.dto.MessageDTO@e9a0e9a[code=9629,locale=en,type=error,desc=No ROWS selected,imgPath=images/messaging/error.gif,cssClassName=msg_error,paramNames=[]]
2008-02-29 12:17:46,814 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :No ROWS selectedparamNames :paramsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,815 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : INTO the method : 9566~en
2008-02-29 12:17:46,815 [SAPEngine_Application_Thread[impl:3]_18] INFO pStrKey :9566~en
2008-02-29 12:17:46,815 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getMessage :   : OUT of the method com.virsa.ae.dao.dto.MessageDTO@6d0b6d0b[code=9566,locale=en,type=error,desc=Please correct the following errors:,imgPath=images/messaging/error.gif,cssClassName=msg_error,paramNames=[]]
2008-02-29 12:17:46,816 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.messaging.MessageFormatter : parseDesc :   : INTO the method : desc :Please correct the following errors:paramNames :paramsMap :{FIELD_NAME=#_!FIELD_NAME#_!}
2008-02-29 12:17:46,816 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getResourceBundle :   : INTO the method : en
2008-02-29 12:17:46,816 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getResourceBundle :   : INTO the method : en
2008-02-29 12:17:46,817 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getResourceBundle :   : INTO the method : en
2008-02-29 12:17:46,817 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getResourceBundle :   : INTO the method : en
2008-02-29 12:17:46,817 [SAPEngine_Application_Thread[impl:3]_18] DEBUG com.virsa.ae.service.cache.AECacheUtil : getResourceBundle :   : INTO the method : en
and the RE one:
2008-02-29 11:44:39,922 [SAPEngine_Application_Thread[impl:3]_30] ERROR java.rmi.RemoteException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
2008-02-29 11:44:39,922 [SAPEngine_Application_Thread[impl:3]_30] ERROR com.virsa.core.service.ServiceException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
2008-02-29 11:44:39,923 [SAPEngine_Application_Thread[impl:3]_30] ERROR com.virsa.re.role.actions.RiskAnalysisAction
com.virsa.core.BOException: Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out
     at com.virsa.re.bo.impl.RiskAnalysisBO.performTranLvlRiskAnalysis(RiskAnalysisBO.java:232)
     at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysis(RiskAnalysisBO.java:167)
     at com.virsa.re.role.actions.RiskAnalysisAction.performAndShowRiskAnalysis(RiskAnalysisAction.java:318)
     at com.virsa.re.role.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:80)
     at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:255)
     at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
     at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:215)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Similar Messages

Ad hoc Risk Analysis report is returning incorrect Risk Level for some Risks

We are running GRC AC 10.0 with SP 16. After application of Support Pack 16, some of our ad hoc risk analysis reports are returning incorrect risk levels. For example: Risk F024 Open closed periods and inappropriately post currency or tax entries is set as High. When the Ad hoc report is run, the risk F024 will show on a user with a level of Medium. We have generated our ruleset and have followed the normal procedures used to implement the support pack. Any ideas what is causing this issue? I have exhausted my knowledge and search attempts.
Any help is appreciated.
Sara B.

Hi Kevin
Many thanks for your post, we did run a full BRA but no luck unfortunately. Some Risks still reporting as Medium when they should be Critical or High. Oddly it is reporting correctly against some risks just not for all!
Cheers
Hussain

Issue with risk analysis report in GRC10.0

Hi All,
We are running the user risk analysis report from NWBC: Reports and Analytics -> Access Risk Analysis Reports -> User Risk Violation report.
This report is not fetching all the data even though user has all the required authorizations.
We are getting the data when we execute the dashboard reports.
Any one has idea?
Cheers
Hari

Alessandro,
Thanks for the reply. I am aware of this.
Problem is when dash board report is showing the risk for the user but risk anaylsis report in Reports and Analytics is not showing the risks to that user.
As per our investigation, the risk data that is displaying in the risk anaylsis report in Reports and Analytics is incomplete. We didn't find any errors in SLG1. Also there is no issues from authorizations side.
Regards
Hari

Mass role risk analysis issue

Hello GRC Community,
I have a following issue:
When I use mass risk analysis the deactivated authorization objects in the role are displayed as result. At the same time, when I use Role Level Risk Analysis the role with deactivated critical authorization objects doesnt appear.
Does anybody know how to solve this issue? Is there any configuration parameter to be adjusted?
thanks
best regards
Sabrina

Prasant,
here are the screenshots of the Job result:
1. Mass role Risk Analysis
2. Risk Analysis on the (Single) Role Level
Im Backend you can see that the role contains lots of deactivated autorization objects.
I have run all sync Jobs, but seemingly it doesnt help.
Thanks,
Sabrina

No result /report when weu00B4re running a risk analysis in background

Dear forum,
We are running several risk analysis in background (from configuration tab) and we cannot see any result
in the column called "result". However, when we run a offline analysis (from informer tab) we can see that the column "result" is containing a file.
Hope you can help us.
Thanks in advance.

Running risk analysis in background from the configuration tab does not produce a report by design. This background job is really just performing a system maintenence activity and is not intended for report generation. This background job preps data for performing offline analysis as well as the underlying data that supports the management reports in the informer tab (among other things). Generally, anything in the configuration tab is system maintenance related.
It sounds like you're attempting to perform typical analysis of end user access, not system maintenance activities. The informer tab is what you need to be using to perform the analysis.
Within the informer tab, whether you choose to perform online analysis or offline analysis, a report result is always generated. In my experience, there has not been a compelling reason to use offline analysis capabilities within the informer tab. Online analysis (real-time analysis of the SAP system rather than the offline data from the last configuration tab background risk analysis) is naturally always current, which is a plus.

CUP 5.3: risk analysis in workflow impossible due to web service performance?

Hello experts,
We are facing a huge challenge within a AC 5.3 implementation.
Here, AC has been used successfully with CUP and RAR for quite some time now. However, the RAR analysis has not yet been integrated into the CUP workflow. We would like to integrate the RAR analyis in CUP now.
Based on the existing role concept (that uses functional master roles and derived roles per company code, with ca. 30 company codes in place) and the shared service operations in some areas such as FI, there is a large number of users with many roles and consequently, many SoD risks (of course, they are all "repeat" risk per company code).
This leads to a long RAR analysis run time, but it's still acceptable. Analysis on permission level for such "power users" runs about 1 minute, on action level about 5-6 seconds.
However, the web service between RAR und CUP is a problem and cannot cope with our violations. We have currently set the threshold to 75000. In this case, the analysis + web service runs 1-2 minutes. However, we have some users with 200-300.000 violations. In this case, if we deactivate the threshold, we will experience a web service time-out eventually, even with analysis on action level because the amount of violations the web service has to process is the same (or even higher with some false positives).
We also have compensating controls in place for these power users, which will of course reduce the web service run-time considerably. However, this is not applicable to NEW user requests because for those, the compensating controls will be assigned only AFTER the risk analysis has taken place and the risk manager receives the workflow item.
Has anyone experienced this in the past and found a viable solution or work-around? We are basically short of options and considering dropping the project.
Note: An upgrade to 10.X is not (currently) a solution because this upgrade is scheduled and budgeted only for later.
Thanks a lot and best regards
Patrick

Any opinions on this?
Cheers and thanks
Patrick

Error while executing the Job for Objects :null Batch Risk Analysis

Hi All,
We've recently upgraded Virsa to version 5.3_14 . I'm encountering a problem when executing the Batch Risk Analysis job for users, roles and profiles. The job does not complete for some objects and it seems to be sporadic and shows this error: -
Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null
I've attached the log for your review.
Thanks in advance for your help.
Linda Lewis
Feb 9, 2011 1:47:53 PM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>
FINEST: ObjAuthMatcher constructed: 4ms, #singles=2141, #ranges=0, #super=0
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis
WARNING: Job ID:395 : Failed to run Risk Analysis
java.lang.StringIndexOutOfBoundsException at java.lang.String.substring(String.java:1019)
at com.virsa.cc.xsys.util.RuleLoader.getPermRule(RuleLoader.java:573)
at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1609)
at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:321)
at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1166)
at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1464)
at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:560)
at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:363)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)
at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)
at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
WARNING: Error: while executing BatchRiskAnalysis for JobId=395 and object(s):ABROWN: Skipping error to continue with next object: null Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
2@@Msg is Error while executing the Job for Object(s) :ABROWN:null
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO: -
Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
INFO: --- BKG User Permission Analysis (System: P20:020) completed --- elapsed time: 4522 ms
Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
Edited by: Linda Lewis on Feb 9, 2011 9:08 PM

Hi,
Was a solution found for this error?
Thanks,
Glen

Error while doing risk analysis for a user

Hi ,
When i did risk analysis at user level for a particular user we are getting this error under level ."Exception!!. No relavent language message available in database for :0292".I had reuploaded the the messages text file but still the error persists i have restarted the j2ee application but still the error is not going .any pointers please thanx in advance.When checked the file CC5.3_MESSAGES.txt it does not contain any entry corresponding to message code 0292.So how shud i proceed.
Edited by: Ambarish annapureddy on Jan 21, 2009 12:54 PM

Hi Ambarish,
What is the patch level of GRC AC 5.3? Did you apply any service pack recently? Did the service pack contain any message file? There has to be some message file which contains message '0292'. If you can not find the message file then open a message with SAP support and they should be able to provide it to you.
Regards,
Alpesh

Job Error- Batch Risk Analysis (Role Full Sync)

Hi Experts,
I have schedule the background job for Role analysis(Full Sync), but it gives an error- status error.
all connections are working fine and pasted the error log for your reference.
Oct 25, 2010 11:56:36 AM com.virsa.cc.common.util.ExceptionUtil logError
SEVERE: null
java.lang.NullPointerException
     at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthChgRoleInputElement.wdGetObject(IPublicBackendAccessInterface.java)
     at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
     at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:401)
     at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
     at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)
     at com.virsa.cc.comp.BackendAccessInterface.getAuthChangedRoles(BackendAccessInterface.java:3735)
     at com.virsa.cc.comp.BackendAccessInterface.getAuthChangedRoles(BackendAccessInterface.java:3724)
     at com.virsa.cc.comp.BackendAccessInterface.getObjDetails(BackendAccessInterface.java:1428)
     at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.getObjDetails(InternalBackendAccessInterface.java:4327)
     at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.getObjDetails(InternalBackendAccessInterface.java:4796)
     at com.virsa.cc.dataextractor.bo.DataExtractorSAP.getObjDetails(DataExtractorSAP.java:630)
     at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.getObjInfoFromSource(AnalysisEngine.java:4140)
     at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1754)
     at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:317)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1055)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1366)
     at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:559)
     at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:362)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)
     at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)
     at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
     at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Job ID:23 : Analysis done: T_00035951_H_IXOSCFGS elapsed time: 666 ms
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 23 Status: Error
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 23 Status: Error
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Detailed Analysis Time:
Risk Analysis Time: Started @:Mon Oct 25 11:56:36 EDT 2010
Rule Load Time: Started @:Mon Oct 25 11:56:36 EDT 2010
Rule Load Time:0millisec
Org Rule Loop Time: Started @:Mon Oct 25 11:56:36 EDT 2010
Rule Loop Time: Started @:Mon Oct 25 11:56:36 EDT 2010
Rule Loop Time:648millisec
Org Rule Loop Time:649millisec
Risk Analysis Time:686millisec
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis
INFO: Job ID:23 : Exec Risk Analysis
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Job ID:23 : Before Rules loading, elapsed time: 2 ms
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
INFO: Job ID:23 : Analysis starts: T_00035952_H_PMREAD_I
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1005
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1005
Oct 25, 2010 11:56:36 AM com.virsa.cc.common.util.ExceptionUtil logError
SEVERE: null
java.lang.NullPointerException
     at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthForRoleInputElement.wdGetObject(IPublicBackendAccessInterface.java)
     at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
     at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:401)
     at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
     at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)
     at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.executeBAPI(InternalBackendAccessInterface.java:4696)
     at com.virsa.cc.dataextractor.bo.DataExtractorSAP.getObjActions(DataExtractorSAP.java:213)
     at com.virsa.cc.dataextractor.bo.DataExtractorSAP.getObjActions(DataExtractorSAP.java:105)
     at com.virsa.cc.xsys.meng.MatchingEngine.getObjActions(MatchingEngine.java:813)
     at com.virsa.cc.xsys.meng.MatchingEngine.matchActRisks(MatchingEngine.java:121)
     at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1407)
     at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:317)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1055)
     at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1366)
     at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:559)
     at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:362)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)
     at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)
     at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)
     at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
     at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Oct 25, 2010 11:56:36 AM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>
FINEST: ObjAuthMatcher constructed: 0ms, #singles=27, #ranges=0, #super=0
Oct 25, 2010 11:56:37 AM com.virsa.cc.common.util.ExceptionUtil logError
Kindly do the needful.
Regards,
Arjun.

Hi,
1.Please check what type of connection is configuired in RAR(Adaptive RFC or SAPJCO). Please switch the connection type to SAPJCO.
2. Please check the daemon & daemon manager statues.
3. Check the Job threds in daemon manager after sechudeling job.
Regards,
Arjun.

Error while executing Batch Risk Analysis job in full sync mode

Hi Gurus,
I am getting following error while executing Batch Risk Analysis job in full sync mode for the first time, please help me out.
May 12, 2011 3:57:26 AM com.virsa.cc.multi.node.dao.NodeDAO deleteMTGenObjTable
INFO: In deleteMTGenObjTable() deleting from VIRSA_CC_MTGENOBJ for jobid = 100
May 12, 2011 3:59:53 AM com.virsa.cc.multi.node.dao.NodeDAO deleteMTGenObjTable
INFO: In deleteMTGenObjTable() deleting from VIRSA_CC_MTGENOBJ for jobid = 100
May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchSyncAndAnalysis
INFO: --- Batch Sync/Analysis/Mgmt Report completed --- elapsed time: 104907817 ms
May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 100 Status: Error
May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
2@@Msg is Error Job not completed
May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO: -
Background Job History: job id=100, status=2, message=Error Job not completed
May 12, 2011 3:59:53 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
INFO: -
Complted Job =>100----
May 12, 2011 3:59:53 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
INFO: Daemon idle time longer than RFC time out, terminating daemon [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0
May 12, 2011 3:59:53 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start
INFO: Analysis Daemon ID [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0 terminiated
May 12, 2011 4:00:35 AM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
FINEST: Analysis Daemon Thread: Invoking (HTTP): http://10.66.218.68:52100/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=[211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/.&threadId=0&daemonType=BG
May 12, 2011 4:01:36 AM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
FINEST: Analysis Daemon Thread: Invoking (HTTP): http://10.66.218.68:52100/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=[211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/.&threadId=0&daemonType=BG
May 12, 2011 4:02:37 AM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
FINEST: Analysis Daemon Thread: Invoking (HTTP): http://10.66.218.68:52100/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=[211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/.&threadId=0&daemonType=BG
May 12, 2011 4:02:37 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start
INFO: Analysis Daemon ID [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0 started
May 12, 2011 4:02:38 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start
FINEST: Another Analysis Daemon ID [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0 is already running

Hi,
May be it worked in your case How the job names going to affect the execution of the job. The issue is purely because of RFC timeout (As per the logs). I recommend to change the parameter in the configuration tab as recommended by Sunny in the previous thread.
Regards,
Raghu

Error while running risk analysis.

Hi,
I am facing problem, while running risk analysis from Access Enforcer for a particular application. Infact problem is for all the connectors. I have done required configuration.
Error i am getting is "Risk analysis failed: Exception from the service : Risk Analysis failed".
Please suggest.
Thanks in Advance.
Regards,
Pravin.

Problem was with JCO connection.

Getting "Risk Analysis Failed " error while raising request from IDM

Hi friends,
Some of the User to Role mapping requests from IDM did not reach CUP (request ID = null) . When noticed the VDS log , we found the error from GRC webservice to be Risk Analysis Failed . We thought it might be an RAR issue , however , the request just got through CUP when submitted from GRC webservice directly . From RAR perspective also, everything looks ok .
Please provide your thoughts as to whether this error is pertaining to some other issue or suggest me what I can check in Identity center to correct this .
Thanks in advance for your help .

The connector set up are all looking correct . However the requests are not getting raised in many cases .
At one point we identified that , since our SAP systems have been migrated to DB2, some of the systems were down .
So when the system is down we decided , Risk analysis is failing . however , now the systems are up and running and still the risk analysis is failing .

RAR: Error message while running role risk analysis.

Hi All,
We are implementing RAR 5.3. When running permission level risk analysis we get the following error message:
"Error while executing the Job:Cannot assign a blank-padded string to host variable 1.u201D
This happens only at permission level for just one single role and for all the composite roles that contain this one.
The rules were generated without any issue and we cannot find anything unusual on that particular single role.
Any ideas of what could be the cause of this error?

Hi Iliya:
Please find below the job log with the detailed error description:
Mon Dec 15 10:06:37 GMT-02:00 2008 : -----------------------Scheduling Job =>233---------------------------------------------------------------
Mon Dec 15 10:06:37 GMT-02:00 2008 : --- Starting Job ID:233 (RISK_ANALYSIS_ADHOC) - mm:user10
Mon Dec 15 10:06:37 GMT-02:00 2008 : ----------- Background Job History: job id=233, status=1, message=mm:user10 started
Mon Dec 15 10:06:37 GMT-02:00 2008 : Job ID:233 : Exec Risk Analysis
Mon Dec 15 10:06:37 GMT-02:00 2008 : Start Analysis Engine->Risk Analysis ..... memory usage: free=1571M, total=1962M
Mon Dec 15 10:06:38 GMT-02:00 2008 : Rule Loader Syskey => *
Mon Dec 15 10:06:38 GMT-02:00 2008 : No of Systems=1
Mon Dec 15 10:06:51 GMT-02:00 2008 : Action rules cache loaded: memory used in cache=56M, free=1512M, total=1962M
Mon Dec 15 10:06:51 GMT-02:00 2008 : Job ID:233 : Rules loaded, elapsed time: 13694 ms
Mon Dec 15 10:06:57 GMT-02:00 2008 : Job ID:233 :
Mon Dec 15 10:06:57 GMT-02:00 2008 : Job ID:233 : Analysis starts: MM:USER10
Mon Dec 15 10:07:16 GMT-02:00 2008 : Auth Map cache reloaded successfully
Mon Dec 15 10:07:32 GMT-02:00 2008 : Cannot assign a blank-padded string to host variable 1.com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
com.sap.sql.types.VarcharResultColumn.setString(VarcharResultColumn.java:66)
com.sap.sql.jdbc.common.CommonPreparedStatement.setString(CommonPreparedStatement.java:511)
com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setString(PreparedStatementWrapper.java:355)
com.virsa.cc.xsys.util.ObjTextReader.lookupByKey(ObjTextReader.java:353)
com.virsa.cc.xsys.util.ObjTextReader.getFieldValueDesc(ObjTextReader.java:261)
com.virsa.cc.xsys.riskanalysis.AnalysisEngine.insertPermReportLines(AnalysisEngine.java:2286)
com.virsa.cc.xsys.riskanalysis.AnalysisEngine.outputPermissionViolation(AnalysisEngine.java:1858)
com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1182)
com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:243)
com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:207)
com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:305)
com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:183)
com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:154)
com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:81)
com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:434)
com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1223)
com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:480)
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
java.security.AccessController.doPrivileged(Native Method)
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Mon Dec 15 10:07:32 GMT-02:00 2008 : Cannot assign a blank-padded string to host variable 1.com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:309)
com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:183)
com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:154)
com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:81)
com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:434)
com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1223)
com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:480)
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
java.security.AccessController.doPrivileged(Native Method)
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Mon Dec 15 10:07:32 GMT-02:00 2008 : Job ID: 233 Status: Error
Mon Dec 15 10:07:32 GMT-02:00 2008 : ----------- Background Job History: job id=233, status=2, message=Error while executing the Job:Cannot assign a blank-padded string to host variable 1.
Mon Dec 15 10:07:32 GMT-02:00 2008 : -----------------------Complted Job =>233---------------------------------------------------------------
Regards.
Leandro.

Error while performing Risk Analysis at user level for a cross system user

Dear All,
I am getting the below error, while performing the risk analysis at user level for a cross system (Oracle) user.
The error is as follows:
"ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 120 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine), 2) The pool size of adapter "SAPJ2EDB" is not enough according to the current load of the system or 3) The specified time to wait for connection is not enough according to the pool size and current load of the system. In case 1) the solution is to check for cached connections using the Connector Service list-conns command, in case 2) to increase the size of the pool and in case 3) to increase the time to wait for connection property. In case of application thread, there is an automatic mechanism which detects unclosed connections and unfinished transactions.RC:1
Can anyone please help.
Regards,
Gurugobinda

Hi..
Check the note # SAP Note 1121978
SAP Note 1121978 - Recommended settings to improve peformance risk analysis.
Check for the following...
CONFIGTOOL>SERVER>MANAGERS>THREADMANAGER
ChangeThreadCountStep =50
InitialThreadCount= 100
MaxThreadCount =200
MinThreadCount =50
Regards
Gangadhar

Risk Analysis Failing in ERM 5.3

Hi All -
I would appreciate some assistance with pin-pointing an issue that I'm having with running Risk Analysis on roles in ERM. Currently I have RAR configured with the appropriate rule set and generating the expected risk/sod conflicts for users & roles. I have also added the appropriate Web Service Info. in th Misc section under the configuration tab (url, user, pwd) for all sections associate with RAR integration.
Now when I run a risk analysis on a particular role in RAR i get the correct conflicts however when I get the Risk Analysis stage with ERM I receive the following Error:
Risk analysis failed; Cannot assign NULL to host variable 5. setNull() can only be used if the corresponding column is nullable. The statement is "INSERT INTO VT_RE_RSK_OBJRULES (OBJCODE, OBJDESC, OBJFLDCODE, OBJFLDDESC, VALFRMID, VALTOID, COND, RSKVIOLID) VALUES(?, ?, ?, ?, ?, ?, ?, ?)".
I also get this error when trying to run Mass Maintenance --> Risk Analysis:
Risk anaysis for role "XX:XXXXX" failed
Before I was getting error: "Risk Analysis performed successfully; No Risk Found" so I referenced SAP Note 1265964 and applied all solution steps.
Lastly here is the error log:
2010-01-14 14:59:28,768 [SAPEngine_Application_Thread[impl:3]_31] ERROR com.virsa.re.role.actions.RiskAnalysisAction
java.lang.Throwable: Cannot assign NULL to host variable 5. setNull() can only be used if the corresponding column is nullable. The statement is "INSERT INTO VT_RE_RSK_OBJRULES (OBJCODE, OBJDESC, OBJFLDCODE, OBJFLDDESC, VALFRMID, VALTOID, COND, RSKVIOLID) VALUES(?, ?, ?, ?, ?, ?, ?, ?)".
     at com.virsa.re.bo.impl.RiskAnalysisBO.saveObjViolations(RiskAnalysisBO.java:906)
     at com.virsa.re.bo.impl.RiskAnalysisBO.performObjLvlRiskAnalysis(RiskAnalysisBO.java:824)
     at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysisOnSystem(RiskAnalysisBO.java:214)
     at com.virsa.re.role.actions.RiskAnalysisAction.performRiskAnalysisOnMultipleRoles(RiskAnalysisAction.java:609)
     at com.virsa.re.role.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
     at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:273)
     at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:286)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
     at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Any help would be greatly appreciate it - Thanks in Advance!

GOing to repost

AC 5.3 Risk Analysis to SRM 7.0

Hi SAP experts.
I would like to know if its posible to execute a Risk Analysis through a SRM 7.0 module, and instead of transacctions if it is posible to use the webdynpro links like actions or tcodes.
My doubt is based on the fact that in SRM 7.0 the proper tcodes like BPP* are not use in this release, and these are changed by webdynpro links. Is it possible to use that links as tcodes for the SoD Matrix?
Thanks in advance.
Regards.

Hi Kunal.
Firstly, thanks a lot for your support.
In addition, I know that with the previous release of SRM, is posible to conect SAP GRC AC with SRM. But if I create a conector like to a SAP system from GRC to SRM, do you think that is imposible to associate that kind of webdynpro links as an AC action?
On the other hand, instead of create a conector SAP, I create a conector, like a NON SAP system from GRC to SRM, could be this a possible way to match Access control actions with SRM webdynpro links?.
And finally, is possible to execute a RAR analysis to a posible Cross-System between ECC and ERM (configured as NON SAP system)?
Thanks in advance.
Regards.

Risk Analysis in AE 5.2

Similar Messages

Maybe you are looking for