Java system error: call FM RSRD_X_PRODUCE_PROXY

Hi Gurus,
When i tried to execute event data change process type in BI component I am getting below error. It clearly says missing password. I haven't understood what password is missing for which user. we checked all user certificates all valid.
Below is the error log:
Java system error: call FM RSRD_X_PRODUCE_PROXY to ProgId BP1TULAP424_PORTAL_WSH on host BP1TULAP424 with SSO not authorized: Missing Password
Message no. RSBOLAP018
Diagnosis
An error occurred in the BI components on the SAP J2EE Engine.
Procedure
Contact your system administrator to have the error analyzed in detail.
Procedure for System Administration
Start the Visual Administrator, log on to the SAP J2EE Engine and choose "<J2EE_SID>" ->"Server" -> "Services" -> "Log Viewer".
The file "defaultTrace.trc" includes detailed information about the error that occurred. In Windows, you can find this file in the Log Viewer under "Cluster <computer name>" -> "Server <server number>" -> "<drive>:\usr\sap\<SID>\JC<INSTANCE>\j2ee\cluster\server<NUMBER>\log". ". In Unix, the file is located under "/usr/sap/<SID>/JC<INSTANCE>/j2ee/cluster/server<NUMBER>/log".
If the file does not include enough detail about the error, you can increase the log level to obtain more information. To do this, choose "<J2EE_SID>" -> "Server" -> "Services" -> "Log Configurator". On the "Locations" tab page, choose "com" -> "sap" -> "ip" -> "bi" -> "webapplications". Using the selection list on the right side of the screen, you can increase the log level, whereby "DEBUG" represents the log level with the most information. You can save your settings by choosing the "Save" icon. The change to the log level is active immediately. Once you have successfully analyzed the error, you should set the log level back to its default value using the appropriate pushbutton; continuous writing to the log file negatively affects the overall performance of the system.
Any help greatly appreicated. Thanks.
Best Regards,
Reddy.

Hi,
> Java system error: call FM RSRD_X_PRODUCE_PROXY to ProgId MOTDALSUN115_PORTAL_BWP on host motdalsun116 with >SSO not authorized: Authentication fai
>
As per your logs it looks like that user from which you are calling FM does not have proper authorization to run this FM. Please check your authorization.
Thanks
Sunny

Similar Messages

Java system error: call FM RSWR_SYSTEM_ALIAS_CHECK_PROXY

We've setup BI 7.0 (EP) using SSO to our ECC 6.0 system leveraging EP on our BI box. Anyways, SSO is activated and working when EP on the BI system calls a BSP or a Transactional iView using ITS on ECC 6.0.
Our issue is when we execute a report BI (EP) utilizing RRI to a transaction in ECC 6.0 we're receiving the following error with SSO:
Termination message sent
ABEND RSBOLAP (018): Java system error: call FM RSWR_SYSTEM_ALIAS_CHECK_PROXY to ProgId COHPSAP06D_PORTAL_BPD on host cohpsap06d with SSO not authorized: Authenticatio
MSGV1: call FM RSWR_SYSTEM_ALIAS_CHECK_PROXY to ProgId CO
MSGV2: HPSAP06D_PORTAL_BPD on host cohpsap06d with SSO no
MSGV3: t authorized: Authenticatio
When we didn't have SSO enable we recevied the typical login screen for the ITS. After we setup SSO we cannot even log in now.
--KAL

Hello Kal,
Am not very sure of the solution but to drill down to the exact cause you can do this small test:
1. In the reference system in Portal, you can remove the ITS enteries like ITS hostname, etc, keeping the rest of the enteries unchanged.
Now, if the exception goes..this shows that the exception could be due to some wrong ITS entry or somewhere related to ITS
If the issue persists then looking at the exception it feels like you should check the in Portal Visual Admin...
Hope this helps.
All the best,
Ritu

Java system error: call FM RSRD_X_DISTRIBUTE_PROXY to ProgId SERVER_PORTAL_

Hi All,
Java system error: call FM RSRD_X_DISTRIBUTE_PROXY to ProgId SERVER_PORTAL_SID on host SERVER with SSO not authorized: Authenticatio...
also Not able to create user ID in BI Portal with J2ee_admin user, as user has full ( Sap_all) athorization in backend.
Thanks & Regards,
Vamsi

Hi,
i have exactly the same error. Can anybody help? or does anyone have an idea?
Thanks and kind regards,
Murat

