Jump to content
We've recently updated our Privacy Statement, available here ×

shmee

Members
  • Posts

    37
  • Joined

  • Last visited

 Content Type 

Profiles

Forum

Events

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Downloads

Posts posted by shmee

  1. There is more to it then just one line.  If you read the whole file you will see several lines that need to be uncommented, and configured. 

    Also do not save backup copies of the file in the same location because JasperServer loads all the .xml files in that location.

    Where are you trying to get your LDAP queries from? Since different LDAP sources have different changes to the file.

    There are several examples in this forum of people getting this to work, if you look around.

  2. I fixed my issue, which was similar, by using a stand alone version of Tomcat 7 (which is the managed version in Ubuntu 12-4), and then doing a WAR installation.  And following the upgrade steps from the install guide for using a new DB.  It is also important to use the export script from the /buildomatic folder from the old version of JasperServer, so in this case the 4.5 version.

  3. When I do an upgrade from 4.5 to 4.7, everything says it installed OK, but when I go to the web page all I get is an Internal Error Has Occurred please contact the Systems Administrator Details:

    But it lists nothing under the Details.

     

    Anyone seen this and able to help?

     

    I have attached the imaged of what the screen looks like.



    Post Edited by shmee at 09/10/2012 18:08



    Post Edited by shmee at 09/10/2012 18:08
  4. Is there a change log for this project?  The one you have only goes to 3.7.  It would be handy to know what has changed when we are performing upgrades.

    Thanks.

  5. I upgraded our JasperServer from 4.0.0 to 4.1.0 and every thing seemed to work just fine, until I tried to log in with my LDAP.  It seems like every release changes something with the Active Directory LDAP.

    I am using the same applicationContext-security.xml as with 4.0.0 but I am getting errors.  Is there something that changed that I should know about?

  6. Depending on the type of machines you have at your disposal you could always setup your own SMTP, or at least install Sendmail if you are on linux, since I am guessing you are mostly sending your reports to internal users. That way you are not always at your SMTP providers mercy.
  7. Thanks for the tips guys! I was just thinking about how I wanted to audit the JasperServer, so I checked the forum, and this thread got me started.

     

    Though it would be much cooler to have built in user and report auditing.

  8. Well the jar that you are looking for would depend on that database you are connecting to and the platform it is running on. Because I also connect to DB2 but on an iSeries server, so the jar I always need to add to lib is jt400.jar
  9. Well if you are not using Active Directory then it should be different.

     

    If you look at one of your groups through an LDAP browser then you will that the "cn" is the name of the group and that the people or objects in the group are all listed as "member".

     

    That is where those values come from. If you are not using AD then I don't know what your values are or should be, but getting a good LDAP browser will help you out a lot. Though my LDAP auth is still not working so maybe you shouldn't be taking my advice.

  10. I have not heard or seen that before but it might help us track the issue down if you posted any relevant logs, and your system configuration (eg. server version, OS it is running on, amount of RAM etc.)

     

    You also may want to check the power saving config on your NIC on the server, to make sure it is not going to sleep or something lame like that.

×
×
  • Create New...