|
| Re: BIRT 2.7 WebSphere 7 [message #901635 is a reply to message #901558] |
Mon, 13 August 2012 17:17   |
|
Graham
Do reports with tables appear fine or do they fail as well? Do you get
anything in the log?
Jason
On 8/13/2012 7:54 AM, Graham Crooks wrote:
> I have created a simple pie chart with a drill through to a table within
> eclipse.It works fine in the preview and I have followed the
> instructions on the BIRTPOJO Viewer, albeit there are no instructions
> for WebSphere 7 so I have deployed as per the WebSphere 6 instructions.
> When I run the /birt/index I see the header but no chart
> The same happens when I run my report I see the header and the date but
> no Pie chart.
> Can anyone give me the instructions for BIRT 2.7 POJO deploy on
> WebSphere V7 and also give me any suggestions why the charts etc are not
> showing
> Thanks
|
|
|
|
|
| Re: BIRT 2.7 WebSphere 7 [message #901662 is a reply to message #901659] |
Tue, 14 August 2012 00:10 |
|
Graham,
Can you set the log level to FINEST in the web.xml and see if you get
anything in the log. Also can you post screenshot of the
test1.rptdesign output that you got?
Jason
On 8/13/2012 7:08 PM, Graham Crooks wrote:
> Just an update I have looked at the classloading Search Order in
> WebSphere and sure enough the birt.war... is being searched first
|
|
|
|
| Re: BIRT 2.7 WebSphere 7 [message #903229 is a reply to message #903173] |
Wed, 22 August 2012 15:27 |
|
Graham
Can you post the report? From the error it does look like you are using
connection profiles.
Jason
On 8/22/2012 7:47 AM, Graham Crooks wrote:
> Hi Jason
> This is appearing to hard and taking my time so I thought I would follow
> the basic direction and download Tomcat and deploy my application to
> this and now another issue
> This should be simple I created a report in Eclipse created the DB2
> Datasource and DataSets, created a Chart with a Drillthru to a table
> report and it all works in the Eclipse Preview
> The instructions for deploying to Tomcat are 4 lines which seems to be
> completely oversimplified as there is no mention of Datasources except
> to copy my DB2 jars to the lib directory.
>
> It keeps mentioning profiles of which I don't believe I am using so I
> figure I must be missing something. I see a few other people are getting
> the same error, but don't see a documented resolution.
> Any assistance would be great as my project is falling behind
>
> Chart (id = 32):
> - An exception occurred during processing. Please see the following
> message for details:
> Cannot open the connection for the driver:
> org.eclipse.birt.report.data.oda.jdbc.dbprofile.
> org.eclipse.datatools.connectivity.oda.OdaException ;
> java.lang.IllegalStateException: Unable to determine the default
> workspace location. Check your OSGi-less platform configuration of the
> plugin or datatools workspace path. (Element ID:32)
>
> exception.error ( 1 time(s) )
> detail : org.eclipse.birt.report.engine.api.EngineException: An
> exception occurred during processing. Please see the following message
> for details:
> Cannot open the connection for the driver:
> org.eclipse.birt.report.data.oda.jdbc.dbprofile.
> org.eclipse.datatools.connectivity.oda.OdaException ;
>
|
|
|
|
| Re: BIRT 2.7 WebSphere 7 [message #903421 is a reply to message #903378] |
Thu, 23 August 2012 14:49 |
|
Graham,
I would suggest you first just use a jdbc connection (no profile) to
verify everything else is working.
Once that is done you can get your profile working. I believe yours is
failing because of its location.
In the profile that you are using open the report double click on the
data source and the data source editor should display. Click on the
Connection Profile in the list view. It should give you a connection
profile store location. This is where the report will look for it when
you run the report. You can change this value based on script or the
Property Binding feature. Look at the Property Binding property in the
same editor. You can can change the Connection Profile Store URL at
runtime.
Take a look at this message for more details
http://www.eclipse.org/forums/index.php/m/736103/
Take a look at this example that sets the profile based on a parameter:
http://www.birt-exchange.org/org/devshare/designing-birt-reports/251-dynamic-location-for-birt-connection-profile-store/
You may also want to look at this:
http://www.birtreporting.com/BIRT%20Connection%20Profiles.pdf
Jason
On 8/23/2012 8:36 AM, Graham Crooks wrote:
> Thanks Jason
> I have moved on a little and have figured out how to create a profile
> What I did was used the datasource I created for the report in the Data
> Explorer View and right clicked and selected "Externalize to Connection
> Profile"
> When I right mouse click and look at the properties it shows under the
> ODA DataSource it shows Connection Profile Store & URL
> C:\Ward2E_Repository\build\.metadata\.plugins\org.eclipse.datatools.connectivity\ServerProfiles.dat
>
> So it seems like it updates the ServerProfiles.dat file.as it shows
> updated with todays time and date
> I have copied the file to the ServerProfiles.dat file to the
> R:\apache-tomcat-6.0.35\webapps\Birt\WEB-INF\lib
> So all should be good but when I run the report
> The following items have errors, so it does appear that I have moved
> on,but not there yet
>
> Thanks
>
> Chart (id = 32):
> - An exception occurred during processing. Please see the following
> message for details:
> Cannot open the connection for the driver:
> org.eclipse.birt.report.data.oda.jdbc.dbprofile.
> org.eclipse.datatools.connectivity.oda.OdaException: Unable to find
> the connection profile referenced by the data source connection
> properties. ;
> org.eclipse.datatools.connectivity.oda.OdaException: Unable to find
> or access the named profile (WSE Export Data Source) in profile store
> path
> (C:\Ward2E_Repository\build\.metadata\.plugins\org.eclipse.datatools.connectivity\ServerProfiles.dat).
> ;
> org.eclipse.datatools.connectivity.oda.OdaException ;
> java.lang.IllegalStateException: Unable to determine the default
> workspace location. Check your OSGi-less platform configuration of the
> plugin or datatools workspace path. (Element ID:32)
>
> exception.error ( 1 time(s) )
> detail : org.eclipse.birt.report.engine.api.EngineException: An
> exception occurred during processing. Please see the following message
> for details:
> Cannot open the connection for the driver:
> org.eclipse.birt.report.data.oda.jdbc.dbprofile.
>
|
|
|
|
| Re: BIRT 2.7 WebSphere 7 [message #903613 is a reply to message #903504] |
Fri, 24 August 2012 14:28 |
|
Graham,
Connection profiles should work fine. I have them working in two tomcat
instances. When you are creating the connection profile you should have
the option of creating it at a certain location and at runtime you can
use property binding to change it. If you have time for a skype session
I can look at your deployment and help find the issue.
Jason
On 8/23/2012 10:07 PM, Graham Crooks wrote:
> Hi Jason
> I am more than happy NOT to use profiles but even not using them it seems BIRT is trying to solve the dbprofile
>
> I have jdbc working perfectly in eclipse as per my diagram.
> I can just select review and it works a treat
> I am confused in the difference between the DataSources that I used to create the report and the DataSourcesExplorer which has others.
> Am I right I need to set up this jdbc connection in Tomcat as a standard jdbc deploy ?
>
> It seems that the profiles don't seem to work relative or absolute so more than happy to ditch this and just use jdbc.
> In WebSphere when I deploy a jee application I have to setup jdbc nd jndi
> I am thinking in the absence of any documentation I would need to do the same for Tomcat
>
>
>
>
>
|
|
|
|
|
| Re: BIRT 2.7 WebSphere 7 [message #904010 is a reply to message #903718] |
Mon, 27 August 2012 14:56 |
|
I sent you a skype invite.
Jason
On 8/24/2012 10:21 PM, Graham Crooks wrote:
> Jason
> As you say should work fine
> I can give you remote desktop access to the system if that helps
> A few clicks and you are in
> Thanks
|
|
|
Powered by
FUDForum. Page generated in 0.31987 seconds
] 
Search
Help
Register
Login
Home
