CUP not pulling through Risks, linked to background jobs? GRC 5.3

[Former Member]

Hi guys,

I have an annoying problem in GRC CUP, I am trying to set up the "Create Request" function for our Company.

When I create a request for either a New User, or Change a User's Roles, then perform the Risk Analysis on this, the result is "0 Risk(s) found". I have added every single role in order to test, which should produce a risk, but still the same message.

I therefore thought OK, maybe the risks are not loaded into CUP, so I had a look in the configuration, namely the background jobs. The SOD Review and the UAR review jobs were not setup, so I scheduled them for every day, roughly every hour. However, this produces an error on the system log as follows:

2009-11-03 08:54:17,505 [Thread-8394] ERROR Service call exception; nested exception is:

* java.net.MalformedURLException: no protocol: 103*

java.rmi.RemoteException: Service call exception; nested exception is:

* java.net.MalformedURLException: no protocol: 103*

* at com.virsa.ae.service.ccSODUsers.ConfigVirsaCCSODViolatedUsersBindingStub.execSODUserAnalysis(ConfigVirsaCCSODViolatedUsersBindingStub.java:90)*

* at com.virsa.ae.service.ccSODUsers.ConfigVirsaCCSODViolatedUsersBindingStub.execSODUserAnalysis(ConfigVirsaCCSODViolatedUsersBindingStub.java:99)*

* at com.virsa.ae.sodreview.SODReviewUserHandler.insertUsers(SODReviewUserHandler.java:123)*

* at com.virsa.ae.sodreview.SODReviewUserHandler.execute(SODReviewUserHandler.java:59)*

* at com.virsa.ae.sodreview.SODReviewBGTask.execute(SODReviewBGTask.java:69)*

* at com.virsa.ae.backgroundjobs.BackgroundTask.run(BackgroundTask.java:51)*

* at java.util.TimerThread.mainLoop(Timer.java:461)*

* at java.util.TimerThread.run(Timer.java:408)*

Caused by:

java.net.MalformedURLException: no protocol: 103

* at java.net.URL.<init>(URL.java:568)*

* at java.net.URL.<init>(URL.java:465)*

* at java.net.URL.<init>(URL.java:414)*

* at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.createHTTPSocket(HTTPTransport.java:110)*

* at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getRequestStream(HTTPTransport.java:319)*

* at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:550)*

* at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1433)*

* at com.virsa.ae.service.ccSODUsers.ConfigVirsaCCSODViolatedUsersBindingStub.execSODUserAnalysis(ConfigVirsaCCSODViolatedUsersBindingStub.java:83)*

* ... 7 more*

Can anyone point me in the right direction as what could be the problem here?

Very much appreciated!! Cheers

[koehntopp · Accepted solution]

It seems that your risk analysis web service setup in CUP is wrong.

Can you post the URLs and other settings for risk analysis in CUP?

Oh, and this has nothing to do with SOD and UAR review - those jobs do not need to be scheduled for risk analysis to work, certainly not every hour....

Edited by: Frank Koehntopp on Nov 3, 2009 11:28 AM

[Former Member]

Yes, there's a Full Background sync every night in RAR for all systems, user and role sync etc.

OK, I better quit and raise a note to support, hopefully they will come back soon, I have an Audit in 2 weeks

Thanks for your help guys!! Cheers

[Former Member]

Hi Frank,

OK, I followed your advise, as expected the simulation in RAR shower 54000 risks, a mixture of low, medium and high.

This was because I was trying to add 30 roles, so expected a lot of risks.

I then checked the Connectors in RAR to the ones in CUP, they match identical, however, one thing I noticed is in RAR there

are SAP adapters for all the systems apart from Solution manager, is that right? If not, where would I create them?

Cheers

[koehntopp]

OK, so the issue is somewhere on the web service level....

Maybe you really should open the system and let support look into it, way easier than doing it here.

One more thing: you did run a role / user sync for that system in RAR, so RAR knows these roles?

The SAP Adapter is basically an RFC server that will allow ABAP systems to connect to RAR for risk analysis, either through Risk Terminator or through Superuser Privilege Management.