Java System error: SSO not authorized: authorization Failed

Hi,
I am getting the following error while opening a BEx report designer or WAD and iam unable to design any report or create a dashboard
"Java System Error: Call to FM BICS_CONS_GET_VIEW_DEF_J_PROXY to ProdId ASEP_PORTAL_E01 on host ASEP wiht SSO not authorized . Authentication Failed"
System Details:
BI and EP are installed in Same server
BI Config:
softwarwe component : SAP_BW
Release : 700
Patch Level: 0021
Support Pack : SAPKW70021 (SAP NetWeaver BI 7.0)
EP config:
SAP NetWeaver BI 7.0 SP Level 15
Please suggest .

It seems that something wrong in integration between JAVA Stack (from where you accessing BW report) a BW back end system. Try to run Support Desk Tool:
http://<your_server>:<port>/irj/servlet/prt/portal/prteventname/HtmlbEvent/prtroot/com.sap.ip.bi.supportdesk.default
to see what is wrong in this area.

Java system error: Server repository could not create function template

Hi, Our BI person is trying to publish/broadcast a query to the PRODCTION portal, she gets the below error message. I am
attaching the defaulttracelog file
"Java system error: Server repository could not create function template for RSRD_X_PRODUCE_PROXY caused by: com.sap.mw.jco.JCO$Exception: (103)"
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[8, 20, 10485760]/>
<!PREVIOUSFILE[defaultTrace.7.trc]/>
<!NEXTFILE[defaultTrace.9.trc]/>
<!LOGHEADER[END]/>
#1.5 #002264F9350800600000022F000019C000048E9B91EF3AB3#1282698726384#com.sap.security.core.persistence#sap.com/irj#com.sap.security.core.persistence#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Security/Usermanagement#Java#An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". ##An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". #1#Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       partner '127.0.0.1:sapgw00' not reached
TIME        Tue Aug 24 21:12:06 201
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER     56
#1.5 #002264F93508006000000230000019C000048E9B91EF47C8#1282698726384#com.sap.engine.services.monitor.mbeans.Monitor#sap.com/irj#com.sap.engine.services.monitor.mbeans.Monitor#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###Caller J2EE_GUEST not authorized, user J2EE_GUEST is not available from user management, reason: com.sap.security.api.NoSuchUserException:USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!#
#1.5 #002264F93508006000000231000019C000048E9B91EF4CD5#1282698726384#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###com.sap.engine.services.jmx.exception.JmxSecurityException: Caller J2EE_GUEST not authorized, user J2EE_GUEST is not available from user management, reason: com.sap.security.api.NoSuchUserException:USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!
     at com.sap.engine.services.jmx.auth.UmeAuthorization.checkMBeanPermission(UmeAuthorization.java:63)
     at com.sap.engine.services.jmx.JmxServerFrame.checkMBeanPermission(JmxServerFrame.java:98)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.unregisterMBean(MBeanServerSecurityWrapper.java:395)
     at com.sap.engine.services.jmx.ClusterInterceptor.unregisterMBean(ClusterInterceptor.java:1327)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.unregisterMBean(MBeanServerInterceptorChain.java:258)
     at com.sap.engine.services.monitor.mbeans.Monitor.unregister(Monitor.java:106)
     at com.sap.engine.library.monitor.impl0.AbstractMonitorNode.remove(AbstractMonitorNode.java:154)
     at com.sap.engine.library.monitor.impl0.MonitorObjectFactory.uninstallMonitorNode(MonitorObjectFactory.java:483)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:595)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:568)
     at com.sap.engine.services.monitor.server.ApplicationLifeCycleImpl.applicationStopped(ApplicationLifeCycleImpl.java:52)
     at com.sap.engine.services.monitor.deployment.MonitorDeploymentContainer.commitStop(MonitorDeploymentContainer.java:630)
     at com.sap.engine.services.deploy.server.application.StopTransaction.commonCommitFinished(StopTransaction.java:244)
     at com.sap.engine.services.deploy.server.application.StopTransaction.commitCommon(StopTransaction.java:290)
     at com.sap.engine.services.deploy.server.application.StopTransaction.commitLocal(StopTransaction.java:278)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:374)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.stopApplicationLocalAndWait(DeployServiceImpl.java:4569)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.stopApplicationLocalAndWait(DeployCommunicatorImpl.java:628)
     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime$2.run(SAPJ2EEPortalRuntime.java:602)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.lang.ClassLoader$NativeLibrary.load(Native Method)
     at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586)
     at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1482)
     at java.lang.Runtime.load0(Runtime.java:737)
     at java.lang.System.load(System.java:811)
     at com.sapportals.wcm.service.fsmount.FSMountService.loadDLL(FSMountService.java:736)
     at com.sapportals.wcm.service.fsmount.FSMountService.<clinit>(FSMountService.java:796)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:219)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.convertGS(CmConfigurationProvider.java:637)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.convertServiceConfig(CmConfigurationProvider.java:601)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.readConfiguration(CmConfigurationProvider.java:205)
     at com.sapportals.wcm.crt.CrtSystemImpl.createComponentManager(CrtSystemImpl.java:108)
     at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:202)
     at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
     at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:249)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
     at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
     at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
     at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)
     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
     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)
