Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Intelligence (Analytics)
Web viewer, Firewalls & antivirus
ALyons
Hi All,
My company has an eclipse product that integrates the BIRT web viewer. The integration and deployment went smoothly however one of our users had an issue with Avast anti virus blocking the loopback connection that BIRT tries to establish.
This has us a little concerned as while most of our users should be unaffected no doubt some of them will have tight security settings and we would like to get an idea of what networking activities BIRT needs to operate correctly.
Is there a list of ports and or connections that BIRT needs to operate?
Are there any known issues with anti virus products?
Any help will be appreciated.
- Adrian
Find more posts tagged with
Comments
mwilliams
I've not seen anyone have an issue with a virus software blocking BIRT. In a quick Google search, I wasn't able to find anything either. Is your user deploying the viewer on their own machine? Or is the viewer in your app on your server and they're just accessing it and having issues?
ALyons
Hi Michael,
We have an Eclipse RCP application into which we packaged BIRT. Our method of launching reports is:
- Generate an xml file (we use the BIRT XML ODA plugin).
- Call WebViewer.startup();
- Open our report viewer (which is just an editor with a SWT browser).
- Generate the browser URL (we do this manually rather than using the webviewer).
- Set the browsers URL.
This has worked without issue for quite a while. Only when did the user install the paid version of avast anti virus which included a firewall did we get an issue, once he turned off the firewall it worked as normal. I'm advising that user to add an exception for our product as a temporary fix.
I'm attaching a section of the log file that shows the stack trace if it helps.
What I'm mostly looking for is a description of ports and connections BIRT establishes so we can at a minimum inform the users what they will need to configure to allow the reports to work.
Thanks
- Adrian