Look into the SPM configuration manual for details on how to set that up.

Frank.

[Former Member]

OK, silly mistake re the initial password of the GRC_USER.

Although I have reset it, I seem to have different passwords in the 4 different systems DE1, QE1, PE1 and SOLMAN.

However, I have tested all the connectors and they are happy.

I ran the process again, back to the first problem, "0 risks found".

Status log shows:

2009-11-04 11:51:53,438 [SAPEngine_Application_Thread[impl:3]_23] ERROR java.lang.VerifyError:

com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;

java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;

2009-11-04 11:51:53,439 [SAPEngine_Application_Thread[impl:3]_23] ERROR Exception during EJB call, Ignoring and trying

Webservice Call

com.virsa.ae.service.ServiceException: Exception in getting the results from the EJB service :

com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;

Caused by:

java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis

(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;

Can someone explain to me why I cant see the RAR>CC that you talked about earlier please?

[koehntopp]

RAR (Risk Analysis and Remediation) is the new name for what used to be called CC (ComplianceCalibrator)

So, go to RAR, Informer, User Analysis.

There you can do a simulation of adding roles to a user and perform risk analysis.

Also, please follow Alpesh's suggestion and check if your connector name is identical in RAR and CUP (that's what the web service uses to tell RAR which system to analyze in).

The "invalid content type" is usually the web service trying to tell you that your password is either wrong or initial.

Frank.

[Former Member]

Hi again, new day, more stress

OK, this morning I have tried Sabita's recommendations:

Port is correct, all of our GRC system runs on port 54000.

Replaced GRC_USER account with mine and ran process again, received following error:

2009-11-04 09:12:11,563 [SAPEngine_Application_Thread[impl:3]_36] ERROR java.lang.VerifyError:

com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;

java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;

so then checked GRC_USER in Solution manager > Has SAP_ALL. Checked in Netweaver > Has ALL Roles added to him.

Changed in Webservice back to GRC_USER, ran process again and received a different error this time:

2009-11-04 09:15:21,844 [SAPEngine_Application_Thread[impl:3]_26] ERROR java.rmi.RemoteException: Service call exception; nested exception is:

java.lang.Exception: Incorrect content-type found 'text/html'

java.rmi.RemoteException: Service call exception; nested exception is:

java.lang.Exception: Incorrect content-type found 'text/html'

STRANGE?

OK, then finally did Frank and Alpesh's suggestion, however I am stuck. In GRC>RAR Module, I have no CC option, what is this?

I have Informer, Rule Architect, Mitigation, Alert Monitor, Configuration. Certainly nothing to do with Simulation when adding roles, is this the problem?

Cheers

Edited by: Ben Neesom on Nov 4, 2009 9:27 AM

Edited by: Ben Neesom on Nov 4, 2009 9:27 AM

[Former Member]

Hi Ben,

Please check these threads also, may be of any help.

Change the user webservice to type service and check that is is logging successfully before putting in URL.

Regards,

Sabita

[Former Member]

Hi Frank,

I'm not 100% sure what you mean about the Simulation.

The CCF* roles that I am tryin to add to a new user, all have risks associated with them. I can see this in RAR if I go to Informer>Management View>Role Level.

Therefore I would expect these risks to be pulled through into CUP when I add the roles, am I missing something?

Cheers

[Former Member]

Ben,

I totally agree with Frank. There is no reason to check other things like JCo, SAP Adapater, background jobs etc. You need to make sure that the webservice communication works correctly. The management reports on the roles may be older or it may be showing roles with mitigated risks as well depending upon your configuration. Go to RAR/CC and run the simulation on this particular user with those roles from the CUP request. If you are finding the violation in RAR then there is some issue with the webservice communcation between CUP and RAR. IS the connector name exactly same in CUP and RAR? Look at the OSS Note # 1085586 and 1296632.

Alpesh

[Former Member]

Hi Ben,

Although all have given same suggestions, still I would request you to check webservice and port number of url. The port you have given is 54000, which seems odd. Additionally you can try IP address instead of domain name in url.

1. Check the port.