#1.5 #002264F93508005C0000042300002CF00004939AAEE9AEB7#1288192475655#com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager#sap.com/irj#com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager#J2EE_GUEST#0##n/a##c7d00e00e1dc11dfa36d002264f93508#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain###setting initial ACL on /reporting_backend/reports/System Administration/CM Store/cm.crawlcontent - com.sap.security.api.NoSuchRoleException: Role with uniqueName system_admin_role not found!
     at com.sap.security.core.imp.RoleFactory.getRoleByUniqueName(RoleFactory.java:1783)
     at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.getRoles(RPRepositoryManager.java:1474)
     at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.syncReportResources(RPRepositoryManager.java:1334)
     at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.initBackend(RPRepositoryManager.java:489)
     at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.getResource(RPRepositoryManager.java:581)
     at com.sapportals.wcm.repository.RMAdapter.getResource(RMAdapter.java:228)
     at com.sapportals.wcm.repository.runtime.CmAdapter.findResource(CmAdapter.java:1349)
     at com.sapportals.wcm.repository.runtime.CmAdapter.findManagerAndResource(CmAdapter.java:1322)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:979)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
     at com.sapportals.wcm.service.reporting.ReportingService.localConfigure(ReportingService.java:294)
     at com.sapportals.wcm.service.reporting.ReportingService.startUpImpl(ReportingService.java:74)
     at com.sapportals.wcm.service.AbstractService.start(AbstractService.java:167)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
     at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
     at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
     at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
     at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)
     at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:278)
     at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)
     at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:227)
     at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
     at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:249)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
     at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
     at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
     at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)

Go to visual admin -> server -> services -> JCO RFC provider.
Check the RFC that connects to the BI Abap.
Its reporting the J2EE_GUEST user in the SAP with the system nr 00.
Is this BI java portal?
Is the java portal a addon to Abap or having seperate SID?
Check the connection definitions are correct and the gateway is running.

Java system error

Hi Guru:
Now I could create a web report and execute it.
But each time I save it, there is an error:
Java system Error: Bean RSWR_TEMPLATE_PROCESS_PROXY is not found.
How to solve it?
Thank you very very much.
Best regards,
Eric

i think its the problem with ur internet connection.i mean the proxy settings have to be checked to recover tht problem.

Java system error: Exception in method processFunction in BEX Broadcaster

Hi All,
We are trying to broadcast a BI7 Webtemplate with our enterprise portal. While clicking on "Create New setting " iam getting the error " Java system error: Exception in method processFunction ".
Detailed error description is
*Diagnosis
An error occurred in the BI components on the SAP J2EE Engine.
System Response
Procedure
Contact your system administrator to have the error analyzed in detail.
Procedure for System Administration
Start the Visual Administrator, log on to the SAP J2EE Engine and choose "<J2EE_SID>" ->"Server" -> "Services" -> "Log Viewer".
The file "defaultTrace.trc" includes detailed information about the error that occurred. In Windows, you can find this file in the Log Viewer under "Cluster <computer name>" -> "Server <server number>" -> "<drive>:\usr\sap\<SID>\JC<INSTANCE>\j2ee\cluster\server<NUMBER>\log". ". In Unix, the file is located under "/usr/sap/<SID>/JC<INSTANCE>/j2ee/cluster/server<NUMBER>/log".
If the file does not include enough detail about the error, you can increase the log level to obtain more information. To do this, choose "<J2EE_SID>" -> "Server" -> "Services" -> "Log Configurator". On the "Locations" tab page, choose "com" -> "sap" -> "ip" -> "bi" -> "webapplications". Using the selection list on the right side of the screen, you can increase the log level, whereby "DEBUG" represents the log level with the most information. You can save your settings by choosing the "Save" icon. The change to the log level is active immediately. Once you have successfully analyzed the error, you should set the log level back to its default value using the appropriate pushbutton; continuous writing to the log file negatively affects the overall performance of the system.
Notification Number RSBOLAP 018 *
Please let us know how to proceed

