Environment: Weblogic 10.3
BIRT runtime: 2.5.1 or 2.5.2
I have been trying to get the sample BIRT Report viewer working in Weblogic 10.3, and have a question. I have deployed the viewer as an ear and seem to lose http session information (in particular authentication info). I'm currently calling the report directly from javascript, on a web application jsp via something like this:
<span onclick="window.open('
http://10.10.10.10:7001/rpt_viewer/run?__report=report_templates_birt/Development/6_all_contracts_report.rptdesign','ContractsbyServiceType','left=10,top=10,width=800,height=650,toolbar=0,resizable=1');">Contracts by Service Type</span>
This seems to work fine when the url I'm accessing is on another server. I've tried deploying to another weblogic managed server, domain, etc but there are problems. What I'm seeing is that when the viewer is deployed on the same app server, the application session (e.g. user authentication information) completely goes away, thus I have no session information available and the user gets logged out. The application I am logged in is under https:. One catch, when the viewer is deployed on a completely different server everything is fine.
I've traced the httpsessionlistener and even added a servlet filter on the BIRT viewer code and notice that when the viewer is located on a different server the http session information (id, etc) is preserved. I understand the viewer session is a subset of the http session, but I don't see this when the viewer is deployed on same server. I want to be able to deploy the viewer and reports on the same server that other webapps are.. I am already aware of js.jar conflicts in weblogic, but seem to have gotten past that.
I want to leverage the viewer capabilities to input parameters, export, etc. Are there other ways people are calling the viewer?
Any help is much appreciated!
-Scott