2. If the port is correct, try one thing. Put any other user ID instead of webuser and save password and log off the screen.

3. Check webuser has all authorizations(e.g. it is super user for CUP,ERM and RAR)

4. Go to CUP, change the url user ID and password again to this super user(webservice)

This is due to the reason that password encryption method was changed after patch 7 and sometimes earlier saved password doesn't work well.

If you have already reset the password after patch7 in given url, then this step is not of any help.

Regards,

Sabita

[Former Member]

Hi, OK, I have done as suggested, however the log is huge. I will paste some sections of the log relating to ther Risk Analysis. there's an error at the bottom relating to EJB?

2009-11-03 14:32:10,364 [SAPEngine_Application_Thread[impl:3]_32] DEBUG AEFrameworkServlet.java@531:logRequest() : role_action_PE1CLNT100!#!KEY!#!1480!#!KEY!#!CCF-S:BSCU_CUSTOMIZATION_DISP!#!KEY!#!0:0::ADD#

2009-11-03 14:32:10,364 [SAPEngine_Application_Thread[impl:3]_32] DEBUG AEFrameworkServlet.java@531:logRequest() : role_validto_PE1CLNT100!#!KEY!#!1481!#!KEY!#!CCF-S:BSCU_MAINT_NO_RANGES!#!KEY!#!0_display:0::12/31/9999#

2009-11-03 14:32:10,400 [SAPEngine_Application_Thread[impl:3]_32] DEBUG NavigationEngine.java@85:execute() : Current Module: |AE| Conversation: |cnvCreateRequest| Screen: |scrRequestDetails|

2009-11-03 14:32:10,401 [SAPEngine_Application_Thread[impl:3]_32] DEBUG NavigationEngine.java@105:execute() : Module#AE#Conversation#cnvCreateRequest#Screen#scrRequestDetails#Action#loadSODAnalysis#

2009-11-03 14:32:10,401 [SAPEngine_Application_Thread[impl:3]_32] DEBUG NavigationEngine.java@261:execute() : Handler found:class com.virsa.ae.accessrequests.actions.UpdateRequestDetailsAction

2009-11-03 14:32:10,418 [SAPEngine_Application_Thread[impl:3]_32] DEBUG RoleValidityHelper.java@157:isExpiredAsOfToday() : INTO the method : dt : Fri Dec 31 00:00:00 CET 9999

2009-11-03 14:32:10,418 [SAPEngine_Application_Thread[impl:3]_32] DEBUG RoleValidityHelper.java@167:isExpiredAsOfToday() : OUT of the method : boolResult : false

2009-11-03 14:32:10,440 [SAPEngine_Application_Thread[impl:3]_32] DEBUG NavigationEngine.java@272:execute() : Target returned by execute action: success

2009-11-03 14:32:10,441 [SAPEngine_Application_Thread[impl:3]_32] DEBUG AEFrameworkServlet.java@452:service() : forwarding to:scrRiskAnalysis.load.do

2009-11-03 14:32:10,441 [SAPEngine_Application_Thread[impl:3]_32] DEBUG AEFrameworkServlet.java@515:logRequest() :

2009-11-03 14:32:12,818 [SAPEngine_Application_Thread[impl:3]_32] DEBUG RequestDetailsHelper.java@731:isRiskAnalysisEligible() : Prov Action is eligible for Risk Analysis : CHANGE_USER

2009-11-03 14:32:12,818 [SAPEngine_Application_Thread[impl:3]_32] DEBUG RequestDetailsHelper.java@739:isRiskAnalysisEligible() : OUT of the method : boolEligible : true

2009-11-03 14:32:12,847 [SAPEngine_Application_Thread[impl:3]_32] DEBUG RiskAnalysisBO.java@130:findViolations() : Starting Risk analysis.....

2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] DEBUG RiskAnalysisBO.java@140:findViolations() : RiskAnalysis________ DAO level System : PE1CLNT100

2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] DEBUG RiskAnalysisBO.java@141:findViolations() : RiskAnalysis________ Include Cross System : PE1CLNT100

2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] INFO SystemDAOFactory.java@73:getRiskAnalysisDAO() : EN