Hi,
This is a configuration issue. All components on the J2EE stack have to
be on the same SPS level. Please make sure of this as a first step.
For special requirements of BI with regards SPS levels please see SAP
Notes 873996 and 1013369.
Please run the latest version of the support desk tool as per SAP note
937697 and ensure that there is no error and then check for the issue
again.
Otherwise, I suggest you open a BW-BEX-ET-BC msg with SAP.
Rgds,
Colum

RSBOLAP 018 Java system error in BEx Web Application Designer

Hello,
while doing inside BEX Web Application Designer "validation of webtemplate" with
command "validate on server" I get following error message of WAD :
" Message RSBOLAP 018 description : Java system error : an Unknow Error occured during portal communication"
My procedure till now was ( please see results as screenshots in attachment) :
a) ckecking prerequisites for "Java template installer'" --> result "prerequisites.jng"
b) running "Java template installer" -> " result templateInstaller.jpg"
c) running Bex Web Application Designer as mentioned above results in error
message as mentioned above
d) running Diagnostic & Support Desktop Tool --> "result Diagnostic support desktop tool.jpg"
It says that something is wrong with "BI Mastersystem" because of failed connect to
message server.
Please advice me what I should do.
Thanks in advance
Regards,
Oscar

Hello
It is obvious that the connection between the ABAP and the Java is not working.
There should be a JCo RFC from the portal side to the ABAP stack set up and an RFC from the ABAP stack to the portal.
Check the entries of the table RSPOR_T_PORTAL
The RFC specified here should be the one mentioned above (ABAP - Java)
Check the name of the system should be SAP_BW
Is the parameter icm/host_name_full set on the ABAP stack with the domain name ?
Connect to the BI portal:
http://FQDN:5NN00/irj/portal
Navigate to system administration -> system configuration -> system landscape -> expand "portal content" -> systemlandscape -> SAP_BW
Right click on SAP_BW - Open - Object
Here you need to maintain these:
ITS Description - BW ABAP Logical System Name - Tx SCC4 or BD54
ITS Host Name - FQDN_OF_BW_ABAP:port - You can use the value of icm/host_name_full parameter and retrieve port number from Tx SMICM - Services
ITS Path - /sap/bc/gui/sap/its/webgui
ITS Protocol - Select http
Logical System Name - BW ABAP Logical System Name - Tx SCC4 or BD54
Logon Method -SAPLOGONTICKET
Message server - BW ABAP FQDN
SAP Client - BW ABAP Client Number
SAP System ID (SID) - BW ABAP SID
Server Port - 39NN
Web AS Description - BW ABAP Logical System Name - Tx SCC4 or BD54
Web AS Host Name - FQDN_OF_BW_ABAP:port - icm/host_name_full and retrieve port number from Tx SMICM - Services
Web AS Path - /sap/bw/BEx
If everything is set properly then do a test connection.
Good Luck
RB

Java system error, when publishing BI Queries to Portals...

Hello all,
I am getting the error 'Java system error: Exception in method processFunction.' when publishing the BI queries (7.0 with SP 14) into EP 7.0 portals. Our BI system is integrated successfully into Portals.
Further diagnosis shows 'An error occurred in the BI components on the SAP J2EE Engine'.
Please reply to this message with any relevant/useful details to resolve this problem. Thanks in advance...
Thanks,
Ram.

also restart the J2EE engine from SMICM.
Hope it Helps
Chetan
@CP..

Java system error: Bean BICS_CONS_GET_VIEW_DEF_J_PROXY not found

