|
| Re: Server Side 'Connection Profile' Usage [message #672266 is a reply to message #672040] |
Fri, 20 May 2011 13:29  |
|
Kado,
I know some users are putting the connection profiles in the resource
folder of the deployed viewer and then setting the profile location in
the beforeOpen of the dataset like:
var myresourcefolder = reportContext.getDesignHandle().getResourceFolder();
this.setExtensionProperty("OdaConnProfileStorePath",
myresourcefolder+"/myprofile.dat");
Jason
On 5/19/2011 12:44 PM, forums-noreply@eclipse.org wrote:
> Hello Gurus,
>
> I am using BIRT to create reports on my local machine (Mac OS X) that
> are then moved to a Linux cloud server (Amazon) which also has a copy of
> the MySQL connector (JAR file) in the same location as my machine (so
> when the XML file, the .rptdesign, is moved up it looks for the JAR in
> the same location and has no problem finding it). These reports is then
> available as an in-line view via a URL that my users incorporate into
> our Sugar CRM system.
>
> This all works great with the database logon built into each XML file
> (whereas each reports logon is independent of the other) but I would
> like to leverage a 'Connection Profile' so that the DB logon for each
> report looks in the same spot (which will make scaling much easier). No
> problem on my local instance using Eclipse/Birt etc.
> But I would like to put the necessary files for the Connection Profile
> on the Linux server (which does not have an Eclipse install) so that
> when the reports are moved up it knows where to find what it needs to
> successfully run the reports. I have taken the simpleton's approach and
> just tried to move the files for the Connection Profile up from the same
> location on my machine to the server but this does not work.
>
> Any suggestions? Thoughts? How-To's anyone out there would recommend?
> THANKS,
> Kado
|
|
|
Powered by
FUDForum. Page generated in 0.03124 seconds
] 
Search
Help
Register
Login
Home