2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] INFO SystemDAOFactory.java@74:getRiskAnalysisDAO() : Locale ID is :1

2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] INFO SystemDAOFactory.java@75:getRiskAnalysisDAO() : Locale date time format is :MM/dd/yyyy HH:MM:SS

2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] DEBUG AECacheUtil.java@882:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1

2009-11-03 14:32:12,848 [SAPEngine_Application_Thread[impl:3]_32] DEBUG SAPConnectorUtils.java@600:getConnectorInformation() : INTO the method : connectorId :PE1CLNT100

2009-11-03 14:32:12,850 [SAPEngine_Application_Thread[impl:3]_32] INFO com.virsa.ae.service.sap.SystemDAOFactory : getRiskAnalysisDAO() : : cc version : 5.3_WS

2009-11-03 14:32:12,850 [SAPEngine_Application_Thread[impl:3]_32] INFO com.virsa.ae.service.sap.SystemDAOFactory : getRiskAnalysisDAO() : : risk analysis dao is set to RiskAnalysisWS52DAO

2009-11-03 14:32:12,850 [SAPEngine_Application_Thread[impl:3]_32] INFO com.virsa.ae.service.sap.SystemDAOFactory : getRiskAnalysisDAO() : : cc uri : http://cvifxpsol.ks.franke.world:54000/VirsaCCRiskAnalysisService/Config1?wsdl&style=document

2009-11-03 14:32:12,850 [SAPEngine_Application_Thread[impl:3]_32] DEBUG SystemDAOFactory.java@221:getRiskAnalysisDAO() : OUT of the method

2009-11-03 14:32:12,857 [SAPEngine_Application_Thread[impl:3]_32] DEBUG RiskAnalysisBO.java@158:findViolations() : RiskAnalysis________ Visible Roles : [com.virsa.ae.accessrequests.po.RolesPO@200f200f[system=PE1CLNT100,systemShortDesc=Production System PE1 - 100,accessType=Select,searchValue=,roleProfName=0,roleProfDispName=CCF-G_BC_BASIS_ADMIN,roleProfDesc=Competence Centre System Administrator,roleProfType=C,roleApproverId=NB014,roleApproverName=Ben Neesom(NB014),roleCriticalLevel=,reqPathId=,status=OPEN,oldStatus=OPEN,actionFlag=ADD,validFrom=11/03/2009,validTo=12/31/9999,selected=true,isReadOnly=false,isNew=true,expanded=true,isSimpleRole=false,isRiskAnalysisonAccessChanged=false,isEditable=true,isApplicable=false,altRoleApproverId=,detailDesc=,reaffirmPeriod=0,isLead=false,lastReaffirmDate=,funcArea=,roleIndex=0,companydesc=,fucntionalAreaDesc=,isExistingRole=false,roleProfIndicator=R,comments=,validityType=NO,actualDate=,years=0,months=0,days=0,URL=,customBAPI=,responsibilityId=0,commentsMandatory=No

2009-11-03 14:32:14,401 [SAPEngine_Application_Thread[impl:3]_32] ERROR java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;

java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;

at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)

at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)

at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)

at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:511)

at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)

at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)

at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)

at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)

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.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:455)

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:219)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

2009-11-03 14:32:14,402 [SAPEngine_Application_Thread[impl:3]_32] ERROR Exception during EJB call, Ignoring and trying Webservice Call

com.virsa.ae.service.ServiceException: Exception in getting the results from the EJB service : com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;

at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:295)

at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)

at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:511)

at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)

at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)

at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)

at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)

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.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:455)

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:219)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Caused by:

java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;

at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)

at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)

... 28 more

2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG RiskAnalysisWS53DAO.java@632:determineRisks() : OUT of the method : com.virsa.ae.service.sap.dto.RiskWithCriticalActionsDTO@deb0deb[listRisks=[],listCriticalActions=[]]

2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG RiskAnalysisBO.java@190:findViolations() : RiskAnalysis___ Completd successfully!

2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG RiskAnalysisBO.java@221:findViolations() : RiskAnalysis________ Risk List Size : 0

