Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 342387

Summary: connection profile change is not working in birt 2.2.2 at runtime
Product: z_Archived Reporter: subbarao <subbu2ats>
Component: BIRTAssignee: Linda Chan <lchan>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: bluesoldier
Version: 2.2.2   
Target Milestone: 3.7.0   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description subbarao CLA 2011-04-11 00:07:15 EDT
Build Identifier: Version: 3.3.0 Build id: I20070625-1500

Hi.. i am using birt2.2.2 eclipse for desining the reports.so i created new connection in connectivity--> Data Source Explorer. and export those details in a single text file and copied that to C: drive

now i m getting the datasource by selecting this text file for connection profile option in birt eclipse. suppose if i change the userid and password in that txt file, automaitcally its effects in the datasource..fine.

now i downloaded birt runtime 2.2.2 and integrate with my work bench and i called that report working fine. now if i change the userid or password in the txt file, it is not effecting in the reports at run time.its taking the old connection and get those old detail.

so plz let me know whts going..on. and how to do  solve this. bcoz i need to change the connection at runtime at diff servers


Reproducible: Always
Comment 1 Linda Chan CLA 2011-04-11 21:28:21 EDT
It appears that when your report design is deployed to runtime environment, it is  not finding the referenced connection profile store file.  And so it falls back to use the connection properties defined locally in the data source.  You can verify by removing the local data source property values in the report design, e.g. by manually editing the xml source, and just keep the connection profile properties.  So if the referenced profile store file is not found, it won't have the local properties to fall back to, and would get a connection error.
In any case, check the connection profile store file path specified, and make sure your runtime environment has access to it.

For further how-to questions, please post to the BIRT user newsgroup instead.