In BEx Report Designer, click Insert Data provider under Report, and then choose one create query, system show the error message(message class:RSBOLAP, message number:018), the detail diagnosis like below, please help to solve it. Thanks!
Diagnosis
Error while loading query metadata, Check the query and portal settings
An error occurred in the BI components on the SAP J2EE Engine.
System Response
Procedure
Contact your system administrator to have the error analyzed in detail.
Procedure for System Administration
Start the Visual Administrator, log on to the SAP J2EE Engine and choose "<J2EE_SID>" ->"Server" -> "Services" -> "Log Viewer".
The file "defaultTrace.trc" includes detailed information about the error that occurred. In Windows, you can find this file in the Log Viewer under "Cluster <computer name>" -> "Server <server number>" -> "<drive>:\usr\sap\<SID>\JC<INSTANCE>\j2ee\cluster\server<NUMBER>\log". ". In Unix, the file is located under "/usr/sap/<SID>/JC<INSTANCE>/j2ee/cluster/server<NUMBER>/log".
If the file does not include enough detail about the error, you can increase the log level to obtain more information. To do this, choose "<J2EE_SID>" -> "Server" -> "Services" -> "Log Configurator". On the "Locations" tab page, choose "com" -> "sap" -> "ip" -> "bi" -> "webapplications". Using the selection list on the right side of the screen, you can increase the log level, whereby "DEBUG" represents the log level with the most information. You can save your settings by choosing the "Save" icon. The change to the log level is active immediately. Once you have successfully analyzed the error, you should set the log level back to its default value using the appropriate pushbutton; continuous writing to the log file negatively affects the overall performance of the system.

hello,
Please check the system configuration using:
937697: Usage of SAP NetWeaver BI Diagnostics & Support Desk Tool
Regards, Karol Kalisz, BI Development

Serious system error while executing the query: java.lang.OutOfMemoryError

From ALSB, we are trying to insert records in a table, by calling the ALDSP webservice. It is working fine when the xml (ie., given as input to the ALDSP webservice) is small. But facing the following error when the input xml size is large.
<ALDSP> <BEA-000000> <Product> <Serious system error while executing the query:
{ld:ABC/Test}createTest:1
java.lang.OutOfMemoryError: Java heap space
We do not want to increase the heap size. Is there any other way we can solve this problem?

In logical dataservice of ALDSP we have created a procedure called createTest, which is used to insert mulitple rows in the table. We have created a webservice for that logical DataService.
Using the ALSB, we are calling the webservice -> createTest Operation and we are passing xml as input to that createTest function.
Input xml:
<ns1:createTest>
<ns1:createTemps>
<ns0:createTemp>
     <ns0:field1>1</ns0:field1>
          <ns0:field10>test1</ns0:field10>
</ns0:createTemp>
<ns0:createTemp>
     <ns0:field1>2</ns0:field1>
          <ns0:field10>test2</ns0:field10>
</ns0:createTemp>
     </ns1:createTemps>
</ns1:createTest>
each ns0:createTemp represent a row that need to be inserted in the table.
When the number of ns0:createTemp is less ( when the number of rows that need to be inserted is less) then no problem occurs, it is getting inserted properly. But when there are more number of ns0:createTemp then we are getting the following error
<ALDSP> <BEA-000000> <Product> <Serious system error while executing the query:
{ld:ABC/Test}createTest:1
java.lang.OutOfMemoryError: Java heap space

Webservice Connection Timeout Error in Sun Java System Application server

I have a java code to connect to Ebay Shopping Webservice that uses the client stub generated through Axis. The code works fine when I run it from the main method of a stand alone Java application. Which means there is no issue with the Proxy settings or any other network setting that could block the webservice from my system. However when I use the same code inside a JSF based Web Application, a connection timeout error comes up. The Web application is deployed on the Sun Java System Application server. The stacktrace of the exception is
java.net.ConnectException: Connection timed out: no further information
     at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
     at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:527)
     at com.sun.enterprise.server.ss.provider.ASClientSocketImpl.connect(ASClientSocketImpl.java:206)
     at java.net.Socket.connect(Socket.java:520)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:153)
     at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:125)
     at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
     at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
     at org.apache.axis.client.Call.invoke(Call.java:2767)
     at org.apache.axis.client.Call.invoke(Call.java:2443)
     at org.apache.axis.client.Call.invoke(Call.java:2366)
     at org.apache.axis.client.Call.invoke(Call.java:1812)
     at com.ebay.api.soap.ShoppingBindingStub.findProducts(ShoppingBindingStub.java:1217)
     at com.shopping.ebay.EbayServiceUtility.performEBaySearch(EbayServiceUtility.java:66)
     at searchProduct.SearchProductBean.search(SearchProductBean.java:98)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sun.el.parser.AstValue.invoke(AstValue.java:151)
     at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
     at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77)
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:96)
     at javax.faces.component.UICommand.broadcast(UICommand.java:383)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:450)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:759)
     at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:244)
     at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:113)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
     at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