2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG RiskAnalysisBO.java@225:findViolations() : RiskAnalysis________ Critical Actions Size : 0

2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] DEBUG RiskAnalysisBO.java@227:findViolations() : Done Risk analysis.

2009-11-03 14:32:15,502 [SAPEngine_Application_Thread[impl:3]_32] INFO MessagingHelper.java@99:addMessage() : @@@Adding msgValue: Code: 2200; Locale: en

2009-11-03 14:32:15,503 [SAPEngine_Application_Thread[impl:3]_32] INFO MessagingHelper.java@109:addMessage() : @@@Creating new message list

2009-11-03 14:32:15,503 [SAPEngine_Application_Thread[impl:3]_32] INFO MessagingHelper.java@119:addMessage() : Adding msg to msglist

2009-11-03 14:32:15,503 [SAPEngine_Application_Thread[impl:3]_32] DEBUG NavigationEngine.java@272:execute() : Target returned by execute action: success

2009-11-03 14:32:15,503 [SAPEngine_Application_Thread[impl:3]_32] DEBUG AEFrameworkServlet.java@452:service() : forwarding to:/sod_analysis.jsp

2009-11-03 14:32:15,519 [SAPEngine_Application_Thread[impl:3]_32] DEBUG PopupCalendarTag.java@180:doStartTag() : Date Format in PopUpCalendar Java :- M/d/yyyy

[koehntopp]

OK, no idea what that verify error means, but analysis seems to finish properly:

Risk List Size : 0

Can you please go to RAR and simulate that request for the user, and see if it comes up with risks there?

Frank.

[Former Member]

Hi Frank, yes I get "0 risks detected" on the CUP Create Request form, then when I look in the system log I get the following:

2009-11-03 12:09:46,165 [SAPEngine_Application_Thread[impl:3]_4] ERROR java.lang.VerifyError:

com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO; java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO; at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305) at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277) at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419) at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:511) at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103) at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182) at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073) at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300) at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109) at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271) at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425) 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.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:455) 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:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

[koehntopp]

OK, two more checks:

- switch log level to DEBUG in Configuration - Miscellaneous and try again. Maybe you have something more detailed (I'm sure there's more around this message)

- does your web service user have the correct UME roles assigned...?

Frank.

[Former Member]

Hi Vit, that's exactly what I have

Edited by: Ben Neesom on Nov 3, 2009 1:36 PM

[koehntopp]

Guys, please let's concentrate on the issue at hand.

- the risk analysis URI seems to be fine, user too

- That means we need to check if we also get no risks if we do the same request as a simulation in RAR

First of all, back to my last question: do you just get "No risks detected", or is there any error message when you do risk analysis (on the screen or in the log)?

What we do NOT need to check:

- UAR and SOD jobs - different functionalities

- Risk and RE exit URIs - different functionality

Please first check if the same risk analysis (i.e. simulation) in RAR delivers a correct result, if it does we can check why it does not get to CUP.

No confusing stuff, please

[Former Member]

Sorry it seems I cant post the results of the url link as it's XML, will try again:

?xml version="1.0" encoding="UTF-8" ?

Generated by WSDLDefinitionsParser

wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="AEWFExitServiceWS_5_2Wsd" targetNamespace="urn:AEWFExitServiceWS_5_2Wsd" xmlns:bns0="urn:AEWFExitServiceWS_5_2Wsd/Config1/document" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

wsdl:import location="http://cvifxpsol.ks.franke.world:54000/VirsaCCWFExitService5_2Service/Config1/bindings?wsdl&style=document" namespace="urn:AEWFExitServiceWS_5_2Wsd/Config1/document" /

wsdl:service name="VirsaCCWFExitService5_2Service"

wsdl:port name="Config1Port_Document" binding="bns0:Config1Binding"

soap:address location="http://cvifxpsol.ks.franke.world:54000/VirsaCCWFExitService5_2Service/Config1?style=document" /

/wsdl:port

/wsdl:service

/wsdl:definitions

[Former Member]

Check CUP >> Config >> Miscellaneous

In config manual they somehow switched order of two services. It is easy to overlook.

