FileNotFoundException in weblogic internal folder

Question

<p>Hi,</p><p>I am trying to integrate CR4E report viewing into our app which is running on a weblogic machine.</p><p>When tyring to load the report file I get a FileNotFoundException and the path it specifies is the real computer path:</p><p>Report file D:/workbench/projects/pa-bam-sp4/build/output/x86/windows/pa/domains/pa-domain/pa-s<br />erver/.wlnotdelete/extract/pa-server__appsdir_pa-pa_ear_pa-web/jarfiles/reports/pojoReport.rpt not found</p><p>I have noticed that the path is not where my ear resides but some internal weblogic folder  (../.wlnotdelete/..).</p><p>Is this a CRConfig.xml problem, weblogic problem or my problem ;-)</p><p>(I have tried running it stand alone on jboss and it worked fine)</p><p>Thanks</p><p>Nathaniel</p>

Answer 1

<p>Hi Nathaniel,</p><p>     This is a known issue and we have included 2 work-arounds in our release notes. Out of curiosity which version of Weblogic are you using? I have heard that this may not be an issue with Weblogic 9 but I haven&#39;t confirmed this yet. The root of the problem lies in how Weblogic launches the application. By default the deployed application is kept in it&#39;s compressed WAR format and is exploded when requested. The Crystal Reports runtime engine (JAR files) are deployed to a temporary JAR files folder at this time. The problem for Crystal Reports users is that by default the report engine uses a relative path to the engine location to determine the report location. So the 2 work-arounds provide a solution to make the report visible to the runtime engine when the JAR file ends up in a "unknown" location.</p><p>You can view these work-arounds in the <a href="/node/447">Release Notes:</a>  </p><p>When using the BEA WebLogic server, it may be unable to resolve the report location and you may see the error, "Report cannot be found". There are two ways to resolve this problem.</p><p><u><strong><br />Workaround 1:</strong></u> <br />1. Remove the <reportlocation> element from the CRConfig.xml file. <br />2. Place your .rpt files in the WEB-INF/classes folder of the WAR file. Alternatively, package the .rpt files in a JAR file and place it in the WEB-INF/lib folder. <br />3. When invoking the &#39;IReportSourceFactory2.createReportSource&#39; or the &#39;ReportClientDocument.open&#39; method to obtain a report source or report client document, use the report name as the value of the report location parameter. For example, the report location could be specified as "/myReport.rpt", where myReport.rpt is either located in the /WEB-INF/classes folder or in a JAR file located in the /WEB-INF/lib folder. </p><p><br /><u><strong>Workaround 2: </strong></u><br />1. Remove the <reportlocation> element from the CRConfig.xml file. <br />2. Modify your JSP to use the absolute path to the report name. For example, you could call clientdoc.open(application.getRealPath("") + "
" + "YourReport.rpt", 0). Note: For workaround 2, you do not need to move the report files. </p><p>Let me know if either of these solutions work for you.</p><p>Sean </p>