Siebel BIP Report Scheduling Fails with Error "oracle.xdo.dataengine.datasource.webservice.WSClientException: MalformedURLException" in BIPublisher.log
(Doc ID 3040546.1)
Last updated on AUGUST 09, 2024
Applies to:
Siebel Reports - Version 17.0 [IP2017] and laterInformation in this document applies to any platform.
Symptoms
When attempting to generate report through Siebel Report Scheduling, the following error occurs in the bipublisher.log on the BIP server.
BIPublisher.log:
[2024-07-18T15:24:48.639+03:00] [bi_server1] [NOTIFICATION] [] [oracle.xdo] [tid: 269] [userId: weblogic] [ecid: e921bdd3-c7b9-4425-a08c-26db40f21c06-0000000c,0:604:4] [APP: bipublisher] [partition-name: DOMAIN] [tenant-name: GLOBAL] [xdojobid: 1018] [essjobid: null] [2024-07-18T15:24:48.638+03:00][dp id:255923926][sch info:JobId:1018[ESS RequestId:null]]oracle.xdo.dataengine.datasource.plugin.DataAccessException: oracle.xdo.dataengine.datasource.plugin.DataAccessException: oracle.xdo.dataengine.datasource.webservice.WSClientException: MalformedURLException[[
at oracle.xdo.dataengine.datasource.XMLStatement.execute(XMLStatement.java:128)
at oracle.xdo.dataengine.XMLPGEN.processDataSet(XMLPGEN.java:1849)
at oracle.xdo.dataengine.XMLPGEN.processDataSet(XMLPGEN.java:2585)
at oracle.xdo.dataengine.XMLPGEN.processMergedDataSet(XMLPGEN.java:2077)
at oracle.xdo.dataengine.XMLPGEN.processMergedDataSet(XMLPGEN.java:3930)
at oracle.xdo.dataengine.DataProcessor.processData(DataProcessor.java:386)
at oracle.xdo.servlet.dataengine.DataProcessorImpl.processData(DataProcessorImpl.java:311)
at oracle.xdo.servlet.dataengine.DataProcessorImpl.render(DataProcessorImpl.java:688)
at oracle.xdo.servlet.ReportModelContextImpl.getReportXMLData(ReportModelContextImpl.java:446)
at oracle.xdo.servlet.ReportContextImplV2.getReportXMLData(ReportContextImplV2.java:167)
at oracle.xdo.servlet.CoreProcessor.getReportXMLData(CoreProcessor.java:2117)
at oracle.xdo.servlet.CoreProcessor.process(CoreProcessor.java:621)
at oracle.xdo.servlet.CoreProcessor.processRequest(CoreProcessor.java:301)
at oracle.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:158)
at oracle.xdo.servlet.ReportImpl.renderReportXML(ReportImpl.java:1362)
at oracle.xdo.enterpriseScheduler.bursting.BurstingJobProcessor.getReportData(BurstingJobProcessor.java:1063)
at oracle.xdo.enterpriseScheduler.bursting.BurstingJobProcessor.execute(BurstingJobProcessor.java:584)
at oracle.xdo.enterpriseScheduler.bursting.BurstingJobProcessor.onMessage(BurstingJobProcessor.java:238)
at oracle.xdo.enterpriseScheduler.util.CheckpointEnabledListener.onMessage(CheckpointEnabledListener.java:26)
at oracle.xdo.enterpriseScheduler.jmswrapper.client.JMSMessageConsumer.processMessage(JMSMessageConsumer.java:276)
at oracle.xdo.enterpriseScheduler.jmswrapper.client.ThreadedMessageDispatcherOpt$DispatchWorker.run(ThreadedMessageDispatcherOpt.java:146)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
Caused by: oracle.xdo.dataengine.datasource.plugin.DataAccessException: oracle.xdo.dataengine.datasource.webservice.WSClientException: MalformedURLException
at oracle.xdo.dataengine.datasource.ThreadExecutor.process(ThreadExecutor.java:103)
at oracle.xdo.dataengine.datasource.ThreadExecutor.run(ThreadExecutor.java:62)
Caused by: oracle.xdo.dataengine.datasource.webservice.WSClientException: MalformedURLException
at oracle.xdo.dataengine.datasource.webservice.WSSoapRequest.createModel(WSSoapRequest.java:86)
at oracle.xdo.dataengine.datasource.webservice.WSSoapRequest.execute(WSSoapRequest.java:58)
at oracle.xdo.dataengine.datasource.webservice.ComplexWSCall.execute(ComplexWSCall.java:210)
at oracle.xdo.dataengine.datasource.XMLStatement.executeWS(XMLStatement.java:572)
at oracle.xdo.dataengine.datasource.ThreadExecutor.process(ThreadExecutor.java:95)
... 1 more
The issue can be reproduced at will with the following steps:
1. Setup Siebel 23.x and Integrate with BIP
2. Configure the Report Scheduling functionality in Siebel.
3. Submit a report generation through report scheduling option.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |