Differences

This shows you the differences between two versions of the page.

--- jasperreports_systems_administrator_guide [2024/03/24 06:54] – [Configuration Notes] ghachey
+++ jasperreports_systems_administrator_guide [2024/12/15 04:51] (current) – [Catalog Restoration] ghachey
@@ Line 6: / Line 6: @@
 Unless you want to not use the bundled Tomcat and PostgreSQL then the only dependency to install is the Java Development Kit (JDK). The JasperSoft Platform Support Guide is the best place to look to decide what version to install. The JDK version 8 is our preferred choice at more recent Java are still only use to runtime only and need version 8 compatibility for compiling reports.
+Here is a good time to set the JAVA_HOME environment variable. On windows you can do this permanently from start menu "Edit the system environment variables". Add the new JAVA_HOME=C:\Program Files\Java\jdk-1.8. Then add to the existing PATH list of items %JAVA_HOME%\bin. This will be handy for using Java tools from the command line specifically when using the JasperServer buildomatic tools.
 ==== Microsoft Visual C++ Redistributable ====
@@ Line 92: / Line 94: @@
   * **font-extension.jar**: Used to support the new custom fonts in jasper server. Can be added directly in **<Jasper Server>\apache-tomcat\webapps\jasperserver\WEB-INF\lib**
   * **reporting-1.0.jar**: Used as a chart customizer to customize the look of exams reports among potentially others. Can be added directly in **<Jasper Server>\apache-tomcat\webapps\jasperserver\WEB-INF\lib**
-  * **sqljdbc4-VERSION.jar**: Used for JBDC connection to interact with the MS SQL Server. Often loaded directly from the UI of JasperServer when creating the data source or in JasperSoft Studio.
+  * **sqljdbc-VERSION.jar**: Used for JBDC connection to interact with the MS SQL Server. Often loaded directly from the UI of JasperServer when creating the data source or in JasperSoft Studio.
 Restart the server when adding the jars for the first time.
@@ Line 185: / Line 187: @@
 </code>
-Change password of the key of interest. This password could also be made simple and convenient but then you would be best to change it in the production stored after ward for tighter security. Another approach is to make it a good password right away and as it gets imported it keeps this password.
+Change password of the key of interest (i.e. importexportencsecret). This password could also be made simple and convenient but then you would be best to change it in the production stored afterward for tighter security. Another approach is to make it a good password right away and as it gets imported it keeps this password.
+<note important>If you do keep to change to a strong password bare in mind that some characters will cause issues as you pass then as command line arguments. So if something goes wrong you may want to look at that first.</note>
 <code>