Problem when trying to publish Query through BeX in Portal as iView
Hi ,
We are trying to publish BW 3.5 query in EP 6.0.
when we are trying to publish the query as iView in portal, it gives the error message 'System Error'. The J2EE Error Log contains the following error :
#1.5#001321FC0EDF001D0000000100000AF800042349427FEAFD#1164697462095#com.sap.security.core.server.jaas##com.sap.security.core.server.jaas#J2EE_GUEST#2##BID#AMARNATH_RR #6AA3FE0EADF14B2593F0019B1DB52607#SAPEngine_Application_Thread[impl:3]_17##0#0#Error##Java###Authentication stack: [].
[EXCEPTION]
#2#evaluate_assertion_ticket#javax.security.auth.callback.UnsupportedCallbackException: Unsupported callback!
at com.sap.engine.services.rfcengine.security.impl.RFCCallbackHandlerImpl.handle(RFCCallbackHandlerImpl.java:49)
at javax.security.auth.login.LoginContext$5.run(LoginContext.java:812)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext$SecureCallbackHandler.handle(LoginContext.java:808)
at com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule.removeSSOHeader(EvaluateAssertionTicketLoginModule.java:736)
at com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule.login(EvaluateAssertionTicketLoginModule.java:390)
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:69)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:154)
at com.sap.engine.system.SystemLoginModule.login(SystemLoginModule.java:90)
at sun.reflect.GeneratedMethodAccessor206.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:675)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607)
at javax.security.auth.login.LoginContext.login(LoginContext.java:534)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:60)
at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#
#1.5#001321FC0EDF00140000000600000AF800042349427FF32E#1164697462095#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal()####BID#AMARNATH_RR #6AA3FE0EADF14B2593F0019B1DB52607#Thread[JCO.ServerThread-8,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Plain###java.lang.RuntimeException: com.sap.engine.services.rfcengine.RFCException: Incoming call is not authorized#
#1.5#001321FC0EDF00140000000700000AF800042349427FF40A#1164697462111#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal()####BID#AMARNATH_RR #6AA3FE0EADF14B2593F0019B1DB52607#Thread[JCO.ServerThread-8,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Plain###java.lang.RuntimeException: com.sap.engine.services.rfcengine.RFCException: Incoming call is not authorized
at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:188)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#
Landscape:We have both BW 3.5 and EP 6.0, SP 16 on the same instance in
same physical machine. EP 6.0 works on J2EE engine as an add-in installtion.
Steps we followed for the integration of EP with BW:
1)Create RFC Destination in J2EE Engine:
Parameters:
Program ID: xyz
Gateway host: abc.ad.company.com
Gateway service: sapgw00
Application server host:abc.ad.company.com
System number: 00
Client: BID
Language: EN
User: sapjsf
Password: ********
2)Maintain RFC Destination for SAP EP 6.0
Parameters:
RFC destination: SAP_EP
Connection type: T for TCP/IP connection
Description: SAP EP RFC Destination
Technical Settings:
- Type of activation: Registered server program
- Program ID: xyz
- Gateway host: abc.ad.company.com
- Gateway service: sapgw00
Logon/Security:
- Send SAP Logon Ticket: Activated
Special Options:
Unicode
3)Maintain Portal Server Settings for SAP EP 6.0 in table RSPOR_T_PORTAL
in BW 3.5
RFC destination: SAP_EP
System name: BIDEV
Default: Checked
Portal URL prefix: http://abc.ad.company.com:50000
RM prefix for BW metadata: <empty>
KM service URL: <empty>
P.S.:We have maintained one more dummy entry as per the SAP Note 815044
in the table RSPOR_T_PORTAL.
4)Maintain Single Sign-On in SAP BW
In transaction RZ10, We have maintained following settings:
login/create_sso2_ticket=2
login/accept_sso2_ticket=1
5)Export BW Certificate to SAP BW and
6)Import BW Certificate to SAP EP 6.0
We have followed the above mentioned two steps.
7)Create BW System in SAP EP 6.0
Parameters:
Log on methods: SAPLOGONTICKET
We have created the BW system and the Connection test in WAS Connection
is working fine.
8)Configure User Management in SAP EP 6.0
This step is not maintained as our scenario does not demand it.
9)Export Portal Certificate to SAP EP 6.0 and
10)Import Portal Certificate to SAP BW
This step is also maintained as per Performance Assistant guidelines in
SPRO.
The user that we are trying to log into BeX Web Query Analyzer is
Amarnath_rr who has 'SAP ALL' rights and the same user in EP is assigned'Super Admin' as well as 'Content Admin' role.
Can anyone throw any light on wat the error might be??