I am new to this field and have no idea how this works. We have BusinessObjects installed on one of our windows servers. We can access the reports after hitting the URL. Now I am trying to make some changes on the reports, I can open this report from Crystal Report > Open > Enterprise > local
I checked Web Content under BO installation path, FileStore but I am not able to find out what is the location of this Enterprise. Can someone tell where we can find these reports on our windows server?
By default, the filestore (FRS) is located in:
C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
However, it is very rare that you'd need to access files in the FRS directly. If you do, you'll need to know the exact folder path and file name. In BI launchpad, open up the report's properties, and the path will be displayed as "File Name". This is the logical path relative to the FRS parent.
Once you have made your changes to the report you need to save it back to the BusinessObjects platform. If you are using Crystal Reports for Enterprise here is a video on how to do that. If you are using Crystal Reports 201x check out this video.
Related
I have a folder (cat1) in jasperServer which contains some reports. After changing the name of the folder using the web interface to category1, the paths of reports which are inside this folder does not change. For example, report1 still has the path /reports/cat1/report1 and not /reports/category1/report1
How to solve this issue ?
I solved the issue by moving the resource as proposed in jasperServer rest client API.
OperationResult<ClientResource> result = client
.authenticate("jasperadmin", "jasperadmin")
.resourcesService()
.resource("/reports/category1/report1")
.moveFrom("/reports/cat1/report1");
I'm trying to setup Microsoft reporting on a shared hosted server. I've set up the web.config files with the necessary entries and uploaded the assemblies Microsoft.ReportViewer.Common.dll and Microsoft.ReportViewer.WebForms.dll as well as the file Microsoft.ReportViewer.xml via FTP.
The site loads OK, but when I try to load a report a get a missing reference to Microsoft.ReportViewer.ProcessingObjectModel.dll. If I can get a hold of a copy of this dll, can I expect the report view to work? If so, what's the best way to get a copy? Or should I start trying to cajole the server administrator to run ReportViewer.exe?
This project is using Visual Studio 2008.
It appears that the answer is yes. I had never extracted a file from the GAC before, but it was pretty easy by following the command line method described in this question. Once the correct version of Microsoft.ReportViewer.ProcessingObjectModel.dll was extracted from the GAC on my development machine and uploaded to the site, the reports started working.
I am developing J2EE application with crystal report. When deploying in tomcat server working fine but when am deploying in weblogic getting following error. I don't know how to fix. Any advice?
The viewer was unable to find the resources required to render the
report. Please check the following to resolve the issue.
Verify that ../../crystalreportviewers120/ is accessible to your WebApp and is the correct path to the viewer resources.
You may customize this location by altering the crystal_image_uri and crystal_image_use_relative properties in the web.xml.
Validate that the file crv.js exists at ../../crystalreportviewers120/js/crviewer/crv.js.
When using The Report Viewer JSP Wizard to create a JSP to call the report viewer, automatically a folder named cristalreportviewers is created under WebContent, which contains all resources required to publish the rpt file. It is required to declare its location to the web.xml file. The Developer Guide for Report Viewer declares how to setup both crystal_image_uri and crystal_image_use_relative properties: You need to declare the relative path to that folder (and its right name) for the first property, and set the interpretation of the crystal_image_uri to be relative to the web page, application, or server, for the second property. The name of folder changed from a version to another: While message refers to cristalreportviewers120, in CR 2011 it is named whitout the "120" suffix. Put the right name in the crystal_image_uri parameter.
Copy the crystalreportviewers120 directory (found in C:\Program Files\Common
Files\Business Objects\3.0) to a subdirectory of the same name directly
underneath the Project directory (as a peer to WEB-INF). Ensure that all
contents, both files and subdirectories, are copied—there should be about 150
files in all.
Reference:-
Crystal Reports XI for J2EE Startup Guide.pdf
My manager asked me to update the .rdl file from prod to dev. But before doing that I have to keep that old report as it is and have to create a duplicate report on same server and that too be I am working on browser.
I have downloaded the the .rdl file and renamed the report as *_old also. But I am not able to understand how to create another same report with same datasources and everything.
I can see an option update next to edit button. I am assuming that if I get a duplicate report on the same server I can update the .rdl file with that update button.
Please help me with this problem.
- Download the report RDL file from the report manager.
- Rename the rdl file eg. MyReport1_old.rdl
- Upload the report rdl file from the report manager.
Now you will have the original report (MyReport1) and the copy of it(MyReport1_old).
We're about to start development of a number of reports using Jasper Server Reports version 3.7.0 CE.
Does anyone have any recommendations as to how best to manage version control with this development, given that the structure of the report units is managed in the database and through either iReport or the web front end?
In fact you can import/export to a directory structure using the js-import/js-export scripts, but then you can't edit these files directly with iReport.
Does anyone have any pointers?
This is problematic. I have established a subversion repository to allow standard reports delivery to be versioned but it is a real pain because jasper does not make this even a little bit easy.
I created a maven project with an assembly descriptor so that "src/main/xml/resources/Reports,adhoc,Domains, etc" can be packaged up in a zip that is pushed to our maven repository.
The biggest problem is that you can't just develop adhoc and input controls merely by modifying XML files. The developer has to import what is in source control into a working jasper server, modify the reports or add new ones (after making sure that his organization and datasources are configured) and once he's satisfied that the report(s) works, export the resources to a directory or zip file, manually modify all references in the exported files from datasources and organization specific resource locations back to "generic" before checking in his changes.
When importing into jasper, the same process has to be done in reverse. The generic paths and organization values have to be converted to the developer's organization so they can be easily imported/updated and he can prove out that the full "round trip" works properly before checking in.
To make the export/subversion checkin easier, I created an ant build file which lives in the maven project's root dir. The build prompts (or will read a properties file) to determine the exported zip location, the organization id of the exported tree. It then opens exported zip file from jasper, explodes it, performs text replacements on the files, resets the "createdDate" and "updatedDate" elements to something standard (so that the developer does not end up checking in files that haven't actually changed since jasper does not preserve the date values), and then copy the files into the subversion tree.
For the import process (from the subversion tree into jasper) we have a script that takes as input the organization id and then modifies the versioned xml files to the appropriate values so that the entire tree can be easily imported/updated into their organization.
The reason this level of complexity is required is to allow us to create the same standard reports in a multi-tenant environment, plus jasper's notion of deploying reports is absolutely bizarre. I'm not sure it would be possible to make this process more difficult if you were intending to do so.
If I was in your position I would have established this kind of process:
end of development session: export all reports to a directory structure in a project under version control
commit the project
before next development session: synchronize the project with svn repository
import directory structure to Jasper Server Reports
continue development
Not sure if someone found posted the solution.
This is what I have done for existing reports.
export reports from jasper server
modify file names from .data to .jrmxl
modify subreport calling to add extension (like in A.jrxml should have subreport name as B.jrxml
modify add .jrmxl to datafile,label and name in report unit xml files.
If you are creating new report on jasper server, it simple
give .jrxml to name and label while adding jrxml file. thats it.
Now you can work same files in local and import same to jasper server.