RAR interaction with CUP is not working correctly

Former Member · ‎05-26-2010

Hi all,

Curently we are migrating from AC 5.2 to 5.3 SP11. Togehter with the migration we want to integrate RAR into our existing workflow processes. At the moment the risk analysis is not working as we want. The risk analysis is executed at the line manager stage. We get the results back from RAR but as soon we want to approve the request to send it to the detour path for SOD cleanup we get a internal server error. If we change the configuration to risk analysis on request level we get the error immediately after we send out the request.

Connector Set Up:

RAR:

System: RIC_001

System Name: RIC_001

CUP:

Name: RIC_001

Short Description: RIC_001

The Web Service User has a productive password and all required roles are assigned.

CUP exit URI`s

http://chwias2383:50000/VirsaCCWFExitService5_2Service/Config1?wsdl&style=document

RAR Work Flow Sercive URI

http://chwias2383:50000/AEWFRequestSubmissionService_5_2/Config1?wsdl&style=document

Log File:

2010-05-25 16:51:30,583 [SAPEngine_Application_Thread[impl:3]_2] ERROR Exception during EJB call, Ignoring and trying Webservice Call

com.virsa.ae.service.ServiceException: Exception in getting the results from the EJB service : loader constraints violated when linking com/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO class

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

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

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

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

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

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

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

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)

Caused by: java.lang.LinkageError: loader constraints violated when linking com/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO class

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

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

... 28 more

Has annyone a idea what we can try to change in our set up before we open a oss call?

Many thanks for your help!

Regards Jeffrey

Former Member · ‎07-20-2010

Hi Experts

Many thanks for your support. It was finaly a configuration issue in CUP. Some web service adresses were missing at this time.

Many thanks Jeffrey

Former Member · ‎05-26-2010

Hi all,

I have checked the settings once again:

- All required connectors are working well if we perform some tests

- The web service adresses are set up correctly in RAR and CUP (Settings could be found in first post)

- The workflow types RISKC/D/U are currently deactivated

- The workflow set up is correct --> the risk analysis should be performed on Line Manager stage

We assigned all available UME roles within the UME to ensure that the authorization for the web service user is sufficient.

Any other ideas?

Many thanks Jeffrey

Former Member · ‎05-26-2010

Hi,

Please check the following:

Web services in RAR and also check whether the workflow type RISK in CUP is activated or not.

And also perform the connection test for connectors and JCOs.

Thanks,

Rama

Former Member · ‎05-26-2010

Hi,

We restarted the J2EE Server. I created a request but the issue still comes up. Below you will find the complete log file from that last request.

2010-05-26 09:40:06,706 [SAPEngine_Application_Thread[impl:3]_10] ERROR Ignoring exception, setting to default value : -1

java.lang.NumberFormatException: For input string: "Z_MM_LALTG_AMFR_2100"

at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)

at java.lang.Integer.parseInt(Integer.java:468)

at java.lang.Integer.parseInt(Integer.java:518)

at com.virsa.ae.commons.utils.Util.parseInt(Util.java:1063)

at com.virsa.ae.search.actions.SearchRolesAction.execute(SearchRolesAction.java:802)