The JDK version on my machine is 1.5.0_14. Can somebody point me as where I should be looking for errors?

You need to delete all the files under the 'generated' directory to force the server to recompile them after the JDK upgrade. Also check in domain.xml and make sure the JVM parameter is pointing to the JDK that you have installed. It is also worthwhile to check asenv.conf to see which JDK that file is pointing to as well.

Cannot get java system call to work

I am trying to make a system level call that will create a new user but have not been sucessful. I am reading the list of new users from newbousrs.txt file. Why am I getting the error message shown below? Here is my program:
import java.io.*;
public class ReadSource {
public static void main(String[] arguments) {
try {
FileReader file = new FileReader("newbousrs.txt");
BufferedReader buff = new BufferedReader(file);
Runtime rt = Runtime.getRuntime();
boolean eof = false;
while (!eof) {
String line = buff.readLine();
if (line == null)
eof = true;
else
System.out.println(line);
Process proc = rt.exec("\\Blowfish\\droot\\Program Files\\Business Objects\\BusinessObjects 5.0\\supervsr.exe -USER xxxxx -PASS yyyy -IMPORTUSERS \\Blowfish\\droot\\accsp\\public\\newusers\\newbousrs.txt");
buff.close();
} catch (IOException e) {
System.out.println("Error -- " + e.toString());
There error I get is this:
C:\jakarta-tomcat-4.0.3\webapps\webdav\WEB-INF\classes\accsp>java ReadSource
NU,Public,Steve Mcnealy,Steve Mcnealy,U,N,N,Y,N,N,PC,F,Y,N,N
Error -- java.io.IOException: CreateProcess: \Blowfish\droot\Program Files\Busin
ess Objects\BusinessObjects 5.0\supervsr.exe -USER accsp -PASS fish -IMPORTUSERS
\Blowfish\droot\accsp\public\newusers\newbousrs.txt error=3

Just a guess....
Program Files\\Business ObjectsSpace used in arguments in a command line command must have quotes around them. That includes the first argument.

System error when calling a servlet

Hi All
I have a servlet deployed in sap j2ee engine. The servlet actually reads a SOAP message , extracts a file attached with the SOAP message and forwards the file to a RFC. Now from a java class I am attaching a file with the SOAP message and calling the servlet. At that moment I am getting system error at com.sap.engine.services.httpserver.server.client.handle(client.java:95) (Thats what I saw in the server system log)...
My servlet extends JAXMServlet implements ReqRespListener.
and use public javax.xml.soap.SOAPMessage onMessage(javax.xml.soap.SOAPMessage sOAPMessage).
Any help would be great!
Regards
Sunit

I understand, so i have a doubt, why the webservice works on jDeveloper ??Not just JDeveloper even soapUI and Neatbeans have a way of working without a client certificate installed.
I do not know how they achieve it. I know that they work without a client DC.
Cheers,
PS: See this http://stackoverflow.com/questions/8887434/webservices-ssl-https, it offers a clue.
The java programs run unhindered when one-way authentication is being used. These products ship with a digital certificate that is in the path of most popular CAs.
Corollary, if the Web Server is configured for mutual authentication then you need to install and configure the client certificate in the tools.
Edited by: Prabodh on Dec 5, 2012 8:36 PM

Calling Java Function error

Hi,
I am trying to call a small hello world java function from Oracle 11g database.But i am getting the below errors:
ORA-29516: Aurora assertion failure: Assertion failure at eox.c:342
Uncaught exception System error: java/lang/UnsupportedClassVersionError
ORA-06512: at "SCOTT.HELLOWORLD", line 1
ORA-06512: at line 4
The database version is 11.1.0.7.0 and jdk version is 1.6
Plz let me know the reason for this.
Thanks.

This error seems to the incompatiable version of complied java with oracle database java version.
Now Oracle 11g is use JDK 1.5. You have to compile the java files with the jdk version which is provided by oracle itself.
So compile the java files with the ORACLE_HOME/jdk/bin/javac

Java system error: call FM RSRD_X_PRODUCE_PROXY

Similar Messages

Maybe you are looking for