This page (revision-5) was last changed on 26-Nov-2021 10:22 by JMyers

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
5 26-Nov-2021 10:22 2 KB JMyers to previous
4 26-Nov-2021 10:22 3 KB JMyers to previous | to last
3 26-Nov-2021 10:22 3 KB JMyers to previous | to last
2 26-Nov-2021 10:22 3 KB JMyers to previous | to last
1 26-Nov-2021 10:22 2 KB JMyers to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 changed one line
!!!SETUP TO USE WINDWARD ON LINUX
!!!SETUP TO USE WINDWARD WITH Personality ON LINUX
At line 3 changed one line
The purpose of this white paper is to give instructions to put the required fonts (Arial Family) on Linux and configure the Windward environment to get the proper formatted report output.
This setup allows you to put the required fonts (Arial Family) on Linux and configure the Windward environment to get the proper formatted report output.
At line 7 changed one line
Since all the reports that High Line has created make use of some version of Arial font, this typeface needs to be purchased. Microsoft has designated Ascender Fonts [http://www.ascenderfonts.com ] to be an authorized distributor of this font. The Arial font set includes Arial Bold, Arial Italic and Arial Bold Italic as well.
Since all the reports that have been created make use of some version of Arial font, this typeface needs to be purchased. Microsoft has designated Ascender Fonts [http://www.ascenderfonts.com ] to be an authorized distributor of this font. The Arial font set includes Arial Bold, Arial Italic and Arial Bold Italic as well.
At line 12 changed 4 lines
a. The following command is entered at a shell prompt, in the directory the WindwardReports.jar file is located, to test the availability of the new font:
java -classpath "WindwardReports.jar" net.windward.tools.ShowFonts
b. The output is a list of fonts that Windward will be able to make use of. If the Arial font is not in the list, it will be substituted in the PDF output with an equivalent font [most likely Helvetica].
4. IF the font is not in the list, upload the four font files into the $JAVA_HOME/lib/fonts directory and test again (Step 3). Since Linux can have multiple versions of Java installed at the same time, these may need to be repeated for each Java home until the font appears in the list.
#*The following command is entered at a shell prompt, in the directory the WindwardReports.jar file is located, to test the availability of the new font:\\java -classpath "WindwardReports.jar" net.windward.tools.ShowFonts
#*The output is a list of fonts that Windward will be able to make use of. If the Arial font is not in the list, it will be substituted in the PDF output with an equivalent font (most likely Helvetica).
#IF the font is not in the list, upload the four font files into the $JAVA_HOME/lib/fonts directory and test again (Step 3). Since Linux can have multiple versions of Java installed at the same time, these may need to be repeated for each Java home until the font appears in the list.
At line 17 changed 2 lines
Windward Configuration
Once the font has been installed and verified that it's available, the Windward properties must be set correctly. This is done within the WindwardReports.properties files, located in the 'home' instance directory of the application server [$JAVA_HOME/j2ee/home]
!!Windward Configuration
Once the font has been installed and verified that it's available, the Windward properties must be set correctly. This is done within the WindwardReports.properties files, located in the 'home' instance directory of the application server ($JAVA_HOME/j2ee/home).
At line 20 changed one line
Configuration File
!Configuration File
At line 22 changed 6 lines
1. “font.files” should be set to the location of all TTF files. For example:
font.files=/usr/local/share/fonts/TTF/*.ttf;/usr/lib/java-1.5.0/jdk1.5.0_11/jre/lib/fonts/*.ttf
2. “'pdf.font_level” should be set to 2 to have the PDF file contain the font itself. For example:
pdf.font_level=2
3. “line.break” is required to be set as internal and thus must be uncommented. For example:
line.break=internal
#“font.files” should be set to the location of all TTF files. For example:\\font.files=/usr/local/share/fonts/TTF/*.ttf;/usr/lib/java-1.5.0/jdk1.5.0_11/jre/lib/fonts/*.ttf
#“'pdf.font_level” should be set to 2 to have the PDF file contain the font itself. For example:\\pdf.font_level=2
#“line.break” is required to be set as internal and thus must be uncommented. For example:\\line.break=internal
At line 29 changed 3 lines
Test
This properties file is only read by the application server during the initial start up of the application server instances, thus you must restart both the 'home' instance and the OC4J instance that is running ePersonality.
After the application server instance has been restarted, log into ePersonality and run any Windward report, generating a PDF file. Open the resulting output file and verify the fonts used from the Files/Properties dialog.
!Test
This properties file is only read by the application server during the initial start up of the application server instances, thus you must restart both the 'home' instance and the OC4J instance that is running Personality.\\
After the application server instance has been restarted, log into Personality and run any Windward report, generating a PDF file. Open the resulting output file and verify the fonts used from the Files/Properties dialog.
At line 29 added 3 lines
----
![Notes|Edit:Internal.SETUP_WINWARD_ON_LINUX]
[{InsertPage page='Internal.SETUP_WINWARD_ON_LINUX' default='Click to create a new notes page'}]