RE should be "http://cvifxpsol.ks.franke.world:54000/AEWFExitServiceWS_5_2/Config1?wsdl&style=document "

RISK should be "http://cvifxpsol.ks.franke.world:54000/VirsaCCWFExitService5_2Service/Config1?wsdl&style=document "

Cheers,

Vit

Edited by: Vit Vesely on Nov 3, 2009 1:32 PM

[Former Member]

Hi,

The webservice URL is:

http://cvifxpsol.ks.franke.world:54000/VirsaCCRiskAnalysisService/Config1?wsdl&style=document

Do you know how I can test this? When I paste into browser I get the following:

<?xml version="1.0" encoding="UTF-8" ?>

- <!-- Generated by WSDLDefinitionsParser

-->

- <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="AEWFExitServiceWS_5_2Wsd" targetNamespace="urn:AEWFExitServiceWS_5_2Wsd" xmlns:bns0="urn:AEWFExitServiceWS_5_2Wsd/Config1/document" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">

<wsdl:import location="http://cvifxpsol.ks.franke.world:54000/VirsaCCWFExitService5_2Service/Config1/bindings?wsdl&style=document" namespace="urn:AEWFExitServiceWS_5_2Wsd/Config1/document" />

- <wsdl:service name="VirsaCCWFExitService5_2Service">

- <wsdl:port name="Config1Port_Document" binding="bns0:Config1Binding">

<soap:address location="http://cvifxpsol.ks.franke.world:54000/VirsaCCWFExitService5_2Service/Config1?style=document" />

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

Does this look correct?

The latest error message I have is as follows:

2009-11-03 13:06:23,959 [SAPEngine_Application_Thread[impl:3]_37] ERROR Requested navigation control not found

com.virsa.ae.commons.utils.framework.ControlNotFoundException: Action not found - linkConfigRiskAnalysis

at com.virsa.ae.commons.utils.framework.ScreenDefn.getActionDefn(ScreenDefn.java:141)

at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:131)

at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)

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:219)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

[Former Member]

Check your Web service URI...

[Former Member]

Hi guys,

OK, the Adapters were grey, which is strange as I checked them last week and they were green. I restarted them and tried again, no luck, same error.

Re the port, I have tried with 50400, no luck. I also pasted the link into my browser, and the 54000 returned an xml link, whereas the 50400 returned nothing, so I think thats correct??

Lastly, I ran the Risk Analysis and looked at the log, I have the following error message:

2009-11-03 12:09:46,165 [SAPEngine_Application_Thread[impl:3]_4] ERROR java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;

java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;

at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)

at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)

at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)

at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:511)

at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)

at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)

at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)

at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:425)

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.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:455)

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:219)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Again, many thanks for your help guys, cheers!!

[former_member771067]

Hi Ben,

There might be so many reason. Please check your JCO is working fine or not and also from: RAR->configuration-> SAP Adaptor, check whether the adopter is grey or green. If it's grey please click on that to turn it green.

Other things need to be checked are the configuration settings in CUP (web service setup).

Regards,

Gurugobinda

[koehntopp]

The CUP configuration looks ok (if the instance of the RAR system is 40).

Can you go to RAR and do a simulation of the access request there?

The error message you posted is from the (irrelevant) background job. Maybe you can look at the log file again immediately after you do risk analysis - do you get an error there, or just "No risks found"?

[Former Member]

Hi Frank, many thanks for your quick reply!!

OK, in CUP > Risk Analysis I have the following settings:

RISK ANALYSIS. Default Analysis Type=Permission Level. Consider Mitigation Controls=TRUE

Version 5.3 webservice

URL=http://cvifxpsol.ks.franke.world:54000/VirsaCCRiskAnalysisService/Config1?wsdl&style=document

Username=GRC_USER (This is not locked and password has been confirmed)

Perform Org.User Analysis=FALSE

Perform Risk Analysis on Request=TRUE

[Former Member]

Are you positive on port 54000? Not 50400?

[former_member771067]

Hi Ben,

For webservice url please follow the sap Note No: 1279722.

I hope it'll help. Also check the port number as suggested by Vit.

Regards,

Gurugobinda