tkavanagh

There are actually a number of scenarios where the postgresql fails to complete its initdb correctly. Unfortunately, Postgresql is pretty sensitive to the configuration and permissions of the underlying operating system. Recently, I've been seeing more errors with Windows when Windows is running as a virtual machine and when the installation drive used is not C:. This looks to be because the windows permissions and authorization on drives such as D: or E: are not what they are reported to be when looking at the permissions using the windows admin tools.
But there was definitely and error with Postgresql when installing to a windows folder which is a symbolic link. The fix in the installer for this issue was to detect that the folder is a symbolic link and give a warning message for the user to choose a different folder.

For JasperReports Server (just the normal download of the installer and installation), the translation bundles are included by default. The languages that are there by default are: Chinese, Japanese, English, French, Spanish, Italian, Romanian, and German. 
For the new 5.5 release, there is also Brazilian Portugese. 
On the Login page, look to the right side drop down box where you can choose the default language to be used. 
 

Hi, this is just the default way that PostgreSQL operates. I think this is the case because there is also Connection Pooling that is specified in the Application Server (ie most commonly Tomcat). And tomcat will use the connection pooling defined here: <tomcat>/webapps/jasperserver/META-INF/context.xml. This is setup to utilize multiple connections to service multiple users when tomcat is running (or other conncurrent operations such as scheduled jobs).
 
However, you can start up just PostgreSQL by itself, without Tomcat. And you will see mutiple postgres threads. I see the same pattern when just postgresql is running whether on linux, Mac, or windows. But with mysql, I usually see two or only one process.
You could try reducing max_connections and see if that changes the number. I see a lot of discussion about increasing max_connections but very little about decreasing them.
 
  http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server

There definitely seems to be an issue with resolving the hostname. I see in the installation.log:
  Unable to set localhost. This prevents creation of a GUID. Cause was: dilx: dilx     
  java.net.UnknownHostException: dilx: dilx     
  at java.net.InetAddress.getLocalHost(InetAddress.java:1353)     
  at net.sf.ehcache.Cache.(Cache.java:214)
Here is a similar issue based on googling around for the above error message:
stackoverflow.com/questions/4969156/error-java-net-unknownhostexception
So, perhaps try playing a bit more with the /etc/hosts file. And try adding the following (and rebooting too):  
127.0.0.1   dilx       localhost

Hi Lisa, there isn't a really "nice" way to upgrade from an instance that was installed with the Windows installer when you install in the default mode. This is because there are "hard coded" menu paths from the original installation that has things like "-4.5" in the path. So, when you upgrade that 4.5 instance to 4.7, some of the paths will still be "-4.5" even though the instance has been upgraded to 4.7.
This is less of an issue under the linux installer (because the menuing is simpler).
Many customers use the installer version to get started and learn the product. But when they move to more of a "production" roll out for the company's users - they install a separate app server (ie tomcat) and a separate database (ie postgresql). Then the jasperserver install goes to those two applications. And then when it is time to upgrade the app server and database can be upgraded and there are not any issues about "hard-coded" paths.
I hope that helps a little bit.
 

Hi Steven, 
Yes, you should create the default_master.properties file. And it should be located in your buildomatic folder. 
To do this, you should start with one of the sample property files and then change the name. There is one property file per supported database. (For Community, it's just postgresql and mysql - but for Pro version there are 5 supported dbs). 
So:
  cd Users/jasper/Desktop/jasperserver-ce-3.7.0-bin/buildomatic
  copy sample_conf/inst-mysql_master.properties  to buildomatic/default_master.properties
  edit default_master.properties
    - point to your application server
    - point to your database (and give db credentials)
  js-ant create-js-db
  js-ant init-js-db-ce
  js-ant import-minimal-data-ce
  js-ant import-sample-data-ce (optional)
  js-ant deploy-webapp-ce
These steps are described in the <js-install>/docs/JasperServer-CE-Install-Guide.pdf, in Section 5 Install from the War File Distribution ZIP.
If you load the sample resources, then you should also create the sample databases (they are called foodmart and sugarcrm). The Install Guide specifies the 5 targets that you need to type in for this. 
You will need to *already* have a Tomcat and MySQL installed to carry out the installation. 
However, the good news is that there is a Mac OSX installer that will be included with the next JasperServer release (it will be the 4.0 version). It's due out around the beginning of the year. So, I am looking forward to feedback about the Mac installer when that is out.
Also, the other good news is that the buildomatic scripts have been upgraded in 4.0 so that (once you have a tomcat and mysql in place), you can run a single command (js-install.sh) and everything described above (after you create your default_master.properties) will be done automatically. (ie for folks who do not want to run the installer).

Yes, you can schedule reports in JasperServer via iReport (and it's jasperserver-plugin).

I think it is best to look at the JasperServer-Web-Services-Guide.pdf, which you can find in the <js-install>/docs directory.
 
Look for Section 3.0 "Report Scheduling Web Services". It talks about parameters such as JobRepositoryDestination and JobSimpleTrigger, startDate.
 
I'm pretty sure that iReport makes use of all this functionality and presents it via the plugin UI.